EGP_ITEM_CAT_ASSIGNMENTS
Product: EGPmasterPer inventory orgThe item-to-category assignment — one row per item, organization, catalog (category set), and category; the bridge every category rollup crosses
The familiar EGP_ITEM_CATEGORIES name is a VIEW over this table in the Fusion dictionary — land this base table. The grain includes CATEGORY_ID: catalogs that allow multiple assignments produce several rows per item per catalog, so aggregate or filter to one catalog before joining to quantities or a rollup double-counts.
What the badges mean
- Product: EGP
- Product: the Oracle product family that owns the object — the short code Oracle's Tables and Views documentation lists as the object owner. Fusion is SaaS, so this isn't a database schema; there's no SQL path to the tables at all (see the quirks guide).
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
- BU-striped (ORG_ID)
- Rows are scoped to a business unit. The column is still named
ORG_ID, but in Fusion it means business unit, not the EBS operating unit — treat any migrated “operating unit” filter as suspect (see the quirks guide). - Per inventory org
- Rows are scoped to an inventory organization via
ORGANIZATION_ID— always pair it withINVENTORY_ITEM_IDon item-level joins (see the quirks guide). - Set / ledger / named-BU striped
- Some tables stripe by a named column instead of
ORG_ID: reference data set (SET_ID— see the quirks guide), ledger (LEDGER_IDon the GL journal tables), or a named business-unit column (PRC_BU_ID/REQ_BU_IDin procurement). The table page’s partition line names the column, and the generated SQL anchors on it — never treat these tables as unpartitioned. - Language-striped
- The table carries a
LANGUAGEcolumn (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to oneLANGUAGEor a join multiplies rows. - Date-effective
- This is an
_Ftable — one row per entity per effectivity window, withEFFECTIVE_START_DATEandEFFECTIVE_END_DATEpart of the key. Join without a window filter and every fact multiplies by history (see the quirks guide). - View
- This is a documented convenience view, not a physical table. Extract through the BICC data store that fronts its base objects instead of assuming the view lands as-is.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
Extract access
The delivered surfaces that reach this table — the BICC extract data store (PVO) for bulk extraction and the OTBI subject areas for real-time queries. There is no SQL path to the SaaS database.
- FscmTopModelAM.ScmExtractAM.EgpBiccExtractAM.ItemCatAssignmentsExtractPVOOTBI: Product Management - Item Catalog Category Hierarchy Real Time
Item Category Assignments data store — the item-to-category relationship this table stores.
Oracle data-store documentation (opens in new tab)
Fields
8 fields · 4 key
8 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | INVENTORY_ITEM_ID | Item being categorized | NUMBER | Key |
| 2 | ORGANIZATION_ID | Organization of the item row | NUMBER | Key |
| 3 | CATEGORY_SET_ID | Catalog (category set) of the assignment | NUMBER | Key |
| 4 | CATEGORY_ID | Category within the catalog | NUMBER | Key |
| 5 | ITEM_CATEGORY_ASSIGNMENT_ID | Surrogate id of the assignment row | NUMBER | |
| 6 | START_DATE | Assignment effective-from date | DATE | |
| 7 | END_DATE | Assignment effective-to date | DATE | |
| 8 | SEQUENCE_NUMBER | Display ordering of categories in the catalog | NUMBER |
Field provenance: hand-curated. 4 key fields.
Boilerplate SQL
Starting point for reading the BICC-landed copy of EGP_ITEM_CAT_ASSIGNMENTS on 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.
7 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <INVENTORY_ITEM_ID>, <CATEGORY_SET_ID>, <CATEGORY_ID>, <watermark>
-- ============================================================
-- Table : EGP_ITEM_CAT_ASSIGNMENTS — The item-to-category assignment — one row per item, organization, catalog (category set), and category; the bridge every category rollup crosses
-- Purpose: Column-selected read of EGP_ITEM_CAT_ASSIGNMENTS — auto-generated from field metadata
-- Grain : One row per inventory org (ORGANIZATION_ID) + INVENTORY_ITEM_ID + CATEGORY_SET_ID + CATEGORY_ID
-- 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.INVENTORY_ITEM_ID AS "Item being categorized",
t.ORGANIZATION_ID AS "Organization of the item row",
t.CATEGORY_SET_ID AS "Catalog (category set) of the assignment",
t.CATEGORY_ID AS "Category within the catalog",
t.ITEM_CATEGORY_ASSIGNMENT_ID AS "Surrogate id of the assignment row",
t.START_DATE AS "Assignment effective-from date",
t.END_DATE AS "Assignment effective-to date",
t.SEQUENCE_NUMBER AS "Display ordering of categories in the catalog"
FROM <catalog>.<schema>.EGP_ITEM_CAT_ASSIGNMENTS t
WHERE
t.ORGANIZATION_ID = <inventory_org_id> -- inventory org, NOT the business unit — see quirks guide #item-org-striping
-- AND t.INVENTORY_ITEM_ID = <INVENTORY_ITEM_ID>
-- AND t.CATEGORY_SET_ID = <CATEGORY_SET_ID>
-- AND t.CATEGORY_ID = <CATEGORY_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- the column incremental BICC extracts key on
ORDER BY t.INVENTORY_ITEM_ID;Verified September 2026 · docs release 26C
Column names differ in BICC extracts — see PVO header drift.
Relationships
Diagram of 1-hop neighbors — join details below. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
ON EGP_ITEM_CAT_ASSIGNMENTS.INVENTORY_ITEM_ID = EGP_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND EGP_ITEM_CAT_ASSIGNMENTS.ORGANIZATION_ID = EGP_SYSTEM_ITEMS_B.ORGANIZATION_IDON EGP_ITEM_CAT_ASSIGNMENTS.CATEGORY_ID = EGP_CATEGORIES_B.CATEGORY_IDON EGP_ITEM_CAT_ASSIGNMENTS.CATEGORY_SET_ID = EGP_CATEGORY_SETS_B.CATEGORY_SET_ID
More Product Master tables
- EGP_ITEM_REVISIONS_BItem 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
- EGP_STRUCTURES_BItem structure (BOM) headers — one row per manufacturing or engineering bill per named variant, identified by BILL_SEQUENCE_ID, with common-structure sharing and change-order linkage
- EGP_SYSTEM_ITEMS_BThe item master — one row per item per inventory organization, carrying the item number as a real column plus status, type, unit of measure, and the control flags for every functional area; every balance, transaction, and order line joins back to it on INVENTORY_ITEM_ID + ORGANIZATION_ID
- EGP_SYSTEM_ITEMS_TLThe item master's translation companion — item description and long description in every installed language, one row per item per organization per language; the only place the item description exists
- EGP_CATEGORIES_BThe category master — one row per category with its user-facing category code and active window; categories are global and keyed by CATEGORY_ID
- EGP_CATEGORY_SETS_BCatalog (category set) definitions — control level, the multiple-assignments flag, hierarchy option, and the default category new items inherit