Search Results msc_scheduling_rules_u1

Overview

The MSC.MSC_SCHEDULING_RULES table is a configuration and reference object within the Oracle Advanced Supply Chain Planning (ASCP) schema. It stores the scheduling rules that the planning engine applies when sequencing and scheduling supply, demand, and resource-loaded operations across the plan. Each row defines a named rule that determines the heuristic algorithm and, optionally, a user-defined PL/SQL package used to order scheduled activities. Because scheduling behavior drives plan feasibility and constraint compliance, this table is a foundational control point for plan reproducibility and for tuning how the engine resolves contention on resources, lines, and supplier capacity.

The table resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10, and its unique indexes are placed in APPS_TS_TX_IDX. In Data Vault terms, the metadata classifies this object heuristically as a standalone structure; from a modeling perspective it is best treated as a reference or lookup satellite rather than a hub or link. It has no documented foreign key relationships and therefore does not participate in a parent-child dependency chain within the schema.

Key Information Stored

The physical primary key is MSC_SCHEDULING_RULES_PK, defined on (SEQUENCE_NUMBER, RULE_ID). Two unique indexes provide business-key candidates: MSC_SCHEDULING_RULES_U1 on (RULE_ID, SEQUENCE_NUMBER, ZD_EDITION_NAME) and MSC_SCHEDULING_RULES_U2 on (MEANING, SEQUENCE_NUMBER, ZD_EDITION_NAME). The user specifically searched for the U1 index, which enforces uniqueness of a rule identifier within an edition and sequence context.

• RULE_ID — Surrogate scheduling rule identifier; the core key column in U1.
• MEANING — The scheduling rule code, a short user-facing identifier; the business key in U2.
• DESCRIPTION — Descriptive text explaining the rule's purpose.
• USER_DEFINED — Flag distinguishing customer-defined rules from Oracle-seeded rules.
• PACKAGE_NAME — Name of the user-defined PL/SQL package implementing custom scheduling logic.
• ENABLED_FLAG — Indicates whether the rule is active and available to the planning engine.
• DEFAULT_FLAG — Marks the rule applied by default when no explicit rule is selected.
• USAGE_CODE — Field used for sequencing or categorizing rule usage.
• SEQUENCE_NUMBER — Determines ordering when multiple rules apply; part of both the primary key and both unique indexes.
• HEURISTIC_CODE — Numeric code identifying the heuristic algorithm used by the rule.
• ZD_EDITION_NAME — Editioning column supporting Oracle EBS online patching and edition-based redefinition.
• Standard Who columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.
• Concurrent Who columns — REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.
• Descriptive flexfield columns — ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15.

Common Use Cases and Queries

Typical reporting queries retrieve the enabled rules for plan setup validation or audit. For example, to list all active, user-defined rules in sequence order:

• SELECT rule_id, meaning, description, heuristic_code, package_name FROM msc.msc_scheduling_rules WHERE enabled_flag = 'Y' AND user_defined = 1 ORDER BY sequence_number;
• To locate the default rule: SELECT meaning, description FROM msc.msc_scheduling_rules WHERE default_flag = 'Y' AND enabled_flag = 'Y';
• To trace concurrent changes: SELECT rule_id, meaning, last_update_date, last_updated_by, request_id FROM msc.msc_scheduling_rules ORDER BY last_update_date DESC;

Common scenarios include verifying that a custom scheduling rule package is correctly registered before a plan run, confirming no duplicate MEANING values exist across editions, and extracting rule metadata for documentation or migration between environments.

Related Objects

The ETRM metadata classifies this table as standalone, with no documented foreign keys to parent tables. Its significant relationships are therefore logical rather than enforced:

• MSC_SCHEDULING_RULES_PK / _U1 / _U2 — Indexes and constraints enforcing rule identity and uniqueness.
• MSC_SCHEDULING_RULES_TL — Logical translation table, if seeded multilingual descriptions are used.
• MSC_PLANNED_ORDERS — Plan output referencing the applied scheduling rule.
• MSC_RESOURCE_REQUIREMENTS — Resource-level scheduling detail governed by the rule's heuristic.
• MSC_SUPPLY / MSC_DEMAND — Supply and demand lines sequenced according to the rule.
• FND_APPLICATION / FND_USER — Reference data for the who columns and application context.

Because no hard referential constraints are documented, joins to dependent planning tables should be performed on logical keys such as RULE_ID or MEANING, with edition-awareness applied for EBS 12.2.x environments.