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/Synchronous Flow Error Handling
Technical Fault
This fault occurs when there is a data 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.
Vendor/Vendor Location Sync and Blanket Contracts Sync: For processing records in a file
When Oracle Utilities Work and Asset Cloud Service returns HTTP status codes 400 or 500, these are considered business faults by the integration. When these errors occur, the flow will not stop but continue to process the next record and the errors will be stored in a temporary error collection. Optional emails are sent when error count reaches the value specified for maxerrorcount.per.email.notification, email with error details is sent.
When the file completes processing, an optional email is sent with the list of remaining errors to the respective user.
Summary of Integration Error Handling
Integration Process: Vendor/VendorLocation Synchronization
Type of error
Action
Notification Type
Retry
Technical or Remote Fault
 
Example: UCM is not accessible
Process Stop
Email
Resubmit Error
Instance From OIC
Business Fault (WACS returns Status Not 400 or 500)
Process Stop
Email
Resubmit Error
Instance From OIC
Business Fault (WACS returns Status 400 or 500)
Continue Process
Collect errors and send errors in Email
Data Fix in Integration:
 
• Rename the file in UCM by removing the “ERROR” prefix in the name.
• Reprocess the Job file.
 
Data Fix in WACS:
• Rename the file in UCM by removing the “ERROR” prefix in the name.
• Reprocess the Job file.
Business Fault Invalid docTitle Name
Process Stop
Email
Retry passing the correct file name
Rename of File Failed
Process Stop
Email
Rename file manually in UCM or retry the OIC flow again for the same docTitle
File is not a zipped file
Process Stop
Email
Retry passing the correct docTitle name
 
Integration Process: Blanket Contract Synchronization
Type of error
Action
Notification Type
Retry
Technical or Remote Fault
 
Example: UCM is not accessible
Process Stop
Email
Resubmit Error
Instance From OIC
Business Fault (WACS returns Status Not 400 or 500)
Process Stop
Email
Resubmit Error
Instance From OIC
Business Fault (WACS returns Status 400 or 500)
Continue Process
Collect errors and send errors in Email
Data Fix in Integration:
 
• Rename the file in UCM by removing the “ERROR” prefix in the name.
• Reprocess the Job file.
 
Data Fix in WACS:
• Rename the file in UCM by removing the “ERROR” prefix in the name.
• Reprocess the Job file.
Business Fault Invalid docTitle Name
Process Stop
Email
Retry passing the correct file name
Rename of File Failed
Process Stop
Email
Rename file manually in UCM or retry the OIC flow again for the same docTitle
File is not a zipped file
Process Stop
Email
Regenerate the zip file in FPRC and run the OIC process to pick up the zip file
Business Fault DocTitle and ContentId parameters are null
Process Stop
Email
Retry passing a valid value for a parameter
Business Fault UOMConversion API returns ReturnStatus as "ERROR"
Collect Error
Email
Update the Blanket contract values in FPRC, re generate the file and run the OIC process again to process the regenerated file.
Technical Fault UOMConversion API throws fault
Collect Error
Email
Rename the file manually in UCM and rerun the OIC flow again to pick up the renamed file.
 
Integration Process: Purchase Requisition Synchronization
Type of error
Action
Notification Type
Retry
Technical Fault
Process Stop
Email
Resubmit Error Instance From OIC
Remote Fault or Business Fault (Invoke FPRC PR Create REST API)
Process Stop
Email
Resubmit From WACS
Remote Fault (Invoke OIC PR Approval REST API)
Process Stop
Email
Invoke OIC PR Approval REST API passing FPRC PR Header ID. The PR in FPRC has been created so only submit it for approval.
 
Integration Process: Purchase Requisition Approval Process
Type of error
Action
Notification Type
Retry
Technical Fault
Process Stop
Email
Resubmit Error Instance From OIC
Remote Fault or Business Fault (Invoke FPRC Submit PR for Approval REST API)
Process Stop
Email
Invoke OIC PR Approval REST API passing FPRC PR Header ID. The PR in FPRC has been created so only submit it for approval.
 
Integration Process: Purchase Order Synchronization
Type of error
Action
Notification Type
Retry
Technical Fault
Process Stop
Email
Resubmit Error Instance From OIC
Remote Fault or Business Fault (Invoke WACS REST API)
Process Stop
Email
Resubmit Error Instance From OIC
 
