Search Results folder_object

Overview

MRP_CRITERIA is a seeded configuration table owned by the MRP schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Master Scheduling/MRP product family and stores the criteria definitions that drive the Oracle Planner Workbench, the primary graphical interface planners use to review, filter, and act on planned orders, suggestions, and exceptions generated by the MRP and MPS planning engines. Each row defines a selectable criterion — such as a field prompt, list of values, or SQL-driven query — that the Workbench presents to users when they build or personalize folders and horizontal displays.

Because the table is seeded, its contents are delivered by Oracle during installation rather than maintained by end users, though customers can extend it. From a Data Vault modeling perspective, the metadata classifies MRP_CRITERIA as standalone, a heuristic suggesting it behaves as a reference or hub-like object with no upstream foreign-key dependencies. It can therefore be modeled as an independent reference hub keyed on its natural business key.

Key Information Stored

The primary key, MRP_CRITERIA_PK, is a composite surrogate key defined over FOLDER_OBJECT and FIELD_NAME. A secondary unique index, MRP_CRITERIA_U1, extends this to (FOLDER_OBJECT, FIELD_NAME, ZD_EDITION_NAME), which is the strongest documented business-key candidate and supports edition-aware lookups in 12.2.2.

• FOLDER_OBJECT — the Planner Workbench folder or object to which the criterion applies.
• FIELD_NAME — the logical field identifier presented within that folder.
• FIELD_TYPE — the data type governing how the field is rendered and validated.
• FIELD_PROMPT — the user-facing label displayed in the Workbench.
• LOV_NAME / LOV_TYPE — the list of values definition and its type, used for pick-list selection.
• SQL_STATEMENT — the query that populates or filters the criterion's values.
• APP_SHORT_NAME — the owning application short name.
• FLEX_NUM / FLEX_CODE — key flexfield context used when the criterion maps to a flexfield segment.
• DATA_SET — groups criteria into logical reporting or display sets.
• LONG_LIST — flag indicating whether an extended value list is required.
• ZD_EDITION_NAME — the edition identifier supporting Online Patching in 12.2.2.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

Typical usage centers on diagnosing or extending Planner Workbench behavior. Planners and implementers query the table to determine which criteria exist for a given folder, to inspect the SQL behind a list of values, or to trace why a field prompt or selection set does not appear.

A representative query retrieves all criteria for a folder:

SELECT FIELD_NAME, FIELD_PROMPT, FIELD_TYPE, LOV_NAME FROM MRP.MRP_CRITERIA WHERE FOLDER_OBJECT = :p_folder ORDER BY FIELD_NAME;

To locate criteria backed by custom SQL, filter on a non-null SQL_STATEMENT. For a specific business key, join on FOLDER_OBJECT and FIELD_NAME. Reporting use cases include auditing seeded versus customer-added rows using CREATED_BY, and verifying edition-specific definitions via ZD_EDITION_NAME after an online patching cycle.

Related Objects

The metadata classifies MRP_CRITERIA as standalone with no foreign-key relationships to other tables. Its key columns (FOLDER_OBJECT, FIELD_NAME) logically correspond to Planner Workbench folder and field definitions, and it is consumed functionally by the Planner Workbench application logic and the MRP/MPS planning engine outputs. Significant associated objects include the Planner Workbench folder definitions, planning exception and suggestion tables that the criteria filter, and the MRP list-of-values views referenced by LOV_NAME. Where no formal FK exists, joins are made at the application layer using FOLDER_OBJECT and FIELD_NAME rather than enforced referential constraints.