Results for “process_in_next_run_flag”

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

Overview

PER_SECURITY_USERS is an Oracle E-Business Suite Human Resources (PER) table, owned by the HR schema, that stores the list of application users associated with each security profile whose access permissions are materialized into static lists during the Security List Maintenance process. In EBS 12.1.1 and 12.2.2, Security List Maintenance is the concurrent program that pre-computes and caches the set of users and organizations a security profile grants access to, so that runtime security checks do not need to resolve complex profile hierarchies dynamically. PER_SECURITY_USERS is the resulting membership table: one row per (user, security profile) pairing that will be represented in those static lists.

Under the heuristic Data Vault classification mined from the foreign key structure, this object is satellite-leaning. It holds descriptive state about a relationship between a user and a security profile, including auditing and processing attributes, rather than acting purely as a link between hubs or as a standalone entity hub.

Key Information Stored

The table carries 10 documented columns. The most significant are:

• SECURITY_USER_ID — the surrogate primary key, enforced by the PER_SECURITY_USERS_PK index. It uniquely identifies each row.
• USER_ID — the application user (FND_USER) covered by the security profile. Together with SECURITY_PROFILE_ID it forms the business-key candidate PER_SECURITY_USERS_UK2, which prevents duplicate user/profile pairings.
• SECURITY_PROFILE_ID — the security profile granting access, and the foreign key column referencing PER_SECURITY_PROFILES.
• PROCESS_IN_NEXT_RUN_FLAG — controls whether the row is (re)processed during the next execution of Security List Maintenance, driving incremental list generation.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Application Framework (OAF) to detect concurrent updates.
• Audit columns — LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE record who created or last modified the row and when.

Common Use Cases and Queries

Administrators and reporting developers query this table to audit which users belong to a given security profile, to verify that Security List Maintenance has populated the expected memberships, and to troubleshoot access issues where a user does not see the expected data.

Count users per security profile:

SELECT security_profile_id, COUNT(*) users
FROM   hr.per_security_users
GROUP  BY security_profile_id;

Locate the profile rows for a specific user (using the UK2 columns):

SELECT security_user_id, security_profile_id, process_in_next_run_flag
FROM   hr.per_security_users
WHERE  user_id = :user_id;

Identify memberships awaiting reprocessing:

SELECT * FROM hr.per_security_users
WHERE  process_in_next_run_flag = 'Y';

Related Objects

• PER_SECURITY_PROFILES — parent table; joined via PER_SECURITY_USERS.SECURITY_PROFILE_ID = PER_SECURITY_PROFILES.SECURITY_PROFILE_ID. This is the only documented foreign key relationship.
• FND_USER — resolves USER_ID to the actual application user name and credentials.
• FND_USER_RESP_GROUPS — responsibility and role assignments that interact with security profile grants.
• PER_SECURITY_ORGANIZATIONS — the organization-side companion static list generated by the same maintenance process.
• PER_SECURITY_APPLICATIONS — defines which applications a security profile touches.
• Security List Maintenance concurrent program — the process that populates and refreshes rows in this table.