Results for “bom_dependent_desc_elements”

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

Overview

The BOM.BOM_DEPENDENT_DESC_ELEMENTS table belongs to the Bills of Material (BOM) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the descriptive elements that are assigned to model and option bills of material. In effect, it records which descriptive element names are valid for a given model or option structure, forming the linkage between a bill structure and the descriptive element vocabulary used in configuration and order-entry logic. This is the metadata that drives option-dependent descriptive behavior in an assembled or configured item context.

From a Data Vault modeling perspective, the metadata classifies this object as satellite-leaning. This is a heuristic suggestion derived from the foreign key structure: the table carries descriptive attributes attached to a parent billing structure, with a compound primary key, which is characteristic of a satellite record rather than an independent hub or a pure link.

Key Information Stored

The table contains 11 documented columns. The most significant columns are as follows.

• BILL_SEQUENCE_ID — Part of the composite primary key and a foreign key to BOM_STRUCTURES_B. It identifies the bill structure (model or option bill) to which the descriptive element is assigned.
• ELEMENT_NAME — Part of the composite primary key. It holds the name of the descriptive element associated with the referenced structure.
• LAST_UPDATE_DATE, LAST_UPDATED_BY — Standard audit columns recording when and by whom the row was last modified.
• CREATION_DATE, CREATED_BY — Standard audit columns recording row creation details.
• LAST_UPDATE_LOGIN — The login identifier of the user who performed the last update.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrency and program context columns identifying the application and concurrent program that last touched the row.
• REQUEST_ID — The concurrent request identifier associated with the last program update.

The surrogate/primary key is defined by BOM_DEPENDENT_DESC_ELEMENTS_PK on the columns (BILL_SEQUENCE_ID, ELEMENT_NAME). A unique index, BOM_DEPENDENT_DESC_ELEMENTS_U1, spans the same two columns, serving as a documented business-key candidate. There is no separate single-column surrogate identifier; the structure identifies each descriptive element uniquely within its bill structure.

Common Use Cases and Queries

Typical usage centers on configuration and modeling processes that must know which descriptive elements apply to a given model or option bill. A common query pattern retrieves all descriptive elements for a specific bill structure:

• SELECT bill_sequence_id, element_name FROM bom.bom_dependent_desc_elements WHERE bill_sequence_id = :p_bill_seq;
• Joining to BOM_STRUCTURES_B by BILL_SEQUENCE_ID to enrich element names with structure context such as assembly item, organization, and effective dates.
• Reporting on model/option configurations to validate that only approved descriptive elements are attached.

Because the table is relatively narrow and keyed on a compound identifier, it is efficient to query by BILL_SEQUENCE_ID. Reporting extracts are frequently combined with BOM_STRUCTURES_B and item master data to produce configuration summaries or audit reports of descriptive element assignments.

Related Objects

The following objects are most significant in relation to this table.

• BOM_STRUCTURES_B — The foreign-key parent. The join is BOM_DEPENDENT_DESC_ELEMENTS.BILL_SEQUENCE_ID = BOM_STRUCTURES_B.BILL_SEQUENCE_ID; this provides the model/option structure context.
• BOM_STRUCTURES_TL — The translated structures table, often joined for language-specific descriptions.
• BOM_BILL_OF_MATERIALS — Related to structures and used when resolving the assembly associated with a bill.
• BOM_COMPONENTS_B — Component records within the referenced structures, relevant when analyzing the full model/option definition.
• BOM_DEPENDENT_DESC_ELEMENTS_PK / _U1 — The primary key and unique index constraints that enforce uniqueness and support access paths.

Collectively these objects support the descriptive element assignment and retrieval functions needed by Oracle BOM configuration and order management processes.