Search Results pa_perf_object_rules_u2

Overview

PA.PA_PERF_OBJECT_RULES is a transactional table in the Oracle E-Business Suite Projects (PA) schema that stores the association between an Exception Rule and a specific business object instance. In the Oracle Projects performance and exception framework, rules defined in PA_PERF_RULES are generic definitions, while PA_PERF_OBJECT_RULES binds each rule to a concrete object — such as a project — so that rule evaluation is scoped to that object. The ETRM metadata documents this table as VALID in release 12.1.1 and 12.2.2, owned by PA, with FND Design Data reference PA.PA_PERF_OBJECT_RULES, and stored in the APPS_TS_TX_DATA tablespace with PCTFREE 10.

The heuristic Data Vault classification for this object is satellite-leaning. That is a modeling suggestion rather than a physical characteristic: the table behaves as a dependent attribute store attached to the parent rule and project hubs, carrying relationship context (object type, object identifier, rule identifier) plus descriptive and Who columns, rather than acting as an independent hub of business entities. The association is enforced by foreign keys to PA_PERF_RULES and PA_PROJECTS_ALL, and the table is itself referenced by PA_PERF_THRESHOLDS and PA_PERF_TRANSACTIONS.

Key Information Stored

The primary key is OBJECT_RULE_ID, a NUMBER(15) surrogate identifier. Two unique indexes act as documented business-key candidates:

• PA_PERF_OBJECT_RULES_U1 — unique on OBJECT_RULE_ID, the surrogate primary key.
• PA_PERF_OBJECT_RULES_U2 — unique on the combination OBJECT_TYPE, OBJECT_ID, RULE_ID. This is the natural business key: it guarantees that a given rule is bound to a given object only once. Because the user searched for pa_perf_object_rules_u2, this index is the most operationally significant constraint on the table; duplicate-insert errors raised against it indicate an attempt to associate the same rule with the same object twice.
• PA_PERF_OBJECT_RULES_N1 — non-unique on RULE_ID, supporting rule-driven lookups.

Priority columns include:

• OBJECT_TYPE (VARCHAR2(30)) — the type of object the rule is associated with.
• OBJECT_ID (NUMBER(15)) — the identifier of the associated object; the FK documents it as referencing PA_PROJECTS_ALL.
• RULE_ID (NUMBER(15)) — the associated exception rule, referencing PA_PERF_RULES.
• PPL_PROJECT_ID — an additional project reference documented in the FK relationship data.
• RECORD_VERSION_NUMBER (NUMBER(15)) — optimistic locking counter used by self-service applications.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard Who columns for audit and concurrency.

Common Use Cases and Queries

Typical uses include determining which rules apply to a project, listing projects governed by a rule, and auditing rule-to-object bindings. A rule-to-object lookup joins both rule and project:

• SELECT por.OBJECT_RULE_ID, por.OBJECT_TYPE, por.OBJECT_ID, pr.RULE_NAME FROM PA.PA_PERF_OBJECT_RULES por, PA.PA_PERF_RULES pr WHERE por.RULE_ID = pr.RULE_ID AND por.OBJECT_ID = :project_id;
• Rule-centric reporting leverages PA_PERF_OBJECT_RULES_N1 by filtering WHERE RULE_ID = :rule_id.
• Diagnosing the PA_PERF_OBJECT_RULES_U2 constraint: query for duplicate business keys before insert, e.g. SELECT COUNT(*) FROM PA.PA_PERF_OBJECT_RULES WHERE OBJECT_TYPE = :type AND OBJECT_ID = :object_id AND RULE_ID = :rule_id;
• Threshold and transaction drill-down joins child tables on OBJECT_RULE_ID to reconstruct the full rule evaluation context.

Related Objects

• PA.PA_PERF_RULES — parent rule definition, joined via RULE_ID.
• PA.PA_PROJECTS_ALL — project master, joined via OBJECT_ID (and PPL_PROJECT_ID).
• PA.PA_PERF_THRESHOLDS — threshold definitions referencing this table through THRES_OBJ_ID.
• PA.PA_PERF_TRANSACTIONS — transaction rows referencing this table through OBJECT_RULE_ID.
• PA.PA_PERF_OBJECT_RULES# — the underlying base object referenced by the table.

Together these objects form the performance rule framework: PA_PERF_RULES supplies definitions, PA_PERF_OBJECT_RULES scopes them to projects, and PA_PERF_THRESHOLDS and PA_PERF_TRANSACTIONS record evaluation outcomes tied back to the association identifier.