Search Results per_security_profiles_s

Overview

The APPS.PER_SECURITY_PROFILES_PKG package body is a core Oracle E-Business Suite object that supports the definition and maintenance of Oracle HRMS security profiles. Security profiles are the mechanism by which access to people, assignments, and organizations is restricted for a given responsibility or user. The package encapsulates the data manipulation and validation logic required to create, modify, and remove security profile records together with their associated assignments.

In EBS 12.1.1 and 12.2.2, the object is classified as a valid OTHER-type API rather than a fully published public interface. It functions primarily as the PL/SQL implementation layer beneath the Security Profiles form and related HRMS setup screens. Because the object name is frequently searched as per_security_profiles_s, it is worth clarifying that PER_SECURITY_PROFILES_S is the underlying sequence used by the package, while PER_SECURITY_PROFILES_PKG is the package that consumes it to generate primary keys for the PER_SECURITY_PROFILES table. The package relies on APP_EXCEPTION, FND_MESSAGE, HR_UTILITY, and dynamic SQL through DBMS_SQL to perform its work.

Key Procedures and Functions

ETRM documents nine procedures and functions in this package:

• INSERT_ROW — Inserts a new security profile row into PER_SECURITY_PROFILES, using the PER_SECURITY_PROFILES_S sequence for the surrogate key.
• LOCK_ROW — Acquires a row-level lock on the target security profile record, ensuring serialized updates in concurrent form sessions.
• UPDATE_ROW — Applies changes to an existing security profile, including its descriptive and defining attributes.
• DELETE_ROW — Removes a security profile record, typically after validation has confirmed it is safe to delete.
• CHECK_UNIQUENESS — Validates that the profile name or other identifying attributes are unique before insert or update.
• CHK_REPORTING_USERNAME_UNIQUE — Enforces uniqueness for the reporting username associated with the profile.
• PRE_DELETE_VALIDATION — Confirms that no blocking dependencies (such as active assignments) prevent deletion of the profile.
• CHECK_SQL_FRAGMENT — Validates the dynamically generated SQL fragment that defines the security profile's data restriction criteria, using DBMS_SQL to parse it.
• CHECK_ASSIGNED_SEC_PROFILE — Verifies whether a security profile is assigned to a responsibility or user before allowing modification or removal.

Tables Accessed

The package reads and writes several documented tables through APPS synonyms:

• PER_SECURITY_PROFILES — Primary table holding security profile definitions; the target of INSERT, UPDATE, LOCK, and DELETE operations.
• PER_SECURITY_PROFILES_S — Sequence supplying the primary key for new profile rows.
• PER_SEC_PROFILE_ASSIGNMENTS — Maps security profiles to responsibilities or users; consulted for assignment validation.
• PER_PERSON_LIST — Stores the SQL fragments defining the population of persons covered by the profile.
• FND_PROFILE_OPTIONS and FND_PROFILE_OPTION_VALUES — Used when validating and setting profile option values that control security behavior.
• ALL_TABLES — Referenced by CHECK_SQL_FRAGMENT to confirm that tables named in the dynamic SQL exist.
• DBMS_SQL — The Oracle-supplied package invoked to parse and validate dynamic SQL fragments.

Usage Notes

This package is typically invoked indirectly through the Oracle HRMS Security Profiles form rather than called directly by end users or custom code. Because the procedures do not expose a documented public parameter list, they are not intended as a supported integration API. Customizations that need to create or modify security profiles should generally use the form or a supported public interface. Direct calls should be limited to controlled scenarios, and callers must respect the locking, uniqueness, and pre-delete validation logic implemented here. ETRM indicates the package is referenced by two other packages within APPS, confirming its role as a shared internal dependency for security profile maintenance in both 12.1.1 and 12.2.2.