Search Results pa_perf_thresholds_v




Overview
Explore in AI Chat

Overview

The view PA_PERF_THRESHOLDS_V is an Oracle E-Business Suite database object owned by the APPS schema and classified under the Projects (PA) product family. Its documented description is "10SC Only," indicating that its use is scoped to a specific localization or deployment context rather than the general Projects application flow. Despite this restriction, the object remains VALID in both Oracle EBS 12.1.1 and 12.2.2, and it is registered in the E-Business Suite Tables and Views Repository (ETRM) as a reporting view.

Functionally, the view exposes performance threshold configurations used by the Projects module. It joins the base performance threshold table to the lookup definitions that describe the associated performance indicator, thereby resolving the raw INDICATOR_CODE into a human-readable INDICATOR_NAME. This denormalized presentation makes the view suitable for reporting, integrations, and analytic queries where threshold rules must be displayed alongside their indicator descriptions without requiring the consumer to perform the lookup join manually.

Underlying Base Objects

The view is defined over two documented referenced base objects:

  • PA_PERF_THRESHOLDS (SYNONYM) — the primary threshold definition table, aliased as TH in the view text. It supplies threshold identifiers, rule types, value ranges, indictor codes, weighting, and audit columns.
  • PA_LOOKUPS (VIEW) — the lookup view, aliased as IND, filtered to LOOKUP_TYPE = 'PA_PERF_INDICATORS'. It supplies the MEANING column, exposed here as INDICATOR_NAME.

The join condition is IND.LOOKUP_CODE = TH.INDICATOR_CODE, restricted by the lookup type predicate. Because PA_LOOKUPS is itself a view over lookup data, the threshold view transitively depends on the lookup infrastructure maintained for the Projects product.

Key Columns

The view projects seventeen columns. The most significant include:

  • THRESHOLD_ID — unique identifier for the threshold definition; the primary key of the underlying table.
  • RULE_TYPE and THRES_OBJ_ID — classify the rule and identify the object against which the threshold is evaluated.
  • FROM_VALUE and TO_VALUE — define the numeric or comparable range bounds for the threshold.
  • INDICATOR_CODE — the lookup code keyed to PA_PERF_INDICATORS; this is the column most frequently referenced in searches, since it links a threshold to its performance indicator.
  • INDICATOR_NAME — the decoded meaning of the indicator code, derived from PA_LOOKUPS.MEANING.
  • EXCEPTION_FLAG and WEIGHTING — control how the threshold is treated during evaluation and scoring.
  • ACCESS_LIST_ID — associates the threshold with an access control list.
  • RECORD_VERSION_NUMBER, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit and concurrency columns.

Common Use Cases and Queries

Typical consumers use this view to report threshold rules by indicator, to validate configurations before deployment, and to drive integrations that require threshold metadata in a flat format. A representative query filtering by indicator code follows:

  • SELECT threshold_id, indicator_code, indicator_name, from_value, to_value, weighting FROM apps.pa_perf_thresholds_v WHERE indicator_code = :indicator_code;

To enumerate all configured thresholds with their decoded names:

  • SELECT indicator_code, indicator_name, rule_type, from_value, to_value FROM apps.pa_perf_thresholds_v ORDER BY indicator_code, from_value;

Because the view performs the lookup join internally, queries should filter on indexed columns such as THRESHOLD_ID or INDICATOR_CODE to avoid unnecessary scans. Given the "10SC Only" designation, implementers should confirm applicability against their specific rollout before relying on the view in production reporting.