MB5T — Stock in Transit
MB5T is used to display stock in transit for stock transport processes where goods issue has occurred but receipt is still outstanding. It is most useful when reconciling inter-plant transfers or investigating quantities that left the supplying location but have not reached the receiving stock. Start with the exact organizational keys, business document and date, then reconcile the resulting SAP document or status before changing master data or configuration.
Verified practitioner reference for MB5T — Stock in Transit. The page covers purpose, when to use it, practical execution, the key business data to capture, how to prove the result, S/4HANA context, common mistakes, ownership and related SAP objects.
Published 19 Sept 2026· 602 words
Diese Seite ist noch nicht auf Deutsch verfügbar.
Purpose
display stock in transit for stock transport processes where goods issue has occurred but receipt is still outstanding. Treat MB5T as one step in an end-to-end process. Values shown or posted here are usually driven by master data, organization, dates and preceding documents, so an accurate diagnosis starts by preserving those inputs rather than changing the symptom screen first.
When it is used
MB5T is typically used when reconciling inter-plant transfers or investigating quantities that left the supplying location but have not reached the receiving stock. It is also valuable in project and regression testing because it provides a repeatable business state. In production, use the narrowest document or organizational selection that answers the question and capture the before-state before any posting, clearing or configuration change.
How to use it in practice
- Restrict by plant/material or stock transport order.
- Identify quantities still in transit.
- Compare with goods-issue material documents.
- Check whether the receiving goods receipt exists or was reversed.
- Reconcile old in-transit items before period close.
Key data objects
These are the fields and business objects that most often explain the result in MB5T. Record them in support evidence so the next person can reproduce the same outcome.
- material — verify the exact value, validity/date context and relationship to the source document.
- supplying/receiving plant — verify the exact value, validity/date context and relationship to the source document.
- stock transport order — verify the exact value, validity/date context and relationship to the source document.
- quantity in transit — verify the exact value, validity/date context and relationship to the source document.
- posting/document dates — verify the exact value, validity/date context and relationship to the source document.
How to prove it in the data
Use document flow and chronology. Start from the source business event, inspect the MB5T document or master data, then follow the resulting accounting, purchasing or asset document and reconcile amount, quantity, account assignment and status. A correct proof uses the same company code or plant, business date, document keys and currency/unit context at every step.
ECC vs S/4HANA
Stock-in-transit reporting remains relevant in S/4HANA stock transport processes. Where S/4HANA offers a Fiori successor or a changed data model, the classic transaction can still be valuable for support, but the strategic process and clean-core guidance should govern new implementations.
Common pitfalls and how to diagnose them
- Treating stock in transit as unrestricted stock at the receiving plant. Reconcile the exact business document and date before applying a workaround.
- Ignoring returns/reversals. Reconcile the exact business document and date before applying a workaround.
- Using current in-transit values to explain a historical period without posting-date context. Reconcile the exact business document and date before applying a workaround.
Whose problem this is
Primary ownership is the MM/P2P team, with adjacent teams involved when the evidence crosses into Asset Accounting, Project System, tax, Basis, Security or integration. Escalate with document numbers, organization, dates, expected result, actual result and checks already completed.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/mb5tERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.