Sales Order — From iPaaS.com

Order Update — From iPaaS.com

Sales Order Lines — From iPaaS.com

Sales Order — To iPaaS.com

Company — To iPaaS.com

Product — To iPaaS.com

Product Inventory — To iPaaS.com

Order Tracking — To iPaaS.com

General Errors

Description: Oracle ERP did not return a created order for the new sales order transfer, so the integration reports the create as failed. This is usually accompanied by the Oracle validation detail described under OERP-EXTN-1002, which explains what Oracle rejected.

Resolution: Review the accompanying OERP-EXTN-1002 validation text to identify the value Oracle rejected, correct the source data or mapping configuration in iPaaS.com — commonly the order type, the sold-to customer, or the ship-to location — then re-transfer the order.

Description: Oracle ERP rejected the order and returned one or more validation messages, which the integration surfaces verbatim in place of [Oracle ERP validation messages]. Typical causes are a missing or invalid order type, an invalid ship-to location, or a value Oracle ERP does not accept. The order is not created.

Resolution: Read the Oracle validation text included with the error to identify which value was rejected, then correct the source data or the mapping configuration in iPaaS.com so the order satisfies Oracle ERP's requirements and re-transfer the order.

Description: Before an order can be created, the company assigned to the iPaaS.com sales order must already exist as a customer in Oracle ERP and be linked to that Oracle ERP customer in iPaaS.com. This error appears when the assigned company has no matching Oracle ERP customer record. [account ID] is the customer account number the integration attempted to match. This check runs on both order creation and order update.

Resolution: Assign a company that is already a registered Oracle ERP customer, or register the company in Oracle ERP first, then ensure it has been transferred to iPaaS.com and matched to its Oracle ERP customer record before the order is synced. This integration does not create customers in Oracle ERP.

Description: An order transfer requires a company to be assigned to the sales order so the integration can resolve which Oracle ERP customer the order belongs to. This error appears when the order has no company assigned. It is distinct from OERP-NFND-1001: here the company link cannot be resolved at all, rather than resolving to a company that is not yet an Oracle ERP customer. This check runs on both order creation and order update.

Resolution: Assign a company to the iPaaS.com sales order, and ensure that company has been transferred to iPaaS.com and matched to its Oracle ERP customer record, before syncing the order.

Description: When resolving the ship-to location for an order, the integration matches the order's PARTY_SITE_NUMBER against the sites registered under the Oracle ERP customer identified by [account ID]. This error appears when that customer has no site matching the provided PARTY_SITE_NUMBER.

Resolution: Provide a PARTY_SITE_NUMBER that exists on the Oracle ERP customer account, and confirm the customer's ship-to sites in Oracle ERP include the site the order references. If the mapping supplies the PARTY_SITE_NUMBER, review that mapping with your MiSP so it resolves to a valid site.

Description: While resolving the customer for an order, the integration looked up the customer number carried on the transaction and Oracle ERP returned no matching customer record. [customer number] is the value the integration attempted to match. This is the same underlying cause as OERP-NFND-1001, surfaced while resolving the order's customer.

Resolution: Confirm the customer number on the order corresponds to a registered Oracle ERP customer, and that the company has been transferred to iPaaS.com and matched to its Oracle ERP customer record before the order is synced.

Description: The integration looked up an order in Oracle ERP by order number and Oracle ERP returned no matching order. [order number] is the value the integration attempted to match. (The message text refers to "Customer" but the lookup is by order number.)

Resolution: Confirm an order with that order number exists in Oracle ERP. If the order should exist, verify the order number matches the value in Oracle ERP.

Description: When writing an order from iPaaS.com, the integration automatically links each order line to the matching Oracle ERP order line to avoid creating duplicates. This error appears when that automatic link could not be recorded, so a duplicate order line may result. This linking is automatic and built into the integration; it is not a configurable setting.

Resolution: Re-transfer the order. If the error persists, ask your MiSP to check the affected order in Oracle ERP for duplicate lines and to confirm the order-line external IDs are recorded in iPaaS.com.

Description: The update flow targets a sales order that is already present in Oracle ERP, matched through the order link recorded when the order was first created. This error appears when no matching order can be found — most often because the order was never created there, or its create transfer has not yet completed. An update never creates a new order.

