Results for “bom_cto_oss_components”

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

Overview

BOM.BOM_CTO_OSS_COMPONENTS is a Bills of Material (BOM) module table that stores the Oracle Selling Solutions (OSS) component definition for configure-to-order (CTO) models. In Oracle EBS 12.1.1 and 12.2.2, it underpins the Configurator/OSS integration, holding the mapping between a configurable model item and the option items that may be selected as components of that model. The table is owned by the BOM schema and is documented in the ETRM as VALID, with a physical schema of 28 columns in 12.2.2.

From a modeling perspective, the metadata's heuristic Data Vault classification is standalone. This suggests that, when represented in a Data Vault, the table is best treated as a reference or hub-style structure rather than as a link or satellite dependent on other entities. Although it carries who/when audit attributes, no foreign key originates from it, so it is not formally modeled as a dependent child of another table in the mined relationship graph.

Key Information Stored

The surrogate primary key is OSS_COMP_SEQ_ID, enforced by unique index BOM_CTO_OSS_COMPONENTS_U1. Two business-key candidates are documented through unique indexes: OSS_COMP_SEQ_ID and the composite (MODEL_ITEM_ID, OPTION_ITEM_ID) via BOM_CTO_OSS_COMPONENTS_U2. The most significant columns are:

• OSS_COMP_SEQ_ID — surrogate identifier for each OSS component definition row.
• MODEL_ITEM_ID — the configurable model item to which the component belongs.
• OPTION_ITEM_ID — the option item that may be selected as a component of the model.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — a standard EBS descriptive flexfield (DFF) block used to store customer-specific and extensible component attributes.
• CREATED_BY, CREATION_DATE, LAST_UPDATE_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard who-audit columns recording row creation and maintenance.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context capturing the request and program that last touched the row.

The combination of model and option item is the practical business key, ensuring that a given option item appears only once per model within the OSS component definition.

Common Use Cases and Queries

Typical scenarios include validating which option items are permitted under a configurable model, driving Configurator rules, and reconciling OSS component definitions against BOM model structures. A common query lists all components for a model:

• SELECT oss_comp_seq_id, model_item_id, option_item_id FROM bom.bom_cto_oss_components WHERE model_item_id = :model_item_id;

Reporting use cases include auditing newly created or modified component definitions using the audit columns, and extracting flexfield attribute values for downstream analytics:

• SELECT oss_comp_seq_id, attribute_category, attribute1, attribute2 FROM bom.bom_cto_oss_components WHERE last_update_date >= :since;
• Joining to the organizations list to determine the inventory organizations in which a component definition is valid.

Related Objects

The documented foreign-key relationship identifies BOM_CTO_OSS_ORGS_LIST as a table referencing this object, joining on OSS_COMP_SEQ_ID. In practice, analysts also relate this table to standard BOM and inventory item master tables using MODEL_ITEM_ID and OPTION_ITEM_ID, and to the standard EBS concurrent program and user references for the audit and request columns. The most significant related objects are:

• BOM.BOM_CTO_OSS_ORGS_LIST — organizations list, joined on OSS_COMP_SEQ_ID.
• BOM.BOM_BILL_OF_MATERIALS and BOM component tables — referenced via model/option item identifiers.
• INV.MTL_SYSTEM_ITEMS_B — item master, joined on MODEL_ITEM_ID and OPTION_ITEM_ID.
• FND_USER and FND_CONCURRENT_REQUESTS — audit and request context.