Search Results score_method

Overview

PA_PERF_OBJECT_RULES_V is an APPS-owned database view in the Oracle E-Business Suite Projects (PA) module. It is documented with the description "10SC Only," indicating it is a restricted or specialized object exposed for a specific business scope rather than for general use. The view joins performance rule definitions to the objects to which those rules are assigned, producing a denormalized, report-friendly projection of rule configuration and its object associations.

Functionally, the view answers the question "which performance rules are attached to which objects, and how is each rule scored?" Because it exposes descriptive attributes such as RULE_NAME, MEASURE_NAME, and SCORE_METHOD alongside the object linkage columns, it serves as a convenient read-only source for reporting, data extraction, and integration scenarios where consumers need combined rule-and-assignment information without writing their own join.

Underlying Base Objects

Per the documented ETRM metadata, PA_PERF_OBJECT_RULES_V is defined over two referenced base objects:

• PA_PERF_OBJECT_RULES (SYNONYM) — supplies the object-to-rule assignment, contributing OBJECT_RULE_ID, OBJECT_TYPE, OBJECT_ID, RULE_ID, and RECORD_VERSION_NUMBER.
• PA_PERF_RULES_V (VIEW) — supplies the rule definition attributes, including RULE_NAME, RULE_DESCRIPTION, RULE_TYPE, KPA_CODE, MEASURE_ID, MEASURE_FORMAT, CURRENCY_TYPE, PERIOD_TYPE, PRECISION, active dates, and SCORE_METHOD.

The view text confirms an inner join on the rule identifier: WHERE PO.RULE_ID = PR.RULE_ID. Consequently, only object-rule assignments whose RULE_ID resolves in PA_PERF_RULES_V are returned. Because one of the base objects is itself a view, the effective query depth extends further into the underlying rule tables.

Key Columns

• OBJECT_RULE_ID — Primary identifier for the object-to-rule assignment row.
• OBJECT_TYPE / OBJECT_ID — Identify the owning performance object to which the rule is attached.
• RULE_ID / RULE_NAME / RULE_DESCRIPTION — Identify and describe the performance rule.
• RULE_TYPE / RULE_TYPE_NAME / KPA_CODE / KPA_NAME — Classify the rule and its associated key performance area.
• MEASURE_ID / MEASURE_NAME / MEASURE_FORMAT — The measure the rule evaluates and its display format.
• CURRENCY_TYPE / PERIOD_TYPE / PRECISION — Define monetary handling, time periodicity, and numeric precision.
• SCORE_METHOD — The scoring algorithm or method applied when the rule is evaluated; this is the column most relevant to the "score_method" search.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Rule effective-dating bounds.
• RECORD_VERSION_NUMBER — Optimistic-locking version of the assignment record.
• CREATION_DATE / CREATED_BY / LAST_UPDATE_LOGIN / LAST_UPDATED_BY — Standard audit columns.

Common Use Cases and Queries

Typical uses include configuration auditing, migration validation, and reporting on how performance rules are scored per object.

• Listing objects scored by a given method: SELECT OBJECT_TYPE, OBJECT_ID, RULE_NAME, SCORE_METHOD FROM APPS.PA_PERF_OBJECT_RULES_V WHERE SCORE_METHOD = :p_method;
• Retrieving all rules for a specific object: SELECT * FROM APPS.PA_PERF_OBJECT_RULES_V WHERE OBJECT_TYPE = :type AND OBJECT_ID = :id;
• Reporting active rules by KPA: SELECT KPA_CODE, RULE_NAME, MEASURE_NAME, SCORE_METHOD, END_DATE_ACTIVE FROM APPS.PA_PERF_OBJECT_RULES_V WHERE TRUNC(SYSDATE) BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE);

Because the object is flagged "10SC Only," consumers should treat it as scope-restricted and confirm availability and row visibility against their specific environment before relying on it in production extractions.