Search Results cs_transaction_types_tl_pk




Overview
Explore in AI Chat

Overview

CS_TRANSACTION_TYPES_TL is the translation (TL) table for the Oracle EBS Service (CS) module's transaction type definition. In Oracle Applications, base tables ending in _B store language-independent attributes, while the companion _TL table stores the language-dependent, translatable descriptive attributes — in this case the name and description of each service transaction type. The table resides in the CS schema and is identified in the Electronic Technical Reference Manual (ETRM) as VALID for releases 12.1.1 and 12.2.2.

From a dimensional or Data Vault modeling perspective, the heuristic classification mined from the foreign key structure indicates this is a standalone object — it is not a dependent child hub or link in the strict Data Vault sense. It functions conceptually like a satellite attached to the _B base table because it carries descriptive, versioned-by-language attributes keyed to the parent business entity. This classification is offered as a modeling suggestion rather than a mandated schema design; EBS itself uses a language-row pattern rather than Data Vault constructs.

Key Information Stored

The table's documentation lists 12 physical columns. The most significant, grouped by purpose, are:

  • TRANSACTION_TYPE_ID — The surrogate/system-generated identifier of the transaction type. It forms part of the composite primary key CS_TRANSACTION_TYPES_TL_PK alongside LANGUAGE, and maps back to the base table CS_TRANSACTION_TYPES_B.
  • LANGUAGE — The installed language code (for example US for American English) identifying which language's text is stored in this row. It is the second component of the primary key.
  • SOURCE_LANG — Indicates the language the record was originally created in, supporting EBS's translation inheritance and the "translated / untranslated" status logic used by the Translation (TL) utilities.
  • NAME — The translatable, user-facing name of the transaction type. This is a documented business-key candidate: unique index CS_TRANSACTION_TYPES_TL_U2 enforces (NAME, LANGUAGE, ZD_EDITION_NAME).
  • DESCRIPTION — The translatable long description of the transaction type, presented to users in forms and reports.
  • ZD_EDITION_NAME — The editioning column introduced under the EBS online patching architecture (12.2.x), used to isolate edition-specific rows; it appears in both unique indexes U1 and U2.
  • SECURITY_GROUP_ID — The multi-tenant/access-control grouping column, documented as a foreign key to FND_SECURITY_GROUPS.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN capture who created and last modified each translated row and when. LAST_UPDATED_BY and CREATED_BY reference FND_USER.

Business-key candidates, per the documented unique indexes, are CS_TRANSACTION_TYPES_TL_U1 (TRANSACTION_TYPE_ID, LANGUAGE, ZD_EDITION_NAME), which effectively enforces one row per language per transaction type per edition, and U2 on (NAME, LANGUAGE, ZD_EDITION_NAME), which prevents duplicate names within a language. The surrogate primary key is (TRANSACTION_TYPE_ID, LANGUAGE).

Common Use Cases and Queries

This table is central to any reporting or integration that must display transaction type names in the user's session language. Typical scenarios include joining to the base table to list transaction types for a service request, validating lookups in a concurrent program, or building multilingual reports.

A representative join resolves the translated name for a given language:

SELECT b.transaction_type_id, tl.name, tl.description
FROM   cs_transaction_types_b b,
       cs_transaction_types_tl tl
WHERE  b.transaction_type_id = tl.transaction_type_id
AND    tl.language = USERENV('LANG');

Another common pattern locates untranslated rows where SOURCE_LANG differs from the installed languages, supporting the Translation Wizard and "Translate" concurrent requests. Reporting queries frequently filter on ZD_EDITION_NAME to restrict rows to the current edition under 12.2.x online patching. Form-level lookups (LOVs) in the Service module also rely on this table when rendering the Transaction Type flexfield.

Related Objects

  • CS_TRANSACTION_TYPES_B — The base, language-independent table; join on TRANSACTION_TYPE_ID. This is the primary parent of the TL row.
  • FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID, controlling row-level access in multi-org/multi-tenant deployments.
  • FND_USER — Referenced implicitly by CREATED_BY and LAST_UPDATED_BY audit columns.
  • FND_LANGUAGES — The installed-language definition that joins to LANGUAGE and SOURCE_LANG.
  • FND_APPLICATION / CS lookup views — Consumed by the Service forms and the Transaction Type LOV.
  • Translation (TL) concurrent programs — Maintain and propagate NAME/DESCRIPTION across languages.

Because the ETRM classifies it as standalone, no downstream child tables depend directly on it through foreign keys; its principal dependencies flow upward to the base table and the security group definition.