Search Results atp_lead_time




Overview
Explore in AI Chat

Overview

APPS.MTL_GROUP_ATPS_VIEW is a reporting and integration view in Oracle E-Business Suite 12.1.1 and 12.2.2 that exposes group-level available-to-promise (ATP) and scheduling data held in the demand interface. As documented in the ETRM metadata, the view is defined as a projection over MTL_DEMAND_INTERFACE and returns the full set of ATP grouping, quantity, date, and descriptive columns required by the ATP and scheduling engines. Its principal role is to present ATP group results — including the earliest ATP date — in a stable, query-friendly shape for concurrent programs, diagnostic reports, and custom extensions. Because the view is a single-table projection, it preserves the ROWID of MTL_DEMAND_INTERFACE, meaning that rows returned can be correlated directly to their source records for update, deletion, or troubleshooting. The inclusion of the EARLIEST_ATP_DATE column makes the view particularly relevant to users investigating scheduling and promise-date behavior, since that column records the earliest point in time at which the grouped demand quantity can be satisfied.

Underlying Base Objects

The documented base object for the view is MTL_DEMAND_INTERFACE, referenced through an APPS-owned synonym. The view text is a straightforward SELECT that lists columns explicitly rather than using a wildcard, so the column order and datatypes are deterministic and aligned with the underlying interface table. The view does not join to additional tables, meaning all ATP grouping attributes and derived scheduling values are materialized in MTL_DEMAND_INTERFACE before the view is queried. This design reflects the fact that MTL_DEMAND_INTERFACE is the staging area populated by the ATP and scheduling processes, and the view exists to expose that staged result set to application code and reporting. No other base objects are documented in the ETRM metadata.

Key Columns

Common Use Cases and Queries

The view is typically used to inspect or report on group ATP results produced during order promising, to diagnose why a requested date could not be met, or to extract earliest and request-date availability for a session or ATP group. A representative query filtering by item and organization would resemble the following:

SELECT ATP_GROUP_ID, ORGANIZATION_ID, INVENTORY_ITEM_ID,
       LINE_ITEM_QUANTITY, EARLIEST_ATP_DATE,
       EARLIEST_ATP_DATE_QUANTITY, REQUEST_ATP_DATE,
       REQUEST_ATP_DATE_QUANTITY, ERROR_CODE, ERR_EXPLANATION
  FROM APPS.MTL_GROUP_ATPS_VIEW
 WHERE INVENTORY_ITEM_ID = :item_id
   AND ORGANIZATION_ID   = :org_id
   AND SESSION_ID        = :session_id
 ORDER BY EARLIEST_ATP_DATE;

Because the view is read-only over the demand interface, insert, update, and delete operations should be performed against MTL_DEMAND_INTERFACE directly rather than through the view.