Search Results trx_psa




Overview
Explore in AI Chat

Overview

APPS.LNS_RECEIVABLE_ACTIVITIES_V is a reporting view in the Oracle E-Business Suite Lease and Loan Management (LNS) module. It consolidates loan amortization schedules, Receivables transactions, and payment application activity into a single, denormalized result set that presents the receivable-side activity of a lease or loan contract. The view correlates each loan (LNS_LOAN_HEADERS_ALL) to its amortization schedules and lines (LNS_AMORTIZATION_SCHEDS, LNS_AMORTIZATION_LINES), then joins outward to the Accounts Receivable transaction and payment schedule tables that represent the invoiced principal, interest, and fee streams.

Because the LNS application generates Receivables invoices for each amortization event, reporting on cash applications and outstanding balances from the Lease Management perspective requires a join between the LNS amortization tables and the AR transaction model. This view encapsulates that join, exposing loan identifiers, amortization schedule identifiers, invoice numbers, payment schedule identifiers, customer transaction line identifiers, application amounts, and apply dates. It is intended primarily for lease analysts, collections personnel, and revenue/accounting teams who need to reconcile loan receivable activity without manually reconstructing the LNS-to-AR relationship.

Underlying Base Objects

The documented base objects include LNS_LOAN_HEADERS_ALL, LNS_AMORTIZATION_SCHEDS, and LNS_AMORTIZATION_LINES on the LNS side, and RA_CUSTOMER_TRX_ALL, RA_CUSTOMER_TRX_LINES_ALL, AR_PAYMENT_SCHEDULES_ALL, AR_RECEIVABLE_APPLICATIONS_ALL, and AR_ADJUSTMENTS_ALL on the Receivables side. Lookup semantics are supplied through the AR_LOOKUPS and LNS_LOOKUPS views, while FND_GLOBAL supplies the runtime organization/security context. The aliased joins in the view text—trx and trx1 to RA_CUSTOMER_TRX_ALL, trx_psa and rec_psa to AR_PAYMENT_SCHEDULES_ALL, and am/aml to the amortization tables—show how invoice-level, payment-schedule-level, and application-level data are stitched together.

Key Columns

Common Use Cases and Queries

A frequent requirement is to report cash collections against a loan's amortization schedule, including the running funded/principal balance:

SELECT loan_id, amortization_schedule_id, payment_number, due_date,
       trx_number, amount_applied, apply_date, phase
FROM   apps.lns_receivable_activities_v
WHERE  loan_id = :p_loan_id
ORDER  BY due_date, payment_number;

Users searching for the term trx_psa are typically looking for the link between a loan's amortization schedule and its AR payment schedule, which this view exposes through the TRX_PSA alias’s PAYMENT_SCHEDULE_ID column. Queries joining the view back to AR_PAYMENT_SCHEDULES_ALL on that identifier allow reconciliation of lease schedules to Receivables aging. Equally common is filtering by org_id and legal_entity_id for multi-organization reporting, or aggregating amount_applied by phase to compare term-phase collections with the loan's funded amount.