Applies to Product - Dynamics 365 Supply Chain Management
What’s happening?
The customer is facing a change in the parcel shipping API integration with UPS, which is transitioning from XML to a SOAP API requiring a different payload format.
Reason:
The underlying cause of this is the requirement from UPS to change the data format for shipping requests and responses from XML to a new payload format.
The underlying cause of this is the requirement from UPS to change the data format for shipping requests and responses from XML to a new payload format.
Resolution:
To utilize the new integration for the Parcel Shipping (SPS) API change, follow these steps: 1. Prepare Your System: Ensure that the SPS feature is turned on in the Feature management workspace. This feature is mandatory from Supply version 10.0.29 and cannot be turned off. 2. Develop and Deploy Rate Engines: Collaborate with your carrier or carrier hub service to develop a rate engine. This rate engine will enable the system to submit details about packed containers to your carrier and receive a shipping label, shipping rate, and tracking number in return. A demo rate engine is provided for testing purposes. 3. Configure Transportation Management: Set up the Transportation management and parcel management modules to support the SPS feature, including adding the rate engine to your system. 4. Integration Adjustments: Update the configuration to handle the new payload format instead of XML. Ensure that the interface can parse and display the new data correctly, and modify any validation rules or data processing logic to accommodate the new format. 5. Utilize Out of the Box Classes: For building the new payload for the integration, utilize classes designed to handle the new data format. Examples include deserializing into instances using plugin services or libraries.
To utilize the new integration for the Parcel Shipping (SPS) API change, follow these steps: 1. Prepare Your System: Ensure that the SPS feature is turned on in the Feature management workspace. This feature is mandatory from Supply version 10.0.29 and cannot be turned off. 2. Develop and Deploy Rate Engines: Collaborate with your carrier or carrier hub service to develop a rate engine. This rate engine will enable the system to submit details about packed containers to your carrier and receive a shipping label, shipping rate, and tracking number in return. A demo rate engine is provided for testing purposes. 3. Configure Transportation Management: Set up the Transportation management and parcel management modules to support the SPS feature, including adding the rate engine to your system. 4. Integration Adjustments: Update the configuration to handle the new payload format instead of XML. Ensure that the interface can parse and display the new data correctly, and modify any validation rules or data processing logic to accommodate the new format. 5. Utilize Out of the Box Classes: For building the new payload for the integration, utilize classes designed to handle the new data format. Examples include deserializing into instances using plugin services or libraries.