Search Results request_arrival_date




Overview
Explore in AI Chat

Overview

APPS.OE_MRP_OPEN_DEMANDS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes open, visible demand from the Order Management module in a flattened, planning-oriented format suitable for consumption by Material Requirements Planning (MRP), Advanced Supply Chain Planning (ASCP), and external reporting tools. The view answers a recurring operational question: which sales order lines are still open and expected to generate demand against inventory or supply? Because it filters on open and visible demand, it is commonly used as a source for "open demand" extracts, one of which is the spreadsheet artifact "Open Demand sheet_Apr'26.xlsx" referenced by users searching this object.

The view consolidates header-level, line-level, and transaction-type information into a single denormalized result set, eliminating the need for report authors to join the Order Management tables manually for routine demand reporting.

Underlying Base Objects

The view is defined over four documented base objects:

The join logic is significant. The view returns only lines where HEADER_ID matches the header, SHIPPED_QUANTITY IS NULL, ORDERED_QUANTITY is greater than zero, SOURCE_TYPE_CODE is not 'EXTERNAL', OPEN_FLAG equals 'Y', and NVL(VISIBLE_DEMAND_FLAG,'N') equals 'Y'. The OE_SETS joins use the Oracle outer-join operator (+), so lines without ship or arrival sets are still returned.

Key Columns

Common Use Cases and Queries

Typical applications include open-order backlog extracts, MRP/ASCP demand feeds, promise-date slippage analysis, and shipment set review. A representative query follows:

  • SELECT order_number, line_number, ordered_item, ordered_quantity, order_quantity_uom, schedule_ship_date, promise_date, ship_from_org_id FROM apps.oe_mrp_open_demands_v WHERE org_id = :p_org AND schedule_ship_date BETWEEN :p_from AND :p_to ORDER BY schedule_ship_date, order_number;
  • To aggregate by item: SELECT ordered_item, SUM(ordered_quantity) FROM apps.oe_mrp_open_demands_v GROUP BY ordered_item;
  • To isolate configured demand: filter on ato_line_id IS NOT NULL OR top_model_line_id IS NOT NULL.

Because the view returns only lines satisfying the open and visible demand predicates, no additional status filtering is generally required, though organizations frequently add ORG_ID and date range restrictions for performance.