Search Results msc_plan_org_kpis




Overview
Explore in AI Chat

Overview

The MSC_PLAN_ORG_KPIS table is a core data structure within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module. It functions as the central repository for defining and storing Key Performance Indicators (KPIs) and their associated threshold values at the organization level for specific supply chain plans. This table is essential for performance monitoring within Oracle Supply Chain Hub, enabling planners to measure, track, and analyze the operational effectiveness of their plans against predefined targets. Its existence is critical for generating plan performance dashboards and reports that drive continuous improvement in the planning process.

Key Information Stored

The table's primary key uniquely identifies a KPI record for a specific organization within a plan, comprising four columns: KPI_ID, ORGANIZATION_ID, PLAN_ID, and SR_INSTANCE_ID. The KPI_ID column identifies the specific performance metric being tracked, such as on-time delivery, inventory turns, or forecast accuracy. The ORGANIZATION_ID, PLAN_ID, and SR_INSTANCE_ID columns together define the organizational and planning context, linking the KPI to a specific entity within a specific plan instance. While the provided metadata does not list all columns, typical data stored would include target thresholds, actual calculated values, and potentially status flags indicating if a KPI is within an acceptable range. The foreign key relationships enforce data integrity by ensuring the organization and plan combination exists in the MSC_PLAN_ORGANIZATIONS table.

Common Use Cases and Queries

The primary use case is reporting and analytics on plan performance. Planners and managers query this table to assess how well a supply chain plan is meeting its strategic objectives. A common query pattern involves joining to MSC_PLAN_ORGANIZATIONS to fetch organization details and filtering by PLAN_ID to review all KPIs for a specific plan run. For example, to find all KPIs where the actual performance is below the target threshold for a given plan, a query might select records based on a comparison between actual and target value columns. Developers may also query this table to populate custom performance scorecards or to integrate KPI data with external business intelligence tools. Searching for a specific KPI_ID across all plans, as indicated by the user's search, is a typical diagnostic or analysis task.

Related Objects

  • MSC_PLAN_ORGANIZATIONS: This is the primary related table, as enforced by a foreign key constraint. The MSC_PLAN_ORG_KPIS table references it via the composite key of PLAN_ID, ORGANIZATION_ID, and SR_INSTANCE_ID. This ensures that a KPI can only be defined for an organization that is included in the plan.
  • MSC_PLAN_ORG_KPIS_PK: This is the primary key constraint on the table itself, defined on the columns (KPI_ID, ORGANIZATION_ID, PLAN_ID, SR_INSTANCE_ID).