Search Results pa_perf_rules_pub




Overview
Explore in AI Chat

Overview

PA_PERF_RULES_PUB is an APPS-owned public PL/SQL package in Oracle EBS that provides the programmatic interface for maintaining performance rules used by Oracle Projects. Performance rules define how project key performance indicators (KPIs) are measured, formatted, scored, and made active over a defined date range. The package encapsulates the business logic and validation required to create, modify, and remove these rule definitions within the PA_PERF_RULES table, shielding callers from direct DML against the underlying schema objects.

The package is classified as a public API (PUB), meaning it is intended for supported invocation by external Oracle EBS components and customer extensions. The version header (PAPERLPS.pls 120.1) identifies it as a long-standing, stable interface that has been part of the Projects performance management subsystem across releases.

Key Procedures and Functions

The ETRM metadata documents four procedures exposed by this package:

  • CREATE_RULE — Inserts a new row into the pa_perf_rules table, populating the rule identifier, name, description, rule type, KPI/KPA code, measure definition, formatting attributes, scoring method, active date range, and standard WHO audit columns. It returns a standard API status payload (return status, message count, and message data) to communicate success or failure.
  • UPDATE_RULE — Updates an existing performance rule row, accepting the same rule attributes as CREATE_RULE together with the record version number to support optimistic locking and the last-update audit columns.
  • DELETE_RULE — Removes a performance rule definition from the table, subject to the package's internal validation of referential and state constraints.
  • VALIDATE_RULE — Performs rule-level validation without committing data. This procedure is commonly invoked prior to create or update to confirm that supplied rule attributes are complete and internally consistent; it is the procedure most frequently searched as validate_rule.

Tables Accessed

The primary table accessed is PA_PERF_RULES, referenced through an APPS synonym. CREATE_RULE and UPDATE_RULE perform inserts and updates respectively against this table, while DELETE_RULE removes rows from it. VALIDATE_RULE reads the table to check existing state and uniqueness as part of its validation logic.

The package also relies on FND_GLOBAL to derive default audit values, including FND_GLOBAL.USER_ID and FND_GLOBAL.LOGIN_ID, which populate the CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN columns. The ETRM metadata lists no additional referenced tables and records no other packages referencing this one, confirming that PA_PERF_RULES_PUB sits at the top of the dependency chain for performance rule maintenance.

Usage Notes

PA_PERF_RULES_PUB is typically invoked from the Oracle Projects forms that maintain KPI performance rules, from concurrent programs that seed or migrate performance rule data, and from custom PL/SQL extensions that must programmatically configure rules during implementation or data conversion. Because it is a published API, customers and integrators should call these procedures rather than issuing direct DML against PA_PERF_RULES, thereby ensuring that validation and audit column population occur correctly.

Callers should inspect the returned X_RETURN_STATUS, X_MSG_COUNT, and X_MSG_DATA values using standard EBS API error-handling patterns. For routine diagnostics of rule definitions, VALIDATE_RULE provides a non-destructive check before committing changes through CREATE_RULE or UPDATE_RULE.