Results for “okl_language”

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

Overview

OKL_AR_REC_APP_REF_VL is an APPS-owned database view in the OKL – Lease and Finance Management module, shipped valid across Oracle EBS 12.1.1 and 12.2.2. It presents a contract-oriented perspective on Accounts Receivable activity by linking receivable application records to the OKL external AR header and line source tables. In practice, the view answers the question "which receivable application corresponds to which lease contract transaction line," exposing contract status, transaction type, stream type, and inventory organization context alongside the AR application identifier.

Because TCA/AR transactional data is stored in normalized form, the contract references required by lease reporting are distributed across AR and OKL extension entities. This view performs that consolidation in a single definition, making it useful for reporting, reconciliation, and integration queries where the calling process needs both the AR identity (RECEIVABLE_APPLICATION_ID, SOURCE_ID) and the OKL descriptive context (contract status, transaction type, stream type) without joining the underlying tables manually. The search term ar_activity_details reflects a frequent entry point for this view, since AR_ACTIVITY_DETAILS supplies the bridge between AR applications and customer transaction lines.

Underlying Base Objects

The view is defined over seven documented base objects, accessed through APPS synonyms:

• AR_RECEIVABLE_APPLICATIONS_ALL — the primary AR application table; supplies RECEIVABLE_APPLICATION_ID, aliased as OKL_REC_APP_ID.
• AR_ACTIVITY_DETAILS — the activity/application detail table linking applications to transaction lines; joined on SOURCE_ID with SOURCE_TABLE = 'RA'.
• RA_CUSTOMER_TRX_LINES_ALL — transaction lines, restricted to LINE_TYPE = 'LINE' and INTERFACE_LINE_CONTEXT = 'OKL_CONTRACTS'.
• OKL_EXT_AR_LINE_SOURCES_B / _TL — lease external AR line sources and their translation table; provide SOURCE_ID, stream type, and line descriptions.
• OKL_EXT_AR_HEADER_SOURCES_B / _TL — lease external AR header sources and translations; provide header statuses, transaction type, and language.

The join path runs from receivable applications to activity details to customer transaction lines, then through INTERFACE_LINE_ATTRIBUTE14 to the OKL line sources, and finally via header and line extension identifiers to the header and translation tables. The WHERE clause enforces the OKL_CONTRACTS context, so only lease-related AR activity is surfaced.

Key Columns

• OKL_REC_APP_ID — the AR receivable application identifier; the anchor key for the row.
• OKL_TXD_ID — the source identifier from the OKL external AR line sources, identifying the contract transaction detail.
• OKL_LANGUAGE — language of the translated header record.
• OKL_CONTRACT_STATUS — status of the lease contract as recorded on the header source.
• OKL_INV_AGRMNT_STATUS — status of the associated invoice agreement.
• OKL_STREAM_TYPE_NAME — the billing stream type for the transaction line.
• OKL_TRANSACTION_TYPE_NAME — the lease transaction type.
• OKL_TRANS_LINE_DESCRIPTION — descriptive text for the transaction line.
• OKL_INVENTORY_ORG_NAME — inventory organization associated with the line, where applicable.

Common Use Cases and Queries

Typical scenarios include reconciling AR receipts and applications back to lease contracts, reporting applied amounts by contract status or transaction type, and supplying integration extracts that require contract descriptors keyed to AR application IDs. A basic query:

SELECT okl_rec_app_id, okl_txd_id, okl_contract_status, okl_transaction_type_name, okl_trans_line_description FROM apps.okl_ar_rec_app_ref_vl WHERE okl_contract_status = 'ACTIVE';

To group applied activity by stream type:

SELECT okl_stream_type_name, COUNT(*) FROM apps.okl_ar_rec_app_ref_vl GROUP BY okl_stream_type_name;

Because the view is already restricted to OKL_CONTRACTS, no additional interface-context filter is required. Join to AR_RECEIVABLE_APPLICATIONS_ALL on the application ID when monetary amounts from the AR side are needed, as this view exposes identifiers and contract attributes rather than amounts.