Search Results msc_criteria




Overview
Explore in AI Chat

Overview

MSC_CRITERIA is a configuration table in the MSC schema belonging to the Oracle Advanced Supply Chain Planning (ASCP) product family. It stores the seeded criteria definitions that drive the Planner Workbench — the primary user interface through which planners review, filter, and act upon supply chain plans. Each row describes a single selectable criterion (a field or folder attribute) that the Workbench exposes to end users for building queries, folder views, and personalized layouts. Because the contents are seeded by Oracle rather than entered by customers, the table functions as a metadata repository for the Workbench rather than as transactional planning data.

The ETRM metadata classifies this object heuristically as standalone from a Data Vault modeling perspective. This suggests it does not participate as a hub or link; it is best modeled as a reference/satellite-style configuration entity keyed by its own business identifiers. In practice, MSC_CRITERIA is a static, low-volume reference table that changes only through patches or seed data updates, not through routine user activity.

Key Information Stored

The table's physical schema in 12.2.2 documents 20 columns. The most operationally significant are described below.

  • FOLDER_OBJECT and FIELD_NAME — Together they form the primary key (MSC_CRITERIA_PK). FOLDER_OBJECT identifies the Workbench folder or entity to which the criterion belongs, while FIELD_NAME names the specific attribute being defined.
  • FIELD_TYPE — Indicates the data type or control type of the criterion, governing how the Workbench renders the field for filtering or display.
  • LOV_NAME and LOV_TYPE — Reference a List of Values definition and its type, populating valid selection choices for the criterion.
  • SQL_STATEMENT and SQL_STATEMENT2 — Store the query fragments used to resolve or filter values for the criterion, enabling dynamic value lists and folder logic.
  • FIELD_PROMPT — The user-facing label displayed in the Planner Workbench interface.
  • APP_SHORT_NAME — Identifies the owning application, allowing criteria to be scoped to a specific EBS module.
  • FLEX_NUM and FLEX_CODE — Support key flexfield-based criteria, tying attributes to flexfield structures.
  • DATA_SET, LONG_LIST, and GROUP_BY — Control dataset association, whether a long list of values is permitted, and grouping behavior within Workbench folders.
  • ZD_EDITION_NAME — The edition identifier used by Oracle's online patching and editioning framework; it participates in the unique index MSC_CRITERIA_U1.
  • Standard WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide audit tracking consistent with EBS conventions.

The surrogate primary key MSC_CRITERIA_PK spans (FOLDER_OBJECT, FIELD_NAME), while the unique index MSC_CRITERIA_U1 spanning (FOLDER_OBJECT, FIELD_NAME, ZD_EDITION_NAME) represents the edition-aware business-key candidate.

Common Use Cases and Queries

MSC_CRITERIA is primarily consumed by the Workbench at runtime, but it is also useful for support analysis, impact assessment, and documentation. Typical scenarios include identifying which criteria a given folder exposes, checking LOV and SQL definitions when a Workbench filter misbehaves, and confirming whether a custom folder object is supported.

A representative query lists all criteria for a folder:

  • SELECT FOLDER_OBJECT, FIELD_NAME, FIELD_PROMPT, FIELD_TYPE, LOV_NAME FROM MSC.MSC_CRITERIA WHERE FOLDER_OBJECT = :folder ORDER BY FIELD_NAME;
  • SELECT FIELD_NAME, SQL_STATEMENT, SQL_STATEMENT2 FROM MSC.MSC_CRITERIA WHERE LOV_NAME = :lov_name;
  • SELECT DISTINCT APP_SHORT_NAME FROM MSC.MSC_CRITERIA ORDER BY 1;

Reporting use cases include auditing which flexfield-based criteria (FLEX_NUM, FLEX_CODE) exist, and verifying GROUP_BY and LONG_LIST settings when performance tuning Workbench folders.

Related Objects

Because the metadata classifies MSC_CRITERIA as standalone, it has no strong foreign-key dependents. Functional dependencies, however, exist through the Planner Workbench and folder infrastructure. The most significant related objects are:

  • FND_FOLDERS / Workbench folder definitions — reference FOLDER_OBJECT values.
  • FND_LOVS — matches against LOV_NAME to resolve list-of-values behavior.
  • MSC_PLANNERS — identifies planner context under which criteria are applied.
  • MSC_PLANS — planning data filtered through Workbench criteria.
  • FND_APPLICATION — resolves APP_SHORT_NAME to the owning application.
  • FND_FLEX_VALUES — used when FLEX_NUM/FLEX_CODE drive key flexfield criteria.

Together these objects connect the seeded criteria metadata to the runtime Workbench experience and the underlying planning data model.