Results for “disposition_status_type”

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

Overview

MRP_WORKBENCH_QUERY is an Oracle EBS table owned by the MRP schema, residing in the Master Scheduling/MRP product family. It stores recommendations that are generated when a planner selects specific criteria within the MRP Planner WorkBench. In effect, it captures a materialized set of planning recommendations returned from a WorkBench query, holding suggested schedule dates, order dates, quantities, disposition codes, and related firming/rescheduling actions for planned orders and discrete jobs. It supports the interactive planning cycle by preserving the planner's query output so that recommendations can be reviewed, implemented, or rescheduled.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is link. The table primarily resolves relationships between a query definition (QUERY_ID), a planning recommendation (TRANSACTION_ID), a WIP line (LINE_ID), and other referenced business entities, rather than functioning as a pure hub of one business concept or a purely descriptive satellite.

Key Information Stored

The table contains 44 documented columns. The composite primary key, MRP_WORKBENCH_QUERY_PK, is defined over the surrogate combination QUERY_ID, TRANSACTION_ID, LINE_ID, and FIRST_UNIT_COMPLETION_DATE. Among the most operationally significant columns are:

• QUERY_ID – Identifies the WorkBench query context under which recommendations were captured; a leading component of the primary key.
• TRANSACTION_ID – Links each row to a specific planning recommendation in MRP_RECOMMENDATIONS.
• LINE_ID – Associates the recommendation with a WIP line via WIP_LINES.
• FIRST_UNIT_COMPLETION_DATE – The earliest completion date; part of the primary key and used in scheduling logic.
• INVENTORY_ITEM_ID, ORGANIZATION_ID, DESIGNATOR – Item and organization identification, joined to MRP_SYSTEM_ITEMS.
• CURRENT_SCHEDULE_DATE / NEW_SCHEDULE_DATE – The existing and recommended schedule dates for the order.
• CURRENT_ORDER_DATE / NEW_ORDER_DATE – Existing and recommended order dates.
• CURRENT_DOCK_DATE / NEW_DOCK_DATE – Existing and recommended dock dates.
• CURRENT_ORDER_QUANTITY / NEW_ORDER_QUANTITY – Existing and recommended order quantities.
• ORDER_NUMBER, ORDER_TYPE – Identifies the discrete job or purchase order context.
• STATUS_CODE, DISPOSITION, DISPOSITION_STATUS_TYPE – Status and planner disposition of the recommendation.
• FIRM_PLANNED_TYPE, FIRM_QUANTITY, FIRM_DATE, RESCHEDULED_FLAG – Flags and values indicating firming and rescheduling actions.
• IMPLEMENT_QUANTITY, IMPLEMENT_DATE – Quantities and dates selected for implementation.
• LOCATION_ID, EMPLOYEE_ID – Foreign keys to HR_LOCATIONS_ALL and PSB_EMPLOYEES respectively.

Audit columns LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN follow standard EBS conventions.

Common Use Cases and Queries

Planners and developers commonly use this table to review pending recommendations flagged as rescheduled, to report firm orders versus planned orders, and to extract quantities proposed for implementation. Representative query patterns include:

• Retrieving all recommendations for a given WorkBench query: SELECT * FROM MRP.MRP_WORKBENCH_QUERY WHERE QUERY_ID = :p_query_id;
• Identifying rescheduled items: SELECT TRANSACTION_ID, INVENTORY_ITEM_ID, NEW_SCHEDULE_DATE FROM MRP.MRP_WORKBENCH_QUERY WHERE RESCHEDULED_FLAG = 'Y';
• Summarizing implementation quantities and dates by organization: SELECT ORGANIZATION_ID, SUM(IMPLEMENT_QUANTITY) FROM MRP.MRP_WORKBENCH_QUERY GROUP BY ORGANIZATION_ID;
• Joining to MRP_RECOMMENDATIONS on TRANSACTION_ID for detailed planning context.

Related Objects

The foreign key relationships define the most significant dependent and referenced objects:

• MRP_RECOMMENDATIONS – joined via TRANSACTION_ID; the core source of planning recommendations.
• MRP_SYSTEM_ITEMS – joined via INVENTORY_ITEM_ID and ORGANIZATION_ID for item master data.
• WIP_LINES – joined via LINE_ID for discrete job line information.
• HR_LOCATIONS_ALL – joined via LOCATION_ID for location details.
• PSB_EMPLOYEES – joined via EMPLOYEE_ID for planner/employee references.

These relationships make MRP_WORKBENCH_QUERY a central linking table within the Planner WorkBench data model, enabling integrated reporting across recommendations, items, jobs, locations, and planners.