Search Results mrp_load_selections_pk
Overview
The MRP_LOAD_SELECTIONS table is a core data structure within the Master Scheduling/MRP module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It functions as a repository for user-defined selection lists, which are critical for filtering and controlling the scope of data processed during MRP planning runs. These lists allow planners to define specific subsets of items, sourcing rules, or other entities to be included or excluded from a material requirements planning or master scheduling calculation. The table's primary role is to store the master definition of these selection criteria, which are then referenced by planning parameters to ensure the MRP engine processes only the intended data set, thereby optimizing performance and planning relevance.
Key Information Stored
The table's structure is defined by a composite primary key that uniquely identifies each selection list within the system. The key columns are SELECTION_LIST_NAME, ORGANIZATION_ID, and SELECTION_LIST_TYPE. The SELECTION_LIST_NAME holds the user-assigned identifier for the list. The ORGANIZATION_ID ties the list to a specific inventory organization, enforcing data partitioning by business unit. The SELECTION_LIST_TYPE column categorizes the list based on its intended use, such as for items, sourcing assignments, or planners. While the provided metadata does not detail all columns, the table logically stores the association between the list header and the specific member records (e.g., item numbers) that constitute the list's contents, which are typically stored in a related child table.
Common Use Cases and Queries
The primary use case is the creation and maintenance of selection lists via the Oracle EBS user interface, which are subsequently chosen in the "Selection Lists" region of the MRP planning parameters form. From a reporting and data validation perspective, common queries involve identifying all selection lists available for a given organization or verifying the lists referenced by active planning parameters. A typical SQL pattern to audit existing lists would be:
- SELECT selection_list_name, selection_list_type, organization_id FROM mrp_load_selections WHERE organization_id = :org_id ORDER BY 1;
Another critical operational query joins MRP_LOAD_SELECTIONS to MRP_LOAD_PARAMETERS to find all planning parameter sets utilizing a specific list, ensuring changes to a list are assessed for downstream impact before execution.
Related Objects
MRP_LOAD_SELECTIONS has a direct and documented foreign key relationship with the MRP_LOAD_PARAMETERS table, which is central to configuring and launching an MRP plan. The relationship is defined as follows:
- Foreign Key Table: MRP_LOAD_PARAMETERS
- Referencing Columns: MRP_LOAD_PARAMETERS.SELECTION_LIST_NAME, MRP_LOAD_PARAMETERS.ORGANIZATION_ID, MRP_LOAD_PARAMETERS.SELECTION_LIST_TYPE
- Referenced Key in MRP_LOAD_SELECTIONS: Primary Key MRP_LOAD_SELECTIONS_PK (SELECTION_LIST_NAME, ORGANIZATION_ID, SELECTION_LIST_TYPE)
This relationship ensures referential integrity, meaning a planning parameter set can only reference a valid, pre-defined selection list. The table is also the likely parent to detail tables (not specified in the provided metadata) that store the individual line items belonging to each selection list.
-
Table: MRP_LOAD_SELECTIONS
12.2.2
owner:MRP, object_type:TABLE, fnd_design_data:MRP.MRP_LOAD_SELECTIONS, object_name:MRP_LOAD_SELECTIONS, status:VALID, product: MRP - Master Scheduling/MRP , description: Selection Lists , implementation_dba_data: MRP.MRP_LOAD_SELECTIONS ,
-
Table: MRP_LOAD_SELECTIONS
12.1.1
owner:MRP, object_type:TABLE, fnd_design_data:MRP.MRP_LOAD_SELECTIONS, object_name:MRP_LOAD_SELECTIONS, status:VALID, product: MRP - Master Scheduling/MRP , description: Selection Lists , implementation_dba_data: MRP.MRP_LOAD_SELECTIONS ,