Results for “heuristic_code”

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

Overview

The MSC_SCH_RULE_NAMES_V view is a reporting and integration object owned by the APPS schema within the MSC (Advanced Supply Chain Planning) product family of Oracle E-Business Suite. It is documented as a VALID view in both EBS 12.1.1 and 12.2.2 environments. The view exposes scheduling rule definitions, presenting a flattened, denormalized projection of the MSC_SCHEDULING_RULES base table so that downstream forms, concurrent programs, reports, and external integrations can resolve rule identifiers to human-readable names and associated configuration attributes.

Its principal role is to provide a stable, read-friendly interface for the planning engine's rule metadata layer. Rather than requiring consuming code to join directly against the scheduling rules base table, the view centralizes the selection of descriptive columns — including the rule meaning, description, package name, enabled state, and the flexible attribute columns — behind a single database object. Because the view applies a SELECT DISTINCT to its projection, callers receive a deduplicated set of rule rows suitable for list-of-values population, lookup resolution, and reference reporting.

Underlying Base Objects

The view is defined over a single documented base object: MSC_SCHEDULING_RULES, referenced through a SYNONYM in the APPS schema. No joins to other tables are present in the documented view text, meaning the view is essentially a filtered column projection rather than an aggregation across multiple entities.

The SELECT DISTINCT MSR.* ... FROM MSC_SCHEDULING_RULES MSR construct indicates that the underlying table may contain logically duplicate rows for a given rule identifier, and the view collapses these into a single distinct representation. This behavior is significant for integrations that expect one row per RULE_ID. The view inherits the storage and indexing characteristics of the base table, so query performance is governed by the indexes defined on MSC_SCHEDULING_RULES, not by any view-level optimization.

Key Columns

• RULE_ID — The primary rule identifier; the join key to scheduling rule consumers.
• MEANING — The user-facing rule name; the primary column used in lists of values and reports.
• DESCRIPTION — Descriptive text explaining the rule's purpose.
• USER_DEFINED — Flag distinguishing user-created rules from seeded Oracle rules.
• PACKAGE_NAME — The name of the PL/SQL package implementing the rule's logic.
• ENABLED_FLAG — Indicates whether the rule is active for planning use.
• DEFAULT_FLAG — Identifies the default rule applied when none is specified.
• HEURISTIC_CODE — The heuristic classification associated with the rule; relevant to users searching on "heuristic_code" for scheduling heuristic configuration.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The standard Oracle flexfield descriptive columns for extensibility.

Common Use Cases and Queries

Typical uses include populating rule selection lists, auditing enabled versus disabled heuristics, and integrating rule metadata into external planning tools. The following query lists all enabled scheduling rules with their heuristic codes:

• SELECT RULE_ID, MEANING, HEURISTIC_CODE FROM MSC_SCH_RULE_NAMES_V WHERE ENABLED_FLAG = 'Y';
• SELECT MEANING, PACKAGE_NAME FROM MSC_SCH_RULE_NAMES_V WHERE DEFAULT_FLAG = 'Y';
• SELECT RULE_ID, MEANING FROM MSC_SCH_RULE_NAMES_V WHERE HEURISTIC_CODE IS NOT NULL AND USER_DEFINED = 'Y';

These patterns reflect the view's purpose as a lookup and reporting layer over the scheduling rules base table.