Transitioning to Enhanced Tracking Solutions

Transitioning to Enhanced Tracking Solutions

SAP is making significant changes to its tracking services, affecting both the deprecation of several resource tracking services and the introduction of new features in the Order Events Provider API. These updates are critical for carriers, shippers, and other stakeholders in the logistics and supply chain ecosystem. Below, we discuss the implications of these changes and how to prepare for them.

Deprecation of Resource Tracking Services in SAP

Overview: SAP has announced the deprecation of several resource tracking services within the Configure Partner Connections app and System Connections app for carriers. This deprecation will take effect on August 17, 2024, and it is crucial for carriers and shippers to prepare for this change. 

Affected Resource Tracking Services: The following resource tracking services will be deprecated:

1. Resource Road Tracking  
   • FTL: Tracking full truckload (FTL) shipments on the road. 
   • LTL: Tracking less-than-truckload (LTL) road shipments. 

2. Resource Ocean Tracking 
   • FCL: Full container load (FCL) tracking for ocean freight. 
   • LCL: Less-than-container load (LCL) tracking for ocean shipments. 

3. Resource Tracking All: Comprehensive tracking service for all types of shipments.

4. Resource Tracking Parcel: Parcel tracking services.

These services have been essential for managing and tracking shipments across various modes of transportation. The removal of these services necessitates adjustments in logistics operations and tracking strategies.

Impact on Global Parcel Tracking

The deprecation will disrupt integration, reduce visibility, cause data fragmentation, increase manual effort in monitoring shipments, and impact customer satisfaction. 

Impact on Carriers and Shippers

1. Carriers: Will need to find alternative solutions for monitoring shipments, possibly integrating new tracking technologies or partnering with third-party logistics providers. 

2. Shippers: Must adapt to the loss of these tracking services, communicate with carriers about new tracking mechanisms, and ensure continued shipment visibility. 

Preparing for the Change

• Review current tracking systems. 

• Explore alternative tracking solutions. 

• Plan integration with new tracking systems or partners. 

• Communicate with logistics partners about the changes. 

New Updates in SAP Provider API for Order Events

Introduction: SAP continues to enhance its products, and the latest improvements to the Order Events Provider API are designed to improve the tracking experience. These updates are particularly impactful for Freight Collaboration (FC) and Global Track and Trace (GTT). 

Key Enhancements 

1. New Event Reason Code: “TRACKING_END” 
   A significant addition is the new event reason code “TRACKING_END”. This code signifies the end of tracking for a particular order, providing clear and definitive closure to the tracking process. This enhancement is crucial for stakeholders who need precise information about the conclusion of their tracking activities.

2. Boolean Field “isFinal”
   Another critical enhancement is the introduction of the Boolean field “isFinal” in the event object. This field helps in identifying whether a milestone event is the final reported event in the tracking sequence. By leveraging this feature, users can easily determine the completion status of an order’s tracking, facilitating more accurate and timely decision-making.

3. Support for rail transport mode  
   Expanding the range of supported transportation modes, the update now includes “02 – Rail transport”. This inclusion broadens the versatility of the API, catering to the needs of businesses that rely on rail transport. This enhancement ensures that users can seamlessly integrate rail transport data into their tracking systems, providing a more comprehensive view of their logistics operations.

4. TIFF File Support for Attachments 
   The update also introduces support for TIFF (Tagged Image File Format) files as attachments. Users can now upload TIFF files with either (.tif ) or (.tiff) extensions. This capability is particularly beneficial for industries that utilize high-quality image formats for documentation and record-keeping purposes. In addition to this, SAP Business Network Global Track and Trace allows users to upload TIFF files as attachments through the Write Service API, further enhancing the flexibility and utility of the platform.

Impact on Stakeholders

These enhancements are set to benefit various stakeholders in the logistics and supply chain ecosystem: 

1. Carriers can now ensure more accurate and comprehensive tracking of shipments, particularly with the ability to identify the final event in the tracking sequence. 

2. Data Contributors will find it easier to manage and share high-quality documentation, thanks to the support for TIFF file attachments. 

3. Shippers can leverage the new tracking capabilities to maintain better oversight of their shipments, ensuring that all tracking milestones are accounted for. 

4. Solution Owners can integrate these new features into their existing systems, enhancing the overall functionality and reliability of their logistics solutions.

Conclusion

The deprecation of resource tracking services in SAP’s Configure Partner Connections app and System Connections app, along with the new enhancements to the Order Events Provider API, mark significant changes for carriers and shippers. Effective from May 18, 2024, with complete removal by August 17, 2024, these changes require proactive steps to ensure continued efficiency and visibility in logistics operations. 

Stay informed and prepared by exploring alternative solutions and planning a smooth transition to maintain operational efficiency and shipment visibility in the dynamic world of logistics and supply chain.

Reference: SAP. ” Transitioning to Enhanced Tracking Solutions.” SAP User Assistance. Last modified May 18, 2024. (SAP Updates © 2024 SAP SE or an SAP affiliate company. All rights reserved)