Search Results bom_cto_order_demand
Overview
BOM_CTO_ORDER_DEMAND (internally referenced as BCOD) is an Oracle Bills of Material table that stores Configure-to-Order (CTO) order demand records. It captures the demand generated against an assemble-to-order (ATO) configuration model when a sales order line is booked, providing the demand-side counterpart that Oracle's planning and manufacturing engines consume during configuration explosion, scheduling, and fulfillment. The table resides in the BOM schema and is classified as VALID in both Oracle EBS 12.1.1 and 12.2.2.
In Data Vault modeling terms, the heuristic classification mined from the foreign key structure is standalone. This suggests the table behaves as an independent entity rather than a strict hub, link, or satellite, primarily because no inbound foreign keys from peer BOM tables define it and its only documented relationship is an outbound reference from MRP_AD_CTO_ORDER_DEMAND. Modelers treating this as a hub should validate whether OE_LINE_ID, ATO_LINE_ID, or HEADER_ID carry sufficient business-key uniqueness; the documented unique business-key candidate is the primary key itself.
Key Information Stored
The table contains 18 documented columns. The most significant are:
- BCOD_LINE_ID — Surrogate primary key (BOM_CTO_ORDER_DEMAND_PK) and the single unique business-key candidate (BOM_CTO_ORDER_DEMAND_U1). It is the join column referenced by MRP_AD_CTO_ORDER_DEMAND.
- OE_LINE_ID — Identifies the originating Order Entry (OE) sales order line that spawned the CTO demand.
- ATO_LINE_ID — Links to the assemble-to-order configuration line, correlating the demand to its configured model context.
- HEADER_ID — The order header, enabling demand aggregation at the order level.
- INVENTORY_ITEM_ID — The item for which demand is recorded.
- ORGANIZATION_ID — The inventory organization that owns the demand, essential for multi-org reporting.
- REQUIRED_DATE — The date the demand must be satisfied.
- REQUIRED_QTY — The quantity required to fulfill the demand.
- ORDER_QUANTITY_UOM — Unit of measure for the ordered quantity.
- PARENT_DEMAND_TYPE — Classifies the demand's parent relationship (e.g., sales order versus other demand sources).
- FORECAST_VISIBLE and DEMAND_VISIBLE — Flags controlling visibility of the record to forecasting and demand planning processes.
- Audit columns — CREATED_BY, LAST_UPDATED_BY, LAST_UPDATED_DATE, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, and PROGRAM_UPDATE_DATE provide standard who-column and concurrent program lineage.
Common Use Cases and Queries
Primary use cases include diagnosing CTO demand visibility in planning, reconciling sales order lines to their configuration demand records, and reporting on required quantities and dates by organization. A typical query joins BCOD to the order line to trace demand:
- SELECT bc.oe_line_id, bc.ato_line_id, bc.inventory_item_id, bc.required_qty, bc.required_date FROM bom_cto_order_demand bc WHERE bc.organization_id = :org_id AND bc.demand_visible = 'Y';
- Identify demand suppressed from forecasting: filter WHERE forecast_visible = 'N'.
- Reconcile plan rows by joining to mrp_ad_cto_order_demand ON mrp.bcod_line_id = bc.bcod_line_id.
- Aggregate required quantities by item and required_date for capacity planning.
Related Objects
- MRP_AD_CTO_ORDER_DEMAND — References BOM_CTO_ORDER_DEMAND.BCOD_LINE_ID; the principal dependent planning table.
- OE_ORDER_LINES_ALL — Source of OE_LINE_ID and order-line context.
- OE_ORDER_HEADERS_ALL — Source of HEADER_ID.
- MTL_SYSTEM_ITEMS_B — Resolves INVENTORY_ITEM_ID.
- ORG_ORGANIZATION_DEFINITIONS — Resolves ORGANIZATION_ID for multi-org reporting.
- BOM_CTO_ORDER_DEMAND_U1 / _PK — Unique index and primary key enforcing BCOD_LINE_ID integrity.
-
Table: BOM_CTO_ORDER_DEMAND
12.2.2
owner:BOM, object_type:TABLE, fnd_design_data:BOM.BOM_CTO_ORDER_DEMAND, object_name:BOM_CTO_ORDER_DEMAND, status:VALID, product: BOM - Bills of Material , description: BCOD , implementation_dba_data: BOM.BOM_CTO_ORDER_DEMAND ,
-
Table: BOM_CTO_ORDER_DEMAND
12.1.1
owner:BOM, object_type:TABLE, fnd_design_data:BOM.BOM_CTO_ORDER_DEMAND, object_name:BOM_CTO_ORDER_DEMAND, status:VALID, product: BOM - Bills of Material , description: BCOD , implementation_dba_data: BOM.BOM_CTO_ORDER_DEMAND ,
-
VIEW: BOM.BOM_CTO_ORDER_DEMAND#
12.2.2
owner:BOM, object_type:VIEW, object_name:BOM_CTO_ORDER_DEMAND#, status:VALID,
-
SYNONYM: APPS.BOM_CTO_ORDER_DEMAND
12.2.2
owner:APPS, object_type:SYNONYM, object_name:BOM_CTO_ORDER_DEMAND, status:VALID,
-
SYNONYM: APPS.BOM_CTO_ORDER_DEMAND
12.1.1
owner:APPS, object_type:SYNONYM, object_name:BOM_CTO_ORDER_DEMAND, status:VALID,
-
VIEW: BOM.BOM_CTO_ORDER_DEMAND#
12.2.2
-
TABLE: BOM.BOM_CTO_ORDER_DEMAND
12.2.2
owner:BOM, object_type:TABLE, fnd_design_data:BOM.BOM_CTO_ORDER_DEMAND, object_name:BOM_CTO_ORDER_DEMAND, status:VALID,
-
TABLE: BOM.BOM_CTO_ORDER_DEMAND
12.1.1
owner:BOM, object_type:TABLE, fnd_design_data:BOM.BOM_CTO_ORDER_DEMAND, object_name:BOM_CTO_ORDER_DEMAND, status:VALID,
-
APPS.CTO_ORDER_PURGE SQL Statements
12.1.1
-
APPS.CTO_ORDER_PURGE SQL Statements
12.2.2
-
PACKAGE BODY: APPS.CTO_ORDER_PURGE
12.2.2
-
PACKAGE BODY: APPS.CTO_ORDER_PURGE
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:CTO_ORDER_PURGE, status:VALID,
-
PACKAGE BODY: APPS.CTO_ORDER_PURGE
12.1.1
-
PACKAGE BODY: APPS.CTO_ORDER_PURGE
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:CTO_ORDER_PURGE, status:VALID,
-
PACKAGE BODY: APPS.CTO_ATP_INTERFACE_PK
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:CTO_ATP_INTERFACE_PK, status:VALID,
-
PACKAGE BODY: APPS.CTO_ATP_INTERFACE_PK
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:CTO_ATP_INTERFACE_PK, status:VALID,
-
APPS.CTO_ATP_INTERFACE_PK SQL Statements
12.1.1
-
APPS.CTO_ATP_INTERFACE_PK SQL Statements
12.2.2
-
12.2.2 DBA Data
12.2.2
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
PACKAGE BODY: APPS.CTO_CONFIG_ITEM_PK
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:CTO_CONFIG_ITEM_PK, status:VALID,
-
PACKAGE BODY: APPS.CTO_CONFIG_ITEM_PK
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:CTO_CONFIG_ITEM_PK, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.1.1 FND Design Data
12.1.1
-
12.2.2 FND Design Data
12.2.2
-
12.2.2 DBA Data
12.2.2
-
APPS.CTO_ATP_INTERFACE_PK dependencies on BOM_CTO_ORDER_DEMAND
12.1.1
-
APPS.CTO_CONFIG_ITEM_PK dependencies on BOM_CTO_ORDER_DEMAND
12.1.1
-
APPS.CTO_ATP_INTERFACE_PK dependencies on BOM_CTO_ORDER_DEMAND
12.2.2
-
APPS.CTO_CONFIG_ITEM_PK dependencies on BOM_CTO_ORDER_DEMAND
12.2.2
-
APPS.CTO_ORDER_PURGE dependencies on BOM_CTO_ORDER_DEMAND
12.1.1
-
APPS.CTO_ORDER_PURGE dependencies on BOM_CTO_ORDER_DEMAND
12.2.2
-
PACKAGE BODY: APPS.CTO_ATP_INTERFACE_PK
12.1.1
-
PACKAGE BODY: APPS.CTO_ATP_INTERFACE_PK
12.2.2
-
APPS.CTO_CONFIG_ITEM_PK SQL Statements
12.1.1
-
APPS.CTO_CONFIG_ITEM_PK SQL Statements
12.2.2
-
APPS.CTO_ORDER_PURGE dependencies on OE_DEBUG_PUB
12.1.1
-
APPS.CTO_ORDER_PURGE dependencies on OE_DEBUG_PUB
12.2.2
-
APPS.CTO_ATP_INTERFACE_PK dependencies on FND_GLOBAL
12.1.1
-
APPS.CTO_ATP_INTERFACE_PK dependencies on FND_GLOBAL
12.2.2
-
APPS.CTO_ATP_INTERFACE_PK dependencies on MRP_ATP_DETAILS_TEMP
12.1.1
-
APPS.CTO_ATP_INTERFACE_PK dependencies on MRP_ATP_DETAILS_TEMP
12.2.2
-
APPS.CTO_ORDER_PURGE dependencies on BOM_CTO_ORDER_LINES
12.1.1
-
APPS.CTO_ORDER_PURGE dependencies on BOM_CTO_ORDER_LINES
12.2.2
-
PACKAGE BODY: APPS.CTO_CONFIG_ITEM_PK
12.1.1
-
PACKAGE BODY: APPS.CTO_CONFIG_ITEM_PK
12.2.2