Search Results offset_supply_id

Overview

MSC.MSC_ATP_PEGGING is a planning table within the Oracle Advanced Supply Chain Planning (ASCP) / MSC schema that stores available-to-promise (ATP) pegging and relief information. It records how supply, demand, resources, and sales order lines are linked together during the ATP and planning relief process, capturing the quantitative "relief" applied to supply when demand is consumed or when resources are relieved across a planning horizon. Because it resides in the MSC schema, it is populated and consumed primarily by the ASCP planning engine rather than by online transactional forms.

Under the heuristic Data Vault classification derived from the FK structure, this object is modeled as a standalone table rather than as a hub, link, or satellite. This reflects the fact that its relationships are defined through business columns (such as PEGGING_ID pointing to MRP_FULL_PEGGING) rather than through a fully normalized integration-layer key structure. Analysts building a Data Vault around MSC should treat MSC_ATP_PEGGING as a source-oriented staging/standalone entity and consider decomposing it into hubs and links based on the natural keys described below.

Key Information Stored

The table contains 42 documented columns. The most operationally significant are organized around the pegging and relief concepts:

• PLAN_ID – identifies the plan under which the pegging record was generated; a leading column in every nonunique index and a primary business-key candidate along with the other key attributes.
• RELIEF_TYPE – numeric discriminator describing the type of relief application (for example, supply relief or resource relief). This is the column referenced by the search term and is a leading column in indexes MSC_ATP_PEGGING_N1 through N4.
• INVENTORY_ITEM_ID, ORGANIZATION_ID, REFERENCE_ITEM_ID, ORIGINAL_ITEM_ID – item and organization context for the pegged record, including original versus referenced item identifiers.
• DEMAND_ID, SUPPLY_ID, RESOURCE_ID, OFFSET_SUPPLY_ID – foreign references to the demand, supply, resource, and offset supply involved in the pegging.
• SALES_ORDER_LINE_ID, DEMAND_SOURCE_TYPE, CUSTOMER_ID, CUSTOMER_SITE_ID – sales order context and demand classification.
• DEMAND_QUANTITY, SUPPLY_QUANTITY, ALLOCATED_QUANTITY, CONSUMED_QTY, OVERCONSUMPTION_QTY, RELIEF_QUANTITY, DAILY_RELIEF_QTY – the quantitative measures describing demand, supply, allocation, consumption, and the relief amounts applied.
• PEGGING_ID, PREV_PEGGING_ID, END_PEGGING_ID, END_DEMAND_ID – the chain indicators that link records in the pegging hierarchy.
• START_DATE, END_DATE, TRANSACTION_DATE, ORIGINAL_DATE – temporal attributes defining the validity and transaction window of the record.
• OFFSET_TYPE – comments indicate this holds the offset type of a particular record.

No surrogate single-column primary key is documented; the table relies on composite business keys represented by the four nonunique indexes (MSC_ATP_PEGGING_N1–N4), each combining PLAN_ID and RELIEF_TYPE with context columns such as SR_INSTANCE_ID, SALES_ORDER_LINE_ID, INVENTORY_ITEM_ID, SUPPLY_ID, and OFFSET_SUPPLY_ID.

Common Use Cases and Queries

Typical uses include ATP pegging analysis, supply/demand reconciliation, relief reporting, and resource consumption review. Analysts generally filter by PLAN_ID and RELIEF_TYPE first, since those are the leading index columns.

• Relief summary by plan and relief type:
  SELECT RELIEF_TYPE, SUM(RELIEF_QUANTITY), SUM(DAILY_RELIEF_QTY) FROM MSC.MSC_ATP_PEGGING WHERE PLAN_ID = :plan_id GROUP BY RELIEF_TYPE;
• Sales order pegging detail:
  SELECT SALES_ORDER_LINE_ID, DEMAND_ID, SUPPLY_ID, DEMAND_QUANTITY, SUPPLY_QUANTITY FROM MSC.MSC_ATP_PEGGING WHERE PLAN_ID = :plan_id AND SALES_ORDER_LINE_ID = :line_id;
• Consumption and overconsumption reporting:
  SELECT INVENTORY_ITEM_ID, CONSUMED_QTY, OVERCONSUMPTION_QTY FROM MSC.MSC_ATP_PEGGING WHERE PLAN_ID = :plan_id AND RELIEF_TYPE = :relief_type;

Because the indexes include OFFSET_SUPPLY_ID (MSC_ATP_PEGGING_N4), queries exploring offset supply relationships should also constrain PLAN_ID and RELIEF_TYPE for optimal access paths.

Related Objects

Documented foreign key relationships identify the following referenced objects:

• BOM.MRP_FULL_PEGGING – referenced through PEGGING_ID; the principal pegging hierarchy source.
• BOM.BOM_DEPARTMENTS – referenced through DEPARTMENT_ID, providing department context for resource-related pegging.

In addition to these documented FKs, MSC_ATP_PEGGING is functionally joined through its key columns to related MSC planning objects such as MRP plan definitions (referenced via PLAN_ID), MSC supply and demand tables (via SUPPLY_ID and DEMAND_ID), and MSC resource tables (via RESOURCE_ID). Oracle ASCP reports and the ATP pegging engine consume this table during plan generation and relief processing, and custom extracts frequently join it back to MRP_FULL_PEGGING to reconstruct the full pegging chain.