Technical Transcript
The ecosystem of SAP Transportation Management (TM) involves multiple organizational units and business partners. Understanding who does what is the foundation of system configuration.
Core Business Partners
In SAP TM, a "Player" is technically defined as a Business Partner (BP) assigned to specific roles. The system relies on these roles to route freight orders and calculate settlements.
- Shipper: The organization requesting the transportation of goods.
- Logistics Service Provider (LSP): The entity managing the transportation on behalf of the shipper.
- Carrier: The actual physical transporter of the goods (e.g., a trucking company or airline).
In the BOPF (Business Object Processing Framework) structure, Business Partners are linked directly to the /SCMTMS/TOR (Transportation Order) root node. The system validates the BP roles before allowing a Freight Order to be saved.
Organizational Units
You cannot assign a Carrier to a Freight Order if your internal organizational units are not mapped correctly to the SAP ECC or S/4HANA core structure.
You must define:
- Purchasing Organization: Responsible for negotiating freight rates with Carriers.
- Planning and Execution Organization: Responsible for the actual routing and execution of the freight units.
Never delete an Organizational Unit in a production environment if it has historical Freight Orders attached to it. It will corrupt your forwarding settlement documents.
Configuration Check
Before moving to the next module, verify that your Business Partner roles are active. You can test this by running a simple background query in your system.
Always verify the BP role CRM010 (Carrier) is extended to your target Purchasing Organization, otherwise your freight agreement calculations will fail silently.