Skip to content
Fusion Reference

EGP_CATEGORIES_B

Product: EGPmaster

The category master — one row per category with its user-facing category code and active window; categories are global and keyed by CATEGORY_ID

Notes

The category NAME is not on this table — it lives only on the translation companion (EGP_CATEGORIES_TL, not yet cataloged), so readable category output is language-filtered. The SEGMENTn and structure columns are legacy leftovers Oracle marks deprecated — CATEGORY_CODE is the real identifier.

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.

Structural facts — how the table is partitioned, not a trap by itself

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 with INVENTORY_ITEM_ID on 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_ID on the GL journal tables), or a named business-unit column (PRC_BU_ID / REQ_BU_ID in 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 LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows.

Join & extract hazards — verify before you rely on this

Date-effective
This is an _F table — one row per entity per effectivity window, with EFFECTIVE_START_DATE and EFFECTIVE_END_DATE part 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.
In field listings, the Key chip marks a key field — a member of the documented primary key or of a documented unique index.

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.CategoryExtractPVO
    OTBI: Product Management - Item Catalog Category Hierarchy Real Time

    Categories data store — keyed on CategoryId. Translated category names ride the separate CategoryTranslationExtractPVO.

    Oracle data-store documentation (opens in new tab)

Fields

5 fields · 1 key

5 fields.

Table fields: position, field name, description, data type, and flags. 5 fields.
#FieldDescriptionTypeFlags
1CATEGORY_IDCategory surrogate keyNUMBER
Key
2CATEGORY_CODEThe user-facing category code — the real identifier (the SEGMENTn columns are deprecated leftovers)VARCHAR2
3START_DATE_ACTIVECategory active-from dateDATE
4END_DATE_ACTIVECategory active-to dateDATE
5ENABLED_FLAGMarked deprecated in the data dictionary — no longer used by the applicationVARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of EGP_CATEGORIES_B 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.

Query parameters

4 parameters not filled: <catalog>, <schema>, <CATEGORY_ID>, <watermark>

-- ============================================================
-- Table  : EGP_CATEGORIES_B — The category master — one row per category with its user-facing category code and active window; categories are global and keyed by CATEGORY_ID
-- Purpose: Column-selected read of EGP_CATEGORIES_B — auto-generated from field metadata
-- Grain  : One row per 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.CATEGORY_ID AS "Category surrogate key",
  t.CATEGORY_CODE AS "The user-facing category code — the real identifier (the SEGMENTn columns are deprecated leftovers)",
  t.START_DATE_ACTIVE AS "Category active-from date",
  t.END_DATE_ACTIVE AS "Category active-to date",
  t.ENABLED_FLAG AS "Marked deprecated in the data dictionary — no longer used by the application"
FROM <catalog>.<schema>.EGP_CATEGORIES_B t
WHERE
  1 = 1  -- no automatic partition anchor on this table; the filters below are optional
  -- AND t.CATEGORY_ID = <CATEGORY_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.CATEGORY_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

  • EGP_ITEM_CAT_ASSIGNMENTSEGP_CATEGORIES_Bforeign key · N:1
    ON EGP_ITEM_CAT_ASSIGNMENTS.CATEGORY_ID = EGP_CATEGORIES_B.CATEGORY_ID
  • EGP_CATEGORY_SETS_BEGP_CATEGORIES_Bforeign key · N:1
    ON EGP_CATEGORY_SETS_B.DEFAULT_CATEGORY_ID = EGP_CATEGORIES_B.CATEGORY_ID
  • PO_LINES_ALLEGP_CATEGORIES_Bforeign key · N:1
    ON PO_LINES_ALL.CATEGORY_ID = EGP_CATEGORIES_B.CATEGORY_ID
  • RCV_SHIPMENT_LINESEGP_CATEGORIES_Bforeign key · N:1
    ON RCV_SHIPMENT_LINES.CATEGORY_ID = EGP_CATEGORIES_B.CATEGORY_ID

Browse more Product Master tables

More Product Master tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Oracle. Oracle and Oracle Fusion Cloud Applications are registered trademarks of Oracle and/or its affiliates.