/LIME/NQUAN
transactionMixed keyThe LIME stock quantities table — the physical quantity of a stock item hanging on one node of the location/handling-unit tree, one row per stock GUID per node per unit of measure
Rows hang on nodes of the LIME tree — never SUM across rows without resolving GUID_PARENT first, or nested handling units are counted more than once
LIME (Lean Inventory Management Engine) is the stock engine underneath EWM: quantities live here, attributes on /SCWM/QUAN, and the bin/HU position on the tree node the row points at. The unit of measure is part of the key, so one stock item can carry several quantity rows in different units.
What the badges mean
- master
- Data class: what the table holds — master data, transaction documents, configuration, an organizational object, or a language-striped text companion.
- Semantic key
- Every non-client key column is readable business data —
LGNUMplus a bin, task, or order number. Joins run on the columns you can see (see the quirks guide). - GUID key
- Every non-client key column is a GUID —
RAW(16)on the /SCWM, /SCDL, /LIME, and /SCMB tables, and theCHAR(22)compressed form on the product master. Join the raw column; a hex rendering is for reading only, and the two encodings need converting between (see the quirks guide). - Mixed key
- The key mixes readable and GUID columns in either direction — a product GUID inside an otherwise-readable bin key, or a readable status type inside an otherwise-GUID key. Check which side of a join you are on (see the quirks guide).
- DOCCAT: PDO
- A /SCDL delivery table holds several document categories in one table — inbound and outbound requests, the inbound delivery, the outbound delivery order, and the final outbound delivery — discriminated by
DOCCAT. The chips list the categories this table carries; anchor the one you mean or documents of every kind come back together (see the quirks guide). - Embedded S/4HANA only
- Deployment: shown only when a table does not exist in both embedded S/4HANA EWM and decentralized EWM. No table in this wave is deployment-specific, so the badge stays absent until one is.
Structural facts — how the table is keyed, not a trap by itself
Join & extract hazards — verify before you rely on this
Fields
12 fields · 5 key
12 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | MANDT | Client | CLNT(3) | Key |
| 2 | GUID_STOCK | Stock GUID — joins to the quant attribute rows | RAW(16) | Key |
| 3 | GUID_PARENT | GUID of the tree node the quantity hangs on — a bin node or a handling-unit node | RAW(16) | Key |
| 4 | VSI | Virtual stock indicator | CHAR(1) | Key |
| 5 | UNIT | Unit of measure of the stock quantity — part of the key, so one stock item can carry several rows | UNIT(3) | Key |
| 6 | QUAN | Physical stock quantity at this node | QUAN(31,14) | |
| 7 | LFT | Width value of the node in the LIME tree (nested-set bookkeeping) | DEC(31) | |
| 8 | LVL | Level of the node within the LIME tree | INT4(10) | |
| 9 | IDX_STOCK | Index of the key table the stock entry belongs to | CHAR(3) | |
| 10 | TYPE_PARENT | Object type of the parent node | CHAR(1) | |
| 11 | INV_BLOCK_IND | Inventory blocking indicator | CHAR(1) | |
| 12 | TS_LAST_ABS_POST | Time of the last absolute posting against the node — a long-form DEC(21,7) UTC stamp, not the DEC(15) shape the generated range filter parses | DEC(21,7) |
Field provenance: hand-curated. 5 key fields.
Boilerplate SQL
Starting point for reading the replicated copy of /LIME/NQUANon Databricks — the client anchor is already in place, the namespaced name is rendered as the underscore bronze name replication targets conventionally land it under, and any RAW16 GUID column selects a hex rendering alongside the raw value. Set your Unity Catalog location, schema, and filter values below; they’re substituted into the SQL and the copy button.
7 parameters not filled: <catalog>, <schema>, <client>, <GUID_STOCK>, <GUID_PARENT>, <VSI>, <UNIT>
-- ============================================================
-- Table : /LIME/NQUAN — The LIME stock quantities table — the physical quantity of a stock item hanging on one node of the location/handling-unit tree, one row per stock GUID per node per unit of measure
-- Purpose: Column-selected read of /LIME/NQUAN — auto-generated from field metadata
-- Grain : One row per client + GUID_STOCK + GUID_PARENT + VSI + UNIT
-- Caution: Rows hang on nodes of the LIME tree — never SUM across rows without resolving GUID_PARENT first, or nested handling units are counted more than once
-- Notes : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /LIME/NQUAN; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as lime_nquan — adjust to your landing convention (see quirks #namespace-slashes). RAW16 GUID columns are joined raw; the hex aliases are for display only (#guid-keys). Timestamps flagged UTC are DEC(15) yyyymmddhhmmss values in UTC, not warehouse local time (#utc-timestamps).
-- ============================================================
SELECT
t.MANDT AS "Client",
t.GUID_STOCK AS "Stock GUID — joins to the quant attribute rows",
lower(hex(t.GUID_STOCK)) AS "Stock GUID — joins to the quant attribute rows (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.GUID_PARENT AS "GUID of the tree node the quantity hangs on — a bin node or a handling-unit node",
lower(hex(t.GUID_PARENT)) AS "GUID of the tree node the quantity hangs on — a bin node or a handling-unit node (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.VSI AS "Virtual stock indicator",
t.UNIT AS "Unit of measure of the stock quantity — part of the key, so one stock item can carry several rows",
t.QUAN AS "Physical stock quantity at this node",
t.LFT AS "Width value of the node in the LIME tree (nested-set bookkeeping)",
t.LVL AS "Level of the node within the LIME tree",
t.IDX_STOCK AS "Index of the key table the stock entry belongs to",
t.TYPE_PARENT AS "Object type of the parent node",
t.INV_BLOCK_IND AS "Inventory blocking indicator",
t.TS_LAST_ABS_POST AS "Time of the last absolute posting against the node — a long-form DEC(21,7) UTC stamp, not the DEC(15) shape the generated range filter parses"
FROM <catalog>.<schema>.lime_nquan t
WHERE
t.MANDT = '<client>' -- client filter — drop on single-client systems
-- AND t.GUID_STOCK = unhex('<GUID_STOCK>') -- pass the 32-character hex form
-- AND t.GUID_PARENT = unhex('<GUID_PARENT>') -- pass the 32-character hex form
-- AND t.VSI = '<VSI>'
-- AND t.UNIT = '<UNIT>'
ORDER BY t.GUID_STOCK;Verified August 2026
Landing conventions differ — see namespaced names in a lakehouse.
Relationships
Diagram of 1-hop neighbors — join details below. GUID joins and text-table joins are highlighted; they’re the joins newcomers most often get wrong.
Join details
ON lime_nquan.MANDT = scwm_quan.MANDT AND lime_nquan.GUID_STOCK = scwm_quan.GUID_STOCK AND lime_nquan.GUID_PARENT = scwm_quan.GUID_PARENT -- RAW16 GUID equality — join raw; hex is for display/conformance onlyON lime_nquan.MANDT = lime_ntree.MANDT AND lime_nquan.GUID_PARENT = lime_ntree.GUID -- RAW16 GUID equality — join raw; hex is for display/conformance only · the join that turns a quantity row into a place — resolve the node before summing anythingthe join that turns a quantity row into a place — resolve the node before summing anything
Transaction codes that touch this table
Curated: the EWM transactions an analyst would trace back to these rows, and how each one touches them.
R read · W write · R/W read + write
- /SCWM/ADGIPost an unplanned goods issue — take stock out of the warehouse without a delivery behind itWrite accessCreatestock-hu
- /SCWM/PACKGeneral packing — build, repack, and unpack handling units at a work centerRead accessChangestock-hu
- /SCWM/POSTPosting change — change a stock attribute in place (stock type, owner, entitled party, batch) without moving the goodsWrite accessCreatestock-hu
More Stock & Handling Units tables
- /LIME/NTREEThe LIME tree structure — one row per node of the location and handling-unit hierarchy stock hangs on, with its object type, its parent node, and the nested-set interval bookkeeping the engine walks the tree with
- /SCWM/AQUAAvailable quants — the stock that warehouse task creation can actually consume, with the bin, handling unit, product, stock type, batch, owner, and entitled party all resolved onto one row
- /SCWM/HUHDRHandling unit header — one row per HU with its external number, packaging material, current storage type and bin, weights, volumes, and the entitled party whose stock it holds
- /SCWM/QUANQuant attributes — the descriptive side of a stock item (units, weight, volume, goods-receipt time, shelf life, country of origin, and the document reference for special stock), keyed by the stock GUID