Search Results infinite_time_fence_date




Overview
Explore in AI Chat

Overview

MTL_GROUP_ATPS_VIEW is an Oracle E-Business Suite (EBS) database view owned by the APPS schema and classified under the INV – Inventory product. Its documented status is VALID, and it is defined as an ATP (Available-to-Promise) view derived from MTL_DEMAND_INTERFACE. Within the Oracle EBS 12.1.1 and 12.2.2 architectures, this view provides a consolidated, read-oriented projection of demand interface rows processed during group ATP calculations. It presents grouped ATP demand records — including schedule group, ATP group, and ATP rule identifiers — together with the calculated date and quantity attributes produced by the ATP engine, such as earliest ATP date, request ATP date, and group available date. Because the view abstracts the physical demand interface table, it supports reporting and integration scenarios where third-party planning, order-promising, or custom scheduling programs need to inspect ATP outcomes without writing directly to the underlying transactional interface table. The view is particularly relevant to users searching on the LATEST_ACCEPTABLE_DATE attribute, which is exposed as a column and represents the final date by which a demand line can still be fulfilled while satisfying the promise constraints established by the ATP routine. LATEST_ACCEPTABLE_DATE is populated during ATP processing and is a key input to scheduling and order-promising decisions, because it bounds the acceptable fulfillment window for a given grouped demand record.

Underlying Base Objects

The documentation identifies a single referenced base object: MTL_DEMAND_INTERFACE, accessed through a synonym in the APPS schema. The view text explicitly selects all of its columns from MTL_DEMAND_INTERFACE using a direct SELECT with an unqualified table reference, meaning the view is a straight column projection rather than a join or aggregation. No joins, unions, or analytic functions appear in the documented view definition, so row cardinality and filtering behavior mirror the underlying interface table exactly. In Oracle EBS, MTL_DEMAND_INTERFACE stores demand records loaded by planning, order management, and scheduling transactions before the ATP engine processes them. The view therefore serves as a stable, group-oriented naming layer over that interface table, exposing ATP-specific column aliases — for example, LINE_ITEM_QUANTITY, LINE_ITEM_UOM, REQUEST_ATP_DATE, and INFINITE_TIME_FENCE_DATE — while the physical columns retain their original names in MTL_DEMAND_INTERFACE. Because the underlying object is a synonym resolving within APPS, the view remains accessible under standard EBS responsibility and security constructs without granting direct access to the base table.

Key Columns

Common Use Cases and Queries

Typical uses include reviewing ATP run output, diagnosing promise-date discrepancies, and integrating ATP results with custom scheduling or order-promising logic. A frequent query searches by item and organization while isolating records approaching or exceeding the latest acceptable date. For example:

SELECT ATP_GROUP_ID, ORGANIZATION_ID, INVENTORY_ITEM_ID, REQUEST_ATP_DATE, EARLIEST_ATP_DATE, LATEST_ACCEPTABLE_DATE, LINE_ITEM_QUANTITY, DEMAND_SOURCE_NAME FROM APPS.MTL_GROUP_ATPS_VIEW WHERE INVENTORY_ITEM_ID = :p_item AND ORGANIZATION_ID = :p_org AND LATEST_ACCEPTABLE_DATE < SYSDATE + 7 ORDER BY LATEST_ACCEPTABLE_DATE;

A second pattern reconciles a specific ATP run by schedule group and session, retrieving errors alongside promise results:

SELECT SCHEDULE_GROUP_ID, SESSION_ID, LINE_NUMBER, ATP_CHECK, GROUP_ATP_CHECK, ERROR_CODE, ERR_EXPLANATION FROM APPS.MTL_GROUP_ATPS_VIEW WHERE SCHEDULE_GROUP_ID = :p_group AND SESSION_ID = :p_session;

Because the view is a direct projection of MTL_DEMAND_INTERFACE, it should be treated as read-only for reporting; modifications belong to the base table or to supported ATP APIs. In both 12.1.1 and 12.2.2 the definition and column set are consistent, so queries written against this view remain portable across those releases. Users should note that the view exposes all rows of the interface table, so filtering by SESSION_ID, SCHEDULE_GROUP_ID, or ORGANIZATION_ID is advisable to limit result sets.