Search Results convert_txn_currency

Overview

The APPS.PA_FP_MULTI_CURRENCY_PKG package body is a core component of the Oracle Project Budgeting and Forecasting (FP) multi-currency architecture in Oracle E-Business Suite 12.1.1 and 12.2.2. Its principal business function is to manage currency conversion, currency resolution, and monetary rounding for project budget and forecast transactions across multiple currencies. Within the Project Management module, budgets and forecasts may be entered in one currency while residing in a project functional currency, so a dedicated package is required to reconcile these values consistently during generation, rollup, and interfacing operations.

The package body status is VALID and it is owned by the APPS schema. It is classified as an OTHER API by ETRM, and it is referenced by 19 other database objects, confirming its role as a foundational utility within the forecast and budget subsystem. Although it is not directly referenced by any other database object in the dependency listing, the reverse-dependency count indicates wide consumption by dependent PL/SQL programs.

Key Procedures and Functions

The package body exposes five documented procedures and functions:

• CONV_MC_BULK — Performs bulk multi-currency conversion, processing sets of transaction or budget amounts in a single invocation. It leverages Oracle database collection types (such as PLITBLM, PA_NUM_TBL_TYPE, and PA_VARCHAR2_30_TBL_TYPE) to convert many rows efficiently, supporting scalable budget and forecast processing.
• CONVERT_TXN_CURRENCY — Converts transaction currency amounts into the applicable project or budget currency. It is invoked where individual currency conversion of forecast or budget transaction values is required.
• ROUND_BUDGET_LINE_AMOUNTS — Applies currency-appropriate rounding rules to budget line amounts. Correct rounding is essential so that budget line totals remain internally consistent and reconcile with converted values.
• GET_FP_CUR_DETAILS — Retrieves forecast and budget currency detail information, resolving which currencies apply to a given project, budget version, or transaction context.
• ROUND_AMOUNTS — Provides a general monetary rounding utility used across the package's conversion and budget processing logic.

Tables Accessed

The package references the following tables via APPS synonyms:

• PA_BUDGET_LINES and PA_BUDGET_VERSIONS — Read and updated to obtain and store budget amounts and version currency attributes.
• PA_PROJECTS_ALL — Supplies project-level currency and organizational context.
• PA_PROJ_FP_OPTIONS — Provides forecast and budget option settings that determine currency handling behavior.
• PA_FP_ROLLUP_TMP — A temporary working area used during rollup of forecast and budget amounts.
• PA_FP_TXN_CURRENCIES — Defines transaction currency associations for forecast and budget processing.
• PA_PROJ_ELEMENTS, PA_RESOURCE_ASSIGNMENTS, and PA_RESOURCE_LIST_MEMBERS — Supply project element and resource context for mapping amounts to the correct currency and rounding treatment.
• PLITBLM — A PL/SQL index-by table of numbers used as a bulk collection container.

Additional dependencies include GL_CURRENCY_API and PA_MULTI_CURRENCY for currency conversion and rate resolution, FND_API, FND_MESSAGE, and FND_MSG_PUB for API result handling and message publication, FND_PROFILE for profile option retrieval, and PA_UTILS, PA_INTERFACE_UTILS_PUB, PA_DEBUG, and PA_PLSQL_DATATYPES for shared utilities and diagnostic logging.

Usage Notes

PA_FP_MULTI_CURRENCY_PKG is typically invoked indirectly rather than directly by end users. It is called by budget and forecast generation, rollup, and interface processes, including concurrent programs that create or transfer project budgets and forecasts, and by the forms and PL/SQL packages that manage budget entry and revision. Because it is referenced by 19 other packages, customizations that adjust budget or forecast currency behavior should call the documented procedures rather than replicate conversion or rounding logic. As with all EBS APIs, callers should honor standard API conventions: check return status, handle FND_MSG_PUB messages, and avoid direct DML against the underlying PA budget tables where this package's routines are the supported path.