SAP stock transfer diagnostics

Core idea

Stock transfers move goods between plants, storage locations, or stock types. The most common support issue is not the transfer itself but the mismatch between what left the source and what arrived at the destination. In-transit stock is invisible to MRP at the destination until receipt is posted, which creates planning gaps. The support goal is to trace the transfer document, confirm the goods issue, track in-transit status, and verify the receipt.

In most cases the goods issue exists but the receipt was never posted. Check the receiving plant's goods receipt queue and physical receiving logs before assuming stock was lost.

Common symptoms

• Stock shows as in transit but never arrived at destination.
• Destination plant shows shortage while source plant shows the goods issue was posted.
• Transfer order quantity does not match goods issue or receipt quantity.
• Valuation difference between source and destination after transfer.
• MRP at destination does not consider in-transit stock as supply.

Likely causes

• Goods issue posted but receipt not posted: the physical shipment arrived but the receiving plant did not confirm it in the system.
• Partial shipment: only part of the transfer quantity was shipped, but the full quantity was expected.
• Wrong movement type: a one-step transfer was used when a two-step transfer was expected, or vice versa.
• Valuation area mismatch: source and destination plants use different valuation classes or currencies.
• Delivery or shipment document stuck: the transfer uses SD delivery and the delivery is blocked or incomplete.

Where to check in SAP

• ME23N — if the transfer is PO-based, check the PO history for goods issue and receipt.
• MIGO — display the material documents for both issue and receipt.
• MB5T — in-transit stock report per material and plant.
• MB52 — stock overview at both source and destination.
• VL03N — if SD delivery is used, check delivery status and shipment.

Key tables / transactions / objects

• EKPO / EKBE — purchase order items and history (for stock transport orders).
• MKPF / MSEG — material documents.
• MSLB / MSKA — special stock tables (if consignment or pipeline).
• LIPS — delivery items (if SD delivery involved).

Diagnostic workflow

1. Confirm the transfer type: one-step (301/311) or two-step (303/305, or stock transport order).
2. Check if a goods issue was posted at the source and capture the material document.
3. Check MB5T or MB52 for in-transit quantity.
4. Check if a goods receipt was posted at the destination.
5. If receipt is missing, verify physical arrival and post the receipt or investigate why it was not posted.
6. If quantities differ, trace partial shipments, returns, or damage.

Typical fixes or next actions

• Post the missing goods receipt at the destination if the goods physically arrived.
• Reverse and re-post the transfer with the correct movement type if the original was wrong.
• Update MRP views to consider in-transit stock if the planning gap is systematic.
• Escalate to logistics if the physical shipment never arrived or was damaged.

Retail-specific: DC-to-store delivery failures

In retail, stock transfers from a DC to a store often use stock transport orders (STOs) with SD deliveries. When a store does not receive expected stock, the issue may be in the STO, the delivery, the shipment, or the carrier.

• Check STO status: ME23N shows whether the STO is released, partially delivered, or fully delivered.
• Check delivery block: VL03N or VL06O shows if the outbound delivery is blocked for picking, packing, or goods issue.
• Check picking status: the delivery may be created but not yet picked due to DC capacity or wave scheduling.
• Check shipment status: VT03N or carrier tracking shows if the shipment is in transit, delayed, or delivered.
• Check store receiving: the delivery may have arrived physically but the store has not posted the goods receipt.

A useful DC-to-store delivery ticket should include: STO number, delivery number, shipment number, expected delivery date, current status, and whether the issue is isolated to one store or affects multiple stores on the same route.

What to capture first

Stock transfer issues are usually process gaps between shipping and receiving, not system errors. Capture: source plant, destination plant, material, transfer document or PO number, goods issue document, expected receipt date, and current in-transit quantity.

Escalation signals

• Stock is physically in transit but missing in the receiving plant, or vice versa, with financial impact.
• The transfer involves intercompany valuation, tax, or customs requirements beyond standard plant-to-plant posting.
• Multiple materials or plants show the same stock transfer discrepancy, indicating a configuration issue.
• The case requires a correction posting that affects inventory valuation or month-end closing.

Boundaries and non-goals

This page is a diagnostic frame, not a stock transfer configuration guide. It does not cover EWM-managed transfers, cross-company code transfers with intercompany billing, or pipeline materials. It does not replace SAP's logistics documentation.

This is not official SAP documentation and not a replacement for system-specific analysis.