Results for “action_no”

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

Overview

MR_PEGG_TBL is a table owned by the GMP schema within the Oracle E-Business Suite Process Manufacturing Process Planning module. Its documented purpose is pegging: it records the linkage between demands and the shortage warnings generated during a planning run, allowing planners to trace which demand elements caused a specific shortage and, conversely, which supply or action resolves a given demand. In the flow of process planning, MR_PEGG_TBL functions as the associative detail behind planning actions, capturing the individual pegged demand records that belong to an action produced for a given MRP plan.

From a modeling perspective, the ETRM heuristic Data Vault classification for this object is satellite-leaning, derived from its foreign key structure. This suggests that MR_PEGG_TBL may be most naturally modeled as a satellite attached to a parent action record, carrying descriptive pegging detail keyed to that parent, rather than as an independent hub or a pure link between multiple business entities. The classification is a heuristic suggestion and should be validated against actual query patterns and cardinality before being adopted in a warehouse design.

Key Information Stored

The documented physical schema contains twelve columns, of which the following carry the substantive business content:

• MRP_ID — identifies the planning action record to which the pegging rows belong. It is both part of the composite primary key and the column participating in the foreign key to MR_ACTN_TBL.
• ACTION_NO — the action number within the plan. Together with MRP_ID it references the parent action record and forms the second component of the primary key.
• LINE_NO — the line sequence within the action, providing the third component of the primary key and uniquely identifying each pegged record under its action.
• LAST_UPDATED_BY, CREATED_BY — standard audit columns identifying the user who last modified and the user who created the record.
• LAST_UPDATE_DATE, CREATION_DATE — standard audit timestamps for the most recent modification and original insertion.
• LAST_UPDATE_LOGIN — the login context associated with the last update.
• REQUEST_ID — the concurrent request that populated the row, useful for tracing the planning run that produced the pegging data.
• PROGRAM_APPLICATION_ID, PROGRAM_ID — identify the concurrent program and application that generated the record.
• PROGRAM_UPDATE_DATE — the date the generating program last touched the row.

The unique index MR_PEGG_TBL_PK on (MRP_ID, ACTION_NO, LINE_NO) is the documented business-key candidate for uniqueness, while the surrogate-level identity of a row is realized through that same composite key rather than a single synthetic column.

Common Use Cases and Queries

Typical uses center on shortage analysis and demand traceability. A planner investigating why an action was raised will join pegging rows back to the action table:

• Listing all pegged lines for a given plan action: SELECT * FROM MR_PEGG_TBL WHERE MRP_ID = :p_mrp_id AND ACTION_NO = :p_action_no ORDER BY LINE_NO;
• Reconciling pegging records to actions: SELECT a.*, p.LINE_NO FROM MR_ACTN_TBL a JOIN MR_PEGG_TBL p ON p.MRP_ID = a.MRP_ID AND p.ACTION_NO = a.ACTION_NO;
• Tracing the concurrent run that produced a set of pegging rows by filtering on REQUEST_ID or PROGRAM_ID for audit and re-run investigation.
• Auditing stale or recently modified pegging entries via LAST_UPDATE_DATE for data-quality checks.

Related Objects

The most significant referenced object is the parent action table, joined on the documented key columns:

• MR_ACTN_TBL — the parent planning action table. The foreign key MR_PEGG_TBL.MRP_ID / ACTION_NO references MR_ACTN_TBL on the same columns, making this the primary join used in every pegging query.
• MR_PEGG_TBL_PK — the unique index enforcing uniqueness of (MRP_ID, ACTION_NO, LINE_NO).
• Other GMP planning tables in the MR_* family (such as plan, demand, and shortage structures) are commonly joined through MRP_ID to provide planning context, though the documented metadata explicitly names only the MR_ACTN_TBL relationship.