MM_P2Pbeginner
Stock Transport Order
Master Stock Transport Orders from plant-to-plant demand through shipping, goods issue, stock in transit, goods receipt and intercompany billing where applicable. Compare one-step, two-step and delivery-based variants and learn to troubleshoot the full document chain.
Overview
Master Stock Transport Orders from plant-to-plant demand through shipping, goods issue, stock in transit, goods receipt and intercompany billing where applicable. Compare one-step, two-step and delivery-based variants and learn to troubleshoot the full document chain.
Lessons in this topic
- MM Stock Transport Order Part 1: Moving Stock Between Plants with STOsA stock transport order (STO) is a purchasing document for transferring stock from a supplying plant to a receiving plant. Learn when to use STOs instead of simple transfer postings, the variants (without delivery, with delivery, one-step, two-step, intra- and cross-company), and the documents involved.
- MM Stock Transport Order Part 2: STO End to End — Configuration and ProcessConfigure and run STOs with delivery: shipping data for plants (supplying plant sales area, receiving plant as customer), delivery type and checking rule per document type and supplying plant, ATP at supplying plant, MRP special procurement key, delivery creation, GI, GR and monitoring.
- MM Stock Transport Order Part 3: One-Step vs Two-Step and Stock in TransitChoose between one-step and two-step STOs: one-step posts GI and GR simultaneously, two-step posts GI into stock in transit and GR later; valuation of stock in transit, visibility, lost or damaged shipments, and monitoring.
- MM Stock Transport Order Part 4: Intercompany STO — Billing and FI IntegrationCross-company transfers: STO document type (e.g. NB) with delivery type NLCC, supplying company code as seller, intercompany billing (e.g. IV) to the receiving company, supplier invoice in the receiving company (manual or automatic via IDoc), pricing, valuation and reconciliation.
- MM Stock Transport Order Part 5: Troubleshooting STOs — Shipping Data, ATP, Delivery, GR and ValuationDiagnose STO issues: no delivery created, ATP not confirming, delivery blocked, GR not possible, stock stuck in transit, valuation or GR/IR differences, and billing problems for cross-company STOs — with a structured checklist.
Interview questions covered
- In designing document type configuration for cross-plant Stock Transport Orders (STOs), what settings govern whether a delivery-based or invoice-based (intercompany billing) process is used, and how do these choices affect the downstream FI-AP and FI-AR postings?
- A cross-company stock transport order has goods sitting in stock-in-transit for over 45 days. The receiving plant's physical inventory count excludes this quantity by design, but the FI-GL trial balance shows a stock-in-transit account balance that does not match the MM transit quantity report (e.g., MB5T). As the architect, how would you troubleshoot this reconciliation gap between MM and FI-GL?
- Your organization is implementing intercompany stock transport orders where goods sit in stock-in-transit for several weeks between plants. How would you design valuation classes and account determination to correctly reflect stock-in-transit value separately from unrestricted stock in each plant's balance sheet?
- A cross-company stock transport order (STO) between two plants in different company codes is not generating the expected intercompany invoice, and goods receipt at the receiving plant is posting without a corresponding FI document. How would you diagnose and correct the document type and pricing setup?
- During period-end close, your controller reports that stock-in-transit values for inter-company STOs are causing physical inventory count discrepancies and the closing balances do not reconcile between the issuing and receiving plants. How would you investigate and structure a resolution?
- What is a Stock Transport Order (STO), and how does source determination differ for an STO compared to a standard third-party purchase order?
- In a global template rollout, a client wants to use Stock Transport Orders (STOs) for intercompany services procurement where a service plant fulfills maintenance requests for another plant under a different company code. What architecture considerations apply?
- STOs for a new plant can be saved, but no deliveries are created and MRP doesn't generate STO requisitions. What do you configure?
- A cross-company STO process shows GR/IR differences and late supplier invoices. How do you design intercompany STO billing and FI integration?
- A distributor moves stock between its warehouses with transfer postings. When would you recommend STOs and which variant?
- Finance complains about stock in transit that never clears, while logistics wants transit visibility. How do you design one-step vs two-step STOs?
- A receiving plant cannot post GR for STOs and some STOs never get deliveries. How do you troubleshoot?
Related topics
MM_P2P
S/4HANA MM Transformation, Ariba, Migration, Public Cloud and Architecture
MM_P2P
Invoice Verification, GR/IR, Integration and Production Support
MM_P2P
Procurement and End-to-End Procure-to-Pay
MM_P2P
Inventory Management, Valuation, Material Ledger and Account Determination
MM_P2P
MM Foundation, Enterprise Structure and Master Data
MM_P2P
Enterprise Structure