EWM Reference
/LIME/PI_PAR_BIZ
transactionMixed keyPhysical inventory parent business keys — the readable location behind a document item's parent object: warehouse, storage type, bin, handling unit, resource, or transportation unit
Identity
Module: Physical InventoryBronze: lime_pi_par_biz
Notes
One of the two tables that make counting data joinable: the document item carries GUIDs, and this row carries the same parent object in readable columns. The columns are sparse by design — a bin count fills the storage type and bin, an HU count fills the HU identification, and the plant and storage location columns fill only where the count reaches non-EWM stock.
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
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
21 fields · 6 key
21 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 | LGNUM | Warehouse number of the counted location | CHAR(4) | |
| 8 | LGTYP | Storage type of the counted location | CHAR(4) | |
| 9 | LGPLA | Storage bin counted — the readable bin behind the item's parent GUID | CHAR(18) | |
| 10 | LGNUM_HU | Warehouse number of the counted handling unit | CHAR(4) | |
| 11 | HUIDENT | External identification of the counted handling unit | CHAR(20) | |
| 12 | VHI | Flag: the handling unit is a virtual one | CHAR(1) | |
| 13 | RSRC | Resource the counted stock was sitting on, where stock was counted on a resource | CHAR(18) | |
| 14 | TU_NUM | Transportation unit the counted stock was on | CHAR(18) | |
| 15 | LGNUM_VIEW | Warehouse number view used for global stock | CHAR(1) | |
| 16 | SSCC | Serial shipping container code of the counted handling unit | NUMC(18) | |
| 17 | WERKS | Plant, where the count reaches stock outside the warehouse structure | CHAR(4) | |
| 18 | LGORT | Storage location of that stock | CHAR(4) | |
| 19 | LOCID | Location GUID of the counted place | RAW(16) | |
| 20 | PARTNER | Partner the location belongs to | CHAR(10) | |
| 21 | PARTNER_ROLE | Role that partner plays | CHAR(2) |
Field provenance: hand-curated. 6 key fields.
Boilerplate SQL
Starting point for reading the replicated copy of /LIME/PI_PAR_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_PAR_BIZ — Physical inventory parent business keys — the readable location behind a document item's parent object: warehouse, storage type, bin, handling unit, resource, or transportation unit
-- Purpose: Column-selected read of /LIME/PI_PAR_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_PAR_BIZ; slashes aren't legal in unquoted Databricks identifiers, so replication targets conventionally land it as lime_pi_par_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.LGNUM AS "Warehouse number of the counted location",
t.LGTYP AS "Storage type of the counted location",
t.LGPLA AS "Storage bin counted — the readable bin behind the item's parent GUID",
t.LGNUM_HU AS "Warehouse number of the counted handling unit",
t.HUIDENT AS "External identification of the counted handling unit",
t.VHI AS "Flag: the handling unit is a virtual one",
t.RSRC AS "Resource the counted stock was sitting on, where stock was counted on a resource",
t.TU_NUM AS "Transportation unit the counted stock was on",
t.LGNUM_VIEW AS "Warehouse number view used for global stock",
t.SSCC AS "Serial shipping container code of the counted handling unit",
t.WERKS AS "Plant, where the count reaches stock outside the warehouse structure",
t.LGORT AS "Storage location of that stock",
t.LOCID AS "Location GUID of the counted place",
lower(hex(t.LOCID)) AS "Location GUID of the counted place (hex)", -- display rendering of the RAW16 GUID — join on the raw column; see quirks guide #guid-keys
t.PARTNER AS "Partner the location belongs to",
t.PARTNER_ROLE AS "Role that partner plays"
FROM <catalog>.<schema>.lime_pi_par_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_par_biz.MANDT AND lime_pi_doc_it.GUID_DOC = lime_pi_par_biz.GUID_DOC AND lime_pi_doc_it.ITEM_NO = lime_pi_par_biz.ITEM_NO AND lime_pi_doc_it.LINE_IDX = lime_pi_par_biz.LINE_IDX AND lime_pi_doc_it.CHANGE_SEQ = lime_pi_par_biz.CHANGE_SEQ AND lime_pi_doc_it.ITEM_TYPE = lime_pi_par_biz.ITEM_TYPE -- RAW16 GUID equality — join raw; hex is for display/conformance only · the readable location behind the item's parent GUIDthe readable location behind the item's parent GUID
ON lime_pi_par_biz.MANDT = scwm_lagp.MANDT AND lime_pi_par_biz.LGPLA = scwm_lagp.LGPLA AND lime_pi_par_biz.LGNUM = scwm_lagp.LGNUM -- bins are unique only within a warehouse — LGNUM belongs in the join even though this table does not key on itbins are unique only within a warehouse — LGNUM belongs in the join even though this table does not key on it
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
More Physical Inventory tables
- /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
- /LIME/PI_IT_BIZPhysical 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
- /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