Results for “ixx_id”

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

Overview

The view OKL_BPD_AR_INVOICES_V resides in the APPS schema within Oracle E-Business Suite and belongs to the OKL (Lease and Finance Management) product family. As documented in the ETRM metadata for release 12.2.2, its purpose is to display Payable Invoice details. The view consolidates Receivables transaction data with payment schedule information, exposing a denormalized set of columns suitable for reporting, integration, and inquiry purposes where lease-related billing data must be presented alongside customer invoice information. Because it draws from multiple core Receivables objects, it functions as a convenience layer that shields consumers from the multi-table joins required to correlate customer transactions with their outstanding balances.

Underlying Base Objects

The documented referenced base objects for this view are:

• AR_PAYMENT_SCHEDULES_ALL (synonym) — supplies payment schedule rows including due date, original amount due, and remaining balance.
• OKX_CUST_SITE_USES_V (view) — supplies customer account site use information used for bill-to resolution.
• RA_CUSTOMER_TRX_ALL (synonym) — the primary source of customer transaction header data such as transaction number, currency, and status.
• RA_CUST_TRX_TYPES_ALL (synonym) — provides the transaction type name used as the invoice classification.
• ARP_ADDR_LABEL_PKG (package) — referenced for address labeling functionality supporting the site use data.

The joins bind each customer transaction to its transaction type, its payment schedules, and, in an outer join, its bill-to site use. The BILL_TO_SITE_USE_ID linkage to OKX_CUST_SITE_USES_V is implemented with the (+) outer-join operator, so transactions lacking a matching site use are still returned.

Key Columns

The view exposes columns that map an Accounts Receivable invoice to its lease billing context. Notable columns include:

• CLASS_ID — sourced from RACTRX.CUST_TRX_TYPE_ID, the identifier of the transaction type. This is the column most commonly referenced when filtering by invoice class.
• CLASS — the transaction type name from RA_CUST_TRX_TYPES_ALL.NAME.
• INVOICE_ID — the CUSTOMER_TRX_ID, uniquely identifying the invoice.
• TRX_NUMBER — the user-facing invoice number.
• DUE_DATE, AMOUNT_DUE_ORIGINAL, and BALANCE — payment schedule attributes describing the obligation and its outstanding remainder.
• CURRENCY_CODE, STATUS, and DATE_CONSOLIDATED — transaction currency, status, and consolidation date.
• CUSTOMER_ID, IXX_ID, SITE_USE_ID, BILL_TO_SITE_USE_ID, RECEIPT_METHOD_ID, INF_NAME, ORG_ID, and PAY_SCH_CLASS — supporting identifiers for customer, site, receipt method, interface attributes, operating unit, and the payment schedule class.

Common Use Cases and Queries

Because the view already joins invoice headers, transaction types, and payment schedules, it is typically used to report on lease-related receivable balances and to drive downstream processing by invoice class.

A representative query filtering on class is:

• SELECT invoice_id, trx_number, class_id, class, balance FROM okl_bpd_ar_invoices_v WHERE class_id = :p_class_id;

Additional scenarios include listing all open balances by customer or org, extracting due-date driven aging information, and feeding integration interfaces that require the invoice class (CLASS_ID) to determine processing rules. When the metadata does not document a precise business rule, the transaction type identified by CLASS_ID should be validated against RA_CUST_TRX_TYPES_ALL configuration for the relevant operating unit.