JDE Reference

P0006

Interactive

Business Units — create and revise business units, the base organizational level for transaction tracking

Module: 00 · Foundation
Lineage hook

Rows written by P0006 carry …PID = 'P0006' 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: P0006 Business Units — create and revise business units, the base organizational level for transaction tracking
-- Purpose: Business Units — create and revise business units, the base organizational level for transaction tracking — auto-generated boilerplate from program-table-map
-- Grain  : F0006 × F0010 — 1:N joins yield one row per detail line
-- Tables : F0006, F0010
-- 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(mc.MCMCU) AS "Business unit number - the key (right-justified, space-padded to 12)",
  mc.MCDL01 AS "Business unit description",
  mc.MCDL02 AS "Description line 2"
FROM <catalog>.<schema_ctl>.f0006 mc
LEFT JOIN <catalog>.<schema_data>.f0010 f
  ON f.CCCO = mc.MCCO
WHERE
  mc.MCMCU = '<MCU>'
ORDER BY mc.MCMCU;

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

Tables Used by This Program

How these tables connect. Nodes are clickable.

Join details

  • F0006F0010foreign key · N:1
    ON f0006.MCCO = f0010.CCCO