Search Results bom_cto_order_demand_u1

Overview

BOM.BOM_CTO_ORDER_DEMAND is a transactional table in the Oracle E-Business Suite Configure-to-Order (CTO) schema. It stores demand information for ATO (Assemble-to-Order) models, option classes, and option items. Critically, the table is populated only for multi-level and multi-organization ATO models, and it also holds the demand records for multi-organization ATO items. It therefore serves as the demand-capture layer that links sales order lines to the inventory and planning structures used to explode and fulfill configured items.

The object resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. Its documented status is VALID, with FND Design Data registered under BOM.BOM_CTO_ORDER_DEMAND. From a Data Vault modeling perspective, the ETRM metadata heuristically classifies this object as standalone — that is, it is not currently mined as a hub, link, or satellite through its foreign-key structure. It does, however, carry a primary key (BOM_CTO_ORDER_DEMAND_PK on BCOD_LINE_ID) and is itself referenced by MRP_AD_CTO_ORDER_DEMAND.

Key Information Stored

The table contains 18 documented columns. The most significant are summarized below.

• BCOD_LINE_ID — The surrogate primary key (NUMBER(10)) and the column that constitutes the unique index BOM_CTO_ORDER_DEMAND_U1. This is the business-key candidate for unique identification of each demand line.
• OE_LINE_ID — The order line identifier from OE_ORDER_LINES_ALL; the foreign key that ties the demand record back to the originating sales order line.
• ATO_LINE_ID — The ATO line identifier used to associate the demand with the configured ATO line context.
• INVENTORY_ITEM_ID — The inventory item for which demand is being recorded.
• ORGANIZATION_ID — The organization in which the demand applies, essential for multi-org ATO scenarios.
• REQUIRED_DATE and REQUIRED_QTY — The date and quantity of demand required for the item.
• ORDER_QUANTITY_UOM — The unit of measure associated with the ordered quantity.
• HEADER_ID — The order header identifier linking the demand to the sales order header.
• PARENT_DEMAND_TYPE — Classifies the nature of the parent demand relationship within the ATO structure.
• FORECAST_VISIBLE and DEMAND_VISIBLE — Flags controlling whether the demand is visible to forecasting and to demand planning respectively.
• Audit columns — CREATED_BY, LAST_UPDATED_BY, LAST_UPDATED_DATE, LAST_UPDATE_LOGIN, and PROGRAM_UPDATE_DATE support standard EBS audit and concurrent program tracing.

Two non-unique indexes support access paths: BOM_CTO_ORDER_DEMAND_N1 on OE_LINE_ID and BOM_CTO_ORDER_DEMAND_N2 on ATO_LINE_ID.

Common Use Cases and Queries

Typical scenarios involve reporting ATO demand, reconciling sales order lines to planning demand, and troubleshooting multi-level ATO configurations.

• Retrieving all demand for a specific sales order line: SELECT * FROM BOM.BOM_CTO_ORDER_DEMAND WHERE OE_LINE_ID = :p_line_id;
• Listing demand visible to planning: SELECT BCOD_LINE_ID, INVENTORY_ITEM_ID, REQUIRED_DATE, REQUIRED_QTY FROM BOM.BOM_CTO_ORDER_DEMAND WHERE DEMAND_VISIBLE = 'Y';
• Joining to the sales order line for descriptive context: SELECT d.BCOD_LINE_ID, l.line_number, l.ordered_item, d.REQUIRED_QTY FROM BOM.BOM_CTO_ORDER_DEMAND d JOIN OE_ORDER_LINES_ALL l ON l.line_id = d.OE_LINE_ID WHERE d.ORGANIZATION_ID = :org_id;
• Aggregating required quantities by item and date for supply/demand review.

Because demand records exist only for multi-level and multi-org ATO models, queries expecting a row for every configured order will over-count on single-level configurations and should be filtered accordingly.

Related Objects

• MRP_AD_CTO_ORDER_DEMAND — References this table via BCOD_LINE_ID; used in the advanced supply chain planning demand interface.
• OE_ORDER_LINES_ALL — Source of OE_LINE_ID; the primary sales order line table.
• OE_ORDER_HEADERS_ALL — Related through HEADER_ID for order header context.
• MTL_SYSTEM_ITEMS_B — Resolves INVENTORY_ITEM_ID to item attributes.
• MTL_PARAMETERS — Resolves ORGANIZATION_ID to organization definitions.
• BOM_ATO_LINES and related BOM CTO views — Provide the ATO line context for ATO_LINE_ID.

These relationships make BOM_CTO_ORDER_DEMAND a pivotal junction between sales order capture and Oracle planning/CTO explosion processes.