Results for “okl_txl_quote_lines_tl”

48 results




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

Overview

OKL_TXL_QUOTE_LINES_TL is the translation (MLS) table for the Oracle Leasing and Finance Management (OKL) quote line entity in Oracle EBS 12.1.1 and 12.2.2. It stores the language-dependent or translatable attributes of quote line records whose language-independent attributes reside in the base table OKL_TXL_QUOTE_LINES_B. Oracle's Multi-Lingual Support (MLS) architecture pairs a base table with a "_TL" companion whenever descriptive or user-facing text (such as a description) must be maintained in multiple installed languages.

The object is owned by the OKL schema and is documented as VALID under ETRM 12.2.2 with a physical schema of 10 columns. From a heuristic Data Vault modeling perspective, the FK structure classifies this object as standalone, meaning it does not participate in a traditional parent-child foreign key relationship within the documented metadata. In Data Vault terms, it would be modeled as a satellite attached to the quote-line hub, carrying the descriptive, language-qualified attributes.

Key Information Stored

The table follows the standard MLS pattern, where translation rows are keyed by both the entity identifier and a language code. The documented columns include:

  • ID — The surrogate/foreign identifier linking the translation row back to the corresponding quote line in OKL_TXL_QUOTE_LINES_B.
  • LANGUAGE — The NLS language code (e.g., US, DE, FR) identifying which translation this row carries.
  • SOURCE_LANG — The source language of the translatable text, used by MLS to indicate the origin language when a translation falls back to the base language.
  • SFWT_FLAG — The "Seed/Force Word Translation" flag, a standard MLS indicator used by Oracle's translation framework to manage dictionary-driven text.
  • DESCRIPTION — The primary translatable text column, holding the language-specific description of the quote line.
  • CREATED_BY, CREATION_DATE — Standard WHO audit columns recording the creating user and timestamp.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — WHO audit columns capturing the last modifying user, timestamp, and login session.

The primary key is OKL_TXL_QUOTE_LINES_TL_PK (ID, LANGUAGE), and the unique index OKL_TXL_QUOTE_LINES_TL_U1 (ID, LANGUAGE) serves as the business-key candidate, enforcing one translated row per quote line per language. The surrogate component is ID; LANGUAGE completes the composite business key.

Common Use Cases and Queries

This table is queried whenever quote line descriptions must be presented in the user's session language. A typical join retrieves the translated description alongside base attributes:

  • SELECT b.id, t.description FROM okl.okl_txl_quote_lines_b b, okl.okl_txl_quote_lines_tl t WHERE b.id = t.id AND t.language = USERENV('LANG');
  • Reporting on all available translations for a quote line by grouping on ID and listing LANGUAGE values.
  • Auditing translation maintenance by filtering on LAST_UPDATED_BY or LAST_UPDATE_DATE.
  • Fallback reporting that selects SOURCE_LANG when a target-language translation is missing, supporting MLS completion checks across installed languages.

Related Objects

The most significant partner object is OKL_TXL_QUOTE_LINES_B, joined on the shared ID column; the "_B" table supplies language-independent columns while the "_TL" table supplies DESCRIPTION and language metadata. The OKL quote and quote-line APIs and concurrent programs that create and maintain quote lines write to the "_B" base and require corresponding "_TL" rows for each installed language. Within the OKL schema, related translatable entities such as quote headers and their translation tables follow the same MLS convention, and reporting views built on the quote line entity typically join the "_B" and "_TL" tables transparently. Because the documented FK structure classifies this object as standalone, no formal foreign keys are declared; relationships are enforced at the application layer via the shared ID.