Results for “okl_bpd_trx_rcpt_header_v”

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

Overview

OKL_BPD_TRX_RCPT_HEADER_V is an APPS-owned database view in the Oracle Lease and Finance Management (OKL) module. It presents lease and finance contract receipts in a unified structure that consolidates accounts receivable cash receipts, receipt applications, and lease contract header information into a single reporting interface. Within the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, this view serves as a transaction-level data source for reporting, reconciliation, and integration scenarios that require visibility into how customer payments have been applied against lease-related receivables invoices.

The view is particularly relevant to the search term receipt_creation_status. The TRANSACTION_STATUS column is derived from the AR lookup RECEIPT_CREATION_STATUS, resolved through the packaged function ARPT_SQL_FUNC_UTIL.GET_LOOKUP_MEANING('RECEIPT_CREATION_STATUS', ARCASH.STATUS). This means the raw numeric STATUS value from AR_CASH_RECEIPTS_ALL is translated into a meaningful, user-facing label at query time. Reports and interfaces that need to display or filter by receipt creation status should therefore select TRANSACTION_STATUS rather than interpreting STATUS directly.

Underlying Base Objects

The view is defined through a UNION of two related queries. The documented base objects include:

• AR_CASH_RECEIPTS_ALL — the core Accounts Receivable receipt table supplying receipt number, date, amount, currency, receipt method, set of books, operating unit, and status.
• AR_RECEIPT_METHODS — joined through RECEIPT_METHOD_ID to provide the receipt method name.
• AR_RECEIVABLE_APPLICATIONS_ALL — joined through APPLIED_PAYMENT_SCHEDULE_ID and CASH_RECEIPT_ID to capture the amount applied to each invoice.
• AR_PAYMENT_SCHEDULES_ALL — restricted to CLASS = 'INV', providing the receivable invoice number (TRX_NUMBER).
• OKL_CNSLD_AR_STRMS_B, OKL_CNSLD_AR_LINES_B, OKL_CNSLD_AR_HDRS_B — consolidated AR stream, line, and header tables linking receipts back to contract detail.
• OKC_K_HEADERS_B — providing the contract ID and contract number.
• OKL_BILLING_UTIL_PVT and OKL_BPD_AR_INV_LINES_V — referenced supporting objects.
• OKL_ACCOUNTING_UTIL and ARPT_SQL_FUNC_UTIL — packages supplying lookup meaning functions for source, transaction type, and transaction status.

The UNION structure accommodates two linkage paths: one through consolidated AR streams and one through AR lines, ensuring receipts tied to contracts via either route appear in the result set.

Key Columns

• RECEIPT_NUMBER, RECEIPT_DATE, TOTAL_AMOUNT, CURRENCY_CODE, RECEIPT_ID — core receipt attributes from AR_CASH_RECEIPTS_ALL.
• NAME — the receipt method name from AR_RECEIPT_METHODS.
• AMOUNT_APPLIED — the amount applied to the corresponding invoice.
• RECEIVABLE_INVOICE_NUMBER — the AR invoice number (TRX_NUMBER).
• SATUS/STATUS and TRANSACTION_STATUS — the raw receipt status and its lookup meaning derived from RECEIPT_CREATION_STATUS; this is the column directly answering the receipt_creation_status search.
• CONTRACT_ID, CONTRACT_NUMBER — lease contract identification.
• SET_OF_BOOKS_ID, ORG_ID — accounting and operating unit context.
• SOURCE_CODE, SOURCE, TRANSACTION_TYPE — fixed indicators ('REC' and resolved lookup meanings) describing the transaction origin.
• DESCRIPTION — currently returned as NULL.

Common Use Cases and Queries

Typical scenarios include receipt-to-contract reconciliation, monitoring receipt creation status for integrations, and reporting applied amounts against lease invoices.

SELECT receipt_number,
       receipt_date,
       total_amount,
       currency_code,
       receivable_invoice_number,
       contract_number,
       transaction_status
FROM   apps.okl_bpd_trx_rcpt_header_v
WHERE  transaction_status = 'Applied'
  AND  receipt_date >= SYSDATE - 30;

To aggregate applied amounts by contract while exposing creation status, a straightforward grouping query can be used:

SELECT contract_number,
       transaction_status,
       SUM(amount_applied) applied_total
FROM   apps.okl_bpd_trx_rcpt_header_v
GROUP  BY contract_number, transaction_status;

Because TRANSACTION_STATUS is resolved through a lookup function, filtering on it should use the seeded lookup meaning values from RECEIPT_CREATION_STATUS, not the underlying numeric codes. Joins to AR and OKL base tables can be added for supplementary detail, but for most reporting purposes the view already supplies the necessary header-level fields.