MSKA
transaction S/4HANA status: Active · Proxy ViewProxy view: reads route through NSDM proxy/CDS views
Sales Order Stock
Special-stock indicator fields persist in MSKA; sales-order stock quantities calculated via NSDM CDS/proxy views using MATDOC
What the badges mean
- S/4HANA status: Active
- Active and unchanged in S/4HANA.
- S/4HANA status: Deprecated
- Still readable today, but no longer SAP's strategic path — plan around it.
- S/4HANA status: Replaced
- Replaced by a new persistence in S/4HANA; the classic name may still answer reads (see read mechanism).
- S/4HANA status: Migrating to IBP
- Planning scope is moving from APO toward IBP.
- S/4HANA status: Active (StRM) · Replaced (EWM)
- Path-dependent: active with SAP Stock Room Management, replaced where EWM is the warehouse path.
- S/4HANA status: Replaced · Compat View
- Compatibility view: the classic table name is redirected to a view over the new persistence — see how the physical model moved.
- S/4HANA status: Active · Proxy View
- Proxy view: reads route through NSDM proxy/CDS views — see how the physical model moved.
- master
- Data class: what the table holds — master data, transaction documents, org structure, config, or texts (one row per language — see the quirks guide).
- Linked type codes
CLNT — the client key; filter it explicitly and carry it through every join.
NUMC — fixed-width numeric text; keep it a string and keep the leading zeros.
DATS, TIMS — character date (YYYYMMDD) and time (HHMMSS), zero-filled when initial.
CURR, CUKY, QUAN, UNIT — amounts and quantities, meaningful only beside the currency key or unit that qualifies them.
LANG — a language key in a text table — one row per language.
Fields
8 fields · 8 key
The join key is all 8 key fields together — matching on any single one fans out. See composite keys in the quirks guide.
8 fields.
| Key | Field | Description | Type | Length | References |
|---|---|---|---|---|---|
| Primary key | MANDT | Client | CLNT | 3 | |
| Primary key | MATNR | Material Number | CHAR | 18 / 40 | MARA |
| Primary key | WERKS | Plant | CHAR | 4 | T001W |
| Primary key | LGORT | Storage Location | CHAR | 4 | T001L |
| Primary key | CHARG | Batch Number | CHAR | 10 | |
| Primary key | SOBKZ | Special Stock Indicator | CHAR | 1 | |
| Primary key | VBELN | Sales Document Number | CHAR | 10 | VBAK |
| Primary key | POSNR | Item Number of Sales Document | NUMC | 6 |
Lengths shown as ECC / S/4HANA where the extended material number applies.
Linked type codes in the Type column jump to the matching section of the SAP data quirks guide.
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading MSKA on Databricks. Set your Unity Catalog location and filter values below — they’re substituted into the SQL and the copy button.
5 parameters not filled: <catalog>, <schema>, <MANDT>, <MATNR>, <WERKS>
-- ============================================================
-- Table : MSKA Sales Order Stock
-- Purpose: Column-selected read of MSKA — auto-generated from field metadata
-- Grain : One row per MATNR + WERKS + LGORT + CHARG + SOBKZ + VBELN + POSNR
-- Notes : Auto-generated skeleton. For multi-table transaction query patterns, see the linked t-codes on this page. Set catalog/schema to your Unity Catalog location; fill remaining placeholders (<...>) for your tenant.
-- ============================================================
SELECT
m.MANDT AS "Client",
m.MATNR AS "Material Number",
m.WERKS AS "Plant",
m.LGORT AS "Storage Location",
m.CHARG AS "Batch Number",
m.SOBKZ AS "Special Stock Indicator",
m.VBELN AS "Sales Document Number",
m.POSNR AS "Item Number of Sales Document"
FROM <catalog>.<schema>.mska m
WHERE
m.MANDT = '<MANDT>'
-- AND m.MATNR = '<MATNR>'
-- AND m.WERKS = '<WERKS>'
ORDER BY m.MATNR;Verified August 2026
Relationships
Diagram of 1-hop neighbors — join details below.
Transaction Codes That Use This Table
R read · W write · R/W read + write