MB5B — Stock on Posting Date
MB5B is used to calculate stock quantities and values as of a historical posting date for a material/plant selection. It is most useful when reconciling month-end inventory or explaining why historical availability differs from today's stock. Work from the exact document, organizational level and business date, then verify downstream status or accounting evidence before changing master data or configuration.
This page explains MB5B — Stock on Posting Date — as a practitioner reference: what it does, when it belongs in the process, the fields that matter, how to prove the result in SAP data, and the mistakes that create the most rework.
Published 19 Sept 2026· 570 words
Esta página ainda não está disponível em português.
Purpose
calculate stock quantities and values as of a historical posting date for a material/plant selection. The key is to treat MB5B as one step in an end-to-end process. What users see here is often determined earlier by master data, document status, organizational assignments or configuration, so always capture those inputs before changing the transaction result.
When it is used
MB5B is typically used when reconciling month-end inventory or explaining why historical availability differs from today's stock. It is also valuable in integration and regression testing because the resulting document/status provides objective evidence of whether upstream data and configuration are aligned. Narrow the working population first so any change can be reconciled safely.
How to use it in practice
- Use the exact historical posting date from the incident or close.
- Restrict material/plant before broad analysis.
- Review opening balance plus movements to closing balance.
- Compare suspicious movements with MB51.
- Use the same valuation and stock scope as the accounting reconciliation.
Key data objects
These fields and business objects usually explain the result in MB5B. Put them into support tickets and test evidence so another consultant can reproduce the same state instead of working from a generic symptom.
- material/plant — verify the exact value, status, organizational context and date relevance.
- posting date — verify the exact value, status, organizational context and date relevance.
- stock type — verify the exact value, status, organizational context and date relevance.
- opening balance — verify the exact value, status, organizational context and date relevance.
- receipts/issues and closing balance — verify the exact value, status, organizational context and date relevance.
How to prove it in the data
Prove the issue through document flow and chronology. Start with the source requirement or document, identify the exact master/configuration keys used, then inspect the generated logistics or accounting document and its status. For quantity issues, reconcile ordered, received, delivered, invoiced and current/historical stock; for value issues, reconcile pricing, account determination and the FI document.
ECC vs S/4HANA
MB5B remains a key inventory-reconciliation report in S/4HANA, especially for period-end and backdated movement analysis. In an S/4HANA program, keep valid GUI transactions as support tools but use the strategic Fiori, workflow, embedded analytics and clean-core integration patterns where they provide the preferred business surface.
Common pitfalls and how to diagnose them
- Using MMBE current stock to explain a historical posting. Check the complete document flow before applying a workaround.
- Mixing document date and posting date. Check the complete document flow before applying a workaround.
- Comparing reports with different stock-type selections. Check the complete document flow before applying a workaround.
Whose problem this is
Primary ownership sits with MM/P2P depending on the transaction, with Finance joining where accounting is created and EWM/integration teams joining where execution happens outside core ERP. Escalate with document numbers, organizational keys, date, expected result and proven status.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/mb5bERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.