Overview
This integration transfers Transaction Tracking Number records from iPaaS to Prophet 21. The integration supports the creation and update of tracking number data in Prophet 21 based on changes made within the iPaaS Transaction Tracking Number entity. This ensures both platforms maintain consistent and accurate tracking information.
Mapping Collection Status
Mapping Status: Enabled.
Trigger Events: Create, Update.
ID Format
When manually transferring data from iPaaS.com to Prophet 21, enter the iPaaS Transaction ID, followed by a pipe (|), and then the Tracking Number ID in the input field (for example, 149049|10001).
External ID Format: The carrierID|orderID serves as the external ID. For example: 155509|62679.
Duplicate or Conflicting Mappings
This mapping applies only to Transaction Tracking Numbers from iPaaS.com. Ensure no other mappings target the same Prophet 21 tracking entity to prevent data from being overwritten.
Supported Child Collections
This integration does not support any child collections.
System Caveats
iPaaS Caveats
TrackingNumber must be present before sync.
ShippingMethod must match the Prophet 21 CarrierId values.
Prophet 21 Caveats
CarrierId must be a valid, pre-configured shipping method.
Incorrect or invalid tracking numbers may be rejected.
Setup Requirements
iPaaS Configuration
Ensure fields pick_ticket_no, ShippingMethod, TrackingNumber, and Cost are properly populated before syncing.
Ensure Tracking Number Collection is enabled.
Prophet 21 Configuration
Shipping Method (CarrierId) must exist in Prophet 21 before tracking can be added.
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 is triggered when a Transaction Tracking Number is created or updated in iPaaS, or manually initiated.
Tracking number data is fetched from iPaaS.
The PickTicketNo is validated to ensure it exists in Prophet 21.
The ShippingMethod is validated against the Prophet 21 CarrierId list.
Field mappings are applied to transform iPaaS data.
The tracking entry is created or updated in Prophet 21 with the carrier, tracking number, and freight cost.
Mappings
Transaction Tracking Number From iPaaS.com
Mapping Type | Source Field (iPaaS.com) | Destination Field (Prophet 21) | Description |
Field | pick_ticket_no | PickTicketNo | Maps the iPaaS pick_ticket_no custom field to the Prophet 21 PickTicketNo. The pick ticket must exist in Prophet 21. |
Field | ShippingMethod | CarrierId | Maps the iPaaS ShippingMethod to the Prophet 21 CarrierId. Must match a valid carrier in Prophet 21. |
Field | TrackingNumber | TrackingNo | Maps the iPaaS TrackingNumber to the Prophet 21 TrackingNo. This is a required field. |
Field | Cost | FreightOut | Maps the iPaaS Cost to the Prophet 21 FreightOut. |
Error Handling
Missing Pick Ticket
PickTicketNo is missing or invalid
Description: Prophet 21 cannot attach tracking without a valid pick ticket
Resolution: Provide a valid pick_ticket_no that exists in Prophet 21
Invalid Shipping Method
ShippingMethod does not match Prophet 21 CarrierId list
Description: The carrier cannot be resolved in Prophet 21. The ShippingMethod value must exactly match a configured CarrierId.
Resolution: Ensure ShippingMethod exists in Prophet 21, or update the value in iPaaS to match a valid CarrierId.
Missing Tracking Number
TrackingNumber cannot be null or empty
Description: Prophet 21 requires a valid tracking number for the shipment entry
Resolution: Add a tracking number in iPaaS before syncing.
Validation & Testing
Before deploying this integration, verify the following configuration items and run the test scenarios to confirm proper operation.
Validation Checklist
PickTicketNo matches an existing Prophet 21 order.
CarrierId is valid in Prophet 21.
TrackingNumber is present and correctly formatted.
FreightOut is a valid numeric value (if provided).
ShippingMethod exists in the Prophet 21 carrier list.
Test Scenarios
Scenario 1: Add New Tracking Number
Create a new Transaction Tracking Number in iPaaS with a valid pick_ticket_no, ShippingMethod, TrackingNumber, and Cost. Sync to Prophet 21 and verify a shipment tracking entry is created with the correct carrier, number, and cost.
Scenario 2: Update Tracking Number
Modify the TrackingNumber for an existing record in iPaaS. Sync to Prophet 21 and verify the tracking number updates correctly without creating a duplicate entry.
Scenario 3: Invalid Carrier (Failure Case)
Use an incorrect ShippingMethod that does not exist in Prophet 21. Attempt to sync and verify that error handling is triggered with an appropriate message.
Scenario 4: Missing Pick Ticket (Failure Case)
Attempt to sync tracking with an invalid or missing pick_ticket_no. Verify the system returns an appropriate error indicating the pick ticket is required.
Scenario 5: Missing Tracking Number (Failure Case)
Attempt to sync with an empty TrackingNumber field. Verify the system returns an error indicating tracking number is required.
Additional Notes
This mapping supports standalone execution, independent of full Transaction mapping.