Search Results requested_arrival_date

Overview

MRP_ATP_BACKLOG_TEMP_V is a view owned by the APPS schema in Oracle E-Business Suite, defined within the MRP (Master Scheduling/MRP) product family. Its primary function is to present, in a single flattened result set, the backlog and scheduling rows held in the temporary ATP (Available-to-Promise) scheduling table. The view is defined as a UNION of two SELECT statements over the same base object, MRP_ATP_SCHEDULE_TEMP, which allows it to combine two logically distinct categories of scheduling rows into one consistent structure.

In the ETRM 12.2.2 metadata the view is reported with a status of VALID, and its only documented referenced base object is the synonym MRP_ATP_SCHEDULE_TEMP. Because the object is a VIEW rather than a stored table, it holds no data of its own; it is a query-time presentation layer used by Oracle's ATP and scheduling logic and available for reporting and integration purposes.

Underlying Base Objects

The view is defined exclusively over MRP_ATP_SCHEDULE_TEMP (referenced through the synonym of the same name). The first branch of the UNION selects every row from that table without restriction. The second branch selects only those rows where either SHIP_SET_NAME or ARRIVAL_SET_NAME is not null, and it projects nulls into the order-line, shipment, option, quantity, and unit-of-measure columns while retaining set-related and firm-source information.

The net effect is that a single row from MRP_ATP_SCHEDULE_TEMP may appear more than once in the view when it carries a ship set or an arrival set. Columns such as SHIP_SET_NAME, SHIP_SET_ID, ARRIVAL_SET_NAME, and ARRIVAL_SET_ID therefore act as the discriminator between the two branches and should be considered when de-duplicating or aggregating results.

Key Columns

• SESSION_ID — Identifier of the ATP session under which the temporary scheduling rows were generated; the principal filter for isolating a specific scheduling run.
• OVERRIDE_FLAG — Indicates whether the schedule was manually overridden.
• SEQUENCE_NUMBER — Ordering sequence for the rows within a session.
• ORDER_NUMBER, ORDER_LINE_NUMBER, ORDER_LINE_ID, SHIPMENT_NUMBER, OPTION_NUMBER — Sales-order and shipment identity of the demand being scheduled.
• SHIP_SET_NAME, SHIP_SET_ID, ARRIVAL_SET_NAME, ARRIVAL_SET_ID — Ship-set and arrival-set identifiers used to group related demand lines.
• INVENTORY_ITEM_NAME, SOURCE_ORGANIZATION_CODE, SOURCE_ORGANIZATION_ID — Item and source organization context for the schedule.
• QUANTITY_ORDERED, UOM_CODE — Ordered quantity and its unit of measure.
• REQUESTED_SHIP_DATE, REQUESTED_ARRIVAL_DATE, SCHEDULED_SHIP_DATE, SCHEDULED_ARRIVAL_DATE, PROMISE_DATE — The requested, scheduled, and promised dates that drive ATP and backlog analysis.
• FIRM_SOURCE_ORG_ID, FIRM_SOURCE_ORG_CODE, FIRM_SHIP_DATE, FIRM_ARRIVAL_DATE — The firmed sourcing organization and its dates.

Common Use Cases and Queries

The view is typically used to inspect the backlog and scheduling detail produced by an ATP run for a given session, and to reconcile requested versus scheduled and promised dates. A representative query filtering on a session follows:

• SELECT session_id, order_number, order_line_number, inventory_item_name, quantity_ordered, uom_code, requested_arrival_date, scheduled_arrival_date, promise_date FROM apps.mrp_atp_backlog_temp_v WHERE session_id = :p_session_id ORDER BY sequence_number;
• Because set-based rows are duplicated across the UNION, aggregations should group by ORDER_LINE_ID, SHIP_SET_ID, and ARRIVAL_SET_ID, or filter on the relevant set columns, to avoid double counting.
• Reporting on the arrival_set_id or ship_set_id columns supports analysis of multi-line set groupings within a single scheduling session.

Results reflect the transient contents of MRP_ATP_SCHEDULE_TEMP at query time and are dependent on the ATP process having populated the temporary table for the session being examined.