SAP Logistics Business Network connects those involved in the supply chain, allowing companies access to the information of all those they work with in a single location. This provides opportunity to find new business partners, gain greater transparency among logistics professionals, and more easily exchange business documents between parties.
Before going to the functional setting linking Shipper Tenant, Carrier Tenant and S/4 HANA TM, there are few connection which is mandatory and is pre- requisites for the Business Network for logistics to work.
Refer the the Link for the above setting
Refer the Link for the Connectivity setting
Once the Sub- Account creation with Shipper tenant has been created and connectivity with the SAP back end system has been done, Shipper LBN ID, Carrier LBN ID need to be obtained from the respective Shipper Tenant and the Carrier Tenant.
Choose the Carrier LBN ID which need to be linked with the given Shipper and log on to the Carrier Tenant of the respective LBN ID as shown in Fig1
Fig1: Log in to the carrier Tenant of the LBN ID
Go to the Manage Business Profile tiles in the carrier tenant and enable the following
Fig 2: Enable the Business Partner in the carrier tenant in Manage Business Profile tiles
Choose the Shipper Tenant for the given Shipper LBN ID and Choose the Discover Business Partners tab to discover the respective carrier LBN ID with which Shipper need to link
Fig 3: Discover Business Partners in shipper tenant
Searching the Carrier LBN ID in the shipper tenant. If the Business Profile of the carrie is not enable then Carrier LBN ID will not be visible in shipper tenant
Fig 4: Searching Carrier LBN ID in Shipper tenant.
Click “Request for connection” tab for accepting the carrier in Shipper tenant and since “Automatically accept connection requests” is enable in carrier tenant then automatically the connection will be established.
Fig 5: Carrier LBN ID connected to the Shipper LBN ID
Before assigning the carrier LBN ID to Carrier Business Partner, EDI communication profile need to be defined for Freight Order Specific Setting.
Path: IMG—>Transportation Management—-> Integration—->Enterprise Services—–> Define EDI communication Profile as shown in Fig 6
Fig 6: Shows the path to access Define EDI Communication Profile
In EDI Communication Profile we need to set the following
Fig 7: Setting Freight-Order-Specific Settings in EDI communication Profile.
Assign EDI Communication Profile and the Carrier LBN ID for the Carrier BP in S/4 HANA TM system using the Transaction Code BP.
In the BP select the BP role as carrier (CRM010), click Identification tab and assign EDI communication Profile under Transportation Management. Assign the Carrier LBN ID under Identification number with ID type LBN001 as shown in the Fig 8.
Fig 8: EDI communication Profile and the Carrier LBN ID assigned to the Carrier BP in S/4 HANA TM system.
Select the Purchase Organisation that is used for the given Freight Order (FO) and access it using the T.code PPOME in S/4 HANA TM system. Go to Organisation Data tab in the Purchase Organisation and note down the Business Partner Number as shown in Fig 9.
Fig 9: Identifying the Business Partner for the given Purchase Organisation
Open the Business Partner using obtained from the Purchase Organisation in T.code BP in S/4 HANA TM system with BP role as General (000000) and assign the Shipper LBN ID in the Identification Numbers with ID type LBN001 as shown in Fig 10
Fig 10: Assigning the Shipper LBN ID to the Business Partner of the respective Purchase Organisation used in Freight Order.
After all the above setting has been done along with the linking the Carrier LBN ID, Shipper LBN ID and the Business Partner in S/4 HANA TM system then we can run all the different scenario that is under the scope of Freight Collaboration.
Below is a demo of Subcontracting after we have done all the above setting in the systems.
LBN Subcontracting – SAP Media Share
For Transportation Management functional role, the Shipper LBN ID, Carrier LBN ID and the Business Partner in S/4 HANA TM system must be linked as explained in point 3.
This will help for all the different scenarios like Subcontracting, RFQ based tendering, Carrier Invoicing, Dispute Management and event triggering to work as a part of Logistics Business Network-Freight Collaboration, provided that the respective configuration for those scenario are in place in SAP S/4 HANA TM system.