Search Results pa_perf_thresholds




Overview
Explore in AI Chat

Overview

PA_PERF_THRESHOLDS is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the threshold definitions associated with exception notification rules. Each row represents a boundary or range against which a project performance metric is evaluated; when a metric breaches a defined threshold, the corresponding exception rule can trigger a notification. The table therefore acts as the quantitative parameter store for the performance exception framework, sitting beneath the rule definitions themselves.

The documented primary key is PA_PERF_THRESHOLDS_PK, defined on the single column THRESHOLD_ID. A unique index, PA_PERF_THRESHOLDS_U1, is also documented on THRESHOLD_ID, confirming the surrogate key as the sole business-key candidate. The metadata's heuristic Data Vault classification is link, which suggests modeling this object as a relationship entity connecting threshold parameters to the rules that consume them. Its foreign keys to PA_PERF_RULES and PA_PERF_OBJECT_RULES on THRES_OBJ_ID reinforce that linking role. The documented physical schema contains 15 columns.

Key Information Stored

The most significant columns of PA_PERF_THRESHOLDS are:

  • THRESHOLD_ID — the surrogate primary key and the column referenced by PA_PERF_THRESHOLDS_PK and PA_PERF_THRESHOLDS_U1.
  • THRES_OBJ_ID — the foreign key linking the threshold to its parent rule or object rule; it references both PA_PERF_RULES and PA_PERF_OBJECT_RULES.
  • RULE_TYPE — classifies the notification or performance rule the threshold belongs to.
  • FROM_VALUE and TO_VALUE — define the numeric range or boundary the metric is compared against.
  • INDICATOR_CODE — identifies the performance indicator being measured.
  • EXCEPTION_FLAG — indicates whether the threshold raises an exception when breached.
  • WEIGHTING — assigns a relative weight to the threshold within rule evaluation.
  • ACCESS_LIST_ID — associates the threshold with an access control list governing visibility or routing.
  • RECORD_VERSION_NUMBER — supports optimistic locking and concurrency control.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard Oracle EBS audit columns recording who created and last modified each row.

The surrogate key (THRESHOLD_ID) is distinct from the business relationship expressed through THRES_OBJ_ID; the latter carries the semantic linkage to the governing rule.

Common Use Cases and Queries

Typical uses include reporting on configured exception thresholds, auditing which ranges are active for a given indicator, and diagnosing why notifications did or did not fire. A representative query joins thresholds to their parent rule:

  • SELECT t.THRESHOLD_ID, t.RULE_TYPE, t.INDICATOR_CODE, t.FROM_VALUE, t.TO_VALUE, t.EXCEPTION_FLAG, t.WEIGHTING FROM PA.PA_PERF_THRESHOLDS t WHERE t.THRES_OBJ_ID = :rule_id;
  • SELECT t.* FROM PA.PA_PERF_THRESHOLDS t, PA.PA_PERF_RULES r WHERE t.THRES_OBJ_ID = r.RULE_ID AND r.RULE_TYPE = :type;
  • Aggregate reporting: SELECT INDICATOR_CODE, COUNT(*), MIN(FROM_VALUE), MAX(TO_VALUE) FROM PA.PA_PERF_THRESHOLDS GROUP BY INDICATOR_CODE;

Because THRES_OBJ_ID can reference either PA_PERF_RULES or PA_PERF_OBJECT_RULES, join logic should account for the applicable parent context. Audit-oriented queries filter on LAST_UPDATE_DATE and LAST_UPDATED_BY.

Related Objects

The following objects are the most significant dependencies, based on the documented foreign-key relationships and their roles in the performance exception framework:

  • PA_PERF_RULES — referenced by PA_PERF_THRESHOLDS.THRES_OBJ_ID; stores the rule definitions to which thresholds belong.
  • PA_PERF_OBJECT_RULES — also referenced by PA_PERF_THRESHOLDS.THRES_OBJ_ID; links thresholds to object-specific rule configurations.
  • PA_PERF_THRESHOLDS_PK — the primary key constraint on THRESHOLD_ID.
  • PA_PERF_THRESHOLDS_U1 — the unique index on THRESHOLD_ID.

These relationships confirm PA_PERF_THRESHOLDS as the parameter-bearing link entity between performance rules and the metrics they monitor.