Results for “ar_calculation_period”
34 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
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
- INTEREST_HEADER_ID / INTEREST_BATCH_ID — primary header identifier and its owning batch.
- CUSTOMER_ID, CUSTOMER_SITE_USE_ID, PARTY_NAME, ACCOUNT_NUMBER, LOCATION, CONCATENATED_ADDRESS — customer and site identification.
- CURRENCY_CODE, EXCHANGE_RATE_TYPE, EXCHANGE_RATE_TYPE_DSP, EXCHANGE_RATE — currency and conversion details.
- HEADER_TYPE / HEADER_TYPE_M — the late charge type; the _M column decodes it via the AR_LATE_CHARGE_TYPE lookup. This is the column referenced when users search on "ar_late_charge_type".
- LATE_CHARGE_CALCULATION_TRX / _M — transaction basis, decoded against AR_MANDATORY_LATE_CHARGES.
- CREDIT_ITEMS_FLAG, DISPUTED_TRANSACTIONS_FLAG, CHARGE_ON_FINANCE_CHARGE_FLAG, HOLD_CHARGED_INVOICES_FLAG, MULTIPLE_INTEREST_RATES_FLAG — YES/NO flags with corresponding decoded _M columns.
- PAYMENT_GRACE_DAYS, LATE_CHARGE_TERM_ID, LATE_CHARGE_TERM_NAME — grace period and payment term.
- INTEREST_PERIOD_DAYS, INTEREST_CALCULATION_PERIOD / _M — calculation frequency, decoded via AR_CALCULATION_PERIOD.
- CHARGE_BEGIN_DATE, MESSAGE_TEXT_ID, MESSAGE_TEXT_NAME, CUST_ACCT_PROFILE_AMT_ID, MIN_FC_INVOICE_OVERDUE_TYPE — scheduling, messaging, and threshold attributes.
- HEADER_AMOUNT — computed header amount.
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.
-
(Release 12.0 Only)
APPS.AR_CUSTOMER_PROFILE_CLASSES_V·↳ ARPT_SQL_FUNC_UTIL·↳ AR_AUTOCASH_HIERARCHIES·↳ AR_COLLECTORS·Explore AR module →
-
View: AR_INTEREST_HEADERS_V 12.1.1
Late Charge header preview work bench
APPS.AR_INTEREST_HEADERS_V·↳ ARPT_SQL_FUNC_UTIL·↳ ARP_ADDR_PKG·↳ AR_CHARGE_SCHEDULES·Explore AR module →
-
View: AR_INTEREST_HEADERS_V 12.2.2
Late Charge header preview work bench
APPS.AR_INTEREST_HEADERS_V·↳ ARPT_SQL_FUNC_UTIL·↳ ARP_ADDR_PKG·↳ AR_CHARGE_SCHEDULES·Explore AR module →
-
(Release 12.0 Only)
APPS.AR_CUSTOMER_PROFILE_CLASSES_V·↳ ARPT_SQL_FUNC_UTIL·↳ AR_AUTOCASH_HIERARCHIES·↳ AR_COLLECTORS·Explore AR module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
Credit information for customer accounts and customer account sites
-
This table is used to store the deleted records for hz_customer_profiles during account merge
-
Credit information for customer accounts and customer account sites
-
Standard credit profile classes
-
This table is used to store the deleted records for hz_customer_profiles during account merge
-
Standard credit profile classes
-
Customer Interface table for customer profile information
-
Customer Interface table for customer profile information
-
eTRM - AR Tables and Views 12.2.2
Territory information
-
eTRM - AR Tables and Views 12.1.1
Territory information