Search Results msc_atp_pegging




Overview
Explore in AI Chat

Overview

MSC_ATP_PEGGING is a table in the MSC schema of Oracle E-Business Suite, belonging to the Advanced Supply Chain Planning (ASCP) product. It stores available-to-promise (ATP) pegging records produced during a planning run, capturing the allocation of supply to demand at the level of individual sales order lines, resources, and departments. Whereas MRP_FULL_PEGGING maintains the general pegging tree linking supplies to demands, MSC_ATP_PEGGING focuses specifically on the ATP context, where the question is not merely which supply satisfies which demand, but how much of a given supply quantity can be promised, when, and against which resource or department capacity.

From a heuristic Data Vault modeling perspective, the metadata classifies this object as standalone. This suggests it is best treated as a satellite-like structure: it carries descriptive and quantitative attributes (quantities, dates, relief types) tied to a business key rather than acting as a pure hub or link. Because foreign key relationships exist to BOM_DEPARTMENTS and MRP_FULL_PEGGING, the table can also be modeled with link references to those parent entities where integration is required.

Key Information Stored

The table contains 42 documented columns in the 12.2.2 release. The most significant columns include:

Common Use Cases and Queries

Typical uses include ATP consumption reporting, supply/demand traceability, and resource-load analysis. A representative query to retrieve ATP pegging for a plan and item follows:

  • SELECT pegging_id, sales_order_line_id, demand_quantity, supply_quantity, allocated_quantity, start_date, end_date FROM msc.msc_atp_pegging WHERE plan_id = :plan_id AND inventory_item_id = :item_id
  • Aggregating consumed quantity by department to analyze resource consumption: SELECT department_id, SUM(daily_resource_hours) FROM msc.msc_atp_pegging WHERE plan_id = :plan_id GROUP BY department_id
  • Tracing a sales order line's promise back to its supply through PEGGING_ID and MRP_FULL_PEGGING joins.

These queries support planners investigating overconsumption, verifying whether promises remain valid, and auditing how ATP was allocated across departments and resources.

Related Objects

The most significant related objects, based on documented foreign keys, include:

  • MRP_FULL_PEGGING — joined via MSC_ATP_PEGGING.PEGGING_ID = MRP_FULL_PEGGING.PEGGING_ID; provides the broader pegging tree.
  • BOM_DEPARTMENTS — joined via MSC_ATP_PEGGING.DEPARTMENT_ID = BOM_DEPARTMENTS.DEPARTMENT_ID; supplies department details.
  • MSC_PLANS — the parent plan referenced by PLAN_ID.
  • MSC_SYSTEM_ITEMS / MTL_SYSTEM_ITEMS_B — item master context for INVENTORY_ITEM_ID and ORGANIZATION_ID.
  • OE_ORDER_LINES_ALL — sales order line detail for SALES_ORDER_LINE_ID.
  • BOM_RESOURCES — resource definitions for RESOURCE_ID.