Results for “msc_allocations”

50+ results




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

Overview

MSC_ALLOCATIONS is a table in the MSC schema owned by Oracle Advanced Supply Chain Planning (ASCP). It stores allocation definitions used during the planning process to distribute constrained supply across demand classes, trading partners, and partner sites. The table operates as part of the allocation rule framework in ASCP, allowing planners to assign a percentage of available supply to specific allocation groups based on priority, service level, and time-phased rules. Its presence is fundamental to constrained and unconstrained plan runs that must respect allocation priorities defined by the enterprise.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure suggests MSC_ALLOCATIONS behaves as a link entity. It connects trading partners, partner sites, allocation rule time phases, and levels through its foreign key columns, capturing relationship-level allocation percentages and priorities. This classification is a modeling suggestion rather than a prescribed Oracle design, but it accurately reflects the table's role as a junction between allocation rule definitions and their target recipients.

Key Information Stored

The table contains 35 documented columns, of which the following are most significant:

Common Use Cases and Queries

Planners and technical teams query this table to audit allocation logic, verify percentage totals by time phase and demand class, and validate priority assignments before launching a plan. A typical reporting query joins MSC_ALLOCATIONS to MSC_TRADING_PARTNERS to display partner-level allocations:

  • SELECT a.ALLOCATION_ID, tp.PARTNER_NAME, a.ALLOCATION_PERCENT, a.PRIORITY FROM MSC_ALLOCATIONS a, MSC_TRADING_PARTNERS tp WHERE a.PARTNER_ID = tp.PARTNER_ID;
  • Aggregation by TIME_PHASE_ID and DEMAND_CLASS (using unique index MSC_ALLOCATIONS_U2) to confirm that allocation percentages sum to 100 percent within a phase.
  • Joins to MSC_ALLOC_RULE_TIME_PHASES to correlate allocations with their effective date ranges.
  • Extraction into custom reporting schemas that feed allocation compliance dashboards.

Because the top-level primary key is the surrogate ALLOCATION_ID, most operational queries filter on TIME_PHASE_ID, DEMAND_CLASS, or PARTNER_ID rather than the surrogate itself.

Related Objects

The following objects are most significant to MSC_ALLOCATIONS through documented relationships:

  • MSC_TRADING_PARTNERS — joined on PARTNER_ID; provides partner identification.
  • MSC_TRADING_PARTNER_SITES — joined on PARTNER_SITE_ID; identifies the receiving partner site.
  • MSC_ALLOC_RULE_TIME_PHASES — joined on TIME_PHASE_ID; defines the time-phased rule context.
  • MSD_LEVELS — joined on LEVEL_ID; defines the supply chain level hierarchy.
  • MSC_ALLOCATIONS_PK / MSC_ALLOCATIONS_U1 / MSC_ALLOCATIONS_U2 — the primary key and unique indexes that enforce uniqueness of ALLOCATION_ID and of the TIME_PHASE_ID plus DEMAND_CLASS combination.