Skip to Content
Product Information

LSP Scenario in embedded Transportation Management of S/4HANA 1809 Release

SAP Standalone Transportation management ( TM) provides functionalities for both Shipper (like Ericsson , Nestle) and LSP – Logistic service provider (like DHL , Panalpina) . TM was embedded in S/4HANA core in 1709 release and it used to support only Shipper scenario as stated in one of my previous blogs https://blogs.sap.com/2017/09/12/advantages-of-sap-tm-being-embedded-in-1709-release-of-s4hana/.  Note that LE-TRA of ECC does not support LSP scenario

Embedded TM of S/4HANA 1809 release now supports LSP scenario and this feature of LSP scenario in embedded TM can be also considered as one of the advantages of embedded TM w.r.t LE-TRA of ECC. There are some Shipper companies who have a group company to take care of all transportation activities of the main Shipper company, so this LSP scenario can also be used by the Transportation unit of the Shipper company.

Typical scenarios for Shipper and LSP in embedded TM of S/4HANA 1809 release have been depicted in below image.

LSP scenario generally starts with a Forwarding order. Freight units can be created automatically from Forwarding order based on the transportation requirement .LSP also can subcontract the transportation to another company and can create Freight order (or Freight booking) similar to Shipper scenario. LSP scenario can have two separate charge calculations

  • Charge calculation on Forwarding order: Freight charges are calculated based on the Forwarding agreement (FWA) of LSP with their customer (a Shipper company like Ericsson, Nestle).
  • Charge calculation on Freight order or freight booking: Freight charges are calculated on the freight order (or freight booking) based on the Freight agreement (FA) of the LSP with their subcontractors (or carriers).

Similarly, LSP scenario can have two separate settlements

  • Forwarding settlement document (FWSD): It is created with freight charges calculated based on the Forwarding agreement (FWA) and is used to create the Billing document to the Customer of LSP.

If the LSP unit belongs to a Shipper organisation , then this settlement will create a                              Intracompany settlement document if the Shipper & LSP unit belong to the same company                  code and can be posted to specific Cost element or cost center or internal order. If the                        Shipper  and LSP unit belong to different company codes , then this settlement will create                  Inter company billing document.

  • Freight settlement document (FSD) : It is created with freight charges calculated based on the Freight agreement (FA) with subcontractor and is used to create Purchase order & Service entry sheet

Document for a typical Forwarding order is in below image

Note that there is no Agency business document (ABD) or Supplier billing document in LSP scenario as there is no need to allocate the freight cost to originating logistic document like Sales order or delivery or Material valuation. However, Profitability can be calculated in LSP scenario, if required.

Forwarding order is also used in Shipper scenario like in case of ‘Transit warehousing’ as described in one of my blogs in link https://blogs.sap.com/2018/07/27/transit-warehousing-with-embedded-tm-and-ewm-in-s4hana-1709-release/

Also like to highlight that the use of LSP scenario in embedded TM of S/4HANA requires additional license i.e LSP scenario is not covered under ‘Basic TM’ of S/4HANA.

5 Comments
You must be Logged on to comment or reply to a post.