Search Results bom_cto_order_lines_pk

Overview

BOM.BOM_CTO_ORDER_LINES is a transactional table in the Oracle E-Business Suite Bills of Material (BOM) module that stores order line detail for Configure-to-Order (CTO) and Assemble-to-Order (ATO) configurations. It captures the relationship between the top-level model line on a sales order, the ATO configuration item, and the individual option/component lines that make up the configured product. The table is central to the order-to-configuration flow where a customer-selected model is exploded into its constituent option classes and options, driving both WIP supply and ship-from sourcing decisions.

Within the documented ETRM 12.2.2 physical schema, the object is owned by the BOM schema and contains 33 columns. The Data Vault classification heuristic, mined from the foreign key structure, identifies this object as standalone — meaning it does not strongly participate as a hub or satellite in a modeled FK dependency graph. In practice, however, the table behaves as a transactional link between order headers, model lines, and configuration items, and modeling it as a link with dependent satellites is a reasonable architectural suggestion.

Key Information Stored

The surrogate primary key is LINE_ID, enforced by BOM_CTO_ORDER_LINES_PK. A unique index BOM_CTO_ORDER_LINES_U1 is also defined on LINE_ID, making it both the surrogate key and the only documented business-key candidate. The most significant columns fall into several functional groups:

• Order linkage: HEADER_ID ties the line to the order header; TOP_MODEL_LINE_ID and ATO_LINE_ID identify the top model and ATO configuration lines; PARENT_ATO_LINE_ID and LINK_TO_LINE_ID establish parent-child and linking relationships across the configured structure.
• Item and component identity: INVENTORY_ITEM_ID, CONFIG_ITEM_ID, COMPONENT_SEQUENCE_ID, COMPONENT_CODE, BOM_ITEM_TYPE, and ITEM_TYPE_CODE describe the item being configured and its components.
• Quantities and scheduling: ORDERED_QUANTITY, ORDER_QUANTITY_UOM, QTY_PER_PARENT_MODEL, and SCHEDULE_SHIP_DATE drive fulfillment and lead-time calculations.
• Sourcing and supply: SHIP_FROM_ORG_ID, WIP_SUPPLY_TYPE, PLAN_LEVEL, and PERFORM_MATCH control how the line is sourced and matched against supply.
• Configuration behavior: REUSE_CONFIG, OPTION_SPECIFIC, and CONFIG_CREATION flag configuration reuse and option-specific behavior.
• Audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, and PROGRAM_UPDATE_DATE support concurrency and audit tracing.

Common Use Cases and Queries

Typical uses include retrieving all configured option lines for a given sales order, tracing parent-child hierarchy within a configuration, and reporting on WIP supply types or ship-from organizations per model. A representative query joins the table to the order header and line tables:

• List all CTO lines for an order: SELECT line_id, ato_line_id, inventory_item_id, ordered_quantity FROM bom_cto_order_lines WHERE header_id = :p_header_id;
• Resolve parent-child links: SELECT a.line_id, a.parent_ato_line_id, b.inventory_item_id FROM bom_cto_order_lines a, bom_cto_order_lines b WHERE a.parent_ato_line_id = b.ato_line_id;
• Identify option-specific configurations: ... WHERE option_specific = 'Y' AND reuse_config = 'N';

These patterns support order promising, configuration validation, and fulfillment reporting, particularly when the top model explodes into multiple option classes.

Related Objects

The table references several core BOM and order objects through its key columns:

• OE_ORDER_HEADERS_ALL — joined via HEADER_ID.
• OE_ORDER_LINES_ALL — joined via LINE_ID, TOP_MODEL_LINE_ID, and ATO_LINE_ID.
• BOM_BILL_OF_MATERIALS — configuration structures linked through COMPONENT_SEQUENCE_ID and CONFIG_ITEM_ID.
• MTL_SYSTEM_ITEMS_B — joined via INVENTORY_ITEM_ID.
• MTL_PARAMETERS / ORG_ORGANIZATION_DEFINITIONS — linked via SHIP_FROM_ORG_ID.

These relationships make BOM_CTO_ORDER_LINES the operational bridge between order capture and configured manufacturing execution.