Oracle ERP Cloud SOAP-Based Callback Failures in the Oracle ERP Cloud Adapter Trigger Connection
If you configured a callback for FBDI-compliant import jobs, after the job completes processing, the Oracle ERP Cloud application should invoke the Oracle Integration endpoint that has the Oracle ERP Cloud Adapter trigger. This is the callback that Oracle Integration receives from the Oracle ERP Cloud application. However, the callback fails.
Error while processing authentication at Trigger. Failed due to - 401 : Unauthorized"
Verify the following steps.
-
Verify the callback integration details in the integration where the import job is invoked. See the invoke Response page of the Adapter Endpoint Configuration Wizard.
If the invoke Response page in your integration includes the Integration Flow Identifier and Integration Flow Version fields below the Enable Callback check box, this indicates that you are using an older version of the Oracle ERP Cloud Adapter that uses a SOAP-based callback architecture. The Oracle ERP Cloud Adapter should now use the business event-based callback architecture.
Solution: To use the business event-based callback architecture and successfully receive the callback integration:- Delete the old Oracle ERP Cloud Adapter from the integration canvas.
- Configure a new version of the Oracle ERP Cloud Adapter and ensure that you select the Enable Callback check box on the invoke Response page. This action ensures that the business event-based callback architecture is used. See Invoke Response Page.
- Reconfigure your mappings in the mapper and reactivate the integration.
- Create a new Oracle ERP Cloud Adapter trigger-based integration to receive the callback and select Receive Callback Message upon completion of FBDI bulk Import Job submitted via another Integration on the trigger Request page and the bulk data import process to receive as a request that starts the integration. This is the callback that Oracle Integration receives from the Oracle ERP Cloud application. See Trigger Request Page.
- Activate the callback integration, which creates the subscription using the business event-based architecture.
- If there are authentication errors when sending the callback, you
see a
Failed at Trigger
message or do not see any events arriving. Ensure that you resolve any authentication issues. - Use REST APIs to diagnosis why you did not receive the callback integration. See this Oracle Support note.