MB1C — Post Goods Receipt Without Reference
MB1C posts a goods receipt that has no preceding purchase order, reservation, or production order. The transaction is entirely driven by the movement type entered on the initial screen, which determines whether the posting touches valuation, triggers an FI document, and which fields become mandatory. It is most commonly used for initial stock uploads and off-cycle receipts.
This page covers MB1C, the transaction for posting goods receipts that have no reference document behind them, such as initial stock balance uploads and free-of-charge receipts. It focuses on how the movement type entered on the selection screen changes the entire behavior of the posting, and on the diagnostic patterns behind failed or wrongly valuated postings.
Reviewed by an ERPClimb SAP consultant on 15 Sept 2026· 1,146 words
Purpose
MB1C posts a goods receipt with no preceding purchase order, reservation, or production order. The single structural fact that explains almost all confusion around it: the transaction itself has no fixed business meaning until a movement type is typed into the header. The movement type decides everything downstream, whether the receipt is valuated or not, whether it updates a GL account, whether batch or valuation type entry is mandatory, and whether the quantity lands in unrestricted, blocked, or quality stock. Consultants who treat MB1C as a single-purpose screen (rather than a generic entry point parameterized by movement type) end up misreading error messages that are actually configuration issues tied to the specific movement type chosen, not to the transaction itself.
When it is used
MB1C is reached for postings that fall outside the normal procure-to-pay or production cycle: loading opening stock balances during a data migration cutover (movement type 561), receiving free samples or promotional goods (501/502), correcting stock discrepancies that are not covered by a physical inventory count, or bringing subcontracting or consignment stock onto the books outside the standard flow. It is a receipt-side counterpart to MB1A (goods issue without reference) and MB1B (transfer posting without reference). In current landscapes MIGO with the 'Other Goods Receipt' transaction variant covers the same movement types through a single unified screen, and many sites standardize on MIGO instead of MB1C for day-to-day use, keeping MB1C mainly for batch-input driven mass uploads during cutover.
How to use it in practice
- Call MB1C and enter the movement type first, since it drives every field that follows, along with the receiving plant
- Enter the storage location if the plant is storage-location managed
- Enter the material number and press enter to expand the item detail line
- Fill quantity, unit of entry, and batch or valuation type if the material is batch-managed or split-valuated
- Respond to the account assignment or GL determination popup if the movement type is valuation-relevant
- Review the item list, check for missing mandatory fields flagged in the status bar, then save
- Confirm the material document number returned and, if relevant, note the accompanying accounting document number
Key data objects
- MKPF - material document header, one row per posting, holds document date, posting date, and the user who posted
- MSEG - material document line items, holds movement type, quantity, plant, storage location, batch, and valuation type per item
- MARD - storage location stock quantities, updated with the posted quantity split by stock category
- MBEW - valuation data at plant level, moving average price or standard price recalculated for valuated movement types
- BKPF and BSEG - FI header and line items, created only when the movement type is valuation relevant and posts to a GL account
How to prove it in the data
In SE16, open MSEG and filter on BWART (movement type) plus WERKS and LGORT for the plant and storage location in question, restricting MBLNR to a date range via a join with MKPF on BUDAT. Compare the summed MENGE against MARD-LABST for the same material, plant, and storage location to confirm the posting actually landed in stock. If a GL impact is expected but missing, check whether an accounting document number exists at all in MSEG (field for the accounting doc reference) before looking in BKPF, since a blank reference means the movement type was configured as non-valuated.
ECC vs S/4HANA
MB1C still exists and behaves the same way on S/4HANA; the underlying movement type logic and table structure are unchanged. The practical shift is that MIGO's 'Other Goods Receipt' variant is the preferred single-transaction interface for the same postings, and Fiori apps for goods movement give business users a simplified front end without exposing the raw movement type selection the way MB1C does. Mass upload scenarios during cutover still lean on MB1C or its batch input variant because it accepts a flat movement-type-driven structure that is easy to script.
Common pitfalls and how to diagnose them
- Wrong movement type chosen for the intent: 561 is meant for initial stock load during migration, not for ongoing operational corrections; using it repeatedly outside cutover masks real process gaps and produces stock that has no traceable origin document.
- Account determination failure: valuation-relevant movement types need a GL account resolved through the automatic account assignment configuration for the valuation class and movement type combination; a missing entry throws an account determination error at save, and the fix belongs to the FI/CO team that owns OBYC-type configuration, not to reposting with a different movement type as a workaround.
- Batch or valuation type not maintained: for batch-managed or split-valuated materials, MB1C will demand a batch or valuation type before the item can be saved; check the material master's batch management flag and existing batch classification before assuming the transaction is broken.
- Storage location or plant not extended for the material: the material master lacks a plant or storage-location view, which surfaces as a material-not-extended error rather than a stock error; check MM03 extension views before touching the movement itself.
- Reversal confusion after mass loads: postings made through MB1C are reversed through MBST or a matching offsetting movement type, and picking the wrong reversal movement type creates a second discrepancy on top of the first; always trace the original MBLNR before choosing how to undo it.
- Batch input session failures during mass upload: when MB1C is driven through a recorded batch input session for cutover loads, authorization gaps or locked material masters cause silent session errors that only show up when the session log is reviewed line by line.
Whose problem this is
Functional MM/inventory management owns the movement type selection and the business justification for using it. FI/CO owns account determination when the posting is valuation-relevant. Basis involvement is limited to batch input session scheduling, authorization objects, or number range exhaustion. A good handover includes the material document number, movement type used, plant and storage location, and whether an accounting document was expected.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/mb1cERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.