Results for “okl_trx_ar_adjsts_tl”
45 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OKL_TRX_AR_ADJSTS_TL is the translation table for the Oracle Leasing and Finance Management (OKL) transaction adjustment entity. Under Oracle E-Business Suite 12.1.1 and 12.2.2, the OKL schema follows the Oracle Multi-Lingual Support (MLS) architecture, in which user-entered descriptive text is stored separately in a _TL table keyed by language. This object holds the translatable columns extracted from OKL_TRX_AR_ADJSTS_B, the base table that carries the installation-independent attributes of an AR adjustment associated with an OKL contract transaction. In the ETRM documentation taxonomy, the heuristic Data Vault classification for this object is standalone, suggesting that OKL_TRX_AR_ADJSTS_TL is best modeled as an independent satellite-like structure attached directly to the OKL_TRX_AR_ADJSTS_B hub while being associated with a LANGUAGE attribute in the composite key. Its documented status in the OKL schema is VALID.
Key Information Stored
The table exposes ten documented columns. The composite primary key, enforced by index OKL_TRX_AR_ADJSTS_TL_PK, is formed by ID and LANGUAGE. ID is the surrogate foreign key that ties each translation row back to a single row in OKL_TRX_AR_ADJSTS_B, while LANGUAGE designates the NLS language code (for example, US for American English) in which the corresponding text is stored. A second unique index, OKL_TRX_AR_ADJSTS_TL_U1, repeats the (ID, LANGUAGE) pair, meaning the business key and the primary key coincide for this object.
The principal payload is COMMENTS, which holds the descriptive or free-form text associated with the adjustment in the target language. SOURCE_LANG records the language in which the source comment was originally authored, allowing runtime comparisons between the translation language and the base language. SFWT_FLAG is the standard MLS "seed for translation" indicator that marks a row as translatable. The remaining columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — form the standard Oracle WHO audit trail that records who inserted or last modified each translation row and when, together with the session login identifier.
Common Use Cases and Queries
The most frequent access pattern is joining the translation table back to its base table for multilingual reporting. A typical query retrieves adjustments for the user's session language:
SELECT b.id, t.comments FROM okl.okl_trx_ar_adjsts_b b, okl.okl_trx_ar_adjsts_tl t WHERE b.id = t.id AND t.language = USERENV('LANG');- Administrators maintain translations using the standard MLS forms, which insert or update rows in OKL_TRX_AR_ADJSTS_TL while auditing the WHO columns.
- Auditors may query LAST_UPDATED_BY and LAST_UPDATE_DATE to trace when a specific comment was re-translated for a business locale.
- Data migration routines frequently compare t.language with t.source_lang to identify languages that have not yet received a translation.
Because the table is effectively a satellite of the adjustment entity, queries should always constrain by LANGUAGE to avoid duplicating rows across installed languages.
Related Objects
The principal relationship is with OKL_TRX_AR_ADJSTS_B, joined on ID, which supplies all non-translatable attributes and the adjustment identity. The unique index OKL_TRX_AR_ADJSTS_TL_U1 and primary key OKL_TRX_AR_ADJSTS_TL_PK constrain the (ID, LANGUAGE) pair. In the broader OKL model, the base adjustment table references AR adjustment and contract-transaction objects such as the OKL transaction header and the AR adjustment identifier, so reporting joins often flow through OKL_TRX_AR_ADJSTS_B to the underlying contract and receivable tables. Standard MLS reference data, including the FND_LANGUAGES lookup, governs the values permitted in LANGUAGE, while FND_USER resolves CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN to application users. Together these objects provide the complete audit and translation context for OKL AR adjustment comments.
-
Translatable columns from OKL_TRX_AR_ADJSTS_B, per MLS standards
-
Translatable columns from OKL_TRX_AR_ADJSTS_B, per MLS standards
-
View: OKL_TRX_AR_ADJSTS_V 12.1.1
OKL writeoffs which generate AR adjustments
APPS.OKL_TRX_AR_ADJSTS_V·↳ OKL_TRX_AR_ADJSTS_B·↳ OKL_TRX_AR_ADJSTS_TL·Explore OKL module →
-
View: OKL_TRX_AR_ADJSTS_V 12.2.2
OKL writeoffs which generate AR adjustments
APPS.OKL_TRX_AR_ADJSTS_V·↳ OKL_TRX_AR_ADJSTS_B·↳ OKL_TRX_AR_ADJSTS_TL·Explore OKL module →
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
eTRM - OKL Tables and Views 12.2.2
Translatable columns from OKL_XTL_SELL_INVS_B, per MLS standards
-
eTRM - OKL Tables and Views 12.1.1
Translatable columns from OKL_XTL_SELL_INVS_B, per MLS standards
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - OKL Tables and Views 12.1.1
Translatable columns from OKL_XTL_SELL_INVS_B, per MLS standards
-
eTRM - OKL Tables and Views 12.2.2
Translatable columns from OKL_XTL_SELL_INVS_B, per MLS standards