SAP Reference

/LIME/PI_DOC_IT

transaction S/4HANA status: Active

Physical Inventory Document Items

What the badges mean
S/4HANA status: Active
Active and unchanged in S/4HANA.
S/4HANA status: Deprecated
Still readable today, but no longer SAP's strategic path — plan around it.
S/4HANA status: Replaced
Replaced by a new persistence in S/4HANA; the classic name may still answer reads (see read mechanism).
S/4HANA status: Migrating to IBP
Planning scope is moving from APO toward IBP.
S/4HANA status: Active (StRM) · Replaced (EWM)
Path-dependent: active with SAP Stock Room Management, replaced where EWM is the warehouse path.
S/4HANA status: Replaced · Compat View
Compatibility view: the classic table name is redirected to a view over the new persistence — see how the physical model moved.
S/4HANA status: Active · Proxy View
Proxy view: reads route through NSDM proxy/CDS views — see how the physical model moved.
master
Data class: what the table holds — master data, transaction documents, org structure, config, or texts (one row per language — see the quirks guide).
Linked type codes

CLNT — the client key; filter it explicitly and carry it through every join.

NUMC — fixed-width numeric text; keep it a string and keep the leading zeros.

DATS, TIMS — character date (YYYYMMDD) and time (HHMMSS), zero-filled when initial.

CURR, CUKY, QUAN, UNIT — amounts and quantities, meaningful only beside the currency key or unit that qualifies them.

LANG — a language key in a text table — one row per language.

In field listings, K marks a primary-key field, and linked type codes in the Type column jump to the matching quirks-guide section.

Fields

6 fields · 6 key

The join key is all 6 key fields together — matching on any single one fans out. See composite keys in the quirks guide.

6 fields.

Table fields: key flag, field name, description, data type (linked to the data quirks guide where the type carries a known trap), length, and check-table references. 6 fields.
KeyFieldDescriptionTypeLengthReferences
Primary keyMANDTClientCLNT3
Primary keyGUID_DOCDocument GUIDRAW16
Primary keyITEM_NOItem NumberNUMC6
Primary keyLINE_IDXLine IndexINT4
Primary keyCHANGE_SEQChange SequenceINT4
Primary keyITEM_TYPEItem TypeCHAR2

Linked type codes in the Type column jump to the matching section of the SAP data quirks guide.

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading /LIME/PI_DOC_IT on Databricks. Set your Unity Catalog location and filter values below — they’re substituted into the SQL and the copy button.

Query parameters

3 parameters not filled: <catalog>, <schema>, <MANDT>

-- ============================================================
-- Table  : /LIME/PI_DOC_IT Physical Inventory Document Items
-- Purpose: Column-selected read of /LIME/PI_DOC_IT — auto-generated from field metadata
-- Grain  : One row per GUID_DOC + ITEM_NO + LINE_IDX + CHANGE_SEQ + ITEM_TYPE
-- Notes  : Auto-generated skeleton. For multi-table transaction query patterns, see the linked t-codes on this page. Set catalog/schema to your Unity Catalog location; fill remaining placeholders (<...>) for your tenant.
-- ============================================================
SELECT
  p.MANDT      AS "Client",
  p.GUID_DOC   AS "Document GUID",
  p.ITEM_NO    AS "Item Number",
  p.LINE_IDX   AS "Line Index",
  p.CHANGE_SEQ AS "Change Sequence",
  p.ITEM_TYPE  AS "Item Type"
FROM <catalog>.<schema>.`/lime/pi_doc_it` p
WHERE
  p.MANDT = '<MANDT>'
ORDER BY p.GUID_DOC;

Verified August 2026

Relationships

Diagram of 1-hop neighbors — join details below.

Transaction Codes That Use This Table

No t-code mappings populated for this table yet.

Browse more EWM tables

More Extended Warehouse Management tables