This article documents the mapping collections that write Sales Orders from iPaaS.com to Oracle ERP. Four collections are covered: a create pair that adds a new Oracle ERP order and its lines, and an update pair that writes changes to an order that already exists in Oracle ERP. Orders are transferred outbound by subscriber-enabled Outbound Data Flow triggers or on demand through Manual Sync; the integration creates new orders and applies partial updates to existing orders, and it never deletes orders.

On this page:

Manual Sync ID Format

Enter the iPaaS.com Sales Order (Transaction) record identifier — the numeric iPaaS.com-side record ID for the order — on the Manual Sync page. The integration uses this ID to retrieve the full order, with its line items, from iPaaS.com and write it to Oracle ERP. The child line collections have no independent Manual Sync entry point; lines are transferred through the parent order's Manual Sync ID. Manual Sync is always available regardless of whether automatic transfers are enabled.

External ID Format (saved after sync)

After a successful create, iPaaS.com records the link between the iPaaS.com Sales Order and the newly created Oracle ERP order (the Oracle ERP order number) on the iPaaS.com Sales Order record. Each line item is linked individually as well, associating the iPaaS.com line with its Oracle ERP order line identifier.

This recorded external-id link is the primary match the integration relies on. It routes subsequent transfers to the update collection — rather than creating a duplicate order — and it is how the update collection locates the existing Oracle ERP order and matches each existing line. The Oracle ERP order number and order line identifiers written onto the order provide cross-system visibility and serve as the values the update formulas resolve through when targeting the existing record. Both the order-number identifier and the line identifiers are numeric values assigned by Oracle ERP; the integration records and reuses them automatically, so subscribers do not create these links manually.

Not supported. In this direction the integration only writes orders to Oracle ERP, and it performs create and update operations only. There is no outbound delete for Sales Orders or Sales Order Lines — removing an order or a line in Oracle ERP is not performed by these collections and must be handled directly in Oracle ERP.

None. The integration does not implement custom-field data types or category management for this direction. One optional mapping on the create collection reads a value from an iPaaS.com custom field named CustomerPO to populate the Oracle ERP customer purchase order number; this is a single field read, documented in the create collection's field mapping table, and requires no other custom-field configuration.

The child line collections are not triggered on their own; they run as part of the parent order transfer.

The integration does not implement selectable collision-handling methods for this direction. Instead, it prevents duplicate orders through the recorded external-id link described under ID Format: once an order has been created in Oracle ERP, its link is stored on the iPaaS.com Sales Order, and later transfers use that link to update the existing order rather than create a second one.

The following collections operate on the same Sales Order data and should be reviewed together before both are enabled:

Before enabling these outbound collections alongside the opposite-direction "TO iPaaS.com" Sales Order collections, review and customize each collection's mapping filters, and clearly define which system is the source of truth for order data, so that changes do not propagate back and forth between the two systems.

Create — Add Oracle ERP Sales Order FROM iPaaS.com. When a Sales Order create transfer is triggered from iPaaS.com, the integration writes to Oracle ERP in the following order:

Update — Update Oracle ERP Sales Order FROM iPaaS.com. When a Sales Order update is sent from iPaaS.com, the integration writes to Oracle ERP in the following order:

Partial update — unmapped fields are not cleared. An update changes only the fields that are mapped and actually provided a value. Fields that are left unmapped, or that resolve to an empty value, are not written and are not cleared in Oracle ERP — they keep their existing Oracle ERP values. This is a partial update, not a full record replace, and the order must already exist in Oracle ERP before it can be updated.

The field mapping tables below list each mapping as it is configured in the default template. In this direction the source system is iPaaS.com and the destination system is Oracle ERP. For each collection whose live mapping filter is non-empty, the filter is reproduced exactly as configured, followed by a plain-language description of how it behaves. The verbatim filter and formula reproductions show the mapping expressions exactly as they appear in the iPaaS.com mapping editor; internal identifiers inside those expressions are part of the configured expression.

