Results for “match_required_yn”

40 results




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

Overview

OKL_TRX_AP_INVOICES_V is a PL/SQL view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the OKL (Leasing and Finance Management) product family and serves as a consolidated collection of all OKL transactions that generate Payables invoices. The view presents one row per OKL transaction record participating in the Payables invoicing flow, exposing both transactional attributes and translated descriptive text. Because OKL lease and loan contracts frequently trigger supplier invoicing — through payment schedules, funding requests, or fee events — this view is the principal read-only interface used to bridge leasing transaction data with the Oracle Payables subledger. Its status is VALID, indicating it is a supported, compiled database object in the APPS schema.

Underlying Base Objects

The documented view metadata lists two referenced base objects, both accessed through synonyms:

  • OKL_TRX_AP_INVOICES_B — the base table holding one row per AP invoice-generating OKL transaction, including identifiers, amounts, currency information, and foreign keys to related OKL and non-OKL entities.
  • OKL_TRX_AP_INVOICES_TL — the translated table supplying language-specific descriptive columns, joined on the transaction identifier so that DESCRIPTION and related text honor the session language.

The view definition selects every column from the base table TAPB (aliased OKL_TRX_AP_INVOICES_B) and joins to TAPT (OKL_TRX_AP_INVOICES_TL) primarily to retrieve SFWT_FLAG and DESCRIPTION. ROWID from the base table is surfaced as ROW_ID, and OBJECT_VERSION_NUMBER supports Oracle's optimistic locking convention. In this sense the view is a thin, denormalized projection over the two base objects rather than a computed or aggregated result set.

Key Columns

Common Use Cases and Queries

Typical usage includes reconciliation of OKL-generated invoices against Payables, reversal tracing, and operational reporting on invoicing status by contract. To locate all original transactions and their reversals:

SELECT a.id, a.invoice_number, a.trx_status_code, a.amount, a.tap_id_reverses FROM apps.okl_trx_ap_invoices_v a ORDER BY a.tap_id_reverses NULLS FIRST, a.id;

To isolate reversal records referencing a specific original invoice:

SELECT id, invoice_number, amount, trx_status_code FROM apps.okl_trx_ap_invoices_v WHERE tap_id_reverses = :p_original_tap_id;

For reporting by contract, join TRY_ID (TRY stands for Transaction Resource; in OKL it associates with the underlying contract/lease) to the appropriate OKL transaction tables and filter on TRX_STATUS_CODE and SET_OF_BOOKS_ID to restrict output by ledger. Because the view exposes ROW_ID and OBJECT_VERSION_NUMBER, it is also suitable for downstream integrations that require row-level identification and concurrency control when writing back to the base table.