Search Results mrp_workbench_query




Overview
Explore in AI Chat

Overview

The MRP_WORKBENCH_QUERY table is a core data repository within the Oracle E-Business Suite (EBS) Master Scheduling/MRP module. It serves as the primary storage for the filtered recommendations displayed to planners within the MRP Planner Workbench. When a planner applies specific search criteria—such as item, organization, planner, or date range—in the workbench interface, the resulting set of supply and demand recommendations is persisted in this table. Its role is to support the interactive, user-specific analysis of Material Requirements Planning (MRP) and Master Production Schedule (MPS) output, enabling planners to efficiently review, firm, reschedule, and take action on system-generated recommendations.

Key Information Stored

The table stores a unique combination of identifiers and key planning attributes for each recommendation that matches a user's query. Its primary key is a composite of QUERY_ID, TRANSACTION_ID, and LINE_ID, ensuring a unique record for each recommendation line within a specific planner query session. The TRANSACTION_ID column is a critical foreign key that links directly to the detailed recommendation data in the MRP_RECOMMENDATIONS table. Other significant columns include INVENTORY_ITEM_ID and ORGANIZATION_ID (linking to item master data), DESIGNATOR (identifying the specific MRP plan), and FIRST_UNIT_COMPLETION_DATE, which is essential for scheduling analysis. The table also holds LOCATION_ID and LINE_ID, connecting the recommendation to specific inventory locations and WIP production lines, respectively.

Common Use Cases and Queries

The primary use case is supporting the Planner Workbench's query-by-example functionality. A typical operational query retrieves all recommendations for a specific planner's saved query to populate the workbench screen. For reporting and data extraction, analysts often join this table with MRP_RECOMMENDATIONS to pull detailed data for a filtered set of items. A common SQL pattern involves filtering by QUERY_ID and joining to item and recommendation tables:

  • SELECT mwbq.*, mr.* FROM mrp_workbench_query mwbq JOIN mrp_recommendations mr ON mwbq.transaction_id = mr.transaction_id WHERE mwbq.query_id = :p_query_id AND mwbq.organization_id = :p_org_id;

This table is also crucial for auditing and understanding which recommendations were presented to a planner for a particular planning run and set of filters.

Related Objects

MRP_WORKBENCH_QUERY has integral relationships with several key EBS tables. Its most critical dependency is on MRP_RECOMMENDATIONS, which holds the detailed recommendation data (type, quantity, dates). It references MRP_SYSTEM_ITEMS for item and planning attributes specific to a plan (DESIGNATOR). For location and production line context, it links to HR_LOCATIONS_ALL and WIP_LINES. The table itself is likely referenced by various private views and the application logic of the MRP Planner Workbench forms and concurrent programs that generate and manage query results. Its foreign key constraints ensure data integrity with these master and transactional tables.