MB1B — MB1B Transfer Posting Between Plants and Storage Locations

MB1B posts a transfer of material stock that is not tied to a purchase order or sales order. It is a single-transaction wrapper around a large family of movement types: plant-to-plant transfer (301), storage-location-to-storage-location transfer (311), stock category change out of quality inspection (321), release from GR blocked stock (411), and several others. The structural fact that explains most confusion is that MB1B does not know or enforce which movement type is 'correct' for a given business intent; the user selects the movement type manually, and the system posts whatever accounting and stock consequences that movement type carries. Two very different transfers can be entered on the identical MB1B screen and produce completely different GL postings, simply because a different four-digit movement type was typed into one field.

MB1B is reached for when stock needs to move somewhere a purchase order or sales order process does not cover: rebalancing stock between plants for production, moving material between storage locations within a plant, releasing quality inspection stock to unrestricted use, or clearing GR blocked stock after inspection. It sits outside the standard procure-to-pay document chain, so it does not appear in purchase order history and is not settled through invoice verification. In S/4HANA the equivalent functional coverage exists in MIGO with transaction 'Transfer Posting' selected, and in the Fiori 'Post Goods Movement' app, both of which use the same movement types underneath. Consultants still use MB1B directly for mass entry, for movement types not well supported in the Fiori tile layout, or when working a batch-input or LSMW-driven mass transfer.

Pull MSEG filtered on BWART for the relevant movement types (301, 311, 321, 411, 351/352) and on MATNR and WERKS for the material and plant in question. Join to MKPF on MBLNR and MJAHR to get posting date and user. Compare WERKS and LGORT on the sending line against the receiving line to confirm the transfer actually moved stock where it was supposed to. If a value discrepancy is reported, take the same MBLNR/MJAHR pair into BKPF/BSEG to see which GL accounts were hit and compare the amount to the valuation in MBEW at the time of posting.

MB1B still functions in S/4HANA as a compatible transaction, but the underlying data model has changed: MKPF and MSEG are compatibility views over the consolidated material document table, and the accounting effects are reflected directly in the universal journal rather than a separate FI document in the classic sense. SAP steers new builds toward MIGO or the Fiori 'Post Goods Movement' app for the same movement types. Reporting and joins written against MSEG in ECC generally still work, but consultants should be aware the physical storage has moved.

Functional MM issue in almost every case: movement type selection, stock category logic, and batch handling belong to the MM consultant. Account determination discrepancies get handed to FI/CO for OBYC review. Basis involvement is rare and limited to authorization objects for movement types or plants. A good handover includes the material document number, the movement type used, and whether the posting was one-step or two-step.

MB1A (goods issue) and MB1C (goods receipt without a purchase order) sit alongside MB1B as the three generic goods movement transactions; understanding how movement types differ across all three clarifies why MB1B behaves the way it does. MBST is the correct reversal path for a bad MB1B posting. MB03 is the direct way to display and verify a posted material document. MB52 is used afterward to confirm the resulting stock position matches expectation.