Search Results pa_perf_transactions




Overview
Explore in AI Chat

Overview

PA_PERF_TRANSACTIONS is a transaction-level table in the Oracle Projects (PA) module of Oracle E-Business Suite, documented as valid in both release 12.1.1 and 12.2.2. It records performance transaction data — the individual measured results produced when performance rules are evaluated against projects and other objects. Each row represents a discrete performance evaluation event, capturing the rule applied, the object evaluated, the measure assessed, the value obtained, and whether the outcome fell inside or outside defined thresholds. Because performance transactions drive key performance indicator (KPI) scoring, exception reporting, and project performance analytics, this table sits at the centre of the Project Performance Reporting and KPI framework.

The heuristic Data Vault classification mined from the foreign-key structure is satellite-leaning. In modeling terms, this suggests PA_PERF_TRANSACTIONS behaves primarily as a descriptive satellite attached to project, rule, and object-rule hubs, with each row holding attributes (measure values, thresholds, flags) that change over time rather than defining new business entities. The presence of CURRENT_FLAG and RECORD_VERSION_NUMBER reinforces the slowly changing dimension / satellite interpretation.

Key Information Stored

The documented schema contains 31 columns. The single-column surrogate primary key is PERF_TXN_ID, also implemented as unique index PA_PERF_TRANSACTIONS_U1, which makes it the strongest business-key candidate in the table. Important columns include:

Common Use Cases and Queries

Typical scenarios include auditing how a KPI score was derived, diagnosing why an exception was raised on a project, and reconciling performance data for a given period. A common lookup retrieves a single transaction by primary key:

  • SELECT * FROM pa.pa_perf_transactions WHERE perf_txn_id = :perf_txn_id;
  • SELECT project_id, measure_id, measure_value, exception_flag FROM pa.pa_perf_transactions WHERE period_name = :period AND current_flag = 'Y';
  • SELECT t.perf_txn_id, t.measure_value, r.rule_name FROM pa.pa_perf_transactions t, pa.pa_perf_rules r WHERE t.rule_id = r.rule_id AND t.exception_flag = 'Y';

Reporting use cases focus on exception dashboards, KPI scorecards where INCLUDED_IN_SCORING and CURRENT_FLAG filter the effective rows, and traceability reports joining PROGRAM_ID to the concurrent request log to identify the batch that produced the transactions.

Related Objects

The most significant related objects, based on documented foreign-key relationships, are:

  • PA_PERF_RULES — joined via PA_PERF_TRANSACTIONS.RULE_ID.
  • PA_PERF_OBJECT_RULES — joined via PA_PERF_TRANSACTIONS.OBJECT_RULE_ID.
  • PA_PROJECTS_ALL — referenced three times, via PROJECT_ID, RELATED_OBJ_ID, and PPL_PROJECT_ID.
  • FND_CONCURRENT_REQUESTS — joined via PROGRAM_ID to identify the generating concurrent request.
  • PA_PERF_COMMENTS — child table joined via PERF_TXN_ID.
  • PA_PERF_KPA_TRANS — child table joined via PERF_TXN_ID.

Together these objects form the performance measurement chain: rules and object rules define what is measured, projects supply the subject, concurrent requests supply the process context, and the comment and KPA transaction tables provide the dependent detail.