Search Results pa_budget

Overview

APPS.PA_PERF_STATUS_CLIENT_EXTN is a public PL/SQL client extension package in Oracle Projects (PA) that provides a customization hook for the logic used to determine the overall performance status of a project. It is classified as an OTHER API under the Oracle E-Business Suite 12.1.1 and 12.2.2 releases and is documented in the Oracle Projects APIs, Client Extensions, and Open Interfaces Reference (doccd 120pjapi.pdf). The package header carries the version identifier PAPESCLS.pls 120.5, dated 2006/10/03, indicating its origins in earlier Projects releases and its continued lifecycle-active status in current EBS versions.

The package belongs to the PA_PERF_REPORTING business entity and is additionally categorized under the PA_PROJECT, PA_BUDGET, and PA_TASK business entities. Its purpose is to allow implementers to override the standard calculation of the aggregate performance status by supplying their own PL/SQL body for the extension function, without modifying Oracle-owned code. Because the extension is invoked by the performance status engine, any custom logic provided here directly affects the KPA (Key Performance Area) indicators surfaced through performance reporting and project status inquiries.

Key Procedures and Functions

The package documents a single public function:

• GET_PERFORMANCE_STATUS — Returns the overall performance status of a project as a VARCHAR2 value. The function is documented as the extension point used to customize the logic for deriving the overall performance status. It accepts the type of object being evaluated (PA_PROJECTS is the supported object type), the identifier of that object (PROJECT_ID is the supported identifier), and a list of Key Performance Area indicators supplied through the pa_exception_engine_pkg.summary_table collection type. All three parameters are marked as required in the parameter metadata. The return value is the computed overall performance status for the object.

The function is declared in the package specification only; no body implementation is shipped with the standard product. This is characteristic of a client extension package: Oracle supplies the signature, and the customer supplies the implementation. Implementations must preserve the exact signature to remain compatible with the calling code in the performance status engine.

Tables Accessed

The ETRM metadata lists a single referenced table via APPS synonyms: PLITBLM. PLITBLM is an Oracle Applications internal table commonly used in client extension and flexfield-related processing, and its presence here indicates that standard internal lookups or cached values may be read during the extension invocation path. The package does not document any direct write operations to project, budget, or task tables. Because this is a client extension, the actual set of tables read or written depends entirely on the custom implementation provided by the customer; Oracle does not constrain the implementation, but customary practice is to query project, budget, and KPA data read-only and return a derived status string.

Usage Notes

This package is typically invoked internally by Oracle Projects performance status processing rather than being called directly from forms or concurrent programs by end users. The calling framework passes the object type and object identifier together with the KPA summary collection, and expects a status string in return. The extension is relevant to the broad "pa_budget" search context because budget-related KPA indicators flow into the KPA summary collection that is passed to the function; implementers customizing performance status logic for budget-driven KPIs will frequently work within this package.

Because the package is referenced by one other standard package, changes to its implementation affect the performance status displayed in project performance reporting. Implementations should be registered and deployed as a normal APPS-owned package with the body supplied by the customer, and any regression testing should cover project status inquiry, performance reporting, and KPA dashboards to confirm that the custom status derivation behaves as intended.