Search Results bank_account_number

Overview

The OKL_RECEIPT_DETAILS_UV view is an Oracle E-Business Suite (EBS) Leasing and Finance Management (OKL) reporting object owned by the APPS schema. It presents a consolidated, denormalized read-only image of cash receipts captured against lease and finance contracts, combining the receipt header, its applied, unapplied and on-account balances, the customer context, the remittance bank information, and the currency conversion attributes applicable at the time of receipt. Its role is primarily reporting and integration: operational users, concurrent programs, and downstream extracts reference this view rather than joining the underlying AR and OKL tables directly, thereby insulating those consumers from the physical data model. The view is documented as VALID in the ETRM repository for 12.2.2 and behaves identically in 12.1.1 for the purposes of reporting.

Underlying Base Objects

The view is defined over a set of AR, HZ, IBY, XLE and OKL objects. The driving table is AR_CASH_RECEIPTS_ALL, aliased AR_HDR, which supplies the receipt header. AR_CASH_RECEIPT_HISTORY_ALL and AR_RECEIVABLE_APPLICATIONS_ALL provide the GL date context and the applied, unapplied, and on-account amounts, the latter computed through correlated subqueries that invoke the OKL_ACCOUNTING_UTIL package function ROUND_AMOUNT for currency rounding. HR_OPERATING_UNITS supplies the operating unit name, while HZ_PARTIES and HZ_CUST_ACCOUNTS provide the customer name and account number. XLE_ENTITY_PROFILES supplies the legal entity. IBY_EXT_BANK_ACCOUNTS and the receipt method join (RM) drive the remittance bank attributes, and OKL_TRX_CSH_RCPT_ALL_B and OKL_TXL_RCPT_APPS_ALL_B link the view back to the leasing transaction and application side. The package OKL_ACCOUNTING_UTIL is referenced in the SELECT list rather than as a join.

Key Columns

• CASH_RECEIPT_ID, RECEIPT_NUMBER, RECEIPT_DATE — receipt identity and date.
• ORG_ID, ORG_NAME, LEGAL_ENTITY_ID, LEGAL_ENTITY_NAME — operating unit and legal entity context.
• CUSTOMER_NAME, CUSTOMER_ACCOUNT — party and customer account from HZ.
• RECEIPT_AMOUNT, APPLIED_AMOUNT, UNAPPLIED_AMOUNT, ONACCOUNT_AMOUNT — receipt value and its application status split, each rounded via OKL_ACCOUNTING_UTIL.ROUND_AMOUNT.
• CURRENCY_CODE, CURRENCY_CONVERSION_TYPE, CURRENCY_CONVERSION_RATE, CURRENCY_CONVERSION_DATE, GL_DATE — currency and accounting date attributes.
• RECEIPT_METHOD_ID, RECEIPT_METHOD, REMIT_BANK_NAME, REMIT_BANK_ACCOUNT, REMIT_BANK_ACCOUNT_ID — the remittance bank detail. REMIT_BANK_ACCOUNT is the column surfaced as the effective bank account number (BANK_ACCOUNT_NUM from the receipt method record).
• ATTRIBUTE_CATEGORY, ATTRIBUTE1, ATTRIBUTE2, ATTRIBUTE3 … — the descriptive flexfield style attributes carried on the receipt header.

Common Use Cases and Queries

Typical use cases include reconciling lease receipts by bank account, reporting applied versus unapplied cash by customer and operating unit, and feeding downstream cash-position extracts. A sample query searching on bank account number:

SELECT receipt_number, receipt_date, customer_name, receipt_amount, applied_amount, unapplied_amount, remit_bank_name, remit_bank_account FROM apps.okl_receipt_details_uv WHERE remit_bank_account = '1234567890' ORDER BY receipt_date DESC;

Because the view exposes only a subset of AR_CASH_RECEIPTS_ALL columns, consumers requiring additional receipt attributes should join back to that table on CASH_RECEIPT_ID. Query performance is best when filters are applied to the driving receipt header (receipt number, date range, org_id), since the applied, unapplied and on-account amounts are computed by scalar subqueries per row.