Results for “tehl_contract_status”

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

Overview

OKL_MLS_EXTRACT_HDR_VL is an APPS-owned, VALID database view within the OKL – Leasing and Finance Management product of Oracle E-Business Suite. It functions as a header-level MLS (Multi-Language Support) extract object, exposing translated descriptive attributes of a leasing contract alongside its associated subledger accounting event identifier. The view is designed primarily to serve extraction, reporting, and integration processes that require contract header information in a specific language, paired with the corresponding XLA event context.

The suffix "_VL" denotes a "value list" or translated view pattern common in EBS: base descriptive columns are sourced from the "_TL" (translated) table so that the appropriate language row is returned. In this view, TEHL.LANGUAGE is exposed directly, making the language context of each extracted row explicit, which is essential when the same contract must be represented across multiple language installations or reporting locales.

The view is relevant to the user search term "tehl_contract_status." This term maps directly to the derived column TEHL_CONTRACT_STATUS, whose value originates from the CONTRACT_STATUS attribute of the header translation table (aliased TEHL). Consumers searching for contract status in the context of MLS extraction should retrieve it from this column rather than from untranslated base tables.

Underlying Base Objects

The view is defined over four base objects, all referenced through APPS synonyms:

• OKL_TRX_CONTRACTS_ALL (alias TCN) – the primary leasing contract header table. The join key is TCN.ID, which links the contract to both its extension record and the XLA event.
• OKL_TRX_EXTENSION_B (alias TEH) – the header extension base table. The view joins TCN.ID = TEH.SOURCE_ID (+) with the restriction TEH.SOURCE_TABLE(+) = 'OKL_TRX_CONTRACTS', filtering extension rows to the contract header entity. TEH.HEADER_EXTENSION_ID bridges to the translation table.
• OKL_TRX_EXTENSION_TL (alias TEHL) – the translated extension table. Joined via TEH.HEADER_EXTENSION_ID = TEHL.HEADER_EXTENSION_ID(+), it supplies the language-dependent columns such as contract status, invoice agreement status, transaction type name, and operating unit name.
• XLA_EVENTS_GT (alias XE) – the Subledger Accounting events global temporary table. It is constrained to APPLICATION_ID = 540 (the OKL application) and linked to the contract via XE.SOURCE_ID_INT_1 = TCN.ID.

Because the joins to TEH and TEHL are outer joins, contract rows are preserved even when no extension or translation record exists.

Key Columns

• EVENT_ID – The XLA accounting event identifier from XLA_EVENTS_GT, providing the link to subledger accounting processing.
• LANGUAGE – The language of the translated header record, sourced from OKL_TRX_EXTENSION_TL.
• TEHL_CONTRACT_STATUS – The contract status from the header translation table; the direct answer to the "tehl_contract_status" search term.
• TEHL_INV_AGRMNT_STATUS – The invoice agreement status of the contract header.
• TEHL_TRANSACTION_TYPE_NAME – The descriptive name of the leasing transaction type.
• TEHL_CHR_OPERATING_UNIT_NAME – The operating unit name associated with the contract header.

Common Use Cases and Queries

This view is typically used when extracting contract header data for a specific accounting event, or when producing language-specific reports of contract status. A representative query retrieving contract status and related attributes by event follows:

• SELECT event_id, language, tehl_contract_status, tehl_inv_agrmnt_status, tehl_transaction_type_name, tehl_chr_operating_unit_name FROM apps.okl_mls_extract_hdr_vl WHERE event_id = :p_event_id;
• Filtering by language: SELECT event_id, tehl_contract_status FROM apps.okl_mls_extract_hdr_vl WHERE language = 'US';
• Joining to other extract views on EVENT_ID to assemble a complete MLS extraction record set.

Because the repository stores the view definition for reference rather than as a supported API, integration logic should treat OKL_MLS_EXTRACT_HDR_VL as a read-only reporting object and avoid direct DML against it.