Results for “ibi_id”

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

Overview

The OKL_XTL_PAY_INVS_V view is a reporting and integration object within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environment, owned by the APPS schema and validated against the OKL — Lease and Finance Management product. As documented in the ETRM repository, the view "stores information used to create invoice distributions." In practice, it presents a flattened, language-resolved projection of the lease payment invoice data maintained by the OKL payables and receivables integration flows, allowing downstream processes, reports, and external interfaces to consume invoice distribution details without joining the underlying base and translation tables directly. The view carries a status of VALID and is exposed as a standard synonym within the APPS schema, making it addressable from custom concurrent programs, BI Publisher data templates, and SQL-based extracts.

Underlying Base Objects

The view is defined over two documented base objects, referenced through synonyms:

• OKL_XTL_PAY_INVS_B — the base ("_B") table that stores the transaction-level invoice distribution rows, including amounts, accounting dates, distribution accounts, and who-columns.
• OKL_XTL_PAY_INVS_TL — the translation ("_TL") table that stores the language-dependent descriptive attributes, such as the invoice description and stream type.

The view joins these on the common identifier XLPB.ID = XLPT.ID and filters rows using XLPT.LANGUAGE = USERENV('LANG'), so each query returns only the description and stream type matching the session language. The ROW_ID column is derived from the base table's physical ROWID, preserving a direct row locator for the underlying record.

Key Columns

Among the columns exposed, several are central to how lease invoice distributions are processed:

• DIST_CODE_COMBINATION_ID — the identifier of the accounting flexfield combination applied to the distribution line; this is the column most relevant to the user's search term "dist_code_combination_id." It links the distribution to the General Ledger code combination used when the invoice is accounted.
• ID, OBJECT_VERSION_NUMBER, LINE_NUMBER, LINE_TYPE — the primary record identifier, optimistic locking version, and the line sequence and type that classify each distribution row.
• AMOUNT and ACCOUNTING_DATE — the monetary value and the date on which the distribution is recognised.
• INVOICE_LINE_ID, TPL_ID, PID_ID, TAP_ID, IBI_ID, XPI_ID_DETAILS — foreign references linking the row to its invoice line and originating lease, payment, and transaction sources.
• DESCRIPTION, STREAM_TYPE, TAX_CODE, SFWT_FLAG — translated and control attributes carried from the associated translation and source records.
• ORG_ID plus the standard ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15, and CREATED_BY/CREATION_DATE/LAST_UPDATED_BY/LAST_UPDATE_DATE audit columns — providing multi-org security and descriptive flexibility.

Common Use Cases and Queries

Typical uses include reconciling lease invoice distributions to General Ledger, extracting distribution accounts for interface files, and validating that a payment invoice line carries a valid code combination before accounting. A representative query retrieving distributions and their associated accounting flexfield follows:

• SELECT id, line_number, line_type, amount, accounting_date, dist_code_combination_id, tax_code, org_id FROM apps.okl_xtl_pay_invs_v WHERE invoice_line_id = :p_invoice_line_id;
• SELECT id, dist_code_combination_id, amount, accounting_date FROM apps.okl_xtl_pay_invs_v WHERE org_id = :p_org_id AND accounting_date BETWEEN :p_start AND :p_end ORDER BY accounting_date;
• SELECT v.id, v.amount, gcc.concatenated_segments FROM apps.okl_xtl_pay_invs_v v, apps.gl_code_combinations_kfv gcc WHERE v.dist_code_combination_id = gcc.code_combination_id;

Because the view already resolves the language-specific description and stream type, and exposes DIST_CODE_COMBINATION_ID directly, it is well suited to joins against GL code combination views and to downstream accounting extraction without additional base-table joins.