Results for “msc_part_pegging”

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

Overview

MSC_PART_PEGGING is a planning table owned by the MSC schema within Oracle Advanced Supply Chain Planning (ASCP). It stores partial pegging relationships that link demand to supply across a planning horizon, enabling planners to trace which supplies satisfy which demands. In Oracle EBS 12.1.1 and 12.2.2, this table is populated during the planning engine run and serves as an intermediate pegging structure that rolls up into the full pegging hierarchy represented by MRP_FULL_PEGGING.

From a Data Vault modeling perspective, the heuristic classification of this table is standalone. It contains no documented child tables referencing it via foreign keys, and its single documented foreign key points outward to MRP_FULL_PEGGING through PEGGING_ID. This suggests the table functions less as a traditional hub or link and more as a transactional detail store attached to the full pegging structure. The classification should be treated as a modeling suggestion rather than a definitive architectural designation.

Key Information Stored

The table contains 49 documented columns. The most significant columns and their roles are:

• PEGGING_ID — The primary key and foreign key to MRP_FULL_PEGGING, uniquely identifying each partial pegging record.
• DEMAND_QUANTITY / SUPPLY_QUANTITY / ALLOCATED_QUANTITY — The core business measures describing how much of a supply is consumed by a demand.
• DEMAND_DATE / SUPPLY_DATE — The dates on which demand and supply occur, used for time-phased pegging analysis.
• DEMAND_ID / SUPPLY_TYPE / DEMAND_CLASS — Identifiers and classifiers describing the nature and origin of the demand and supply records.
• INVENTORY_ITEM_ID / ORGANIZATION_ID / PLAN_ID — Contextual keys tying the pegging record to an item, organization, and specific plan run.
• PREV_PEGGING_ID / END_PEGGING_ID — Pointers establishing the chain of pegging through intermediate levels up to the end pegging node.
• TRANSACTION_ID / DISPOSITION_ID / PROJECT_ID / TASK_ID — Additional business references linking pegging to transactions, dispositions, and project/task structures.
• SR_INSTANCE_ID — Identifies the source instance for multi-instance or global planning scenarios.
• LAST_UPDATE_DATE / CREATION_DATE / CREATED_BY / LAST_UPDATED_BY — Standard audit columns maintained by the planning engine.

The surrogate primary key is PEGGING_ID. Business-key candidates are not documented as unique indexes in the provided metadata, but combinations of PLAN_ID, INVENTORY_ITEM_ID, ORGANIZATION_ID, DEMAND_ID, and PEGGING_ID typically serve as the logical business identifier in planning contexts.

Common Use Cases and Queries

Planners and developers query MSC_PART_PEGGING to answer questions about supply-demand matching, such as identifying which supplies satisfy a given demand or tracing the origin of a supply allocation. A typical query pattern joins the table to MRP_FULL_PEGGING on PEGGING_ID to retrieve the complete pegging chain:

• Reporting on supply consumed per demand for a specific plan: SELECT DEMAND_ID, SUPPLY_TYPE, ALLOCATED_QUANTITY WHERE PLAN_ID = :plan.
• Drill-down from a full pegging node: SELECT p.* FROM MSC_PART_PEGGING p, MRP_FULL_PEGGING f WHERE p.PEGGING_ID = f.PEGGING_ID AND f.PEGGING_ID = :id.
• Analyzing time-phased pegging by comparing DEMAND_DATE and SUPPLY_DATE to detect late or early supply.
• Auditing project-specific pegging using PROJECT_ID and TASK_ID for project-driven supply chains.

Related Objects

The most significant related objects, based on documented foreign key relationships and typical ASCP usage, are:

• MRP_FULL_PEGGING — Referenced via PEGGING_ID; the parent table representing the full pegging hierarchy.
• MSC_PLANS — Supplies the PLAN_ID context for plan-specific pegging records.
• MTL_SYSTEM_ITEMS_B — Joined via INVENTORY_ITEM_ID for item descriptions.
• MTL_PARAMETERS / ORG_ORGANIZATION_DEFINITIONS — Joined via ORGANIZATION_ID for organization detail.
• MSC_SUPPLY_DEMAND — Provides the underlying supply and demand records that pegging references.
• MRP_GROSS_REQUIREMENTS / MRP_RECOMMENDED_PLAN_ORDERS — Correlated supply and demand source objects used in pegging traceability.