Search Results request_atp_date_quantity




Overview
Explore in AI Chat

Overview

MRP_PF_ATP_V is an APPS-owned view in the Oracle E-Business Suite Master Scheduling/MRP module, valid in releases 12.1.1 and 12.2.2. It is documented as being used for Available-to-Promise (ATP) processing and is derived from MTL_DEMAND_INTERFACE. The view couples the transient ATP demand records staged in the demand interface with item and planning-parameter master data, resolving ATP behavior attributes such as the ATP rule, inventory item identifier, and quantity values that the ATP engine requires.

The view plays a supporting role in the ATP workflow that surrounds request date quantity calculations. Users searching for the term "request_atp_date_quantity" are typically tracing the ATP columns populated on demand interface rows; the view exposes REQUEST_ATP_DATE and REQUEST_ATP_DATE_QUANTITY, which carry the requested ATP date and the quantity that must be available on that date. Because ATP results are written back to MTL_DEMAND_INTERFACE, the view behaves as a read-side projection over that interface, presenting resolved item attributes alongside the raw demand columns.

Underlying Base Objects

The view is defined over three referenced base objects, all resolved through APPS synonyms:

Join predicates require I1.INVENTORY_ITEM_ID = D.INVENTORY_ITEM_ID and I1.ORGANIZATION_ID = D.ORGANIZATION_ID, with I2 resolving the item identity as either the product family member or a standard item. This construction allows the view to surface the ATP rule that should apply, whether inherited from MTL_PARAMETERS, defined on the item, or derived from an ATP-checked configuration item.

Key Columns

Beyond the identification and audit columns (ROWID, ORGANIZATION_ID, INVENTORY_ITEM_ID, LAST_UPDATE_DATE, CREATED_BY, and the ATTRIBUTE columns), several columns are of primary interest for ATP reporting:

Common Use Cases and Queries

This view is typically queried to inspect staged ATP requests, verify the ATP rule applied to a demand row, or diagnose unresolved request date quantity scenarios before the interface is processed. A frequent pattern is filtering the interface by ORGANIZATION_ID and SESSION_ID or SCHEDULE_GROUP_ID to isolate a batch, then reviewing the request versus earliest ATP date and quantity columns. Typical SQL resembles:

SELECT organization_id, inventory_item_id, request_atp_date, request_atp_date_quantity, earliest_atp_date, earliest_atp_date_quantity, atp_rule_id, error_code FROM apps.mrp_pf_atp_v WHERE organization_id = :org_id;

Analysts also join the view back to MTL_SYSTEM_ITEMS or MTL_PARAMETERS to audit which default ATP rule was inherited, and to MTL_DEMAND_INTERFACE for the full demand record. Because the view is read-oriented over the demand interface, it is used for inquiry and validation rather than direct DML.