Search Results mtl_group_item_atps_view




Overview
Explore in AI Chat

Overview

MTL_GROUP_ITEM_ATPS_VIEW is a valid APPS-owned database view in the Oracle E-Business Suite Inventory (INV) module, present in both 12.1.1 and 12.2.2. It is a focused projection over MTL_DEMAND_INTERFACE and exposes only the subset of columns required for Available-to-Promise (ATP) processing at the group-item level. The view is the read interface through which the ATP engine, planning processes, and custom extensions obtain ATP grouping, organization, item, rule, and calendar context without accessing the full, wide demand interface table. Because it is a view rather than a table, it carries no independent storage and reflects MTL_DEMAND_INTERFACE data at query time, so its contents are exactly as current as the underlying rows. This makes it suitable for reporting on pending or staged ATP check data and for joining to inventory item and organization master data, while the presence of the ATP_CHECK column ties it directly to the "atp_check" concept: each row represents an ATP evaluation request for a given group, organization, and item combination.

Underlying Base Objects

The view is defined solely over MTL_DEMAND_INTERFACE, referenced through a synonym in the APPS schema. MTL_DEMAND_INTERFACE is a standard Inventory interface table used to stage demand records prior to processing, and the documented view text confirms a straight projection with no joins, unions, or aggregation: SELECT ATP_GROUP_ID, ORGANIZATION_ID, INVENTORY_ITEM_ID, ATP_RULE_ID, ATP_CHECK, ATP_CALENDAR_ORGANIZATION_ID, N_COLUMN1, DEMAND_CLASS FROM MTL_DEMAND_INTERFACE. Consequently, all filtering, ordering, and validation semantics are inherited directly from the base table, and any DML performed against the interface table is immediately visible through the view. No other base objects are documented for this view in the ETRM 12.2.2 metadata.

Key Columns

  • ATP_GROUP_ID — Identifier of the ATP group that the row belongs to; groups related items for collective ATP evaluation.
  • ORGANIZATION_ID — Inventory organization in which the ATP check applies.
  • INVENTORY_ITEM_ID — The item being checked; joins to MTL_SYSTEM_ITEMS_B.
  • ATP_RULE_ID — The ATP rule governing how availability is calculated (lead time, past due supply/demand handling, and so on).
  • ATP_CHECK — Flag indicating the ATP check context or state; this is the column of primary interest to users searching on "atp_check". Note that the view text lists ATP_CHECK while the documented column inventory names AVAILABLE_TO_ATP, reflecting the underlying interface attribute used to carry the check/availability indicator.
  • ATP_CALENDAR_ORGANIZATION_ID — Organization whose ATP calendar is used for the availability calculation, which may differ from the transaction organization.
  • N_COLUMN1 — Generic numeric attribute column reserved for interface flexibility.
  • DEMAND_CLASS — Classification of the demand, used to segregate demand types in ATP and planning logic.

Common Use Cases and Queries

Typical usage includes diagnosing ATP group behaviour, validating staged interface rows before ATP processing, and building custom availability reports. The following examples illustrate common access patterns.

List ATP check rows for a specific organization and item:

  • SELECT ATP_GROUP_ID, ORGANIZATION_ID, INVENTORY_ITEM_ID, ATP_RULE_ID, ATP_CHECK, DEMAND_CLASS FROM APPS.MTL_GROUP_ITEM_ATPS_VIEW WHERE ORGANIZATION_ID = :org_id AND INVENTORY_ITEM_ID = :item_id;

Join to item master for readable output:

  • SELECT v.ATP_GROUP_ID, v.ORGANIZATION_ID, msi.segment1 item, v.ATP_RULE_ID, v.ATP_CHECK FROM APPS.MTL_GROUP_ITEM_ATPS_VIEW v, APPS.MTL_SYSTEM_ITEMS_B msi WHERE msi.INVENTORY_ITEM_ID = v.INVENTORY_ITEM_ID AND msi.ORGANIZATION_ID = v.ORGANIZATION_ID;

Count rows by ATP group and demand class:

  • SELECT ATP_GROUP_ID, DEMAND_CLASS, COUNT(*) FROM APPS.MTL_GROUP_ITEM_ATPS_VIEW GROUP BY ATP_GROUP_ID, DEMAND_CLASS;

Because the view is a direct projection, queries are subject to the same performance characteristics as MTL_DEMAND_INTERFACE; selective predicates on ORGANIZATION_ID, INVENTORY_ITEM_ID, and ATP_GROUP_ID are advisable on large interface volumes.