Search Results mrp_atp_v




Overview
Explore in AI Chat

Overview

MRP_ATP_V is a valid APPS-schema view in Oracle E-Business Suite 12.1.1 and 12.2.2, owned by the APPS schema and belonging to the MRP (Master Scheduling/MRP) product family. It exposes Available-to-Promise (ATP) and Capable-to-Promise (CTP) scheduling data, combining demand-side requirements with supply, resource, and bill-of-material context so that planners, order-management processes, and custom reports can evaluate whether a requested item quantity and date can be promised. The view sits at the intersection of inventory, bills of material, work-in-process, and MRP demand data; it is not a base table but a query surface designed to unify disparate ATP-related records. Because the view text is dated and internally selective — several columns are literally TO_NUMBER(NULL), TO_CHAR(NULL), or 0-( ... ) expressions — it primarily targets legacy ATP/CTP reporting and integration paths rather than public transactional APIs. As with most APPS views, direct DML is not supported; it is a read-only reporting and integration surface.

Underlying Base Objects

Per the documented ETRM metadata, MRP_ATP_V is defined over a mixture of views and synonyms across multiple modules.

This breadth explains why the view can return both item-level ATP data (from MTL_SYSTEM_ITEMS and MTL_DEMAND_INTERFACE) and resource-level CTP data (from BOM_RESOURCES and the routing tables), joining them through the organization and item identifiers.

Key Columns

Common Use Cases and Queries

MRP_ATP_V is most often queried to validate ATP/CTP results for a specific item and organization, or to integrate MRP scheduling output into custom reports. A common pattern filters on inventory item and organization:

  • Availability by item/organization: retrieve the earliest promise date and available quantity.
  • Demand-driven CTP analysis: join on DEMAND_SOURCE_HEADER_ID and DEMAND_SOURCE_LINE to trace sales-order or interface demand to its CTP result.
  • Resource capacity checks: group on RESOURCE_ID and DEPARTMENT_ID to review CTP capacity contributions.

Sample query:

  • SELECT inventory_item_id, organization_id, earliest_atp_date, earliest_atp_date_quantity, request_atp_date, request_atp_date_quantity, uom_code, error_code, err_explanation
  • FROM apps.mrp_atp_v
  • WHERE inventory_item_id = :p_item_id
  •   AND organization_id = :p_org_id
  •   AND latest_acceptable_date >= SYSDATE
  • ORDER BY request_atp_date, inventory_item_id;

Because the view joins many modules and includes complex expressions, filters on INVENTORY_ITEM_ID and ORGANIZATION_ID should always be supplied to keep queries performant and results meaningful.