Results for “msc_allocation_rules”

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

Overview

MSC_ALLOCATION_RULES is a table in the MSC schema (Advanced Supply Chain Planning) that describes allocation rules within Oracle E-Business Suite releases 12.1.1 and 12.2.2. Allocation rules in MSC are used by the planning engine to distribute constrained supply across competing demand, to apportion on-hand inventory, or to drive sourcing and supply allocation logic during a plan run. Each row in the table defines a named rule that can then be assigned to a plan, organization, or item context through related assignment tables.

The table carries a documented primary key constraint, MSC_ALLOCATION_RULES_PK, defined on the ALLOCATION_RULE_NAME column, and a unique index, MSC_ALLOCATION_RULES_U1, also on ALLOCATION_RULE_NAME. Based on the foreign-key topology supplied in the ETRM metadata—where MSC_ALLOCATION_ASSIGNMENTS and MSC_ALLOC_RULE_TIME_PHASES both reference this table on ALLOCATION_RULE_NAME—the object exhibits hub-leaning characteristics. In Data Vault modeling terms, MSC_ALLOCATION_RULES is best treated as a hub candidate: a business-key-anchored entity that other tables reference.

Key Information Stored

The table contains 23 documented columns. The most operationally significant are listed below.

• ALLOCATION_RULE_NAME — The business key. It is the primary key column of MSC_ALLOCATION_RULES_PK and the unique-indexed column in MSC_ALLOCATION_RULES_U1. It is also the foreign-key target from both dependent tables.
• DESCRIPTION — Free-text description of the allocation rule, used in the MSC planning UI and in reporting to identify the rule's purpose.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS audit and concurrency columns that record who created and last modified each rule and when.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard Oracle EBS descriptive-flexfield placeholder columns, available for customer-specific extension attributes.

The metadata does not document a surrogate sequence-generated primary key column separate from the business key ALLOCATION_RULE_NAME; the unique index on that column serves as the business-key candidate.

Common Use Cases and Queries

Typical scenarios include retrieving the list of allocation rules available to a plan, validating rule assignments, and auditing rule creation history. A basic lookup of rule name and description is shown below.

• List all allocation rules: SELECT ALLOCATION_RULE_NAME, DESCRIPTION FROM MSC.MSC_ALLOCATION_RULES ORDER BY ALLOCATION_RULE_NAME;
• Find rules assigned to plans or organizations: join MSC_ALLOCATION_RULES to MSC_ALLOCATION_ASSIGNMENTS on ALLOCATION_RULE_NAME.
• Inspect time-phased behavior of a rule: join to MSC_ALLOC_RULE_TIME_PHASES on ALLOCATION_RULE_NAME.
• Audit recently modified rules: filter MSC_ALLOCATION_RULES on LAST_UPDATE_DATE and report LAST_UPDATED_BY.

These queries support reporting on planning configuration, troubleshooting allocation outcomes, and reconciling rule definitions across environments.

Related Objects

The ETRM metadata documents two dependent tables that reference MSC_ALLOCATION_RULES via the ALLOCATION_RULE_NAME column.

• MSC_ALLOCATION_ASSIGNMENTS — References MSC_ALLOCATION_RULES.ALLOCATION_RULE_NAME. It records where a given rule is applied (for example, plan, organization, or item assignment).
• MSC_ALLOC_RULE_TIME_PHASES — References MSC_ALLOCATION_RULES.ALLOCATION_RULE_NAME. It stores the time-phased values or percentages that define how the allocation rule behaves over planning buckets.

Together these objects form the core structure around allocation rule definition, assignment, and time-phased execution within Advanced Supply Chain Planning.