Overview
This document catalogs the error messages subscribers or their MiSP may encounter in the iPaaS.com Oracle ERP integration, grouped by data flow. For each error it explains, in plain language, what the error means, why it occurs, and how to resolve it.
Errors surface in iPaaS.com under Dashboard / Integration Monitoring / Error Logs. When a transfer stops with an error, no partial record is written for that transfer, and the record can be retried once the underlying cause is corrected.
This article covers the errors that require action. Behaviors that are handled silently by design — such as records skipped when a required key is empty, or lookups that treat a removed source record as deleted — do not raise an error and are described in the Oracle ERP Known Limitations article and the relevant Mapping Documentation instead.
Supported Flows
Order Creation — From iPaaS.com
Order Update — From iPaaS.com
Order Lines — From iPaaS.com
Company — To iPaaS.com
Product — To iPaaS.com
Product Inventory — To iPaaS.com
General Errors
Order Creation — From iPaaS.com
These errors occur when a new sales order is transferred from iPaaS.com to Oracle ERP.
Company Not a Registered Customer
The company linked to Account ID [account ID] 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.
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. A closely related message — noting that a customer number associated with the transaction does not exist in the Oracle ERP customer records — indicates the same underlying cause.
Resolution: Confirm the company assigned to the order is a registered customer in Oracle ERP, and that it has been transferred to iPaaS.com and matched to its Oracle ERP customer record before the order is synced. Either assign a company that is already a registered Oracle ERP customer, or register the company in Oracle ERP first. This integration does not create customers in Oracle ERP. This check runs on both order creation and order update.
Company Not Associated with the Transaction
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.
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, or the assigned company has not yet been linked to an Oracle ERP customer in iPaaS.com. It is distinct from the registered-customer error above: 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.
Order Rejected by Oracle ERP
Failed to create Sale Order in Oracle ERP.
Description: Oracle ERP rejected the new sales order during validation. When this happens, the integration also surfaces the validation messages Oracle ERP returned describing what was wrong with the order — for example 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: Review the Oracle ERP validation text included with the error to identify which value was rejected. Correct the source data or the mapping configuration in iPaaS.com so the order satisfies Oracle ERP's requirements — commonly the order type, the sold-to customer, or the ship-to location — then re-transfer the order. If the validation text is not actionable, contact iPaaS.com Support at support@ipaas.com.
Order Update — From iPaaS.com
These errors occur when a change to an existing sales order is transferred from iPaaS.com to Oracle ERP.
Order Does Not Exist Yet
Failed to update the Sales Order in Oracle ERP because the order does not exist. Please ensure the order is created in Oracle before attempting an update.
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 in Oracle ERP — 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.
The company prerequisite errors described under Order Creation — Company Not a Registered Customer and Company Not Associated with the Transaction — also apply when updating an order.
Order Lines — From iPaaS.com
These errors occur while writing the individual line items of a sales order to Oracle ERP, as part of a parent order create or update transfer.
Line Product Not Found
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.
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. The integration does not create products in Oracle ERP. [SKU] is the value taken from the iPaaS.com order line. Lines with an empty SKU are skipped rather than raising this error. During an order update, a nearly identical message appears that refers to creating or updating a line item.
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 used 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.
Company — To iPaaS.com
These errors occur while retrieving a customer from Oracle ERP, either during a company transfer or while resolving the customer for an order.
Customer Not Found by Account Number
Customer not found by Customer Account Number '[account number]'.
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 sold-to 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 Company Not a Registered Customer above. If the record should exist and the issue persists, contact iPaaS.com Support at support@ipaas.com.
Product — To iPaaS.com
These errors occur while retrieving a product from Oracle ERP by item number.
Product Not Found by Item Number
The product not found by item number '[item number]'.
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 in Oracle ERP, no action is needed on the missing record. If the product should exist, confirm the item number matches what is registered in Oracle ERP. If the issue persists, contact iPaaS.com Support at support@ipaas.com.
Product Inventory — To iPaaS.com
These errors occur while transferring inventory records from Oracle ERP into iPaaS.com.
Location Not Found
Cannot find location "[warehouse name]" please create it manually in iPaaS
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 the warehouse name. [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 with the Oracle ERP warehouse name. When several warehouses are in use, create a matching iPaaS.com Location for each.
General Errors
These errors can occur across more than one data flow.
Resource Not Found
Resource Not found
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. If the issue persists, contact iPaaS.com Support at support@ipaas.com.
Oracle ERP Unavailable or Returned an Error
Error calling Oracle ERP: [Oracle ERP response] (Http Code: [status])
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, 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.
Write Attempted on a Read-Only Data Flow
A create or update was attempted on a data flow that only reads from Oracle ERP.
Description: In this integration, only sales orders are written to Oracle ERP. All other entities — products, product inventory, companies, and order tracking — are read-only: they transfer from Oracle ERP into iPaaS.com and cannot be written back. This error appears if a create or update transfer is attempted on one of those read-only data flows, which are not configured to write to Oracle ERP.
Resolution: Configure create and update transfers only on the supported Oracle ERP write flow — the Add and Update Oracle ERP Sales Order collections. Do not enable create or update on a read-only data flow. If you encounter this on a data flow you did not change, contact iPaaS.com Support at support@ipaas.com.