Skip to content
EWM Reference

/SCWM/AQUA

transactionGUID key

Available 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

Grain note

Available quantity, not on-hand: stock already committed to open warehouse tasks is excluded, so AQUA and the LIME quantities do not tie out row for row

Notes

The practical stock table for analytics: it carries the stock identity columns /SCWM/QUAN keeps inside unexpanded includes. Described as available quants deliberately — the "fixed bins" description circulating in third-party table dumps is wrong. There is no GUID_HU column: the handling unit is carried as the readable HUIDENT, which is how this reference joins it to the HU header.

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.

Structural facts — how the table is keyed, not a trap by itself

Semantic key
Every non-client key column is readable business data — LGNUM plus a bin, task, or order number. Joins run on the columns you can see (see the quirks guide).

Join & extract hazards — verify before you rely on this

GUID key
Every non-client key column is a GUID — RAW(16) on the /SCWM, /SCDL, /LIME, and /SCMB tables, and the CHAR(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.
In field listings, the Key chip marks a primary-key field, and UTC marks a timestamp stored in UTC rather than warehouse-local time.

Fields

18 fields · 3 key

18 fields.

Table fields: position, field name, description, data type, and flags. 18 fields.
#FieldDescriptionTypeFlags
1MANDTClientCLNT(3)
Key
2GUID_PARENTGUID of the parent node (a bin or a handling unit) the available quant sits underRAW(16)
Key
3GUID_STOCKStock GUID — joins to the quant attribute rowsRAW(16)
Key
4LGNUMEWM warehouse numberCHAR(4)
5LGTYPStorage type of the quant's locationCHAR(4)
6LGPLAStorage bin the quant sits inCHAR(18)
7HUIDENTExternal handling-unit identification the stock sits in — the readable join to the HU headerCHAR(20)
8MATIDProduct GUID (RAW16 form)RAW(16)
9CATStock type or category, such as unrestricted versus blockedCHAR(2)
10DOCCATDocument category for document-related stockCHAR(3)
11STOCK_USAGEStock usage classificationCHAR(1)
12OWNERStock owner (business partner)CHAR(10)
13ENTITLEDParty entitled to dispose of the stockCHAR(10)
14CHARGBatch number in its readable formCHAR(10)
15QUANAvailable quantity usable for warehouse task creationQUAN(31,14)
16UNITBase unit of the available quantityUNIT(3)
17VFDATShelf-life expiration or best-before dateDATS(8)
18WDATUGoods receipt date and timeDEC(15)
UTCFilter date

Field provenance: hand-curated. 3 key fields.

Boilerplate SQL

Starting point for reading the replicated copy of /SCWM/AQUAon 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.

Query parameters

7 parameters not filled: <catalog>, <schema>, <client>, <GUID_PARENT>, <GUID_STOCK>, <TS_FROM>, <TS_TO>

-- ============================================================
-- Table  : /SCWM/AQUA — Available 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
-- Purpose: Column-selected read of /SCWM/AQUA — auto-generated from field metadata
-- Grain  : One row per client + GUID_PARENT + GUID_STOCK
-- Caution: Available quantity, not on-hand: stock already committed to open warehouse tasks is excluded, so AQUA and the LIME quantities do not tie out row for row
-- Notes  : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /SCWM/AQUA; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as scwm_aqua — 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_PARENT AS "GUID of the parent node (a bin or a handling unit) the available quant sits under",
  lower(hex(t.GUID_PARENT)) AS "GUID of the parent node (a bin or a handling unit) the available quant sits under (hex)",  -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
  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.LGNUM AS "EWM warehouse number",
  t.LGTYP AS "Storage type of the quant's location",
  t.LGPLA AS "Storage bin the quant sits in",
  t.HUIDENT AS "External handling-unit identification the stock sits in — the readable join to the HU header",
  t.MATID AS "Product GUID (RAW16 form)",
  lower(hex(t.MATID)) AS "Product GUID (RAW16 form) (hex)",  -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
  t.CAT AS "Stock type or category, such as unrestricted versus blocked",
  t.DOCCAT AS "Document category for document-related stock",
  t.STOCK_USAGE AS "Stock usage classification",
  t.OWNER AS "Stock owner (business partner)",
  t.ENTITLED AS "Party entitled to dispose of the stock",
  t.CHARG AS "Batch number in its readable form",
  t.QUAN AS "Available quantity usable for warehouse task creation",
  t.UNIT AS "Base unit of the available quantity",
  t.VFDAT AS "Shelf-life expiration or best-before date",
  t.WDATU AS "Goods receipt date and time"  -- UTC
FROM <catalog>.<schema>.scwm_aqua t
WHERE
  t.MANDT = '<client>'  -- client filter — drop on single-client systems
  -- AND t.GUID_PARENT = unhex('<GUID_PARENT>')  -- pass the 32-character hex form
  -- AND t.GUID_STOCK = unhex('<GUID_STOCK>')  -- pass the 32-character hex form
  -- AND t.WDATU >= <TS_FROM>  -- UTC yyyymmddhhmmss — convert warehouse-local dates first (#utc-timestamps)
  -- AND t.WDATU <= <TS_TO>
ORDER BY t.GUID_PARENT;

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

  • /SCWM/AQUA/SCWM/QUANGUID join · 1:1
    ON scwm_aqua.MANDT = scwm_quan.MANDT AND scwm_aqua.GUID_STOCK = scwm_quan.GUID_STOCK AND scwm_aqua.GUID_PARENT = scwm_quan.GUID_PARENT -- RAW16 GUID equality — join raw; hex is for display/conformance only
  • /SCWM/AQUA/SCWM/HUHDRforeign key · N:1
    ON scwm_aqua.MANDT = scwm_huhdr.MANDT AND scwm_aqua.HUIDENT = scwm_huhdr.HUIDENT AND scwm_aqua.LGNUM = scwm_huhdr.LGNUM
  • /SCWM/AQUA/SCWM/LAGPforeign key · N:1
    ON scwm_aqua.MANDT = scwm_lagp.MANDT AND scwm_aqua.LGPLA = scwm_lagp.LGPLA AND scwm_aqua.LGNUM = scwm_lagp.LGNUM
  • /SCWM/AQUA/SAPAPO/MATKEYGUID join · N:1
    ON scwm_aqua.MANDT = sapapo_matkey.MANDT AND scwm_aqua.MATID = sapapo_matkey.MATID -- the /SCWM side is RAW(16) and MATKEY keys the CHAR 22 compressed form — convert before comparing; this is not a raw equality

    the /SCWM side is RAW(16) and MATKEY keys the CHAR 22 compressed form — convert before comparing; this is not a raw equality

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

Browse more Stock & Handling Units tables

More Stock & Handling Units tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by SAP. SAP, SAP S/4HANA, and SAP Extended Warehouse Management are trademarks or registered trademarks of SAP SE.