Search Results compare_currency_codes

Overview

The APPS.FII_CURRENCY package body is a currency conversion and rate utility within the Oracle E-Business Suite Financials Intelligence (FII) product family. It provides the underlying PL/SQL implementation for retrieving exchange rates, computing monetary asset unit (MAU) values, and converting amounts between functional, global, and transactional currencies. Because the package is a body, its specification defines the public interface, while the body encapsulates the conversion logic that other EBS components call at runtime.

In Oracle EBS 12.1.1 and 12.2.2, the package supports multi-currency reporting and global consolidation scenarios where amounts must be restated from a transactional or foreign currency into a primary or secondary global currency. This is consistent with the FII architecture, which relies on standardized currency translation for financial analysis. The package is classified as a custom "OTHER" API and holds a VALID status in the APPS schema.

Key Procedures and Functions

The package exposes twelve documented procedures and functions, organized into logical groups:

• GET_GLOBAL_RATE_PRIMARY and GET_GLOBAL_RATE_SECONDARY — return global exchange rates for the primary and secondary global currency perspectives.
• CONVERT_GLOBAL_AMT_PRIMARY and CONVERT_GLOBAL_AMT_SECONDARY — convert an input amount into the primary or secondary global currency.
• GET_MAU_PRIMARY and GET_MAU_SECONDARY — retrieve the monetary asset unit value for the primary and secondary global currency contexts.
• GET_RATE — a general-purpose rate retrieval routine used across the conversion functions.
• COMPARE_CURRENCY_CODES — compares two currency codes, supporting validation and equality checks during conversion logic.
• GET_FC_TO_PGC_RATE and GET_FC_TO_SGC_RATE — return the rate from a foreign currency (FC) to the primary global currency (PGC) or secondary global currency (SGC).
• GET_TC_TO_PGC_RATE and GET_TC_TO_SGC_RATE — return the rate from a transactional currency (TC) to the primary or secondary global currency.

Together these routines form a layered conversion API: conversion-procedure callers obtain rates through the GET_* functions, which in turn resolve the specific currency pair through the foreign/transactional-to-global rate helpers.

Tables Accessed

The package references the following objects via APPS synonyms:

• GL_CURRENCIES — the General Ledger currency definitions table, used to validate currency codes and retrieve currency attributes such as precision and currency type.
• PLITBLM — a PL/SQL table type used internally, likely as a lookup or mapping structure within the conversion logic.
• FII_CURRENCY — the package references itself, which may reflect recursive or overloaded calls within the package body.
• BIS_COMMON_PARAMETERS — read for shared configuration parameters governing currency and conversion behavior.
• FND_PROFILE — accessed to retrieve profile option values that influence rate selection and global currency settings.
• GL_CURRENCY_API — the General Ledger currency API, invoked to obtain authoritative conversion rates.

Standard dependencies include DBMS_STANDARD, STANDARD, and SYS built-ins for PL/SQL runtime support.

Usage Notes

FII_CURRENCY is referenced by 41 other database objects, indicating that it acts as a shared utility layer for currency conversion across the FII and adjacent financial modules. Typical invocation points include:

• Forms and OAF pages that display multi-currency balances requiring restatement into a global currency.
• Concurrent programs and batch processes that consolidate financial data across ledgers and currencies.
• Custom code and reporting scripts that need foreign-currency or transactional-currency to global-currency conversions.

Because it is a body-only implementation with no listing of callers within the metadata, integrators should obtain rates through the documented GET_* and CONVERT_* entry points rather than replicating conversion arithmetic. Profile options and BIS_COMMON_PARAMETERS settings should be verified before relying on global currency results, as these influence the primary and secondary global currency contexts. The package is not referenced by any object according to the dependency extract, so its dependents rely exclusively on the package interface for conversion services.