Results for “mrp_full_pegging”

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

Overview

MRP_FULL_PEGGING is a table in the MRP schema (product: Master Scheduling/MRP) that stores Full Pegging information generated by the Oracle Materials Requirements Planning and Advanced Supply Chain Planning engines. In Oracle EBS 12.1.1 and 12.2.2, pegging establishes the end-to-end relationship between supply and the demand that consumes it, tracing each supply recommendation back through intermediate nodes to the originating gross requirement or end-item demand. This table is the persistent store for that relationship network and is populated during the MRP/ASCP planning run.

From a dimensional modeling perspective, the heuristic Data Vault classification mined from the foreign-key structure is satellite-leaning. This suggests that MRP_FULL_PEGGING behaves primarily as a descriptive satellite attached to core planning hubs (items, organizations, demand, and supply transactions), rather than as an independent hub or a pure link table. The self-referencing foreign keys to PREV_PEGGING_ID and END_PEGGING_ID reinforce that the table is a chain-oriented structure describing traversal through a pegging graph rather than a normalized business entity on its own.

Key Information Stored

The table contains 28 documented columns. The surrogate primary key is PEGGING_ID, enforced by MRP_FULL_PEGGING_PK and mirrored by the unique index MRP_FULL_PEGGING_U1, which serves as the documented business-key candidate. Key columns include:

• PEGGING_ID — surrogate primary key uniquely identifying each pegging record.
• INVENTORY_ITEM_ID and ORGANIZATION_ID — the item and inventory organization context for the pegging node.
• COMPILE_DESIGNATOR — identifies the specific plan/MRP compilation the record belongs to.
• DEMAND_ID and DEMAND_QUANTITY — link to the gross requirement and the quantity demanded.
• TRANSACTION_ID and SUPPLY_QUANTITY — link to the MRP recommendation (supply) and the quantity supplied.
• ALLOCATED_QUANTITY — the portion of supply allocated to the demand node.
• PREV_PEGGING_ID and END_PEGGING_ID — self-referencing pointers that form the pegging chain and identify its terminal node.
• DEMAND_CLASS, DEMAND_DATE, and SUPPLY_DATE — categorize the demand and provide the respective dates.
• SUPPLY_TYPE — distinguishes the nature of the supplying transaction.
• END_ITEM_USAGE, END_ORIGINATION_TYPE, and END_ITEM_UNIT_NUMBER — describe the originating end-item demand.
• PROJECT_ID and TASK_ID — tie pegging to project/task cost contexts where applicable.
• STATUS, UPDATED, and standard audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN).

Common Use Cases and Queries

The most frequent use is reporting full pegging for an item/organization to trace which supplies satisfy which demands. A typical pattern filters by item, plan, and status and joins to the recommendation and gross-requirement tables:

• Upstream/downstream tracing — walk PREV_PEGGING_ID and END_PEGGING_ID to reconstruct the pegging chain from an end demand to its supply.
• ATP and available-to-promise calculations — MSC_ATP_DETAIL_PEG_TEMP, MRP_ATP_DETAILS_TEMP, and MSC_ATP_PEGGING reference PEGGING_ID to associate order promising with pegging nodes.
• Analytics and reporting — ISC_DBI_FULL_PEGGING_F exposes pegged supply/demand for BI Publisher and Discoverer reports.
• Allocation analysis — aggregate ALLOCATED_QUANTITY versus DEMAND_QUANTITY and SUPPLY_QUANTITY to identify shortfalls or over-supply.

Representative SQL: SELECT p.PEGGING_ID, p.INVENTORY_ITEM_ID, p.DEMAND_ID, p.TRANSACTION_ID, p.DEMAND_QUANTITY, p.ALLOCATED_QUANTITY FROM MRP.MRP_FULL_PEGGING p WHERE p.ORGANIZATION_ID = :org AND p.COMPILE_DESIGNATOR = :plan;

Related Objects

• MRP_RECOMMENDATIONS — joined on TRANSACTION_ID to obtain the supply recommendation details.
• MRP_GROSS_REQUIREMENTS — joined on DEMAND_ID to obtain the originating gross requirement.
• MRP_FULL_PEGGING (self) — joined on PREV_PEGGING_ID and END_PEGGING_ID to traverse the pegging chain.
• MSC_ATP_PEGGING and MSC_PART_PEGGING — reference PEGGING_ID for planning/ATP pegging.
• MSC_ATP_DETAIL_PEG_TEMP and MRP_ATP_DETAILS_TEMP — temporary ATP detail tables keyed by PEGGING_ID.
• ISC_DBI_FULL_PEGGING_F — the reporting/BI fact view built on this table.