MKOL table — MKOL Special Stock at Vendor Table

One row of MKOL represents the valuated quantity of a material that a plant has physically located at a vendor's site, broken down by material, plant, vendor and stock category (unrestricted, quality inspection, blocked, returns blocked). It exists to track components issued to a subcontractor for further processing, special stock indicator O, and any other stock a plant owns but does not physically hold in one of its own storage locations. Quantities in MKOL move with goods movements against subcontracting purchase orders: components sent out to the vendor, components consumed when the finished or semi-finished product is received, and components returned unused. The table never describes the finished good the subcontractor is producing, only the raw components MM still owns while they sit outside the plant.

The fields below are the ones actually used in reconciliation work; anything not listed here should be looked up in the ABAP dictionary rather than assumed.

MKOL is a leaf table in the material master hierarchy; it does not carry its own header, everything is resolved through material and vendor master data plus the movement history that built the balance.

Always restrict on MANDT implicitly and then on WERKS plus MATNR before pulling anything; the table is small compared to MARD but scanning it by vendor alone across all materials returns noise. LBKUM by itself is only the unrestricted-use portion of the balance; a real stock-at-vendor figure is LBKUM plus INSME plus SPEME plus RETME. There is no storage location field because vendor stock is not tracked at that granularity, so any query trying to break the balance down by storage location will fail silently or return nothing rather than an error.

Symptom: a subcontracting invoice or a physical count at the vendor suggests more components were consumed than were ever sent. Select MKOL on WERKS, LIFNR and MATNR for the component in question and read LBKUM plus the qualifier fields for the current balance, then select MSEG on the same three keys filtered to the relevant movement types to see the issue, consumption and return history that produced that balance, and compare the running total against LBKUM.

MKOL still exists as a physical table in S/4HANA and continues to be updated the same way, through goods movements tied to subcontracting purchase orders. It has not been absorbed into the universal journal or the unified material document table the way some valuation tables were; stock overview and subcontracting monitor apps in S/4 read it, or content derived from it, alongside MARD and MSLB for the special stock picture. No specific compatibility view name is asserted here without confirmation.

First point of contact is the MM consultant who owns the subcontracting process and the movement type configuration behind it. If the dispute turns into a real quantity correction at the vendor, it moves to whoever owns physical inventory counts and posts the correcting movement, not to a basis or data team.

MSLB is the mirror table for vendor consignment stock and is the most common source of confusion. MARD, MARA and MARC provide the plant and material master context. LFA1 resolves the vendor. MSEG carries the movement history that builds every MKOL balance, written from goods movements posted through MIGO against subcontracting purchase order items in EKPO, and reviewed through stock overview and subcontractor stock monitor transactions.