Search Results ar_interest_headers_v




Overview
Explore in AI Chat

Overview

AR_INTEREST_HEADERS_V is an Oracle E-Business Suite Receivables (AR) view owned by the APPS schema and classified as a Late Charge header preview workbench. It exposes one row per late charge (interest) header, joining the core late charge header record in AR_INTEREST_HEADERS to customer, party, site, address, currency, terms, and system parameter data. Its primary design purpose is to supply the Receivables "Late Charges" preview and workbench UI with a flattened, display-ready result set.

The view is a presentation and reporting construct rather than a transactional base object. It performs no DML of its own; it derives its content from the header table plus lookup translation functions and address formatting logic. Because it is a database view over documented base objects, it is accessible to any tool that can issue SQL against the APPS schema, including Oracle Reports, BI Publisher, custom concurrent programs, and OAF-based workbench pages.

In the 12.1.1 and 12.2.2 releases, the object retains its VALID status and its dependency footprint is consistent with the ETRM documentation. The "_V" suffix denotes a view, and the presence of the "_M" suffixed columns (for example, HEADER_TYPE_M, CREDIT_ITEMS_FLAG_M) indicates that the view pre-resolves Oracle lookup codes into their user-facing meanings at query time, sparing the calling application from a secondary lookup join.

Underlying Base Objects

The view is defined over the following documented base objects. The central table is AR_INTEREST_HEADERS, which stores the late charge header rows keyed by INTEREST_HEADER_ID and INTEREST_BATCH_ID. Customer master data is drawn from HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES, HZ_CUST_SITE_USES, HZ_PARTY_SITES, and HZ_LOCATIONS, supplying party name, account number, site use, and address attributes. Address assembly is performed through ARP_ADDR_PKG.FORMAT_ADDRESS, with territory short names coming from FND_TERRITORIES_VL.

Currency conversion metadata is sourced from GL_DAILY_CONVERSION_TYPES (joined for EXCHANGE_RATE_TYPE_DSP). Late charge terms come from RA_TERMS via LATE_CHARGE_TERM_ID. Transaction type context is available through RA_CUST_TRX_TYPES, and charge scheduling through AR_CHARGE_SCHEDULES. Standard message text is retrieved from AR_STANDARD_TEXT. System-level defaults, including organizational and ledger context, are supplied by AR_SYSTEM_PARAMETERS and XLE_LE_OU_LEDGER_V.

Two PL/SQL packages are essential to the view's behavior. ARPT_SQL_FUNC_UTIL.GET_LOOKUP_MEANING is called repeatedly to translate lookup codes in the AR_LATE_CHARGE_TYPE, AR_MANDATORY_LATE_CHARGES, AR_CALCULATION_PERIOD, and YES/NO lookup types. AR_INTEREST_HEADERS_PKG.GET_HEADER_AMOUNT computes the HEADER_AMOUNT at runtime. Because these are package calls embedded in the SELECT list, each row incurs lookup and function execution, which is relevant to performance tuning.

Key Columns

Common Use Cases and Queries

The view is most frequently queried to preview or audit late charge headers before generation, to report on charged interest by customer or collector, and to expose translated lookup meanings to downstream systems. A typical query filters on header type or translated type value:

  • Preview all headers for a customer: SELECT interest_header_id, customer_id, account_number, header_amount, header_type_m FROM ar_interest_headers_v WHERE customer_id = :customer_id;
  • Find headers by translated type: SELECT interest_header_id, party_name, header_type, header_type_m, header_amount FROM ar_interest_headers_v WHERE header_type_m = :interest_type_m;
  • Batch-level reporting by currency and org: SELECT interest_batch_id, currency_code, SUM(header_amount) FROM ar_interest_headers_v WHERE org_id = :org_id GROUP BY interest_batch_id, currency_code;

Because HEADER_AMOUNT and the _M columns are resolved through PL/SQL functions, queries returning large row counts benefit from restrictive predicates on indexed base columns such as CUSTOMER_ID, INTEREST_BATCH_ID, and ORG_ID. Where only raw codes are required, querying AR_INTEREST_HEADERS directly avoids function overhead. For integrations, the view provides a convenient single source for both codes and their meanings, ensuring consistent presentation across Receivables reports and workbench screens.