Results for “fnd_currency”

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

Overview

FND_CURRENCY is a core Oracle E-Business Suite PL/SQL package body owned by the APPS schema. It encapsulates the display and formatting logic for currency values across the E-Business Suite, providing a single, centralized programmatic interface through which applications obtain currency-specific display characteristics such as the currency symbol, format masks, and descriptive attributes. Because multi-currency processing is pervasive in EBS — spanning General Ledger, Payables, Receivables, Purchasing, Order Management, and Payroll — the package serves as the foundation for presenting monetary amounts uniformly and consistently regardless of the responsibility, region, or ledger being used. The package body is documented with a status of VALID and is classified under the ETRM taxonomy as OTHER, indicating that it is a supporting utility package rather than a transactional or workflow API. Its existence reflects Oracle's design principle of isolating currency presentation metadata in a single reusable component, thereby preventing duplicated logic and ensuring that changes to currency formatting propagate automatically to every dependent module. The package body depends on the FND_CURRENCY specification, the FND_CURRENCIES table (accessed through an APPS synonym), FND_PROFILE, and the SYS.STANDARD package, which supplies the fundamental PL/SQL runtime constructs.

Key Procedures and Functions

The ETRM metadata documents five procedures and functions within the package body, each oriented toward producing or protecting currency format information.

• GET_FORMAT_MASK — The primary accessor that returns the formatting mask used to render a currency amount for display. Callers use this mask to apply consistent decimal precision, grouping, and symbol placement.
• SAFE_GET_FORMAT_MASK — A null-safe wrapper around GET_FORMAT_MASK. It shields calling code from runtime exceptions when currency or format information is missing or invalid, returning a controlled fallback rather than raising an error.
• BUILD_FORMAT_MASK — Constructs a format mask dynamically, deriving the mask components from currency attributes rather than retrieving a pre-existing value. This supports currencies or configurations for which no stored mask is readily available.
• SAFE_BUILD_FORMAT_MASK — The exception-tolerant counterpart to BUILD_FORMAT_MASK, ensuring that mask construction never terminates a calling process with an unhandled error.
• GET_INFO — A general-purpose retrieval routine that returns currency attribute information for a given currency, allowing callers to obtain descriptive data without querying FND_CURRENCIES directly.

No parameter lists are asserted here, as the ETRM metadata does not enumerate them.

Tables Accessed

The package reads the FND_CURRENCIES table, referenced through its APPS synonym. FND_CURRENCIES is the EBS repository of currency definitions and holds attributes such as the currency code, name, symbol, precision, and extended formatting information. FND_CURRENCY consults this table to resolve the format mask and descriptive details returned by its procedures and functions. The metadata gives no indication that the package performs inserts, updates, or deletes; it is a read-oriented utility. The package also references FND_PROFILE, indicating that profile option values may influence currency formatting behavior, for example through a user's or responsibility's default currency or reporting preferences.

Usage Notes

FND_CURRENCY is not referenced by any other database object according to the dependency information, yet the ETRM 12.2.2 record notes that the package is referenced by 352 other packages in the broader application schema, underscoring its role as a widely consumed currency formatting service. It is typically invoked from Oracle Forms-based business flows and concurrent programs whenever a monetary value must be formatted for display, and from custom PL/SQL code that needs to honor the same currency conventions as standard EBS screens. Developers should prefer the SAFE_ variants when writing code that must remain resilient to incomplete currency setup, and should avoid circumventing the package by querying FND_CURRENCIES directly, since doing so bypasses the centralized formatting logic and risks inconsistent presentation of amounts across the application.