Description: Writes a new sales order to Oracle ERP for each transferred iPaaS.com Sales Order. It writes the order header — the sold-to customer, ship-to location, order type, and reference attributes — and, through its child collection, writes each line item in the same transfer.

Mapping Filter (live configuration):

if(CompanyId > 0){
var AccountId = await GetExternalIdAsync(CompanyId, "Company", SpaceportSystemId);
if(AccountId != null && !string.IsNullOrEmpty(AccountId.ToString())){
var CustomerExsists = await GetOracleCustomerByiPaaSCompanyID(CompanyId.ToString());
if(CustomerExsists != null && CustomerExsists == "true"){
return true;
}
throw new Exception($"The company linked to Account ID {AccountId} does not exist as a customer in Oracle ERP. You need to assign a company to the transaction that is already registered as a customer in Oracle ERP.");
}
}
throw new Exception("The company is not associated with the transaction. You need to assign a company to the transaction in order to proceed with the flow transfer.");

Filter Description: This filter enforces a customer prerequisite before an order is processed:

The filter does not pin any environment-specific value; it evaluates the company on each order, so nothing in the filter itself needs to be replaced.

Field Mapping Table

Mapping Formulas — the Dynamic Formula mappings above are configured with the following expressions:

var AccountId = await GetExternalIdAsync(CompanyId, "Company", SpaceportSystemId);
if(AccountId != null && !string.IsNullOrEmpty(AccountId.ToString())){
return long.Parse(AccountId);
}

var AccountId = await GetExternalIdAsync(CompanyId, "Company", SpaceportSystemId);
if(AccountId != null && !string.IsNullOrEmpty(AccountId.ToString())){
var ShipId = await GetOracleCustomerShipToOrgIdByiPaaSCompanyIdAndOracleCustomerPartySiteNumber(CompanyId.ToString(), "1234");
if(!string.IsNullOrEmpty(ShipId)){
return long.Parse(ShipId);
}
throw new Exception($"The company linked to Account ID {AccountId} does not have the specified PARTY_SITE_NUMBER in an Oracle ERP customer. You need to provide a valid PARTY_SITE_NUMBER to the mapping function.");
}

return GetCustomFieldValue(CustomFields, "CustomerPO");

Description: Writes the line items of a sales order to Oracle ERP as the child of the create collection. For each line on the iPaaS.com Sales Order, it resolves the line's SKU to an Oracle ERP item, sets the ordered quantity, sets a scheduled ship date, and directs Oracle ERP to create the line. Lines are added only when their product and quantity are valid.

Mapping Filter (live configuration):

if(!string.IsNullOrEmpty(Sku.ToString())){
var InventoryItemId = await GetOracleProductBySku(Sku.ToString());
if(!string.IsNullOrEmpty(InventoryItemId.ToString())){
return true;
}
throw new Exception($"The product with the provided SKU = {Sku} does not exist in Oracle ERP as a valid Product Item Number. To create a line item for the sales order, you must assign a product that is already registered as a valid item in Oracle ERP.");
}
return false;

Filter Description: This filter enforces a product prerequisite on each line:

The filter does not pin any environment-specific value; it evaluates the SKU on each line, so nothing in the filter itself needs to be replaced.

Field Mapping Table

Mapping Formulas — the Dynamic Formula mappings above are configured with the following expressions:

if (Qty > 0)
return Qty;
return null;

if(!string.IsNullOrEmpty(Sku.ToString())){
var InventoryItemId = await GetOracleProductBySku(Sku.ToString());
if(!string.IsNullOrEmpty(InventoryItemId.ToString())){
return long.Parse(InventoryItemId);
}
}

