Results for “okl_bpd_invoice_hdr_bc_v”

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

Overview

The OKL_BPD_INVOICE_HDR_BC_V view is an Oracle E-Business Suite dictionary object owned by the APPS schema in the OKL (Leasing and Finance Management) product. It presents a consolidated header-level picture of lease and finance invoices, joining receivables transaction data with contract and customer information. The view's primary purpose is to supply header information for consolidated invoice reporting and integration, exposing both balanced consolidated invoice headers produced by OKL and their individual receivables invoice counterparts through a UNION ALL structure. It is defined as a valid database view and depends on a mixture of OKL consolidated receivables tables, Oracle Receivables tables, and OKX customer/party views.

Underlying Base Objects

The documented base objects of the view span several modules. The consolidated invoicing side relies on OKL_CNSLD_AR_HDRS_B (headers), OKL_CNSLD_AR_LINES_B (lines), and OKL_CNSLD_AR_STRMS_B (streams). Contract context is drawn from OKC_K_HEADERS_B, while receivables data comes from AR_PAYMENT_SCHEDULES_ALL, RA_CUSTOMER_TRX_ALL, and RA_CUSTOMER_TRX_LINES_ALL. Customer and party information is supplied through HZ_CUST_ACCOUNTS, HZ_PARTIES, and the OKX views OKX_CUST_SITE_USES_V and OKX_PARTIES_V. The view text indicates joins linking consolidated header IDs to lines and streams, streams to receivables invoices via RECEIVABLES_INVOICE_ID, and contracts to bill-to site uses and lessee party roles. The package ARP_ADDR_LABEL_PKG is also referenced, indicating address formatting support for the bill-to site name.

Key Columns

Column names in this view map directly to header-level reporting needs. INVOICE_ID carries the consolidated invoice number on the first branch and the receivables transaction number on the second. AR_INVOICE_ID is intentionally nulled on the consolidated branch but populated with CUSTOMER_TRX_ID on the receivables branch — a distinction important for the user's search term. Other fields include CUSTOMER_NAME, BILL_TO_SITE_NAME, CURRENCY_CODE, DUE_DATE, AMOUNT, computed BALANCE (from SUM(AMOUNT_DUE_REMAINING)), INVOICE_DATE, BILL_TO_SITE_USE_ID, CUSTOMER_ACCT_ID, ORG_ID, CUSTOMER_NUMBER, and a literal INVOICE_TYPE value of 'OKL-CONS-INV'. The CONTRACT_NUMBER column is present but commented out in the consolidated branch, effectively null. Because the view aggregates by consolidated invoice, the consolidated branch returns one row per header, while the receivables branch returns distinct transaction-level rows.

Common Use Cases and Queries

Typical usage covers lease consolidated invoice reporting, reconciliation between OKL consolidated headers and AR transactions, and customer-facing extracts requiring a single invoice header feed. A basic query retrieving the AR side of the UNION is:

• SELECT INVOICE_ID, AR_INVOICE_ID, CUSTOMER_NAME, DUE_DATE, AMOUNT, BALANCE FROM APPS.OKL_BPD_INVOICE_HDR_BC_V WHERE AR_INVOICE_ID IS NOT NULL;
• SELECT ORG_ID, CUSTOMER_NUMBER, SUM(AMOUNT), SUM(BALANCE) FROM APPS.OKL_BPD_INVOICE_HDR_BC_V GROUP BY ORG_ID, CUSTOMER_NUMBER;
• SELECT * FROM APPS.OKL_BPD_INVOICE_HDR_BC_V WHERE INVOICE_ID = :p_invoice OR AR_INVOICE_ID = :p_ar_invoice_id;

Because the view unions consolidated and individual invoices, queries should filter on AR_INVOICE_ID to isolate true AR transactions or on INVOICE_TYPE to identify consolidated entries. Joining AR_INVOICE_ID back to RA_CUSTOMER_TRX_ALL provides drill-down to the underlying receivables transaction. Performance is influenced by the join across payment schedules and customer tables, so queries filtering by ORG_ID and invoice identifiers are advisable.