Oracle Integration Cloud: ERP Cloud Adapter import bulk data, callback never arrives
OIC ERP Cloud Adapter importBulkData callback not received integration stuck waiting
Also searched as
- Oracle Integration Cloud Fusion import bulk data callback
- OIC ERP adapter submit ESS job callback not triggered
- Fusion ErpIntegrationService uploadFileToUCM importBulkData error
- OIC integration fails ERP Cloud Adapter UCM upload
Short answer
In an OIC flow that loads FBDI data, the ERP Cloud Adapter uploads the file to UCM, submits the ESS import job and waits for a callback when the job ends. If the callback never arrives, trace each hop separately: the upload, the ESS job in Scheduled Processes, then the callback registration and the security of the integration user.
Applies to: Oracle Integration (OIC Gen 3) with the Oracle ERP Cloud Adapter against Fusion Cloud ERP and SCM
Trace the flow hop by hop
- 1In OIC Observability, open the failed or waiting instance and note the last completed action and any fault message.
- 2In Fusion, open Tools > Scheduled Processes and search for the import job by time and submitter; confirm whether the ESS job was submitted at all.
- 3If no job exists, check the UCM upload: the file name, the document account and whether the upload action returned a document ID.
- 4If the job ran, check its final status and log. A job that errored or finished with warnings still fires a callback in most designs, but a job stuck in Blocked or Wait will not.
- 5Verify the integration user has the roles for the import job and for the integration service, such as the Integration Specialist and the application's data import roles.
- 6Check the callback configuration on the adapter action and that OIC is reachable by the Fusion pod, including any allow list or private endpoint setup.
- 7Check for event delivery by testing the ESS job status through the get ESS job status operation, and add a scheduled fallback poll.
- 8After the fix, resubmit with a new file name or batch identifier so the earlier upload does not collide.
Anatomy of the flow
The ERP Cloud Adapter wraps Fusion's ERP integration service. A typical FBDI load is three calls: upload the zipped data file to Universal Content Management, submit the Load Interface File for Import job (or a product-specific import job) through the ESS submission operation, then wait for completion. The adapter can raise a callback to OIC when the ESS job reaches a terminal state, which lets the integration continue without polling.
Each hop has its own failure mode. A failed upload leaves no job. A failed submission leaves a file with no process. A job that never leaves a non-terminal status never calls back. A job that completes, but whose callback cannot reach OIC, looks identical from OIC's side: the instance waits and eventually times out.
Why the callback goes missing
The job did not finish. An ESS request in Blocked, Wait, or stuck behind an incompatible job does not complete, so no callback is raised. Look at the incompatibility and the job queue before suspecting the integration.
Callback registration and reachability. The adapter relies on the callback destination being valid and reachable from the Fusion side. Network restrictions, a changed OIC instance URL after a cloning or refresh, or an expired connection configuration can break delivery without any error visible in the integration.
Security. The user behind the connection must be allowed to submit the job and to be the owner of its callback. A password change on the service account, or an account lock, causes the call to fail after a period of working fine.
Job parameters. If the import is submitted with parameters that cause an immediate failure, such as a wrong interface identifier or a source file that cannot be found, the job ends in error. Make the integration handle error status as a normal path, not only success.
Designing for resilience
Do not depend on a single callback. Add a scheduled integration that polls the status of ESS requests submitted but not marked completed, and use it to close out stale instances. Persist the request ID returned at submission in a tracking store or the instance tracking field so that any later process can find it.
Treat the load and the import as separate transactions. After the ESS job succeeds, confirm results from the interface and error tables, because a job can complete with rejected rows. Pull the error output for the request and route rejections to someone who can fix the data.
Make the integration idempotent. Use unique file names or batch identifiers and check for existing documents before upload, so that a retry does not load the same data twice.
# Outline of the ERP integration service calls (verify payload names in your release) 1. uploadFileToUCM -> returns document ID 2. submitESSJobRequest -> returns ESS request ID 3. callback / getESSJobStatus(requestId) 4. downloadESSJobExecutionDetails(requestId) -> logs and output
Checking from Fusion
In Scheduled Processes, filter by the integration user and the time window. The process details show parameters, status, the log and the output file, and the parent-child hierarchy for import jobs that spawn a validation or loader child. Compare the ESS request ID in Fusion with the one stored by OIC to be sure you are looking at the same run.
If you can, test the same sequence manually using the file import path in Fusion. If the manual load works while the integration fails, the problem is in the connection, roles or callback rather than in the data.
Common pitfalls
- !Relying solely on the callback with no fallback poll, so a missed event leaves instances waiting for days.
- !Treating ESS job warnings and errors as unexpected exceptions rather than normal outcomes to route.
- !Re-running a failed integration with the same file name and loading duplicate data.
- !Letting a service account password expire or lock without monitoring.
- !Not recording the ESS request ID at submission, which makes later tracing guesswork.
How an ERP-grounded AI assistant handles this
A grounded assistant can help here by correlating records: it can read the ESS request history and the interface error tables in Fusion and tell the integration owner which submitted loads never reached a terminal status and which completed with rejected rows. It stays read-only by default and shows its query. Any resubmission or repair is performed by the team with the normal approval step.
Frequently asked questions
Why does my OIC integration wait forever after submitting the ESS job?
Either the ESS job has not reached a terminal state, or the callback could not be delivered. Check Scheduled Processes first for Blocked or Wait status, then verify the callback configuration and the integration user's access. Add a polling fallback in all cases.
Does a failed ESS import still trigger a callback?
Generally, a job reaching an error or warning end state is still a terminal state, so a callback should be raised. Design the flow to read the final status and handle failure paths, rather than assuming only successful completions call back.
Which roles does the integration user need?
It needs the roles to use the integration service, upload to UCM, and submit and view the specific import job, plus data access for the business unit or ledger. Exact role names depend on the product, so compare against a working manual import by a named user.
How do I avoid loading the same file twice on retry?
Use a unique file name or batch identifier per run, record the ESS request ID at submission, and check for an existing request before resubmitting. Reconcile the interface table contents when a retry is unavoidable.
Related
Connect Oracle Integration Cloud (OIC) To Fusion ERP
OIC connects to Fusion ERP primarily through the prebuilt ERP Cloud Adapter, which wraps Fusion's REST and SOAP web services with OAuth-based authentication and pick-list discovery of available business objects and operations, instead of you hand-building every REST call. Use the adapter for standard integrations; drop to a generic REST or SOAP adapter only when the ERP Cloud Adapter does not yet expose the specific service you need.
Error fixFix FBDI Import Failures From Interface Table Validation Errors
When a Fusion FBDI import job errors out, the cause is almost always bad data in the interface tables (an invalid value set, a wrong date format, or a missing required column), not the ESS job itself. Open the process's Interface Errors Report or the Correct Import Errors spreadsheet to see the exact rejected rows and reason codes, fix the source data, and resubmit from the interface tables instead of re-running the whole FBDI load.
Error fixClear An Oracle Fusion ESS Job Stuck In Blocked Status
A Blocked status on an Oracle Fusion Enterprise Scheduler (ESS) job almost always means an earlier instance of the exact same job is still running or stuck, and the job definition does not allow simultaneous requests. Find and finish, or cancel, the earlier request first; only then does the Blocked request move to Running.
How-toPaginate And Authenticate Oracle Fusion REST API Calls Correctly
Oracle Fusion Cloud REST APIs authenticate with HTTP Basic Authentication, an integration user's credentials, over HTTPS by default, and paginate with limit and offset query parameters rather than a page number. Loop on the hasMore flag in the response until it returns false to retrieve a full result set.
How-toOTBI vs BI Publisher: Which One Should You Use
Use OTBI when a business user needs ad hoc, self-service, real-time analysis with no fixed layout. Use BI Publisher when you need a pixel-perfect, scheduled, high-volume, or externally distributed document such as an invoice, check, or statutory report. Most Fusion implementations end up using both, not one instead of the other.
Error fixFix The Oracle Fusion "You Don't Have Access To This Data" Error
This generic Oracle Fusion security message means the function privilege and the data security scope did not both line up for that user on that record - most often the job role is assigned but the matching data role, security profile, or business unit and ledger context in Manage Data Access for Users is missing. Fix it by checking data access setup for the user's role, not by re-granting the same job role again.
AI for ERPFusion Cloud ERP AI: OCI Generative AI Service vs. a Private LLM
Oracle's OCI Generative AI Service is a real option for Fusion Cloud ERP, but not the only one. Compare it honestly against a private LLM for sensitive data.
Stuck on Oracle Fusion Cloud ERP?
Talk to engineers who work inside Oracle Fusion Cloud ERP every week, and who build private AI that answers these questions from your own ERP data.