Stock Transport Order
MM / P2Pintermediate

MM Stock Transport Order Part 3: One-Step vs Two-Step and Stock in Transit

Key takeaway

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

Explanation

📌 KEY POINTS
✅ Two-step (641 GI + 101 GR) keeps goods in stock in transit until the receiving plant confirms.

✅ One-step (647) posts GR automatically at GI — no transit visibility.

✅ Stock in transit is valuated and belongs to the receiving plant (intra-company).

✅ Lost or damaged goods must be handled explicitly (GR partial, scrapping, claims).

⚠️ One-step for long transport routes hides goods physically on trucks as already received.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE

Part 2 covered configuration. Now step choice.

━━━━━━━━━━━━━━━━━━━━
▶ 1. TWO-STEP

  • GI 641 → stock in transit → GR 101 at receipt.

━━━━━━━━━━━━━━━━━━━━
▶ 2. ONE-STEP

  • GI 647 posts GR at receiving plant immediately (config per plant pair).

━━━━━━━━━━━━━━━━━━━━
▶ 3. STOCK IN TRANSIT

  • MB5T report; valuation and ownership.

━━━━━━━━━━━━━━━━━━━━
▶ 4. EXCEPTIONS

  • Partial receipt, loss, damage; closing open transit.

━━━━━━━━━━━━━━━━━━━━
▶ 5. CHOICE

  • Distance, need for receipt control, accounting preferences.

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

  1. Run a two-step STO; check MB5T.
  2. Switch plant pair to one-step and compare.

✅ CHECKPOINT: transit stock is only used where receipt confirmation matters, and cleared regularly.

Code example

ABAP Code
===== STEP 1: movements =====Two-step: 641 (GI, stock in transit) → 101 (GR) | one-step: 647Cross-company: 643 (two-step) / 645 (one-step) ===== STEP 2: monitoring =====MB5T stock in transit per STO | aging review monthly ===== STEP 3: exceptions =====Partial GR + delivery completed | damaged → GR to blocked then scrapping | claims to carrier

Real project scenario

A transfer was considered lost after three months in transit, but still sat in stock in transit and inflated inventory. The team introduced monthly MB5T reviews, a process for losses (GR then scrapping with approval) and carrier claims.

Common mistakes

  • One-step for long transports.
  • Never clearing transit.
  • No loss process.
  • Ignoring valuation.
  • No monitoring.

Best practices

  • Choose steps per route.
  • Review MB5T monthly.
  • Define loss handling.
  • Align with finance.
  • Track transit times.

Interview angle

Questions: "One-step vs two-step STO?", "What is stock in transit?", "How do you handle lost transfers?"
Strong answer: movement types, transit valuation/visibility, exceptions, choice criteria, monitoring.

Practice this lesson

Quick check

1. Which movement type posts a two-step intra-company STO goods issue into stock in transit?

2. A transfer considered lost three months ago still sits in stock in transit. What should be done?

3. A company uses one-step STOs for week-long truck transports. What is the problem?

Interview questions

1. 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?

Answer it in your own words first, then compare.

2. 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?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.

More lessons in this topic

Interview questions on this topic

Related SAP topics