Resolution: Create the order in Oracle ERP first through the Add Oracle ERP Sales Order flow, confirm that transfer completed successfully, then run the update.

Description: The integration attempted to retrieve an existing order from Oracle ERP and no order was returned. This typically means the order does not exist in Oracle ERP under the expected order number, or was removed after iPaaS.com last received it.

Resolution: Confirm the order exists in Oracle ERP under the expected order number. If it was intentionally removed, no action is needed; if it should exist, verify the order number matches the value in Oracle ERP.

Description: Each order line's SKU must resolve to an item that already exists in Oracle ERP. This error appears when a line's SKU does not match any Oracle ERP item number. [SKU] is the value taken from the iPaaS.com order line. The integration does not create products in Oracle ERP. Lines with an empty SKU are skipped rather than raising this error.

Resolution: Ensure every product used on an order line is registered as an item in Oracle ERP with an item number that matches the SKU on the iPaaS.com sales order line, before syncing the order. Keep SKUs on iPaaS.com sales order lines consistent with the item numbers registered in Oracle ERP.

Description: The integration found an existing iPaaS.com transaction matching the Oracle order number and tried to link them to avoid a duplicate, but the link could not be recorded.

Resolution: Re-transfer the order. If the error persists, ask your MiSP to check iPaaS.com for a duplicate transaction with the same order number and to confirm the transaction's external ID is recorded.

Description: Before transferring the order, the integration attempted to create the order's customer company in iPaaS.com because it did not yet exist, and that create did not succeed. The order is not transferred.

Resolution: Confirm the customer associated with the order is valid in Oracle ERP and can transfer to iPaaS.com on its own through the Company flow, then re-transfer the order. If the company transfer fails on its own, resolve that error first.

Description: The integration matched an Oracle order line to an existing iPaaS.com transaction line by SKU and tried to link them to avoid a duplicate, but the link could not be recorded.

Resolution: Re-transfer the order. If the error persists, ask your MiSP to check the transaction in iPaaS.com for duplicate lines and to confirm the line external IDs are recorded.

Description: An order line referenced a product that did not yet exist in iPaaS.com, so the integration attempted to create it first, and that create did not succeed. The order is not transferred.

Resolution: Confirm the product for the affected line is valid in Oracle ERP and can transfer to iPaaS.com on its own through the Product flow, then re-transfer the order.

Description: The integration matched an Oracle order's tracking record to an existing iPaaS.com tracking record by tracking number and tried to link them to avoid a duplicate, but the link could not be recorded.

Resolution: Re-transfer the order. If the error persists, ask your MiSP to check the transaction in iPaaS.com for duplicate tracking records and to confirm the tracking external IDs are recorded.

Description: The integration matched an Oracle order's billing or shipping address to an existing iPaaS.com transaction address and tried to link them to avoid a duplicate, but the link could not be recorded.

Resolution: Re-transfer the order. If the error persists, ask your MiSP to check the transaction in iPaaS.com for duplicate addresses and to confirm the address external IDs are recorded.

Description: The integration looked up a customer in Oracle ERP by account number and Oracle ERP returned no matching record. [account number] is the account number the integration attempted to match. This can occur during a company transfer, or while resolving the customer for an order.

Resolution: Verify that a customer with that account number exists in Oracle ERP. When this occurs while transferring an order, confirm the company assigned to the order is a registered Oracle ERP customer — see OERP-NFND-1001.

Description: The integration found an existing iPaaS.com company matching the Oracle customer by name and tried to link them to avoid a duplicate, but the link could not be recorded.

Resolution: Re-transfer the company. If the error persists, ask your MiSP to check iPaaS.com for a duplicate company with the same name and to confirm the company external ID is recorded.

Description: The integration matched an Oracle customer address to an existing iPaaS.com company address by party site ID and tried to link them to avoid a duplicate, but the link could not be recorded.

Resolution: Re-transfer the company. If the error persists, ask your MiSP to check the company in iPaaS.com for duplicate addresses and to confirm the address external IDs are recorded.

