Overview
This integration transfers Transaction Tracking Number records from Prophet 21 to iPaaS. The mapping transfers Prophet 21 Pick Ticket, Carrier, Tracking Number, and Freight Cost fields into the format required by iPaaS Transaction Tracking entities.
Mapping Collection Status
Mapping Status: Enabled.
Trigger Events: Create, Update.
ID Format
When manually transferring data from Prophet 21 to iPaaS, enter the Transaction Tracking Number ID in the iPaaS input field (for example, 2). The Prophet 21 Transaction Tracking Number ID is used directly without any suffix.
External ID Format: The carrierID|orderID serves as the external ID. For example: 155509|62679
Supported Child Collections
This integration does not support any child collections.
Duplicate and Conflicting Mappings
This mapping applies only to Transaction Tracking Numbers from Prophet 21. Ensure no other mappings target the same iPaaS Transaction Tracking entity to prevent data from being overwritten.
System Caveats
Prophet 21
Transaction Tracking NumberNo must be unique.
CarrierId must be a valid Prophet 21 shipping carrier.
iPaaS
ParentId must resolve to an existing iPaaS Transaction.
An incorrect or missing ShippingMethod will block tracking sync.
Setup Requirements
Prophet 21 Configuration
Ensure PickTicketNo, CarrierId, TrackingNo, and FreightOut are populated properly.
CarrierId values must match iPaaS Shipping Method names.
iPaaS Configuration
Shipping Methods must be created in advance.
Parent Transaction must exist for ParentId resolution.
Authentication & Security
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 processes Prophet 21 transaction tracking numbers as follows:
The integration is triggered when a Transaction Tracking Number is created or updated in Prophet 21.
The mapping filter verifies that the CarrierId exists as a Shipping Method in iPaaS.
Field and dynamic formula mappings are applied to transform Prophet 21 data.
The system validates that the parent Transaction exists in iPaaS.
The Transaction Tracking record is created or updated in iPaaS.
Mappings
Prophet 21 Transaction Tracking Number To iPaaS
Mapping Filter
string Id = await ShippingMethodIdFromName(CarrierId);
if (!string.IsNullOrEmpty(Id)){
return true;
}
else{
throw new Exception("Shipping Method "+CarrierId+" could not be found in iPaaS and must be manually created ");
}
Description
This filter checks whether the Carrier Id specified in the Prophet21 transaction tracking record exists in iPaaS as a Shipping Method name. If the Shipping Method is found, the record proceeds to transfer. If not found, the record is rejected with a custom error message indicating the Shipping Method must be manually created in iPaaS.
Mapping Type | Source (Prophet 21) | Destination (iPaaS.com) | Description |
Field | PickTicketNo | PickTicketNo (custom field) | Maps the Prophet 21 PickTicketNo to the iPaaS PickTicketNo custom field |
Dynamic Formula |
| ParentId | Retrieves the iPaaS Transaction ID by looking up the Prophet 21 InvoiceNo. Links the tracking number to its parent transaction. |
Field | CarrierId | ShippingMethod | Maps the Prophet 21 CarrierId to the iPaaS ShippingMethod. The CarrierId must match an existing Shipping Method name in iPaaS. |
Field | TrackingNo | TrackingNumber | Maps the Prophet 21 TrackingNo to the iPaaS TrackingNumber. |
Field | FreightOut | Cost | Maps the Prophet 21 FreightOut to the iPaaS Cost field. |
Error Handling Shipping Method Missing
Shipping Method Missing
Shipping Method {CarrierId} not found in iPaaS
Description: The CarrierId value from Prophet 21 does not match any existing Shipping Method name in iPaaS.
Resolution: Create the required Shipping Method in iPaaS with a name that exactly matches the Prophet 21 CarrierId value.
Parent Transaction Missing
ParentId could not be resolved
Description: The InvoiceNo from Prophet 21 does not match any existing Transaction in iPaaS.
Resolution: Ensure the related Transaction exists in iPaaS
Invalid CarrierId Format
CarrierId not acceptable or contains unsupported characters
Description: The CarriedId is formatted incorrectly.
Resolution: Correct the CarrierId value in Prophet 21 to use only supported characters.
Validation & Testing
Before deploying this integration, verify the following configuration items and run the test scenarios to confirm proper operation.
Validation Checklist
PickTicketNo is present and unique.
CarrierId matches an existing Shipping Method name in iPaaS.
TrackingNo is present.
Parent Transaction (InvoiceNo) exists in iPaaS.
FreightOut is a valid numeric value (if provided).
Shipping Method exists in iPaaS before syncing tracking numbers.
Test Scenarios
Scenario 1: Sync Valid Tracking Number
Create a Transaction Tracking Number in Prophet 21 with a valid PickTicketNo, CarrierId, TrackingNo, and FreightOut. Sync to iPaaS and verify the record appears with correct data mapped to all fields.
Scenario 2: Missing Shipping Method (Failure Case)
Attempt to sync a tracking number with a CarrierId that does not exist as a Shipping Method in iPaaS. Verify the error message is returned, indicating the Shipping Method must be manually created.
Scenario 3: Missing Parent Transaction (Failure Case)
Attempt to sync a tracking number where the InvoiceNo does not exist as a Transaction in iPaaS. Verify the sync fails with an appropriate error indicating ParentId could not be resolved.
Scenario 4: Update Existing Tracking Number
Update an existing Transaction Tracking Number in Prophet 21 (change TrackingNo or FreightOut). Sync to iPaaS and verify updates apply without creating duplicate records.
Additional Notes
Shipping Method must exist in iPaaS before syncing tracking numbers.
The CarrierId value must exactly match the Shipping Method name in iPaaS (case-sensitive).
Parent Transactions must be synced before their associated tracking numbers.