Results for “mrp_recommendations_u1”

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

Overview

MRP.MRP_RECOMMENDATIONS is the central planning-output table in Oracle Master Scheduling/MRP and Advanced Supply Chain Planning. It stores the planning engine's suggestions for a given plan, with one row per recommended supply action: purchase orders, purchase requisitions, purchase orders in receiving, discrete jobs, nonstandard jobs, intransit shipments, intransit receipts, planned orders, and suggested repetitive schedules. Each row carries both the current state of an order (old quantity and date) and the planner's recommendation (new quantity and date), enabling the Material Planner Workbench to display, reschedule, firm, and implement suggestions. The table is populated by the planning manager concurrent program and consumed by workbench queries, pegging, capacity, and relief interfaces.

From a Data Vault modeling perspective, the mined foreign-key structure classifies this object as hub-leaning. It is best treated as a durable hub-like entity keyed on TRANSACTION_ID, with dependent satellite attributes capturing the disposable planning state (dates, quantities, firming flags, and implementation status) that is regenerated on each plan run.

Key Information Stored

The documented physical schema for 12.2.2 contains 92 columns. The most significant are:

• TRANSACTION_ID — surrogate primary key (MRP_RECOMMENDATIONS_PK); also the single-column business-key candidate via unique index MRP_RECOMMENDATIONS_U1.
• INVENTORY_ITEM_ID, ORGANIZATION_ID — the planned item and its planning organization.
• COMPILE_DESIGNATOR — identifies the plan (e.g., production, simulation) that generated the recommendation.
• ORDER_TYPE — the supply type: planned order, discrete job, purchase requisition, purchase order, intransit, or repetitive schedule.
• NEW_SCHEDULE_DATE / OLD_SCHEDULE_DATE — recommended versus current date; the difference represents the reschedule recommendation.
• NEW_ORDER_QUANTITY / OLD_ORDER_QUANTITY — recommended versus current quantity; equal in the current version because quantity changes are not recommended.
• NEW_WIP_START_DATE / OLD_WIP_START_DATE — work-in-process start date recommendations.
• DISPOSITION_ID, DISPOSITION_STATUS_TYPE — link to the dispositioned supply document (self-referencing FK).
• FIRM_PLANNED_TYPE, FIRM_QUANTITY, FIRM_DATE — firming status and firming window attributes.
• RESCHEDULED_FLAG, RESCHEDULE_DAYS, SCHEDULE_COMPRESSION_DAYS — reschedule indicators and compressibility measures.
• NEW_PROCESSING_DAYS — workdays for a repetitive schedule, inclusive of both endpoints.
• LAST_UNIT_COMPLETION_DATE, FIRST_UNIT_START_DATE, LAST_UNIT_START_DATE, DAILY_RATE — repetitive schedule span; NEW_ORDER_QUANTITY holds the daily rate.
• IMPLEMENT_* columns — implementation instructions (job name, WIP class, schedule group, project/task, vendor, and status code).
• DISPOSITION_ID → DISPOSITION_ID self-reference and FKs to MRP_SYSTEM_ITEMS, MRP_ITEM_PURCHASE_ORDERS, MRP_ITEM_WIP_ENTITIES, and WIP_LINES.

Common Use Cases and Queries

The dominant use case is the Planner Workbench, which reads rows by plan and item to present reschedule, cancel, and firm recommendations. Planners query by COMPILE_DESIGNATOR, ORGANIZATION_ID, ORDER_TYPE, and DISPOSITION_STATUS_TYPE to isolate actionable exceptions such as late supplies or reschedules.

A typical pattern retrieves recommendations for a specific plan and item:

• SELECT transaction_id, order_type, new_schedule_date, new_order_quantity, reschedule_days FROM mrp.mrp_recommendations WHERE compile_designator = :plan AND inventory_item_id = :item AND organization_id = :org;
• Join to MRP_SYSTEM_ITEMS on INVENTORY_ITEM_ID for item attributes.
• Aggregate by DISPOSITION_STATUS_TYPE to report firm versus unfirm supply.
• Detect slippage via NEW_SCHEDULE_DATE minus OLD_SCHEDULE_DATE and group by program_run to trend plan behavior.

The IMPLEMENT_* columns support programmatic implementation (firming, creating jobs, releasing requisitions), while RELEASE_STATUS and RELEASE_ERRORS track the outcome of those automated actions.

Related Objects

MRP_RECOMMENDATIONS sits at the center of a dense relational web. The most significant dependents and references are:

• MRP_GROSS_REQUIREMENTS.DISPOSITION_ID — links requirements to the supply recommendations that satisfy them.
• MRP_FULL_PEGGING.TRANSACTION_ID — end-to-end pegging from demand to recommended supply.
• MRP_SCHEDULE_DATES.REFERENCE_SCHEDULE_ID — detailed scheduling output for repetitive recommendations.
• MRP_SUGG_REP_SCHEDULES.TRANSACTION_ID — suggested repetitive schedule detail rows.
• MRP_WORKBENCH_QUERY.TRANSACTION_ID — the workbench display layer over this table.
• MRP_RELIEF_INTERFACE.PLANNED_ORDER_ID — relief processing for implemented planned orders.
• CRP_RESOURCE_PLAN.SOURCE_TRANSACTION_ID — capacity planning against recommended supply.
• MRP_SYSTEM_ITEMS, MRP_ITEM_PURCHASE_ORDERS, MRP_ITEM_WIP_ENTITIES, WIP_LINES — inbound FKs resolving item, purchasing, WIP, and production line context via INVENTORY_ITEM_ID, DISPOSITION_ID, and LINE_ID.