Integration Process: Receipt Synchronization
Type of error
Action
Notification Type
Retry
Technical or Remote Fault in CreateReceiptsiptsIn FPRC scope in OIC
Process Stop
Email
Resubmit Error Instance From OIC or resend outbound message from WACS
Technical or Remote Fault in FPRC_ProcessingErrors scope in OIC
Collect Error
Email
Query FPRC Interface tables for Receipts to check the error records
Technical or Remote Fault in Receipt_ProcessingError scope in OIC
Collect Error
Email
Query FRPC Interface tables for Receipts to check the error records
Technical or Remote Fault in FPRC_LinesTo
Return scope in OIC
Collect Error
Email
Manually Return the quantity from FPRC
Technical or Remote Fault in ReturnReceipts scope in OIC
Collect Error
Email
Manually Return the quantity from FPRC
Technical or Remote Fault in ReceivingReceipt
TrxmProcessing
Errors scope in OIC
Collect Error
Email
Query FPRC Interface tables for Returns to check the error records
Technical or Remote Fault in Rename_Close
POLine scope in OIC
Collect Error
Email
Manually close the PO line from FPRC
Business Error in Receipts API (Processing error in any receipt line indicated by ReturnStatus = "Error")
Continue Process Receipt is created with partial lines
Collect errors and send errors in Email
Fix the error lines in the Interface Tables for FPRC and upload the fixed receipt lines to the main Receipt.
Business Error in Receipts(Processing error in ALL the receipt lines indicated by ReturnStatus = "Error" and ProcessingStatus = "ERROR")
Return fault 400 status is sent back to WACS
Collect errors and send errors in Email
Resend the Receipt outbound message from WACS
Business Fault in Close PO Line API
Process Stop
Email
If the PO line is not closed in FPRC, close it manually in FPRC.
BusinessError in Returns API ("ReturnStatus'=ERROR' on Receipt LineToReturn)
Collect Error
Email
Fix the error lines in Interface tables for Returns in FPRC and upload the fixed Returns to the main Returns table.
 
Integration Process: Returns Synchronization
Type of error
Action
Notification Type
Retry
Technical or Remote Fault in InvokeLinesTo
Return scope in OIC
Process Stop
Email
Resubmit error instance from OIC or resend outbound message from WACS
Technical or Remote Fault in ProcessReturns scope in OIC
Process Stop
Email
Resubmit error instance from OIC or resend outbound message from WACS
Technical or Remote Fault in InvokeReturn scope in OIC
Collect Error
Email
Query FRPC interface tables for Receipts to check the error records
Technical or Remote Fault in ProcessErrors scope in OIC
Collect Error
Email
Manually return the quantity from FPRC
Business Error (Processing error on Returns API on any Receipt LinesToReturn indicated by ReturnStatus = "ERROR" in response)
Continue process of Return on other Receipt LinesTo
Return
Collect errors and send errors in Email
Fix the error lines in Interface Tables for Returns in FPRC and upload the fixed receipt lines to the main Returns table
Business Fault (Processing error on Returns API on ALL Receipt LinesToReturn indicated by ReturnStatus = "ERROR" in response)
Return fault 400 status is sent back to WACS
Collect errors and send errors in Email
Resend the Returns outbound message from WACS
 
Integration Process: Invoice Validated Synchronization
Type of error
Action
Notification Type
Retry
Technical Fault
Process Stop
Email
Resubmit Error Instance From OIC
Remote Fault or Business Fault (Any API Invocation)
Process Stop
Email
Resubmit Error Instance From OIC
 
Integration Process: Invoice Cancelled Synchronization
Type of error
Action
Notification Type
Retry
All Errors Encountered
Process Stop
Email
Resubmit Error Instance From OIC
 
Integration Process: Invoice Payment Synchronization
Type of error
Action
Notification Type
Retry
Technical Fault
Process Stop
Email
Resubmit Error Instance From OIC
Remote Fault or Business Fault (Any API Invocation)
Process Stop
Email
Resubmit Error Instance From OIC
 
Integration Process: Invoice Payment Voided Synchronization
Type of error
Action
Notification Type
Retry
Technical Fault
Process Stop
Email
Resubmit Error Instance From OIC
Remote Fault or Business Fault (Any API Invocation)
Process Stop
Email
Resubmit Error Instance From OIC
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.
Reprocess Vendor/Vendor Location File
To reprocess the Vendor/Vendor Location file:
1. Login to Oracle Integration Cloud.
2. Navigate to Integrations > Integrations.
• For Vendor Sync: Navigate to Oracle Utilities FPRC WACS Vendor Location Sync integration and click Run.
3. Click Submit Now to display the Schedule Parameters.
4. Enter the DocTitle of the file.
Note: Enter the complete DocTitle of the file to process single file or enter the DocTitle with wildcard (such as file*) to process multiple files.
5. Click Submit.
Reprocess Blanket Contract File
To reprocess the Blanket Contract file:
1. Login to Oracle Integration Cloud.
2. Navigate to Integrations > Integrations.
3. Navigate to Oracle Utilities FPRC WACS Blanket Contract Sync integration and click Run.
4. Click Submit Now to display the Schedule Parameters.
5. Enter the DocTitle or ContentId of the file.
Note: Enter the complete DocTitle of the file to process single file or enter the DocTitle with wildcard (such as file*) to process multiple files.
6. Click Submit.