Overview
This integration transfers Company records from the Prophet 21 Customer entity to the iPaaS Company entity. The integration uses an API-based sync that triggers whenever a customer record is created or updated in Prophet 21. This mapping ensures that Customer (Company in iPaaS) data remains consistent and up to date across both systems.
Mapping Collection Status
Mapping Status: Enabled.
Trigger Events: Create, Update.
ID Format
When manually transferring data from Prophet 21 to iPaaS, enter the Prophet 21 Customer ID in the iPaaS input field (for example, 12345). The Prophet 21 Customer ID is used directly without any suffix.
Duplicate and Conflicting Mappings
This mapping applies only to Companies from Prophet 21. Ensure no other mappings target the same iPaaS Company entity to prevent data from being overwritten.
Supported Child Collections
This parent mapping collection supports the following child collections:
Epicor Prophet 21 Add Company Address TO iPaaS.com
Epicor Prophet 21 Add Company Relationship TO iPaaS.com
System Caveats
Prophet 21 Caveats
The Customer" entity is used as the source for iPaaS Company.
iPaaS Caveats
Company Name must be unique or follow business rules.
Company records may require at least one address and one related contact.
RelatedToId must resolve correctly using dynamic lookup formulas.
Setup Requirements
Prophet 21 Configuration
Customer (Company) records must have a valid CustomerName.
iPaaS Configuration
The company module must be enabled.
Referenced Company IDs must exist for relationship mappings.
Authentication & Security
Epicor Prophet 21 uses username and password authentication to access the iPaaS API. These credentials authorize all Prophet 21 API requests during transfer operations.
Integration Flow
The integration is triggered when a Customer is created or updated in Prophet 21.
Customer data is fetched from Prophet 21.
Field values are validated (CustomerName, ArAccountNo, Tax fields).
Field and dynamic formula mappings are applied to populate iPaaS Company fields.
Child collections (Address and Relationship) are processed.
The Company and related entities are created or updated in iPaaS.
Sync results are logged for troubleshooting.
Mappings
Parent: Prophet 21 Add Company TO iPaaS.com(Parent)
Description
This mapping collection transfers customer data from Prophet 21 to iPaaS as Company records.
Mapping Type | Source Field (Prophet 21) | Destination Field (iPaaS.com) | Description |
Field | ArAccountNo | AccountNumber | Maps the Prophet 21 ArAccountNo to the iPaaS AccountNumber. |
Field | FederalExemptionNumber | TaxIdNumber | Maps the Prophet 21 FederalExemptionNumber to the iPaaS TaxIdNumber. |
Field | CustomerName | Name | Maps the Prophet 21 CustomerName to the iPaaS Company Name. This is a required field. |
Child: Prophet 21 Add Company Address TO iPaaS.com
Description
This mapping collection transfers address data from Prophet 21 customers to iPaaS Company addresses.
Mapping Type | Source Field (Prophet 21) | Destination Field (iPaaS.com) | Description |
Field | MailAddress1 | Address1 | Maps the Prophet 21 MailAddress1 to the iPaaS Address1. |
Field | MailAddress2 | Address2 | Maps the Prophet 21 MailAddress2 to the iPaaS Address2. |
Field | MailAddress3 | Address3 | Maps the Prophet 21 MailAddress3 to the iPaaS Address3. |
Field | MailCity | City | Maps the Prophet 21 MailCity to the iPaaS City. |
Field | MailState | Region | Maps the Prophet 21 MailState to the iPaaS Region. |
Field | MailCountry | Country | Maps the Prophet 21 MailCountry to the iPaaS Country. |
Field | MailPostalCode | PostalCode | Maps the Prophet 21 MailPostalCode to the iPaaS PostalCode. |
Field | IsPrimaryBilling | IsPrimarysBilling | Maps the Prophet 21 IsPrimaryBilling flag to iPaaS. |
Field | IsPrimaryShipping | IsPrimaryShipping | Maps the Prophet 21 IsPrimaryShipping flag to iPaaS. |
Child: Prophet 21 Add Company Relationship TO iPaaS.com
Description
This mapping collection transfers contact/relationship data from Prophet 21 customers to iPaaS Company Relationships.
Mapping Type | Source Field (Prophet 21) | Destination Field (iPaaS.com) | Description |
Field | EmailAddress | Email (custom field) | Maps the Prophet 21 EmailAddress to the iPaaS Email custom field. |
Field | FirstName | First Name (custom field) | Maps the Prophet 21 FirstName to the iPaaS First Name custom field. |
Field | LastName | Last Name (custom field) | Maps the Prophet 21 LastName to the iPaaS Last Name custom field. |
Static | SuperUser | Types | Sets the iPaaS Types to the static value SuperUser. |
Dynamic Formula |
| RelatedToId | Retrieves the iPaaS Company ID by looking up the Prophet 21 Customer ID. Links the relationship to its parent company. |
Error Handling
Missing Company Name
CustomerName is empty.
Description: The CustomerName field is required but was not provided from Prophet 21.
Resolution: Populate CustomerName in Prophet 21 before syncing.
AccountNumber Missing
ArAccountNo is required for iPaaS AccountNumber.
Description: The ArAccountNo field is expected for the iPaaS AccountNumber but was not provided.
Resolution: Ensure Prophet 21 Customer has a valid AR Account Number.
Failed RelatedToId Lookup
Dynamic lookup for RelatedToId returned null.
Description: The parent Company could not be found in iPaaS when resolving the RelatedToId.
Resolution: Ensure the parent Company exists in iPaaS before syncing relationships, or verify the mapping rules are correct.
Validation Rules & Testing
Validation Checklist
CustomerName is present and not empty.
ArAccountNo is unique and non-empty (if required).
Address fields meet minimum requirements.
Relationship emails are valid format.
Parent Company exists in iPaaS for relationship mappings.
Company Name follows iPaaS naming rules to prevent duplicates.
Test Scenarios
Scenario 1: New Company Sync
Create a new Customer in Prophet 21 with CustomerName, ArAccountNo, and address fields populated. Sync to iPaaS and verify the Company appears with correct data.
Scenario 2: Update Company Info
Modify the CustomerName or FederalExemptionNumber in Prophet 21. Sync to iPaaS and verify changes are reflected without creating duplicates.
Scenario 3: Add Address
Update the customer address fields in Prophet 21. Sync to iPaaS and verify the address is updated correctly in the Company record.
Scenario 4: Relationship Sync
Add a new contact (with FirstName, LastName, EmailAddress) in Prophet 21. Sync to iPaaS and verify the contact appears as a Company Relationship.
Scenario 5: Invalid Lookup (Failure Case)
Remove the parent Company from iPaaS and attempt to sync a relationship. Verify the RelatedToId error is triggered and logged appropriately.
Scenario 6: Missing Required Field (Failure Case)
Attempt to sync a Customer without a CustomerName. Verify an appropriate error message appears and the sync is prevented.
Additional Notes
Ensure Company names follow iPaaS naming rules to prevent duplicates.
The Prophet 21 Customer entity maps to the iPaaS Company entity.
Parent Company records must exist in iPaaS before syncing relationships that reference them.
Address and Relationship child collections are processed after the parent Company is created.