Results for “arpcurr”

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

Overview

ARPCURR is a core currency-handling PL/SQL package owned by the APPS schema in Oracle E-Business Suite, shipped as part of the Oracle Receivables (AR) product. Its primary business function is to centralize currency conversion, rounding, and rate-resolution logic for the Receivables application, ensuring consistent monetary arithmetic across receipts, transactions, and reconciliations. The package derives its functional currency context from FND_CURRENCIES and determines the ledger's functional currency from the set of books, allowing all downstream calculations to reference a single authoritative source. Because the source header dates to the 12.1.x code line (ARPLCURS.pls 120.4.12010000.1), the package is present in both 12.1.1 and 12.2.2, though in 12.2.2 the set-of-books identifier resolves through the subledger accounting/ledger architecture rather than the legacy chart of accounts model. The package also maintains internal PL/SQL index-by-table caches for segment and conversion-type lookups, which reduces repeated queries against GL_DAILY_CONVERSION_TYPES during high-volume batch processing.

Key Procedures and Functions

• CURRROUND — Rounds a supplied amount to the precision appropriate for a given currency, defaulting to the session's functional currency.
• RECONCILEACCTDAMOUNTS — Reconciles a child amount and its accounted amount against parent reconciliation amounts, maintaining running totals to keep distributed or matched amounts in balance.
• GETCURRENCYDETAILS — Returns the precision and minimum accounting unit for a currency, supplying the numeric tolerances used by rounding and validation routines.
• FUNCTIONAL_AMOUNT — Converts a transaction amount into the functional currency using a supplied exchange rate, precision, and minimum accounting unit.
• GETFUNCTCURR — Resolves and returns the functional currency code for a given set of books identifier.
• GETCONVTYPE — Normalizes or returns the effective conversion type for a specified conversion type input.
• GETRATE — Retrieves the exchange rate between a from-currency and to-currency for a conversion date and conversion type.
• RATEEXISTS — Determines whether a valid conversion rate exists for a set of books, currency pair, date, and conversion type.
• ISFIXEDRATE — Indicates whether a receipt or transaction currency relationship is governed by a fixed rate, optionally considering transaction-level currency and date.
• FLUSH_CACHED_RATES — Clears the package's internal rate and segment caches, used when conversion data changes during a session.
• INIT — Initializes package state, including cache structures.

Tables Accessed

The package reads FND_CURRENCIES to obtain currency precision, minimum accounting units, and the functional currency datatype used broadly across Receivables. It references AR_SYSTEM_PARAMETERS for Receivables-level configuration defaults. Exchange rate definitions and conversion-type semantics are sourced from GL_DAILY_CONVERSION_TYPES. Utility routines from DBMS_UTILITY support error/stack handling, while PLITBLM supports PL/SQL table management for the internal caches. These lookups are read-oriented; ARPCURR does not directly post accounting entries.

Usage Notes

ARPCURR is a low-level utility package invoked by numerous other APPS packages — the ETRM metadata records it as referenced by 57 dependent packages — rather than being called directly from forms. It is typically reached through the Receivables receipts, transactions, and autoaccounting flows, and through subledger accounting when accounted amounts must be derived or validated. Because the routines honor the ledger's functional currency and cached rates, callers should invoke FLUSH_CACHED_RATES after modifying conversion rate data mid-session. In 12.2.2, the set-of-books parameter used by GETFUNCTCURR continues to function, but the value is supplied by the ledger context of the calling process. Custom extensions that require consistent currency rounding or rate resolution should reference ARPCURR instead of reimplementing conversion logic, preserving behavioral parity with standard Receivables processing.