Search Results pa_client_extn_burden_summary




Overview
Explore in AI Chat

Overview

PA_CLIENT_EXTN_BURDEN_SUMMARY is an Oracle EBS Applications (APPS) PL/SQL package body residing in the APPS schema. Within the Oracle Projects (PA) module it functions as a client extension point for burden summarization logic applied to project cost and expenditure data. In Oracle Projects terminology a "burden" is an indirect cost applied on top of raw expenditure — for example overhead, fringe, or general and administrative cost — that is computed by a burden schedule and distributed across expenditure items and cost distribution lines. The naming convention used here ("CLIENT_EXTN") identifies the package as part of the client extension framework, meaning it exists to expose a supported customization hook rather than to implement Oracle's core, sealed burden processing. Its API classification in ETRM is OTHER, and it is not referenced by any other database object, confirming it sits at the outer edge of the dependency tree as an exit point that Oracle's delivered code expects a customer or partner to implement or optionally extend. The package is recorded as VALID in both 12.1.1 and 12.2.2, and the documented metadata is specific to release 12.2.2.

Key Procedures and Functions

Three documented procedures and functions constitute the public surface of this package. Client_Grouping defines how expenditure records are grouped into the logical buckets that burden summary reporting or processing will use; it allows the grouping key to be adjusted for customer-specific reporting hierarchies instead of relying on Oracle's default grouping. Client_Column_Values supplies the values that populate client-defined columns in the burden summary output, enabling additional descriptive or analytical attributes to be carried through alongside the standard summarized amounts. Same_Line_Burden_CMT addresses same-line burden handling in the context of cost management transactions (CMT), where burden is expected to be tracked on the same expenditure line rather than redistributed. The exact parameter lists are not documented in the ETRM extract; Oracle's published client extension documentation should be consulted before implementing or overriding any of these entry points.

Tables Accessed

The package reads from three core Oracle Projects tables, accessed through APPS synonyms. PA_EXPENDITURE_ITEMS_ALL holds the individual expenditure items — the atomic transactions charged to a project — and provides the raw amounts, quantities, and item attributes that form the basis of burden calculation. PA_EXPENDITURE_TYPES defines the expenditure type classifications (for example, straight time, overtime, or expense) that determine which burden schedule and burden cost codes apply. PA_COST_DISTRIBUTION_LINES_ALL stores the distribution of expenditure amounts across cost and accounting lines, and is the table where burdened cost amounts and their associated accounted entries are persisted. Reading across these three tables allows the extension logic to join expenditure detail to expenditure type definition and cost distribution results, producing a burden summary aligned to the client's grouping and column requirements.

Usage Notes

Because the package is not referenced by any other database object, it is not invoked automatically by Oracle's delivered burden processing; instead it is executed by the calling framework through the client extension mechanism, typically during burden summarization, cost distribution, or reporting flows configured for the installation. It is registered as a client extension and therefore is invoked from Oracle Projects concurrent programs, from Oracle Projects forms that trigger burden processing, or from custom PL/SQL that follows the documented client extension contract. The package depends on GMS_PA_API3, PA_INSTALL, and STANDARD, with four dependent packages reported in ETRM. Implementations should treat it as a supported customization point, preserve the documented signatures, and validate changes in a non-production environment before deploying to 12.1.1 or 12.2.2.