Search Results mr_size_tbl




Overview
Explore in AI Chat

Overview

The MR_SIZE_TBL table is a core data object within the Process Manufacturing Process Planning (GMP) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. Its primary function is to manage and optimize memory allocation for Material Requirements Planning (MRP) runs. The table stores sizing thresholds that the MRP engine uses to pre-allocate system memory dynamically based on the expected volume of data for a specific production schedule. This mechanism is critical for ensuring MRP runs perform efficiently by preventing memory overallocation for small runs and underallocation for large, complex runs. The values within this table are not static; they are automatically updated by the application whenever an MRP run processes a number of rows exceeding the currently stored maximum, thereby allowing the system to adapt to evolving data volumes over time.

Key Information Stored

While the provided metadata does not list all columns, the documented primary and foreign keys reveal the essential structure. The central column is SCHEDULE_ID, which serves as the primary key (MR_SIZE_TBL_PK) and uniquely identifies a production schedule. This column is the foreign key linking to the PS_SCHD_HDR table, which contains the schedule header information. The table's primary purpose, as described, is to store the maximum row counts ("max number of rows") for various entities or stages within an MRP run for a given schedule. These numeric values dictate the memory footprint allocated. The exact nature of these row count columns is product-specific but fundamentally relates to key MRP entities like planned orders, material requirements, or resource loads.

Common Use Cases and Queries

The primary use case is the internal optimization of MRP engine performance. Database administrators or functional consultants might query this table to analyze historical sizing trends or troubleshoot performance issues related to MRP runs. A common query would join the table to the schedule header to understand which schedules have the largest memory footprints. For example:

  • Identifying Schedules with High Allocation: SELECT s.schedule_name, m.* FROM gmp.mr_size_tbl m, gmp.ps_schd_hdr s WHERE m.schedule_id = s.schedule_id ORDER BY [SIZING_COLUMN] DESC;
  • Monitoring Adaptive Updates: Administrators may track changes to the max row values over time to confirm the self-tuning mechanism is functioning after particularly large MRP runs.

Direct manipulation of this table is atypical, as updates are managed by the application. Reporting use cases are generally limited to technical performance analysis rather than functional business reporting.

Related Objects

The MR_SIZE_TBL has a direct and documented relationship with one other key table in the GMP schema, forming a critical link between MRP runtime configuration and production scheduling data.

  • PS_SCHD_HDR (Table): This is the primary foreign key relationship. The MR_SIZE_TBL.SCHEDULE_ID column references the PS_SCHD_HDR table. This join allows the MRP sizing data to be contextualized with specific production schedule details, such as the schedule name, dates, and status. Any analysis of MR_SIZE_TBL data typically requires this join to make the information meaningful.