How to Track SAP TM Shipments using BN4L GTT and Visibility Provider?

In today's fast-paced environment, maintaining a robust and transparent supply chain is crucial for staying competitive in the market. Achieving supply chain goals requires building effective strategies and ensuring resilience. These objectives can be met by leveraging technology and providing real-time data to customers and suppliers. 

SAP has made significant advancements in supply chain management, transforming businesses with cutting-edge technology and IoT to enhance customer experiences. One notable development is the Global Track and Trace under SAP Business Network for Logistics (BNL). For more details on BN4L GTT, please find the attached link below. 

https://help.sap.com/docs/business-network-global-track-and-trace  

SAP BNL enables logistics end-users involving carrier and shippers to collaborate effectively, facilitating communication between users and providing real-time data inputs. It integrates seamlessly with cross-functional modules like SAP ERP, SAP TM, and SAP IBP, enhancing overall efficiency in track and trace. 

At SCMYUGA my recent project experience with SAP BNL GTT involved working in a shipper scenario with SAP TM. In this project, freight bookings and Freight orders were sent to GTT for tracking based on container IDs or truck plate numbers. These IDs and plate numbers were communicated to a visibility provider, which then supplied tracking updates to GTT. Through this blog, I wanted to share some basic and mandatory data points which will ensure your shipments tracking is successful with GTT and visibility provider. 

Below are the sequence of steps that cover the technical configuration, data prerequisites, and troubleshooting of some common integration errors.

Disclaimer: All screenshots are from the SCMYUGA internal demo system and are shared for demonstration purposes only.

Step-1:

Under FB/FO type configuration maintain execution settings for relevant Freight Orders and Freight Bookings types in SPRO. Also ensure application object type is assigned. 

Step-2:

Import ABAP code from GitHub. 

Install ABAPGit. To install, follow the instruction on https://docs.abapgit.org/guide-install.html 

Step-3:

Activate PI-EM Integration using Tcode FIBF. 

Step-4:

Create RFC Connection (Transaction SM59) for sending tracking requests from TM to GTT (Messages inbound to GTT) 

Step-5:

Define logical system in SPRO transaction 

Step-6:

Under ‘Define CI Tenant for SAP GTT’ in SPRO map the logical system created in previous step. 

Step-7:

Define Ports under IDoc settings for GTT. 

Step-8: 

Define partner profiles under IDoc settings for GTT 

• Assign Logical system in partner profile. 

• Assign ports in partner profile. 

• Define IDOC type in partner profile. 

Step-9:

SOAMANAGER  

Under Web Service Configuration (Transaction SOAMANAGER), service binding to be created for standard service definition /SCMTMS/TPEVTBNTFI. This is done to update the tracking updates from GTT to respective Freight documents in TM. 

Step-10:

Create API or EDI Connections to Carriers or LSP’s or visibility provider under ‘Configure partner Connections’ in GTT.  

Using ‘Discover Business Partners’ app, you can identify a partner with whom the integration needs to be setup for tracking updates. A connection request can be sent to the partner and the partner needs to approve it. 

Step-11: 

In BTP under sub account where SAP BNL GTT is subscribed, create a destination that points to TM System. 

Step-12:

Below are critical fields in Freight Booking / Freight Order that are expected to be maintained for successful tracking with BNL GTT. 

1. Carrier along with SCAC code 

2. Source Location & Destination Location 

3. Planned Departure / Arrival Dates  

4. Shipping Type (FCL / FTL) 

5. Tracking Identifier (Container ID or Truck LP)  

6. Carrier Reference document no (BL No, Booking Number)  

Step-13: 

Set Execution status to ‘Ready for Transportation Execution’ in TM Freight Order/Booking. 

Step-14:

Shipment is sent to GTT through IDOCS. Shipment is seen in GTT with FB/FO Number. 

If in case shipment is not found in GTT check for errors as below:  

1. IDOC transmission using Tcode WE05 in TM. 

2. In GTT Check View logs à Manage Message logs  

Step-15:

Verify Integration logs in View Logs  

Here we can view the logs for data exchange between GTT to Visibility provider/Carriers. Tracking request is initiated from GTT to Visibility provider/Carriers in return the tracking updates are received from visibility provider to GTT.  

Step -16:

Verify Event Logs in View logs 

For any event updates from visibility provider/carrier or manual event updates, event logs will show whether the events are processed successfully in GTT.  

Step 17:

Verify Event Updates in SAP TM Freight documents. 

Once an event is reported in GTT, the update is forwarded to destination maintained in SAP BTP cockpit(Refer Step 11). The event updates can be seen in Execution tab of Freight documents. 

In case, the event update is missing the respective error logs can be seen in transaction SRT_MONI in TM. 

Hope my blog has given you insights into the bare minimum setup required for tracking TM shipments. Stay tuned for more such articles and your feedback will be valuable. 

Author: Ambareesh Vemuri 

Designation: Associate consultant at SCMYuga Technologies Pvt Ltd.  

For more details contact@scmyuga.com