Search Results mrp_scheduling_rules_pk

Overview

MRP_SCHEDULING_RULES is a reference and configuration table in the Oracle E-Business Suite Master Scheduling/MRP (MRP) module, owned by the MRP schema. It stores the scheduling rules consumed by the planning and execution engines to determine how planned orders, repetitive schedules, and discrete jobs are sequenced and dated. Rather than holding transactional supply or demand, the table acts as a control-point library: each row defines a named rule, the logic that implements it, and the operational context in which it applies. Rows are read at plan run time and during execution, allowing planners to influence scheduling behaviour without modifying application code.

From a data-modelling perspective, the ETRM metadata classifies this object heuristically as standalone under Data Vault conventions. In practice this suggests modelling MRP_SCHEDULING_RULES as a hub keyed on RULE_ID, with its descriptive and flag columns carried as satellite attributes, and no natural link to another hub since no foreign-key relationships are documented. The classification is a modelling suggestion only; the physical table remains a conventional Oracle EBS setup entity.

Key Information Stored

The table is documented with 32 columns in the 12.2.2 physical schema. The most significant are:

• RULE_ID — the surrogate primary key, constrained by MRP_SCHEDULING_RULES_PK, uniquely identifying each scheduling rule.
• MEANING and DESCRIPTION — the user-facing rule name and its explanatory text.
• PACKAGE_NAME — the PL/SQL package invoked to apply the rule during planning or execution.
• ENABLED_FLAG — controls whether the rule is active and therefore eligible for selection.
• DEFAULT_FLAG — identifies the rule applied when no explicit selection is made.
• USER_DEFINED — distinguishes seeded Oracle rules from customer-created rules.
• USAGE_CODE — denotes the functional context (for example planning versus execution) in which the rule may be used.
• SEQUENCE_NUMBER — orders rules for evaluation and presentation.
• HEURISTIC_CODE — links the row to heuristic scheduling logic.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS flexfield descriptor columns for extensibility.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — the mandatory WHO audit columns.
• ZD_EDITION_NAME — the editioning column supporting EBS online patching.

Two unique indexes act as business-key candidates: MRP_SCHEDULING_RULES_U1 on (RULE_ID, SEQUENCE_NUMBER, ZD_EDITION_NAME) and MRP_SCHEDULING_RULES_U2 on (MEANING, SEQUENCE_NUMBER, ZD_EDITION_NAME).

Common Use Cases and Queries

Typical scenarios include auditing which scheduling rules are active, locating the default rule, and tracing the package that implements a given rule. A standard listing query is:

• SELECT rule_id, meaning, package_name, usage_code, enabled_flag, default_flag FROM mrp.mrp_scheduling_rules WHERE enabled_flag = 'Y' ORDER BY sequence_number;
• Isolating the default: SELECT * FROM mrp.mrp_scheduling_rules WHERE default_flag = 'Y' AND enabled_flag = 'Y';
• Separating seeded from custom rules: SELECT meaning, user_defined, creation_date FROM mrp.mrp_scheduling_rules WHERE user_defined = 'Y';
• Environment comparison, joining MRP_SCHEDULING_RULES_U2 business keys between instances to detect drift in rule definitions after patching or migration.

Reporting use cases include a scheduling-rule register for change control, verification that a default rule exists before a plan run, and impact analysis before disabling a rule referenced by execution logic.

Related Objects

The ETRM metadata records no foreign-key dependencies, consistent with the standalone classification. The following objects are the most likely consumers or logical companions:

• MRP_SCHEDULING_RULES_PK and the unique indexes MRP_SCHEDULING_RULES_U1 / U2 — enforce identity and business-key integrity.
• FND_LOOKUP_VALUES — typically supplies the meaning behind USAGE_CODE and similar coded values.
• FND_USER — resolves CREATED_BY and LAST_UPDATED_BY to user names.
• MRP_PLANNERS — planner definitions that operate against rules selected from this table.
• MRP_AP_SCHEDULING_RULES — the application-program layer invoked when a rule is applied during a plan run.
• MRP_SCHEDULING_RULES_TL — the translated variant, where installed, holding language-specific MEANING and DESCRIPTION.

Because no FK columns are documented, joins to these objects are driven by coded values and the PACKAGE_NAME reference rather than enforced referential constraints.