Search Results fv_finance_charge_history




Overview
Explore in AI Chat

Overview

The FV_FINANCE_CHARGE_HISTORY table is a core data repository within the Oracle E-Business Suite Federal Financials (FV) module, specifically designed for managing finance charge calculations. Its primary role is to store the historical and current parameters—either a percentage rate or a flat fee amount—that are applied when generating finance charges for transactions. This table is essential for maintaining an auditable trail of charge configurations over time, ensuring that calculations for interest or penalties on items like late payments are accurate, traceable, and compliant with federal financial regulations. It functions as a child table to the main finance charge control definitions, enabling organizations to adjust charge rules by effective date ranges.

Key Information Stored

The table's structure centers on linking a charge rule to its specific calculation parameters and effective period. The primary key, CHARGE_HISTORY_ID, uniquely identifies each historical record. The critical foreign key, CHARGE_ID, links directly to a parent rule defined in the FV_FINANCE_CHARGE_CONTROLS_ALL table. Another significant foreign key, SET_OF_BOOKS_ID, ties the charge parameter to a specific accounting ledger, as defined in GL_SETS_OF_BOOKS_11I. While the provided metadata does not list all columns, the description confirms the table holds the essential data for the charge calculation itself: the applicable finance charge rate or the flat fee amount. It will also logically contain columns to manage the effective start and end dates for each parameter set, allowing for historical tracking of rate changes.

Common Use Cases and Queries

This table is primarily accessed during the automated or manual process of assessing finance charges on transactions. A common operational query involves retrieving the active charge parameters for a given charge rule and ledger as of a specific date. For auditing and reporting purposes, analysts run queries to review the history of rate changes. Sample SQL patterns include identifying all parameters for a control or validating current rates.

  • Fetching the active rate for a charge ID: SELECT * FROM fv_finance_charge_history WHERE charge_id = :p_charge_id AND set_of_books_id = :p_sob_id AND SYSDATE BETWEEN effective_start_date AND NVL(effective_end_date, SYSDATE).
  • Historical audit report: SELECT fch.charge_history_id, fch.charge_id, fch.effective_start_date, fch.effective_end_date FROM fv_finance_charge_history fch, fv_finance_charge_controls_all fcc WHERE fch.charge_id = fcc.charge_id ORDER BY fcc.name, fch.effective_start_date DESC.

Related Objects

The FV_FINANCE_CHARGE_HISTORY table has defined dependencies within the Federal Financials schema. Its two documented foreign keys establish its core relationships:

  • FV_FINANCE_CHARGE_CONTROLS_ALL: This is the primary parent table. Each record in FV_FINANCE_CHARGE_HISTORY must correspond to a master finance charge control definition via the CHARGE_ID column.
  • GL_SETS_OF_BOOKS_11I: This relationship, via SET_OF_BOOKS_ID, ensures that finance charge parameters are segregated and applied correctly per the assigned accounting ledger, a critical requirement for multi-ledger implementations.

While not listed in the metadata, this table is also intrinsically linked to transaction processing engines and reports within the FV module that calculate and display assessed finance charges.