EWM Reference
/SCWM/PI_CREATE
CreateCreate physical inventory documents — raise the counting work for a set of bins, handling units, or products
Tables behind this transaction
Curated: these are the tables an analyst reads to see what this transaction did, and how it touches each of them. Every table page carries its own field list and Databricks SQL.
How these tables connect — join details in the list below. GUID joins and text-table joins are highlighted.
Join details
ON lime_pi_loghead.MANDT = lime_pi_doc_it.MANDT AND lime_pi_loghead.GUID_DOC = lime_pi_doc_it.GUID_DOC -- the counting document's readable year and number live only on the header — every item row carries the GUID alone, so the join runs on the raw GUID column with hex reserved for displaythe counting document's readable year and number live only on the header — every item row carries the GUID alone, so the join runs on the raw GUID column with hex reserved for display
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_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
R read · W write · R/W read + write
Primary 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 wholeWrite accessMixed keytransaction
- /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 forWrite accessGUID keytransaction
Secondary tables
- /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 inWrite accessMixed keytransaction
- /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 unitWrite accessMixed keytransaction
- /SCWM/AQUAAvailable 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 rowRead accessGUID keytransaction