Supply Chain Management Blog Posts by Members
cancel
Showing results for 
Search instead for 
Did you mean: 
Saurabh
Participant
1,716

<Note : Article has referred SAP Note 3065464>

Basic TM: More Power Under the Hood Than You Think

Don't underestimate the Basic Transportation Management (TM) license. Many assume it only handles simple, straight-line shipments, leading them to overlook its true value. In fact, Basic TM offers a robust foundation for complex logistics right out of the box.

You might be surprised by what's included without needing the Advanced license:

  • Complex Route Planning is fully supported. Basic TM handles both multi-pick and multi-drop scenarios for both incoming (inbound) and outgoing (outbound) deliveries.
  • The Critical Restriction: The only key limitation is that you cannot combine Freight Units from inbound and outbound deliveries onto the same Freight Order.
  • Core Execution and Settlement: It supports FSD creation , and generating PO/Service entry sheets.
  • GIS Integration: Direct external GIS hooks for geo-coordinates, distances, and durations—Basic only, no Advanced needed.
  • Unified Package Building (UPB): Auto-building via Packaging Specifications (PS) or Packing Instructions (PI)—basic supports.

A Single Process Step Can Trigger an Advanced License

Nuance is king. The line is indeed "pretty-thin," often hinging on one config or data choice. ( Refre SAP Note 3065464 )

  • Freight Unit Creation: Basic  supports deliveries only. Advanced required for direct from sales/purchase/stock transfer orders (early planning).
  • Freight Rate Tables: Basic limits to 3 scales/dimensions; 4+ scales need Advanced for granularity. Again it does not fullfill many customers wish list but a smart consultant can suggest alternative by following same restriction.
  • Charge Calculation: Be careful many calculation bases can not be used like: Holiday charges etc.
  • Schedules: Basic allows Schedules master data, but "cut-off dates" (e.g., for time windows) are Advanced-only.
  • Resource Management: Basic permits simple "Active Vehicle" in Freight Orders; full Resource objects (vehicles, trailers, drivers) are Advanced. This is really disappointing as my per my experience, it gives lot of pain while suggesting alternatives to client  to manage that .
  • Freight Forwarding: All core capabilities designed for LSPs are Advanced-only. This includes managing Forwarding Orders, Agreements, Settlements, and using Strategic Freight Procurement.
  • Modern Carrier Collaboration: The dedicated suite of Fiori apps for working directly with carriers—covering tendering, order confirmation, execution, and settlement—all require the Advanced TM license

Key Points: The Technical Traps

  • TM-EWM Integration (Advanced Shipping & Receiving - ASR):

Basic TM is allowed only if TM and EWM are embedded within the same S/4HANA system.If you deploy TM or EWM on a separate, decentralized server, the exact same integration instantly demands an Advanced TM license.

  • Side-by-Side Deployments:

The rule is strict: Any standard side-by-side deployment of S/4HANA TM with any other ERP system (ECC, another S/4HANA instance, or a third-party ERP) requires the Advanced TM license.

The exact same business process—integrating TM with an EWM warehouse—can be covered by your Basic license or require a costly Advanced license, based entirely on whether the systems are on the same server or different ones.

JUST THINK: A technical design decision, made without considering licensing knowledge, can lead to multi-million dollar software costs, even when the business process itself is simple.

 

Conclusion: Plan Before You Suggest your client

Choosing between Basic and Advanced Transportation Management is not a simple menu selection; it is a strategic decision that demands a meticulous review of your

  • end-to-end business processes,
  • charge calculation methodologies, 
  • long-term IT landscape strategy.

The line between the two is filled with subtleties that can be easily missed, and the wrong assumption can lead to unplanned costs or functional gaps down the road.

Before you make a final decision, you must map your non-negotiable business requirements against the detailed feature list, go through the notes.

Please share your experience – what strategies you applied during your implementation while being on Basic License.

2 Comments
Saurabh
Participant
0 Likes

@SAPEXPERTS:Does any one have clarity or on resource master data? Notes is pretty confusing, should we use resource in basic TM or not. It mentiones not to use resource with capacity ….

Ronald_Knienieder
Participant
0 Likes

Resources are not allowed in basic but you can use equipment types to create truck types with capacity (in SPRO)