Results for “partition_number”

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

Overview

The MSC_PLAN_PARTITIONS table in the MSC schema (Advanced Supply Chain Planning) stores partition information for planning plans in Oracle EBS 12.1.1 and 12.2.2. Each row captures the partitioning metadata associated with a plan, defining how plan data is segmented and identified within the planning engine. This object is central to the way Advanced Supply Chain Planning (ASCP) organizes and retrieves planning results across large data sets, and it is documented as VALID in the ETRM repository.

The heuristic Data Vault classification mined from the foreign-key structure is standalone, suggesting a modeling pattern where the table functions as an independent reference or hub-like object rather than a dependent satellite or a link between two other entities. In practice, this means MSC_PLAN_PARTITIONS can be modeled as its own primary entity keyed by PLAN_NAME, without assuming a mandatory parent dependency in the Data Vault sense.

Key Information Stored

The documented physical schema exposes 13 columns. The most significant are:

• PLAN_NAME — the business identifier for the plan and, per the documented primary key MSC_PLAN_PARTITIONS_PK, the key column defining this table.
• PLAN_ID — the internal numeric identifier of the plan, typically used in joins to other MSC planning tables.
• PARTITION_NUMBER — the partition sequence identifier; it is also the column behind the unique index MSC_PLAN_PARTITIONS_U1, making it a business-key candidate.
• FREE_FLAG — a flag indicating whether the partition is free or allocated, useful when managing partition availability.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context columns identifying the request and program that created or last updated the partition record.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard Oracle EBS audit columns tracking who and when the row was created and modified.

Note the distinction between the surrogate primary key (MSC_PLAN_PARTITIONS_PK on PLAN_NAME) and the unique business-key candidate (MSC_PLAN_PARTITIONS_U1 on PARTITION_NUMBER). Both must be honored in any integration or data-extraction logic.

Common Use Cases and Queries

Typical scenarios include identifying the partition layout for a given plan, verifying unused (free) partitions before initiating a new planning run, and reconciling partition metadata against plan execution history. A representative query to list partitions for a specific plan:

• SELECT plan_name, plan_id, partition_number, free_flag FROM msc.msc_plan_partitions WHERE plan_name = :plan_name ORDER BY partition_number;
• SELECT partition_number FROM msc.msc_plan_partitions WHERE free_flag = 'Y';
• SELECT p.plan_name, p.partition_number, p.last_update_date, p.last_updated_by FROM msc.msc_plan_partitions p WHERE p.plan_id = :plan_id;

Reporting use cases include partition utilization reports, audit trails of partition creation by concurrent program (via REQUEST_ID and PROGRAM_ID), and data-cleanup scripts that purge partitions associated with obsolete plans.

Related Objects

Because the documented FK classification is standalone, no mandatory parent relationships are recorded. Nonetheless, in the MSC planning schema the following objects are commonly referenced alongside MSC_PLAN_PARTITIONS via PLAN_ID or PLAN_NAME:

• MSC_PLANS — master plan definition table, joined on PLAN_ID/PLAN_NAME.
• MSC_PLAN_SCHEDULES — associated plan scheduling metadata.
• MSC_SUPPLY_PLANS / MSC_DEMAND — plan output data partitioned by the values defined here.
• FND_CONCURRENT_REQUESTS — join on REQUEST_ID for program-context reporting.
• FND_CONCURRENT_PROGRAMS — join on PROGRAM_ID and PROGRAM_APPLICATION_ID.

These joins support both operational troubleshooting and historical analysis of planning partition lifecycles.