Skip to content
EWM Reference

/LIME/PI_IT_BIZ

transactionMixed key

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

Identity
Module: Physical InventoryBronze: lime_pi_it_biz
Notes

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.

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

28 fields · 6 key

28 fields.

Table fields: position, field name, description, data type, and flags. 28 fields.
#FieldDescriptionTypeFlags
1MANDTClientCLNT(3)
Key
2GUID_DOCGUID of the physical inventory documentRAW(16)
Key
3ITEM_NOItem number within the counting documentNUMC(6)
Key
4LINE_IDXRow index within the itemINT4(10)
Key
5CHANGE_SEQChange version of the itemINT4(10)
Key
6ITEM_TYPELine category of the itemCHAR(2)
Key
7MATNRProduct number of the counted stock, in readable formCHAR(40)
8MATIDProduct GUID of the counted stock (RAW16 form)RAW(16)
9CHARGBatch number of the counted stockCHAR(10)
10BATCHIDBatch GUID of the counted stockRAW(16)
11CATStock type of the counted stock, such as unrestricted against blockedCHAR(2)
12STOCK_USAGEStock usage classificationCHAR(1)
13OWNEROwner of the counted stockCHAR(10)
14ENTITLEDParty entitled to dispose of the counted stockCHAR(10)
15STOCK_DOCCATSpecial stock reference category, where the stock is document-relatedCHAR(3)
16STOCK_DOCNOReadable number of that reference documentCHAR(35)
17DOCCATDocument category for document-related stockCHAR(3)
18LGNUM_STOCKWarehouse number the stock is managed inCHAR(4)
19LGNUMWarehouse number of the counted locationCHAR(4)
20LGTYPStorage type of the counted locationCHAR(4)
21LGPLAStorage bin the stock was counted inCHAR(18)
22LGNUM_HUWarehouse number of the handling unit the stock was counted inCHAR(4)
23HUIDENTExternal identification of that handling unitCHAR(20)
24HU_PMATPackaging material of that handling unitCHAR(40)
25HU_TYPEHandling unit typeCHAR(4)
26SSCCSerial shipping container code of the handling unitNUMC(18)
27WERKSPlant, where the count reaches stock outside the warehouse structureCHAR(4)
28LGORTStorage location of that stockCHAR(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.

Query parameters

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

  • /LIME/PI_DOC_IT/LIME/PI_IT_BIZGUID join · 1:1
    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 GUID

    the readable stock identity behind the item's object GUID

  • /LIME/PI_IT_BIZ/SCWM/LAGPforeign key · N:1
    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.LGNUM
  • /LIME/PI_IT_BIZ/SAPAPO/MATKEYGUID join · N:1
    ON 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 equality

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

  • /LIME/PI_IT_BIZ/SCWM/HUHDRforeign key · N:1
    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's

    the 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

Browse more Physical Inventory tables

More Physical Inventory 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.