Search Results okc_line_styles_tl




Overview
Explore in AI Chat

Overview

OKC_LINE_STYLES_TL is the translatable (language-specific) child table of OKC_LINE_STYLES_B within the OKC – Contracts Core module of Oracle E-Business Suite, and it exists to satisfy Oracle's Multi-Lingual Support (MLS) standard. Line styles in OKC define the reusable formatting and text-placement attributes applied to contract clauses and contract line text, and because the descriptive text attached to a line style must be presented in each installed language, the translatable columns are separated from the base table into this _TL table. In Oracle EBS 12.1.1 and 12.2.2 the table resides in the OKC schema and is reported as VALID in the data dictionary. The Base table OKC_LINE_STYLES_B holds the language-independent attributes (including the primary key ID), while OKC_LINE_STYLES_TL stores the language-dependent NAME and DESCRIPTION rows, one row per installed language per line style. Reporting against OKC_LINE_STYLES_TL alone therefore returns repeated logical entities, and queries should be filtered on LANGUAGE or joined to FND_LANGUAGES so that exactly one translation is returned per style.

The ETRM relationship metadata classifies this object heuristically as standalone in Data Vault terms. In practice this is best read as a modeling suggestion: the translation table behaves as a satellite-like extension of the base line-style entity, keyed by the parent identifier plus LANGUAGE, rather than as an independent hub or a link between two business entities. When modeling the Contracts Core domain in a warehouse, OKC_LINE_STYLES_TL is most naturally treated as a descriptive satellite attached to the OKC_LINE_STYLES_B hub.

Key Information Stored

The documented physical schema for 12.2.2 carries 13 columns. The most significant are:

  • ID – Surrogate identifier of the parent line style; the join column back to OKC_LINE_STYLES_B. It forms part of the primary key OKC_LINE_STYLES_TL_PK together with LANGUAGE.
  • LANGUAGE – The installed Oracle language code for the translated row (for example US, DE, FR). It is the second component of the primary key OKC_LINE_STYLES_TL_PK and is the column that must be constrained when a single translation is required.
  • SOURCE_LANG – The language from which the current translation was derived, used by MLS to track translation provenance (for example, whether the row originated from the base language).
  • SFWT_FLAG – The Sub-Flow / "seed from which translation" style indicator maintained by the MLS framework to denote the translation status of the row.
  • NAME – The translated user-visible name of the line style, displayed in the Contracts authoring and clause-formatting user interfaces.
  • DESCRIPTION – The translated free-text description explaining the purpose or appearance of the line style.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – The standard EBS WHO columns capturing audit and concurrency information for each translated row.
  • SECURITY_GROUP_ID – The multi-tenant security grouping identifier, with a documented foreign key reference to FND_SECURITY_GROUPS.
  • ZD_EDITION_NAME – The editioning column introduced for EBS 12.2 online patching, identifying the edition in which the row is visible.

Two unique indexes are documented: OKC_LINE_STYLES_TL_PK on (ID, LANGUAGE), which is the true primary key, and OKC_LINE_STYLE_TL_U1 on (ID, LANGUAGE, ZD_EDITION_NAME), which is the business-key candidate reflecting the editioning-aware uniqueness enforced in 12.2.2.

Common Use Cases and Queries

The principal use case is resolving the display text of a line style for a specific language when building contract clause or contract template reports. A typical pattern joins the translation table to the base table and restricts the language:

  • Translated line-style list: SELECT b.id, t.name, t.description FROM okc_line_styles_b b, okc_line_styles_tl t WHERE b.id = t.id AND t.language = USERENV('LANG') ORDER BY t.name;
  • Fallback to base language: use a correlated subquery or an outer join on LANGUAGE = 'US' where no translation exists, so that untranslated styles still appear in the report.
  • Translation completeness audit: SELECT id, COUNT(*) FROM okc_line_styles_tl GROUP BY id HAVING COUNT(DISTINCT language) < (SELECT COUNT(*) FROM fnd_languages WHERE installed_flag IN ('I','B')); identifies styles missing translations.
  • Edition-aware extraction for 12.2: restrict to zd_edition_name = 'SET1' (or the current run edition) to avoid returning duplicate rows across editions during online patching.
  • Seeded versus customized review: filtering on SECURITY_GROUP_ID distinguishes multi-tenant groups, while SOURCE_LANG and SFWT_FLAG indicate how a translation was seeded versus manually maintained.

Because the table holds only text, it is not used for transactional processing; it is queried primarily by the Contracts Core UI layer, by concurrent programs that publish contract formats, and by customer-built BI extracts that require localized clause formatting.

Related Objects

  • OKC_LINE_STYLES_B – the base line-style table; joined on ID and the source of all language-independent attributes.
  • OKC_LINE_STYLES_VL** – the MLS view that unions the base and translation tables and is the object the application normally queries.
  • FND_SECURITY_GROUPS – referenced through OKC_LINE_STYLES_TL.SECURITY_GROUP_ID, linking translated rows to the security group that owns them.
  • FND_LANGUAGES – provides the valid LANGUAGE codes and installed-language flags used to filter and validate translations.
  • OKC_CLAUSES_B / OKC_CLAUSES_TL – clause text objects whose formatting and display reference line styles through the Contracts Core clause-line-style relationships.
  • OKC_TEMPLATES_B / OKC_TEMPLATES_TL – contract templates that reference line styles when rendering formatted contract text and which inherit the same MLS translation structure.
  • FND_APPLICATION / FND_APPLICATION_TL – context objects confirming that OKC_LINE_STYLES_TL belongs to the OKC application and is patched across editions in 12.2.2.

Relationships to these objects should be joined on ID for the base table, on LANGUAGE for language resolution, and on ZD_EDITION_NAME where editioning is in use.