Search Results fnd_security_groups_ul

Overview

FND_SECURITY_GROUPS_PKG is the foundational database package within the Oracle E-Business Suite APPS schema that manages the persistence layer for security groups. Security groups are a core EBS security construct that partition application data and responsibilities, allowing a single EBS instance to host multiple logically isolated business entities or operating units. The package exposes the low-level Data Manipulation Language (DML) routines that create, modify, translate, load, and remove records from the underlying security group tables. It is classified under ETRM as an OTHER API rather than a formal public API, meaning it is intended primarily as an internal implementation package consumed by higher-level APIs and generated forms infrastructure rather than by customer code. The package holds a VALID status in both Oracle EBS 12.1.1 and 12.2.2 and is owned by the APPS schema, which is standard for all FND (Foundation) technology stack components. Its procedures form the mechanical layer beneath the more abstract FND_SECURITY_GROUPS_API, the package most application developers reference when manipulating security groups programmatically.

Key Procedures and Functions

ETRM documents nine procedures and functions within FND_SECURITY_GROUPS_PKG. Their purposes are as follows:

• INSERT_ROW — Inserts a new security group record, populating the base and translated tables during initial creation.
• LOCK_ROW — Acquires a row-level lock on an existing security group record to serialize concurrent updates and prevent lost modifications.
• UPDATE_ROW — Modifies an existing security group record, updating all applicable intersection, base, and translation tables.
• LOAD_ROW — Performs an upsert-style load, typically used by seed data and patching routines to insert or refresh a security group from a predefined data set.
• TRANSLATE_ROW — Maintains translatable (TL) attribute values for a security group, supporting multilingual deployments.
• DELETE_ROW — Removes a security group and its associated subordinate records from the affected tables.
• ADD_LANGUAGE — Adds language-specific rows to the translation table when a new language is enabled for the instance. Note that ETRM lists nine total procedures while only seven names plus ADD_LANGUAGE are documented in the extract; the remaining routine is not named in the supplied metadata.

Parameter lists are intentionally not reproduced here; ETRM documents the existence and role of these routines without exposing their signatures.

Tables Accessed

The package operates against four documented objects, accessed through APPS synonyms:

• FND_SECURITY_GROUPS — The base table holding the primary security group definition and its enablement attributes.
• FND_SECURITY_GROUPS_S — The primary single-table structure that stores the core descriptive columns for each security group.
• FND_SECURITY_GROUPS_TL — The translation table containing language-specific values for translatable columns.
• FND_LANGUAGES — Consulted to validate and resolve language codes during translation and ADD_LANGUAGE processing.
• DUAL — Used for simple scalar evaluations and sequence or version lookups.

Usage Notes

FND_SECURITY_GROUPS_PKG is not typically invoked directly by end users or custom applications. It is referenced by five other database objects: the public-facing FND_SECURITY_GROUPS_API, the generated form-handler packages FND_SECURITY_GROUPS_DL (delete), FND_SECURITY_GROUPS_IL (insert), and FND_SECURITY_GROUPS_UL (update/load), plus HR_DM_DELETE in the Oracle HRMS data-merge/cleanup flow. This dependency pattern confirms its role as a form-generated backend: the Oracle Application Framework forms that maintain security groups call these DL/IL/UL packages, which in turn delegate to FND_SECURITY_GROUPS_PKG. Developers who need to create or modify security groups programmatically should generally call FND_SECURITY_GROUPS_API instead of the internal package. Direct use of FND_SECURITY_GROUPS_PKG should be limited to controlled infrastructure, patch scripts, and diagnostic work, and should always observe the same validation, security-group assignment, and translation rules that the forms enforce.