Search Results mrp_recommendations

Overview

The MRP_RECOMMENDATIONS table is a core transactional repository within the Oracle E-Business Suite (EBS) Master Scheduling/MRP module. It serves as the central data store for all output recommendations generated by a Material Requirements Planning (MRP) or Master Production Schedule (MPS) plan run. When a plan is compiled, this table is populated with detailed, time-phased suggestions for managing supply and demand, including planned orders, reschedule in/out actions, and cancellation recommendations. Its role is critical for planners who use the MRP Workbench and related processes to review, firm, and implement these system-generated suggestions to maintain an optimal supply chain.

Key Information Stored

The table's primary key is the TRANSACTION_ID, uniquely identifying each recommendation record. Key columns define the item, organization, and plan context (INVENTORY_ITEM_ID, ORGANIZATION_ID, COMPILE_DESIGNATOR). The RECOMMENDATION_TYPE column categorizes the action, such as 'CREATE', 'RESCHEDULE IN', or 'CANCEL'. Dates like NEW_SUGGESTED_DATE and OLD_SUGGESTED_DATE track schedule changes, while QUANTITY and ORDER_NUMBER detail the recommendation specifics. The DISPOSITION_ID is a crucial foreign key linking the recommendation to its source supply (e.g., a purchase order or work order) in related disposition tables. This structure provides a complete audit trail of the plan's logic.

Common Use Cases and Queries

The primary use case is querying recommendations for planner review and action within the MRP Workbench. Typical queries filter by plan, organization, item, date range, and recommendation type. For example, to extract all planned order creation recommendations for a specific plan, a query would join to MRP_SYSTEM_ITEMS for item details:

• SELECT ms1.concatenated_segments ITEM, mr.RECOMMENDATION_TYPE, mr.NEW_SUGGESTED_DATE, mr.QUANTITY FROM MRP_RECOMMENDATIONS mr, MRP_SYSTEM_ITEMS ms1 WHERE mr.ORGANIZATION_ID = ms1.ORGANIZATION_ID AND mr.INVENTORY_ITEM_ID = ms1.INVENTORY_ITEM_ID AND mr.COMPILE_DESIGNATOR = '<PLAN_NAME>' AND mr.RECOMMENDATION_TYPE = 'CREATE' ORDER BY ms1.concatenated_segments, mr.NEW_SUGGESTED_DATE;

Reporting often focuses on summarizing recommendations by type or analyzing suggested reschedule actions to assess plan stability. Data from this table is also the source for pegging and relief transactions when recommendations are implemented.

Related Objects

MRP_RECOMMENDATIONS has extensive foreign key relationships, underscoring its central role. Key documented relationships include:

• MRP_SYSTEM_ITEMS: Joined via INVENTORY_ITEM_ID, ORGANIZATION_ID, and COMPILE_DESIGNATOR for plan-specific item attributes.
• MRP_ITEM_PURCHASE_ORDERS & MRP_ITEM_WIP_ENTITIES: Joined via DISPOSITION_ID to link recommendations to specific purchase or work order supplies.
• MRP_FULL_PEGGING & MRP_GROSS_REQUIREMENTS: Joined via TRANSACTION_ID and DISPOSITION_ID, respectively, for demand-supply traceability.
• MRP_RELIEF_INTERFACE: Joined via PLANNED_ORDER_ID to track the relief of planned orders.
• MRP_WORKBENCH_QUERY & MRP_SUGG_REP_SCHEDULES: Joined via TRANSACTION_ID to support workbench filtering and suggested repetitive schedules.
• WIP_LINES: Joined via LINE_ID for production line details.
• CRP_RESOURCE_PLAN & FLM_SEQ_TASK_DEMANDS: Joined via SOURCE_TRANSACTION_ID and DEMAND_ID, respectively, linking to Capacity Planning and Flow Manufacturing.