Skip to content
JDE Reference

F41021

masterAlso in JDE World

Item location — on-hand, committed, and inbound quantities by item, branch, location, and lot

What the badges mean
Superseded
Superseded — a newer table has replaced it, but older scripts still read this one.
Also in JDE World
Also present in JDE World A9.x on the same table name.
master
Data class: what the table holds — master data, transaction documents, control/setup values, history, or a workfile.
Read/write access
Access mode: how the paired program reads or writes this table — R (read), W (write), or R/W (both).
No lifecycle badge means the table is current and not documented in JDE World. In field listings, K marks a primary-key field.

Fields

26 fields · 4 key

26 fields.

Table fields: key flag, field name, DD alias, description, data type, length, and quirk flags (Julian date, implied decimals, padded string, UDC decode). 26 fields.
KeyFieldAliasDescriptionTypeLengthFlags
Primary keyLIITMITMShort item number - the internal numeric item keyNumeric8
Primary keyLIMCUMCUBusiness unit / branch plant (right-justified, space-padded to 12)String12
Primary keyLILOCNLOCNStorage location within the branch plantString20
Primary keyLILOTNLOTNLot or serial numberString30
LIPBINPBINFlags the primary location for the item at this branchCharacter1
LIGLPTGLPTG/L class code for this location (overrides branch/item value)String4
LILOTSLOTSLot status code - blank means approvedCharacter1
LILRCJLRCJDate of last receipt into this locationNumeric (DD type: Date)6
LIPQOHPQOHQuantity on hand in primary UOMNumeric15
LIPBCKPBCKQuantity on backorderNumeric15
LIPREQPREQQuantity on open purchase ordersNumeric15
LIQWBOQWBOQuantity expected from open work ordersNumeric15
LIOT1POT1POther quantity 1 (primary UOM)Numeric15
LIOT2POT2POther quantity 2 (primary UOM)Numeric15
LIOT1AOT1AOther purchasing quantity 1Numeric15
LIHCOMHCOMQuantity hard committed to specific locations/lotsNumeric15
LIPCOMPCOMQuantity soft committed by sales/work ordersNumeric15
LIFCOMFCOMQuantity committed to future dated ordersNumeric15
LIFUN1FUN1Quantity soft committed to work ordersNumeric15
LIQOWOQOWOQuantity hard committed to work ordersNumeric15
LIQTTRQTTRQuantity in transit between branchesNumeric15
LIQTINQTINQuantity in inspectionNumeric15
LIQONLQONLQuantity on loan to manufacturingNumeric15
LIQTRIQTRIInbound warehouse-management quantityNumeric15
LIQTROQTROOutbound warehouse-management quantityNumeric15
LINCDJNCDJNext cycle count dateNumeric (DD type: Date)6

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading F41021 on Databricks — Julian dates, implied decimals, and padded strings are already converted. Set your Unity Catalog location and filter values below; they’re substituted into the SQL and the copy button.

Query parameters

4 parameters not filled: <catalog>, <schema_data>, <ITM>, <MCU>

-- ============================================================
-- Table  : F41021 Item location — on-hand, committed, and inbound quantities by item, branch, location, and lot
-- Purpose: Column-selected read of F41021 — auto-generated from field metadata
-- Grain  : One row per LIITM + LIMCU + LILOCN + LILOTN
-- Notes  : Auto-generated skeleton. Julian dates (CYYDDD) are converted to DATE and implied-decimal amounts are scaled (verify decimals in F9210); padded business-unit/UDC keys are TRIMmed. Audit columns (…USER/…PID/…UPMJ) are omitted — see the quirks guide. Set catalog/schema to your Unity Catalog location; fill remaining placeholders (<...>) for your tenant.
-- ============================================================
SELECT
  loc.LIITM AS "Short item number - the internal numeric item key",
  TRIM(loc.LIMCU) AS "Business unit / branch plant (right-justified, space-padded to 12)",
  loc.LILOCN AS "Storage location within the branch plant",
  loc.LILOTN AS "Lot or serial number",
  loc.LIPBIN AS "Flags the primary location for the item at this branch",
  loc.LIGLPT AS "G/L class code for this location (overrides branch/item value)",
  loc.LILOTS AS "Lot status code - blank means approved",
  CASE WHEN loc.LILRCJ IS NULL OR loc.LILRCJ = 0 THEN NULL ELSE DATE_ADD(MAKE_DATE(1900 + CAST(loc.LILRCJ AS INT) DIV 1000, 1, 1), CAST(loc.LILRCJ AS INT) % 1000 - 1) END AS "Date of last receipt into this location",  -- CYYDDD Julian → DATE
  loc.LIPQOH AS "Quantity on hand in primary UOM",
  loc.LIPBCK AS "Quantity on backorder",
  loc.LIPREQ AS "Quantity on open purchase orders",
  loc.LIQWBO AS "Quantity expected from open work orders",
  loc.LIOT1P AS "Other quantity 1 (primary UOM)",
  loc.LIOT2P AS "Other quantity 2 (primary UOM)",
  loc.LIOT1A AS "Other purchasing quantity 1",
  loc.LIHCOM AS "Quantity hard committed to specific locations/lots",
  loc.LIPCOM AS "Quantity soft committed by sales/work orders",
  loc.LIFCOM AS "Quantity committed to future dated orders",
  loc.LIFUN1 AS "Quantity soft committed to work orders",
  loc.LIQOWO AS "Quantity hard committed to work orders",
  loc.LIQTTR AS "Quantity in transit between branches",
  loc.LIQTIN AS "Quantity in inspection",
  loc.LIQONL AS "Quantity on loan to manufacturing",
  loc.LIQTRI AS "Inbound warehouse-management quantity",
  loc.LIQTRO AS "Outbound warehouse-management quantity",
  CASE WHEN loc.LINCDJ IS NULL OR loc.LINCDJ = 0 THEN NULL ELSE DATE_ADD(MAKE_DATE(1900 + CAST(loc.LINCDJ AS INT) DIV 1000, 1, 1), CAST(loc.LINCDJ AS INT) % 1000 - 1) END AS "Next cycle count date"  -- CYYDDD Julian → DATE
FROM <catalog>.<schema_data>.f41021 loc
WHERE
  loc.LIITM = <ITM>
  -- AND loc.LIMCU = '<MCU>'
ORDER BY loc.LIITM;

Verified September 2026

Relationships

Diagram of 1-hop neighbors — join details below. UDC decode edges point coded fields at their F0005 lookup.

Join details

  • F41021F4101foreign key · N:1
    ON f41021.LIITM = f4101.IMITM

Programs That Use This Table

R read · W write · R/W read + write

Primary programs

Secondary programs

More Inventory Management 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 Oracle. Oracle, JD Edwards, and EnterpriseOne are registered trademarks of Oracle and/or its affiliates.