Results for “okl_bpd_ar_header_v”

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

Overview

OKL_BPD_AR_HEADER_V is a presentation view owned by the APPS schema within the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite. The view is documented under ETRM 12.2.2 and is marked VALID in the data dictionary for both 12.1.1 and 12.2.2 environments. Its declared purpose is to support the Operations and Transactions search page within the Lease and Finance Management application, providing a consolidated, user-facing projection of accounts receivable transactions that originate from lease contracts and associated billing activity.

The view sits at the boundary between the OKL lease transaction data model and the Oracle Receivables (AR) transaction tables. It presents receivables invoices, their transaction types, statuses, amounts, currencies, and linkage back to lease contract headers and ledger context, so that the OKL transaction search user interface can expose a single queryable source without forcing the calling code to join across the lease and receivables schemas directly.

Underlying Base Objects

The view is defined over a subquery that joins several lease, receivables, and reference objects. Documented referenced base objects include OKC_K_HEADERS_B, OKL_K_HEADERS, OKL_PRODUCTS, OKL_TRX_AR_INVOICES_B, OKL_TXD_AR_LN_DTLS_B, OKL_TXL_AR_INV_LNS_B, RA_CUSTOMER_TRX_ALL, RA_CUSTOMER_TRX_LINES_ALL, RA_CUST_TRX_TYPES, AR_PAYMENT_SCHEDULES_ALL, and HZ_CUST_ACCOUNTS, together with the OKL_ACCOUNTING_UTIL package used for lookup translations.

• OKC_K_HEADERS_B / OKL_K_HEADERS supply contract number and contract header identity (KHR_ID).
• RA_CUSTOMER_TRX_ALL / RA_CUSTOMER_TRX_LINES_ALL provide the receivables invoice header and line detail, including transaction number, date, currency, extended amount, and tax recoverable values.
• RA_CUST_TRX_TYPES supplies transaction type codes and names used to build the description string.
• OKL_PRODUCTS supplies the product name, and OKL_TXD_AR_LN_DTLS_B and the associated invoice line tables bridge lease billing detail into the AR lines.
• OKL_ACCOUNTING_UTIL is invoked through GET_LOOKUP_MEANING to translate lookup codes into descriptive meanings for source, transaction type, transaction status, and actual/draft status.

Key Columns

• ID – the RA_CUSTOMER_TRX_ALL.CUSTOMER_TRX_ID, converted to character, identifying the AR transaction.
• KHR_ID / CONTRACT_NUMBER – the lease contract header identifier and human-readable contract number.
• SOURCE_CODE / SOURCE – source classification such as 'REC', with the lookup meaning resolved via OKL_VIEW_ACC_SOURCES.
• TRANSACTION_NUMBER, TRANSACTION_TYPE, TRANSACTION_DATE, TRX_TYPE – receivables transaction identifying attributes.
• TRANSACTION_STATUS – derived from COMPLETE_FLAG using the INVOICE_DETAIL_REPORT lookup.
• DESCRIPTION – concatenation of interface header attribute, transaction type name, and lookup meaning.
• AMOUNT / TOTAL_TRANSACTION_AMOUNT – the summed extended amount plus tax recoverable, and the summed extended amount for LINE and TAX line types.
• CURRENCY_CODE, LEDGER_ID, ORG_ID, ACCOUNT_NUMBER, TRY_ID, CHECK_ID – currency, ledger, operating unit, account, and secondary reference identifiers.

Common Use Cases and Queries

Typical usage is to drive the OKL Operations and Transactions search page and to build custom receivables-to-lease reconciliation reports. A minimal query returns the transaction list for a contract:

SELECT id, contract_number, transaction_number, transaction_type, transaction_status, transaction_date, amount, currency_code FROM okl_bpd_ar_header_v WHERE contract_number = :p_contract_number ORDER BY transaction_date;

To reconcile billed amounts per ledger and operating unit:

SELECT ledger_id, org_id, currency_code, SUM(amount) total_amount FROM okl_bpd_ar_header_v WHERE transaction_date BETWEEN :p_from AND :p_to GROUP BY ledger_id, org_id, currency_code;