Results for “okl_services_tl”

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

Overview

OKL_SERVICES_TL is the translation table for OKL_SERVICES_B within the Oracle E-Business Suite Leasing and Finance Management module (OKL). In Oracle EBS, the "_TL" suffix identifies tables that store language-dependent, translatable descriptive columns, while the corresponding "_B" table holds the base or language-independent attributes. This object therefore provides multilingual text for service definitions used throughout lease and finance contract processing.

The heuristic Data Vault classification derived from the foreign key structure is standalone. From a modeling perspective, this suggests the table is neither a pure hub, link, nor satellite and carries no outward-referencing foreign keys to other OKL entities. Its functional role, however, aligns closely with a satellite pattern: it holds descriptive, attribute-level text keyed by the parent entity identifier and language, tracking audit columns typical of an EBS transactional record.

Key Information Stored

The table contains 12 documented columns. The most significant are listed below.

• ID — Surrogate identifier for the service, shared with the parent OKL_SERVICES_B record. It forms the leading component of the primary key.
• LANGUAGE — The language code identifying the translation. Combined with ID, it forms the trailing component of the primary key.
• SOURCE_LANG — Indicates the source language from which the translation was derived, supporting EBS multilingual seeding.
• SFWT_FLAG — The "Seed/Flexfield/Whatever Translation" flag used by the translation framework to control how a row is treated during language installation and upgrade.
• SHORT_DESCRIPTION — A brief translated name or label for the service.
• DESCRIPTION — The full translated description of the service.
• COMMENTS — Additional translated free-text notes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing who created and last modified each translation row, when, and through which login session.

The documented primary key is OKL_SVCT_PK (ID, LANGUAGE). A unique index, OKL_SVCT_UC1 (ID, LANGUAGE), serves as the business-key candidate and enforces the same uniqueness at the index level, guaranteeing one translation row per service per language. There is no separate surrogate key beyond the composite ID and LANGUAGE pair.

Common Use Cases and Queries

Typical usage centers on retrieving readable service text for a given language, joining translations back to the base table, and auditing multilingual coverage.

• Retrieve the English description for a specific service:
  SELECT short_description, description FROM okl_services_tl WHERE id = :service_id AND language = USERENV('LANG');
• List all translations for one service to review localization completeness.
• Report services missing a translation in a target language by comparing against OKL_SERVICES_B.
• Populate custom concurrent programs or OAF pages that display service labels dynamically based on the runtime session language.
• Data migration and reconciliation scripts that validate the one-row-per-language rule enforced by OKL_SVCT_UC1.

Related Objects

The following objects are most significant to OKL_SERVICES_TL, joined through the shared ID column:

• OKL_SERVICES_B — The base table holding language-independent service attributes; join on OKL_SERVICES_B.ID = OKL_SERVICES_TL.ID.
• OKL_SERVICES_VL — The translated view that typically unions the base and translation tables to present a single localized row.
• Service-related setup and contract line tables within OKL reference the parent service ID and thus depend indirectly on the translation supplied here.
• EBS multilingual (MLS) framework objects that manage the SOURCE_LANG and SFWT_FLAG columns during language installation and upgrades.

When querying, always constrain by LANGUAGE to avoid returning multiple rows for a single service ID.