MM / P2Pbeginner

MM Stock Transport Order Part 1: Moving Stock Between Plants with STOs

Key takeaway

A 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.

What this complete series covers

Learn Stock Transport Order in a clear, practical sequence — from the basic idea to real project use, troubleshooting, and interview-ready understanding.

Who it is for: Best for SAP consultants, developers, and learners who want a practical understanding of Stock Transport Order.
Prerequisites: Basic SAP S/4HANA navigation and an understanding of the business process are helpful. Configuration or transaction steps require suitable access to a practice or project system.
Final outcome: By the end, you should be able to explain Stock Transport Order clearly, follow the main end-to-end flow, apply it in a project scenario, and troubleshoot the most common issues.

Part 1: MM Stock Transport Order Part 1: Moving Stock Between Plants with STOs
Use delivery-based STO when transportation execution needs picking, packing, shipping point determination, PGI and warehouse integration before receiving-plant GR.
Part 2: MM Stock Transport Order Part 2: STO End to End — Configuration and Process
Understand STO as an internal procurement document that controls material transfer between plants with purchasing visibility, stock-in-transit handling and optional shipping/billing integration.
Part 3: MM Stock Transport Order Part 3: One-Step vs Two-Step and Stock in Transit
Choose one-step or two-step transfer based on physical handoff, transit visibility and organizational control, understanding when stock in transit exists between issue and receipt.
Part 4: MM Stock Transport Order Part 4: Intercompany STO — Billing and FI Integration
Understand cross-company STO as both a logistics transfer and an intercompany commercial process requiring billing, valuation and company-code financial postings.
Part 5: MM Stock Transport Order Part 5: Troubleshooting STOs — Shipping Data, ATP, Delivery, GR and Valuation
Use a fixed evidence sequence for STO failures: organizational data, source stock and ATP, delivery relevance, shipping execution, PGI, in-transit quantity, GR and financial valuation.

System and release assumptions: Examples focus on SAP S/4HANA. Exact apps, transaction codes, configuration paths, and field names can vary by release and deployment model.

Explanation

📌 KEY POINTS
✅ An STO plans and documents plant-to-plant transfers: requirement at receiving plant, supply from supplying plant.
✅ Intra-company STO usually uses document type UB (item category U); cross-company STO often NB with delivery and billing.
✅ With delivery: outbound delivery (VL10B/VL10x), picking, GI at supplying plant, GR at receiving plant.
✅ Two-step (641 + 101) shows stock in transit; one-step (647) posts GI and GR together.
⚠️ Using transfer postings for planned inter-plant flows loses MRP visibility, shipping and tracking.

━━━━━━━━━━━━━━━━━━━━
▶ WHAT THIS SERIES COVERS
Part 1: Moving stock with STOs
Part 2: STO end to end
Part 3: One-step vs two-step and stock in transit
Part 4: Intercompany STO billing and FI
Part 5: Troubleshooting STOs

━━━━━━━━━━━━━━━━━━━━
▶ 1. WHY STO

MRP-driven replenishment between plants, shipping, tracking, valuation control.

━━━━━━━━━━━━━━━━━━━━
▶ 2. VARIANTS

Without delivery (GI with MIGO 351) vs with delivery.
Intra-company (UB) vs cross-company (NB + billing).

━━━━━━━━━━━━━━━━━━━━
▶ 3. DOCUMENTS

STO → outbound delivery → GI → (billing for cross-company) → GR.

━━━━━━━━━━━━━━━━━━━━
▶ 4. MOVEMENT TYPES

351/641 to stock in transit, 101 GR; 643/645 cross-company; 647 one-step.\n\n━━━━━━━━━━━━━━━━━━━━\n▶ 5. MRP\n• Special procurement key for stock transfer; STO requisitions from MRP.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Create a UB STO from plant 1000 to 1100.
Create delivery in VL10B and post GI.
Post GR at plant 1100.

✅ CHECKPOINT: STO history shows GI and GR; stock moved between plants.

Code example

ABAP Code

===== STEP 1: create =====ME21N: document type UB, supplying plant 1000, receiving plant 1100, material, quantity ===== STEP 2: delivery and GI =====VL10B → outbound delivery (NL) → picking → PGI 641 (stock in transit) ===== STEP 3: GR =====MIGO 101 at receiving plant with reference to STO/delivery | MB5T stock in transit

Real project scenario

A distributor moved stock between warehouses with 301 transfer postings. MRP at receiving plants didn't see in-transit supply, and nothing tracked shipments. Switching to UB STOs with deliveries gave MRP visibility, shipping documents and transit monitoring.

Common mistakes

Transfer postings instead of STOs.
Wrong document type for cross-company.
No delivery where shipping is needed.
Not monitoring stock in transit.
Missing special procurement keys.

Best practices

Use STOs for planned transfers.
Choose variant by process needs.
Monitor transit.
Configure MRP special procurement.
Train on document flow.

Interview angle

Questions: "What is an STO?", "One-step vs two-step?", "Intra- vs cross-company STO?"
Strong answer: purpose, variants, documents, movement types, MRP integration.

Practice this lesson

Quick check

1. Which transaction is typically used to create outbound deliveries for STOs?

2. A team proposes using 301 transfer postings for all planned plant-to-plant replenishments. What is lost compared with STOs?

3. Which document type is typically used for intra-company STOs?

Interview questions

1. A distributor moves stock between its warehouses with transfer postings. When would you recommend STOs and which variant?

Answer it in your own words first, then compare.

2. What is a Stock Transport Order (STO), and how does source determination differ for an STO compared to a standard third-party purchase order?