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 OUTL-BRT-WACS_ERPPM_Email_ID lookup.
Summary of Integration Error Handling
Integration Process: OU ERPPM WACS Project Sync
Type of error
Action
Notification Type
Retry
Remote
 
Example: WACS is not accessible
Stop process
Email
Resubmit the error instance from OIC.
Business
 
Example: Worktype not configure in lookup
Stop process
Email
 
 
Integration Process: OU WACS ERPPM Task Sync
Type of error
Action
Notification Type
Retry
Remote
 
Example: WACS is not accessible
Stop process
Email
 
Business
Stop process
Email
 
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.