Search Results get_global_currency_rate




Overview

POA_CURRENCY_PKG is an Oracle E-Business Suite (EBS) PL/SQL package owned by the APPS schema and classified under the ETRM "OTHER" API category. Its primary business function is to centralize the resolution of currency codes and exchange rates used throughout the Procurement and Oracle Advanced Procurement (POA) product family, including Purchasing, iProcurement, and related sourcing modules. Rather than requiring each form, report, or concurrent program to re-derive the global (functional/ledger) currency and its associated conversion rate, this package exposes a consistent set of server-side functions. In EBS 12.1.1 and 12.2.2, this consistency is essential for multi-organization, multi-currency deployments where each operating unit may be associated with a different ledger and functional currency. The package also supports Oracle's Secondary Global Currency feature, introduced for environments that maintain a secondary reporting currency in addition to their primary functional currency. Functions are declared with the PRAGMA RESTRICT_REFERENCES (WNDS) directive, marking them as write-free and therefore safe for use in SQL statements, PL/SQL expressions, and function-based indexes.

Key Procedures and Functions

  • GET_GLOBAL_CURRENCY — Returns the global (functional) currency code applicable to the current session or context.
  • GET_GLOBAL_RATE — Returns the exchange rate for a given transaction currency, exchange date, and optional exchange rate type against the global currency.
  • GET_GLOBAL_CURRENCY_RATE — This is the function most often targeted by the search term "get_global_currency_rate." It accepts a rate type, currency code, rate date, and an inbound rate value, and returns the resolved global currency rate. It is commonly used to convert an already-known rate into the global currency basis. It carries the WNDS restriction, permitting its use directly in SQL.
  • GET_DISPLAY_CURRENCY — Returns the currency code that should be displayed to the user, based on the supplied currency code, the selected operating unit, and a global currency type parameter (with 'P' as the default for Primary). The global currency type argument was added specifically to distinguish Primary versus Secondary Global Currency behavior.
  • GET_DBI_GLOBAL_RATE — Returns the global currency rate for Data Build/BI (DBI) processing. It is declared with PARALLEL_ENABLE, enabling its use in parallel DML and parallel query operations, which is characteristic of Oracle Business Intelligence and Daily Business Intelligence extract workloads.
  • GET_DBI_SGLOBAL_RATE — The secondary-global-currency counterpart to GET_DBI_GLOBAL_RATE, similarly declared PARALLEL_ENABLE for BI extract scenarios.
  • GET_SECONDARY_GLOBAL_CURRENCY — Returns the secondary global currency code for the current context.
  • DISPLAY_SECONDARY_CURRENCY_YN — A Boolean function indicating whether secondary currency amounts should be displayed to the user.

Tables Accessed

The package references three documented objects through APPS synonyms. FINANCIALS_SYSTEM_PARAMS_ALL supplies the system-level financial configuration, including the global (functional) currency and related rate-type defaults that drive the resolution logic. PER_ORGANIZATION_LIST is used to relate the selected operating unit to its owning organization and ledger context, which is required for GET_DISPLAY_CURRENCY and the operating-unit-aware functions. DUAL is queried for scalar selections and default handling. No direct DDL or write operations are implied; the package is read-only in nature, consistent with its WNDS restriction pragmas.

Usage Notes

The package is referenced by seven other packages within the APPS schema, indicating it is a shared utility rather than an end-user entry point. It is typically invoked from Procurement forms and OA Framework pages to render converted amounts, from concurrent programs and DBI/BI extracts to compute reporting currency values, and from custom PL/SQL code that must reproduce EBS standard currency behavior. Because the WNDS pragmas are present, GET_GLOBAL_RATE, GET_GLOBAL_CURRENCY_RATE, GET_DBI_GLOBAL_RATE, and GET_DBI_SGLOBAL_RATE can be embedded in SQL SELECT statements and used within function-based indexes. Customizations referencing this package should be validated against both 12.1.1 and 12.2.2, since the secondary global currency support represented by the type parameter and the two secondary-currency functions is a later enhancement.