Many shippers and carriers that have been using SAP Transportation Management have found value in leveraging the Carrier Collaboration Portal (CCP). The CCP is a web portal that provides easy to use functionalities between shippers and carriers such as: freight procurement, tendering, freight order execution, and freight settlement. However, as of TM stand-alone version 9.5 (released December 2017), no further enhancements are planned for the CCP. Instead, SAP is leveraging a new cloud-based tool called the Logistics Business Network (LBN).
What is the Logistics Business Network (LBN)?
The logistics business network is similar in many ways to the CCP. It provides the same functionality as the CCP such as freight procurement, tendering, etc. However, the main difference is the LBN runs entirely on the SAP Cloud Platform which leverages the leading cloud database, Amazon Web Services.
Credit: SAP Press- Introducing Transportation Management in SAP S/4HANA
Advantage of Logistics Business Network over Carrier Collaboration Portal
– Leverages integration with other SAP investments (S/4HANA, SAP Leonardo, SAP Ariba, SAP Global Track and Trace, etc.)
– Portal/Mobile access for all partners in the network
– Improved look and feel by using SAP Fiori UI
– Pre-delivered mapping of various EDI formats (ANSI, EDIFACT, etc) using the Descartes Global Logistics Network
Can I Use the LBN on a Stand-Alone TM System?
Yes – however, not all functionality will be supported and customers must be on a specific version of TM or higher to use certain functionalities. See below for a complete chart of the functionalities and the TM version that must be used.
| Functionality | System Release | Software Component | SP |
| Freight Tendering / Subcontracting | SAP TM 9.3 | SAPTM 140 | SP09 |
| SCM_BASIS 7.13 | SP16 | ||
| SAP TM 9.4 | SAPTM 150 | SP06 | |
| SCM_BASIS 7.14 | SP10 | ||
| SAP TM 9.5 | SAPTM 160 | SP01 | |
| SCM_BASIS 7.14 | SP10 | ||
| SAP TM 9.6 | SAPTM 170 | SP00 | |
| SCM_BASIS 7.14 | SP11 | ||
| TM in S/4HANA 1709 | S4CORE 102 | FPS02 | |
| On- Boarding | SAP TM 9.3 | SAPTM 140 | SP08 |
| SAP TM 9.4 | SAPTM 150 | SP06 | |
| SAP TM 9.5 | SAPTM 160 | SP01 | |
| TM in S/4HANA 1709 | S4CORE 102 | FPS02 | |
| Carrier Invoice | SAP TM 9.6 | SAPTM 170 | SP00 |
| SCM_BASIS 7.14 | SP11 | ||
| TM in S/4HANA 1809 | S4CORE 103 | FPS00 | |
| Self Billing without Dispute | SAP TM 9.3 | SAPTM 140 | SP09 |
| SCM_BASIS 7.13 | SP16 | ||
| SAP TM 9.4 | SAPTM 150 | SP06 | |
| SCM_BASIS 7.14 | SP10 | ||
| SAP TM 9.5 | SAPTM 160 | SP01 | |
| SCM_BASIS 7.14 | SP10 | ||
| TM in S/4HANA 1709 | S4CORE 102 | FPS02 | |
| SAP TM 9.6 | SAPTM 170 | SP00 | |
| SCM_BASIS 7.14 | SP11 | ||
| TM in S/4HANA 1809 | S4CORE 103 | FPS00 | |
| Freight Order for Reporting | TM in S/4 HANA 1809 | S4CORE 103 | FPS02 |
Next Steps for Carrier Collaboration Customers
Current customers using the Carrier Collaboration Portal should first consider migrating to S/4HANA with embedded TM. If that is not an option, then customers should consider migrating to the LBN.
New customers looking to implement SAP TM should strongly consider implementing SAP S/4HANA with embedded TM and leveraging the Logistics Business Network to fully optimize their supply chain. Contact Krypt today!
