Results for “kpi_value”

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

Overview

MSC_PLAN_ORG_KPIS is a table in the MSC schema (Oracle Advanced Supply Chain Planning) that maintains the key performance indicators and thresholds for plans created on the Oracle Supply Chain Hub. In Oracle EBS 12.1.1 and 12.2.2 deployments, this table serves as the persistent store for KPI measurement values that are computed per plan, per organization, and per source instance, enabling planners and supply chain analysts to evaluate plan quality against configured targets and thresholds.

The table is owned by MSC and is documented as VALID. Its physical schema comprises five columns, and its primary key is constrained by MSC_PLAN_ORG_KPIS_PK, which is composed of KPI_ID, ORGANIZATION_ID, PLAN_ID, and SR_INSTANCE_ID. Under the heuristic Data Vault classification derived from the foreign key structure, this object is assessed as satellite-leaning. In modeling terms, that classification suggests MSC_PLAN_ORG_KPIS behaves as a descriptive satellite attached to a parent hub or link keyed by the plan/organization/source-instance combination, with KPI_ID further qualifying the measured attribute. It should not be treated as an independent hub, because its identity is inherited from the entities it references.

Key Information Stored

The documented column set is compact, and the following columns carry the substantive business meaning:

• KPI_ID — Identifies the specific key performance indicator being measured or thresholded. It participates in the composite primary key and is the principal discriminator of the metric recorded on each row.
• PLAN_ID — Identifies the supply chain plan to which the KPI value applies. This is a foreign key referencing MSC_PLAN_ORGANIZATIONS.PLAN_ID and is part of the primary key.
• ORGANIZATION_ID — Identifies the inventory organization within which the KPI is evaluated. It is part of the primary key and is also covered by the foreign key relationship to MSC_PLAN_ORGANIZATIONS.
• SR_INSTANCE_ID — Identifies the source instance from which the plan and organizational data originate, supporting multi-instance and hosted Supply Chain Hub deployments. It forms part of the primary key.
• KPI_VALUE — Holds the measured or threshold value for the indicator. This is the principal payload attribute of the satellite and is the column most frequently consumed in reporting.

Regarding key structure, the surrogate primary key documented here is the composite constraint MSC_PLAN_ORG_KPIS_PK spanning KPI_ID, ORGANIZATION_ID, PLAN_ID, and SR_INSTANCE_ID. The business-key candidates are effectively these same columns, since no separate single-column surrogate or alternate unique index is documented. The natural grain of the table is therefore one row per KPI per organization per plan per source instance.

Common Use Cases and Queries

The table is typically queried to report plan performance, to compare KPI values against thresholds, and to trend indicator values across plans or organizations. A representative query joining to the parent plan organization table is shown below:

• Plan-level KPI reporting: select KPI_ID, ORGANIZATION_ID, KPI_VALUE from MSC_PLAN_ORG_KPIS where PLAN_ID = :plan_id order by KPI_ID.
• Threshold comparison: filter rows where KPI_VALUE exceeds a configured target, using KPI_ID to select the relevant indicator family.
• Multi-instance consolidation: group by SR_INSTANCE_ID and ORGANIZATION_ID to compare KPI outcomes across hosted source instances.
• Join to plan organizations: join MSC_PLAN_ORG_KPIS k to MSC_PLAN_ORGANIZATIONS o on k.PLAN_ID = o.PLAN_ID and k.ORGANIZATION_ID = o.ORGANIZATION_ID and k.SR_INSTANCE_ID = o.SR_INSTANCE_ID to obtain plan names and organizational context.

Because the table has no date-effective or version columns documented, historical trending generally requires retaining snapshots or joining to plan definition tables elsewhere in the MSC schema.

Related Objects

The most significant related object is the parent in the documented foreign key relationship:

• MSC_PLAN_ORGANIZATIONS — Referenced by MSC_PLAN_ORG_KPIS.PLAN_ID, ORGANIZATION_ID, and SR_INSTANCE_ID. This is the primary join partner and supplies the plan and organization context for each KPI row.
• MSC_PLANS — The plan header table that underlies MSC_PLAN_ORGANIZATIONS; useful for retrieving plan names and attributes in KPI reports.
• MSC_KPIS / KPI definition metadata — Supplies the descriptive definition of each KPI_ID value, including name, unit, and threshold semantics.
• MSC_ORGANIZATIONS / organization views — Provide organization names and classifications for readability in reports.
• MSC_SR_INSTANCES / source instance views — Provide the source instance descriptions referenced by SR_INSTANCE_ID.
• MSC_PLAN_ORG_KPIS_PK index — The primary key constraint and its underlying index, relevant for query tuning on the composite key.

Together these objects form the plan KPI reporting layer within Oracle Advanced Supply Chain Planning, with MSC_PLAN_ORG_KPIS acting as the satellite holding measured values keyed to plan and organization context.