Results for “security_group_name”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_SECURITY_GROUPS_VL is a seeded, valid view owned by the APPS schema within the Oracle E-Business Suite Application Object Library (FND) product. It exposes security group definitions in the language of the current session. Security groups are a foundational construct in EBS multi-organization and multi-Org Access Control (MOAC) architecture: they partition operating units and inventory organizations into logical groupings that govern which data a responsibility may access. This view provides a translation-aware, user-friendly projection of that configuration data — pairing the surrogate key and developer-facing key with the translated name and description — making it the standard read-only interface for reports, concurrent programs, integrations, and ad hoc queries that need to resolve or enumerate security groups.

Because it is a view rather than a table, it holds no data of its own; it is a query-time join over the security group base tables. This ensures that any change to a security group definition is immediately visible through the view without synchronization.

Underlying Base Objects

The documented view text joins two base objects:

• FND_SECURITY_GROUPS (referenced via a synonym) — the base table holding the security group definition and its control columns.
• FND_SECURITY_GROUPS_TL (referenced via a synonym) — the translation table holding language-specific SECURITY_GROUP_NAME and DESCRIPTION values.

The join condition is B.SECURITY_GROUP_ID = T.SECURITY_GROUP_ID, combined with T.LANGUAGE = USERENV('LANG'). The _VL suffix denotes a "view with language," meaning the row returned reflects the translated text appropriate to the current session language. Because USERENV('LANG') is evaluated at query time, the same statement can return different names depending on the environment in which it executes.

Key Columns

• SECURITY_GROUP_ID — The primary surrogate key of the security group. This is the value stored on related configuration and Org Access records.
• SECURITY_GROUP_KEY — The developer-facing, language-independent identifier for the security group, suitable for lookups that must remain stable across languages.
• SECURITY_GROUP_NAME — The translated display name retrieved from FND_SECURITY_GROUPS_TL for the session language.
• DESCRIPTION — The translated descriptive text for the security group.
• ROW_ID — The base-table ROWID, exposed for row-level addressing.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS who-columns providing audit lineage for the definition.

Common Use Cases and Queries

Typical scenarios include validating a security group during responsibility or user setup, populating LOVs in custom forms and OAF pages, and joining Org Access data to a human-readable group name for reporting. Because it resolves the session language, it is also useful when the same report must render correctly for users across locales.

To enumerate all security groups with translated names:

• SELECT security_group_id, security_group_key, security_group_name, description FROM fnd_security_groups_vl ORDER BY security_group_name;

To resolve a single group by its stable key:

• SELECT security_group_id, security_group_name FROM fnd_security_groups_vl WHERE security_group_key = :p_key;

To join MOAC configuration to readable names:

• SELECT sgv.security_group_name, so.organization_id FROM fnd_security_groups_vl sgv, fnd_org_access so WHERE so.security_group_id = sgv.security_group_id ORDER BY sgv.security_group_name, so.organization_id;

Note that a security group may have a row in the base table without a matching translation row for the current session language, in which case the inner join excludes it from the result set. Code relying on this view should therefore treat it as a filtered, language-specific interface rather than a guaranteed superset of all defined groups.