The Oracle ERP integration is a REST integration. It communicates with a single, configurable Oracle ERP endpoint — referred to throughout this article as [Base URL] — using standard HTTP requests.

The [Base URL] value is the API endpoint for your Oracle ERP instance. It is configured in the iPaaS.com Subscription Settings (the API URL setting) and is provided to you by the client that owns the Oracle ERP environment. Because this integration is built for a specific client's Oracle ERP configuration, there is no shared or default host — the endpoint is supplied during installation.

Most entities are read into iPaaS.com from Oracle ERP (TO iPaaS.com). Only the Order entity is written back to Oracle ERP (FROM iPaaS.com). Each entity is polled on a schedule using a retrieve-since-modified operation, so that only records created or changed since the last successful poll are transferred.

Table of Contents

Company records represent the customer accounts held in Oracle ERP. This data flows one way, from Oracle ERP into iPaaS.com.

Retrieve Companies Since Modified Date/Time (Retrieve)

Retrieves company records that were created or changed in Oracle ERP since the last successful poll. Used during TO iPaaS.com transfers to keep iPaaS.com company records in step with Oracle ERP. The date/time watermark and the historical look-back window are controlled by the Company Search Poll Days and Time Zone Offset subscription settings.

Product records represent the item catalog held in Oracle ERP. This data flows one way, from Oracle ERP into iPaaS.com.

Retrieve Products Since Modified Date/Time (Retrieve)

Retrieves product records that were created or changed in Oracle ERP since the last successful poll. Used during TO iPaaS.com transfers. The historical look-back window on the first poll is controlled by the Product Search Poll Days subscription setting (with a built-in default when left blank).

Product Inventory records represent on-hand quantities for items, by warehouse or location. This data flows one way, from Oracle ERP into iPaaS.com.

Retrieve Product Inventory Since Modified Date/Time (Retrieve)

Retrieves inventory records that were created or changed in Oracle ERP since the last successful poll. Used during TO iPaaS.com transfers to keep iPaaS.com inventory levels aligned with Oracle ERP. The historical look-back window on the first poll is controlled by the Product Inventory Search Poll Days subscription setting.

Order records represent sales orders. Orders are the only entity that moves in both directions: they are read from Oracle ERP into iPaaS.com, and they are also created and updated in Oracle ERP from iPaaS.com.

Retrieve Orders Since Modified Date/Time (Retrieve)

Retrieves order records that were created or changed in Oracle ERP since the last successful poll. Used during TO iPaaS.com transfers. The historical look-back window on the first poll is controlled by the Transaction Search Poll Days subscription setting.

Create an Order (Create)

Creates a new sales order in Oracle ERP. Used during FROM iPaaS.com transfers when a new order is sent to Oracle ERP. Each order line is included only when it carries both an item reference and an ordered quantity.

Update an Order (Update)

Updates an existing sales order in Oracle ERP. Used during FROM iPaaS.com transfers when changes to an existing order are sent to Oracle ERP. This is a partial update: only the fields that are mapped and supplied are changed, and any field that is not mapped keeps its existing value in Oracle ERP. The order must already exist in Oracle ERP before an update can be applied.

Order Tracking records represent shipment and tracking detail associated with orders. This data flows one way, from Oracle ERP into iPaaS.com.

Retrieve Order Tracking Since Modified Date/Time (Retrieve)

Retrieves tracking records that were created or changed in Oracle ERP since the last successful poll. Used during TO iPaaS.com transfers. The historical look-back window on the first poll is controlled by the Transaction Tracking Search Poll Days subscription setting.

The integration authenticates to Oracle ERP using HTTP Basic authentication. The Username and Password you enter in the iPaaS.com Subscription Settings are sent with each request to [Base URL]. There is no separate token or OAuth authorization step — the same credentials are presented on every call.

For details on where these credentials come from and how to enter them, see the Connections and Settings and Installation Instructions articles linked below.

When a read operation can return a large number of records, the integration retrieves the results in successive pages rather than in a single response. It walks through the full result set using an offset value and a page-size value, requesting one page at a time until all matching records have been retrieved.

This paging happens automatically as part of each scheduled poll. Subscribers or their MiSP do not set these paging values directly; they are handled by the integration during the transfer.

Oracle ERP does not publish fixed request-rate limits for this integration, so request pacing and concurrency are managed on the iPaaS.com side through standard subscription settings:

These settings let subscribers or their MiSP tune throughput to what the client's Oracle ERP environment can comfortably handle. Recommended starting values and further guidance are covered in the Installation Instructions and Connections and Settings articles.