Search Results request_date_atp_quantity




Overview

The APPS.MRP_PF_ATP_V view is a Master Scheduling/MRP (MRP) module database object used to support Available-to-Promise (ATP) processing and inquiry within Oracle E-Business Suite 12.1.1 and 12.2.2. It is a view rather than a standalone table, and its record definition is derived from the MTL_DEMAND_INTERFACE table, which acts as the staging area for demand and ATP-related request records. The view exposes ATP-relevant attributes—such as requested quantities, ATP dates, ATP rules, and grouping information—so that ATP checks can be evaluated against staged demand records without directly querying the interface table.

Because the view is owned by the APPS schema and is reported as VALID in the ETRM metadata, it is available for reporting and integration queries within the standard EBS security model. Its primary role is to present a consolidated, item-aware ATP picture, allowing external programs, concurrent requests, and custom reports to retrieve ATP information keyed by organization, item, and ATP group. The view text applies DECODE logic against MTL_SYSTEM_ITEMS to substitute the ATP item, ATP rule, and related values when the item is a product-family style configuration (BOM_ITEM_TYPE = 5) with the ATP flag enabled.

Underlying Base Objects

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

The join conditions tie the interface demand row to a valid inventory item in the same organization, then resolve the applicable ATP item and rule. This design ensures that ATP evaluation respects both item-level and organization-level ATP configuration.

Key Columns

Common Use Cases and Queries

Typical uses include diagnosing ATP failures, reporting requested versus available ATP quantities, and validating staged demand interface records prior to processing. A representative query retrieving requested ATP quantity by organization and item:

  • SELECT organization_id, inventory_item_id, request_date_atp_quantity, request_atp_date, earliest_atp_date, atp_rule_id FROM apps.mrp_pf_atp_v WHERE organization_id = :org_id AND inventory_item_id = :item_id;
  • SELECT atp_group_id, SUM(request_date_atp_quantity) FROM apps.mrp_pf_atp_v GROUP BY atp_group_id;
  • SELECT * FROM apps.mrp_pf_atp_v WHERE error_code IS NOT NULL;

These queries support ATP review, error triage, and exception reporting against the ATP-enabled demand staged in MTL_DEMAND_INTERFACE.