Results for “mrp_atp_v”

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

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.

• BOM objects: BOM_BILL_OF_MATERIALS (view), BOM_INVENTORY_COMPONENTS (view), BOM_CALENDAR_DATES, BOM_DEPARTMENTS, BOM_DEPARTMENT_RESOURCES, BOM_OPERATIONAL_ROUTINGS, BOM_OPERATION_RESOURCES, BOM_OPERATION_SEQUENCES, and BOM_RESOURCES — supplying structure, routings, resources, and ATP calendar dates.
• Inventory objects: MTL_SYSTEM_ITEMS, MTL_UOM_CONVERSIONS, MTL_PARAMETERS, MTL_DEMAND_INTERFACE — supplying item master attributes, UOM conversion factors, organization parameters, and demand records.
• WIP: WIP_LINES — supplying work-in-process job/schedule lines for CTP context.
• Oracle Foundation: FND_GLOBAL and FND_PROFILE packages — providing session context, organization ID, and profile option values used inside the view.

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

• INVENTORY_ITEM_ID and ORGANIZATION_ID — the core keys linking demand, item, and inventory context. Note that the view exposes both I3.INVENTORY_ITEM_ID and D.INVENTORY_ITEM_ID; the latter is the demand-side item.
• ATP_GROUP_ID, USER_LINE_NUM — grouping and sequencing identifiers for ATP result sets.
• REQUEST_DATE_ATP_QUANTITY, EARLIEST_ATP_DATE, EARLIEST_ATP_DATE_QUANTITY, REQUEST_ATP_DATE, REQUEST_ATP_DATE_QUANTITY, GROUP_AVAILABLE_DATE — the central ATP result columns describing available quantity and the earliest/requested promise dates.
• ACCUMULATION_WINDOW, ATP_LEAD_TIME, ATP_CHECK, INFINITE_TIME_FENCE_DATE — ATP behavior and scheduling parameters.
• RESOURCE_ID, RESOURCE_CODE, DEPARTMENT_ID, DEPARTMENT_CODE — CTP context identifying the resource and department supplying capacity.
• DEMAND_CLASS, DEMAND_SOURCE_TYPE, DEMAND_SOURCE_HEADER_ID, DEMAND_SOURCE_LINE, DEMAND_SOURCE_DELIVERY, DEMAND_SOURCE_NAME — demand origination traceability, typically populated via MTL_DEMAND_INTERFACE.
• LATEST_ACCEPTABLE_DATE, ERROR_CODE, ERR_EXPLANATION — viability and error signaling for ATP checks.
• UOM_CODE, CALENDAR_DATE, plus standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and a full set of DFF/attribute columns and C/N/D_COLUMN placeholders.

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.