Search Results bom_cto_order_lines_upg




Overview
Explore in AI Chat

Overview

The BOM.BOM_CTO_ORDER_LINES_UPG table is a Bills of Material (BOM) module object in Oracle E-Business Suite, documented as a VALID table in both the 12.1.1 and 12.2.2 releases. Its description, "bom cto order lines," identifies it as a staging or upgrade-support structure associated with Configure-to-Order (CTO) order lines. In Oracle EBS, CTO order lines represent the model and option configurations captured on sales and manufacturing orders, where a top-level model item is exploded into its configured components. Tables bearing the _UPG suffix typically exist to facilitate data migration, concurrent-processing staging, or upgrade transformation of CTO order line data between structures or releases, populating downstream order-line and configuration tables used by the CTO and ATO (Assemble-to-Order) processes.

The ETRM Data Vault classification for this object is standalone, mined heuristically from its foreign-key structure. In Data Vault modeling terms this suggests treating BOM_CTO_ORDER_LINES_UPG as a hub-like anchor rather than a link or satellite, since no explicit parent-child FK relationships are documented. The single surrogate key, LINE_ID, serves as the natural candidate for a hub business key, with the remaining attributes modeled as descriptive satellite columns.

Key Information Stored

The table exposes 35 documented columns. The most operationally significant include:

Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_UPDATE_DATE) are also present, supporting row-level change tracking during upgrade and migration activity.

Common Use Cases and Queries

Typical usage centers on validating and reconciling staged CTO order line data before or after it is loaded into production order-configuration tables. A common pattern joins staging rows to configuration headers by HEADER_ID and isolates rows belonging to a specific upgrade batch:

SELECT LINE_ID, HEADER_ID, CONFIG_ITEM_ID, ORDERED_QUANTITY, STATUS
FROM   BOM.BOM_CTO_ORDER_LINES_UPG
WHERE  BATCH_ID = :batch_id
ORDER  BY LINE_ID;

Hierarchy traversal queries use the self-referencing columns ATO_LINE_ID and PARENT_ATO_LINE_ID to reconstruct the model-to-option explosion, while reconciliation reports compare ORDERED_QUANTITY against QTY_PER_PARENT_MODEL to detect configuration mismatches. Because the table is staging-oriented, queries are frequently bounded by REQUEST_ID or PROGRAM_ID to isolate a single concurrent run.

Related Objects

Although the table is classified as standalone with no documented foreign-key targets, in practice it interacts within the CTO/ATO processing ecosystem. The most significant related objects and join columns are:

These relationships should be confirmed against the specific instance's foreign-key metadata, as the ETRM does not document enforced constraints for this table.