Results for “ozf_dashb_daily_kpi”

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

Overview

The OZF_DASHB_DAILY_KPI table is a Trade Management (OZF) data object in Oracle E-Business Suite, owned by the OZF schema. It stores the Account Manager Dashboard Key Performance Indicator (KPI) records, which are used to present aggregated, business-relevant metrics to account managers who monitor trade promotion and channel revenue activity. The table is registered as VALID and is documented in both ETRM 12.1.1 and 12.2.2 environments with a stable nine-column physical schema.

The object is classified heuristically as standalone for Data Vault modeling purposes, meaning it does not contain foreign key relationships to other OZF objects in the documented metadata. In Data Vault terms, the table can be modelled most naturally as a satellite anchored to a daily KPI hub (DASHB_DAILY_KPI_ID), because it stores descriptive, time-stamped KPI measurements rather than entity relationships. This classification is a modeling suggestion; the physical schema does not enforce parent-child links.

Key Information Stored

The table contains nine documented columns, anchored by a single-column surrogate primary key.

• DASHB_DAILY_KPI_ID — surrogate primary key, implemented through the index DASHB_DAILY_KPI_ID_PK. Uniquely identifies each dashboard KPI record.
• DASHB_DAILY_KPI_ID also appears in the unique index OZF_DASHB_DAILY_KPI_U1, making it a business-key candidate in addition to its PK role.
• REPORT_DATE — the calendar date on which the KPI value was calculated and reported.
• RESOURCE_ID — identifier of the account manager or resource for whom the KPI is captured.
• PERIOD_TYPE_ID — reference to the period type (e.g., daily, weekly, monthly) governing the KPI measurement window.
• TIME_ID — reference to the time dimension member associated with the KPI snapshot.
• SEQUENCE_NUMBER — ordering value used to control display sequence of KPI records on the dashboard.
• KPI_NAME — the descriptive label of the metric being stored.
• KPI_VALUE — the computed numeric or textual value of the KPI.
• ALERT_TYPE — classification flag used to drive visual alerting or exception highlighting on the dashboard.

Common Use Cases and Queries

The primary use case is rendering the Account Manager Dashboard, where daily KPI values must be retrieved, ordered, and threshold-checked per resource. A typical retrieval query:

• SELECT resource_id, report_date, kpi_name, kpi_value, alert_type FROM ozf.ozf_dashb_daily_kpi WHERE report_date = :p_date AND resource_id = :p_resource ORDER BY sequence_number;
• Trend analysis by joining on kpi_name and aggregating kpi_value across report_date ranges to plot performance over time.
• Exception reporting using ALERT_TYPE to isolate KPIs breaching configured thresholds for a given period type.

Because the classification is standalone, queries typically rely on the surrogate key or the business-key index rather than FK joins. Report developers should filter on REPORT_DATE to keep result sets narrow, since the table accumulates daily rows per resource.

Related Objects

As a standalone object, OZF_DASHB_DAILY_KPI has no documented foreign key dependencies. Related objects are therefore inferred from shared columns and OZF module adjacency:

• OZF_DASHB_DAILY_KPI_U1 — unique index enforcing the business key on DASHB_DAILY_KPI_ID.
• DASHB_DAILY_KPI_ID_PK — primary key index supporting row identification.
• RESOURCE_ID logical references to the resource table (e.g., JTF_RS_RESOURCE_EXTNS / PER_ALL_PEOPLE_F) for account manager identity.
• PERIOD_TYPE_ID and TIME_ID logically reference time/period definition tables used elsewhere in Trade Management analytics.

Developers integrating with this table should treat it as an isolated KPI fact store and perform any dimensional lookups on RESOURCE_ID, TIME_ID, and PERIOD_TYPE_ID through custom join logic rather than dependent constraints.