MSLB table — Vendor Stock for Subcontracting Table MSLB

One row in MSLB represents the current stock of a specific material, owned by a specific plant, sitting physically at a specific subcontractor vendor, valuated under special stock type O (subcontracting). It is populated and updated as components are issued to the subcontractor (movement type 541), consumed in the subcontracted process, or returned/adjusted. The table does not describe a transaction or a point in time; it is a running balance, similar in nature to MARD for storage-location stock or MCHB for batch stock, except the storage location is replaced by a vendor. When the balance for a material/plant/vendor combination falls to zero, the row is typically cleared rather than kept as a zero-quantity historical record.

MANDT must always be part of the selection. The table is small relative to MARD or MSEG because it only carries rows for material/plant/vendor combinations that currently have subcontracting stock outstanding, so a query restricted by WERKS and LIFNR is fast and selective, and adding MATNR narrows it to a single row. Do not scan the table unfiltered looking for 'all subcontracting stock' across a large vendor base; restrict by plant first, since that is usually the known starting point of an incident. Remember there is no date or document number on the row, so it cannot answer 'when' or 'which order', only 'how much, right now'.

Symptom: subcontractor reports a component shortage or a physical count mismatch at their site. Selection: read MSLB with WERKS equal to the owning plant, LIFNR equal to the subcontractor, MATNR equal to the disputed component, and note LBKUM. Then read MSEG (or MATDOC) for the same MATNR, WERKS and LIFNR restricted to movement types 541 and 542 (issued to vendor) against 543 and 544 (returned or consumed) over the relevant period, and confirm the net of those movements reconciles to the current LBKUM.

On S/4HANA, MSLB along with the other classic aggregate stock tables (MARD, MCHB, MKOL, MSKA and similar) is generally exposed through a compatibility view rather than read as a directly maintained physical table, with the underlying stock quantities derived from the consolidated material document data model. Reports and standard transactions that select from MSLB continue to return correct current balances. Custom code doing native SQL reads or relying on database-level locking behaviour against MSLB specifically should be reviewed, since the storage and update mechanics behind the view differ from the ECC-era table.

A discrepancy surfaced through MSLB is first a subcontracting/inventory management question for the MM consultant running the procure-to-pay process, working jointly with plant operations that owns the physical relationship with the vendor. Master data mismatches on the material or vendor route to the MM master data team, and value-side questions on SALK3 route to inventory accounting or controlling.

Neighbouring stock tables covering the same balance-per-special-stock pattern include storage location stock, batch stock, sales order stock and vendor consignment stock. The movements that write to MSLB come from goods issue and goods receipt postings against a subcontracting purchase order (item category relevant to subcontracting), typically executed through the standard goods movement transactions and reflected in the material document tables that carry the movement type detail.