Search Results pa_client_extn_costing

Overview

PA_CLIENT_EXTN_COSTING is a client extension package in Oracle Project Accounting (PA). It is designed as a customer-modifiable hook that Oracle E-Business Suite exposes so that implementers can override or supplement the standard raw cost calculation logic that Project Accounting applies to expenditure items. The package body shipped by Oracle contains only skeletal, empty logic (the shipped source consistently uses null; placeholders), which signals that the body is intended for site-specific customization rather than out-of-the-box execution.

In Oracle EBS 12.1.1 and 12.2.2, the package is owned by APPS and is classified in the ETRM metadata as a generic extension API ("OTHER"). Its central purpose is to let customers compute the raw cost amount and the associated denominated currency for an expenditure item when the delivered cost derivation rules do not satisfy a particular business requirement. Because the package is part of the extensibility surface, Oracle retains the signature and rebuilds the object on patching; customer logic is expected to be re-applied through the supported customization mechanisms.

Key Procedures and Functions

The package exposes a single documented procedure, CALC_RAW_COST. Its role is to return the calculated raw cost for a given expenditure item, along with the currency in which that cost is denominated and a status indicator. The procedure accepts an input describing the transaction type (for example, actual versus forecast), an expenditure item identifier, and a system linkage function that distinguishes categories such as straight time and overtime. Its output parameters carry the raw cost amount, the denominated currency code, and a status code. The status parameter is initialized to zero on entry to indicate success, and the procedure is documented to signal application errors by assigning a positive number to the status or to return an Oracle error by assigning SQLCODE.

The shipped body initializes the output parameters to NULL and zero, then branches on transaction type. Within actual transactions, the code separates straight time from overtime handling, and a further branch covers forecast transactions. All branches are placeholders, confirming that the delivered procedure performs no calculation on its own. The package contains no functions and no additional documented procedures; CALC_RAW_COST is the sole entry point of the extension.

Tables Accessed

The metadata records a single table reference: PA_EXPENDITURE_ITEMS, accessed through an APPS synonym. This is the core Project Accounting table that stores expenditure items, including the raw cost and denominated currency columns whose data types are referenced by the procedure's output parameters. The reference is primarily a data-typing and contextual association — the shipped procedure itself performs no DML — but any customer implementation of CALC_RAW_COST is expected to read or write the expenditure item record to derive and store the raw cost and currency values.

Usage Notes

CALC_RAW_COST is not intended to be called directly by end users or by arbitrary custom code. It is invoked by the standard Project Accounting cost processing flows when they delegate raw cost derivation to the client extension. Because it is referenced by another package, the calling framework supplies the transaction type, expenditure item identifier, and system linkage function, then consumes the returned cost, currency, and status values.

Implementers customizing this package must observe several constraints documented in the source. They must not issue COMMIT or ROLLBACK, since Project Accounting controls the transaction boundary. Any exception handler should set the status output appropriately rather than raise unhandled errors. Because the object resides in APPS and is patched by Oracle, customizations must be preserved through the approved extension and version-control process. Typical triggering occurs during expenditure item cost processing and forecasting, and the procedure effectively serves as a plug-in point for organizations whose raw cost rules differ from the delivered behavior.