Search Results pa_perf_rules




Overview
Explore in AI Chat

Overview

PA_PERF_RULES is a core configuration table in the Oracle Projects (PA) module of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the definitions of the available performance rules used by Oracle Projects to evaluate project, resource, and transaction performance against established key performance indicators (KPIs) and key performance areas (KPAs). Each row in the table represents a single performance rule, combining the rule's identity, the measure it evaluates, the scoring methodology applied, and the active date range over which the rule is valid.

In Data Vault modeling terms, the heuristic classification mined from the foreign-key structure is hub-leaning. This suggests PA_PERF_RULES functions primarily as a reference or dimension hub, with its surrogate key (RULE_ID) distributed to dependent transactional and summary tables. The table is owned by the PA schema and is marked VALID in the ETRM dictionary.

Key Information Stored

The table contains 19 documented columns. Of these, the most significant are:

  • RULE_ID — The surrogate primary key, defined by the PA_PERF_RULES_PK constraint. It uniquely identifies each performance rule and is the column carried into all foreign-key relationships.
  • RULE_NAME — The user-facing name of the performance rule. Along with RULE_TYPE, this forms a business-key candidate (unique index PA_PERF_RULES_U2).
  • RULE_TYPE — Classifies the rule category, and together with RULE_NAME constitutes the second unique index.
  • RULE_DESCRIPTION — A free-text description of the rule's purpose and behavior.
  • KPA_CODE — Identifies the Key Performance Area to which the rule belongs.
  • MEASURE_ID — References the measure evaluated by the rule.
  • MEASURE_FORMAT — Defines the display or storage format of the measured value.
  • CURRENCY_TYPE — Indicates the currency context when the measure is monetary.
  • PERIOD_TYPE — Specifies the time period granularity over which the rule is evaluated.
  • PRECISION — Defines the numeric precision applied to the score or measured value.
  • SCORE_METHOD — Identifies the method used to compute the rule's score.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — Bound the effective date range during which the rule is usable.
  • RECORD_VERSION_NUMBER — Supports optimistic concurrency control.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns.

The distinction between the surrogate key (RULE_ID) and the business-key candidates (RULE_NAME and RULE_TYPE) is important when integrating with external systems or de-duplicating rule definitions.

Common Use Cases and Queries

Typical usage includes creating performance rules, reporting on enabled rules, and tracing how rules flow into performance transactions and summaries. A common query retrieves all active rules for a given KPA and type:

  • SELECT rule_id, rule_name, rule_type, kpa_code, score_method FROM pa_perf_rules WHERE rule_type = :p_rule_type AND TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, TRUNC(SYSDATE)+1);
  • Joining to dependent tables to audit rule usage: SELECT r.rule_name, t.transaction_id FROM pa_perf_rules r, pa_perf_transactions t WHERE r.rule_id = t.rule_id;
  • Reporting rules lacking thresholds or object mappings by outer-joining PA_PERF_THRESHOLDS and PA_PERF_OBJECT_RULES.

These patterns support operational dashboards, configuration audits, and migration validation when moving rules between environments.

Related Objects

The foreign-key metadata identifies four principal dependent tables that reference PA_PERF_RULES through RULE_ID or THRES_OBJ_ID:

  • PA_PERF_TRANSACTIONS — Joins on RULE_ID; stores performance transactions generated against each rule.
  • PA_PERF_OBJECT_RULES — Joins on RULE_ID; maps rules to project objects.
  • PA_PERF_KPA_SUMMARY_DET — Joins on RULE_ID; holds KPA summary detail aggregations.
  • PA_PERF_THRESHOLDS — Joins on THRES_OBJ_ID to RULE_ID; defines threshold bands applied to rule scores.

Together these tables form the performance-management subsystem, with PA_PERF_RULES acting as the central hub supplying rule identity to transactional, mapping, summary, and threshold satellites.