Search Results fnd_security_groups_tl_pk

Overview

FND_SECURITY_GROUPS_TL is the translation table for FND_SECURITY_GROUPS in the Oracle E-Business Suite Application Object Library (FND) schema, owned by APPLSYS. A security group is the highest-level grouping construct in EBS, used to partition a single database and application installation into logically isolated data domains — most commonly separating a base EBS installation from a Multi-Org-enabled or hosted environment, or from Oracle's own seeded groups such as "Standard" and "Oracle Self-Service Web Applications." The _TL suffix identifies this as a multilingual (MLS) table that stores the translatable descriptive attributes — principally the security group name and description — for each installed language, while non-translatable and structural attributes remain in the base table. This design lets the same security group be presented to users in their native language without duplicating the underlying configuration.

The supplied metadata classifies this object heuristically as standalone from a Data Vault modeling perspective. Read as a modeling suggestion rather than a physical constraint, this reflects the fact that FND_SECURITY_GROUPS_TL neither acts as a pure hub (its keys are not solely business identifiers independent of the parent) nor as a clean link between unrelated hubs; functionally it behaves as a satellite-like translation store attached to the parent security group, with the parent-child relationship expressed through the shared surrogate key rather than a separately mined foreign key.

Key Information Stored

The table carries 11 documented columns. The principal ones are:

• SECURITY_GROUP_ID — surrogate identifier inherited from the base table, tying each translation row to its parent security group.
• LANGUAGE — the language code for the translated row; together with SECURITY_GROUP_ID, it forms the primary key FND_SECURITY_GROUPS_TL_PK.
• SECURITY_GROUP_NAME — the translated, user-facing name of the security group.
• DESCRIPTION — the translated long description.
• SOURCE_LANG — the language in which the row was originally authored, used by the MLS framework for fallback resolution.
• ZD_EDITION_NAME — the edition marker used by EBS's Edition-Based Redefinition (EBR) infrastructure in 12.2.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns tracking who created and last modified each row.

Two unique indexes serve as business-key candidates: FND_SECURITY_GROUPS_TL_U1 on (SECURITY_GROUP_ID, LANGUAGE, ZD_EDITION_NAME) enforces one translation per group per language per edition, while FND_SECURITY_GROUPS_TL_U2 on (SECURITY_GROUP_NAME, LANGUAGE, ZD_EDITION_NAME) enforces uniqueness of the translated name within a language. U2 is significant because it prevents two security groups from sharing the same localized name.

Common Use Cases and Queries

Typical reporting and administration scenarios include listing all security groups with their descriptions in a target language, validating that every group has a translation for each installed language, and auditing name uniqueness across locales. A representative query follows:

• SELECT t.security_group_id, t.security_group_name, t.description FROM fnd_security_groups_tl t WHERE t.language = USERENV('LANG');
• Joining to the base table (FND_SECURITY_GROUPS) on SECURITY_GROUP_ID to combine structural attributes with translated text.
• Detecting missing translations by comparing FND_LANGUAGES against rows returned by this table.

Related Objects

• FND_SECURITY_GROUPS — parent "base" table; joined on SECURITY_GROUP_ID.
• FND_SECURITY_GROUPS_TL_PK / _U1 / _U2 — primary and unique constraints enforcing identity and uniqueness.
• FND_LANGUAGES — defines the installed languages that drive available LANGUAGE values.
• FND_APPLICATION — applications are assigned to security groups, linking configuration to translated group names.
• FND_USER / FND_RESPONSIBILITY — assignments ultimately surface the localized security group name to end users.
• FND_SECURITY_GROUPS_VL — the MLS view commonly queried instead of the raw base and _TL tables.