Results for “bom_structures_ext_b”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BOM_STRUCTURES_EXT_B is a key flexfield-style extension table in the Oracle Bills of Material (BOM) module, owned by the BOM schema. It stores the descriptive flexfield (DFF) attribute values attached to bill of material structures and their revisions. In Oracle EBS 12.1.1 and 12.2.2, the BOM module relies on this table to persist user-defined, context-sensitive attributes that extend the standard structure definition without requiring schema changes to the core BOM tables.

The table holds 102 columns and is uniquely identified by the business-key candidate index BOM_STRUCTURES_EXT_B_U1 on EXTENSION_ID. The heuristic Data Vault classification mined from the foreign-key structure is standalone, suggesting this object is best modeled as an independent satellite rather than a hub or link. It maintains referential dependencies on BOM_BILL_REVISIONS_B via BILL_REVISION_ID and on BOM_STRUCTURE_TYPES_B via STRUCTURE_TYPE_ID, anchoring each extension row to a specific bill revision and structure type.

Key Information Stored

The table is dominated by flexfield attribute columns grouped by datatype: 40 character attributes (C_EXT_ATTR1 through C_EXT_ATTR40), 20 numeric attributes (N_EXT_ATTR1 through N_EXT_ATTR20), 10 date attributes (D_EXT_ATTR1 through D_EXT_ATTR10), and 20 unit-of-measure attributes (UOM_EXT_ATTR1 through UOM_EXT_ATTR20). The most significant columns are:

• EXTENSION_ID — surrogate primary key and the sole unique-index business-key candidate (BOM_STRUCTURES_EXT_B_U1).
• BILL_SEQUENCE_ID — links the extension row to the specific bill sequence.
• BILL_REVISION_ID — foreign key to BOM_BILL_REVISIONS_B, identifying the revision.
• STRUCTURE_TYPE_ID — foreign key to BOM_STRUCTURE_TYPES_B, defining the structure type.
• CHANGE_LINE_ID — associates the row with an engineering change line.
• ACD_TYPE — indicates the application context/descriptive type used for DFF segments.
• ATTR_GROUP_ID — identifies the attribute group for grouped flexfield values.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns tracking record provenance.

The C_EXT_ATTR, N_EXT_ATTR, D_EXT_ATTR, and UOM_EXT_ATTR columns carry the actual user-defined values, whose meaning is defined through the DFF segment setup rather than the column names themselves.

Common Use Cases and Queries

Typical scenarios include extracting custom attribute values for a given bill revision, validating that DFF segments are populated, and joining structure data to its extensions for reporting. A representative query joins the extension table to the revision table:

• Retrieve extensions for a revision: SELECT e.EXTENSION_ID, e.C_EXT_ATTR1, e.N_EXT_ATTR1 FROM BOM_STRUCTURES_EXT_B e WHERE e.BILL_REVISION_ID = :revision_id;
• Join to revisions and structure types: SELECT e.*, r.* FROM BOM_STRUCTURES_EXT_B e, BOM_BILL_REVISIONS_B r, BOM_STRUCTURE_TYPES_B t WHERE e.BILL_REVISION_ID = r.BILL_REVISION_ID AND e.STRUCTURE_TYPE_ID = t.STRUCTURE_TYPE_ID;
• Filter by context: constrain on ACD_TYPE to isolate a specific DFF context for a report or migration.

Common use cases include custom BOM reporting, data migration of legacy attributes, and integration interfaces that exchange user-defined structure characteristics with external PLM or manufacturing systems.

Related Objects

The most significant related objects, based on the documented foreign-key relationships, include:

• BOM_BILL_REVISIONS_B — referenced via BILL_REVISION_ID; holds bill revision headers.
• BOM_STRUCTURE_TYPES_B — referenced via STRUCTURE_TYPE_ID; defines structure types.
• BOM_STRUCTURES_B / BOM_STRUCTURES_EXT_B — the base structure tables that share the extension pattern.
• BOM_BILL_SEQUENCES — related through BILL_SEQUENCE_ID for sequence context.
• BOM_ATTRIBUTE_GROUPS — associated via ATTR_GROUP_ID for grouped flexfield definitions.
• BOM Components and BOM APIs — the BOM interface/API layer that reads and writes extension values during structure maintenance.

Because the Data Vault classification is standalone, no natural parent hub is imposed; the table functions as an independent satellite keyed on EXTENSION_ID while remaining referentially bound to the revision and structure-type parents.