Skip to content
Fusion Reference

EGP_COMPONENTS_B

Product: EGPmaster

Item structure component lines — one row per component per operation per effectivity window, child of the structure header, with quantity, yield, and WIP supply behavior

Grain note

Component rows are effectivity slices — filter EFFECTIVITY_DATE/DISABLE_DATE to the window you mean or component counts multiply

Notes

Like its header, the component item is NOT a real id column: OBJ_NAME/PK1_VALUE/PK2_VALUE hold the component item and org ids as text, so no component→item edge is drawn. Join to the header on BILL_SEQUENCE_ID; the org is inherited from the header.

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.ComponentsExtractPVO
    OTBI: Product Management - Components Real TimeOTBI: Product Management - Structures and Components Real Time

    Structure Components data store — keyed on ComponentSequenceId; documented as the child store of Item Structures.

    Oracle data-store documentation (opens in new tab)

Fields

18 fields · 1 key

18 fields.

Table fields: position, field name, description, data type, and flags. 18 fields.
#FieldDescriptionTypeFlags
1COMPONENT_SEQUENCE_IDComponent line surrogate keyNUMBER
Key
2BILL_SEQUENCE_IDParent structure header — the join back to the bill; a foreign key, not part of this table's documented key (PK/unique index is COMPONENT_SEQUENCE_ID alone)NUMBER
3OBJ_NAMEObject type of the component reference (EGO_ITEM)VARCHAR2
4PK1_VALUEThe component item's INVENTORY_ITEM_ID — stored as text; cast before joining the item masterVARCHAR2
5PK2_VALUEThe component's ORGANIZATION_ID — stored as textVARCHAR2
6ITEM_NUMLine/sort sequence of the component on the structureNUMBER
7OPERATION_SEQ_NUMOperation the component is consumed atNUMBER
8COMPONENT_QUANTITYQuantity of the component per assemblyNUMBER
9COMPONENT_YIELD_FACTORYield multiplier applied to the required quantityNUMBER
10PLANNING_FACTORMultiplier for planning quantity on option componentsNUMBER
11PRIMARY_UOM_CODEUnit of measure for the component quantityVARCHAR2
12EFFECTIVITY_DATEStart of the component's effectivity windowDATE
Filter date
13DISABLE_DATEEnd of the component's effectivity windowDATE
14IMPLEMENTATION_DATEChange-order implementation date — NULL while pendingDATE
15OPTIONALWhether the component is optional (model/option structures)NUMBER
16WIP_SUPPLY_TYPEHow the component is issued to work in processNUMBER
17SUPPLY_SUBINVENTORYDefault supply subinventory for the componentVARCHAR2
18COMPONENT_ITEM_REVISION_IDItem revision of the component, when revision-pinnedNUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

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

6 parameters not filled: <catalog>, <schema>, <COMPONENT_SEQUENCE_ID>, <DATE_FROM>, <DATE_TO>, <watermark>

-- ============================================================
-- Table  : EGP_COMPONENTS_B — Item structure component lines — one row per component per operation per effectivity window, child of the structure header, with quantity, yield, and WIP supply behavior
-- Purpose: Column-selected read of EGP_COMPONENTS_B — auto-generated from field metadata
-- Grain  : One row per COMPONENT_SEQUENCE_ID
-- Caution: Component rows are effectivity slices — filter EFFECTIVITY_DATE/DISABLE_DATE to the window you mean or component counts multiply
-- 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.COMPONENT_SEQUENCE_ID AS "Component line surrogate key",
  t.BILL_SEQUENCE_ID AS "Parent structure header — the join back to the bill; a foreign key, not part of this table's documented key (PK/unique index is COMPONENT_SEQUENCE_ID alone)",
  t.OBJ_NAME AS "Object type of the component reference (EGO_ITEM)",
  t.PK1_VALUE AS "The component item's INVENTORY_ITEM_ID — stored as text; cast before joining the item master",
  t.PK2_VALUE AS "The component's ORGANIZATION_ID — stored as text",
  t.ITEM_NUM AS "Line/sort sequence of the component on the structure",
  t.OPERATION_SEQ_NUM AS "Operation the component is consumed at",
  t.COMPONENT_QUANTITY AS "Quantity of the component per assembly",
  t.COMPONENT_YIELD_FACTOR AS "Yield multiplier applied to the required quantity",
  t.PLANNING_FACTOR AS "Multiplier for planning quantity on option components",
  t.PRIMARY_UOM_CODE AS "Unit of measure for the component quantity",
  t.EFFECTIVITY_DATE AS "Start of the component's effectivity window",
  t.DISABLE_DATE AS "End of the component's effectivity window",
  t.IMPLEMENTATION_DATE AS "Change-order implementation date — NULL while pending",
  t.OPTIONAL AS "Whether the component is optional (model/option structures)",
  t.WIP_SUPPLY_TYPE AS "How the component is issued to work in process",
  t.SUPPLY_SUBINVENTORY AS "Default supply subinventory for the component",
  t.COMPONENT_ITEM_REVISION_ID AS "Item revision of the component, when revision-pinned"
FROM <catalog>.<schema>.EGP_COMPONENTS_B t
WHERE
  1 = 1  -- no automatic partition anchor on this table; the filters below are optional
  -- AND t.COMPONENT_SEQUENCE_ID = <COMPONENT_SEQUENCE_ID>
  -- 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.COMPONENT_SEQUENCE_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_COMPONENTS_BEGP_STRUCTURES_Bforeign key · N:1
    ON EGP_COMPONENTS_B.BILL_SEQUENCE_ID = EGP_STRUCTURES_B.BILL_SEQUENCE_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.