MSKA table — MSKA Sales Order Stock Table

One row in MSKA represents the quantity of a material tied to one sales order and sales order item, at a given plant, storage location and batch, under special stock indicator E. This is sales order stock: physically received or produced inventory that SAP segregates so it can only be withdrawn against that specific order line, typically arising from make-to-order production, third-party order processing, or individual purchase orders assigned to a sales order. The row carries separate quantity fields for unrestricted-use, quality inspection, blocked and stock-in-transfer status, mirroring the structure used for plant stock in MARD but scoped to a sales order. A valuation number (KALNR) is populated when the stock is valuated separately from standard plant stock, which happens in make-to-order and engineer-to-order scenarios where each sales order needs its own cost view.

Always restrict on MANDT first. MSKA is far smaller than MARD or MSEG in most systems because only sales order stock rows exist, but selectivity still matters: never select on VBELN alone across a whole client if the system runs multiple company codes with overlapping order number ranges without also checking WERKS. The natural narrow key for a single incident is MATNR plus WERKS plus VBELN plus POSNR, which returns at most a handful of rows including batch splits. Do not read LABST in isolation and assume it is the total sales order stock; sum LABST, INSME, SPEME and UMLME if the question is 'how much stock is held against this order,' because a quality-inspection lock or a blocked-stock posting can hide quantity that still belongs to the order.

Symptom: a sales order shows a delivery-blocking shortage even though goods receipt was posted. Select MSKA on MATNR, WERKS, VBELN and POSNR for the order line. If a row exists with quantity sitting in INSME or SPEME rather than LABST, the stock arrived but is inspection-locked or blocked, not actually short. If no row exists at all, the goods receipt was posted to plant stock (SOBKZ blank) instead of sales order stock, usually because the purchase order account assignment or the delivery's requirement was not flagged as order-related.

MSKA continues to exist as a transparent table in S/4HANA and is still the authoritative source for sales order stock quantities; it was not absorbed into the unified MATDOC document table the way MSEG summary logic was reworked. Standard reporting and Fiori stock apps read sales order stock through compatibility views built on top of MSKA rather than querying it directly, but the table itself and its field layout are unchanged from the ECC version for practical consulting purposes.

Sales order stock discrepancies are jointly owned by MM inventory management and SD order fulfillment, since the special stock indicator originates from the sales order's requirement configuration but the quantity movement is an MM goods movement. Valuation questions involving KALNR belong to controlling or product costing, particularly for make-to-order cost object analysis.

MARD and MCHB hold the equivalent quantities for normal (non-special) plant and batch stock, useful for contrast when checking whether stock posted to the wrong bucket. MSEG and MKPF record the individual goods movements that created or reduced the MSKA balance, identifiable by SOBKZ E and matching VBELN/POSNR. MBEW carries the valuation figures when KALNR points to a separate valuation. MVKE holds the sales-org-level material master data that determines whether a material is typically handled through make-to-order logic in the first place. Movements are posted through standard goods movement transactions and order confirmations, not maintained directly.