Week 7 of 8
Integrations and Oracle Integration
Banks, tax engines, payroll providers, warehouses and data platforms all connect to Fusion, often through Oracle Integration (OIC). A common pattern: OIC sends a zip to Fusion through the ERP Cloud adapter, and a separate callback integration reacts when the import finishes. Oracle raises that callback whether the job succeeded or failed.
A real example of why integrations belong in every quarterly regression: after instances moved to 25C, integrations still using the older SOAP-based callback got “401 : Unauthorized” at the callback trigger until they were rebuilt on the event-based design.
This week: inventory every integration and test both outcomes
- List each integration: pattern (FBDI bulk import, REST, SOAP, BI Publisher extract, file transfer), direction, owner, partner contact and the Fusion objects it touches.
- For FBDI-based integrations, test the callback for a successful import and for a failed one. The failure path is where errors go unnoticed.
- Record the endpoint per environment, and re-check it after every P2T refresh (endpoints are not copied).
- Mark which integrations run in every quarterly regression. If it moves money or posts to the ledger, it is in.
Number of the week
25C
the update after which SOAP-based ERP Cloud adapter callbacks failed with a 401 error until rebuilt on the event-based callback.
Source: Oracle Integration documentation: SOAP-Based Callback FailuresUse this week
- Oracle OIC Integration & P2T Refresh Tracker →
Integration inventory with success and failure callback results per cycle, and endpoint checks per environment.
- SIT Cycle Plan & Entry/Exit Criteria →
End-to-end scenarios that cross integrations, with a burn-down.
Next week, the last of the playbook: running the quarterly update as a repeatable two-week regression, and what to automate.
Get the playbook in your inbox, one week at a time
Subscribe free and every template in the library is yours.