Skip to content
JDE Reference

P46010

Interactive

Item Profile Revisions — the setup application that defines each item's warehouse behavior: default pick/replenishment zones, process groups for movement instructions, and overflow handling

Lineage hook

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

Notes

An item needs a profile before Warehouse Management will generate requests for it.

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
-- ============================================================
-- Program: P46010 Item Profile Revisions — the setup application that defines each item's warehouse behavior: default pick/replenishment zones, process groups for movement instructions, and overflow handling
-- Purpose: Item Profile Revisions — the setup application that defines each item's warehouse behavior: default pick/replenishment zones, process groups for movement instructions, and overflow handling — auto-generated boilerplate from program-table-map
-- Grain  : F46010 × F4101, F4100 — 1:N joins yield one row per detail line
-- Tables : F46010, F4101, F4100
-- 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
  TRIM(h.IPMCU) AS "Branch/plant the profile applies to.",
  h.IPITM AS "Short item number the profile applies to.",
  f.LMLOCN AS "Storage location within the branch, formatted per the branch location structure."
FROM <catalog>.<schema_data>.f46010 h
LEFT JOIN <catalog>.<schema_data>.f4101 im
  ON im.IMITM = h.IPITM
LEFT JOIN <catalog>.<schema_data>.f4100 f
  ON f.LMMCU = h.IPMCU
WHERE
  h.IPMCU = '<MCU>'
  AND h.IPITM = <ITM>
ORDER BY h.IPMCU;

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

Tables Used by This Program

How these tables connect. Nodes are clickable.

Join details

  • F46010F4101foreign key · N:1
    ON f46010.IPITM = f4101.IMITM