Search Results fnd_security_groups_s

Overview

The APPS.FND_SECURITY_GROUPS_API package body is the application programming interface that governs the creation, maintenance, and validation of security groups within the Oracle E-Business Suite. Security groups are a foundational component of the EBS security architecture: they partition application data by associating a group of responsibilities with a specific set of Oracle schemas, thereby enforcing data isolation across business entities, operating units, or legal partitions. This package encapsulates the business logic required to define such groups without requiring direct manipulation of the underlying base tables.

In Oracle EBS 12.1.1 and 12.2.2, the package resides in the APPS schema and holds a VALID status. Its API classification as a formal API indicates that it is intended for programmatic invocation by Oracle Forms, concurrent programs, and custom extensions, rather than being an internal-only utility. The package body depends on a compact set of supporting objects, most notably FND_SECURITY_GROUPS, FND_SECURITY_GROUPS_S, the view FND_SECURITY_GROUPS_VL, and the validation helper package FND_SECURITY_GROUPS_PKG, alongside standard infrastructure utilities FND_GLOBAL, FND_MESSAGE, APP_EXCEPTION, and SYS.DUAL.

Key Procedures and Functions

The documented interface exposes five callable routines. Three are existence-check functions used to protect uniqueness and referential integrity before any write operation:

• ID_EXISTS — determines whether a security group row already exists for a supplied internal identifier, guarding against duplicate or invalid primary key references.
• KEY_EXISTS — verifies the existence of a security group by its unique key, supporting key-based lookups and validation.
• NAME_EXISTS — confirms whether a security group with a given user-defined name is already defined, enabling the API to enforce uniqueness on the business-facing name.
• CREATE_GROUP — inserts a new security group record. It applies the validation logic and derives the surrogate key and seed columns required by the underlying tables.
• UPDATE_GROUP — modifies the attributes of an existing security group, refreshing the corresponding translation/seed rows to keep the base and secure tables synchronized.

Together these routines form a controlled create-and-maintain workflow that enforces naming and key uniqueness while abstracting the multi-table write sequence from the caller.

Tables Accessed

The package reads from and writes to two documented tables through APPS synonyms:

• FND_SECURITY_GROUPS — the primary table storing security group definitions and their associated schema assignments. It is the target of the CREATE_GROUP and UPDATE_GROUP operations.
• FND_SECURITY_GROUPS_S — the secure (MLS) table that holds the translatable, language-dependent column values and the seed columns that tie them to the base record. The existence-check routines and the write routines consult this table to validate identity and to maintain translation integrity.

The related view FND_SECURITY_GROUPS_VL provides the joined presentation of base and translation data and is referenced by the package's logic rather than queried directly by callers.

Usage Notes

This API is typically invoked by Oracle Forms-based setup screens and by concurrent or custom programs that need to register or amend security groups. Because it centralizes validation, direct DML against FND_SECURITY_GROUPS and FND_SECURITY_GROUPS_S is strongly discouraged; custom code should call CREATE_GROUP and UPDATE_GROUP so that uniqueness checks and translation rows remain consistent. The existence-check functions are useful for pre-validation in custom loaders and interfaces.

The package is not referenced by any other database object, confirming it is a top-level entry point. Callers should note that state changes may require a commit or rollback in the invoking transaction, and that security group configuration generally requires an application-level context established through FND_GLOBAL.