Results for “mrp_atp_items_resource_v”

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

Overview

MRP_ATP_ITEMS_RESOURCE_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Master Scheduling/MRP product family and is documented as the "ATP items resource view." Its purpose is to expose the resource-level information required by Available-to-Promise (ATP) and Capable-to-Promise (CTP) processing for configured or routed items. Where a standard ATP check confirms supply availability against on-hand, planned orders, and calendars, CTP extends the check to manufacturing capacity by evaluating whether the resources at specific routing operations can support an incoming demand. This view supplies the resource definition, usage rate, offset, and calendar context needed for that evaluation.

The view is intended primarily for internal consumption by Oracle's ATP/CTP engine and for diagnostic reporting by implementers investigating why a promising result was returned for a resource-constrained item.

Underlying Base Objects

The view is defined over a mixture of BOM routing entities, MTL supply-chain tables, and one MRP view. The documented referenced base objects are:

• MRP_ATP_BASE_V (view) — provides the driving ATP rows, including resource, organization, department, demand class, ATP rule, and request date.
• BOM_OPERATIONAL_ROUTINGS — supplies the routing header, and is filtered by CTP_FLAG = 1.
• BOM_OPERATION_SEQUENCES — supplies operation sequence number, effectivity, disable date, and option-dependent flags.
• BOM_OPERATION_RESOURCES — supplies the resource-to-operation assignment and the usage rate/offset basis.
• BOM_DEPARTMENT_RESOURCES — links resources to departments, honoring shared departments.
• BOM_CALENDAR_DATES — joined twice to validate the request date against the manufacturing calendar and exception set.
• MTL_PARAMETERS — supplies the organization's calendar code.
• MTL_UOM_CONVERSIONS — joined twice to convert the resource basis UOM into the ATP UOM.

Key Columns

• ATP_GROUP_ID, ATP_RULE_ID, N_COLUMN1, DEMAND_CLASS — ATP grouping and rule attributes that govern which demand the resource answer applies to.
• ORGANIZATION_ID, INVENTORY_ITEM_ID — the organization and assembly item under evaluation (ASSEMBLY_ITEM_ID from the routing).
• DEPARTMENT_ID, RESOURCE_ID, LINE_ID — the owning department and the specific resource being checked.
• AVAILABLE_TO_ATP, AVAILABLE_24_HOURS_FLAG — flags controlling whether the resource contributes to ATP and whether it is available around the clock.
• RESOURCE_USAGE_RATE_OR_AMOUNT — the resource consumption per unit, derived from BR.USAGE_RATE_OR_AMOUNT scaled by UOM conversion rates.
• RESOURCE_OFFSET_PERCENT — the offset as a fraction (BR.RESOURCE_OFFSET_PERCENT/100) used to place the resource load in time.
• OPERATION_SEQ_NUM, OPTION_DEPENDENT_FLAG — routing operation context, including whether the operation is option-dependent.
• ATP_CALENDAR_ORGANIZATION_ID, RESOURCE_BASIS_TYPE — calendar ownership and the basis type used to compute the load.

Common Use Cases and Queries

Typical uses include validating that CTP-enabled routings exist for an item and reviewing the computed usage rate and offset. A basic query:

• SELECT organization_id, inventory_item_id, resource_id, operation_seq_num, resource_usage_rate_or_amount FROM apps.mrp_atp_items_resource_v WHERE organization_id = :org AND inventory_item_id = :item; — lists resources contributing to ATP for an assembly.
• SELECT DISTINCT resource_id, department_id FROM apps.mrp_atp_items_resource_v WHERE organization_id = :org AND available_to_atp = 'Y'; — identifies ATP-eligible resources.
• SELECT * FROM apps.mrp_atp_items_resource_v WHERE atp_rule_id = :rule AND demand_class = :class; — inspects rule and demand-class scope.

Because the view joins several routing and calendar tables with NVL-based filtering, queries should always constrain ORGANIZATION_ID and INVENTORY_ITEM_ID to limit row volume.