Skip to content
JDE Reference

P3002

Interactive

Bill of Material Revisions — the screen where engineering builds and maintains bills of material: components, quantities per, effectivity dates, and substitutes.

Lineage hook

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

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: P3002 Bill of Material Revisions — the screen where engineering builds and maintains bills of material: components, quantities per, effectivity dates, and substitutes.
-- Purpose: Bill of Material Revisions — the screen where engineering builds and maintains bills of material: components, quantities per, effectivity dates, and substitutes. — auto-generated boilerplate from program-table-map
-- Grain  : F3002 × F4101, F4102 — 1:N joins yield one row per detail line
-- Tables : F3002, F4101, F4102
-- 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.IXTBM AS "Bill type — M is the standard manufacturing bill; other UDC values cover rework, spare parts, and planning bills.",
  h.IXKIT AS "Short item number of the parent being built — the top of this BOM line.",
  TRIM(h.IXMMCU) AS "Branch/plant that owns this bill — BOMs are branch-specific in JDE.",
  h.IXSBNT / POWER(10, 2) AS "Sequence that orders substitute items for a component; 0 for the primary component line.",  -- implied decimals: 2 (verify in F9210)
  h.IXBQTY AS "Batch quantity of the parent that the quantity-per is stated against; part of the key, so one item can carry separate bills per batch size — implied decimals vary by setup.",
  h.IXCOBY AS "Classifies the line as a component, co-product, by-product, or intermediate.",
  h.IXCPNB / POWER(10, 2) AS "System-assigned BOM component line number that uniquifies lines within a parent/branch/type/batch key.",  -- implied decimals: 2 (verify in F9210)
  ib.IBITM AS "Short item number - the internal numeric item key",
  TRIM(ib.IBMCU) AS "Business unit / branch plant (right-justified, space-padded to 12)"
FROM <catalog>.<schema_data>.f3002 h
LEFT JOIN <catalog>.<schema_data>.f4101 im
  ON im.IMITM = h.IXITM
 AND im.IMITM = h.IXKIT
LEFT JOIN <catalog>.<schema_data>.f4102 ib
  ON 1 = 1  -- TODO: define join condition (no shared aliases detected)
ORDER BY h.IXTBM;

2 parameters not filled: <catalog>, <schema_data>

Tables Used by This Program

How these tables connect. Nodes are clickable.

Join details

  • F4102F4101foreign key · N:1
    ON f4102.IBITM = f4101.IMITM
  • F3002F4101foreign key · N:1
    ON f3002.IXITM = f4101.IMITM
  • F3002F4101foreign key · N:1
    ON f3002.IXKIT = f4101.IMITM