/LIME/PI_IT_BIZ
transactionMixed keyPhysical inventory item business keys — the readable stock identity behind a document item: product, batch, stock type, owner and entitled party, plus the location and handling unit the stock was counted in
The stock-identity companion to the parent business keys, and the join surface for counting analytics: MATNR and MATID give the product in both forms, and CAT, OWNER, and ENTITLED say which slice of stock was counted. The same row also repeats the location columns, so a product-level count analysis does not have to join both business-key tables.
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
28 fields · 6 key
28 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | MANDT | Client | CLNT(3) | Key |
| 2 | GUID_DOC | GUID of the physical inventory document | RAW(16) | Key |
| 3 | ITEM_NO | Item number within the counting document | NUMC(6) | Key |
| 4 | LINE_IDX | Row index within the item | INT4(10) | Key |
| 5 | CHANGE_SEQ | Change version of the item | INT4(10) | Key |
| 6 | ITEM_TYPE | Line category of the item | CHAR(2) | Key |
| 7 | MATNR | Product number of the counted stock, in readable form | CHAR(40) | |
| 8 | MATID | Product GUID of the counted stock (RAW16 form) | RAW(16) | |
| 9 | CHARG | Batch number of the counted stock | CHAR(10) | |
| 10 | BATCHID | Batch GUID of the counted stock | RAW(16) | |
| 11 | CAT | Stock type of the counted stock, such as unrestricted against blocked | CHAR(2) | |
| 12 | STOCK_USAGE | Stock usage classification | CHAR(1) | |
| 13 | OWNER | Owner of the counted stock | CHAR(10) | |
| 14 | ENTITLED | Party entitled to dispose of the counted stock | CHAR(10) | |
| 15 | STOCK_DOCCAT | Special stock reference category, where the stock is document-related | CHAR(3) | |
| 16 | STOCK_DOCNO | Readable number of that reference document | CHAR(35) | |
| 17 | DOCCAT | Document category for document-related stock | CHAR(3) | |
| 18 | LGNUM_STOCK | Warehouse number the stock is managed in | CHAR(4) | |
| 19 | LGNUM | Warehouse number of the counted location | CHAR(4) | |
| 20 | LGTYP | Storage type of the counted location | CHAR(4) | |
| 21 | LGPLA | Storage bin the stock was counted in | CHAR(18) | |
| 22 | LGNUM_HU | Warehouse number of the handling unit the stock was counted in | CHAR(4) | |
| 23 | HUIDENT | External identification of that handling unit | CHAR(20) | |
| 24 | HU_PMAT | Packaging material of that handling unit | CHAR(40) | |
| 25 | HU_TYPE | Handling unit type | CHAR(4) | |
| 26 | SSCC | Serial shipping container code of the handling unit | NUMC(18) | |
| 27 | WERKS | Plant, where the count reaches stock outside the warehouse structure | CHAR(4) | |
| 28 | LGORT | Storage location of that stock | CHAR(4) |
Field provenance: hand-curated. 6 key fields.
Boilerplate SQL
Starting point for reading the replicated copy of /LIME/PI_IT_BIZon 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.
3 parameters not filled: <catalog>, <schema>, <client>
-- ============================================================
-- Table : /LIME/PI_IT_BIZ — Physical inventory item business keys — the readable stock identity behind a document item: product, batch, stock type, owner and entitled party, plus the location and handling unit the stock was counted in
-- Purpose: Column-selected read of /LIME/PI_IT_BIZ — auto-generated from field metadata
-- Grain : One row per client + GUID_DOC + ITEM_NO + LINE_IDX + CHANGE_SEQ + ITEM_TYPE
-- Notes : Auto-generated skeleton for SAP EWM data replicated into your lakehouse — it reads the replicated copy, not the SAP database. Source table /LIME/PI_IT_BIZ; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as lime_pi_it_biz — 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_DOC AS "GUID of the physical inventory document",
lower(hex(t.GUID_DOC)) AS "GUID of the physical inventory document (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.ITEM_NO AS "Item number within the counting document",
t.LINE_IDX AS "Row index within the item",
t.CHANGE_SEQ AS "Change version of the item",
t.ITEM_TYPE AS "Line category of the item",
t.MATNR AS "Product number of the counted stock, in readable form",
t.MATID AS "Product GUID of the counted stock (RAW16 form)",
lower(hex(t.MATID)) AS "Product GUID of the counted stock (RAW16 form) (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.CHARG AS "Batch number of the counted stock",
t.BATCHID AS "Batch GUID of the counted stock",
lower(hex(t.BATCHID)) AS "Batch GUID of the counted stock (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.CAT AS "Stock type of the counted stock, such as unrestricted against blocked",
t.STOCK_USAGE AS "Stock usage classification",
t.OWNER AS "Owner of the counted stock",
t.ENTITLED AS "Party entitled to dispose of the counted stock",
t.STOCK_DOCCAT AS "Special stock reference category, where the stock is document-related",
t.STOCK_DOCNO AS "Readable number of that reference document",
t.DOCCAT AS "Document category for document-related stock",
t.LGNUM_STOCK AS "Warehouse number the stock is managed in",
t.LGNUM AS "Warehouse number of the counted location",
t.LGTYP AS "Storage type of the counted location",
t.LGPLA AS "Storage bin the stock was counted in",
t.LGNUM_HU AS "Warehouse number of the handling unit the stock was counted in",
t.HUIDENT AS "External identification of that handling unit",
t.HU_PMAT AS "Packaging material of that handling unit",
t.HU_TYPE AS "Handling unit type",
t.SSCC AS "Serial shipping container code of the handling unit",
t.WERKS AS "Plant, where the count reaches stock outside the warehouse structure",
t.LGORT AS "Storage location of that stock"
FROM <catalog>.<schema>.lime_pi_it_biz t
WHERE
t.MANDT = '<client>' -- client filter — drop on single-client systems
ORDER BY t.GUID_DOC;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_pi_doc_it.MANDT = lime_pi_it_biz.MANDT AND lime_pi_doc_it.GUID_DOC = lime_pi_it_biz.GUID_DOC AND lime_pi_doc_it.ITEM_NO = lime_pi_it_biz.ITEM_NO AND lime_pi_doc_it.LINE_IDX = lime_pi_it_biz.LINE_IDX AND lime_pi_doc_it.CHANGE_SEQ = lime_pi_it_biz.CHANGE_SEQ AND lime_pi_doc_it.ITEM_TYPE = lime_pi_it_biz.ITEM_TYPE -- RAW16 GUID equality — join raw; hex is for display/conformance only · the readable stock identity behind the item's object GUIDthe readable stock identity behind the item's object GUID
ON lime_pi_it_biz.MANDT = scwm_lagp.MANDT AND lime_pi_it_biz.LGPLA = scwm_lagp.LGPLA AND lime_pi_it_biz.LGNUM = scwm_lagp.LGNUMON lime_pi_it_biz.MANDT = sapapo_matkey.MANDT AND lime_pi_it_biz.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 equalitythe /SCWM side is RAW(16) and MATKEY keys the CHAR 22 compressed form — convert before comparing; this is not a raw equality
ON lime_pi_it_biz.MANDT = scwm_huhdr.MANDT AND lime_pi_it_biz.HUIDENT = scwm_huhdr.HUIDENT AND lime_pi_it_biz.LGNUM_HU = scwm_huhdr.LGNUM -- the counted handling unit, joined on the readable HU number and its own warehouse column (LGNUM_HU), not on the location'sthe counted handling unit, joined on the readable HU number and its own warehouse column (LGNUM_HU), not on the location's
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/DIFF_ANALYZERThe difference analyzer — review, approve, and clear the differences a count produced against book stockRead accessReportphysical-inventory
- /SCWM/PI_CREATECreate physical inventory documents — raise the counting work for a set of bins, handling units, or productsWrite accessCreatephysical-inventory
- /SCWM/PI_PROCESSProcess a physical inventory document — enter counts, recount, and post the resultRead accessChangephysical-inventory
More Physical Inventory tables
- /LIME/PI_LOGHEADPhysical inventory document header — the log header that resolves a counting document's GUID to its readable year and number, its process type, and the warehouse it was raised for
- /LIME/PI_PAR_BIZPhysical inventory parent business keys — the readable location behind a document item's parent object: warehouse, storage type, bin, handling unit, resource, or transportation unit
- /LIME/PI_DOC_ITPhysical inventory document item — the countable line: its type and status, when it was created, counted, and posted, who counted it, the physical inventory area it belongs to, and the completeness flags that say whether a bin or handling unit was counted whole
- /LIME/PI_DOC_TBPhysical inventory quantities — the book and counted quantities behind a document item, one row per quantity parameter per unit of measure