Results for “re_source_flag”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.OE_MRP_OPEN_DEMANDS_V is a read-only database view in the Oracle E-Business Suite Order Management (ONT) product. Its documented purpose is to supply Material Requirements Planning (MRP) with the open demand lines the planning engine requires for the Scheduler's Workbench. In both 12.1.1 and 12.2.2 the object is deployed in the APPS schema with a status of VALID and is treated as a reporting and integration surface rather than a transactional entity; no data is stored in the view itself, and all values are derived at query time from the Order Management tables.

The view consolidates the scheduling attributes of open sales order lines — request, promise, schedule, and latest acceptable dates — into a single row per document line or shipment line. MRP's Scheduler's Workbench consumes this output to sequence and re-schedule demand against supply, which is why the view filters aggressively to expose only demand that is genuinely available to the planner.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects: OE_ORDER_HEADERS_ALL (synonym), OE_ORDER_LINES_ALL (synonym), OE_SETS (synonym), and OE_TRANSACTION_TYPES_VL (view). The header and line tables are joined on HEADER_ID, providing order-level context (order number, order date type, order type) alongside line-level scheduling data. OE_SETS is outer-joined twice, once through SHIP_SET_ID and once through ARRIVAL_SET_ID, to resolve ship-set and arrival-set names. OE_TRANSACTION_TYPES_VL supplies the transaction type name and is joined on ORDER_TYPE_ID and ORG_ID.

The view text applies several mandatory predicates. Only lines where SHIPPED_QUANTITY IS NULL and ORDERED_QUANTITY > 0 are returned, and lines whose SOURCE_TYPE_CODE is 'EXTERNAL' (outside the NVL default of 'INTERNAL') are excluded. In addition, OPEN_FLAG must equal 'Y' and NVL(VISIBLE_DEMAND_FLAG,'N') must equal 'Y'. These filters ensure the Scheduler's Workbench sees only unshipped, non-external, visible open demand.

Key Columns

• ORDER_NUMBER, HEADER_ID, LINE_ID, LINE_NUMBER, SHIPMENT_NUMBER, OPTION_NUMBER — document identity and line hierarchy.
• ORG_ID — operating unit that owns the order line.
• ORDERED_ITEM, INVENTORY_ITEM_ID — the ordered item and its inventory key.
• REQUEST_SHIP_DATE and REQUEST_ARRIVAL_DATE — the two decoded scheduling dates, split from REQUEST_DATE according to ORDER_DATE_TYPE_CODE ('ARRIVAL' routes the value to REQUEST_ARRIVAL_DATE; otherwise it lands in REQUEST_SHIP_DATE).
• PROMISE_DATE, SCHEDULE_SHIP_DATE, SCHEDULE_ARRIVAL_DATE, LATEST_ACCEPTABLE_DATE — planning dates used by the Scheduler's Workbench.
• ORDERED_QUANTITY, ORDER_QUANTITY_UOM, DELIVERY_LEAD_TIME — demand quantity and lead-time values.
• SHIP_FROM_ORG_ID, SHIP_TO_ORG_ID, SOLD_TO_ORG_ID — inventory and trading partner organization references.
• DEMAND_CLASS_CODE, FLOW_STATUS_CODE, PLANNING_PRIORITY, LINE_CATEGORY_CODE — demand classification and prioritization attributes.
• PROJECT_ID, TASK_ID, SHIPPING_METHOD_CODE, FREIGHT_CARRIER_CODE — project and shipment characteristics.
• ATO/configured-item columns such as ATO_LINE_ID, COMPONENT_NUMBER, TOP_MODEL_LINE_ID, SHIP_MODEL_COMPLETE_FLAG, plus set names from OE_SETS.

Common Use Cases and Queries

Typical use is to report open order demand by item, organization, or date window, and to verify which lines MRP considers visible. The following query lists open demands scheduled to ship within a date range:

• SELECT order_number, line_number, shipment_number, ordered_item, ordered_quantity, schedule_ship_date, promise_date, flow_status_code FROM apps.oe_mrp_open_demands_v WHERE org_id = :org_id AND schedule_ship_date BETWEEN :start_date AND :end_date ORDER BY schedule_ship_date, order_number;
• SELECT ordered_item, SUM(ordered_quantity) demand_qty FROM apps.oe_mrp_open_demands_v WHERE org_id = :org_id GROUP BY ordered_item ORDER BY demand_qty DESC;
• SELECT order_number, line_id, latest_acceptable_date, planning_priority FROM apps.oe_mrp_open_demands_v WHERE plan_priority IS NOT NULL AND org_id = :org_id;

Because the view is a database object rather than an executable concurrent program, it is queried directly through SQL, BLT, or custom reporting, and it should not be updated or extended with insert or update statements. All reported behavior is consistent with the documented ETRM metadata for release 12.2.2.