Search Results msc_full_pegging




Overview
Explore in AI Chat

Overview

The MSC_FULL_PEGGING table is a core data structure within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module, specifically for releases 12.1.1 and 12.2.2. It serves as the central repository for storing pegging relationships generated during a planning run. Pegging is the fundamental process of linking supply transactions (e.g., purchase orders, work orders, on-hand inventory) to specific demand transactions (e.g., sales orders, forecasts, dependent demands). This table enables planners to perform detailed supply chain traceability, answering critical questions about which supplies are allocated to fulfill which demands, thereby supporting analysis of material shortages, order promising, and the impact of supply changes.

Key Information Stored

The table's primary key uniquely identifies a pegging record through a combination of PLAN_ID, SR_INSTANCE_ID, and PEGGING_ID. Its most critical columns establish the supply-demand link and provide context. The TRANSACTION_ID column references a supply record in MSC_SUPPLIES, while the DEMAND_ID column references a demand record in MSC_DEMANDS. The QUANTITY column stores the pegged amount. Hierarchical pegging for multi-level bills of material is supported through the PREV_PEGGING_ID and END_PEGGING_ID columns, which create self-referential foreign keys to other rows within the same table, allowing navigation from component supply to end-item demand. Additional key columns include INVENTORY_ITEM_ID, ORGANIZATION_ID, PROJECT_ID, and TASK_ID for project-specific planning, linking to MSC_SYSTEM_ITEMS, MSC_PROJECTS, and MSC_PROJECT_TASKS.

Common Use Cases and Queries

Primary use cases involve diagnosing plan results and building custom traceability reports. A common analytical query traces all supply allocated to a specific sales order demand. For example: SELECT s.supply_type, s.new_order_quantity, fpg.quantity FROM msc_full_pegging fpg, msc_supplies s WHERE fpg.plan_id = :p_plan_id AND fpg.demand_id = :p_demand_id AND fpg.transaction_id = s.transaction_id AND fpg.plan_id = s.plan_id; Conversely, to find all demands consuming a specific supply: SELECT d.demand_type, d.using_requirement_quantity, fpg.quantity FROM msc_full_pegging fpg, msc_demands d WHERE fpg.plan_id = :p_plan_id AND fpg.transaction_id = :p_supply_id AND fpg.demand_id = d.demand_id AND fpg.plan_id = d.plan_id; These queries form the basis for custom reports on order fulfillment status, component shortage analysis, and project material allocation.

Related Objects

MSC_FULL_PEGGING has integral relationships with other core planning tables. Its primary foreign keys link to MSC_SUPPLIES and MSC_DEMANDS, the definitive sources for supply and demand transaction details. It references MSC_SYSTEM_ITEMS for item master attributes. For Project Manufacturing scenarios, it links to MSC_PROJECTS and MSC_PROJECT_TASKS. The table also features recursive foreign keys to itself (PREV_PEGGING_ID, END_PEGGING_ID) to manage pegging hierarchies. Data is typically populated by the planning engine (MSC planner) and is accessed by standard Oracle Planning business views and custom analytical solutions for supply chain visibility.