Integrating With Oracle Fusion ERP
Oracle ERP Cloud (Fusion) provides a comprehensive set of REST APIs for programmatic access to financials, procurement, project management, and other modules. Unlike EBS where you call PL/SQL APIs directly against the database, ERP Cloud integrations are exclusively through REST endpoints over HTTPS, making them accessible from any platform.
API Endpoint Structure
ERP Cloud REST APIs follow a consistent pattern:
https://{server}/fscmRestApi/resources/{version}/{resource}
-- Examples:
GET /fscmRestApi/resources/11.13.18.05/invoices
GET /fscmRestApi/resources/11.13.18.05/invoices/{InvoiceId}
POST /fscmRestApi/resources/11.13.18.05/invoices
GET /fscmRestApi/resources/11.13.18.05/ledgers
GET /fscmRestApi/resources/11.13.18.05/journalsHeaders
Authentication
ERP Cloud APIs support Basic Authentication and OAuth2 token-based authentication. For production integrations, use OAuth2 with JWT assertions for service-to-service communication:
-- From PL/SQL using APEX_WEB_SERVICE
DECLARE
l_response CLOB;
BEGIN
APEX_WEB_SERVICE.G_REQUEST_HEADERS(1).name := 'Content-Type';
APEX_WEB_SERVICE.G_REQUEST_HEADERS(1).value := 'application/json';
l_response := APEX_WEB_SERVICE.MAKE_REST_REQUEST(
p_url => 'https://erp.example.com/fscmRestApi/resources/11.13.18.05/invoices',
p_http_method => 'GET',
p_username => 'integration_user',
p_password => 'integration_pass'
);
APEX_JSON.PARSE(l_response);
-- Process invoice data
END;
Common Integration Patterns
The most common ERP Cloud integrations include importing invoices from external systems using the Invoices REST API, synchronizing suppliers and customers between ERP Cloud and on-premise systems, extracting financial reports and GL balances for custom dashboards, and creating journal entries from external calculations or allocations.
FBDI (File-Based Data Import)
For bulk data loads, ERP Cloud uses File-Based Data Import (FBDI). You prepare a CSV file following Oracle’s published templates, upload it to UCM (Universal Content Management), and then trigger an ESS (Enterprise Scheduler Service) job to process it. This is more efficient than row-by-row REST calls for large volumes:
Prepare the CSV following the FBDI template. Upload to UCM using the UCM REST API. Submit the import ESS job using the ERP Integration REST API. Poll the job status until completion.
Error Handling
ERP Cloud REST APIs return standard HTTP status codes. A 201 means successful creation, 400 means validation errors with details in the response body, and 401 or 403 indicate authentication or authorization issues. Always parse the response body for error details, as ERP Cloud provides specific validation messages that are essential for troubleshooting.