Search Results ato_flag

Overview

The MRP_RHX_SALES_ORDERS_HISTORY_V view is an Oracle Master Scheduling/MRP (MRP) Integration Toolkit object that exposes the historical shipment activity of sales orders relating to planned items. It belongs to the Rapid Implementation (RHX) family of integration views used by Oracle's planned-item data collections, most notably the MRP / ASCP planning data repository and related demand history extracts. The view presents a consolidated, read-only projection that joins sales order headers, sales order lines, shipping details, the planned-items integration view, and customer information to produce a single row per shipped sales order line.

The view is intended for reporting and integration consumers—such as planning engines, custom concurrent programs, and external data warehouses—that require a normalized history of fulfilled demand for items under planning control. Because it derives from the Integration Toolkit and is described in the ETRM metadata as “not implemented in this database,” it may not exist in every environment by default and should be validated against the deployed schema before use.

Underlying Base Objects

The ETRM 12.2.2 metadata records no explicitly documented base objects, but the embedded view text reveals the constituent sources:

• OE_ORDER_HEADERS_ALL SOH — sales order header information, including order number, order type, and sold-to organization.
• OE_ORDER_LINES_ALL LINES — sales order line detail, including ordered, cancelled, and shipped quantities, demand class, schedule ship date, and ATO-related flags.
• WSH_SHIPPING_DETAILS_V WSHSDV — shipping confirmation details, used to derive the shipped quantity and warehouse.
• RA_CUSTOMERS CUST — customer name lookup.
• MRP_RHX_PLANNED_ITEMS_V ITEMS — the planned-items integration view, which restricts results to items under MRP planning.

The view is additionally gated by OE_INSTALL.GET_ACTIVE_PRODUCT = 'ONT' to ensure the Oracle Order Management product is active, and it filters to lines with a non-null LINES.SHIPPED_QUANTITY and a positive WSHSDV.SHIPPED_QUANTITY, so only genuinely fulfilled lines are returned.

Key Columns

The view exposes a broad set of columns, several of which are central to the ato_flag search term that led here:

• ATO_FLAG — derived via DECODE(LINES.ATO_LINE_ID, NULL, 'N', 'Y'), indicating whether the line is an Assemble-to-Order (ATO) configured line.
• OPTION_FL (OPTION_FLAG) — identifies ATO option lines within a configuration.
• SHIP_MODEL_COMPLETE_FLAG — denotes whether a model configuration has shipped completely.
• INVENTORY_ITEM_ID / ORGANIZATION_ID / ITEM_NUMBER — planned item identity and warehouse organization.
• LINE_ID / LINE_NUMBER / HEADER_ID / SALES_ORDER_NUMBER — sales order and line identifiers. SALES_ORDER_NUMBER is composed as ORDER_NUMBER || ':' || ORDER_TYPE_ID || ':' || FND_PROFILE.VALUE('OE_SOURCE_CODE').
• ORDERED_QUANTITY / CANCELLED_QUANTITY / SHIPPED_QUANTITY — quantity metrics for historical demand analysis.
• DEMAND_CLASS, SCHEDULE_DATE, DATE_REQUESTED_CURRENT, UOM_CODE, SHIP_SET_NUMBER — planning and scheduling attributes.
• SHIP_TO_SITE_USE_ID, SOLD_TO_ORG_ID — party and address references.
• ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield context for the order line.

Common Use Cases and Queries

Typical uses include historical demand reporting, ATO configuration analysis, and feeding planning data marts. A query to identify ATO shipment history for a given item and organization:

SELECT SALES_ORDER_NUMBER, ITEM_NUMBER, ORGANIZATION_ID,
      ORDERED_QUANTITY, SHIPPED_QUANTITY, ATO_FLAG, OPTION_FL
FROM  MRP_RHX_SALES_ORDERS_HISTORY_V
WHERE  ITEM_NUMBER = :item
AND    ATO_FLAG = 'Y';

A demand-class summary for planning:

SELECT DEMAND_CLASS, SUM(SHIPPED_QUANTITY) SHIPPED
FROM  MRP_RHX_SALES_ORDERS_HISTORY_V
WHERE  ORGANIZATION_ID = :org
GROUP  BY DEMAND_CLASS;

Because the view is restricted to planned items and confirmed shipments, it is well suited to backward-looking demand analysis rather than open-order book reporting. Verify deployment in each environment, as the metadata marks it not implemented by default.