Search Results pa_perf_key_areas

Overview

APPS.PA_PERF_RULES_V is a reporting and integration view in Oracle E-Business Suite that exposes the definition of performance rules used by Oracle Project Management and the Performance Management framework. Performance rules encode the scoring logic, measures, key performance areas (KPAs), and formatting conventions that determine how project performance indicators are calculated and displayed. The view presents a denormalized, human-readable rendition of the base performance rule data by joining the transaction table PA_PERF_RULES against the PA_LOOKUPS lookup view and the PJI_MT_MEASURES_V measure view. Because it carries the descriptive meaning values for rule types and key areas alongside the raw lookup codes, the view is well suited to reporting, BI Publisher data templates, and integration endpoints where consumers require labels rather than internal codes. The view is owned by the APPS schema, consistent with other seeded EBS objects.

Underlying Base Objects

The view is defined over three documented referenced objects:

• PA_PERF_RULES (SYNONYM) — The driving table holding the performance rule definitions. Each row represents one rule identified by RULE_ID and named by RULE_NAME.
• PA_LOOKUPS (VIEW) — Joined twice, once as rt with LOOKUP_TYPE = 'PA_PERF_RULE_TYPES' to translate RULE_TYPE, and once as kpa with LOOKUP_TYPE = 'PA_PERF_KEY_AREAS' to translate KPA_CODE. The key-area join additionally enforces KPA.ENABLED_FLAG = 'Y', so only enabled key areas are surfaced. This is why the search term "pa_perf_rule_types" resolves here: PA_PERF_RULE_TYPES is the lookup type used by the view.
• PJI_MT_MEASURES_V (VIEW) — Joined on MEASURE_ID using an outer join (MS.MEASURE_ID (+)), supplying MEASURE_NAME. The outer join allows rules without an associated measure to remain visible.

Unlike the inner joins to PA_LOOKUPS, the measure join is optional; rule rows that do not resolve to a measure are retained with a null measure name.

Key Columns

• RULE_ID, RULE_NAME, RULE_DESCRIPTION — Primary identifier and descriptive attributes of the performance rule.
• RULE_TYPE, MEANING — The lookup code for the rule type and its translated meaning from PA_PERF_RULE_TYPES.
• KPA_CODE, KPA.MEANING — The key performance area code and its translated meaning from PA_PERF_KEY_AREAS.
• MEASURE_ID, MEASURE_NAME — The associated measure and its name sourced from PJI_MT_MEASURES_V.
• MEASURE_FORMAT, CURRENCY_TYPE, PERIOD_TYPE, PRECISION — Formatting and dimensional attributes controlling how the measure value is rendered.
• START_DATE_ACTIVE, END_DATE_ACTIVE — Validity window for the rule.
• SCORE_METHOD — The scoring approach applied by the rule.
• Audit columns — RECORD_VERSION_NUMBER, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include listing all enabled performance rules with their translated rule type and key area, and joining to measures for scorecard reporting. A representative query:

• SELECT rule_id, rule_name, meaning AS rule_type_meaning, kpa.meaning AS kpa_meaning, measure_name FROM apps.pa_perf_rules_v WHERE rule_type = :p_rule_type;

Because the view already resolves the PA_PERF_RULE_TYPES lookup, it is often used to drive LOVs and validation in custom concurrent programs and reports.