Overview
This article catalogs the error messages the Epicor Prophet 21 integration can record while synchronizing data between Prophet 21 and iPaaS.com. Each entry explains what the message means, what causes it, and how to resolve it. Errors appear in the iPaaS.com Dashboard under Dashboard / Integration Monitoring / Error Logs, alongside the record and mapping collection that produced them.
Errors fall into two broad groups. Some come from validation rules built into the integration's mapping collections — subscribers or their MiSP can adjust these by editing the relevant mapping collection filter in the iPaaS.com UI. Others come from the integration's transfer logic and are resolved by correcting the underlying data or, where the message indicates a technical condition, by contacting iPaaS.com Support. The Resolution for each entry tells you which applies.
The integration also surfaces error text returned directly by the Prophet 21 platform during a write (for example, when Prophet 21 rejects an order). That text is passed through as Prophet 21 generates it and is not standardized here; treat the wording in the log as the platform's own and follow the guidance in Prophet 21 platform errors, at the end of this article.
Supported Flows
Customer To iPaaS
Company To iPaaS
Location To iPaaS
Product To iPaaS
Product Inventory To iPaaS
Transaction Add/Update From iPaaS
Transaction Line To iPaaS
Transaction Tracking Number To iPaaS
Transaction Tracking From iPaaS
Transaction Address From iPaaS
Prophet 21 platform errors
Customer To iPaaS
Duplicate customer link risk
Unable to dynamically link to existing Prophet 21 customer using email address. This may result in duplicate customer records.
Description: While preparing a customer for transfer, the integration found an existing iPaaS.com customer that matches by email address but could not confirm the link between that record and the Prophet 21 customer. Continuing without a confirmed link could create a duplicate customer.
Resolution: Open the matching customer in iPaaS.com and confirm whether it already represents this Prophet 21 customer. If it does, the records can be linked so future syncs reuse it; if the email address is shared by genuinely different customers, correct the conflicting email so each customer is uniquely identifiable, then re-run the transfer. If the records appear correct and the error persists, contact iPaaS.com Support at support@ipaas.com.
Company To iPaaS
Duplicate company link risk
Unable to dynamically link to existing iPaaS Company using name. This may result in duplicate company records.
Description: The integration found an existing iPaaS.com company that matches by name but could not confirm the link to the incoming Prophet 21 company. Proceeding could create a duplicate company.
Resolution: Review the matching company in iPaaS.com to confirm it is the same organization. If two distinct companies share the same name, adjust the names so each is unique, then re-run the transfer. If the match is correct and the error continues, contact iPaaS.com Support at support@ipaas.com.
Duplicate customer link risk
Unable to dynamically link to existing iPaaS customer using customer number.
Description: While transferring a company, the integration tried to link the company's billing contact to an existing iPaaS.com customer by customer number but could not confirm the link.
Resolution: Verify that the customer number on the billing contact matches exactly one customer in iPaaS.com. Correct any mismatched or duplicated customer numbers, then re-run the transfer. If the value is correct and the error persists, contact iPaaS.com Support at support@ipaas.com.
Customer creation blocked
Unable to create or transfer customer. This will prevent the transfer of the company.
Description: The company being transferred requires its billing-contact customer to exist in iPaaS.com first, and that customer could not be created. Because the prerequisite failed, the company is not transferred.
Resolution: Check the Error Logs for an accompanying customer error from the same run — it usually explains why the customer could not be created (for example, missing required customer data). Resolve that underlying issue and re-run the transfer so the customer is created before the company. If no underlying cause is visible, contact iPaaS.com Support at support@ipaas.com.
Location To iPaaS
Duplicate location link risk
Unable to dynamically link to existing iPaaS Location using name. This may result in duplicate location records.
Description: The integration found an existing iPaaS.com location matching by name but could not confirm the link to the incoming Prophet 21 location, which could create a duplicate.
Resolution: Confirm in iPaaS.com whether the matching location is the same one. If distinct locations share a name, make the names unique and re-run the transfer. If the match is correct and the error persists, contact iPaaS.com Support at support@ipaas.com.
Product To iPaaS
Duplicate product link risk
Unable to dynamically link to existing iPaaS Product using Product No. This may result in duplicate product records.
Description: The integration found an existing iPaaS.com product matching by product number but could not confirm the link to the incoming Prophet 21 product, which could create a duplicate.
Resolution: Check the matching product in iPaaS.com to confirm it is the same item. If two different products share a product number, correct the numbers so each is unique, then re-run the transfer. If the match is correct and the error continues, contact iPaaS.com Support at support@ipaas.com.
Product creation blocked
Unable to create product. This will prevent the transfer of the product.
Description: The integration attempted to create the product in iPaaS.com as part of the transfer and the creation did not complete, so the product is not transferred.
Resolution: Review the Error Logs for a related product error in the same run that explains the cause (for example, a missing required field on the product mapping). Resolve that issue and re-run the transfer. If no underlying cause is visible, contact iPaaS.com Support at support@ipaas.com.
Product Inventory To iPaaS
Duplicate product inventory link risk
Unable to dynamically link to existing iPaaS Product Inventory using Product and Location Id. This may result in duplicate product records.
Description: The integration found existing iPaaS.com product inventory matching by product and location but could not confirm the link to the incoming Prophet 21 inventory record, which could create a duplicate.
Resolution: Confirm in iPaaS.com that the matching inventory record represents the same product-and-location combination. Correct any duplicated product or location identifiers, then re-run the transfer. If the records appear correct and the error persists, contact iPaaS.com Support at support@ipaas.com.
Transaction Add/Update From iPaaS
Duplicate SKUs on order lines
Order line items contain duplicate SKUs not allowed in Prophet 21: {duplicateSkus}
Description: The order being sent to Prophet 21 has the same SKU on more than one line item. Prophet 21 does not accept an order with duplicate line-item SKUs, so the transfer is stopped before the order is sent. The
{duplicateSkus}placeholder lists the SKUs that appear more than once.Resolution: Edit the source order so each SKU appears on a single line — combine the duplicated lines into one line with the correct total quantity — then re-run the transfer. This check is enforced by the mapping collection filter for this flow; subscribers or their MiSP who need to change how duplicates are handled can adjust that filter in the iPaaS.com UI.
Duplicate transaction link risk
Unable to dynamically link to existing Prophet 21 transaction using Invoice No. This may result in duplicate transaction records.
Description: The integration found an existing Prophet 21 transaction matching by invoice number but could not confirm the link to the iPaaS.com order, which could create a duplicate transaction.
Resolution: Confirm in Prophet 21 whether the matching transaction is the same order. If distinct orders share an invoice number, correct the numbering so each is unique, then re-run the transfer. If the match is correct and the error persists, contact iPaaS.com Support at support@ipaas.com.
Product not found in Prophet 21
Product not found in Prophet 21: The specified product does not exist or is unavailable in the Prophet 21 system.
Description: While building an order line, the integration looked up the order's product in Prophet 21 by SKU and found no matching, available product. The line cannot be created without a valid Prophet 21 product.
Resolution: Verify that the product exists in Prophet 21 and is active, and that the SKU on the iPaaS.com order matches the Prophet 21 product exactly — product matching is case-sensitive and exact. Create or activate the missing product in Prophet 21, or correct the SKU on the order, then re-run the transfer.
Order prerequisite blocked
Unable to create Company in Prophet 21. This will prevent the transfer of the order.
Unable to create Customer in Prophet 21. This will prevent the transfer of the order.
Unable to create product in Prophet 21. This will prevent the transfer of the order.
Description: Before an order can be transferred, its related company, customer, and products must exist in iPaaS.com. One of these prerequisites could not be created, so the order is not transferred. The message names which prerequisite failed.
Resolution: Look in the Error Logs for a related company, customer, or product error from the same run — it usually explains the underlying cause (for example, a missing required field). Resolve that issue so the prerequisite record can be created, then re-run the order transfer. If no underlying cause is visible, contact iPaaS.com Support at support@ipaas.com.
Transaction Line To iPaaS
Product not found in iPaaS.com
Product does not exist in iPaaS by Item Id: {ItemId}
Description: A transaction line references a product that has not yet been synchronized to iPaaS.com. The
{ItemId}placeholder shows the Prophet 21 item identifier that could not be found. The line is held until the product exists in iPaaS.com.Resolution: Make sure the product has been synchronized to iPaaS.com before its transaction lines — run the product sync first, then re-run the transaction line transfer. This check is enforced by the mapping collection filter for this flow; subscribers or their MiSP can adjust how missing products are handled by editing that filter in the iPaaS.com UI.
Transaction Tracking Number To iPaaS
Shipping method not found
Shipping Method {CarrierId} could not be found in iPaaS and must be manually created
Description: A tracking-number record references a shipping method (carrier) that does not exist in iPaaS.com. The
{CarrierId}placeholder shows the carrier name from the source record. The record is held until a matching shipping method exists.Resolution: Create the shipping method in iPaaS.com using the exact carrier name shown in the message — matching is by name, so it must match exactly — then re-run the transfer. This check is enforced by the mapping collection filter for this flow; subscribers or their MiSP can adjust how unmatched carriers are handled by editing that filter in the iPaaS.com UI.
Transaction Tracking From iPaaS
Transaction prerequisite blocked
Unable to create or transfer transaction in Prophet 21. This will prevent the transfer of the transaction tracking number.
Unable to create transaction. This will prevent the transfer of the Transaction Tracking Number.
Description: A tracking number can only be sent to Prophet 21 once its parent transaction exists there. The parent transaction could not be created or transferred, so the tracking number is not sent.
Resolution: Confirm the parent order transferred successfully, and check the Error Logs for a related transaction error from the same run that explains why it did not. Resolve that issue and re-run so the transaction is created before its tracking number. If no underlying cause is visible, contact iPaaS.com Support at support@ipaas.com.
Duplicate company link risk
Unable to dynamically link to existing Prophet 21 company using iPaaS customer email address. This may result in duplicate customer records in Prophet 21.
Description: While preparing the tracking-number transfer, the integration found an existing Prophet 21 company matching by the iPaaS.com customer's email address but could not confirm the link, which could create a duplicate customer in Prophet 21.
Resolution: Confirm in Prophet 21 whether the matching company is the same customer. If different customers share an email address, correct the conflicting email so each is uniquely identifiable, then re-run the transfer. If the match is correct and the error persists, contact iPaaS.com Support at support@ipaas.com.
Transaction Address From iPaaS
Duplicate customer address link risk
Unable to dynamically link to existing customer Address in Prophet 21 using iPaaS customer address. This may result in duplicate customer address records in Prophet 21.
Description: The integration found an existing Prophet 21 customer address matching the iPaaS.com customer address but could not confirm the link, which could create a duplicate address in Prophet 21.
Resolution: Review the matching address in Prophet 21 to confirm it is the same address. If genuinely different addresses appear identical, adjust them so each is distinguishable, then re-run the transfer. If the match is correct and the error persists, contact iPaaS.com Support at support@ipaas.com.
Prophet 21 platform errors
Some failures during a write into Prophet 21 surface the error text that Prophet 21 itself returns — for example, when Prophet 21 rejects an order or a related record. This text is passed through as the platform generates it and is not standardized in this article, so the exact wording you see in the Error Logs comes from Prophet 21.
Description: The integration sent a request to Prophet 21 and Prophet 21 returned an error. The message shown in the log is Prophet 21's own response and usually identifies the field or rule that was violated.
Resolution: Read the platform message in the log to identify what Prophet 21 rejected, correct the underlying data in iPaaS.com or in Prophet 21 (for example, a required field or an invalid value), and re-run the transfer. If the platform message is unclear or the failure recurs with valid data, contact iPaaS.com Support at support@ipaas.com.