Search Results atp_group_id




Overview
Explore in AI Chat

Overview

APPS.MTL_GROUP_ITEM_ATPS_VIEW is a reporting and integration view in Oracle E-Business Suite 12.1.1 and 12.2.2 that exposes ATP (Available-to-Promise) grouping and scheduling attributes held on the demand interface. The view presents a focused projection of the demand interface record, surfacing the ATP group identifier, organization, inventory item, ATP rule, ATP check flag, ATP calendar organization, an untyped column, and demand class. Because it is owned by APPS, it is accessible to application users and concurrent programs operating under the APPS schema without requiring direct grants on the underlying interface table.

The view is commonly consulted when operational or technical users search for the column atp_group_id, since that identifier is the pivot used to associate items with grouping rules that govern how ATP is computed across collections of items. It functions as a lightweight, read-oriented layer over the demand interface, allowing ATP-related groupings to be inspected without navigating the full width of the interface record. In integration contexts it supports extraction of item-to-ATP-group mappings for planning, scheduling, and external ATP evaluation processes.

Underlying Base Objects

According to the documented view metadata (ETRM 12.2.2), the view is defined over a single base object: MTL_DEMAND_INTERFACE, referenced as a synonym. The view text is a straightforward SELECT of specific columns from that table, with no joins, aggregation, or filtering:

  • MTL_DEMAND_INTERFACE — the underlying interface table that stores demand records awaiting processing by Oracle planning and scheduling programs. The view is a synonym-level passthrough over this table, restricted to the ATP-related columns.

Because the definition contains no WHERE clause and no DISTINCT, every row of MTL_DEMAND_INTERFACE is visible through the view. The view therefore inherits row-level behavior directly from the interface table, including any staging or error rows present during demand interface processing cycles.

Key Columns

The view projects the following columns, each derived from the corresponding column of MTL_DEMAND_INTERFACE:

  • ATP_GROUP_ID — the identifier that links the interface record to an ATP grouping definition; the central column of interest for group-level ATP analysis.
  • ORGANIZATION_ID — the inventory organization to which the demand record belongs.
  • INVENTORY_ITEM_ID — the item for which demand and ATP information is staged.
  • ATP_RULE_ID — the ATP rule applied to the record, governing how available quantities are calculated.
  • ATP_CHECK — a flag indicating the ATP check behavior or state for the record.
  • ATP_CALENDAR_ORGANIZATION_ID — the organization whose ATP calendar supplies the working and non-working day pattern for the check.
  • N_COLUMN1 — a generic numeric column reserved for interface flexibility and contextual use.
  • DEMAND_CLASS — the demand class used to segregate demand for ATP and planning purposes.

Common Use Cases and Queries

The view is typically used to verify item-to-group assignments, audit ATP setup staged in the demand interface, and export mappings for external scheduling engines. A representative query retrieves all items associated with a specific ATP group and organization:

  • SELECT atp_group_id, organization_id, inventory_item_id, atp_rule_id, atp_check, atp_calendar_organization_id, demand_class FROM apps.mtl_group_item_atps_view WHERE atp_group_id = :p_group_id AND organization_id = :p_org_id;
  • SELECT atp_group_id, COUNT(*) FROM apps.mtl_group_item_atps_view GROUP BY atp_group_id; — to enumerate groups and their staged item counts.
  • SELECT organization_id, inventory_item_id, demand_class FROM apps.mtl_group_item_atps_view WHERE atp_rule_id = :p_rule_id; — to review items sharing a given ATP rule.

Because the view lacks filtering, queries should constrain ORGANIZATION_ID and INVENTORY_ITEM_ID where possible to avoid scanning the entire interface table. This is especially important during active demand interface processing, when the volume of staged rows may be high.