Results for “msc_atp_peg_temp”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MSC_ATP_PEG_TEMP is a table in the MSC schema (Advanced Supply Chain Planning) within Oracle E-Business Suite 12.1.1 and 12.2.2. It serves as a temporary working table used by the available-to-promise (ATP) and pegging engines to stage supply-demand allocation results, resource consumption, and pegging relationships during a planning run. The table materialises the transient, in-flight calculation state that links demands to supplies and derives pegging chains for end demands, feeding downstream planning, scheduling, and order promising processes. It is a staging artifact rather than a persistent master table; its contents are typically rebuilt or purged with each planning run.

The heuristic Data Vault classification for this object is standalone, which suggests it is best modelled as a satellite-like structure keyed by a planning-scoped business key, without strong hub-and-link dependencies. Because it carries substantial descriptive and quantitative columns (quantities, dates, resource hours), a satellite classification is the closest fit; the absence of incoming FK relationships reinforces its role as a lean working set rather than a shared reference entity.

Key Information Stored

The table contains 43 documented columns. The most operationally significant are:

• PLAN_ID — the plan for which ATP/pegging results are computed; effectively part of the composite business key.
• SR_INSTANCE_ID — source instance identifier, supporting multi-instance or multi-org sourcing.
• INVENTORY_ITEM_ID / ORGANIZATION_ID — the item and organization context for each demand or supply record.
• DEMAND_ID, DEMAND_QUANTITY, CONSUMED_QTY, OVERCONSUMPTION_QTY — demand identity and allocation quantities.
• SUPPLY_ID, SUPPLY_QUANTITY, ALLOCATED_QUANTITY — the supply side of the ATP allocation.
• PEGGING_ID, PREV_PEGGING_ID, END_PEGGING_ID — the pegging chain that ties intermediate nodes to the originating end demand.
• END_DEMAND_ID, CUSTOMER_ID, CUSTOMER_SITE_ID — the ultimate customer demand the allocation satisfies.
• RESOURCE_ID, DEPARTMENT_ID, RESOURCE_HOURS, DAILY_RESOURCE_HOURS, RELIEF_QUANTITY — capacity and relief information for constrained resources.
• START_DATE, END_DATE, ATF_DATE, TRANSACTION_DATE — scheduling and ATP feasibility dates.
• Standard audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE.

Documented foreign keys include PEGGING_ID → MRP_FULL_PEGGING, DISPOSITION_ID → AHL_PRD_DISPOSITIONS_B, and DEPARTMENT_ID → BOM_DEPARTMENTS. No single-column surrogate primary key is documented; the effective business key is the composite of PLAN_ID, SR_INSTANCE_ID, DEMAND_ID, and SUPPLY_ID.

Common Use Cases and Queries

Typical uses include diagnosing why a specific sales order was promised a given date, tracing pegging chains for a plan, and analysing resource consumption or overconsumption.

• Identify the full pegging chain for a demand:

SELECT DEMAND_ID, SUPPLY_ID, PEGGING_ID, END_DEMAND_ID
  FROM MSC.MSC_ATP_PEG_TEMP
 WHERE PLAN_ID = :plan_id AND DEMAND_ID = :demand_id;

• Report resource load and relief by department:

SELECT RESOURCE_ID, DEPARTMENT_ID, SUM(RESOURCE_HOURS) HRS
  FROM MSC.MSC_ATP_PEG_TEMP
 WHERE PLAN_ID = :plan_id
 GROUP BY RESOURCE_ID, DEPARTMENT_ID;

These queries support planners investigating ATP failures, allocation shortages, and end-demand fulfilment timelines.

Related Objects

• MRP_FULL_PEGGING — joined via PEGGING_ID to resolve full pegging node details.
• AHL_PRD_DISPOSITIONS_B — joined via DISPOSITION_ID for disposition codes.
• BOM_DEPARTMENTS — joined via DEPARTMENT_ID to resolve department names.
• MSC_ATP_PEG — the persistent companion holding finalised ATP/pegging output.
• OE_ORDER_LINES_ALL / OE_ORDER_HEADERS_ALL — referenced via SALES_ORDER_LINE_ID and CUSTOMER_ID for demand context.
• MTL_SYSTEM_ITEMS_B — resolved through INVENTORY_ITEM_ID and ORIGINAL_ITEM_ID.