Search Results kpa_code

Overview

PA_PERF_RULES_V is an Oracle Applications (APPS) database view within the Projects (PA) product family. It exposes the definition of the performance rules available to the Oracle Projects performance and measurement framework. Performance rules associate a rule type with a key performance area (KPA), an underlying measure, a scoring method, and a set of formatting and validity attributes. The view is a denormalized, user-facing read layer over the base performance rule table, resolving code values to their translated meanings and joining supplemental measure information.

In Oracle EBS 12.1.1 and 12.2.2, this view is typically consumed by reporting tools, custom extensions, and integrations that need to enumerate or validate performance rules without performing lookup joins manually. It is a standard, VALID view owned by the APPS schema. The view flattens several coded reference columns into display-ready names, which makes it suitable for use in Oracle Reports, BI Publisher data models, OBIEE-style federated queries, and ad hoc SQL. Because it is a view rather than a table, it carries no independent data; all content is derived from its referenced base objects at query time.

Underlying Base Objects

Per the documented ETRM metadata, PA_PERF_RULES_V is defined over three referenced objects:

• PA_PERF_RULES (SYNONYM) — the primary driving table, supplying the persistent rule definition. This is the fact source for the view.
• PA_LOOKUPS (VIEW) — a lookup view referenced twice in the definition: once aliased as RT for the PA_PERF_RULE_TYPES lookup type, and once as KPA for the PA_PERF_KEY_AREAS lookup type. These joins translate RULE_TYPE and KPA_CODE into their MEANING values.
• PJI_MT_MEASURES_V (VIEW) — a measures view joined on MEASURE_ID to resolve MEASURE_NAME. This join is an outer join, meaning rules without a valid measure still appear.

The joins are enforced on lookup type plus lookup code, and the key area lookup is further restricted by ENABLED_FLAG = 'Y'. As a result, the view returns only rules whose key area code maps to an enabled lookup value, and it suppresses rows whose rule type lacks a corresponding lookup entry.

Key Columns

• RULE_ID, RULE_NAME, RULE_DESCRIPTION — identifier, display name, and narrative describing each performance rule.
• RULE_TYPE and RULE_TYPE_NAME — the stored rule type code and its translated meaning from PA_PERF_RULE_TYPES.
• KPA_CODE and KPA_NAME — the key performance area code (the column central to the "kpa_code" search) and its translated meaning from PA_PERF_KEY_AREAS.
• MEASURE_ID, MEASURE_NAME, MEASURE_FORMAT, CURRENCY_TYPE, PERIOD_TYPE, PRECISION — the associated measure and its presentation attributes, including formatting and numeric precision.
• SCORE_METHOD — the method applied to score the rule.
• START_DATE_ACTIVE, END_DATE_ACTIVE — effective dating that governs when the rule is active.
• RECORD_VERSION_NUMBER and the standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) — concurrency and audit tracking.

Common Use Cases and Queries

Typical uses include listing active rules filtered by key performance area, reporting rule-to-measure mappings, and validating KPA codes supplied by an interface or integration. The following retrieves rules for a specific KPA:

• SELECT rule_name, kpa_code, kpa_name, measure_name, score_method FROM pa_perf_rules_v WHERE kpa_code = 'YOUR_KPA' ORDER BY rule_name;
• SELECT kpa_code, kpa_name, COUNT(*) FROM pa_perf_rules_v GROUP BY kpa_code, kpa_name;
• SELECT r.rule_name, r.measure_name FROM pa_perf_rules_v r WHERE TRUNC(SYSDATE) BETWEEN NVL(r.start_date_active, SYSDATE) AND NVL(r.end_date_active, SYSDATE);

Because KPA_CODE is resolved through an enabled-flag-filtered lookup join, queries on this column return only valid, active key areas, making the view a reliable source for code validation and reference reporting.