In this blog post, I would like to give an overview of API and EDI integration options to support new shippers and carriers as well as our partners in implementing SAP Business Network for Logistics solutions. (I am using the phrase carrier here for simplicity, but also mean any other business partner in logistics including freight forwarders or data contributors such as visibility providers.)
The blog is structured into the following sections:
Introduction to SAP Business Network for Logistics
Let me set the scene and briefly explain what SAP Business Network for Logistics is about and introduce you to the processes it supports.
It is a cloud service with global coverage, specifically built to connect shippers with carriers. The network enables collaboration across companies fast and easily breaking up siloed operations, manage freight more efficiently and leverage situational awareness for eased decision making.
There are two major solutions: SAP Business Network Freight Collaboration and SAP Business Network Global Track and Trace. Together, they cover the end-to-end process from:
Collaboration and the Network
Shippers usually already have a backend system such as SAP S/4HANA, SAP Transportation Management or a non-SAP system to manage their transport operations, for example create sales orders, plan freight etc.
As to collaborate with the carrier, some of the shipper’s operational data needs to be shared – and vice versa –the carrier’s input needs to be shared with the shipper and potentially be synchronized with the backend system. With SAP Business Network for Logistics, we provide a reliable and secure platform to share transport-related information.
For example, a shipper plans to ship break components for a bike to another company for assembly of the bikes. The transport has been planned in the shipper’s transportation management system. Next, the shipper sends the respective Freight Order for Confirmation to the carrier. The carrier confirms the order and can add or change details such as price proposal, name of the driver, license plate, … The shipper’s transportation management system is updated accordingly. This scenario requires the shipper’s backend system and SAP Business Network for Logistics to be integrated. For carriers, we support all process steps with web portal applications, but for automated operations carriers may alternatively leverage API or EDI.
Architecture and therefore means of integration are different for SAP Business Network Freight Collaboration and SAP Business Network Global Track and Trace, therefore let’s look at each of them individually.
SAP Business Network Freight Collaboration
Scenarios supported through API or EDI in SAP Business Network Freight Collaboration
On the left side of the below diagram, you see different scenarios for integration with shipper backend systems.
There is out-of-the-box integration with SAP S/4HANA, SAP Transportation Management and SAP Yard Logistics for contracting, execution and settlement as per SAP Notes 2620322, 2753223 and 2764922. The SAP Notes utilize our public SOAP API but provide a plug and play approach. There is also out-of-the-box integration with SAP Yard Logistics for dock appointment scheduling (a cookbook is available for additional integration scenarios).
When integrating with non-SAP systems, public SOAP API may also be used. And finally, when integrating with SAP ECC, IDocs are used.
On the right side of the diagram, you see how carriers can integrate with SAP Business Network for Logistics. We support all process steps with web portal applications for carriers, but for automated operations, carriers might decide to leverage public REST API to integrate to their backend systems or communicate through EDI standards.
Overview of available public API and EDI in SAP Business Network Freight Collaboration
As you have learned so far, SAP Business Network for Logistics supports different collaboration processes between shipper and carrier. The network enables collaboration as it helps exchange relevant information between the involved business partners. In the above chapter, I have outlined integration via API. However, you may also leverage global standards to exchange data electronically, e.g. via EDI.
The below graphic gives an overview of API and EDI we currently support.
Not illustrated in the graphic is that we also support acknowledgement of successful transfer of EDI message (EDI 997) for inbound messages i.e. EDI 990, 301, 210 and 214.
Please note that we constantly extend our product capabilities, and more API and EDI will become available over time. Therefore, please regularly check our roadmap and documentation.
SAP Business Network Global Track and Trace
Scenarios supported through API or EDI in SAP Business Network Global Track and Trace
SAP Business Network Global Track and Trace supports process monitoring with out-of-the-box visibility connectivity, exception management and impact analysis.
Before getting into the tracking itself, solution owners (which usually are the shippers) need to setup synchronization of business object information, documents, and milestones. For example, a solution owner might define that the following milestones shall be tracked for its sales order fulfillment: goods issue, delay, delivery, quality inspection, goods receipt. Milestones and tracked process are different from customer to customer. Therefore, there are no standard API here, but API are generated by the customer to write or read information from SAP Business Network Global Track and Trace.
Overview of available public API and EDI in SAP Business Network Global Track and Trace
For the operational process of tracking, there are standard API (see graphic below). There is a ‘Provider API to update track process’ and a ‘Consumer API for Order Tracking’ that notifies the carrier about a new or updated tracking request.
As an alternative to connecting via API, carriers may also integrate using standard EDI 213 and 214.
Not illustrated in the graphic is that we also support acknowledgement of successful transfer of EDI message (EDI 997) for inbound message 214.
Please note that we constantly extend our product capabilities, and more API and EDI will become available over time. Therefore, please regularly check our roadmap and documentation.
-----------------
Highly recommended! Also read my colleagues bogs on:
SAP Business Network For Logistics – Carrier Side Integration – API vs EDI
SAP Business Network For Logistics – Road EDI Integration Tips and Tricks
To learn more about SAP Business Network for Logistics visit SAP - Business Network for Logistics.
For further questions and feedback related to the blog, please check the Q&A area and feel free to post your questions in the link with the tag SAP Business Network for Logistics.
The blog is structured into the following sections:
- Introduction to SAP Business Network for Logistics
- Collaboration and the Network
- SAP Business Network Freight Collaboration
- Scenarios supported through API or EDI in SAP Business Network Freight Collaboration
- Overview of available public API and EDI in SAP Business Network Freight Collaboration
- SAP Business Network Global Track and Trace
- Scenarios supported through API or EDI in SAP Business Network Global Track and Trace
- Overview of available public API and EDI in SAP Business Network Global Track and Trace
Introduction to SAP Business Network for Logistics
Let me set the scene and briefly explain what SAP Business Network for Logistics is about and introduce you to the processes it supports.
It is a cloud service with global coverage, specifically built to connect shippers with carriers. The network enables collaboration across companies fast and easily breaking up siloed operations, manage freight more efficiently and leverage situational awareness for eased decision making.
There are two major solutions: SAP Business Network Freight Collaboration and SAP Business Network Global Track and Trace. Together, they cover the end-to-end process from:
- Contracting and quotes to
- Dock appointment scheduling and gate processing,
- Execution and event reporting to
- Settlement, including invoicing and dispute management.
Supported processes in SAP Business Network for Logistics
Collaboration and the Network
Shippers usually already have a backend system such as SAP S/4HANA, SAP Transportation Management or a non-SAP system to manage their transport operations, for example create sales orders, plan freight etc.
As to collaborate with the carrier, some of the shipper’s operational data needs to be shared – and vice versa –the carrier’s input needs to be shared with the shipper and potentially be synchronized with the backend system. With SAP Business Network for Logistics, we provide a reliable and secure platform to share transport-related information.
For example, a shipper plans to ship break components for a bike to another company for assembly of the bikes. The transport has been planned in the shipper’s transportation management system. Next, the shipper sends the respective Freight Order for Confirmation to the carrier. The carrier confirms the order and can add or change details such as price proposal, name of the driver, license plate, … The shipper’s transportation management system is updated accordingly. This scenario requires the shipper’s backend system and SAP Business Network for Logistics to be integrated. For carriers, we support all process steps with web portal applications, but for automated operations carriers may alternatively leverage API or EDI.
Architecture and therefore means of integration are different for SAP Business Network Freight Collaboration and SAP Business Network Global Track and Trace, therefore let’s look at each of them individually.
SAP Business Network Freight Collaboration
Scenarios supported through API or EDI in SAP Business Network Freight Collaboration
On the left side of the below diagram, you see different scenarios for integration with shipper backend systems.
There is out-of-the-box integration with SAP S/4HANA, SAP Transportation Management and SAP Yard Logistics for contracting, execution and settlement as per SAP Notes 2620322, 2753223 and 2764922. The SAP Notes utilize our public SOAP API but provide a plug and play approach. There is also out-of-the-box integration with SAP Yard Logistics for dock appointment scheduling (a cookbook is available for additional integration scenarios).
When integrating with non-SAP systems, public SOAP API may also be used. And finally, when integrating with SAP ECC, IDocs are used.
On the right side of the diagram, you see how carriers can integrate with SAP Business Network for Logistics. We support all process steps with web portal applications for carriers, but for automated operations, carriers might decide to leverage public REST API to integrate to their backend systems or communicate through EDI standards.
Overview of available public API and EDI in SAP Business Network Freight Collaboration
As you have learned so far, SAP Business Network for Logistics supports different collaboration processes between shipper and carrier. The network enables collaboration as it helps exchange relevant information between the involved business partners. In the above chapter, I have outlined integration via API. However, you may also leverage global standards to exchange data electronically, e.g. via EDI.
The below graphic gives an overview of API and EDI we currently support.
Not illustrated in the graphic is that we also support acknowledgement of successful transfer of EDI message (EDI 997) for inbound messages i.e. EDI 990, 301, 210 and 214.
Public API and EDI in SAP Business Network Freight Collaboration
Please note that we constantly extend our product capabilities, and more API and EDI will become available over time. Therefore, please regularly check our roadmap and documentation.
SAP Business Network Global Track and Trace
Scenarios supported through API or EDI in SAP Business Network Global Track and Trace
SAP Business Network Global Track and Trace supports process monitoring with out-of-the-box visibility connectivity, exception management and impact analysis.
Before getting into the tracking itself, solution owners (which usually are the shippers) need to setup synchronization of business object information, documents, and milestones. For example, a solution owner might define that the following milestones shall be tracked for its sales order fulfillment: goods issue, delay, delivery, quality inspection, goods receipt. Milestones and tracked process are different from customer to customer. Therefore, there are no standard API here, but API are generated by the customer to write or read information from SAP Business Network Global Track and Trace.
Overview of available public API and EDI in SAP Business Network Global Track and Trace
For the operational process of tracking, there are standard API (see graphic below). There is a ‘Provider API to update track process’ and a ‘Consumer API for Order Tracking’ that notifies the carrier about a new or updated tracking request.
As an alternative to connecting via API, carriers may also integrate using standard EDI 213 and 214.
Not illustrated in the graphic is that we also support acknowledgement of successful transfer of EDI message (EDI 997) for inbound message 214.
Public API and EDI in SAP Business Network Global Track and Trace
Please note that we constantly extend our product capabilities, and more API and EDI will become available over time. Therefore, please regularly check our roadmap and documentation.
-----------------
Highly recommended! Also read my colleagues bogs on:
SAP Business Network For Logistics – Carrier Side Integration – API vs EDI
SAP Business Network For Logistics – Road EDI Integration Tips and Tricks
To learn more about SAP Business Network for Logistics visit SAP - Business Network for Logistics.
For further questions and feedback related to the blog, please check the Q&A area and feel free to post your questions in the link with the tag SAP Business Network for Logistics.
- SAP Managed Tags:
4 Comments
| User | Count |
|---|---|
| 6 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
