Search Results msc_planners




Overview
Explore in AI Chat

Overview

MSC_PLANNERS is a foundational table within the Oracle Advanced Supply Chain Planning (ASCP) module, owned by the MSC schema. It stores and maintains the master list of planner codes used throughout the planning application. In Oracle EBS 12.1.1 and 12.2.2, planner codes serve as the primary organizational unit by which supply chain planning activities are segmented, secured, and reported. Each planner represents an individual or organizational role responsible for reviewing, approving, and executing planning recommendations for a specific set of items, organizations, or supply chain entities.

From a data modeling perspective, the heuristic Data Vault classification for this table is standalone, based on its mined foreign key structure. While it contains a self-contained business key, the mining exercise did not surface strong hub, link, or satellite relationships from the schema alone. A data vault practitioner might nevertheless treat the planner code as a natural business key candidate for a hub, given the presence of the unique index MSC_PLANNERS_U1. This classification should be regarded as a modeling suggestion rather than a definitive architectural directive.

Key Information Stored

The table contains 35 documented columns. The most significant business columns include:

  • PLANNER_CODE — The business identifier for a planner, widely referenced across planning tables, concurrent programs, and profile options.
  • ORGANIZATION_ID — The inventory organization to which the planner is associated, enabling organization-specific planner segmentation.
  • SR_INSTANCE_ID — The source system instance identifier, supporting multi-source or multi-instance data collection scenarios.
  • DESCRIPTION — A human-readable description of the planner.
  • DISABLE_DATE — The date on which the planner became inactive; null values typically indicate active planners.
  • EMPLOYEE_ID — A foreign key referencing PSB_EMPLOYEES, linking the planner to an HR employee record.
  • ELECTRONIC_MAIL_ADDRESS — The planner's email address, used for notification workflows.
  • USER_NAME — The associated application user account.
  • CURRENT_EMPLOYEE_FLAG — Indicates whether the planner currently corresponds to an active employee.
  • REFRESH_NUMBER — Supports the ASCP data refresh and collection versioning process.
  • Standard audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and the ATTRIBUTE1–ATTRIBUTE15 descriptive flexfield columns.

The surrogate primary key is MSC_PLANNERS_PK, defined over (PLANNER_CODE, ORGANIZATION_ID, SR_INSTANCE_ID). The unique index MSC_PLANNERS_U1 covers (SR_INSTANCE_ID, PLANNER_CODE, ORGANIZATION_ID), confirming the composite business key candidate.

Common Use Cases and Queries

Typical use cases include validating planner codes during ASCP setup, generating planner-based assignment reports, and filtering plan outputs by planner. A common query pattern retrieves active planners for a given organization:

  • SELECT planner_code, description, employee_id, electronic_mail_address FROM msc_planners WHERE organization_id = :org_id AND disable_date IS NULL;
  • Joining to PSB_EMPLOYEES on employee_id to enrich planner records with HR details.
  • Joining to planning result tables (such as MSC_SUPPLIES or MSC_DEMANDS) on planner_code to produce planner-scoped exception reports.

Reporting use cases include planner workload summaries, inactive planner audits, and reconciliation between ASCP planner codes and HR employee assignments.

Related Objects

  • PSB_EMPLOYEES — Referenced via MSC_PLANNERS.EMPLOYEE_ID, providing HR employee context.
  • MSC_PLANNERS_PK — Primary key constraint governing uniqueness.
  • MSC_PLANNERS_U1 — Unique index supporting the business key.
  • Planning result tables (e.g., msc_supplies, msc_demands, msc_exceptions) — Joined on planner_code for planner-scoped reporting.
  • MRP/MPS planning tables — Share planner_code semantics across planning modules.
  • FND_USER — Correlates via USER_NAME for application account linkage.

Together these associations establish MSC_PLANNERS as the reference anchor for planner-driven segmentation and security across Oracle Advanced Supply Chain Planning.