Search Results pa_perf_thresholds_u1




Overview

PA.PA_PERF_THRESHOLDS is a transactional table in the Oracle Projects (PA) schema that stores the threshold definitions used by the exception notification framework. Each row defines a numeric range (a lower bound and an upper bound) that is evaluated against performance indicators; when a measured value falls within a configured range, the exception notification rule associated with the threshold is triggered. As a result, the table functions as the quantitative configuration layer that sits beneath Oracle Projects performance rules and their object associations.

The table resides in the APPS_TS_TX_DATA tablespace, which is consistent with its role as an application-owned transactional repository rather than a pure setup or reference table. The mined relationship data classifies PA_PERF_THRESHOLDS with a Data Vault classification of "link." Interpreted as a modeling suggestion, this indicates that the table functions primarily as an associative structure connecting performance rules or rule-object associations (via THRES_OBJ_ID) to the indicator values and ranges that govern exception evaluation. It is a dependency object rather than an independent master entity.

Key Information Stored

The primary key of the table is PA_PERF_THRESHOLDS_PK on THRESHOLD_ID, a NUMBER(15) surrogate key whose only documented business function is to uniquely identify each threshold row. The unique index PA_PERF_THRESHOLDS_U1 also covers THRESHOLD_ID, confirming it as the sole documented business-key candidate; purely from the documented metadata, THRESHOLD_ID behaves both as surrogate primary key and as the unique access path.

The most significant columns for understanding a threshold record are:

  • THRES_OBJ_ID — identifies the object the threshold is associated with. Valid objects are documented as a Performance Rule and a Performance Rule Object Association, making this the principal foreign-key-style linkage column.
  • RULE_TYPE — VARCHAR2(30) storing the performance rule type, used to categorize the rule context under which the threshold is evaluated.
  • FROM_VALUE and TO_VALUE — the lower and upper numeric bounds of the threshold range. Together they define the interval against which an indicator is tested.
  • INDICATOR_CODE — VARCHAR2(30) lookup code identifying the performance indicator that the threshold measures.
  • EXCEPTION_FLAG — indicates whether the threshold is checked against an exception condition, effectively determining whether the row participates in exception notification.
  • WEIGHTING — numeric weighting applied to the threshold, used when thresholds are aggregated or scored.
  • ACCESS_LIST_ID — access list identifier governing visibility of the threshold.
  • RECORD_VERSION_NUMBER — the record-locking counter used by self-service applications to detect concurrent updates.
  • Standard Who columnsCREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN capture audit and multi-user update context.

Common Use Cases and Queries

The primary operational use case is exception notification configuration review: administrators inspect which ranges are defined for a given rule, indicator, or performance object. A second use case is investigating why a notification did or did not fire, which requires tracing the threshold range against the observed indicator value.

A straightforward query by threshold identifier uses the unique index:

  • SELECT THRESHOLD_ID, RULE_TYPE, THRES_OBJ_ID, FROM_VALUE, TO_VALUE, INDICATOR_CODE, EXCEPTION_FLAG FROM PA.PA_PERF_THRESHOLDS WHERE THRESHOLD_ID = :threshold_id;

To review all thresholds for a given performance rule or rule-object association, filter on THRES_OBJ_ID, optionally narrowing by RULE_TYPE and INDICATOR_CODE. Reporting extracts commonly join PA_PERF_THRESHOLDS to PA_PERF_RULES and PA_PERF_OBJECT_RULES on THRES_OBJ_ID to present readable rule names alongside the raw range values. Because FROM_VALUE and TO_VALUE are numeric, range-overlap validations and gap analyses for an indicator can be expressed directly in SQL.

Related Objects

Dependencies documented through the foreign-key relationship data establish the following principal associations:

  • PA.PA_PERF_RULES — referenced by PA_PERF_THRESHOLDS.THRES_OBJ_ID; supplies the performance rule definition when THRES_OBJ_ID points to a rule.
  • PA.PA_PERF_OBJECT_RULES — also referenced by THRES_OBJ_ID; supplies the rule-to-object association when the threshold is bound at the association level.
  • APPS.PA_PERF_THRESHOLDS — the APPS-layer synonym or view through which application code and reports reference the table.
  • Supporting indicators and access lists referenced through INDICATOR_CODE and ACCESS_LIST_ID (lookup and access-list based) are frequently joined for reporting readability.

No database objects are documented as being referenced solely by this table beyond these relationships; the APPS synonym remains the standard access path for external consumers.