Results for “perf_txn_id”

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

Overview

PA_PERF_KPA_TRANS is a table in the PA (Projects) product schema of Oracle E-Business Suite, holding records of transactions associated with a project key performance indicator (KPI) scoring summary. It is the associative intersection that ties an individual performance transaction to a specific key performance area (KPA) scoring summary detail line. In ETRM 12.2.2 the object is documented with Owner PA and seven columns, and it remains VALID in 12.1.1 and 12.2.2.

From a dimensional modeling standpoint, the provided metadata classifies this object heuristically as a link table. That classification is a modeling suggestion derived from the foreign key structure: the table resolves a many-to-many association between scoring summary detail records and performance transactions, rather than storing descriptive attributes of a single business entity (a hub or satellite). The KPA summary detail and the performance transaction each act as referenced hubs; PA_PERF_KPA_TRANS holds the key pair that joins them.

Key Information Stored

The documented columns are KPA_SUMMARY_DET_ID, PERF_TXN_ID, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. The two identifier columns carry the analytical weight:

• KPA_SUMMARY_DET_ID — Foreign key to PA_PERF_KPA_SUMMARY_DET, identifying the KPA scoring summary detail line to which the transaction contributes.
• PERF_TXN_ID — Foreign key to PA_PERF_TRANSACTIONS, identifying the individual performance transaction being scored or rolled into the KPA summary.
• CREATION_DATE / CREATED_BY — Standard Oracle who-columns recording insert timestamp and the application user responsible for the row.
• LAST_UPDATE_DATE / LAST_UPDATED_BY / LAST_UPDATE_LOGIN — Standard audit columns capturing the most recent modification timestamp, user, and login context.

The primary key, PA_PERF_KPA_TRANS_PK, is the composite of (KPA_SUMMARY_DET_ID, PERF_TXN_ID). A unique index, PA_PERF_KPA_TRANS_U1, covers the same column pair and therefore represents the business-key candidate; consequently no separate surrogate sequence-generated identifier is documented. The primary key itself enforces that a given performance transaction is associated at most once with a given KPA summary detail.

Common Use Cases and Queries

Typical use cases revolve around KPI scoring drill-down and reconciliation: reporting which transactions contributed to a KPA score, verifying that every scored transaction is linked to a summary detail, and auditing score changes. A representative join pattern follows the documented foreign keys:

• Join to PA_PERF_TRANSACTIONS on PERF_TXN_ID to retrieve transaction detail for a summary line.
• Join to PA_PERF_KPA_SUMMARY_DET on KPA_SUMMARY_DET_ID to obtain the KPA score context (for example, the key performance area and period) for each contributing transaction.
• Filter by CREATION_DATE or LAST_UPDATE_DATE for incremental extraction and change-data tracking.
• Group by KPA_SUMMARY_DET_ID to count or aggregate transactions supporting each score.

Sample SQL: SELECT t.kpa_summary_det_id, t.perf_txn_id, x.transaction_attributes FROM pa.pa_perf_kpa_trans t JOIN pa.pa_perf_transactions x ON x.perf_txn_id = t.perf_txn_id WHERE t.kpa_summary_det_id = :detail_id;

Related Objects

The most significant related objects are the two foreign-key parents and their contributing structures:

• PA_PERF_TRANSACTIONS — referenced via PA_PERF_KPA_TRANS.PERF_TXN_ID; supplies the individual performance transaction.
• PA_PERF_KPA_SUMMARY_DET — referenced via PA_PERF_KPA_TRANS.KPA_SUMMARY_DET_ID; supplies the KPA scoring summary detail.
• PA_PERF_KPA_SUMMARIES / scoring summary headers — parent structures aggregated by the KPA summary detail rows.
• PA_PERF_KPA_ASSIGNMENTS / KPA definition tables — provide the key performance area definitions scored by these transactions.
• PA Project Performance reporting views and concurrent programs — consume this link table to present KPI scores and their underlying transactions.

Because PA_PERF_KPA_TRANS is a pure intersection link carrying only keys and audit columns, changes to it directly affect KPI score reconstruction and any downstream performance reporting in the Projects module.