Contents
Summary
ID Format
Deleted Record Support
Custom Field Support
Mapping Collection Status
Duplicate or Conflicting Mappings
Supported Child Collections
System Caveats
Setup Requirements
Integration Flow
Mappings
Error Handling
Testing & Validation
Additional Notes
Related Documents
Summary
This documentation covers how Oracle ERP customer company records are captured into iPaaS.com as Customer Company records. The integration reads companies from Oracle ERP and creates or updates the matching Customer Company in iPaaS.com, mapping the company name and account number so each Oracle ERP company is represented once in iPaaS.com and matched reliably on future transfers. Each company's addresses are transferred alongside it through the associated Add/Update Oracle ERP Company Address TO iPaaS.com child collection. Transfers run in one direction only — Oracle ERP to iPaaS.com — and are driven by scheduled polling or on-demand Manual Sync.
ID Format
Manual Sync ID Format
Enter the Oracle ERP company's account identifier — a numeric value, for example 12345 — on the iPaaS.com Manual Sync page to transfer a specific company together with its address child records. The child address collection has no independent Manual Sync entry point; to re-transfer a company's addresses on demand, run a Manual Sync of the parent company and its addresses transfer with it.
External ID Format (saved after sync)
On the first successful transfer, iPaaS.com saves the Oracle ERP company account identifier as the external ID on a dedicated, platform-managed external-ID record. That external-ID record is the primary match used to route subsequent updates to the same iPaaS.com Customer Company rather than creating a duplicate.
Until that external-ID link exists — typically on the very first transfer — the company name is the practical match: the integration looks for an existing iPaaS.com Customer Company whose name matches and links to it rather than creating a duplicate, then records the external-ID link for future transfers. The account number carried on the company record (see the AccountNumber mapping) is a stored business identifier for visibility and reporting; it is not the record's required primary identifier and is not the value used to prevent duplicates.
Each address transferred through the child collection is saved with its own external-ID link so subsequent transfers update the same address rather than creating a duplicate. An address external ID is formed from the Oracle ERP address site identifier and the company account identifier joined by a pipe character — the address site identifier, then a pipe character, then the company account identifier (for example, 45678|12345). Each address is also linked back to its parent company.
Deleted Record Support
Not supported. This integration captures companies and addresses from Oracle ERP into iPaaS.com in one direction only, and it does not process deletions for these records. Removing a company or an address in Oracle ERP does not delete the corresponding record in iPaaS.com, and the integration does not delete companies or addresses in either system.
Custom Field Support
None. These mapping collections do not configure, require, or transfer custom fields.
Mapping Collection Status
Status: Enabled. Neither the Company collection nor its Company Address child collection has a mapping filter applied, so all companies retrieved from Oracle ERP — and all of their addresses — are processed.
Trigger Events: Scheduled polling and Manual Sync. Through scheduled polling, the integration periodically checks Oracle ERP for companies created or updated since the last successful poll and transfers them, together with their addresses, to iPaaS.com. How far back the initial poll reaches is governed by the Company Search Poll Days subscription setting. Manual Sync is available on demand for the parent company. These collections are poll-driven; they do not use webhooks, and no Inbound Data Flows or webhook configuration is required or available for them.
Duplicate or Conflicting Mappings
This integration captures companies and their addresses in one direction only (Oracle ERP to iPaaS.com). There is no collection that writes companies or addresses back to Oracle ERP, so there is no opposing-direction collection to reconcile against and no circular-update risk for these records.
The integration does not implement selectable collision-handling methods for these collections. Instead, duplicate prevention is handled by matching and external-ID linking:
Company: When a company is transferred, the integration first looks for an existing iPaaS.com Customer Company whose name matches the incoming company name and links to it rather than creating a duplicate. A company is uniquely identified in iPaaS.com by its name together with its department. Once the external-ID link is established, that dedicated external-ID record becomes the primary match for subsequent transfers, and the company name remains the fallback match until the link exists.
Company Address: Before adding an address, the integration compares it against the company's existing iPaaS.com addresses using the subscription's Customer Address Fields to Match setting and links to a matching address instead of creating a duplicate. The PreventDuplicate flag is set to true on every address to enable this comparison.
Supported Child Collections
Add/Update Oracle ERP Company Address TO iPaaS.com: Transfers the company's addresses, one record per address. Each address is linked back to the parent company and is transferred automatically as part of the company transfer. This is a child collection with no independent Manual Sync entry point; its addresses are refreshed by re-syncing the parent company.
System Caveats
Oracle ERP Caveats
Read-only source: These collections only read from Oracle ERP. The integration never creates, updates, or deletes companies or addresses in Oracle ERP.
Company identity: Companies are matched by company name, and the Oracle ERP account number is stored on the iPaaS.com record as a business identifier. A stable, accurate company name in the source is required for reliable matching across transfers.
Address completeness: Only address fields present in the source are written. Blank source fields are left unset on the iPaaS.com address rather than overwriting existing values with blanks.
iPaaS.com Caveats
Company name is the match key: iPaaS.com uses the mapped Name (company name) to match an incoming company to an existing Customer Company before the external-ID link is established, and a company is uniquely identified by its name together with its department. Ensure the mapped company name is accurate and stable per company; leaving it unmapped can result in duplicate company records.
Account number is not the match key: The mapped account number is stored for visibility and reporting. It is not the required primary identifier and is not used to prevent duplicates; the transfer does not fail if it is left unmapped.
Address matching setting: Duplicate-address prevention depends on the subscription's Customer Address Fields to Match setting. The fields listed there determine when two addresses are treated as the same; configure them to match your data before transferring companies with addresses.
Parent company dependency: Addresses are linked to their parent company. The parent company is created or matched as part of the same transfer, so if the parent company fails to create, its addresses cannot be linked.
Setup Requirements
For full setup steps, see the Installation Instructions and Connections and Settings articles. The integration-wide setup (connection credentials, subscription settings) is documented there and not repeated here. Before transferring companies with addresses, configure the Customer Address Fields to Match subscription setting so that duplicate-address prevention compares the fields appropriate for your data.
Integration Flow
When a scheduled poll runs, or a Manual Sync is initiated, the integration processes the transfer in the following order:
Retrieve companies from Oracle ERP. For scheduled polling, the integration reads companies created or updated since the last successful poll; the initial poll window is governed by the Company Search Poll Days subscription setting. For Manual Sync, the integration reads the single company identified by the account identifier entered on the Manual Sync page. Each company is read together with its addresses.
Match the company and prevent duplicates. The integration looks for an existing iPaaS.com Customer Company that matches by external-ID record first, and by company name before that link exists. If a match is found, the integration links to it rather than creating a duplicate; otherwise a new Customer Company is created.
Map the company fields. The company name and account number are translated into the iPaaS.com Customer Company shape.
Process the child addresses. Each address on the company is processed through the Add/Update Oracle ERP Company Address TO iPaaS.com child collection. Before adding an address, the integration compares it against the company's existing iPaaS.com addresses using the Customer Address Fields to Match setting and links to a matching address instead of creating a duplicate. The company name is carried from the parent record onto each address.
Record external-ID links. On success, iPaaS.com records the external-ID link for the company and for each address so that subsequent transfers route to the same records rather than creating duplicates.
Subscribers or their MiSP do not need to pre-create companies or addresses in iPaaS.com for this matching to occur; there is no hard prerequisite that blocks the company transfer.
Mappings
Add/Update Oracle ERP Company TO iPaaS.com
Description: Transfers customer company records from Oracle ERP to iPaaS.com through scheduled polling or Manual Sync. Maps the company name and account number so each Oracle ERP company is represented once as a Customer Company in iPaaS.com and matched reliably on future transfers.
Mapping Filter: None — this collection does not have a mapping filter applied. All company records retrieved through scheduled polling or Manual Sync are processed without additional filtering conditions.
Field Mapping Table
Mapping Type | Source Field (Oracle ERP) | Destination Field (iPaaS.com) | Description |
Field | Partyname | Name | Required. Maps the Oracle ERP party name to the iPaaS.com Customer Company Name (the company name). This is the only company field iPaaS.com requires, and a company is uniquely identified by its name together with its department. This value also drives duplicate prevention: when a company is transferred, the integration looks for an existing Customer Company whose name matches and links to it rather than creating a duplicate, until the external-ID link takes over that role. Keep the source party name stable and accurate so matching stays reliable; leaving it unmapped can result in duplicate company records. |
Field | AccountNumber | AccountNumber | Recommended. Sets the iPaaS.com Customer Company AccountNumber from the Oracle ERP customer account number. It stores the account number on the iPaaS.com record as a stable business identifier useful for reference and reporting. It is not the record's required primary identifier and is not the value used to prevent duplicate companies — the company name serves that role. The transfer does not fail if it is left unmapped. |
Add/Update Oracle ERP Company Address TO iPaaS.com (Child)
Description: Transfers company addresses from Oracle ERP to iPaaS.com as children of the parent Company transfer, one record per address. Maps the street lines, city, region, postal code, and country; carries the company name onto the address; and sets a duplicate-prevention flag so repeated transfers link to an existing address instead of creating duplicates. Addresses are not transferred independently through this collection — they always accompany the parent company.
Mapping Filter: None — this collection does not have a mapping filter applied. All addresses retrieved with their parent company are processed without additional filtering conditions.
Field Mapping Table
Mapping Type | Source Field (Oracle ERP) | Destination Field (iPaaS.com) | Description |
Field | Address1 | Address1 | Recommended. Maps the first line of the Oracle ERP customer address. Not required by iPaaS.com, but a complete street address improves address quality and helps the integration match this address against existing iPaaS.com addresses. When the source value is blank, no first address line is written. |
Field | Address2 | Address2 | Recommended. Maps the second line of the Oracle ERP customer address, typically used for suite, unit, or building detail. When the source value is blank, no second address line is written. |
Field | Address3 | Address3 | Recommended. Maps the third line of the Oracle ERP customer address, typically used only when the source address has a third line. When the source value is blank, no third address line is written. |
Field | City | City | Recommended. Maps the Oracle ERP address city. Improves address completeness and can contribute to duplicate-address matching depending on the fields configured in the Customer Address Fields to Match setting. When the source value is blank, no city is written. |
Field | State | Region | Recommended. Maps the Oracle ERP address state to the iPaaS.com address Region (state or province). Improves address completeness and can contribute to duplicate-address matching depending on the fields configured in the Customer Address Fields to Match setting. When the source value is blank, no region is written. |
Field | PostalCode | PostalCode | Recommended. Maps the Oracle ERP address postal code. Improves address completeness and can contribute to duplicate-address matching depending on the fields configured in the Customer Address Fields to Match setting. When the source value is blank, no postal code is written. |
Field | Country | Country | Recommended. Maps the Oracle ERP address country. Improves address completeness and can contribute to duplicate-address matching depending on the fields configured in the Customer Address Fields to Match setting. When the source value is blank, no country is written. |
Dynamic Formula | Parent.CustomerName | Company | Recommended. Carries the company name from the parent Company record onto the address, keeping the address labeled with the same company name as the customer it belongs to. Because the value comes from the parent record, it stays consistent with the company name mapped on the parent Company collection. |
Static | Static value: true | PreventDuplicate | Control flag. Sets the address PreventDuplicate flag to true for every address transferred through this collection. With this flag set, iPaaS.com checks whether the incoming address already exists on the company before adding it and links to the existing address instead of creating a duplicate. The comparison uses the fields configured in the Customer Address Fields to Match setting. This is a valid control-flag value, not a placeholder; leave it set unless you specifically intend to allow duplicate addresses. |
Error Handling
Errors from these mapping collections appear in the iPaaS.com Dashboard under Integration Monitoring / Error Logs. If Oracle ERP is temporarily unavailable when a transfer is triggered, the transfer fails and an error appears there; the company and its addresses can be retried through Manual Sync of the parent company or on the next scheduled poll. For the full catalog of error messages, their descriptions, and resolution steps, see the Error Messages article.
Testing & Validation
Test Scenarios
Create a new company in Oracle ERP with a name and account number, then run a scheduled poll or a Manual Sync using the account identifier, and verify that a new iPaaS.com Customer Company is created with the correct Name and AccountNumber.
Update the name of an existing company in Oracle ERP and verify that the matching iPaaS.com Customer Company is updated on the next transfer without creating a duplicate.
Transfer a company that already exists in iPaaS.com by name (with no external-ID link yet) and verify the integration links to the existing record rather than creating a duplicate, then records the external-ID link.
Add one or more addresses to a company in Oracle ERP and verify that the addresses are transferred with the parent company, carry the correct company name, and populate the mapped street, city, region, postal code, and country fields.
Re-transfer a company whose addresses already exist in iPaaS.com and verify that the PreventDuplicate flag and the Customer Address Fields to Match setting cause the integration to link to the existing addresses rather than create duplicates.
Validation Checklist
The Company Search Poll Days subscription setting is configured to the desired initial poll window.
The Customer Address Fields to Match subscription setting lists the fields that should determine when two addresses are treated as the same.
The mapped Name field is populated for every company so that matching stays reliable and duplicates are prevented.
After a transfer, the iPaaS.com Customer Company shows the expected Name and AccountNumber, and its addresses show the expected street, city, region, postal code, country, and company name.
Additional Notes
Addresses transfer with the parent. Company addresses are transferred as part of the parent company transfer and are not synced independently. To refresh a company's addresses, re-sync the parent company.
Custom integration scope. At the time this documentation was written, this integration is built for a specific client's Oracle ERP configuration. Behavior with other Oracle ERP configurations has not been validated; subscribers or their MiSP should validate company and address transfers in a staging environment before relying on them in production.