Results for “fnd_security_groups”

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

Overview

FND_SECURITY_GROUPS is an Application Object Library (FND) table owned by the APPLSYS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the definition of service bureau data security groups, the construct used to partition application data across logically isolated security partitions — most commonly encountered when a single EBS instance is operated as a shared service bureau on behalf of multiple organizations, or when set-based data segregation is required within one installation. Each row identifies one security group and carries the standard EBS audit columns and, in 12.2.2, the editioning column ZD_EDITION_NAME that supports online patching.

From a dimensional modeling perspective, the mined foreign-key structure suggests a hub-leaning classification. The table is referenced by a very large number of child tables through SECURITY_GROUP_ID, and it holds no foreign keys of its own toward other business entities. This pattern is consistent with a durable business key registry — a hub — surrounded by dependent data. The classification should be treated as a modeling suggestion rather than a documented Oracle design intent.

Key Information Stored

The documented physical schema defines eight columns. The most important are:

• SECURITY_GROUP_ID — the surrogate primary key, enforced by FND_SECURITY_GROUPS_PK and also the leading column of unique index FND_SECURITY_GROUPS_U1. It is the value propagated to every dependent table in the instance and is the join key for all security-partition filtering.
• SECURITY_GROUP_KEY — the business-key candidate, enforced by unique index FND_SECURITY_GROUPS_UK and also the leading column of FND_SECURITY_GROUPS_U2. This is the user-meaningful identifier for the group.
• CREATED_BY, CREATION_DATE — standard EBS who-columns recording the creating user and timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns tracking the last modifying user, the modification timestamp, and the login session associated with the change.
• ZD_EDITION_NAME — the editioning column introduced with 12.2 online patching, participating in both unique indexes (FND_SECURITY_GROUPS_U1 on SECURITY_GROUP_ID, ZD_EDITION_NAME; FND_SECURITY_GROUPS_U2 on SECURITY_GROUP_KEY, ZD_EDITION_NAME).

Common Use Cases and Queries

Typical usage centers on identifying the active security group for a session and resolving the group key for reporting or integration mappings.

• Listing groups and their audit history: SELECT SECURITY_GROUP_ID, SECURITY_GROUP_KEY, CREATION_DATE, LAST_UPDATE_DATE FROM APPLSYS.FND_SECURITY_GROUPS ORDER BY SECURITY_GROUP_KEY;
• Resolving a business key to its surrogate: SELECT SECURITY_GROUP_ID FROM APPLSYS.FND_SECURITY_GROUPS WHERE SECURITY_GROUP_KEY = :key;
• Counting dependent records per group, for example against FND_CONCURRENT_REQUESTS or WF_ITEMS, to assess partition skew: join on SECURITY_GROUP_ID and aggregate by SECURITY_GROUP_KEY.
• Verifying uniqueness under editioning: query FND_SECURITY_GROUPS_U1 and FND_SECURITY_GROUPS_U2 to confirm no duplicate surrogate or business key exists within an edition.

Because SECURITY_GROUP_ID is referenced by hundreds of child tables, any lookup by key should be driven from the primary key or the unique business key to avoid full scans on large dependent tables.

Related Objects

The table is a parent to many FND, workflow, and application-object children. The most representative relationships on the join column SECURITY_GROUP_ID are:

• FND_CONCURRENT_REQUESTS — concurrent request definitions are partitioned by security group.
• FND_LOOKUP_TYPES — lookup type ownership is scoped to a security group.
• FND_CONCURRENT_PROGRAMS and FND_IREP_CLASSES / FND_IREP_CLASSES_TL — program and report class definitions carry the group reference.
• AP_WEB_PROXY_ASSIGNMENTS — the documented child at the top of the FK list, joining on AP_WEB_PROXY_ASSIGNMENTS.SECURITY_GROUP_ID.
• GL_DEFAS_RESP_ASSIGN and PER_SEC_PROFILE_ASSIGNMENTS — responsibility and HR security profile assignments that bind a group to an access context.
• WF_ITEMS, WF_LOCAL_USER_ROLES, and WF_LOOKUP_TYPES_TL — workflow runtime and directory objects partitioned by group.
• JTF_RS_SALESREPS and JTF_RS_ROLES_TL — resource and role definitions in the CRM resource manager.

These are illustrative of the broader reference set; the full child list extends across most EBS product families, all joining on SECURITY_GROUP_ID.