JDE Reference
P4105
InteractiveCost Revisions — maintain item costs by cost method and branch/plant, generating variance journal entries on change
Lineage hook
Rows written by P4105 carry …PID = 'P4105' in their audit columns — a ready-made marker for isolating the records this program produced. See the audit-columns guide
Boilerplate SQL
Databricks SQLStarting 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: P4105 Cost Revisions — maintain item costs by cost method and branch/plant, generating variance journal entries on change
-- Purpose: Cost Revisions — maintain item costs by cost method and branch/plant, generating variance journal entries on change — auto-generated boilerplate from program-table-map
-- Grain : F4105 × F4101, F4102 — 1:N joins yield one row per detail line
-- Tables : F4105, 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.
-- Omitted: F0911 is cataloged for this program, but no verified join condition connects it to F4105, so it is left out of this skeleton. Add the join yourself using the key fields on each table's page.
-- ============================================================
SELECT
h.COITM AS "Short internal item number (8-digit numeric key).",
TRIM(h.COMCU) AS "Branch/plant (business unit); stored right-justified with leading blanks.",
h.COLOCN AS "Storage location within the branch, formatted per the branch location structure.",
h.COLOTN AS "Lot or serial number identifying the specific lot of stock.",
h.COLEDG AS "Cost method code (e.g. 01 last-in, 02 weighted average, 07 standard) selecting which cost applies."
FROM <catalog>.<schema_data>.f4105 h
LEFT JOIN <catalog>.<schema_data>.f4101 im
ON im.IMITM = h.COITM
LEFT JOIN <catalog>.<schema_data>.f4102 ib
ON ib.IBITM = h.COITM
AND ib.IBMCU = h.COMCU
WHERE
h.COITM = <ITM>
AND h.COMCU = '<MCU>'
ORDER BY h.COITM;Tables Used by This Program
How these tables connect — join details in the list below.
Loading relationship diagram…
R read · W write · R/W read + write
Secondary tables
- F0911General ledger transaction detail: every journal entry line with its account, G/L date, amount, batch, subledger, and source-document references.Write accesstransaction
- F4101Item master — one row per item with descriptions, units of measure, and category codes shared across branchesRead accessmaster
- F4102Item branch — branch/plant-level item attributes, planning parameters, and sourcing responsibilityRead accessmaster