Search Results receipt_status_code

Overview

OKL_CS_TRX_PAYMENTS_UV is a consolidated reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL (Leasing and Finance Management) module. It presents a unified, denormalized picture of contract-related cash receipts and their application against customer transactions — principally lease invoices, payment schedules, and receivables activity. The view bridges Oracle Lease Management contract data (OKC/OKL tables) with Oracle Receivables transactional data (AR_CASH_RECEIPTS_ALL, AR_RECEIVABLE_APPLICATIONS_ALL, AR_PAYMENT_SCHEDULES_ALL, RA_CUSTOMER_TRX_ALL), which makes it valuable for reporting on lease billing, receipt application status, and stream-type attribution without requiring the report author to join these modules manually.

Because the view surfaces receipt_status_code-adjacent attributes — notably the lookup meaning derived from AR_LOOKUPS (alias ALKP, exposed as STATUS) and receipt-history STATUS from AR_CASH_RECEIPT_HISTORY_ALL — it is commonly used when a report or integration must determine whether a receipt is applied, unapplied, or otherwise dispositioned. Users searching for receipt_status_code will typically find the decoded MEANING column here rather than the raw code.

Underlying Base Objects

The view is defined over the following documented base objects:

• AR_CASH_RECEIPTS_ALL, AR_RECEIVABLE_APPLICATIONS_ALL, AR_ACTIVITY_DETAILS, AR_PAYMENT_SCHEDULES_ALL — Receivables receipt, application, and payment-schedule data.
• AR_CASH_RECEIPT_HISTORY_ALL — receipt lifecycle history, contributing the STATUS column.
• AR_RECEIPT_METHODS, AR_LOOKUPS, FND_LOOKUPS — lookup and reference data providing decoded meanings (ALKP, RCTSTSLK, RTYPLK aliases).
• RA_CUSTOMER_TRX_ALL, RA_CUSTOMER_TRX_LINES_ALL — invoice header and line detail, including tax lines linked via LINK_TO_CUST_TRX_LINE_ID.
• OKC_K_HEADERS_ALL_B (contract header), OKL_TRX_CSH_RCPT_ALL_B and OKL_TXL_RCPT_APPS_ALL_B — leasing contract and cash-receipt framework tables.
• HZ_CUST_ACCOUNTS (customer account/party), plus FND_GLOBAL for session context.

Joins are driven from cash receipt ID through receivable applications to payment schedules and customer transaction lines, with contract header linkage via OKC_K_HEADERS_ALL_B.

Key Columns

• RECEIVABLE_APPLICATION_ID — unique key of the application record joining receipt to transaction.
• INVOICE_NUMBER, TRX_DATE, DUE_DATE, APPLY_DATE — invoice and application dating.
• ORIGINAL_AMOUNT, APPLIED_AMOUNT, AMOUNT_REMAINING — amounts including linked tax lines.
• RECEIPT_NUMBER, RECEIPT_DATE, AMOUNT, CURRENCY_CODE — receipt identity and value.
• STATUS (ALKP.MEANING) and MEANING (RCTSTSLK.MEANING) — decoded receipt/application status values relevant to receipt_status_code lookups.
• RECEIPT_TYPE — DECODE on OKLCASH.RECEIPT_TYPE yielding 'ADV' (advance) or 'REG' (regular).
• ADVANCED_YN (RTYPLK.MEANING), CONTRACT_NUMBER, STREAM_TYPE, LINE_NUMBER — leasing contract and stream attribution.
• PARTY_ID, ACCOUNT_NUMBER, ORG_ID — customer and operating-unit context.

Common Use Cases and Queries

Typical scenarios include reconciling lease receipts to invoice applications, reporting advance versus regular receipts, and validating receipt_status_code by inspecting decoded status meanings. A representative query:

• SELECT invoice_number, receipt_number, status, receipt_type, applied_amount, amount FROM okl_cs_trx_payments_uv WHERE party_id = :p_party_id AND status = 'Applied';
• SELECT contract_number, SUM(applied_amount) FROM okl_cs_trx_payments_uv GROUP BY contract_number;
• SELECT invoice_number, receipt_status_code, meaning FROM okl_cs_trx_payments_uv WHERE receipt_type = 'ADV'; — note that if a literal receipt_status_code is not exposed, use the STATUS/MEANING columns derived from AR_LOOKUPS.

Because it joins Receivables and Lease Management, the view is well suited to Discoverer, BI Publisher, and custom concurrent-program extraction. Performance is improved by filtering on ORG_ID, PARTY_ID, or contract number, since the underlying joins span high-volume transaction tables.