Results for “okl_txl_assets_tl”

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

Overview

OKL_TXL_ASSETS_TL is the translatable (TL) child table of OKL_TXL_ASSETS_B within the OKL — Leasing and Finance Management module of Oracle E-Business Suite. It exists to satisfy Oracle's Multi-Lingual Support (MLS) architecture, which separates language-independent attributes from language-dependent descriptive text. The base table OKL_TXL_ASSETS_B stores the structural and transactional columns of the asset record, while OKL_TXL_ASSETS_TL holds the translated descriptive columns, allowing each asset to be represented in any installed language without duplicating the master row.

In the documented 12.2.2 schema, the table resides in the OKL schema and exposes ten columns. Its primary key, OKL_TXL_ASSETS_TL_PK, is defined on (ID, LANGUAGE), which is the standard MLS pattern combining the surrogate entity identifier with the NLS language code. A unique index, OKL_TRX_ASSETS_TL_U1, mirrors the same (ID, LANGUAGE) column pair. Because no foreign keys are documented, the heuristic Data Vault classification returned by the mining process is standalone. In dimensional modelling terms this is best treated as a satellite attached to the asset hub represented by OKL_TXL_ASSETS_B rather than as an independent hub or link.

Key Information Stored

The most significant columns fall into three groups: identity, translation metadata, and audit.

• ID — Surrogate identifier inherited from OKL_TXL_ASSETS_B. Together with LANGUAGE it forms the primary key OKL_TXL_ASSETS_TL_PK and the business-key candidate OKL_TRX_ASSETS_TL_U1.
• LANGUAGE — NLS language code indicating which installed language the row's descriptive text is written in. Every asset may have one row per active language.
• SOURCE_LANG — The language of the source record from which this translation originated, used by MLS to resolve the "source" language when a translation is missing.
• SFWT_FLAG — The standard MLS "Seed/Force/Write/Translate" flag that governs whether the translation row is seeded, overridden, or synchronized with the base record.
• DESCRIPTION — The translated descriptive text for the asset. This is the principal language-dependent payload of the table; it is the column most commonly surfaced in reporting and user interfaces.
• CREATED_BY, CREATION_DATE — Standard WHO audit columns recording the user and timestamp of initial row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard WHO audit columns recording the user and timestamp of the most recent change to the row.
• LAST_UPDATE_LOGIN — The login identifier associated with the last update, used for session-level auditing.

Because the operational key is a composite of ID and LANGUAGE, any query that ignores LANGUAGE risks returning multiple rows per asset on a multi-language instance.

Common Use Cases and Queries

The table is typically joined to its base table to present asset descriptions in a specific language. A representative query filters on the session language or a supplied parameter:

• Retrieve the description for a specific asset in English: SELECT t.description FROM okl.okl_txl_assets_tl t WHERE t.id = :asset_id AND t.language = 'US';
• Join base and translation to report assets in the user's language: SELECT b.id, t.description FROM okl.okl_txl_assets_b b, okl.okl_txl_assets_tl t WHERE b.id = t.id AND t.language = USERENV('LANG');
• Detect missing translations: compare base IDs against translation rows filtered by a target language to find assets lacking localized descriptions.
• Audit recent changes: SELECT id, language, last_updated_by, last_update_date FROM okl.okl_txl_assets_tl WHERE last_update_date > SYSDATE - 30;

Typical reporting scenarios include asset inventory listings, lease contract documentation, and localization completeness checks ahead of a multi-language rollout.

Related Objects

• OKL_TXL_ASSETS_B — The base (non-translatable) table. Joined on ID; it supplies all language-independent asset attributes.
• OKL_TXL_ASSETS_V — The MLS view (where present) that unions base and translation columns and automatically restricts rows to the session language.
• OKL_TXL_ASSETS_TL_PK — The primary key constraint/index on (ID, LANGUAGE) that enforces uniqueness.
• OKL_TRX_ASSETS_TL_U1 — The unique index on (ID, LANGUAGE) serving as the business-key candidate.
• FND_LANGUAGES — The language reference table that validates LANGUAGE and SOURCE_LANG values.
• OKL_TXL_ASSETS_B_..._FK — Parent integrity is conventionally maintained through the base table's own key; the TL row's ID must ultimately resolve to OKL_TXL_ASSETS_B.

Application program interfaces that maintain asset records (such as the OKL asset APIs) write to both tables in a single transaction, ensuring translation rows are inserted or updated whenever the base record changes.