Skip to main content

Oracle ERP Connections and Settings

How to connect iPaaS.com to Oracle ERP, including the required credentials, subscription settings, Basic authentication, and throttling.

Integrate iPaaS.com with Oracle ERP to enable data synchronization for products, product inventory, customer companies, sales orders, and order tracking.

This integration was built for a specific client's Oracle ERP configuration. The connection details below are provided by that client's Oracle ERP administrator, and subscribers or their MiSP should confirm each value with the administrator before configuring the subscription.

On this page:

  • How to Connect

  • Configure Subscription Settings

  • Authentication Methods

  • Initialization Support

  • Throttling

  • Related Documents

How to Connect

Prerequisites

Before you connect, obtain the following from the Oracle ERP administrator who manages your Oracle ERP instance. iPaaS.com does not provision these values; they are issued and controlled by the Oracle ERP side.

  • A reachable REST endpoint for the Oracle ERP instance (base URL).

  • A service account that is authorized to read the customer, product, inventory, order, and shipment data being synchronized, and to submit sales orders.

  • The username and password for that service account.

Configuration Details

Enter the following credentials on the iPaaS.com Subscription Settings page when you configure the subscription:

  • API URL: The base URL of the Oracle ERP REST endpoint, provided by your Oracle ERP administrator. This value is also shown as Environment URL on the subscription form. Example: https://your-oracle-erp.example.com:443

  • Username: The username of the Oracle ERP service account used to authenticate every request. Example: ipaas_service_account

  • Password: The password for that service account. It is stored securely and is not displayed after it is saved.

Configure Subscription Settings

The following subscription settings are configured on the iPaaS.com Subscription Settings page during installation and remain available for ongoing reference and updates. The Required column indicates whether a value must be supplied for the connection to function.

Field

Description

Required

Example

API URL

The base URL of the Oracle ERP REST endpoint (shown as Environment URL on the subscription form). All requests are sent to this host.

Yes

Username

The Oracle ERP service account username used for authentication.

Yes

ipaas_service_account

Password

The password for the Oracle ERP service account.

Yes

Your service account password

Customer Address Fields to Match

A comma-separated list of address fields the integration compares to decide whether an incoming Oracle ERP customer address already exists in iPaaS.com, which prevents duplicate address records. All listed fields must match for two addresses to be treated as the same.

Recommended

address_1,postal_code,city

Product Search Poll Days

How far back, in days, the first poll reaches when the integration begins retrieving product records. Subsequent polls retrieve only records created or updated since the last successful poll. Defaults to 4 days if left blank.

No

100

Product Inventory Search Poll Days

How far back, in days, the first poll reaches when the integration begins retrieving product inventory records. Subsequent polls retrieve only records changed since the last successful poll.

No

30

Company Search Poll Days

How far back, in days, the first poll reaches when the integration begins retrieving customer company records. Subsequent polls retrieve only records changed since the last successful poll.

No

30

Transaction Search Poll Days

How far back, in days, the first poll reaches when the integration begins retrieving sales order records. Subsequent polls retrieve only records changed since the last successful poll.

No

30

Transaction Tracking Search Poll Days

How far back, in days, the first poll reaches when the integration begins retrieving order tracking (shipment) records. Subsequent polls retrieve only records changed since the last successful poll. Defaults to 4 days if left blank.

No

100

Time Zone Offset

The number of hours to shift from UTC so that date and time filtering aligns with the local time zone of the Oracle ERP instance. Applied when each scheduled poll calculates its since-modified window.

No

-5

API Throttle Limit

Standard platform setting. The maximum number of API requests allowed within each throttle window.

No

500

API Throttle Seconds

Standard platform setting. The length, in seconds, of each throttle window used to count requests against the limit.

No

60

Concurrent Connections

Standard platform setting. The maximum number of API requests processed at the same time.

No

5

Concurrent Batch Executions

Standard platform setting, pre-populated by iPaaS.com. This integration does not specifically act on this value.

No

Platform default

NOTE: The Customer Address Fields to Match value affects how customer addresses are matched and de-duplicated. Subscribers or their MiSP should validate the chosen field set in a staging environment before relying on it in production, so that legitimately distinct addresses are not merged and true duplicates are correctly matched.

Authentication Methods

The integration authenticates to Oracle ERP using HTTP Basic authentication. The Username and Password entered in Subscription Settings are sent with every request to the API URL. There is no separate application registration, client secret, or OAuth authorization step, and no confidential host to configure.

Credentials are supplied by the Oracle ERP administrator and entered once during installation. If the service account password changes on the Oracle ERP side, update the Password setting on the Subscription Settings page and click Apply; no re-authorization flow is required.

Initialization Support

Initialization (a one-time bulk import of all existing records on first connect) is not supported for Oracle ERP in iPaaS.com. Ongoing synchronization is handled by scheduled polling and on-demand Manual Sync.

To load a large volume of historical records during setup, subscribers or their MiSP can perform a bulk sync using Postman. The Search Poll Days settings above also let you widen the first poll's lookback window to capture records created before the subscription was configured.

Throttling

The throttle and concurrency settings control the rate and volume of API traffic between iPaaS.com and Oracle ERP. They are pre-populated with recommended defaults during installation and can be adjusted on the Subscription Settings page:

  • API Throttle Limit and API Throttle Seconds together define how many requests are allowed within each time window.

  • Concurrent Connections limits how many requests run at the same time.

  • Concurrent Batch Executions is a standard platform preset that this integration does not specifically act on.

If Oracle ERP begins returning rate limit errors, subscribers or their MiSP should reduce these values. For more detail on adjusting these fields, see Subscription Configuration - Edit.

Related Documents

Did this answer your question?