Search Results bom_comp_attr_ctx_assocs_b

Overview

BOM.BOM_COMP_ATTR_CTX_ASSOCS_B is a base table within the Oracle Bills of Material (BOM) product family. It stores the association between component-level attribute contexts and the attribute extensions that apply to them, scoped to a specific bill structure. In practice, the table supports the configurable, attribute-driven behavior of bill components, allowing Oracle EBS to resolve which attribute extension definitions apply to a given component on a given bill across revisions and structure types.

The table resides in the BOM schema and is marked VALID in the EBS 12.1.1 / 12.2.2 data dictionary. It is delivered as part of the standard Oracle E-Business Suite installation and is used internally by the Bills of Material application rather than being exposed as an end-user maintenance screen.

From a Data Vault modeling perspective, the heuristic classification is standalone. This means the mined foreign-key structure does not place the table cleanly into a hub, link, or satellite role. A practical modeling suggestion is therefore to treat it as a standalone association or reference table that records contextual attribute bindings for bill components, keyed by its own unique index rather than by a hub-and-link pattern.

Key Information Stored

The table contains 20 documented columns. The most significant are:

• CONTEXT_ID — identifies the attribute context to which the association applies.
• EXTENSION_ID and BASE_EXTENSION_ID — identify the attribute extension being associated, and its base definition respectively.
• COMPONENT_SEQUENCE_ID — points to the component line on the bill for which the context association is defined.
• BILL_SEQUENCE_ID and TOP_BILL_SEQUENCE_ID — identify the bill and the top-level bill scope of the association.
• STRUCTURE_TYPE_ID — the only documented foreign key, referencing BOM_STRUCTURE_TYPES_B; it scopes the association to a bill structure type.
• ATTR_GROUP_ID — the attribute group to which the extension belongs.
• COMPONENT_CODE — a short identifier for the component.
• FROM_REVISION_ID, TO_REVISION_ID, FROM_REVISION_CODE, TO_REVISION_CODE — define the effective revision range over which the association applies.
• ATTRIBUTES_LIST — the serialized list of attributes bound by the association.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — standard audit and concurrency-control columns.

The table does not carry a documented single-column surrogate primary key. Its business-key candidate is the unique index BOM_COMP_ATTR_CTX_ASSOCS_B_U, defined on the composite of EXTENSION_ID, BASE_EXTENSION_ID, COMPONENT_SEQUENCE_ID, BILL_SEQUENCE_ID, and TOP_BILL_SEQUENCE_ID. Row identity is therefore established by that composite rather than by a sequence-generated surrogate.

Common Use Cases and Queries

Because the table governs how attribute extensions bind to bill components, the primary reporting scenarios involve tracing which extensions apply to a given component, bill, or structure type, and over which revision range.

A representative query joins the table to the structure types reference table and filters by component:

• Retrieve all attribute context associations for a component sequence, joining STRUCTURE_TYPE_ID to BOM_STRUCTURE_TYPES_B to resolve the structure type name.
• Reconstruct the effective attribute set for a bill by filtering on BILL_SEQUENCE_ID and comparing FROM_REVISION_ID / TO_REVISION_ID against the revision in effect.
• Audit changes to attribute bindings using LAST_UPDATE_DATE and LAST_UPDATED_BY.
• Detect duplicate or overlapping associations using the unique index columns as the deduplication key.

Typical SQL pattern: SELECT a.COMPONENT_SEQUENCE_ID, a.EXTENSION_ID, a.FROM_REVISION_CODE, a.TO_REVISION_CODE, s.STRUCTURE_TYPE FROM BOM.BOM_COMP_ATTR_CTX_ASSOCS_B a, BOM.BOM_STRUCTURE_TYPES_B s WHERE a.STRUCTURE_TYPE_ID = s.STRUCTURE_TYPE_ID AND a.BILL_SEQUENCE_ID = :bill_seq;

Related Objects

• BOM_STRUCTURE_TYPES_B — referenced via STRUCTURE_TYPE_ID; the sole documented foreign-key relationship.
• BOM_COMPONENTS_B / component tables — related through COMPONENT_SEQUENCE_ID to resolve the bill component line.
• BOM_BILL_OF_MATERIALS — related through BILL_SEQUENCE_ID and TOP_BILL_SEQUENCE_ID to identify the parent bill.
• BOM_ATTRIBUTE_EXTENSIONS — related through EXTENSION_ID and BASE_EXTENSION_ID for extension definitions.
• BOM_ATTRIBUTE_GROUPS — related through ATTR_GROUP_ID for attribute grouping.
• BOM_ITEM_REVISIONS — related via the FROM/TO revision identifiers and codes.

These relationships make the table a supporting association layer beneath the Bills of Material component configuration model.