Search Results msc_atp_detail_peg_temp




Overview
Explore in AI Chat

Overview

MSC_ATP_DETAIL_PEG_TEMP is a temporary staging table in the MSC schema, owned by the Advanced Supply Chain Planning (ASCP) module of Oracle E-Business Suite. It stores the detailed pegging relationships generated during ATP (Available-to-Promise) and supply chain planning calculations, capturing how demand is allocated to supply at the detail level. The table is populated transiently during a planning engine run and normally truncated or refreshed on subsequent runs; it should be treated as operational scratch data rather than persistent master data.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign-key structure is standalone. Based on the documented FK to MRP_FULL_PEGGING, the table most closely resembles a satellite or link-like structure that hangs off the full pegging entity, recording descriptive and quantitative measures for each pegging step (demand dates, supply dates, allocated quantities). Because the metadata does not document a surrogate primary key or unique constraint, the classification should be regarded as a modeling suggestion rather than a definitive label.

Key Information Stored

The table exposes 41 documented columns. The most significant include:

No surrogate primary key or unique index is documented in the ETRM metadata; the combination of PEGGING_ID with the supply/demand identifiers functions as a de facto business key for tracing a single pegging step.

Common Use Cases and Queries

Typical scenarios include diagnosing why a demand is pegged to a specific supply, examining ATP consumption and overconsumption, and validating pegging chains across a plan run.

  • Trace a pegging chain: SELECT demand_id, supply_id, allocated_quantity, prev_pegging_id FROM msc_atp_detail_peg_temp WHERE pegging_id = :p_id.
  • Find overconsumption: SELECT original_demand_id, forecast_qty, consumed_qty, overconsumption_qty FROM msc_atp_detail_peg_temp WHERE overconsumption_qty > 0 AND plan_id = :plan.
  • Total supply relief by item: SELECT inventory_item_id, SUM(tot_relief_qty) FROM msc_atp_detail_peg_temp WHERE plan_id = :plan GROUP BY inventory_item_id.
  • Sales-order pegging detail: SELECT sales_order_line_id, sales_order_qty, demand_date, supply_type FROM msc_atp_detail_peg_temp WHERE sales_order_line_id IS NOT NULL.

Related Objects

  • MRP_FULL_PEGGING — referenced via PEGGING_ID; the master full-pegging table holding each pegging header.
  • MRP_SYSTEM_ITEMS / MTL_SYSTEM_ITEMS_B — joined on INVENTORY_ITEM_ID for item descriptions.
  • MRP_PLANS — joined on PLAN_ID for plan context.
  • OE_ORDER_LINES_ALL — joined on SALES_ORDER_LINE_ID for sales-order detail.
  • MRP_FORECAST_DATES / MSC_FORECAST_*** — forecast consumption cross-reference on ORIGINAL_DEMAND_ID / DEMAND_ID.
  • ASCP planning engine programs that INSERT and DELETE rows in this staging table during the peg generation phase.

Because the table is a temporary planning artifact, its contents should not be referenced outside the plan run window.