Integration and Prerequisites  

Objectives

After completing this lesson, you will be able to:

  • Integration and Prerequisites  

Integrating SAP Business Network Global Track and Trace

As of today, SAP Business Network Global Track and Trace supports the following B2B standards and corresponding messages:​

EDI/B2B Message StandardMessage TypeVersionDescription
EDIANSI 213V4010Motor Carrier Shipment Status Inquiry
EDIANSI 214V4010Shipment Status

To set up ANSI X12 integration, an SFTP connection needs to be configured in the System Connections app.​

Complete instructions can be found in the ANSI How to Guide forGlobal Track and Trace.

Prerequisites for ANSI X12 Integration​

To set up EDI integration with SAP Business Network Global Track and Trace, you must meet the following requirements: ​

  • Data contributor tenant is available in the test and productive environments. For more information, see theOnboarding (DataContributors) chapter in the Administration Guide for Version 2. ​

  • In case your SFTP server uses IP filtering, you need to add the IP ranges 155.56.128.0/17 and 130.214.160.64/28 to the allow list in order to enable Cloud Integration tenants to connect to your SFTP server. See also region Europe (Rot) in Regions and Hosts Available for the NeoEnvironment. Make sure that the SFTP server is accessible on the internet.​

  • It is expected that data contributors set up an SFTP server on their side for information exchange. Data contributors have to set up the SFTP connection once and solution owners can use the same SFTP connection for communication. Data contributors must enter a base64-encoded string of their SFTP server in the Known Host Key field of the System Connections app. See also Specifying theAuthentication Details and Base URLs for Your System’s Endpoints. ​

    The following diagram outlines the SFTP communication between the involved parties:​

Track the Progress of Orders and Releases (Global Track and Trace Option)​

This feature provides buyers the ability to receive tracking information in SAP Business Network for ship notices, using SAP Business Network for Logistics Global Track and Trace option.​

This feature navigates between SAP Business Network and corresponding information in the global track and trace option, for every ship notice in SAP Business Network. The feature also enables SAP Business Network to receive tracking events information for each document.​

Prerequisites for Tracking the Progress of Orders and Releases​

  • SAP Business Network integration using SAP Ariba Cloud Integration Gateway, add-on for SAP S/4HANA is set up. This integration enables SAP Business Network to send the corresponding inbound delivery number to SAP Business Network for Logistics Global Track and Trace option.​

  • SAP Business Network for Logistics Global Track and Trace option is enabled for your SAP Business Network account. For setup instructions, see Appendix Four: How to Set Up Global Track and Trace Integration for Ariba Network in Administration Guide for Version 2.​

Restrictions for Tracking Progress of Orders and Releases​

This feature supports only material purchase orders, scheduling agreements, and scheduling agreement releases. It does not support service orders or orders that have a mix of material and service items.​

Buyer User Interface Changes​

This feature adds multiple elements to SAP Business Network that enable buyers to access SAP Business Network for Logistics Global Track and Trace option information through the SAP Business Network user interface.​

Purchase Order Tracking Page

  • This feature provides two ways in SAP Business Network to access the global track and trace option:​

  • Go to a purchase order details page and choose the Track Order button. In the Purchase order tracking page that opens, go to the Tracking information table, locate the ship notice that you want to track, then in its row chooseView tracking detail in the Actions column.​

  • Go to a ship-notice details page and choose Track Ship Notice.​

  • In the Tracking information section, this feature adds the following functionality to the table of ship notices:​

  • The Estimated Arrival Date and Execution Status columns show this information when it is available for a ship notice. The feature retrieves this information from events from SAP Logistics Business Network, global track and trace option.​

  • A View tracking detail option is added to the dropdown in the Actions column. This option goes to SAP Business Network for Logistics Global Track and Trace option.​

Ship Notice Details Page​

  • After a ship notice is sent to the buyer system, this feature adds a Ship Notice Tracking section to the ship notice details page. This section shows the Execution Status and Estimated ArrivalDate provided by SAP Logistics Business Network, global track and trace option. If the ExecutionStatus is Delayed, the section also shows the Reason if a reason for the delay was given.​

  • This section also shows a Track Ship Notice button, which takes the buyer to SAP Business Network for Logistics Global Track and Trace option.​

Connectivity for SAP Business Network Material Traceability

The success of a material traceability network relies on the material genealogy data that’s contributed to it as well as the ability to retrieve data from the network.

We will discuss at a high level the following topics:

Creating Material Genealogy Data – Suitable for SAP Backend Systems

With an on-premise SAP S/4HANA or SAP ERP back-end system, you can contribute material genealogy data from these systems to a material traceability network.

To achieve this, you’ll need to complete the following setup consisting of three main steps:

  • Installing the add-on GBTRINT 100 to your SAP back-end system.
  • Connecting your SAP back-end system with the network.
  • Using the transactions installed by the GBTINT 100 add-on to specify the material genealogy data that will be contributed from your SAP back-end system to the network.

Before beginning, we recommend that you read about the supported ERP processes, restrictions, and the prerequisite setup in your SAP backend system. Additionally, for more information about the SOAP message that sends data between your SAP back-end system and the material traceability network, read the API documentation

The SAP Help Portalprovides the complete instructions for creating material genealogy.

Creating Material Genealogy Data - Suitable for non-SAP Backend Systems

If you have a non-SAP back-end system, that’s not a problem. You’ll need to create your own report that collects the relevant material genealogy data from your system. You’ll then need to create a message service that’s based on the material traceability API.

The SAP Help Portallists all available API endpoints for importing material genealogy data.

For more information about the API, read the API documentation at SAP API Business Hub. You will need client certificates as an authentication method.

Retrieving Material Genealogy Data

By calling /api/v1/attributequery you can retrieve the upstream material genealogy data of a product from the material traceability network's blockchain.

You can retrieve the upstream material genealogy data of a product by querying the attributes of the six types of supply chain events:

  • receive: product batch
  • receive: serialized product
  • produce: product batch
  • produce: serialized product
  • deliver: product batch
  • deliver: serialized product

By filtering on these attributes, you can retrieve specific product batch or serialized product information for verifying a product’s provenance.

To see how to structure the message query and to see an example response, read the API documentation at SAP API Business Hub as well as the quick tutorial in this admin guide: Tutorial – Retrieve Data.

Log in to track your progress & complete quizzes