Description: The integration looked up a product in Oracle ERP by its item number and Oracle ERP returned no matching record. [item number] is the value the integration attempted to match. This can occur when a product referenced by another record — such as an order line or an inventory record — no longer exists in Oracle ERP, or when the item number does not match any Oracle ERP item.

Resolution: Verify the product exists in Oracle ERP under the expected item number. If it was intentionally removed, no action is needed on the missing record; if it should exist, confirm the item number matches what is registered in Oracle ERP.

Description: The integration found an existing iPaaS.com product matching the Oracle item and tried to link them to avoid a duplicate, but the link could not be recorded.

Resolution: Re-transfer the product. If the error persists, ask your MiSP to check iPaaS.com for a duplicate product and to confirm the product external ID is recorded.

Description: The integration attempted to retrieve an inventory record from Oracle ERP and none was returned, so the record is reported as not found. This most often means the referenced item or its inventory no longer exists in Oracle ERP.

Resolution: Confirm the item and its inventory exist in Oracle ERP. If the item was intentionally removed, no action is needed; if it should exist, verify the item number matches what is registered in Oracle ERP.

Description: Inventory in iPaaS.com is tracked per location. For each inventory record, the integration looks up an iPaaS.com Location whose name matches the Oracle ERP warehouse name on that record. This error appears when no iPaaS.com Location matches. [warehouse name] is the Oracle ERP warehouse the record came from.

Resolution: Create a Location in iPaaS.com whose name matches the Oracle ERP warehouse name exactly, then re-transfer the inventory record. The match is by name, so confirm the spelling and spacing align. When several warehouses are in use, create a matching iPaaS.com Location for each.

Description: The integration matched an Oracle inventory record to an existing iPaaS.com inventory record by product and location and tried to link them to avoid a duplicate, but the link could not be recorded.

Resolution: Re-transfer the inventory record. If the error persists, ask your MiSP to check iPaaS.com for a duplicate inventory record for that product and location and to confirm the external ID is recorded.

Description: An inventory record referenced a product that did not yet exist in iPaaS.com, so the integration attempted to create it first, and that create did not succeed. The inventory record is not transferred.

Resolution: Confirm the product for the affected inventory record is valid in Oracle ERP and can transfer to iPaaS.com on its own through the Product flow, then re-transfer the inventory record.

Description: A standalone tracking transfer identifies the delivery record with a composite id made of the line id, order number, and delivery id. This error appears when the id supplied for a standalone transfer is missing or not in the required LINE_ID|ORDER_NUMBER|DELIVERY_ID format.

Resolution: Provide the delivery id in the exact LINE_ID|ORDER_NUMBER|DELIVERY_ID format, with all three parts present and separated by the | character.

Description: A tracking record referenced an order that did not yet exist in iPaaS.com, so the integration attempted to create the order first, and that create did not succeed. The tracking record is not transferred.

Resolution: Confirm the order for the affected tracking record is valid in Oracle ERP and can transfer to iPaaS.com on its own through the Sales Order flow, then re-transfer the tracking record.

Description: The integration received an error response, or no usable response, from Oracle ERP while making a request. This is commonly a transient condition — Oracle ERP was temporarily unavailable, timed out, or returned a server error — rather than a problem with the data being sent. [status] is the HTTP status Oracle ERP returned, [action] is the operation being performed, and [Oracle ERP response] carries any detail Oracle ERP included.

Resolution: Retry the transfer, or re-trigger the parent order transfer through Manual Sync. If the error persists across retries, confirm the Oracle ERP endpoint is reachable and the connection credentials are current — see the Oracle ERP Connections and Settings article. For sustained failures, contact iPaaS.com Support at support@ipaas.com.

Description: A lookup in Oracle ERP for a specific record — a customer, an order, or an inventory record — returned no result, so the integration reports the record as not found. This most often means the referenced record does not exist in Oracle ERP, or was removed after iPaaS.com last received it.

Resolution: Confirm the referenced record exists in Oracle ERP. If it was intentionally removed, no action is needed; if it should exist, verify the identifier used to look it up — account number, order number, or item number — matches the value in Oracle ERP.

Oracle ERP Connections and Settings

Oracle ERP Installation Instructions

Oracle ERP API Endpoints

Oracle ERP Known Limitations