Customer To iPaaS.com

Customer Address To iPaaS.com

Company To iPaaS.com

Location To iPaaS.com

Product To iPaaS.com

Product Inventory To iPaaS.com

Transaction To iPaaS.com

Transaction Line To iPaaS.com

Transaction Tracking Number To iPaaS.com

Transaction From iPaaS.com

Transaction Line From iPaaS.com

Customer Address From iPaaS.com

Transaction Address

Description: While preparing a customer for transfer, the integration found an existing record that matches by email address but could not confirm that it represents the same 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 the same email address is shared by genuinely different customers, correct the conflicting address so each customer is uniquely identifiable, then re-run the transfer.

Description: The integration requested a specific customer from Prophet 21 and Prophet 21 returned no record. This usually means the customer was deleted or renumbered in Prophet 21 after it was first synchronized, so the identifier iPaaS.com holds no longer resolves. The same message can appear during a company transfer, because a company transfer also retrieves its billing-contact customer.

Resolution: Look up the customer in Prophet 21 using the identifier shown alongside the error in the Error Logs. If the customer was deleted, remove or re-point the corresponding iPaaS.com record so the sync no longer requests it. If it was renumbered, re-run the customer sync so iPaaS.com picks up the current identifier.

Description: The integration requested a specific customer address from Prophet 21 and Prophet 21 returned no record. The address was most likely removed from the customer in Prophet 21 after it was first synchronized.

Resolution: Confirm in Prophet 21 whether the address still exists on the customer. If it was deleted intentionally, remove the corresponding address record in iPaaS.com. If it should exist, re-create it in Prophet 21 and re-run the customer sync so the address is picked up again.

Description: The integration found an existing iPaaS.com company that matches by name but could not confirm that it represents 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 a name, adjust the names so each is unique, then re-run the transfer.

Description: While transferring a company, the integration tried to link the company's billing contact to an existing iPaaS.com customer by customer number and could not confirm the match. Proceeding could create a duplicate customer.

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.

Description: A company can only be transferred once its billing-contact customer exists in iPaaS.com. That customer could not be created, so the company transfer stops before it begins.

Resolution: Check the Error Logs for a customer error recorded in the same run — it normally names the underlying cause, such as a required customer field that has no value. Resolve that issue so the customer can be created, then re-run the company transfer.

Description: The integration requested a specific company from Prophet 21 and Prophet 21 returned no record, typically because the company was deleted or renumbered in Prophet 21 after it was first synchronized.

Resolution: Look up the company in Prophet 21 using the identifier shown alongside the error in the Error Logs. If it was deleted, remove or re-point the corresponding iPaaS.com record. If it was renumbered, re-run the company sync so iPaaS.com picks up the current identifier.

Description: The integration found an existing iPaaS.com location matching by name but could not confirm that it represents 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, then re-run the transfer.

Description: The integration requested a specific location from Prophet 21 and Prophet 21 returned no record. The location was most likely deleted or deactivated in Prophet 21 after it was first synchronized.

Resolution: Confirm the location still exists in Prophet 21. If it was retired intentionally, remove or re-point the corresponding iPaaS.com location so the sync no longer requests it; otherwise restore it in Prophet 21 and re-run the transfer.

Description: The integration found an existing iPaaS.com product matching by product number but could not confirm that it represents the incoming Prophet 21 product, which could create a duplicate. The same message can appear during a product inventory transfer, because inventory records resolve their parent product the same way.

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.

Description: The integration found existing iPaaS.com product inventory matching by product and location but could not confirm that it represents 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.

Description: The integration requested a specific product from Prophet 21 and Prophet 21 returned no record, typically because the item was deleted or its item ID was changed in Prophet 21 after it was first synchronized.

Resolution: Look up the item in Prophet 21 using the identifier shown alongside the error in the Error Logs. If it was deleted, remove or re-point the corresponding iPaaS.com product. If its item ID changed, re-run the product sync so iPaaS.com picks up the current identifier.

Description: The integration attempted to create the product in iPaaS.com as part of the inventory transfer and the creation did not complete, so nothing is transferred.

Resolution: Review the Error Logs for a product error recorded in the same run — it normally explains the cause, such as a required field with no value in the product mapping. Resolve that issue and re-run the transfer.

Description: The integration requested a specific inventory record from Prophet 21 and Prophet 21 returned no record. This usually means the item was removed from that location in Prophet 21 after it was first synchronized.

Resolution: Confirm in Prophet 21 that the item is still stocked at the location shown alongside the error. If the combination was retired, remove the corresponding iPaaS.com inventory record; otherwise restore it in Prophet 21 and re-run the transfer.

Description: The integration found an existing transaction matching by invoice number but could not confirm that it represents the same 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.

Description: An order can only be transferred once its related company exists. The company could not be created, so the order is not transferred.

Resolution: Look in the Error Logs for a company error from the same run — it normally names the underlying cause, such as a required company field with no value. Resolve that issue so the company can be created, then re-run the order transfer.

Description: An order can only be transferred once its related customer exists. The customer could not be created, so the order is not transferred.

