Search Results rec_trx_name

Overview

APPS.AR_INTEREST_LINES_V is a supplementary Oracle E-Business Suite view owned by the APPS schema and registered in FND Design Data as AR.AR_INTEREST_LINES_V. It exposes the detail rows of Oracle Receivables late-charge (interest) processing, presenting one record per interest line generated against an overdue payment schedule. In releases 12.1.1 and 12.2.2 the object remains VALID. Oracle classifies it as a "supplementary view used to simplify forms coding," and the standard warning applies: the view is not intended as a public query or DML interface and may change dramatically in subsequent minor or major releases.

The view is the principal source for the Receivables interest line form and for the columns surfaced around the REC_TRX_NAME field. REC_TRX_NAME carries the name of the receivables transaction (activity) that produced the charge — typically the Late Charge transaction type defined in AR_RECEIVABLES_TRX — allowing users and reports to identify the interest activity without a further join to the transaction setup table.

Underlying Base Objects

The documented dependency list identifies four base objects, each accessed through an APPS synonym:

• AR_INTEREST_LINES — the primary interest line table supplying line identifiers, amounts, rates, dates, process status, and audit columns.
• AR_PAYMENT_SCHEDULES — supplies schedule-level context such as days overdue, amounts due original and remaining, and due dates.
• AR_RECEIVABLES_TRX — the receivables activity definition, joined to derive the transaction name exposed as REC_TRX_NAME and the CLASS/type context.
• RA_CUSTOMER_TRX — the customer transaction header, providing the transaction number (TRX_NUMBER) and document sequencing information.

The view therefore denormalizes interest line data with payment schedule status and transaction/activity descriptive attributes, sparing form code and reports from repeating a four-table join.

Key Columns

• INTEREST_LINE_ID / INTEREST_HEADER_ID — primary line and header identifiers linking the row to its interest batch.
• ORIGINAL_TRX_ID / TRX_NUMBER / ORIGINAL_TRX_CLASS — the transaction being charged and its class.
• OUTSTANDING_AMOUNT, AMOUNT_DUE_ORIGINAL, AMOUNT_DUE_REMAINING — monetary basis for the calculation.
• DAYS_OVERDUE_LATE, DAYS_OF_INTEREST, INTEREST_RATE, INTEREST_CHARGED, FINANCE_CHARGE_CHARGED, DAILY_INTEREST_CHARGE — the interest computation results.
• PAYMENT_DATE, DUE_DATE, LAST_CHARGE_DATE, RATE_START_DATE, RATE_END_DATE, ACTUAL_DATE_CLOSED — key dates for aging and rate-period analysis.
• RECEIVABLES_TRX_ID, REC_TRX_NAME, TYPE — the Receivables activity and its descriptive name; REC_TRX_NAME is the user-facing label most often searched.
• PROCESS_STATUS, PROCESS_MESSAGE — outcome of the Late Charges process for the line.
• ORG_ID — multi-org operating unit identifier.
• OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, CREATED_BY — concurrency and audit columns.

Common Use Cases and Queries

Typical uses include reconciling Late Charges program output, reporting accrued interest by customer or activity, and diagnosing lines that failed processing. The following returns lines for a named late-charge activity:

SELECT interest_line_id, trx_number, rec_trx_name,
       days_overdue_late, interest_rate, interest_charged,
       process_status, org_id
  FROM apps.ar_interest_lines_v
 WHERE rec_trx_name = :p_activity_name
   AND org_id = :p_org_id;

Aggregate queries sum INTEREST_CHARGED by REC_TRX_NAME or TYPE for a period defined by LAST_CHARGE_DATE, and exception reports filter on PROCESS_STATUS and PROCESS_MESSAGE to isolate rejected lines. Because the object is a forms-support view, production integrations should prefer the base tables, treating AR_INTEREST_LINES_V as a read-only convenience layer that Oracle may redefine.