Results for “min_interest_charge”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AR_LATE_CHARGE_TRX_T is a Receivables (AR) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that supports late charge processing. It stores the transactional detail generated when the Late Charges program evaluates overdue customer transactions and calculates finance or late charge amounts. The table is owned by the AR schema and is documented as VALID in ETRM, with 47 columns in the 12.2.2 physical schema. Its primary key is AR_LATE_CHARGE_TRX_PK, defined on the LATE_CHARGE_TRX_ID column, and a unique index AR_LATE_CHARGE_TRX_U1 also exists on LATE_CHARGE_TRX_ID.

From a Data Vault modeling perspective, the ETRM metadata classifies this table heuristically as standalone, meaning it does not participate in a broader hub/link/satellite relationship pattern in the documented FK structure. In practice, it behaves like a transaction fact or satellite tied to customer transactions, payment schedules, and late charge terms, capturing the evaluated charge result for a given billing period.

Key Information Stored

The surrogate primary key is LATE_CHARGE_TRX_ID, which uniquely identifies each late charge processing record and is also the business-key candidate via AR_LATE_CHARGE_TRX_U1. The most significant columns include:

• CUSTOMER_ID, CUSTOMER_SITE_USE_ID – the customer and site context for the charge.
• CUSTOMER_TRX_ID, PAYMENT_SCHEDULE_ID – the invoice/transaction and installment being evaluated.
• CUST_TRX_TYPE_ID, LEGAL_ENTITY_ID – transaction type and legal entity; both are foreign keys (to RA_CUST_TRX_TYPES_ALL and FV_LEGAL_ENTITIES respectively).
• CURRENCY_CODE, EXCHANGE_RATE, EXCHANGE_RATE_TYPE – currency and conversion details for the charge.
• AMOUNT_DUE_ORIGINAL, AMOUNT_DUE_REMAINING, ORIGINAL_BALANCE – balance measures driving interest calculation.
• LATE_CHARGE_AMOUNT, FIN_CHARGE_CHARGED, CHARGE_TYPE, LATE_CHARGE_TYPE – the computed charge and its classification.
• INTEREST_RATE, INTEREST_DAYS, INTEREST_PERIOD_DAYS, INTEREST_CALCULATION_PERIOD, INTEREST_TYPE – parameters and results of the interest computation.
• TRX_DATE, DUE_DATE, LAST_CHARGE_DATE, FINANCE_CHARGE_DATE, RATE_START_DATE, RATE_END_DATE – key dates defining the evaluation window.
• LATE_CHARGE_TERM_ID – link to the late charge term definition controlling the calculation.
• ORG_ID, REQUEST_ID – multi-org and concurrent request context.
• CASH_RECEIPT_ID, RECEIPT_DATE, ACTUAL_DATE_CLOSED – receipt linkage and closure information.

Common Use Cases and Queries

Typical uses include auditing finance charge calculations, reporting late charge revenue, reconciling charges back to invoices, and debugging the Late Charges concurrent program output. A common query joins to RA_CUST_TRX_TYPES_ALL and FV_LEGAL_ENTITIES on the documented foreign keys:

SELECT t.late_charge_trx_id, t.customer_trx_id, t.late_charge_amount, t.fin_charge_charged, t.charge_type, t.trx_date
FROM ar.ar_late_charge_trx_t t
WHERE t.org_id = :org_id
AND t.finance_charge_date BETWEEN :start_date AND :end_date;

Analysts may group by CHARGE_TYPE or LATE_CHARGE_TYPE for trend reporting, filter by REQUEST_ID to isolate a specific Late Charges run, or join to RA_CUSTOMER_TRX_ALL via CUSTOMER_TRX_ID for invoice-level drill-down.

Related Objects

• RA_CUST_TRX_TYPES_ALL – referenced via CUST_TRX_TYPE_ID.
• FV_LEGAL_ENTITIES – referenced via LEGAL_ENTITY_ID.
• RA_CUSTOMER_TRX_ALL – joined via CUSTOMER_TRX_ID for invoice detail.
• AR_PAYMENT_SCHEDULES_ALL – joined via PAYMENT_SCHEDULE_ID.
• AR_CASH_RECEIPTS_ALL – joined via CASH_RECEIPT_ID.
• AR_LATE_CHARGE_TERMS / AR_LATE_CHARGE_TERMS_TL – joined via LATE_CHARGE_TERM_ID.
• HZ_CUST_ACCOUNTS / HZ_CUST_SITE_USES_ALL – customer context.
• FND_CONCURRENT_REQUESTS – joined via REQUEST_ID for program traceability.