Search Results mrp_ad_cto_order_demand




Overview
Explore in AI Chat

Overview

MRP_AD_CTO_ORDER_DEMAND is a table owned by the MRP schema (Master Scheduling/MRP product) in Oracle E-Business Suite 12.1.1 and 12.2.2. It participates in the Configure-to-Order (CTO) demand-processing stream, where sales-order lines for configured items must be exploded into their component demand before MRP/MPS planning can consume them. The AD prefix typically denotes an "application data" or staging/interface context used by MRP's CTO demand collection and netting logic, while the CTO_ORDER_DEMAND suffix ties the table to the source demand records produced by Oracle Bills of Material's CTO order demand model.

The table is registered as VALID with 11 documented columns in the 12.2.2 ETRM physical schema. Heuristic Data Vault classification mined from the foreign-key structure is standalone — it references exactly one parent table (BOM_CTO_ORDER_DEMAND) and is not joined by other documented tables through incoming foreign keys. As a modeling suggestion, this object is therefore best treated as a satellite (or a thin link-plus-satellite) attached to the CTO order demand hub represented by BOM_CTO_ORDER_DEMAND, carrying planning-specific attributes about each demand line.

Key Information Stored

The column set is compact and centers on identifying the order line and its planning context:

  • OE_LINE_ID — the order-entry line identifier, linking the record back to the originating sales-order line in Oracle Order Management.
  • HEADER_ID — the order header identifier for the parent sales order.
  • ORGANIZATION_ID — the inventory organization in which the demand is planned; critical for multi-org reporting and MRP netting.
  • BCOD_LINE_ID — the foreign key to BOM_CTO_ORDER_DEMAND.BCOD_LINE_ID, anchoring this row to its CTO demand parent and the surrogate identifier of that parent.
  • RN — a sequence or rank number used to order or version the demand rows during processing.
  • CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO-column audit attributes.
  • LAST_UPDATED_DATE, PROGRAM_UPDATE_DATE — timestamps marking row maintenance and concurrent-program updates.
  • PROGRAM_APPLICATION_ID — identifies the concurrent program/application that last wrote the row.

No explicit surrogate primary key or unique index is documented in the ETRM metadata beyond the FK relationship; BCOD_LINE_ID combined with ORGANIZATION_ID and RN is the most credible business-key candidate for deduplication.

Common Use Cases and Queries

Typical scenarios include diagnosing missing CTO component demand in MRP plans, reconciling sales-order lines against exploded demand, and auditing which concurrent program last refreshed a planning row.

  • Join to the parent to trace demand: SELECT d.OE_LINE_ID, d.ORGANIZATION_ID, d.RN FROM MRP.MRP_AD_CTO_ORDER_DEMAND d, BOM.BOM_CTO_ORDER_DEMAND b WHERE d.BCOD_LINE_ID = b.BCOD_LINE_ID;
  • Filter by organization and recency: WHERE ORGANIZATION_ID = :org AND PROGRAM_UPDATE_DATE > :since
  • Detect orphaned demand: left-outer join to BOM_CTO_ORDER_DEMAND and select rows where the parent key is null.
  • Volume/trend reporting by organization and update date to spot stalled CTO demand collection.

Related Objects