Landed cost in SAP MM: planned and unplanned delivery costs
landed cost in sap mm
Also searched as
- sap mm planned delivery costs
- sap mm unplanned delivery costs
- freight and duty cost in purchase order sap
Short answer
SAP MM handles landed cost through delivery cost conditions. Planned delivery costs are conditions on the purchase order (flagged as delivery costs) that are accrued at goods receipt and settled with the freight invoice. Unplanned delivery costs are entered in MIRO when the invoice arrives. How they hit inventory value depends on the price control of the material.
Applies to: SAP ECC 6.0 and S/4HANA on-premise; newer S/4HANA releases also offer extended landed cost functions
Set up and post landed cost for a purchase
- 1Decide which costs are landed: freight, insurance, customs duty, handling. Create or reuse condition types such as FRA1 or FRB1 for freight in the purchasing calculation schema, and mark delivery cost condition types appropriately in customizing.
- 2In the purchase order (ME21N), add the delivery cost condition on the item conditions tab, or maintain it in the vendor info record, so it is planned.
- 3Post the goods receipt in MIGO. The material is valued at purchase price plus the planned delivery cost under moving average price (V), with a GR/IR credit for the planned amount.
- 4When the vendor invoice for the goods arrives, post it in MIRO. Match the goods price against the receipt.
- 5For a separate freight or duty invoice from another vendor, post it in MIRO with reference to the same PO using the delivery cost vendor and the planned cost item.
- 6If the cost was not planned, use the unplanned delivery costs option in MIRO and choose to allocate it to the material or distribute it across items.
- 7Review the valuation and the GR/IR account with MR11 or the GR/IR reports; confirm the stock value and price difference postings.
Planned versus unplanned delivery costs
Planned delivery costs are known when you create the order. They are conditions on the item, accrued at goods receipt, so inventory is valued at the full landed price from the start. When the freight invoice is posted, it clears the accrual, and any difference between plan and actual becomes a price difference or is adjusted into stock depending on valuation.
Unplanned delivery costs arrive on the invoice without a PO condition. In MIRO you can add them on the unplanned delivery costs tab and choose whether they are distributed to the items by quantity or value. They are posted to the material or to an account depending on the settings in invoice verification customizing.
Effect on valuation: standard versus moving average price
For a material with moving average price, delivery costs increase the stock value and thereby change the price. For standard price, the delivery cost does not alter the standard price; the difference goes to a price difference account, and the variance shows up in the period. This is why finance and purchasing should agree early whether landed cost is capitalised into the price or expensed through variances.
The accounting entries are driven by transaction keys in automatic account determination (OBYC): BSX for the stock account, WRX for GR/IR clearing, PRD or UMB for price differences, and FR1 or FRL for freight provision in the standard keys. Confirm the exact keys with your finance configuration because they are often customised.
OBYC transaction keys (typical): BSX stock, WRX GR/IR, PRD price difference, FR1 freight provision, FR2 freight clearing
MIRO: Details > Unplanned delivery costs tab; Planned delivery costs: post a separate invoice referencing the PO
Import duty and customs
For imports, duty is often posted as a separate invoice from a customs broker and referenced to the purchase order as a delivery cost. If your process requires exact duty per shipment, build the duty as its own condition type and keep the broker as a separate vendor on the item, so the cost can be settled independently of the goods vendor.
Where you need a full cost build-up across many shipments, SAP provides extended landed cost functionality in newer S/4HANA releases that works with the import process. Check the release documentation and whether it is licensed and activated before designing around it.
Try it here, free
SAP MM Transaction Codes Reference
Searchable list of the SAP MM transaction codes consultants and buyers use daily, grouped by purchasing, inventory, invoice verification and MRP.
Common pitfalls
- !Booking freight directly to an expense account and bypassing inventory, which understates cost of goods.
- !Using standard price and expecting freight to raise the price.
- !Posting freight against the wrong PO item, which misstates GR/IR for that line.
- !Leaving a planned cost on the PO that never gets invoiced, leaving an open GR/IR balance.
- !Assuming OBYC keys are standard without checking your configuration.
How an ERP-grounded AI assistant handles this
A grounded assistant can read PO conditions, goods receipt documents and open GR/IR items and explain where a freight cost went, which items are carrying an uninvoiced accrual and how much price difference a material built up. It queries your SAP data on-prem, read-only, and leaves any correction postings to finance users.
Frequently asked questions
What is the difference between planned and unplanned delivery costs?
Planned delivery costs are conditions on the purchase order and are accrued at goods receipt. Unplanned delivery costs appear first on the invoice and are entered during invoice verification in MIRO. Both can be allocated to the material value.
Does freight change the standard price?
No. With standard price the delivery cost is not added to the price. The difference goes to a price difference account. Under moving average price, delivery costs increase the stock value and change the average price.
How do I post a separate freight invoice in SAP?
Use MIRO and reference the purchase order, selecting the delivery cost item when the cost was planned. If it was not planned, use the unplanned delivery costs option and allocate the amount to the items on the invoice.
Is there a landed cost transaction in SAP?
Classic MM has no single landed cost transaction; it is built from conditions and invoice verification. Newer S/4HANA releases include dedicated landed cost functionality, which depends on release and activation.
Related
SAP MM price determination: pricing procedure, condition types and fixing wrong PO prices
In SAP MM the purchase price comes from condition records, read in the order set by the calculation schema (standard RM0000), which the system assigns using the purchasing organization, vendor schema group and plant. PB00 is the gross price condition type. A wrong price in ME21N is usually a missing or outdated info record or condition, or the wrong schema.
How-toSAP GR/IR clearing account balance: reconcile with MB5S and clear with MR11
The GR/IR clearing account holds the value of goods received but not yet invoiced, and invoices not yet matched with receipts. It should trend to zero per PO item. Reconcile it with MB5S, find the PO items that are stuck, and clear true differences with MR11 or automatic clearing in F.13, after correcting the cause.
How-toSAP MIRO: invoice blocked for price variance, and how to release it in MRBR
MIRO blocks an invoice for payment when its price or quantity differs from the PO or goods receipt by more than the tolerance limits defined in OMR6. The invoice posts, but it carries a payment block reason (R for price) until someone releases it in MRBR or corrects the underlying data. Release only after confirming which side is wrong.
How-toDynamics 365 Supply Chain Landed Cost: Voyages, Charges and Allocation
Landed cost in Dynamics 365 Supply Chain Management lets you add freight, duty, insurance and similar costs to the inventory cost of imported goods. You group purchase lines into a voyage, attach shipping containers, add costs from charges codes, and the system allocates those costs back to the received items so item cost reflects the true cost to land them.
Error fixSAP M7 021: Deficit of SL Stock Quantity
M7 021 fires during a goods issue, delivery, or confirmation when SAP checks the unrestricted-use (SL) stock for the exact plant, storage location and batch combination and finds less than what you are trying to post out. Fix the entry (batch, storage location, quantity) first; only enable negative stock or downgrade the message to a warning if the business genuinely needs to post ahead of a receipt.
Error fixSAP IDoc Status 51: Application Document Not Posted
Status 51 tells you the IDoc reached the application layer and failed to post, but the status text itself is not the error - the real cause sits in the status record's long text or the linked application log. Fix the underlying data or configuration, then reprocess the IDoc through BD87 rather than editing the status.
AI for ERPAI for SAP S/4HANA, Running On-Prem or in Your Private Cloud
Run AI on SAP S/4HANA without sending ERP data to a public API. On-prem and private-cloud architecture, CDS views, OData, and honest deployment trade-offs.
Stuck on SAP ECC / S/4HANA?
Talk to engineers who work inside SAP ECC / S/4HANA every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
ERP fixes and how-tos
- Freight Cost in SAP MM: Planned and Unplanned Delivery CostsHow to handle inbound freight in SAP MM: planned delivery costs on the PO, freight condition types, unplanned costs in MIRO, and the GR/IR and stock impact.
- Pricing Procedure in SAP MM, with a Worked PO ExampleHow the SAP MM purchasing pricing procedure works: condition types, calculation schema, schema determination, a worked PO and how freight is captured.