MSEG table — MSEG Material Document Line Items

One row in MSEG represents a single material movement line within a material document. A material document created by a single posting transaction can contain many lines, for example a goods receipt against a purchase order with ten line items, or a transfer posting moving three different materials at once. Each row records what moved, from where, to where, in what quantity, and the resulting value change to inventory. The movement type on the row determines what kind of event it is: goods receipt, goods issue, stock transfer, physical inventory difference, and so on. MSEG never stands alone; every row belongs to exactly one header row in MKPF, identified by document number and fiscal year. Reversal movements appear as separate rows with an offsetting quantity, not as an update to the original row.

MSEG has no direct posting date field, so any date restriction has to come through MKPF-BUDAT or MKPF-CPUDT joined on MBLNR and MJAHR; selecting MSEG alone by a date range is not possible and pulling the full table to filter in an application layer will time out on any live system. Always restrict by MANDT implicitly through the standard client handling, then narrow by plant, material, and movement type before touching quantity or value fields, since BWART groups behave very differently from each other. MJAHR is part of the key and easy to forget; a query on MBLNR alone across years returns wrong or duplicate-looking rows. For a specific purchase order line, filtering on EBELN and EBELP first is far cheaper than scanning by material across an entire plant.

To confirm that a purchase order line was actually received rather than just showing open quantity on the order, select MSEG where EBELN and EBELP match the order line and BWART is in the goods receipt range for the account assignment category in use, then check SHKZG to confirm the movement was a debit to stock. Join to MKPF on MBLNR and MJAHR to get the actual posting date. If no row is returned, no goods receipt has been posted against that line regardless of what the order status shows.

On S/4HANA, MSEG is no longer a physical transparent table but a compatibility view generated on top of the unified journal table for material documents, commonly referred to by its underlying table name MATDOC. Existing reports, joins, and ABAP code that read MSEG continue to work because the view exposes the same field structure, but new development is expected to read MATDOC directly for better performance on large volumes. The field content and key structure that consultants rely on for MSEG have not materially changed.

A discrepancy traced to MSEG is an inventory management or MM functional consultant question first, since the movement type configuration and account assignment logic determine what got posted and why. If the value fields disagree with the general ledger, it becomes a joint MM and FI question resolved through the material ledger or account determination setup, not by editing the table.

MKPF is the header table for every MSEG row and is written by the same posting transactions, principally goods movement postings, goods receipt against purchase order, and physical inventory documents. EKBE reflects the purchase order history built from these same postings and is the usual next stop when reconciling a purchase order against what was actually received or issued. MARD and MBEW hold the resulting stock quantities and values that MSEG postings update.