A common Oracle ERP Cloud integration pattern is to upload a file to UCM, submit an ESS job, and then poll the ESS job status until it completes successfully. This pattern is widely used for payment processing, FBDI imports, bank acknowledgements, and other batch integrations.
Business Requirement
Suppose an external system generates a file (CSV/XML/TXT) that needs to be processed by Oracle ERP Cloud.
The integration should:
- Upload the file into Oracle ERP Cloud UCM.
- Submit the required ESS job.
- Wait for the job to finish.
- Check the ESS job status.
- Continue processing only when the job completes successfully.
Integration Flow
External System
│
▼
Receive File
│
▼
Upload File to UCM
│
▼
Receive Content ID
│
▼
Submit ESS Job
│
▼
Receive Request ID
│
▼
Loop Until Completion
│
▼
Get ESS Job Status
│
▼
Success / Error Handling
Step 1 – Upload File to UCM
Configure the Oracle ERP Cloud Adapter and select:
Operation: File Upload to WebCenter (UCM)
Example values:
Account: FAFusionImportExport
UCM Folder: fin$/payments$/import$
After upload, Oracle returns a Content ID, which is required by many ESS jobs.
Step 2 – Submit ESS Job
Invoke another ERP Cloud Adapter.
Choose: Submit ESS Job
Provide:
Job Package Name
Job Definition Name
Parameters
Example ESS Job Path:
/oracle/apps/ess/financials/payments/fundsDisbursement/payments/FDAckProcessing
The adapter returns an ESS Request ID.
Example:
Request ID : 300000458912345
Step 3 – Wait Before Polling
Instead of checking immediately, add a Wait activity.
Example:
Wait 20–30 seconds
This avoids unnecessary API calls while Oracle begins processing the job.
Step 4 – Check ESS Job Status
Use a While scope.
Pseudo logic: While Status != SUCCEEDED
Wait 20 Seconds
Get ESS Job Status : Pass the Request ID returned during job submission.
End While
If the status becomes:
SUCCEEDED → Continue integration.
ERROR → Raise fault.
WARNING → Handle based on business requirement.
Typical statuses include:
Status Meaning
WAIT Waiting to start
READY Ready for execution
RUNNING Currently executing
SUCCEEDED Completed successfully
ERROR Failed
WARNING Completed with warnings
When to use Upload File to UCM:
You are uploading a payment file or bank file.
You need to run a specific ESS job yourself after the upload.
The file is not a standard Oracle FBDI import.
You need full control over the sequence (Upload → ESS Job → Poll Status).
Example:
Upload payment acknowledgment file.
Upload HSBC bank file.
Upload custom XML/CSV.
Upload a file and then run FDAckProcessing ESS job.
When to use Bulk Import:
You are importing Oracle ERP business data using FBDI.
Oracle ERP supports that object through the Bulk Import operation.
You want Oracle to manage the import process for that business object.
Examples:
Supplier Import
Customer Import
GL Journal Import
AP Invoice Import
Asset Import
Item Import
Conclusion
Uploading a file to UCM, submitting an ESS job, and continuously monitoring the job status is one of the most common Oracle Integration Cloud design patterns. By combining the ERP Cloud Adapter, Wait, and While activities, you can build a robust integration that ensures downstream processing starts only after the ERP job has successfully completed.
No comments:
Post a Comment