Results for “msc_full_pegging”

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

Overview

MSC_FULL_PEGGING is a table in the MSC schema (Advanced Supply Chain Planning) within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the pegging relationships that link supplies to the demands they satisfy. Pegging is the mechanism by which Advanced Supply Chain Planning (ASCP) and related planning engines trace how a given supply—a planned order, work order, purchase order, or on-hand quantity—is allocated against specific demand sources. Each row represents one pegging link between a supply transaction and a demand.

From a Data Vault modeling perspective, the metadata's heuristic classification of this object is satellite-leaning. It behaves primarily as a descriptive satellite attached to planning keys, with a significant amount of surrounding structural context (foreign keys to supplies, demands, projects, and items) rather than acting as a pure hub or link. This classification should be treated as a modeling suggestion rather than a prescriptive design.

Key Information Stored

The table contains 50 documented columns. The most significant are:

• PEGGING_ID — Surrogate identifier for the pegging record; part of the primary key MSC_FULL_PEGGING_PK (PLAN_ID, SR_INSTANCE_ID, PEGGING_ID).
• PLAN_ID — Identifies the plan to which the pegging belongs; part of the primary key and most foreign keys.
• SR_INSTANCE_ID — Source instance identifier; part of the primary key and used to segregate source systems.
• DEMAND_ID — Foreign key to MSC_DEMANDS, identifying the demand being satisfied.
• TRANSACTION_ID — Foreign key to MSC_SUPPLIES, identifying the supply transaction.
• DEMAND_QUANTITY / SUPPLY_QUANTITY / ALLOCATED_QUANTITY — Quantities of demand, supply, and the allocated pegged amount.
• DEMAND_DATE / SUPPLY_DATE — Effective dates of the demand and supply.
• INVENTORY_ITEM_ID / ORGANIZATION_ID — Foreign keys to MSC_SYSTEM_ITEMS and project/task structures.
• PREV_PEGGING_ID / END_PEGGING_ID — Self-referencing keys that chain pegging records into a hierarchy.
• PROJECT_ID / TASK_ID — Foreign keys to MSC_PROJECTS and MSC_PROJECT_TASKS for project-referenced pegging.
• SUPPLY_TYPE, DEMAND_CLASS, DISPOSITION_ID — Classification attributes describing the nature of each end of the pegging.

The unique index MSC_FULL_PEGGING_U1 (PLAN_ID, PEGGING_ID, SR_INSTANCE_ID) is the business-key candidate, distinct from the surrogate-style composite primary key.

Common Use Cases and Queries

Typical uses include supply/demand traceability, root-cause analysis of shortages, and pegging reports. A common pattern joins pegging rows to supplies and demands within a plan:

• Trace all demands satisfied by a given supply: filter PLAN_ID and TRANSACTION_ID, then join to MSC_DEMANDS on DEMAND_ID.
• Identify all supplies pegged to a critical demand: filter on DEMAND_ID and join to MSC_SUPPLIES on TRANSACTION_ID.
• Report allocated versus demand quantity to find partially satisfied demands where ALLOCATED_QUANTITY < DEMAND_QUANTITY.
• Follow pegging chains via PREV_PEGGING_ID and END_PEGGING_ID using a hierarchical query.
• Restrict to a specific source instance with SR_INSTANCE_ID for multi-instance environments.

Related Objects

The table is tightly integrated with the MSC planning data model.

• MSC_DEMANDS — joined on PLAN_ID and DEMAND_ID.
• MSC_SUPPLIES — joined on PLAN_ID and TRANSACTION_ID.
• MSC_SYSTEM_ITEMS — joined on INVENTORY_ITEM_ID, PLAN_ID, SR_INSTANCE_ID, and ORGANIZATION_ID.
• MSC_PROJECTS — joined on PLAN_ID, SR_INSTANCE_ID, PROJECT_ID, and ORGANIZATION_ID.
• MSC_PROJECT_TASKS — joined on ORGANIZATION_ID, TASK_ID, PROJECT_ID, SR_INSTANCE_ID, and PLAN_ID.
• MSC_FULL_PEGGING (self) — joined on PLAN_ID with PREV_PEGGING_ID and END_PEGGING_ID to traverse pegging hierarchies.