Results for “inv_hdr”

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

Overview

The view APPS.OKL_BPD_INVEST_TRX_SUM_UV is a reporting and integration object within the Oracle E-Business Suite Lease and Finance Management (OKL) module. It presents a consolidated, denormalized summary of investor-related transactions, specifically those processed through the Bill Presentment and Distribution (BPD) investor invoicing flow. The view surfaces investor invoice data alongside payment schedule detail, enabling downstream reporting, reconciliation, and extraction of investor billing information.

Its central role is to expose a single, query-ready row set that merges accounts receivable invoice headers, investor master data, address information, receipt methods, payment terms, and the associated payment schedule lines. Because the view draws together both invoice-level and payment-schedule-level attributes, it is particularly useful for investor statements, aging reports, and integration interfaces that must communicate amounts due and remaining balances per investor agreement. The inclusion of PAY_SCHED (from AR_PAYMENT_SCHEDULES_ALL) as a core join makes this view a natural source when users search for "pay_sched," since it links each investor invoice to its scheduled installments and due dates.

Underlying Base Objects

The view is defined over a set of documented base objects that span the Receivables and Trading Community Architecture schemas, unified through the APPS synonyms and helper packages:

• RA_CUSTOMER_TRX (synonym) — the invoice header source, aliased as INV_HDR. Rows are restricted to the investor billing context via interface_header_context = 'OKL_INVESTOR'.
• AR_PAYMENT_SCHEDULES_ALL (synonym) — the payment schedule source, aliased as PAY_SCHED, joined on customer_trx_id. This supplies due dates and amount fields.
• HZ_CUST_ACCOUNTS and HZ_PARTIES (synonyms) — provide the investor account number and investor party name.
• AR_RECEIPT_METHODS (synonym) — supplies the payment method name via an outer join on receipt_method_id.
• RA_TERMS_VL (view) — supplies the payment term name.
• OKX_CUST_SITE_USES_V (view) — provides the bill-to address components for the transaction.
• OKL_ACCOUNTING_UTIL (package) — used to format monetary amounts into the invoice currency.
• ARP_ADDR_LABEL_PKG (package) — a documented referenced object associated with address handling utilities.

Key Columns

• investor_agreement — sourced from interface_header_attribute1, identifying the investor agreement associated with the invoice.
• investor_number / investor_name — the customer account number and party name of the investor.
• invoice_id / invoice_number / invoice_date / invoice_currency_code — the customer transaction identity and currency.
• due_date — from the payment schedule, the scheduled due date of the installment line.
• payment_method / payment_term — receipt method and payment term descriptions.
• invoice_amount — formatted from amount_due_original, the original amount due on the schedule line.
• balance — formatted from amount_due_remaining, the open remaining balance.
• address1–address4, city, state, postal_code, country — bill-to address attributes for the investor site.
• org_id — the operating unit identifier, supporting multi-org querying and security.

Common Use Cases and Queries

Typical scenarios include investor aging analysis, open balance reporting, and reconciliation of scheduled installments against billed invoices. Because the view exposes both invoice_amount and balance per schedule line, it supports straightforward open-item reporting.

A representative query to retrieve investor balances by agreement:

SELECT investor_agreement,
       investor_name,
       invoice_number,
       due_date,
       invoice_amount,
       balance
FROM   apps.okl_bpd_invest_trx_sum_uv
WHERE  org_id = :p_org_id
ORDER  BY investor_agreement, due_date;

A second query to isolate amounts still outstanding for a given investor:

SELECT invoice_number,
       payment_term,
       payment_method,
       balance
FROM   apps.okl_bpd_invest_trx_sum_uv
WHERE  investor_number = :p_investor_number
AND    balance > 0;

These patterns make the view well suited for custom concurrent programs, BI Publisher investor statements, and integration extracts requiring payment schedule detail joined to investor invoice headers.