Results for “okl_ajl_id”

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

Overview

The view OKL_AR_ADJ_KHR_IA_REF_VL is an APPS-owned database view within the Oracle Leasing and Finance Management (OKL) module. It presents a joined, denormalized projection that links Oracle Receivables adjustment records to their corresponding OKL transaction adjustment lines and their external Receivables interface metadata. The view is a core component of the OKL-to-Receivables integration layer, allowing technical users and reporting tools to reconcile lease-related adjustments with the descriptive attributes maintained in the external AR source extension tables. The _VL suffix conventionally denotes a validated list-style view intended primarily for value-list and lookup-style querying, though it can be queried directly for reporting.

The view carries a status of VALID and is documented for both EBS 12.1.1 and 12.2.2. Because the object name begins with OKL and references Receivables adjustment identifiers, it is frequently surfaced in integration and reconciliation reporting for lease contracts and inventory agreements.

Underlying Base Objects

The view is defined over five referenced base objects, all exposed in the APPS schema as synonyms:

• OKL_EXT_AR_HEADER_SOURCES_B — header-level external AR source records that anchor the header extension identifier.
• OKL_EXT_AR_HEADER_SOURCES_TL — translatable header-level attributes (language-specific descriptive text).
• OKL_EXT_AR_LINE_SOURCES_B — line-level external AR source records, including the source table and source ID mapping.
• OKL_EXT_AR_LINE_SOURCES_TL — translatable line-level attributes.
• OKL_TXL_ADJSTS_LNS_ALL_B — the OKL transaction adjustment lines base table, joined via AJL.ID.

The join logic keys the line source to the adjustment line through RXL.SOURCE_TABLE = 'OKL_TXL_ADJSTS_LNS_B' and RXL.SOURCE_ID = AJL.ID. The header and line extensions are linked by header extension and line extension identifiers, and the translated header and line rows are constrained to matching languages (RXHL.LANGUAGE = RXLL.LANGUAGE).

Key Columns

• RECEIVABLES_ADJUSTMENT_ID — the AR adjustment identifier sourced directly from the adjustment line; this is the column most commonly used to join back to Receivables.
• OKL_AJL_ID — the internal OKL adjustment line identifier (AJL.ID).
• OKL_LANGUAGE — the language code under which the translated attributes were resolved.
• OKL_CONTRACT_STATUS — the contract status attribute from the header source.
• OKL_INV_AGRMNT_STATUS — the inventory agreement status from the header source.
• OKL_STREAM_TYPE_NAME — the stream type name associated with the line source.
• OKL_TRANSACTION_TYPE_NAME — the transaction type name from the header source.
• OKL_TRANS_LINE_DESCRIPTION — the descriptive text for the transaction line.
• OKL_INVENTORY_ORG_NAME — the inventory organization name tied to the transaction line.

Common Use Cases and Queries

The primary use case is resolving a receivables_adjustment_id to its OKL lease context. A typical reconciliation query retrieves all adjustment-linked lease attributes for a given AR adjustment:

• Reconciling lease adjustment transactions posted to Receivables against their originating contract or inventory agreement.
• Enriching Receivables adjustment reports with OKL contract status, transaction type, stream type, and inventory organization descriptors.
• Building value-list or lookup queries keyed on language and adjustment identifiers.

Sample query:

SELECT receivables_adjustment_id,
       okl_ajl_id,
       okl_contract_status,
       okl_transaction_type_name,
       okl_stream_type_name,
       okl_trans_line_description,
       okl_inventory_org_name
FROM   apps.okl_ar_adj_khr_ia_ref_vl
WHERE  receivables_adjustment_id = :p_adjustment_id
AND    okl_language = USERENV('LANG');

Because the underlying tables are large transactional structures, queries should be filtered by the adjustment identifier or language to avoid full scans, and the view should be accessed with appropriate APPS responsibility and reporting privileges.