Results for “okl_bpd_inv_srch_v”

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

Overview

OKL_BPD_INV_SRCH_V is a read-only database view owned by the APPS schema within the Oracle Lease and Finance Management (OKL) product family. Its documented purpose is to supply the context region of the BPD (Business Process Document) invoice search page, presenting consolidated receivables invoice data joined to customer, party, and receipt-method attributes. In Oracle EBS 12.1.1 and 12.2.2, the view is consumed by the lease management search pages and by any custom reporting or integration layer that needs a denormalized snapshot of invoice records for lease and finance contracts.

The view is significant to the user's keyword "receipt_method_name" because it exposes the RECEIPT_METHOD_NAME column, which resolves the receipt method identifier on the receivables invoice to a human-readable name from AR_RECEIPT_METHODS. This lets downstream consumers display, filter, or integrate on the payment instrument configured for each invoice without an additional lookup.

Underlying Base Objects

The view is defined over the following documented objects:

• OKL_BPD_AR_INVOICES_V (VIEW) — the primary driver, supplying invoice, balance, currency, and consolidation columns.
• HZ_CUST_ACCOUNTS (SYNONYM) and HZ_PARTIES (SYNONYM) — provide the customer account and party name.
• OKL_INVOICE_FORMATS_V (VIEW) — supplies invoice format identifier and name via an outer join on INF_NAME.
• AR_RECEIPT_METHODS (SYNONYM) — joined with an outer join to resolve RECEIPT_METHOD_NAME.
• AR_ADDRESSES_V (VIEW) — outer-joined on BILL_TO_SITE_USE_ID to deliver the formatted bill-to address.
• ARP_ADDR_LABEL_PKG and ARP_ADDR_PKG (PACKAGES) — invoked for address formatting logic.

All joins to the invoice-format, receipt-method, and address objects are outer joins, so invoice rows survive even when the related lookup data is absent.

Key Columns

• IXX_ID — the customer account identifier used to join to HZ_CUST_ACCOUNTS.
• RECEIVABLES_INVOICE_ID and CONSOLIDATED_INVOICE_NUMBER — the receivables invoice and its consolidation reference.
• IRM_ID and RECEIPT_METHOD_NAME — the receipt method identifier and its decoded name.
• DUE_DATE, DATE_CONSOLIDATED, CURRENCY_CODE — invoice timing and currency attributes.
• AMOUNT_DUE_ORIGINAL and BALANCE — original amount and remaining balance.
• PARTY_NAME and ADDRESS — customer name and formatted bill-to address.
• INF_ID and NAME — invoice format identifier and name (defaulted to 'NONE' when absent).
• ORG_ID — the operating unit for multi-org security.

Common Use Cases and Queries

Typical usage includes invoice search pages, lease billing reconciliations, and custom extracts filtered by receipt method. A representative query follows:

• SELECT consolidated_invoice_number, party_name, receipt_method_name, balance FROM okl_bpd_inv_srch_v WHERE org_id = :p_org_id AND receipt_method_name = :p_method;
• SELECT ixx_id, due_date, amount_due_original, currency_code FROM okl_bpd_inv_srch_v WHERE due_date BETWEEN :p_from AND :p_to;

Because the view is a standard APPS-owned object, it should be queried directly rather than recreated, ensuring consistency with Oracle's supported lease management search behavior.