Search Results as_issues_tl_u1

Overview

OSM.AS_ISSUES_TL is the translation (TL) table that stores the language-dependent, translatable attributes of the Issue entity within Oracle E-Business Suite. It is owned by the OSM schema (Oracle Services / CRM Online Services), carries the FND Design Data reference AS.AS_ISSUES_TL, and is classified as VALID in the ETRM metadata. The "_TL" suffix is a standard EBS convention: each translatable base table has a companion _TL table whose rows are keyed jointly by the entity identifier and a LANGUAGE code, allowing the same logical record to carry distinct NAME and DESCRIPTION values for every installed language. The base table AS_ISSUES holds non-translatable attributes, while AS_ISSUES_TL holds only the columns requiring multilingual support. The object resides in the APPS_TS_SEED tablespace with PCT Free 10, reflecting its role as seeded, reference-style configuration data.

From a Data Vault modeling perspective, the metadata classifies this table heuristically as standalone, meaning it has no outbound foreign keys to other business entities (its only documented FK is to FND_SECURITY_GROUPS). This suggests modeling it as a self-contained hub or reference satellite keyed on the composite business key (ISSUE_ID, LANGUAGE), rather than as a link joining multiple hubs.

Key Information Stored

The table contains 11 documented columns. The most significant are:

• ISSUE_ID (NUMBER, mandatory) — the issue identifier; the surrogate relationship that ties each translation row back to its parent issue record.
• LANGUAGE (VARCHAR2(30)) — the language code for this translated row.
• NAME (VARCHAR2(60)) — the translated issue name.
• DESCRIPTION (VARCHAR2(240)) — the translated issue description.
• SOURCE_LANG (VARCHAR2) — the source language from which the translation was derived.
• SECURITY_GROUP_ID (NUMBER) — subscriber identifier for CRM Online Services.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard EBS Who columns capturing audit and concurrency information.

The primary key is AS_ISSUES_TL_PK on (ISSUE_ID, LANGUAGE), and the unique index AS_ISSUES_TL_U1 likewise covers (ISSUE_ID, LANGUAGE), confirming the composite pair as the business-key candidate. The surrogate key of the underlying entity is ISSUE_ID, while LANGUAGE supplies the translation dimension.

Common Use Cases and Queries

Typical usage centers on multilingual reporting and joining translated text to base issue data. A common pattern restricts results to a single language:

• Retrieve the name and description for a specific issue in a given language by filtering on ISSUE_ID and LANGUAGE.
• Build language-comparison reports by grouping on LANGUAGE to audit which issues have complete translations across installed languages.
• Detect missing translations by comparing the set of ISSUE_ID values in AS_ISSUES against those present in AS_ISSUES_TL for a target language.
• Audit change history using LAST_UPDATE_DATE and LAST_UPDATED_BY to track recent edits to translated text.

A representative query joins the base and translation tables on ISSUE_ID and constrains LANGUAGE to the session's active language, ensuring users see text in their preferred locale. Because the table is seeded data in APPS_TS_SEED, queries are generally read-only in production.

Related Objects

• OSM.AS_ISSUES — the base (non-translatable) parent table joined on ISSUE_ID.
• FND_SECURITY_GROUPS — referenced by the SECURITY_GROUP_ID foreign key for subscriber/CRM security partitioning.
• OSM.AS_ISSUES_TL# — the underlying table object referenced internally by the synonym.
• FND_LANGUAGES — provides the LANGUAGE code domain used by the translation key.
• AS_ISSUES_TL_PK / AS_ISSUES_TL_U1 — the primary key constraint and unique index enforcing one translation row per issue per language.