Results for “atp_lead_time”

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

Overview

MRP_ATP_BASE_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is delivered as part of the MRP (Master Scheduling/MRP) product family and is documented as the ATP/CTP View. Its purpose is to expose the base result set produced by Oracle's Available-to-Promise (ATP) and Capable-to-Promise (CTP) scheduling engine, combining resource-level and material-level availability information into a single queryable structure. The view is not a table and holds no data of its own; it is a projection over existing transactional and planning tables. Because it resides in APPS and is defined over SYNONYM-accessible base objects, it can be queried from SQL*Plus, TOAD, or any external reporting layer, and it is commonly referenced by concurrent programs, Discoverer workbooks, and custom PL/SQL that need to interrogate ATP/CTP results without calling the scheduling engine directly.

Underlying Base Objects

The documented ETRM metadata lists six referenced base objects, all exposed through SYNONYMs: BOM_DEPARTMENTS, BOM_RESOURCES, MTL_DEMAND_INTERFACE, MTL_PARAMETERS, MTL_SYSTEM_ITEMS, and WIP_LINES. The view text confirms these joins explicitly. BOM_RESOURCES (aliased R) supplies resource identity and descriptive data, while BOM_DEPARTMENTS (aliased DEPT) supplies department codes and descriptions used for resource-level ATP/CTP rows. The MTL_DEMAND_INTERFACE table (aliased D) provides the core ATP/CTP demand and supply records, including ATP group, request dates, ATP quantities, lead times, and the C_COLUMN and N_COLUMN flex fields. MTL_SYSTEM_ITEMS anchors the inventory item context, MTL_PARAMETERS supplies organization-level defaults and calendar context, and WIP_LINES provides the work-in-process supply records that participate in CTP evaluation. The joins across these objects produce one row per ATP/CTP result record, with resource-based rows tagged through a RESOURCES comment marker in the select list.

Key Columns

The view exposes a broad set of columns. Identity and grouping columns include ATP_GROUP_ID, ORGANIZATION_ID, INVENTORY_ITEM_ID, SESSION_ID, and SCHEDULE_GROUP_ID. Resource attributes appear as RESOURCE_ID, RESOURCE_CODE, DEPARTMENT_ID, DEPARTMENT_CODE, and the department DESCRIPTION. Planning and availability columns include LINE_ITEM_QUANTITY, REQUEST_DATE_ATP_QUANTITY, EARLIEST_ATP_DATE, EARLIEST_ATP_DATE_QUANTITY, REQUEST_ATP_DATE, REQUEST_ATP_DATE_QUANTITY, GROUP_AVAILABLE_DATE, ATP_LEAD_TIME, ACCUMULATION_WINDOW, INFINITE_TIME_FENCE_DATE, and LATEST_ACCEPTABLE_DATE. Rule and control columns include ATP_RULE_ID, ATP_CHECK, GROUP_ATP_CHECK, and ACTION_CODE. Demand context columns include DEMAND_CLASS, DEMAND_SOURCE_TYPE, DEMAND_SOURCE_HEADER_ID, DEMAND_SOURCE_LINE, DEMAND_SOURCE_NAME, and CUSTOMER_ID. Error diagnostics are captured in ERROR_CODE and ERR_EXPLANATION. The view also carries a derived sort key based on RESOURCE_ID and C_COLUMN8, plus the standard audit columns LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN, and the ATTRIBUTE1 through ATTRIBUTE15 descriptive flex fields.

Common Use Cases and Queries

Typical uses include diagnosing why an ATP check failed, reviewing ATP quantities by date for a specific item and organization, and validating CTP results for resource-constrained scheduling. A representative query for item-level ATP history is shown below.

• Filter by ORGANIZATION_ID and INVENTORY_ITEM_ID to isolate a single item's ATP records.
• Use ERROR_CODE and ERR_EXPLANATION to surface scheduling failures for troubleshooting.
• Join to MTL_SYSTEM_ITEMS on INVENTORY_ITEM_ID for item descriptions and to BOM_RESOURCES on RESOURCE_ID for resource detail.

SELECT atp.organization_id,
       atp.inventory_item_id,
       atp.resource_id,
       atp.request_atp_date,
       atp.request_atp_date_quantity,
       atp.earliest_atp_date,
       atp.earliest_atp_date_quantity,
       atp.atp_rule_id,
       atp.error_code,
       atp.err_explanation
  FROM apps.mrp_atp_base_v atp
 WHERE atp.organization_id = :org_id
   AND atp.inventory_item_id = :item_id
 ORDER BY atp.request_atp_date;

Because MRP_ATP_BASE_V consolidates resource, department, item, parameter, demand interface, and WIP line data into one structure, it remains the standard reporting entry point for ATP/CTP diagnostics in both 12.1.1 and 12.2.2.