This documentation covers how Oracle ERP item (product catalog) records are captured into iPaaS.com as Product records, and how their on-hand inventory is captured as Product Inventory records. The integration reads items from Oracle ERP and creates or updates the matching Product in iPaaS.com, mapping the item's identity fields and description and applying a set of standard catalog defaults so transferred items are immediately usable. Each item's inventory is transferred alongside it through the associated Add/Update Oracle ERP Item Inventory TO iPaaS.com child collection, one record per warehouse; a separate Add/Update Oracle ERP Item Inventory Standalone TO iPaaS.com collection can transfer inventory on its own. Transfers run in one direction only — Oracle ERP to iPaaS.com — and are driven by scheduled polling or on-demand Manual Sync.

Manual Sync ID Format

To transfer a specific item together with its inventory child records, enter the Oracle ERP item's system record identifier — a numeric value, for example 100000 — on the iPaaS.com Manual Sync page.

An inventory record is identified by the Oracle ERP item number and the warehouse name joined by a pipe character — the item number, then a pipe character, then the warehouse name (for example, 100000|Main Warehouse). This Manual Sync ID applies to both inventory collections. The child and the standalone Item Inventory collections are each independently transferable — each has its own scheduled polling and its own Manual Sync entry point using this ID — and the child inventory is additionally transferred automatically as part of a parent Item transfer.

External ID Format (saved after sync)

On the first successful transfer, iPaaS.com saves the Oracle ERP item 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 Product rather than creating a duplicate.

Until that external-ID link exists — typically on the very first transfer — the mapped Sku value is the practical match: when no external-ID record yet exists for an incoming item, the integration links to an existing iPaaS.com Product whose SKU matches, then records the external-ID link for future transfers. Keep the mapped SKU unique and stable per item.

Each inventory record transferred through the child or standalone collection is saved with its own external-ID link so subsequent transfers update the same Product Inventory record rather than creating a duplicate. Each inventory record is also linked to its parent Product and to the resolved iPaaS.com Location.

Not supported. This integration captures items and inventory from Oracle ERP into iPaaS.com in one direction only, and it does not process deletions for these records. Removing an item or an inventory record in Oracle ERP does not delete the corresponding record in iPaaS.com, delete mappings are not included in the default templates, and the integration does not delete products or inventory in either system.

None. These mapping collections do not configure, require, or transfer custom fields.

This integration captures items and their inventory in one direction only (Oracle ERP to iPaaS.com). There is no collection that writes items or inventory back to Oracle ERP, so for the parent Item there is no opposing-direction collection to reconcile against and no circular-update risk.

Two collections operate on the same Product Inventory records, and they can conflict with each other:

Before enabling both, review their mapping filters and Add/Update settings so that inventory for the same item and warehouse is not processed by two conflicting configurations, and decide which collection is the source of truth for a given set of records.

The integration does not implement selectable collision-handling methods for these collections. Instead, duplicate prevention is handled by matching and external-ID linking: an item links to an existing iPaaS.com Product by external-ID record first, and by matching Sku before that link exists; an inventory record is matched by its external-ID link and is tied to its parent Product and resolved iPaaS.com Location.

The Add/Update Oracle ERP Item Inventory Standalone TO iPaaS.com collection covers the same Product Inventory records but is a standalone collection, not a child of the Item collection — it resolves its parent Item link itself and is documented in the Mappings and Duplicate or Conflicting Mappings sections above.

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 inventory through either inventory collection, create the iPaaS.com Locations the transfers depend on: in iPaaS.com, go to Settings → Locations and create a Location for each Oracle ERP warehouse whose inventory you intend to transfer, with each Location's name matching the corresponding Oracle ERP warehouse name exactly. When using the standalone Item Inventory collection, also transfer the parent Items first (through Add/Update Oracle ERP Item TO iPaaS.com), or confirm they are already present in iPaaS.com, so the standalone inventory records can resolve their parent link. Subscribers or their MiSP must create these Locations manually — the integration does not create them.

When a scheduled poll runs, or a Manual Sync is initiated, the integration processes an item transfer in the following order:

Beyond this parent-driven flow, the child Item Inventory collection is also independently transferable: its own scheduled polling (governed by the Product Inventory Search Poll Days subscription setting) and its own Manual Sync entry point transfer inventory records directly, following the same Location resolution described in step 4, in addition to being transferred automatically with a parent Item as described above.

The standalone Item Inventory collection likewise follows the same Location resolution but transfers inventory on its own. Unlike the child collection, it does not transfer the parent Item automatically — instead it resolves the parent Product from the Oracle ERP item's existing external-ID link, so the parent Item must already have been transferred to iPaaS.com. When the parent link or the Location cannot be resolved, the inventory transfer stops with an error.

