Search Results discount_factor_conv

Overview

XTR_RATE_CONVERSION is a PL/SQL package owned by APPS in Oracle E-Business Suite, classified as an OTHER API under the ETRM (Enterprise Treasury and Risk Management) module. Its core business function is to convert interest rates and yields between differing day count bases and varying compounding conventions. As stated in the package header comments, RATE_CONVERSION "converts between two rates that have different day count basis or compounding types." The package is a foundational treasury calculation utility used when financial instruments are priced, revalued, or compared against benchmarks that employ different interest conventions.

The package assumes the effective period for rates is one year and operates on the notion of a start date and an end date defining when the rates become effective. It supports three fundamental rate types: Simple Rate ('S'), Continuous Rate ('C'), and Compounding Rate ('P'). These distinctions are essential in treasury management, where a rate quoted on an Actual/360 basis with annual compounding is not directly comparable to one quoted on a 30/360 basis with semi-annual compounding. The package also explicitly does not cover DISCOUNT_TO_YIELD_RATE and YIELD_TO_DISCOUNT_RATE conversions within the general RATE_CONVERSION procedure, although dedicated procedures exist for discount-related calculations.

Key Procedures and Functions

The package documents 17 procedures and functions that fall into several functional groupings:

• Base conversions: DISCOUNT_TO_YIELD_RATE and YIELD_TO_DISCOUNT_RATE convert between discount and yield quotations; these are noted as outside the scope of the central RATE_CONVERSION routine.
• Day count conversion: DAY_COUNT_BASIS_CONV converts a rate from one day count basis to another.
• Simple/continuous conversions: SIMPLE_TO_CONTINUOUS_RATE and CONTINUOUS_TO_SIMPLE_RATE transform between simple and continuously compounded rates.
• Simple/compound conversions: SIMPLE_TO_COMPOUND_RATE and COMPOUND_TO_SIMPLE_RATE transform between simple and discretely compounded rates, using compounding frequency parameters.
• Continuous/compound conversions: CONTINUOUS_TO_COMPOUND_RATE and COMPOUND_TO_CONTINUOUS_RATE transform between continuous and discrete compounding.
• Compound frequency conversion: COMPOUND_TO_COMPOUND_RATE converts between two discretely compounded rates with differing frequencies.
• General conversion: RATE_CONVERSION performs the combined day count basis and rate type conversion in a single call.
• Discount factor variants: YIELD_TO_DISCOUNT_FACTOR_SHORT, YIELD_TO_DISCOUNT_FACTOR_LONG, DISCOUNT_FACTOR_TO_YIELD_SHORT, DISCOUNT_FACTOR_TO_YIELD_LONG, and DISCOUNT_FACTOR_CONV provide discount factor computations over short and long tenors.
• Annualization: RATE_CONV_SIMPLE_ANNUALIZED converts a simple rate to an annualized form.

Tables Accessed

The documented metadata lists no tables referenced via APPS synonyms. XTR_RATE_CONVERSION is a computational utility package; it operates purely on scalar input parameters and returns computed scalar results. It does not perform DML against treasury tables such as rate schedules or instrument definitions. Any persistence of converted rates is therefore the responsibility of the calling code, not this package.

Usage Notes

The package is a low-level calculation engine rather than a user-facing component. It is referenced by 9 other packages, indicating it is invoked internally by higher-level treasury packages that manage rate definitions, yield curves, and instrument valuation. Typical invocation contexts include forms that display or accept rate inputs in different conventions, and concurrent programs that perform mass rate or yield recalculations and revaluations. Custom extensions performing treasury calculations should call these procedures rather than reimplementing conversion formulas, ensuring consistency with the methodology described in the Oracle Rate Conversions HLD.

Developers must be aware of a documented methodological caveat: performing day count basis conversion first and then rate type conversion yields a different result than performing the rate type conversion first. Consequently, round-trip conversions—such as converting a simple rate to a compounded rate with a different day count basis and then back—will not return the original value. This is an inherent mathematical property of the conversion methodologies, not an implementation defect. Callers should therefore treat converted rates as approximations and avoid relying on round-trip identity in reconciliation logic.