Search Results mrp_scheduling_rules_v

Overview

MRP_SCHEDULING_RULES_V is a seeded, read-only view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the scheduling rule definitions used by the Master Scheduling/MRP (MRP) product to determine how planned orders are scheduled, rescheduled, and time-fenced during planning runs. The view provides a business-friendly projection of the underlying MRP_SCHEDULING_RULES base table, surfacing rule identity, descriptive text, enablement status, package binding, usage classification, sequence ordering, and the full DFF-attribute block along with the ROWID alias ROW_ID.

Because it is a view rather than a table, MRP_SCHEDULING_RULES_V is intended for reporting, integration, and inquiry purposes. It carries no independent storage; all reads resolve to the base table. This makes it a safe target for BI Publisher data models, custom concurrent program queries, and inbound/outbound interface logic that needs to present scheduling rules without touching the base table directly. The presence of standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) means it participates in Oracle's standard audit and multi-org-aware reporting conventions.

Underlying Base Objects

The view is defined over a single documented base object: the synonym MRP_SCHEDULING_RULES. The view text shows a straight SELECT ... FROM MRP_SCHEDULING_RULES with no joins, unions, or aggregation. Every column in the view maps one-to-one to a column in the base table, and the additional ROWID ROW_ID projection aliases the physical row identity for the underlying row. Because the view is owner APPS and the base object is referenced as a synonym, the view resolves against the APPS-owned MRP scheduling rules table at runtime; the synonym abstraction shields dependent code from any future schema reorganization.

Status is VALID, indicating the view compiles and is queryable in the documented ETRM 12.2.2 environment. No INSTEAD-OF triggers or updatable-view logic are documented, so all DML must target the base table, not the view.

Key Columns

• ROW_ID — ROWID of the underlying MRP_SCHEDULING_RULES row; useful for uniquely identifying a rule without relying on RULE_ID.
• RULE_ID — Primary identifier of the scheduling rule.
• MEANING — Translated/display name of the rule, typically populated from the lookup meaning.
• DESCRIPTION — Free-text description of the rule's purpose.
• USER_DEFINED — Flag distinguishing seeded (system) rules from user-created rules. In the context of the search term "user_defined", this is the pivotal column: it allows a query to isolate custom scheduling rules from Oracle-delivered ones.
• ENABLED_FLAG — Indicates whether the rule is active (Y) or disabled (N) for use in planning.
• PACKAGE_NAME — PL/SQL package invoked to perform the rule's scheduling logic.
• USAGE_CODE — Classification of the rule's usage (e.g., planning, scheduling context).
• SEQUENCE_NUMBER — Ordering value determining the precedence in which rules are evaluated.
• HEURISTIC_CODE — Code identifying the heuristic applied by the rule.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — Standard descriptive flexfield (DFF) context and segment columns for customer-extensible data.
• WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN for audit lineage.

Common Use Cases and Queries

The most frequent use of this view, and the one implied by the "user_defined" search, is reporting on custom versus seeded scheduling rules. A typical query lists enabled, user-defined rules in evaluation order:

• SELECT RULE_ID, MEANING, DESCRIPTION, SEQUENCE_NUMBER FROM APPS.MRP_SCHEDULING_RULES_V WHERE USER_DEFINED = 'Y' AND ENABLED_FLAG = 'Y' ORDER BY SEQUENCE_NUMBER;
• Auditing all rules defined in the instance: SELECT RULE_ID, MEANING, PACKAGE_NAME, USAGE_CODE, ENABLED_FLAG, USER_DEFINED FROM APPS.MRP_SCHEDULING_RULES_V ORDER BY SEQUENCE_NUMBER;
• Identifying the package bound to a rule for troubleshooting: SELECT MEANING, PACKAGE_NAME, HEURISTIC_CODE FROM APPS.MRP_SCHEDULING_RULES_V WHERE RULE_ID = :p_rule_id;
• Reporting customized DFF content: SELECT RULE_ID, MEANING, ATTRIBUTE_CATEGORY, ATTRIBUTE1, ATTRIBUTE2 FROM APPS.MRP_SCHEDULING_RULES_V WHERE ATTRIBUTE_CATEGORY IS NOT NULL;
• Change tracking via audit columns: SELECT RULE_ID, MEANING, LAST_UPDATE_DATE, LAST_UPDATED_BY FROM APPS.MRP_SCHEDULING_RULES_V ORDER BY LAST_UPDATE_DATE DESC;

These queries support planning rule administration reviews, migration validation between environments, and integration extracts that must enumerate available scheduling rules with their enablement and ordering metadata.