Description: Transfers item (product catalog) records from Oracle ERP to iPaaS.com through scheduled polling or Manual Sync. Maps the item's name, SKU, and description, and applies fixed catalog defaults (type, status, tracking method, and a default price) so transferred items are immediately usable in iPaaS.com.

Mapping Filter: None — this collection does not have a mapping filter applied. All item records retrieved through scheduled polling or Manual Sync are processed without additional filtering conditions.

Field Mapping Table

Description: Transfers on-hand inventory quantities from Oracle ERP to iPaaS.com as children of the parent Item transfer, one record per item and warehouse combination. Maps the on-hand quantity to the available and on-hand quantity fields, resolves the iPaaS.com Location that corresponds to the Oracle ERP warehouse, and records an inventory cost. This collection is transferred automatically as part of a parent Item transfer, and it can also be transferred independently through its own scheduled polling and its own Manual Sync entry point.

Mapping Filter:

if (Id == "|" || Id == null)
return false;
​
var Locationid = await GetLocationIdByName(WarehouseName);
if(!string.IsNullOrEmpty(Locationid))
return true;
throw new Exception($"Cannot find location \"{WarehouseName}\" please create it manually in iPaaS");

Filter Description: This collection's mapping filter enforces the location prerequisite. Records with an empty item-and-warehouse key (no item number and no warehouse name) are skipped and not processed. For all other records, the integration looks up an iPaaS.com Location whose name matches the Oracle ERP warehouse name; if a matching Location exists, the record is processed. If no matching Location exists, the transfer stops with the error Cannot find location "[warehouse name]" please create it manually in iPaaS. The filter does not pin any environment-specific value — the warehouse name comes from each source record — so the subscriber action is to create the matching Locations in iPaaS.com, not to edit the filter.

Field Mapping Table

Dynamic Formula Documentation — LocationId

var Locationid = await GetLocationIdByName(WarehouseName);
if(!string.IsNullOrEmpty(Locationid))
return Locationid;
return null;

This formula looks up an iPaaS.com Location whose name matches the Oracle ERP warehouse name on the source record and returns that Location's identifier, or no value when no matching Location is found. It resolves the same Location prerequisite enforced by the collection's mapping filter: the matching iPaaS.com Location must exist before inventory for that warehouse can transfer.

Description: Transfers on-hand inventory quantities from Oracle ERP to iPaaS.com independently of the parent Item transfer, one record per item and warehouse combination. Maps the on-hand quantity to the available and on-hand quantity fields, resolves the iPaaS.com Location that corresponds to the Oracle ERP warehouse, and links each inventory record to its parent Item. Unlike the child collection, this collection has its own Manual Sync entry point and does not transfer the parent Item automatically.

Mapping Filter:

var Locationid = await GetLocationIdByName(WarehouseName);
if(!string.IsNullOrEmpty(Locationid))
return true;
throw new Exception($"Cannot find location \"{WarehouseName}\" please create it manually in iPaaS");

Filter Description: This collection's mapping filter enforces the location prerequisite. For each record, the integration looks up an iPaaS.com Location whose name matches the Oracle ERP warehouse name; if a matching Location exists, the record is processed. If no matching Location exists, the transfer stops with the error Cannot find location "[warehouse name]" please create it manually in iPaaS. The filter does not pin any environment-specific value — the warehouse name comes from each source record — so the subscriber action is to create the matching Locations in iPaaS.com, not to edit the filter.

Field Mapping Table

Dynamic Formula Documentation — LocationId

var Locationid = await GetLocationIdByName(WarehouseName);
if(!string.IsNullOrEmpty(Locationid))
return Locationid;
return null;

This formula looks up an iPaaS.com Location whose name matches the Oracle ERP warehouse name on the source record and returns that Location's identifier, or no value when no matching Location is found. It resolves the same Location prerequisite enforced by the collection's mapping filter.

Dynamic Formula Documentation — ParentId

var ExternalId = await GetProductExternalIdByItemNumber(Item);
if(!string.IsNullOrEmpty(ExternalId)){
return await GetSpaceportIdAsync(ExternalId, "Product", SpaceportSystemId);
}

This formula finds the external-ID link recorded for the Oracle ERP item number and, when a link exists, returns the identifier of the corresponding iPaaS.com Item so the inventory record can be attached to its parent. If the item has not yet been transferred to iPaaS.com — and therefore has no external-ID link — no value is returned, and the parent Item must be transferred first through Add/Update Oracle ERP Item TO iPaaS.com.

Errors from these mapping collections appear in the iPaaS.com Dashboard under Integration Monitoring / Error Logs.

For the full catalog of error messages, their descriptions, and resolution steps, see the Error Messages article.