Search Results ar_late_charge_type




Overview
Explore in AI Chat

Overview

APPS.AR_INTEREST_HEADERS_V is a reporting and integration view in Oracle EBS Receivables (AR) that exposes late charge (interest) header records together with their descriptive attributes and decoded lookup meanings. The underlying transactional table, AR_INTEREST_HEADERS, stores the header-level definitions of a late charge batch — the criteria, calculations, terms, and flags that govern how finance charges are computed against overdue transactions. The view enriches that raw data with denormalized customer, party, site, address, currency, and term information, and it decodes several code columns into user-facing meanings through ARPT_SQL_FUNC_UTIL.get_lookup_meaning calls.

Because it decodes values such as the late charge type, calculation transaction basis, and various YES/NO flags, the view is particularly useful for reporting, concurrent program outputs, Discoverer or OBIEE reporting layers, and integrations that must present late charge configuration in a human-readable form. It is one of the primary supported interfaces for reading late charge header setups without joining multiple lookup and customer tables manually.

Underlying Base Objects

The view is defined over AR_INTEREST_HEADERS (synonym) as its driving table, aliased h. It joins to HZ_CUST_ACCOUNTS (c), HZ_PARTIES (party), HZ_CUST_ACCT_SITES, HZ_CUST_SITE_USES (su), HZ_LOCATIONS (addr), HZ_PARTY_SITES, and FND_TERRITORIES_VL (terr) to assemble customer name, account number, site use, and a concatenated address formatted by ARP_ADDR_PKG.format_address. GL_DAILY_CONVERSION_TYPES supplies the currency exchange rate type and its descriptive value, while RA_TERMS (rt) provides the late charge term name and XLE_LE_OU_LEDGER_V supports operating unit / ledger context.

RA_CUST_TRX_TYPES and AR_CHARGE_SCHEDULES are referenced for transaction-type and charge-schedule relationships, and AR_STANDARD_TEXT (msg) supplies the message text name. AR_SYSTEM_PARAMETERS provides system-level defaults. The function AR_INTEREST_HEADERS_PKG.get_header_amount computes the header amount on the fly, and ARPT_SQL_FUNC_UTIL performs all lookup decodings.

Key Columns

Common Use Cases and Queries

Typical uses include listing all active late charge headers for a customer, auditing the type of each header, and feeding downstream reporting with decoded flag values.

SELECT interest_header_id, header_type_m, party_name,
       account_number, currency_code, header_amount
FROM   apps.ar_interest_headers_v
WHERE  header_type_m IS NOT NULL
AND    org_id = :p_org_id;

To isolate headers by late charge type, filter on the decoded column rather than the raw code:

SELECT interest_header_id, party_name, late_charge_term_name,
       interest_period_days
FROM   apps.ar_interest_headers_v
WHERE  header_type_m = 'Late Charges';

The view is also well suited to reconcile grace periods and calculation bases, and to expose which headers charge interest on finance charges or hold charged invoices. Because amount and lookup decoding are performed by PL/SQL functions, heavy-volume extracts should be filtered before selecting HEADER_AMOUNT or the _M columns to limit function-call overhead.