EGP_STRUCTURES_B
Product: EGPmasterItem 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
The assembly item and organization are NOT real id columns here: OBJ_NAME/PK1_VALUE/PK2_VALUE hold the item id and org id as text — so this catalog draws no structure→item join edge; cast TO_NUMBER(PK1_VALUE)/TO_NUMBER(PK2_VALUE) deliberately when you need one. COMMON_BILL_SEQUENCE_ID equals the row's own id when the bill is not shared.
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.StructuresExtractPVOOTBI: Product Management - Structures Real TimeOTBI: Product Management - Structures and Components Real Time
Item Structures data store — keyed on BillSequenceId, mirroring the structure header's key.
Oracle data-store documentation (opens in new tab)
Fields
14 fields · 1 key
14 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | BILL_SEQUENCE_ID | Structure header surrogate key — what component rows point at | NUMBER | Key |
| 2 | OBJ_NAME | Object type the structure hangs on (EGO_ITEM for item structures) | VARCHAR2 | |
| 3 | PK1_VALUE | The assembly item's INVENTORY_ITEM_ID — stored as text; cast before joining the item master | VARCHAR2 | |
| 4 | PK2_VALUE | The assembly's ORGANIZATION_ID — stored as text; cast before joining | VARCHAR2 | |
| 5 | ALTERNATE_BOM_DESIGNATOR | Named structure variant — the structure name | VARCHAR2 | |
| 6 | STRUCTURE_TYPE_ID | Structure type identifier | NUMBER | |
| 7 | EFFECTIVITY_CONTROL | Effectivity mode — date, unit number, or serial | NUMBER | |
| 8 | COMMON_BILL_SEQUENCE_ID | Source bill when this bill references a shared structure — equals the row's own id when not shared | NUMBER | |
| 9 | COMMON_ASSEMBLY_ITEM_ID | Assembly item of the shared (common) bill | NUMBER | |
| 10 | COMMON_ORGANIZATION_ID | Organization of the shared (common) bill | NUMBER | |
| 11 | SOURCE_BILL_SEQUENCE_ID | Originating bill sequence | NUMBER | |
| 12 | CHANGE_ID | Change order that created the bill | NUMBER | |
| 13 | CHANGE_LINE_ID | Change-order line that created the bill | NUMBER | |
| 14 | VERSION_ID | Structure version for version-controlled setups | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the BICC-landed copy of EGP_STRUCTURES_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.
4 parameters not filled: <catalog>, <schema>, <BILL_SEQUENCE_ID>, <watermark>
-- ============================================================
-- Table : EGP_STRUCTURES_B — Item 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
-- Purpose: Column-selected read of EGP_STRUCTURES_B — auto-generated from field metadata
-- Grain : One row per BILL_SEQUENCE_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.BILL_SEQUENCE_ID AS "Structure header surrogate key — what component rows point at",
t.OBJ_NAME AS "Object type the structure hangs on (EGO_ITEM for item structures)",
t.PK1_VALUE AS "The assembly item's INVENTORY_ITEM_ID — stored as text; cast before joining the item master",
t.PK2_VALUE AS "The assembly's ORGANIZATION_ID — stored as text; cast before joining",
t.ALTERNATE_BOM_DESIGNATOR AS "Named structure variant — the structure name",
t.STRUCTURE_TYPE_ID AS "Structure type identifier",
t.EFFECTIVITY_CONTROL AS "Effectivity mode — date, unit number, or serial",
t.COMMON_BILL_SEQUENCE_ID AS "Source bill when this bill references a shared structure — equals the row's own id when not shared",
t.COMMON_ASSEMBLY_ITEM_ID AS "Assembly item of the shared (common) bill",
t.COMMON_ORGANIZATION_ID AS "Organization of the shared (common) bill",
t.SOURCE_BILL_SEQUENCE_ID AS "Originating bill sequence",
t.CHANGE_ID AS "Change order that created the bill",
t.CHANGE_LINE_ID AS "Change-order line that created the bill",
t.VERSION_ID AS "Structure version for version-controlled setups"
FROM <catalog>.<schema>.EGP_STRUCTURES_B t
WHERE
1 = 1 -- no automatic partition anchor on this table; the filters below are optional
-- AND t.BILL_SEQUENCE_ID = <BILL_SEQUENCE_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- the column incremental BICC extracts key on
ORDER BY t.BILL_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
ON EGP_COMPONENTS_B.BILL_SEQUENCE_ID = EGP_STRUCTURES_B.BILL_SEQUENCE_ID- EGP_STRUCTURES_BEGP_STRUCTURES_Bforeign key · N:1
ON EGP_STRUCTURES_B1.COMMON_BILL_SEQUENCE_ID = EGP_STRUCTURES_B2.BILL_SEQUENCE_ID ON WIS_WORK_DEFINITIONS.BILL_SEQUENCE_ID = EGP_STRUCTURES_B.BILL_SEQUENCE_ID
More Product Master tables
- 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
- EGP_COMPONENTS_BItem structure component lines — one row per component per operation per effectivity window, child of the structure header, with quantity, yield, and WIP supply behavior
- EGP_ITEM_CAT_ASSIGNMENTSThe item-to-category assignment — one row per item, organization, catalog (category set), and category; the bridge every category rollup crosses