Results for “per_security_users_v”

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

Overview

PER_SECURITY_USERS_V is an APPS-owned database view in the Human Resources (PER) product family of Oracle E-Business Suite. It is documented in ETRM for both 12.1.1 and 12.2.2 with a status of VALID, and its stated purpose is to support the user interface. Rather than functioning as a standalone reporting entity, the view acts as a presentation-layer join that resolves the association between a security profile assignment and the underlying application user and person record.

The view exposes one row per security-user assignment, enriched with the FND user name and the full name of the associated person, while restricting the result set to the effective person record that is current as of the caller's session date. This design makes it suitable for LOVs, security administration screens, and integration extracts that need human-readable identity information alongside the raw security identifiers stored in PER_SECURITY_USERS.

Because the view references FND_SESSIONS via USERENV('SESSIONID'), it is session-context dependent and will return data only within a valid EBS session. This is an important operational characteristic: the view is not intended for bulk, session-independent batch extraction against arbitrary dates.

Underlying Base Objects

The view is defined over four synonyms resolving to the following base objects:

• PER_SECURITY_USERS — the driving table holding the security user assignment, supplying SECURITY_USER_ID, SECURITY_PROFILE_ID, USER_ID, and the standard WHO/version columns.
• FND_USER — supplies USER_NAME and EMPLOYEE_ID; joined on PSU.USER_ID = FNDU.USER_ID.
• PER_ALL_PEOPLE_F — joined via FNDU.EMPLOYEE_ID = PAPF.PERSON_ID(+), an outer join that preserves security users who have no corresponding person record.
• FND_SESSIONS — joined on FNDS.SESSION_ID = USERENV('SESSIONID'), anchoring the effective-date filter.

The effective-date predicate FNDS.EFFECTIVE_DATE BETWEEN NVL(PAPF.EFFECTIVE_START_DATE, FNDS.EFFECTIVE_DATE) AND NVL(PAPF.EFFECTIVE_END_DATE, FNDS.EFFECTIVE_DATE) ensures that only the person record valid at session time is returned, preventing duplicate rows from the date-tracked PER_ALL_PEOPLE_F table.

Key Columns

• SECURITY_USER_ID — primary identifier of the security user assignment.
• SECURITY_PROFILE_ID — the security profile to which the user is assigned.
• USER_ID / USER_NAME — FND user identifiers, useful for joining to other FND-based views.
• PERSON_ID / FULL_NAME — the person identity; both may be null for users without an employee link.
• PROCESS_IN_NEXT_RUN_FLAG — a flag column, retained in the view's column list. Note that this column is not present in the documented SELECT text; it appears in the ETRM column listing and should be treated cautiously in custom code, since its availability depends on the actual deployed view definition.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — standard WHO audit and optimistic-locking columns inherited from PER_SECURITY_USERS.

Common Use Cases and Queries

Typical uses include security administration reports, user-identity reconciliation extracts, and LOV-driven inquiry within the HR security setup UI.

SELECT security_user_id
     , security_profile_id
     , user_name
     , full_name
  FROM apps.per_security_users_v
 ORDER BY user_name;

To list assignments for a specific profile:

SELECT user_name, full_name
  FROM apps.per_security_users_v
 WHERE security_profile_id = :profile_id;

Because of the FND_SESSIONS dependency, these queries must be executed inside an authenticated EBS session. Batch programs should generally query PER_SECURITY_USERS directly and apply their own effective-date logic against PER_ALL_PEOPLE_F.