Search Results fv_finance_charge_grp_dtls

Overview

FV_DC_ASSIGN_FINANCE_CHRG is an APPS-owned PL/SQL package body within the Oracle E-Business Suite Receivables (AR) module, specifically part of the FlexValue (FV) finance charge feature set. Its documented purpose is to assign finance charges to eligible customer accounts and to accrue those charges, producing finance charge invoices and invoice lines. In release 12.1.1 and 12.2.2 this package is the engine invoked by the Finance Charge Assignment process and related concurrent programs. The package reads the finance charge setup defined in the FV_FINANCE_CHARGE_GRP_HDRS and FV_FINANCE_CHARGE_GRP_DTLS headers and detail tables (the object most closely associated with the user's search term) together with control records in FV_FINANCE_CHARGE_CONTROLS and FV_AR_CONTROLS to determine which customers, sites, and overdue transactions qualify for a charge.

The package operates in the context of Multi-Org, as evidenced by dependencies on MO_GLOBAL and MO_UTILS, and it uses the standard FND API, logging, message, and file utilities for error handling, debug logging, and report output. It writes the resulting finance charge invoices into the FV_AR_FIN_CHRG_INVOICES and FV_AR_FIN_CHRG_INV_LINES tables, updating AR customer transaction tables through the AR_INVOICE_API_PUB and related Receivables tables.

Key Procedures and Functions

Two documented entry points exist in the package:

• ASSIGN_FINANCE_CHARGE — the primary procedure that identifies eligible overdue transactions and customer accounts, applies the finance charge rules defined in the finance charge group setup (FV_FINANCE_CHARGE_GRP_HDRS / FV_FINANCE_CHARGE_GRP_DTLS, FV_FINANCE_CHRG_CUST_CLASSES), and assigns the resulting charges. It interacts with AR_PAYMENT_SCHEDULES to evaluate amounts due and days overdue, and with FV_CUST_FINANCE_CHRGS / FV_CUST_FINANCE_CHRGS_ALL to record charges at the customer level.
• ACCRUE_FINANCE_CHARGE — accrues the finance charges calculated for a customer or transaction, posting the accrued amounts and creating the corresponding invoice header and line records. It uses FV_INVOICE_FINANCE_CHRGS / FV_INVOICE_FINANCE_CHRGS_ALL and FV_FINANCE_CHARGE_HISTORY to persist accrued amounts and audit history, and relies on AR_INVOICE_API_PUB to generate the actual debit memos or finance charge invoices.

Tables Accessed

The package reads and writes a broad set of Receivables and FlexValue tables. Setup and control data are drawn from FV_FINANCE_CHARGE_GRP_HDRS, FV_FINANCE_CHARGE_GRP_DTLS, FV_FINANCE_CHARGE_CONTROLS, FV_FINANCE_CHRG_CUST_CLASSES, and FV_AR_CONTROLS. Transaction and eligibility data come from AR_PAYMENT_SCHEDULES, RA_CUSTOMER_TRX / RA_CUSTOMER_TRX_ALL, RA_CUSTOMER_TRX_LINES / RA_CUSTOMER_TRX_LINES_ALL, RA_CUST_TRX_LINE_GL_DIST, RA_CUST_TRX_TYPES, RA_TERMS, and customer data in HZ_CUST_ACCOUNTS and HZ_CUST_SITE_USES_ALL. Output and audit records are written to FV_AR_FIN_CHRG_INVOICES, FV_AR_FIN_CHRG_INV_LINES, FV_INVOICE_FINANCE_CHRGS, FV_INVOICE_FINANCE_CHRGS_ALL, FV_CUST_FINANCE_CHRGS, FV_CUST_FINANCE_CHRGS_ALL, and FV_FINANCE_CHARGE_HISTORY. AR_TRX_ERRORS_GT captures transaction-level errors, while GL_LEDGERS, GL_LEDGERS_PUBLIC_V, GL_PERIOD_STATUSES, and FV_VALUE_OF_FUND_PERIODS support accounting and period validation. Standard FND dependencies (FND_API, FND_FILE, FND_GLOBAL, FND_LOG, FND_MSG_PUB, FND_REQUEST) provide API, logging, and concurrent request functionality.

Usage Notes

FV_DC_ASSIGN_FINANCE_CHRG is not referenced by any other database object, indicating it is a top-level driver invoked directly rather than called from a dependency chain. It is typically executed from the Oracle Receivables Finance Charge concurrent programs, either through the standard submission flow or via FND_REQUEST.Submit_Request from custom code. The presence of FND_FILE implies report or log output generation, and FND_LOG supports debug tracing. Because the package performs Multi-Org-aware processing through MO_GLOBAL, callers must ensure the correct operating unit context is initialized before invocation. No public PL/SQL callers exist in the schema, so the supported interface is the concurrent program and, secondarily, direct API invocation.