See what the Oracle ERP integration can do →
This guide walks through subscribing to the Oracle ERP integration in iPaaS.com and configuring it for first-time use. Work through the sections in order: gather your credentials, subscribe to the integration from the marketplace, complete the required and operational configuration, then verify the installation before relying on it in production.
In this article:
Before You Begin
Installation Instructions for Integration Setup
Required Configuration Fields
Operational Configuration
Additional Configuration Options
Post-Installation Verification
Support and Troubleshooting
Before You Begin
The Oracle ERP integration connects iPaaS.com to your Oracle ERP instance. Before you install the subscription, obtain the following from the client or the team that administers the Oracle ERP environment:
API endpoint URL: the address of the Oracle ERP API your subscription will connect to. This is provided by the client and differs between test and production environments.
Username: the account used to authenticate to the Oracle ERP API.
Password: the password for that account.
The integration authenticates to Oracle ERP using Basic authentication (username and password), so all three values must be available before you begin. If you do not have them, request them from the client before starting the subscription setup.
NOTE: This is a custom integration built against a specific client's Oracle ERP configuration. Confirm with the client which environment (test or production) you are configuring, and use the endpoint, username, and password that match that environment.
Installation Instructions for Integration Setup
In the left navigation, expand Subscriptions Management and click Subscriptions, then click Search Certified Integration Marketplace and Subscribe.
Click the Oracle ERP integration tile.
On the Subscription Detail page, click the Subscribe button.
The Subscription Settings page opens. Complete the Required Configuration Fields, Operational Configuration, and Additional Configuration Options described in the sections below.
When all fields are set, click Apply to save the subscription.
Required Configuration Fields
These fields must be completed for the subscription to connect to Oracle ERP.
Name: a descriptive, unique subscription name within the company where the subscription is created.
Format: [Product Name] - [Environment/Purpose]
Example: Oracle ERP - Release
Create Default Mappings: leave checked (recommended). Checking this box auto-creates the standard field mappings for the integration. Uncheck it only if you intend to build all mappings from scratch yourself.
Version: select the appropriate integration version from the dropdown. The latest version is recommended, as it includes all available features.
Environment URL: your Oracle ERP API endpoint, provided by the client. Use the test endpoint when configuring a test or sandbox subscription and the production endpoint for a production subscription. Both are supplied by the client for the environment you are setting up.
Username: the Oracle ERP API account username.
Password: the password for that account.
Operational Configuration
These fields control how the integration matches customer addresses, how far back it looks for records on its first poll, and how it aligns date and time values with Oracle ERP. The integration retrieves data from Oracle ERP on a scheduled polling cycle; the poll-day fields apply to the historical lookback performed on the initial run.
Customer Address Fields to Match: a comma-separated list of address field names the integration uses to identify duplicate customer addresses. Two addresses are treated as the same only when all of the listed fields match. For example, address_1, postal_code, city compares those three fields. This value is recommended for accurate address de-duplication; if your source data can produce sparse addresses, validate the matching behavior in a staging environment before relying on it in production.
Product Search Poll Days: the number of days of historical product data to retrieve on the initial poll. For example, entering 100 retrieves product records from the past 100 days. If left blank, the integration defaults to 4 days.
Product Inventory Search Poll Days: the number of days of historical product inventory data to retrieve on the initial poll.
Company Search Poll Days: the number of days of historical company data to retrieve on the initial poll.
Transaction Search Poll Days: the number of days of historical transaction (order) data to retrieve on the initial poll.
Transaction Tracking Search Poll Days: the number of days of historical shipment tracking data to retrieve on the initial poll. If left blank, the integration defaults to 4 days.
Time Zone Offset: the number of hours to shift from UTC to match the Oracle ERP instance's local time zone. This keeps date and time values aligned when exchanging data between the two systems.
NOTE: The poll-day fields govern only the historical lookback on the first poll. After the initial run, the integration tracks the last poll time for each entity and retrieves only records changed since the previous poll.
Additional Configuration Options
These settings appear at the bottom of the Subscription Settings page. They are standard iPaaS.com subscription controls that govern the frequency and volume of data movement. Adjust them if you encounter rate-limit errors from Oracle ERP.
API Throttle Limit: controls the number of API requests the subscription can make within each throttle window, protecting Oracle ERP performance and ensuring fair usage.
Recommended values: Initial Setup 5; Ongoing Operations 500; High Volume 500.
API Throttle Seconds: the length, in seconds, of the throttle window over which the API Throttle Limit is measured. Requests beyond the limit are held until the window resets.
Default: 60 seconds.
Concurrent Connections: the maximum number of simultaneous API connections the subscription can use for the integration. Requests beyond this limit are queued until an active connection finishes.
Concurrent Batch Executions: a standard iPaaS.com platform setting for the number of batch operations that can run simultaneously. This integration does not act on it in any integration-specific way; leave it at the platform default unless directed otherwise.
Post-Installation Verification
After clicking Apply, verify the installation before relying on it in production.
Data Sync Test
Initiate a sample data pull from Oracle ERP into iPaaS.com — for example, run a Manual Sync on the Company, Product, or Order collection and confirm records are retrieved.
Initiate a sample data push from iPaaS.com to Oracle ERP — for example, create or update a test order and confirm it is written to Oracle ERP.
Functionality Test
Run an end-to-end business process that covers the entities you plan to sync.
Validate key features such as field mappings and logging.
Review the integration logs in iPaaS.com under Integration Monitoring to confirm the transfers completed without errors.
Support and Troubleshooting
Click the Help button on any iPaaS.com page to contact iPaaS.com Support or to search the documentation.
Documentation: iPaaS.com API Introduction
Support Portal: support.ipaas.com
Contact Information: Contact iPaaS.com