Error Handling
This section provides information about the different ways used to handle errors in the integration and also resubmitting the instances after rectifying the errors.
Error Handling Ways
In this integration, all integration flows are asynchronous. This section describes error handling for asynchronous flows.
Asynchronous Flow Error Handling
Technical Fault
This fault occurs when there is a datatype mismatch or any Xpath related error.
Remote Fault
This fault occurs when the target system is down or not accessible.
Business Fault
These faults are application-specific faults that occur when there is a problem with the information being processed in the target application due to invalid data or business error validations.
When the file completes processing, an optional email is sent with the list of remaining errors to the respective users configured in the OUTL-BRT-WACS_ERPSCM_EMAIL_ID lookup.
Summary of Integration Error Handling
Integration Process: OU ERPSCM WACS Active Storeroom Sync
Type of error
Action
Notification Type
Retry
Technical
Example: No files to extract in the UCM
Stop process
Email
 
Remote
 
Example: If the Address is missing from ERP
Continue process
Collect errors and send errors in message
 
 
Integration Process: OU ERPSCM WACS Inactive Storeroom Sync
Type of error
Action
Notification Type
Retry
Technical
 
Example: Incorrect BIP report path in the lookup.
Stop process
Email
Resubmit the scheduler correct path
Remote
 
Example: If the Address is missing in the storeroom record from ERP.
Continue process
Collect errors and send errors in message
 
 
Integration Process: OU ERPSCM WACS Storeroom SID Sync
Type of error
Action
Notification Type
Retry
Remote
 
Example: If the WACS service is not accessible.
Stop process
Email
 
 
Integration Process: OU ERPSCM WACS Stock Item Detail Inv Adj Extract
Type of error
Action
Notification Type
Retry
Technical
 
Example: BIP in ERP is not accessible.
Stop process
Email
Resubmit the fixed asset addition error instance from OIC
Remote
 
No adjustments records found.
Stop the flow
Email
 
Business
Continue process
Collect errors and send errors in message
 
 
Integration Process: OU ERPSCM WACS Stock Item Detail Inv Adjustment
Type of error
Action
Notification Type
Retry
Remote
 
Example: WACS service is not accessible
Stop Process
Email
 
Business
Continue process
Collect errors and send errors in message
 
 
Integration Process: OU ERPSCM WACS Stock Item Detail Bulk Load
Type of error
Action
Notification Type
Retry
Remote
 
Example: WACS is not accessible
Stop process
Email
Resubmit the error instance from OIC.
Technical
 
Example: No file fund
Stop
Email
 
Business
Continue process
Collect errors and send errors in message
 
Business
 
Example: If UOM is missing
Skip record and continue process
Collect errors and send errors in message
 
 
Integration Process: OU ERPSCM WACS Stock Item Detail Incremental Sync
Type of error
Action
Notification Type
Retry
Remote
 
Example: WACS is not accessible
Stop process
Email
Resubmit the error instance from OIC.
Business
Continue process
Collect errors and send errors in message
 
Resubmitting the Error Instances in Oracle Integration Cloud
In this integration, all processes are asynchronous flows so the resubmit option is available in Oracle Integration Cloud if the process ends in a fault.
To resubmit the error instances in Oracle Integration Cloud:
1. Login to Oracle Integration Cloud.
2. Navigate Integrations > Monitoring > Errors.
3. Select the integration to resubmit.
4. Click the Resubmit icon.