Results for “gl_euro_user_rate_api”

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

Overview

APPS.GL_EURO_USER_RATE_API is a PL/SQL API owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its header identifies it as the "Euro User Rate API," created in May 1999 by D. J. Ogg during the original Economic and Monetary Union (EMU) transition. The package addresses a specific regulatory and functional requirement introduced by the euro: controlling whether users in the General Ledger application may directly enter foreign exchange rates between the euro (EMU) and other currencies.

The business purpose of the package, as stated in its source comments, is threefold. First, it determines whether a customer is permitted to enter EMU-to-OTHER and OTHER-to-EMU rates directly. Second, it detects when the current conversion type is "User," the customer is not permitted to enter those rates directly, and the conversion being attempted falls into that restricted situation. Third, it supplies the appropriate prompts for EURO-to-OTHER, OTHER-to-EURO, EURO-to-EMU, and EMU-to-OTHER conversions, together with the triangulated rate derived through EURO-to-EMU. Because EMU currencies were permanently fixed to the euro at defined conversion ratios, Oracle restricted direct user entry of rates between EMU and non-EMU currencies and instead required the system to derive those rates through triangulation. This package encapsulates that logic for other EBS modules.

Key Procedures and Functions

The package exposes four documented program units.

• ALLOW_DIRECT_ENTRY (function) — Returns 'Y' if the customer is allowed to directly enter EMU-to-OTHER and OTHER-to-EMU rates, and 'N' otherwise. It takes no arguments and serves as the capability check that governs whether direct rate entry is permissible in the current configuration.
• IS_CROSS_RATE (function) — Returns 'Y' when the current conversion type is User, the conversion is from EMU to OTHER or from OTHER to EMU, and direct entry of those rates is not allowed. Returns 'N' in all other cases. Its arguments are the from-currency, to-currency, conversion date, and conversion type, allowing the caller to evaluate a specific conversion scenario rather than just a global setting.
• GET_PROMPTS_AND_RATE (procedure) — Provides the prompts to be used for EURO-to-OTHER (or OTHER-to-EURO), EURO-to-EMU, and EMU-to-OTHER (or OTHER-to-EMU) conversions, along with the rate from EURO-to-EMU. This supports the rate-entry user interface by returning the correct field labels and the underlying fixed euro rate.
• GET_CROSS_RATE (function) — Retrieves the applicable cross rate for a conversion, consistent with the package's triangulation responsibilities.

The package also declares two user-defined exceptions, INVALID_CURRENCY (raised when one of the two currencies is invalid) and INVALID_RELATION, which callers are expected to handle when invoking these APIs.

Tables Accessed

The ETRM metadata does not document specific base tables referenced through APPS synonyms for this package. Functionally, the API depends on General Ledger currency and rate definitions—principally the FND_CURRENCIES and GL_DAILY_RATES (or GL_DAILY_CONVERSION_TYPES) structures—to evaluate currency validity, conversion types, and rate relationships. Where the metadata is silent, the package should be treated as reading currency and rate configuration rather than writing transactional data.

Usage Notes

The package is a standard APPS API and is referenced by three other packages within the EBS code set, indicating that it is consumed by Oracle's own currency and rate processing logic rather than being an end-user entry point. It is typically invoked from General Ledger rate-entry forms and from any custom or standard code that must determine whether a euro-related conversion may be entered directly or must be triangulated. Customizations should call ALLOW_DIRECT_ENTRY and IS_CROSS_RATE before presenting rate fields, and handle the INVALID_CURRENCY and INVALID_RELATION exceptions. The 12.2.2 release status confirms the API remains available, though its operational relevance is largely historical given the completion of the euro transition.