MB1A — MB1A Goods Issue for Consumption
MB1A posts a goods issue that consumes stock against a cost object - a cost center, internal order, sales order, or for scrapping - without reference to a purchase order or production order confirmation. It creates a material document (MKPF/MSEG) and, where relevant, an FI and CO document in the same posting. It does not cover goods receipts or warehouse transfers.
MB1A is the classic single-screen transaction for manually posting a goods issue that is not driven by a purchase order or a production order backflush. This page covers the movement types it actually handles, the account assignment traps that generate the bulk of support tickets, and how to trace a posting back through MSEG, COEP, and the accounting document.
Reviewed by an ERPClimb SAP consultant on 15 Sept 2026· 1,164 words
What it does
MB1A posts goods issues for movements that have no automatic trigger elsewhere in the system - withdrawal for a cost center (movement type 201/202), consumption against a sales order (231/232), or scrapping (551/552). It writes a material document header in MKPF and one line per posting in MSEG, exactly like MIGO does, but it has no referencing tabs for purchase order, production order, or delivery. The one fact that explains most confusion around it: MB1A is for issues you type in by hand because nothing upstream generated them. If a movement is meant to happen automatically off a PO or an order confirmation, MB1A is the wrong transaction and forcing it there breaks the natural document chain.
When it is used
MB1A sits in the physical execution part of the process, after material has already been procured or produced and is sitting in unrestricted stock. It gets used when a cost center draws material for internal consumption, when a sample or scrap quantity needs to leave inventory without a formal order, or when a sales order needs a manual consumption posting outside the standard delivery flow. Consultants reach for MB1A instead of MIGO when the required movement type is a manual issue type that MIGO's document-referencing structure does not naturally support, or when supporting a legacy process that has never been migrated onto MIGO or a Fiori goods movement app. It is not used for receipts, transfers between storage locations, or reversals of PO-based movements.
How to use it
- Call MB1A and select the movement type first (201/202 cost center, 231/232 sales order, 551/552 scrapping, or a custom manual issue type)
- Enter plant and storage location for the header
- Enter the GI/GR slip or external document reference if the business process requires one
- Enter posting date and document date if different from today
- On the item screen, enter material, quantity, unit of measure, and the account assignment object required by the movement type (cost center, order, WBS element, sales order item)
- Enter batch or serial number if the material is batch- or serial-managed
- Use item check or simulate to catch account determination and stock shortage errors before saving
- Save to generate the material document; note the document number and material document year
Key fields
- MKPF - material document header: document number, document date, posting date, user
- MSEG - material document line items: movement type, plant, storage location, quantity, batch, account assignment fields
- BKPF/BSEG - accounting document header and line items, created when the movement is valuation-relevant
- COEP/COBK - CO line items and document header, updated when the offsetting posting hits a cost center, internal order, or WBS element
- MBEW - material valuation, moving average price and stock value updated by the posting
How to prove it in the data
Start in MSEG filtered on BWART for the movement type in question (201, 202, 231, 551, and their reversal counterparts) and on werks and lgort if the complaint is plant- or location-specific. Cross-check MBLNR and MJAHR against MKPF to confirm document existence and posting date. For cost impact questions, take the same MBLNR/MJAHR/ZEILE combination and look it up in COEP to see which cost object and cost element actually absorbed the consumption, and compare against BSEG for the FI side if a value discrepancy is being investigated.
ECC vs S/4HANA
MB1A is unchanged structurally in S/4HANA; it still writes to MKPF and MSEG (now backed by the merged MATDOC-based data model under the hood, but the transaction and its field behavior are the same). SAP's direction of travel is toward MIGO and the Fiori 'Post Goods Movement' style apps for new implementations, but MB1A has not been withdrawn and continues to work in the classic GUI. No new mandatory fields or movement type restrictions have been introduced specifically for this transaction.
Common pitfalls
- Wrong movement type chosen - 201 versus 202 are opposite directions, and confusing them with a similar-looking transfer type (3xx series) produces a posting that looks fine on screen but consumes the wrong account. Check BWART on the resulting MSEG line against what the business actually intended before touching anything else.
- Account assignment errors - the movement type demands a cost center, order, or WBS element and either the field was left blank, the object is locked, or the order carries a status (technically complete, closed) that no longer allows postings. This is the single most common MB1A ticket; check the account assignment object's status first, then account determination in the material master valuation class.
- Valuation and negative stock - posting an issue that drives on-hand quantity negative without negative stock being allowed for that storage location fails outright; posting one that is allowed but unintended silently distorts the moving average price. Check MB52 for the stock position before assuming the transaction itself is broken.
- Batch or serial number omitted - for batch-managed materials the system either blocks the posting or, worse, allows it against the wrong batch if batch determination defaults incorrectly. Verify batch management is active on the material master before diagnosing further downstream.
- Reversal handled wrong - users re-run MB1A with the opposite movement type instead of reversing the original document through MBST, which breaks the document chain and makes root-cause tracing much harder later. Always check whether a clean reversal document exists before accepting a manual counter-posting as the fix.
- Posting period errors - the posting date falls in a closed MM period; the fix is a period change through the standard period-open process, never backdating around it with a workaround posting date.
Whose problem this is
Primarily a functional MM issue; ownership shifts to FI or CO when the account determination or cost object posting fails, and to ABAP or Basis only if a custom substitution, validation, or user exit is intercepting the posting. A good handover includes the material document number and year if one was created, the movement type attempted, plant and storage location, and the exact account assignment object involved.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/mb1aERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.