Scenario 7 — Intra-Company STO (Karachi → Lahore)
📊 Business Case — When & Why You Use This
An intra-company Stock Transport Order (STO) moves material between two plants of the same company code using a formal PO document (Doc Type UB). Unlike a quick storage-location transfer (311), an STO gives you a tracked, approvable document, optional delivery/shipping, and a proper paper trail for stock crossing plant boundaries — all without any vendor invoice, because both plants belong to one legal entity.
🕐 When to use it
One plant has surplus stock another plant needs — e.g. PakSteel Karachi has 20 TO of finished rebars and Lahore has demand. You want a tracked transfer with delivery/transit visibility, not an untracked shelf move.
❓ Why it matters
It is the controlled way to balance stock across plants. The UB PO supports approval, scheduling, in-transit tracking, and (optionally) SD delivery — far more than a plain 311/301 transfer posting can offer.
👤 Who triggers it
The receiving plant's planner/storekeeper raises the STO; the supplying plant's storekeeper issues the goods; in the SD-integrated route a shipping clerk creates the outbound delivery.
🔁 The key distinction
One-step vs two-step. One-step (mvt 647) moves stock instantly with no in-transit phase. Two-step (mvt 641 → 101) parks stock "in transit" until the receiving plant confirms receipt — realistic for trucks taking days.
💰 Financial Impact — The Easy-Money Example
PakSteel moves 20 TO of finished rebars (FERT-REBAR-01), valued ₨3,000,000, from Karachi (PK01) to Lahore (PK02). Both plants sit inside company code PSPK. Here is the money story — and the punchline is that nothing hits the P&L:
The big idea: an intra-company STO has no P&L impact — it is just inventory moving between plants (and storage locations) inside the same company code, so total assets are unchanged. The only possible accounting entry is a small price-difference variance if the two plants happen to carry different valuation prices for the same material. Contrast this with an inter-company STO (Scenario 8), where the two plants belong to different legal entities — that one does create a real receivable/payable and intercompany revenue between the two company codes.
🇵🇰 The Business Story
🎯 What you'll learn — STO vs simple transfer (311)
- STO uses a PO document (Doc Type UB) — for tracking, approval, delivery
- Cross-plant (PK01 → PK02), not just SLoc-to-SLoc
- No invoice when intra-company (same CC, no AR/AP)
- Delivery via SD optional (more enterprise; simple cases use direct mvt 351 without SD)
- FI impact depends on whether plants share valuation area (usually plant-level → potential price-difference posting)
📋 Prerequisites
- Both plants PK01 + PK02 assigned to same CC PSPK
- Material FERT-REBAR-01 extended to BOTH plants (MM01 with plant view for each)
- STO Doc Type
UBactive (delivered standard) - For SD-integrated route: shipping points + sales area assignments (skip for simple route)
FERT-REBAR-01 (FERT, finished) — create steps. First time? the why behind every field.
🔧 Step-by-Step — Simple route (mvt 351 without delivery)
7.1 — Create STO · ME21N with Doc Type UB
- ME21N · Doc Type:
UB(Stock Transport Order) - Supplying Plant:
PK01(header → Customer/Vendor tab if needed) - Line:
- Material
FERT-REBAR-01· Qty 20 TO - Receiving Plant:
PK02(in the Plant field on line) - Item Category: blank (standard)
- Storage Location at receiving:
FNGD
- Material
- Save → STO # (e.g., 4500000200)
7.2 — Goods Movement — Method 1: One-step (647)
Stock leaves PK01 and arrives at PK02 instantly. No in-transit stock.
- MIGO · Goods Issue · Reference: Purchase Order · STO #
- Movement Type: 647 (auto)
- Confirm qty + SLocs (RAWM out at PK01, FNGD in at PK02)
- Post
FI: NONE if plant valuation prices are equal (same material code, same plant-level price). If price differs → variance to gain/loss G/L.
7.3 — Goods Movement — Method 2: Two-step (641 → 101)
Stock leaves PK01 → in-transit → arrives at PK02 later (realistic for trucks taking 2 days).
- Step A (issue from supplying plant): MIGO → Goods Issue → STO → mvt 641 → post (creates in-transit stock at PK02)
- Step B (receipt at receiving plant): MIGO → Goods Receipt → STO → mvt 101 → post (clears in-transit, lands at FNGD)
Track in-transit: MMBE for FERT-REBAR-01 → "Stock in Transit" column shows qty between steps A and B.
✅ Verification — Confirm Scenario 7 Worked
- MMBE → FERT-REBAR-01 → 20 TO moved from PK01 to PK02
- MB51 → mvt 351/641/647 entries
- ME23N → STO 4500000200 → all items delivered
- ME2O stock provided to vendor / stock transit overview
🎓 Interview-Ready Answers
Q: What is the difference between an STO and a normal stock transfer (311/301)?
An STO is driven by a purchase order document (Doc Type UB for intra-company), so it supports approval, scheduling, delivery via SD, and in-transit tracking across plants. A 311 is a plain transfer posting between storage locations in the same plant; a 301 is a one-step plant-to-plant move with no PO. Use an STO when you need a tracked, document-based transfer between plants.
Q: Does an intra-company STO post any accounting document?
Generally no P&L impact — both plants belong to the same company code, so total inventory value is unchanged; stock simply moves from one plant to another. The only accounting entry is a price-difference variance if the two plants carry different valuation prices for the same material. There is no invoice, no AR, and no AP.
Q: When would you choose one-step (647) over two-step (641 → 101)?
One-step (647) is for instant transfers where issue and receipt happen together and you don't need to see stock in transit. Two-step (641 then 101) is for realistic logistics where the truck takes time — the goods sit as "stock in transit" (visible in MMBE) after the 641 issue until the receiving plant confirms with the 101 receipt.