var currentDateTime = CurrentDateTime();
int businessDaysAdded = 0;
while (businessDaysAdded < 6)
{
currentDateTime = currentDateTime.AddDays(1);
// Check if the current day is a weekday
if (currentDateTime.DayOfWeek != DayOfWeek.Saturday && currentDateTime.DayOfWeek != DayOfWeek.Sunday)
{
businessDaysAdded++;
}
}
return currentDateTime.ToString("yyyy-MM-ddTHH:mm:sszzz");;

Description: Writes header-level changes to a Sales Order that already exists in Oracle ERP and, through its child collection, updates existing order lines and adds new lines to the same order. Creating new orders is handled by the create collection; this collection is dedicated to updates and does not create orders.

Mapping Filter (live configuration):

if(CompanyId > 0){
var AccountId = await GetExternalIdAsync(CompanyId, "Company", SpaceportSystemId);
if(AccountId != null && !string.IsNullOrEmpty(AccountId.ToString())){
var CustomerExsists = await GetOracleCustomerByiPaaSCompanyID(CompanyId.ToString());
if(CustomerExsists != null && CustomerExsists == "true"){
return true;
}
throw new Exception($"The company linked to Account ID {AccountId} does not exist as a customer in Oracle ERP. You need to assign a company to the transaction that is already registered as a customer in Oracle ERP.");
}
}
throw new Exception("The company is not associated with the transaction. You need to assign a company to the transaction in order to proceed with the flow transfer.");

Filter Description: This filter enforces the same customer prerequisite as the create collection before an order is processed:

The filter does not pin any environment-specific value; the company it checks comes from each order.

Field Mapping Table

Mapping Formulas — the Dynamic Formula mapping above is configured with the following expression:

var OrderNumber = await GetExternalIdAsync(Id, "Transaction", SpaceportSystemId);
if(OrderNumber != null && !string.IsNullOrEmpty(OrderNumber.ToString()))
{
var HeaderId = await GetOracleOrderHeaderIdByOrderNumber(OrderNumber.ToString());
if(!string.IsNullOrEmpty(HeaderId.ToString()))
{
return HeaderId.ToString();
}
}
return null;

Description: Writes each Sales Order line to Oracle ERP as part of the parent order update. For each line, it resolves the Oracle ERP item for the line's SKU, decides whether the line already exists in Oracle ERP, and either updates the existing line or adds a new line to the order — without creating duplicate lines. Only the fields that are mapped and provided are written; unmapped or empty fields are not cleared on the existing Oracle ERP line.

Mapping Filter (live configuration):

if(!string.IsNullOrEmpty(Sku.ToString())){
var InventoryItemId = await GetOracleProductBySku(Sku.ToString());
if(!string.IsNullOrEmpty(InventoryItemId.ToString())){
return true;
}
throw new Exception($"The product with the provided SKU = {Sku} does not exist in Oracle ERP as a valid Product Item Number. To create/update a line item for the sales order, you must assign a product that is already registered as a valid Product in Oracle ERP.");
}
return false;

Filter Description: This filter enforces a product prerequisite on each line:

The filter does not pin any environment-specific value; the SKU it checks comes from each line.

Field Mapping Table

Mapping Formulas — the Dynamic Formula mappings above are configured with the following expressions:

var InventoryItemId = await GetOracleProductBySku(Sku.ToString());
if(!string.IsNullOrEmpty(InventoryItemId.ToString())){
return long.Parse(InventoryItemId);
}
return null;

var LineId = await GetExternalIdAsync(Id, "Transaction Line", SpaceportSystemId);
if(LineId != null && !string.IsNullOrEmpty(LineId.ToString()))
return LineId.ToString();
return null;

var LineId = await GetExternalIdAsync(Id, "Transaction Line", SpaceportSystemId);
if(LineId != null && !string.IsNullOrEmpty(LineId.ToString())){
return "UPDATE";
}
return "CREATE";

if (Qty > 0)
return Qty;
return null;

Errors from these mapping collections appear in the iPaaS.com Dashboard / Integration Monitoring / Error Logs. The most common subscriber-facing errors are:

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