Skip to content
JDE Reference

P4602

Interactive

Location Detail Maintenance — the interactive application for reviewing and correcting location detail records: what is stored in each warehouse location, in which units of measure, and how much capacity is committed

Lineage hook

Rows written by P4602 carry …PID = 'P4602' in their audit columns — a ready-made marker for isolating the records this program produced. See the audit-columns guide

Notes

F4602 is Warehouse Management's working view of inventory by location; R46820 builds it initially from existing balances.

Boilerplate SQL

Databricks SQL

Starting point for querying the tables behind this program. 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>

-- ============================================================
-- Program: P4602 Location Detail Maintenance — the interactive application for reviewing and correcting location detail records: what is stored in each warehouse location, in which units of measure, and how much capacity is committed
-- Purpose: Location Detail Maintenance — the interactive application for reviewing and correcting location detail records: what is stored in each warehouse location, in which units of measure, and how much capacity is committed — auto-generated boilerplate from program-table-map
-- Grain  : F4602 × F4100, F41021 — 1:N joins yield one row per detail line
-- Tables : F4602, F4100, F41021
-- Notes  : Auto-generated skeleton. Julian dates are converted to DATE and implied-decimal amounts are scaled (verify decimals in F9210). 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
  h.IFITM AS "Short item number stored in the location.",
  TRIM(h.IFMCU) AS "Branch/plant (warehouse) the location belongs to.",
  h.IFLOCN AS "Warehouse location (bin) this row describes.",
  h.IFLOTN AS "Lot/serial number of the stock in the location.",
  h.IFLDSQ AS "Sequence distinguishing multiple detail rows for the same item/location/lot — the same key F4600/F4611 carry in their from/to sequence fields."
FROM <catalog>.<schema_data>.f4602 h
LEFT JOIN <catalog>.<schema_data>.f4100 f
  ON f.LMLOCN = h.IFLOCN
 AND f.LMMCU = h.IFMCU
LEFT JOIN <catalog>.<schema_data>.f41021 loc
  ON loc.LIITM = h.IFITM
 AND loc.LIMCU = h.IFMCU
 AND loc.LILOCN = h.IFLOCN
 AND loc.LILOTN = h.IFLOTN
WHERE
  h.IFITM = <ITM>
  AND h.IFMCU = '<MCU>'
ORDER BY h.IFITM;

Tables Used by This Program

How these tables connect — join details in the list below.

Join details

  • F4602F4100foreign key · N:1
    ON f4602.IFLOCN = f4100.LMLOCN

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.