EGP_COMPONENTS_B
Product: EGPmasterItem structure component lines — one row per component per operation per effectivity window, child of the structure header, with quantity, yield, and WIP supply behavior
Component rows are effectivity slices — filter EFFECTIVITY_DATE/DISABLE_DATE to the window you mean or component counts multiply
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
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
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.ComponentsExtractPVOOTBI: 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 →
Fields
18 fields · 2 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | COMPONENT_SEQUENCE_ID | Component line surrogate key | NUMBER | Key |
| 2 | BILL_SEQUENCE_ID | Parent structure header — the join back to the bill | NUMBER | Key |
| 3 | OBJ_NAME | Object type of the component reference (EGO_ITEM) | VARCHAR2 | |
| 4 | PK1_VALUE | The component item's INVENTORY_ITEM_ID — stored as text; cast before joining the item master | VARCHAR2 | |
| 5 | PK2_VALUE | The component's ORGANIZATION_ID — stored as text | VARCHAR2 | |
| 6 | ITEM_NUM | Line/sort sequence of the component on the structure | NUMBER | |
| 7 | OPERATION_SEQ_NUM | Operation the component is consumed at | NUMBER | |
| 8 | COMPONENT_QUANTITY | Quantity of the component per assembly | NUMBER | |
| 9 | COMPONENT_YIELD_FACTOR | Yield multiplier applied to the required quantity | NUMBER | |
| 10 | PLANNING_FACTOR | Multiplier for planning quantity on option components | NUMBER | |
| 11 | PRIMARY_UOM_CODE | Unit of measure for the component quantity | VARCHAR2 | |
| 12 | EFFECTIVITY_DATE | Start of the component's effectivity window | DATE | Filter date |
| 13 | DISABLE_DATE | End of the component's effectivity window | DATE | |
| 14 | IMPLEMENTATION_DATE | Change-order implementation date — NULL while pending | DATE | |
| 15 | OPTIONAL | Whether the component is optional (model/option structures) | NUMBER | |
| 16 | WIP_SUPPLY_TYPE | How the component is issued to work in process | NUMBER | |
| 17 | SUPPLY_SUBINVENTORY | Default supply subinventory for the component | VARCHAR2 | |
| 18 | COMPONENT_ITEM_REVISION_ID | Item revision of the component, when revision-pinned | NUMBER |
Field provenance: hand-curated. 2 key fields.
Boilerplate SQL
Starting point for reading the BICC-landed copy of EGP_COMPONENTS_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.
-- ============================================================
-- 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 + BILL_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",
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 partition column on this table; the filters below are optional
-- AND t.COMPONENT_SEQUENCE_ID = <COMPONENT_SEQUENCE_ID>
-- AND t.BILL_SEQUENCE_ID = <BILL_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;7 parameters not filled: <catalog>, <schema>, <COMPONENT_SEQUENCE_ID>, <BILL_SEQUENCE_ID>, <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
ON EGP_COMPONENTS_B.BILL_SEQUENCE_ID = EGP_STRUCTURES_B.BILL_SEQUENCE_ID