Resolution: Look in the Error Logs for a customer error from the same run — it normally names the underlying cause, such as a required customer field with no value. Resolve that issue so the customer can be created, then re-run the order transfer.

Description: An order can only be transferred once every product on its lines exists. One of those products could not be created, so the order is not transferred.

Resolution: Look in the Error Logs for a product error from the same run — it normally names the underlying cause, such as a required product field with no value. Resolve that issue so the product can be created, then re-run the order transfer.

Description: The integration requested a specific transaction from Prophet 21 and Prophet 21 returned no record, typically because the order was deleted or its invoice number was changed in Prophet 21 after it was first synchronized.

Resolution: Look up the order in Prophet 21 using the invoice number shown alongside the error in the Error Logs. If it was deleted, remove or re-point the corresponding iPaaS.com transaction. If the invoice number changed, re-run the transaction sync so iPaaS.com picks up the current value.

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: Run the product sync so the item reaches iPaaS.com, then re-run the transaction line transfer. If the product is intentionally excluded from iPaaS.com, you or your MiSP can change how missing products are handled by editing this mapping collection's filter in the iPaaS.com UI.

Description: The integration requested a specific transaction line from Prophet 21 and Prophet 21 returned no record. This usually means the line was removed from the order in Prophet 21 after it was first synchronized.

Resolution: Open the order in Prophet 21 and confirm whether the line still exists. If it was removed intentionally, remove the corresponding line in iPaaS.com; otherwise re-run the transaction sync so the order and its current lines are re-read together.

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 the value must match exactly — then re-run the transfer. If unmatched carriers should be handled differently, you or your MiSP can adjust this mapping collection's filter in the iPaaS.com UI.

Description: A tracking number can only be transferred once its parent transaction exists. 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 transaction error from the same run explaining why it did not. Resolve that issue and re-run so the transaction is in place before its tracking number.

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 carrying the correct total quantity — then re-run the transfer. If your business genuinely requires repeated SKUs on an order, you or your MiSP can change how duplicates are handled by editing this mapping collection's filter in the iPaaS.com UI.

Description: While preparing the transfer, the integration found an existing Prophet 21 company matching the iPaaS.com customer's email address but could not confirm the link, which could create a duplicate customer in Prophet 21. The same message can appear during a customer transfer from iPaaS.com, which resolves its company the same way.

Resolution: Confirm in Prophet 21 whether the matching company is the same customer. If different customers share an email address, correct the conflicting address so each is uniquely identifiable, then re-run the transfer.

Description: A tracking number requires its parent transaction to exist in Prophet 21. The integration attempted to create that transaction as a prerequisite and the creation did not complete, so the tracking number is not sent.

Resolution: Check the Error Logs for a transaction error from the same run — it normally explains why the order could not be created, such as a rejected field value. Resolve that issue and re-run so the transaction is created before its tracking number.

Description: The integration sent the order to Prophet 21 and Prophet 21 did not return a created order. Prophet 21 rejected the write, usually because a value on the order or one of its lines violates a Prophet 21 rule.

Resolution: Look for a Prophet 21 response recorded alongside this error in the Error Logs — it names the field or rule that was rejected. Correct that value on the iPaaS.com order, or adjust the corresponding record in Prophet 21, then re-run the transfer.

Description: The integration sent an update for an existing order to Prophet 21 and Prophet 21 did not return an updated order. This usually means a changed value violates a Prophet 21 rule, or the order has reached a status Prophet 21 no longer allows to be modified.

Resolution: Open the order in Prophet 21 and confirm it is still in a state that accepts changes. Review the Prophet 21 response recorded alongside this error in the Error Logs for the field or rule that was rejected, correct it, then re-run the transfer.

Description: While building an order line, the integration looked up the line's product in Prophet 21 by SKU and found no matching, available product. The line cannot be created without a valid Prophet 21 product. The same message appears when the line carries no SKU at all.

Resolution: Confirm the order line has a SKU, that a product with that exact SKU exists in Prophet 21, and that it is available — matching is exact, so differences in case or spacing will not resolve. Create or activate the product in Prophet 21, or correct the SKU on the iPaaS.com order, then re-run the transfer.

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.

Description: Something requested one transaction address record on its own. The integration transfers transaction addresses only as part of their parent transaction and cannot retrieve one independently, so the request fails.

Resolution: Re-run the transfer at the transaction level so the address moves with its parent order rather than on its own. If this error appears during a normal scheduled sync rather than a targeted single-record request, contact iPaaS.com Support at support@ipaas.com with the date, time, and mapping collection shown in the Error Logs.

Description: The integration called Prophet 21 and the call did not succeed. This single message covers every failed call to Prophet 21, in any flow: the request never reached Prophet 21, or Prophet 21 returned a failure. The {action} placeholder names the operation that was attempted, {details} carries the response Prophet 21 returned, and {status} is the HTTP status — shown by name, such as NotFound or Unauthorized, rather than as a number.

iPaaS.com <> Epicor Prophet 21: Background

Epicor Prophet 21 Installation Instructions

Epicor Prophet 21 Connections and Settings

Epicor Prophet 21 Mapping Functions

Epicor Prophet 21 API Endpoints

Epicor Prophet 21 Integration Known Limitations