Results for “pa_multi_currency_txn”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_MULTI_CURRENCY_TXN is an Oracle Applications (APPS) PL/SQL package within the Oracle E-Business Suite Projects (PA) module. Its role is to centralize multi-currency and inter-company transaction processing logic for project expenditure, enabling the conversion, derivation, and validation of currency-related attributes that arise when organizations record, accumulate, and transfer project costs across multiple currencies and operating units.

The package resolves the complex decisions that surround currency handling in project accounting: which project or project function rate type applies, which effective rate date should be used, and how the resulting currency amounts should be derived and returned to the calling process. By encapsulating these rules, it provides a consistent currency calculation engine shared across numerous project accounting processes, including cost distribution, cost adjustments, cross-charge transfer pricing, transaction import, planning, and progress analysis. In releases 12.1.1 and 12.2.2, the package is documented as VALID in the APPS schema and is classified under the ETRM "OTHER" API category, indicating it is an internal, callable utility rather than a released public API.

Key Procedures and Functions

The documented interface exposes twelve procedures and functions, grouped into rate-type resolution, rate-date resolution, currency attribute retrieval, and processing routines:

• GET_PROJFUNC_COST_RATE_TYPE and GET_DEF_PROJFUNC_CST_RATE_TYPE — return the project function cost rate type, and its default value, governing which exchange rate type applies to project cost conversions.
• GET_PROJ_RATE_TYPE and GET_PROJ_CURR_CODE_SQL — return the project-level rate type and the SQL construct used to resolve the project currency code.
• GET_PROJFUNC_COST_RATE_DATE, GET_DEF_PROJFUNC_CST_RATE_DATE, GET_ACCT_RATE_DATE, and GET_DEFAULT_ACCT_RATE_DATE — determine the effective dates on which exchange rates are applied for project function and accounting conversions, along with their defaults.
• GET_PROJ_RATE_DATE — returns the project-level rate date used in currency conversion.
• GET_CURRENCY_AMOUNTS and GET_CURRENCY_ATTRIBUTES — derive and return converted currency amounts and the associated currency attributes for a transaction.
• PERFORM_MC_AND_IC_PROCESSING — performs the combined multi-currency and inter-company processing for the supplied transaction context.

All routines act as reusable currency rule resolution services; their detailed signatures are intentionally not documented here.

Tables Accessed

The package references project accounting tables through APPS synonyms, including PA_PROJECTS_ALL and PA_TASKS for project and task currency definitions; PA_EXPENDITURE_ITEMS_ALL, PA_EXPENDITURES, and PA_EXPENDITURE_ITEMS for cost transaction and item detail; PA_TRANSACTION_SOURCES for transaction source configuration; PA_CC_DIST_LINES_ALL for cross-charge distribution lines; and PA_IMPLEMENTATIONS and PA_IMPLEMENTATIONS_ALL for installation-level currency and functional settings. PLITBLM is a PL/SQL table used for bulk collection handling. Read operations dominate, retrieving rate-type, rate-date, and currency attributes that drive downstream monetary derivation.

Usage Notes

PA_MULTI_CURRENCY_TXN is an internal dependency rather than an end-user entry point. It is referenced by eighteen other packages, including PA_MULTI_CURRENCY, PA_ADJUSTMENTS, PA_COST, PA_TXN_ACCUMS, PA_TRX_IMPORT, PA_CE_INTEGRATION, PA_CC_TRANSFER_PRICE, PA_FIN_PLAN_UTILS2, PA_FP_CALC_PLAN_PKG, PA_PLANNING_RESOURCE_UTILS, PA_PROGRESS_UTILS, and the PAAP_PWP_PKG and PA_PAXINGEN_XMLP_PKG report-level packages.

Invocations therefore originate from concurrent programs, project accounting forms, transaction import and cross-charge processes, and custom extensions that must reproduce standard currency behavior. When extending project cost or cross-charge logic in 12.1.1 or 12.2.2, custom code should call these routines rather than reimplementing rate-type and rate-date derivation, ensuring consistent multi-currency and inter-company treatment.