Fusion Reference

EGP_ITEM_REVISIONS_B

Product: EGPmasterPer inventory org

Item revisions — one row per revision level of an item in an organization, with effectivity and implementation dates and the change-order line that introduced it

Module: Product MasterInventory-org partitioned (ORGANIZATION_ID)

Notes

REVISION_ID is the surrogate key; the business key is item + org + revision. No BICC extract data store covers revisions in the documented catalog — the OTBI Item Revisions subject area is the delivered reporting path (see the extract map verdicts in the plan doc).

What the badges mean

master: Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.

Fields

10 fields · 4 key

Table fields: position, field name, description, data type, and flags. 10 fields.
#	Field	Description	Type	Flags
1	REVISION_ID	Surrogate key of the revision	NUMBER	Key
2	INVENTORY_ITEM_ID	Item the revision belongs to — part of the natural unique key	NUMBER	Key
3	ORGANIZATION_ID	Organization the revision is defined in — part of the natural unique key	NUMBER	Key
4	REVISION	Revision code (A, B, C…) — part of the natural unique key	VARCHAR2	Key
5	EFFECTIVITY_DATE	When the revision becomes effective	DATE	Filter date
6	END_EFFECTIVITY_DATE	When the revision stops being effective	DATE
7	IMPLEMENTATION_DATE	When the revision was implemented — NULL while pending on a change order	DATE
8	REVISION_REASON	Reason code for creating the revision	VARCHAR2
9	CURRENT_PHASE_ID	Lifecycle phase of the revision	NUMBER
10	CHANGE_LINE_ID	Change-order line that created the revision	NUMBER

Field provenance: hand-curated. 4 key fields.

Boilerplate SQL

Starting point for reading the BICC-landed copy of EGP_ITEM_REVISIONS_Bon Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark (the column incremental BICC extracts key on) are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.

Query parameters

CatalogSchemaInventory org (ORGANIZATION_ID)Revision IDItem (INVENTORY_ITEM_ID)RevisionDate from (yyyy-mm-dd)Date to (yyyy-mm-dd)watermark

Include optional filters (6)

-- ============================================================
-- Table  : EGP_ITEM_REVISIONS_B — Item revisions — one row per revision level of an item in an organization, with effectivity and implementation dates and the change-order line that introduced it
-- Purpose: Column-selected read of EGP_ITEM_REVISIONS_B — auto-generated from field metadata
-- Grain  : One row per inventory org (ORGANIZATION_ID) + REVISION_ID + INVENTORY_ITEM_ID + REVISION
-- Notes  : Auto-generated skeleton for Oracle Fusion Cloud data landed in your lakehouse by a BICC extract — there is no SQL path to the SaaS database. Column names follow Oracle's table documentation — if your landed data still carries PVO attribute headers, map names first; see quirks #pvo-drift. Dates are real DATE/TIMESTAMP columns — no conversion needed. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts.
-- ============================================================
SELECT
  t.REVISION_ID AS "Surrogate key of the revision",
  t.INVENTORY_ITEM_ID AS "Item the revision belongs to — part of the natural unique key",
  t.ORGANIZATION_ID AS "Organization the revision is defined in — part of the natural unique key",
  t.REVISION AS "Revision code (A, B, C…) — part of the natural unique key",
  t.EFFECTIVITY_DATE AS "When the revision becomes effective",
  t.END_EFFECTIVITY_DATE AS "When the revision stops being effective",
  t.IMPLEMENTATION_DATE AS "When the revision was implemented — NULL while pending on a change order",
  t.REVISION_REASON AS "Reason code for creating the revision",
  t.CURRENT_PHASE_ID AS "Lifecycle phase of the revision",
  t.CHANGE_LINE_ID AS "Change-order line that created the revision"
FROM <catalog>.<schema>.EGP_ITEM_REVISIONS_B t
WHERE
  t.ORGANIZATION_ID = <inventory_org_id>  -- inventory org, NOT the business unit — see quirks guide #item-org-striping
  -- AND t.REVISION_ID = <REVISION_ID>
  -- AND t.INVENTORY_ITEM_ID = <INVENTORY_ITEM_ID>
  -- AND t.REVISION = '<REVISION>'
  -- AND t.EFFECTIVITY_DATE >= DATE '<DATE_FROM>'
  -- AND t.EFFECTIVITY_DATE <= DATE '<DATE_TO>'
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.REVISION_ID;

9 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <REVISION_ID>, <INVENTORY_ITEM_ID>, <REVISION>, <DATE_FROM>, <DATE_TO>, <watermark>

Relationships

1-hop neighbors — click a table to navigate there. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

EGP_ITEM_REVISIONS_BEGP_SYSTEM_ITEMS_Bforeign key · N:1
ON EGP_ITEM_REVISIONS_B.INVENTORY_ITEM_ID = EGP_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND EGP_ITEM_REVISIONS_B.ORGANIZATION_ID = EGP_SYSTEM_ITEMS_B.ORGANIZATION_ID

Browse more Product Mastertables →