Search Results bom_comp_attr_ctx_assocs_b_u

Overview

BOM.BOM_COMP_ATTR_CTX_ASSOCS_B is a base table in the Oracle E-Business Suite Bills of Material (BOM) schema. It stores the association between component-level attribute contexts and the component occurrences within a bill of materials or engineering structure. In practical terms, the table records which attribute groups, context identifiers, and revision-scoped component attributes apply to a given component sequence across a defined structure, bill, and top-level bill hierarchy. This makes the table a control point for attribute-driven component configuration, particularly where revision-specific attribute values must be persisted against component usage.

In Oracle EBS 12.1.1 and 12.2.2, the table resides in the APPS_TS_TX_DATA tablespace and participates in the standard multi-org, audit-enabled BOM data model. It carries the standard WHO columns, including CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER, which support concurrency control and audit reporting. Based on the mined foreign key structure, the ETRM heuristic classifies this object as standalone rather than a hub, link, or satellite. A Data Vault modeler may nevertheless treat it as a link-like association table, since it joins attribute context information to component and structure identifiers.

Key Information Stored

The documented physical schema contains twenty columns. The most significant include the following:

• EXTENSION_ID — Surrogate identifier and the leading column of the unique index BOM_COMP_ATTR_CTX_ASSOCS_B_U.
• BASE_EXTENSION_ID — The second business-key column, typically linking the association to a parent extension definition.
• COMPONENT_SEQUENCE_ID — Identifies the specific component occurrence within the bill of materials to which the attribute context applies.
• BILL_SEQUENCE_ID — Identifies the bill sequence header for the component association.
• TOP_BILL_SEQUENCE_ID — Identifies the top-level bill in a multilevel structure, enabling hierarchical reporting.
• CONTEXT_ID — The attribute context identifier used to resolve which attribute group applies.
• STRUCTURE_TYPE_ID — Foreign key to BOM_STRUCTURE_TYPES_B, defining the structure type of the bill.
• ATTR_GROUP_ID — The attribute group referenced by the association.
• COMPONENT_CODE — VARCHAR2(4000) component code or equivalent descriptive key.
• FROM_REVISION_ID / TO_REVISION_ID — Revision range identifiers governing the validity of the association.
• FROM_REVISION_CODE / TO_REVISION_CODE — Human-readable revision codes paired with the ID columns.
• ATTRIBUTES_LIST — VARCHAR2(880) payload containing the serialized attribute values associated with the context.

The unique key BOM_COMP_ATTR_CTX_ASSOCS_B_U spans EXTENSION_ID, BASE_EXTENSION_ID, COMPONENT_SEQUENCE_ID, BILL_SEQUENCE_ID, and TOP_BILL_SEQUENCE_ID. Users searching for "bom_comp_attr_ctx_assocs_b_u" are referencing this unique index, which enforces the business key and provides the primary access path for lookups by extension and component sequence.

Common Use Cases and Queries

Typical queries retrieve attribute context associations for a specific component sequence or extension. For example, to list all contexts for a given component occurrence:

• SELECT COMPONENT_SEQUENCE_ID, CONTEXT_ID, ATTR_GROUP_ID, FROM_REVISION_CODE, TO_REVISION_CODE, ATTRIBUTES_LIST FROM BOM.BOM_COMP_ATTR_CTX_ASSOCS_B WHERE COMPONENT_SEQUENCE_ID = :component_sequence_id;
• SELECT * FROM BOM.BOM_COMP_ATTR_CTX_ASSOCS_B WHERE EXTENSION_ID = :extension_id AND BASE_EXTENSION_ID = :base_extension_id;
• SELECT a.*, s.STRUCTURE_TYPE_NAME FROM BOM.BOM_COMP_ATTR_CTX_ASSOCS_B a, BOM.BOM_STRUCTURE_TYPES_B s WHERE a.STRUCTURE_TYPE_ID = s.STRUCTURE_TYPE_ID;

Common reporting scenarios include auditing which attribute groups are attached to components across revision ranges, comparing FROM_REVISION_CODE and TO_REVISION_CODE to determine effective validity, and extracting ATTRIBUTES_LIST for downstream configuration or integration processing. Because the table is audit-enabled, delta reports can be built using LAST_UPDATE_DATE and OBJECT_VERSION_NUMBER to detect changes between EBS runs.

Related Objects

The most significant related objects and relationships are:

• BOM.BOM_STRUCTURE_TYPES_B — Referenced via the foreign key BOM_COMP_ATTR_CTX_ASSOCS_B.STRUCTURE_TYPE_ID → BOM_STRUCTURE_TYPES_B, supplying structure type definitions.
• BOM.BOM_COMP_ATTR_CTX_ASSOCS_B# — The named constraint associated with the table, enforcing the unique key BOM_COMP_ATTR_CTX_ASSOCS_B_U.
• BOM_COMPONENTS_B / BOM_COMPONENTS_TL — Component definitions whose COMPONENT_SEQUENCE_ID values are referenced logically by this association table.
• BOM_BILL_OF_MATERIALS — Bill header information aligned with BILL_SEQUENCE_ID.
• BOM_STRUCTURES_B — Structure definitions that contextualize TOP_BILL_SEQUENCE_ID relationships.
• BOM_ATTRIBUTE_GROUPS / BOM_ATTR_GROUPS — Attribute group metadata referenced by ATTR_GROUP_ID.
• BOM_EXTENSIONS_B — Extension definitions aligned with EXTENSION_ID and BASE_EXTENSION_ID.

These objects are most often joined on the component sequence, bill sequence, and structure type keys to resolve full bill and attribute context information.