
Cost distribution takes place in a freight order (FO), a freight booking (FB), or a freight settlement document (FSD). Posting of the distributed cost to SAP S/4HANA is done with the freight settlement document (FSD).
In the shipper scenario, the distribution level is set to ERP item (Order/ Delivery item). In the logistics service provider (LSP) scenario (for cost-based internal settlement), the distribution level is set to forwarding order.
Cost Distribution Steps
Cost distribution involves the following steps:
- Distribution of the freight costs at the level of delivery items based on some rules, such as Weight of the Delivery items. This step is executed in TM.
- Processing of the distributed freight costs in the financials for either processing the freight cost for material valuation or for expensing at the product level. This step is executed in the respective SAP S/4HANA modules.
For example, the inbound delivery freight cost is typically posted for material valuation. Outbound delivery costs are posted to cost objects or modules, such as CO-PA segments from the sales order, to calculate the profitability during sales order processing.
Freight Cost Posting via Settlement Management Integration
TM uses SAP S/4HANA's LO Settlement Management module for distributed freight cost posting.
Settlement Management provides a flexible posting engine where you can define the type of processing that is carried out from a financial processing perspective via customizing. TM uses this posting engine to hand over the distributed freight cost to SAP S/4HANA.
The Settlement Management document provides a documented way of posting distributed freight costs in SAP S/4HANA.
The Settlement Management document item created for TM freight cost postings has references to the following:
- Order and order item–sales order, purchase order, or stock transfer order and the corresponding item reference.
- Delivery and delivery item–Inbound or outbound delivery and the corresponding item references. During order and delivery integration processing, TM transfers these references.
- Service purchase order–The service purchase order (for freight cost), linked to the FSD integration with SAP MM.
- TM freight settlement document (FSD).
- TM freight order (FO).
Settlement Management provides native integration to financial functions, such as financial accounting, controlling, CO profitability analysis, material valuation, and material ledger. For example, based on a given reference document, you can specify that the freight cost processing will be posted to the material account.
Settlement documents do not create or update any accounts receivables or accounts payables. The document is used only for material adjustment postings to either expense general ledger (G/L) accounts or to material accounts.
Document Types in Freight Cost Posting
For posting freight costs, SAP LO Settlement Management uses the following document types:
- Settlement Document Generic: This document type enables you to post freight costs to material valuation.
- Settlement Process Type: This document type enables you to post freight costs to the G/L accounts.
Existing processes in Settlement Management and posting options are determined via use case types and document categories during mapping for cost distribution.
Customer Scenarios: Examples
The following are examples of customer scenarios:
SAP S/4HANA Integration
Transfer transportation cost as a delivery cost for the inbound material (material-level tracking).
The transportation cost flows to material valuation. The freight cost transfer as delivery cost is not updated in the purchase order of the material. The delivery cost posting is achieved via the posting carried out by the Settlement Management document.
Post the cost back to CO objects linked from order/delivery/material.
The material-relevant costs are tracked directly down to the CO objects from the transactions but more likely at an aggregated level, not necessarily at the material level. That is, there is no material valuation update. For example, all material-relevant costs, including indirect costs such as transportation, are tracked at the profit center level. Costs are segregated based on material movements (inbound, inter/intra, and customer deliveries).
Post cost back to the sales order /CO-PA responsible for the delivery (outbound scenario).
This scenario occurs on the seller's side. Costs associated with the sales order directly are tracked and have an impact on profitability analysis (CO-PA) segments.
Customer Scenario: Goods Calculation

In the example in the figure, we see how the final cost of a finished good is calculated.
Before the finished good leaves the factory, the material cost consists of different cost components, such as the cost of material and manufacturing overheads. In CO-PA, some other costs can be displayed, such as fixed costs based on material costs or depreciations, and so on.
In the case of a stock transfer order where finished goods are moved from the manufacturing plant to an external warehouse, a transportation cost is incurred. Cost distribution is required to assign this cost to the responsible material.
The material in the external warehouse is charged with the transportation costs based on a certain distribution key, such as weight or volume.
The scenario illustrates how the freight cost distribution functionality allocates the freight cost to the level of material and then processes the cost for material valuation. This is one example where the TM freight cost distribution functionality plays a role in allocating the freight cost to the level of material from the freight orders, before processing this cost information for material valuation.
From the example, you can extrapolate that the material cost valuation increased from $750 to $870, including the $120 actual transport cost from TM. This $120 represents the distributed cost for a given material in a transport. If the material valuation type is set to moving average, the cost increases upon receipt of the product. If the material valuation type is set to standard pricing the cost does not change until the next valuation run.
Freight Cost Distribution Process

- In LE, create a delivery.
- In TM, based on the delivery, freight units (FUs) are created in the background.
- The freight units are assigned to certain freight orders (FOs) or freight bookings (FBs) for subcontracting to a carrier (air/ocean/land) and charge calculation.
- In TM, create a freight settlement document (FSD) to post to SAP S/4 for invoicing and cost distribution.
- In TM, cost distribution occurs in the FSD based on certain distribution rules such as weight, volume, distance-times-weight, or a customer-specific rule such as the number of product pieces in an SD order item.
- Send the FSD containing all the freight costs and the distributed freight cost details to SAP S/4HANA. Here the following two process subsets are executed:
- The overall freight costs are posted to SAP Materials Management (MM) (step 6a in the figure) where a purchase order and a service entry sheet (SES) are created.
- The distributed freight costs from the FSD are transferred to the settlement management posting engine in SAP S/4HANA for posting to the responsible cost collector (step 6b in the figure). Based on information such as an SD order item, the settlement management distributes the cost to the appropriate cost object in Controlling or to CO-PA. In the case of inbound deliveries for purchase orders or stock transfer orders, the freight cost may be posted to material valuation and to different CO object-level cost centers, determined from the production order or stock transport order. This step takes place in the background. In SAP S/4HANA, you can monitor this event using transaction WLFLTM2 or the Fiori Launchpad and view the list of such freight cost documents.
- In MM, based on the purchase order with a service entry sheet (SES), an incoming carrier invoice is verified and posted using transaction MIRO. Any deviation in the verification creates a new Adjustment settlement management document for the difference. The adjustment document uses the same splitting logic as the original document for the planned costs coming from TM (See step 7a and step 7b in the figure).









