Results for “per_security_organizations_v”

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

Overview

PER_SECURITY_ORGANIZATIONS_V is a view owned by the APPS schema within the Oracle E-Business Suite Human Resources (PER) product family. It presents organization-level security assignments in a denormalized, query-friendly form by joining the security definition table PER_SECURITY_ORGANIZATIONS to the multilingual organization name table HR_ALL_ORGANIZATION_UNITS_TL. The view is validated and available in both EBS 12.1.1 and 12.2.2, and it is a documented object in the ETRM repository for release 12.2.2.

Its primary purpose is to expose the relationship between a security profile, the organizations secured under that profile, and the ENTRY_TYPE attribute that classifies how each organization participates in the security hierarchy. Because the view resolves the organization name using USERENV('LANG'), it delivers organization names in the session's current language, making it suitable for localized concurrent programs, OAF pages, and custom reports. It is a read-only query surface; DML must be directed against the base table PER_SECURITY_ORGANIZATIONS.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through APPS synonyms:

• PER_SECURITY_ORGANIZATIONS — the transactional security table that stores each organization's membership in a security profile, along with the ENTRY_TYPE value, audit columns, and the OBJECT_VERSION_NUMBER used for optimistic locking.
• HR_ALL_ORGANIZATION_UNITS_TL — the translated name table for organization units, supplying NAME (aliased as ORGANIZATION_NAME in the view).

The join condition links UTL.ORGANIZATION_ID = PSO.ORGANIZATION_ID and restricts rows with UTL.LANGUAGE = USERENV('LANG'), ensuring that exactly one translated name row is returned per organization and per session language. This design means the view inherits the language behavior of the TL table and will only return rows when a translation exists for the current session language.

Key Columns

• ORGANIZATION_NAME — the organization unit's translated name from HR_ALL_ORGANIZATION_UNITS_TL.
• ORGANIZATION_ID — the unique identifier of the secured organization unit.
• SECURITY_PROFILE_ID — the security profile to which the organization assignment belongs.
• ENTRY_TYPE — the classification of the security entry, indicating how the organization is included in the security profile. This is the attribute that users most frequently search for when analyzing security hierarchies.
• SECURITY_ORGANIZATION_ID — the surrogate primary key of the underlying PER_SECURITY_ORGANIZATIONS row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns indicating who created and last modified the row and when.
• OBJECT_VERSION_NUMBER — the concurrency-control version token, incremented on each update to the base row in 12.2.x.

Common Use Cases and Queries

The view is commonly used to audit and troubleshoot Organization Security Profile configuration, to reproduce the organization set implied by a profile, and to drive custom reports or integrations that require descriptive organization names rather than raw IDs. Because it joins to the TL table, it should be queried in the language context intended for the report.

A typical query listing all organizations secured by a given profile is:

• SELECT organization_name, organization_id, security_profile_id, entry_type FROM apps.per_security_organizations_v WHERE security_profile_id = :p_profile_id ORDER BY organization_name;

To isolate specific entry types, users can filter on the ENTRY_TYPE column directly, which is the attribute behind the frequent "entry_type" search. When correlating security definitions back to the underlying base rows (for example, to inspect audit history), join SECURITY_ORGANIZATION_ID to PER_SECURITY_ORGANIZATIONS.SECURITY_ORGANIZATION_ID. Since the view is read-only, any maintenance of organization security assignments must be performed through supported EBS forms or against the base table, not through this view.