Search Results as_issue_groups_tl




Overview
Explore in AI Chat

Overview

AS_ISSUE_GROUPS_TL is the translation (MLS) table for Issue Groups within the Oracle E-Business Suite Sales Foundation product (AS). Issue Groups are used to categorize and group customer issues or service requests, providing a classification mechanism that supports reporting, routing, and assignment logic. The "_TL" suffix indicates that this table stores language-specific, translated values for descriptive attributes, while the base table (AS_ISSUE_GROUPS_B, not documented here) holds the language-independent definition columns. It resides in the OSM schema and is marked VALID in the ETRM catalog.

From a modeling perspective, the metadata's heuristic Data Vault classification identifies this object as standalone — it carries no dependent entities and is treated as an independent reference. In Data Vault terms, AS_ISSUE_GROUPS_TL functions effectively as a surrounding satellite attached to the AS_ISSUE_GROUPS_B hub: it describes the issue group entity over a language dimension rather than acting as a link between entities. All translation rows for a given ISSUE_GROUP_ID are held in this satellite, keyed by the addition of LANGUAGE.

Key Information Stored

The table documents 10 columns. The most significant are:

  • ISSUE_GROUP_ID — The surrogate identifier inherited from the base table; combined with LANGUAGE it forms the primary key (AS_ISSUE_GROUPS_TL_PK) and the unique business-key index (AS_ISSUE_GROUPS_TL_U1).
  • LANGUAGE — The NLS language code identifying the locale of the translated row (for example, US or ZH). Together with ISSUE_GROUP_ID it establishes one row per translated language.
  • NAME — The translated display name of the issue group, the principal user-facing text subject to multi-language support.
  • SOURCE_LANG — The source language of the base record, used to identify the authoritative language from which translations are derived.
  • SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing row-level security and data access scoping.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN, which record who created or altered each translated row and when.

The surrogate primary key (ISSUE_GROUP_ID, LANGUAGE) is distinct from the unique index AS_ISSUE_GROUPS_TL_U1, which is composed of the same columns and therefore also enforces the business rule that no more than one translation per language may exist for an issue group.

Common Use Cases and Queries

Because Issue Groups appear in user-facing LOVs and lookups, the most frequent pattern is joining translations back to the base table filtered by the runtime language, with a fallback to SOURCE_LANG when no translation exists. A representative pattern:

  • Retrieve the translated name for the current session language: SELECT t.NAME FROM OSM.AS_ISSUE_GROUPS_TL t WHERE t.ISSUE_GROUP_ID = :p_id AND t.LANGUAGE = USERENV('LANG');
  • Report all available translations for an issue group across languages, ordering by LANGUAGE.
  • Data-quality checks that identify base records missing a translation in a target deployment language.
  • Join to FND_SECURITY_GROUPS on SECURITY_GROUP_ID to restrict results to the caller's authorized security scope.

Related Objects

The most significant related objects include:

  • AS_ISSUE_GROUPS_B — the base language-independent issue group table; join on ISSUE_GROUP_ID.
  • FND_SECURITY_GROUPS — referenced by the SECURITY_GROUP_ID foreign key; join on SECURITY_GROUP_ID.
  • FND_LANGUAGES — supplies valid LANGUAGE values used in the composite key.
  • AS_ISSUE_GROUPS_TL_PK / AS_ISSUE_GROUPS_TL_U1 — the primary key and unique index enforcing translation uniqueness.
  • Sales Foundation (AS) issue-group lookup and API components — consume the translated NAME through standard LOV and validation logic.