Search Results pa_perf_object_rules_pk

Overview

PA_PERF_OBJECT_RULES is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the association between an Exception Rule and the actual project object against which that rule is evaluated. In the Oracle Projects performance and exception framework, rules are defined generically in PA_PERF_RULES, and this table materializes the linkage of a given rule to a specific object, such as a project or project-related identifier. Each row therefore represents one concrete rule-to-object binding that drives exception checking, threshold evaluation, and resulting transaction generation.

Within the documented foreign key topology, the table behaves as a satellite-leaning structure. It carries descriptive and contextual attributes tied to the rule and object entities rather than serving as a pure intersection or a standalone hub. The heuristic Data Vault classification is satellite-leaning, suggesting it is best modeled as a dependent entity keyed by its own surrogate identifier while capturing the state of a rule-object association. The primary key is enforced by PA_PERF_OBJECT_RULES_PK on OBJECT_RULE_ID, which is the surrogate key referenced by downstream tables.

Key Information Stored

The documented physical schema contains ten columns. The most significant are described below, distinguishing the surrogate primary key from business-key candidates.

• OBJECT_RULE_ID — Surrogate primary key (PA_PERF_OBJECT_RULES_PK). It uniquely identifies each rule-to-object association and is the column referenced by dependent tables.
• OBJECT_TYPE — Classifies the object being associated with the exception rule. Along with OBJECT_ID and RULE_ID, it forms unique index PA_PERF_OBJECT_RULES_U2, a business-key candidate preventing duplicate associations.
• OBJECT_ID — The identifier of the actual object, with a foreign key to PA_PROJECTS_ALL. This is the core business reference linking the rule to a specific project object.
• RULE_ID — Foreign key to PA_PERF_RULES, identifying the exception rule being applied.
• PPL_PROJECT_ID — An additional foreign key to PA_PROJECTS_ALL, supporting project-level context where the association is governed at project level.
• RECORD_VERSION_NUMBER — Optimistic locking / versioning column used to detect concurrent updates to the association row.
• CREATION_DATE, CREATED_BY — Standard WHO audit columns recording row creation metadata.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns recording the most recent modification and the login context.

The unique index PA_PERF_OBJECT_RULES_U2 on (OBJECT_TYPE, OBJECT_ID, RULE_ID) is the critical business-key constraint, ensuring a rule is associated only once per object.

Common Use Cases and Queries

Typical use cases include reporting which exception rules apply to which projects, tracing how thresholds and performance transactions are generated, and auditing rule coverage across a project portfolio. A frequent query joins the table to PA_PERF_RULES and PA_PROJECTS_ALL to resolve rule names and project numbers.

• Listing active rule-object associations: SELECT por.object_rule_id, por.object_type, por.object_id, por.rule_id FROM pa_perf_object_rules por WHERE por.object_id = :project_id;
• Resolving the rule definition for a binding: SELECT pr.rule_id, pr.rule_name FROM pa_perf_object_rules por, pa_perf_rules pr WHERE por.rule_id = pr.rule_id AND por.object_rule_id = :object_rule_id;
• Tracing dependent transactions: SELECT pt.* FROM pa_perf_transactions pt WHERE pt.object_rule_id = :object_rule_id;
• Tracing thresholds: SELECT pth.* FROM pa_perf_thresholds pth WHERE pth.thres_obj_id = :object_rule_id;

These patterns support exception analysis, rule maintenance, and reconciliation of generated threshold and transaction records back to their originating associations.

Related Objects

The following objects are most significant to PA_PERF_OBJECT_RULES, based on the documented foreign key relationships.

• PA_PERF_RULES — Referenced via RULE_ID; defines the exception rule applied to the object.
• PA_PROJECTS_ALL — Referenced via OBJECT_ID; the primary project object associated with the rule.
• PA_PROJECTS_ALL — Referenced again via PPL_PROJECT_ID; provides project-level linkage context.
• PA_PERF_THRESHOLDS — References this table through THRES_OBJ_ID, storing threshold values bound to the rule-object association.
• PA_PERF_TRANSACTIONS — References this table through OBJECT_RULE_ID, storing generated performance/exception transactions produced by the association.

Together these objects form the performance exception rule chain: rule definitions, their object bindings, the thresholds evaluated, and the transactions produced.