Results for “okl_asset_components_tl”

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

Overview

OKL_ASSET_COMPONENTS_TL is a translation table in the OKL (Oracle Lease and Finance Management) schema. It stores the language-dependent, translatable attributes of records whose language-independent definitions are held in the base table OKL_ASSET_COMPONENTS_B. The _TL suffix follows the standard Oracle E-Business Suite multilanguage design pattern, in which a _B table carries non-translatable columns and a companion _TL table carries the descriptive text for each installed language. The object is flagged VALID in the ETRM 12.2.2 data model and is documented as holding translatable data of OKL_ASSET_COMPONENTS_B.

In functional terms, the asset components represent the constituent items that make up a leased asset within a contract, and the translation table allows the short description, long description, and comments attached to those components to be presented in the user's session language. From a Data Vault modeling perspective, the metadata's heuristic classification is standalone; that is, the entity does not participate in the mined foreign-key relationships of the surrounding model and may be treated as an independent or peripheral structure rather than a true hub, link, or satellite. This classification is a modeling suggestion only, derived from the absence of FK dependencies, and does not affect the table's operational role as the descriptive extension of the base table.

Key Information Stored

The two most important columns are those that constitute the primary key OKL_ASOT_PK:

• ID — the surrogate identifier of the asset component record; it matches the corresponding ID in OKL_ASSET_COMPONENTS_B and is the first component of the composite primary key.
• LANGUAGE — the language code of the translated row; it is the second component of the composite primary key and, together with ID, uniquely identifies each translation.
• SOURCE_LANG — the language from which the current translation was derived, used for determining whether re-translation is required.
• SHORT_DESCRIPTION — a brief translated description of the asset component, typically the value displayed in lists of values and inquiry screens.
• DESCRIPTION — the full translated description of the asset component.
• COMMENTS — free-form translated remarks associated with the component.
• SFWT_FLAG — the Oracle "Seed/Force/Wherever/Translate" style flag used to control whether the row is a seed row subject to translation synchronization.

Standard EBS WHO columns are also present and complete the 12-column footprint: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN. The business-key candidate is the composite of ID and LANGUAGE; no separate unique index beyond OKL_ASOT_PK is documented. The surrogate key is therefore ID (with LANGUAGE as the discriminator).

Common Use Cases and Queries

The table is accessed almost exclusively through joins to its base table, filtered by the session or reporting language. A typical query returns the translated descriptions for a component:

• Retrieve the current-language description: SELECT t.short_description, t.description FROM okl.okl_asset_components_tl t WHERE t.id = :component_id AND t.language = USERENV('LANG');
• Fetch translations in every installed language for a single component, useful for audit or globalization review: join on ID only and order by LANGUAGE.
• Populate a component description list of values for a lease contract entry screen, joining OKL_ASSET_COMPONENTS_TL to OKL_ASSET_COMPONENTS_B on ID.
• Detect missing or stale translations by comparing SOURCE_LANG to LANGUAGE, or by outer-joining the _B and _TL tables on ID and LANGUAGE to find base records without a corresponding translated row.

Because the table is descriptive rather than transactional, reporting usage centers on descriptive lookup and multilingual verification rather than on volume analysis. Queries should always constrain LANGUAGE to avoid returning one row per installed language.

Related Objects

The most significant related objects, based on the documented primary key and the standard _B/_TL design pairing, are:

• OKL_ASSET_COMPONENTS_B — the base table holding language-independent attributes; joined to OKL_ASSET_COMPONENTS_TL on B.ID = TL.ID. This is the principal and mandatory relationship.
• OKL_ASSET_COMPONENTS_VL — the standard translated view that selects the appropriate TL row for the session language; it joins _B and _TL on ID.
• OKL_ASSET_COMPONENTS_V — the base-oriented view over the component entity.
• OKL_ASSET_COMPONENTS — the API package (or public synonym) used to create and maintain component records, which populates the _TL table on insert and update.
• OKL_ASSET_COMPONENTS_VL and the associated design-time/translation utilities (for example, the Oracle Translation (XLIFF) framework) that use SFWT_FLAG and SOURCE_LANG when seeding and synchronizing translations.
• FND_LANGUAGES — the standard reference table validating the LANGUAGE and SOURCE_LANG values.

All joins should be driven by the ID column, which is the shared business identifier across the _B, _TL, and _VL objects.