Results for “xla_mo_security_profile_level”

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

Overview

The view APPS.PJI_OPERATING_UNITS_V exposes a security-filtered list of valid operating units within Oracle E-Business Suite. It is defined over HR organization units that have been implemented as operating units in Oracle Projects, and returns a simple two-column key/value set (organization identifier and organization name) intended for use in list-of-values (LOV) components, concurrent program parameters, and other reporting or integration surfaces that must restrict user selection to the operating units the current user is authorized to access.

The defining characteristic of this view is its dependence on the profile option XLA_MO_SECURITY_PROFILE_LEVEL. This is the profile that controls multi-organization (MO) security for subledger accounting (XLA). Rather than returning every operating unit, the view joins to PER_SECURITY_PROFILES and PER_ORGANIZATION_LIST so that only organization units permitted by the active security profile are surfaced. This makes the view a standard mechanism for honoring MO security in customizations and extensions, particularly in XLA and Projects contexts.

Underlying Base Objects

The view text references four documented base objects:

• HR_ALL_ORGANIZATION_UNITS_TL — the translated organization units table. The alias HRORG supplies both the ID (ORGANIZATION_ID) and the display NAME, restricted to the user's current language via USERENV('LANG').
• PA_IMPLEMENTATIONS_ALL — the Oracle Projects implementations table. Joining on PAIMP.ORG_ID = HRORG.ORGANIZATION_ID restricts results to organizations actually implemented as operating units in Projects.
• PER_ORGANIZATION_LIST — the list of organizations assigned to a security profile. This is outer-joined ((+)) so that rows are not lost when the profile grants access to all organizations.
• PER_SECURITY_PROFILES — the security profile definition, which provides VIEW_ALL_ORGANIZATIONS_FLAG, the flag distinguishing "view all" profiles from restricted ones.

The join chain ties the security profile named by the profile option XLA_MO_SECURITY_PROFILE_LEVEL to the organizations in PER_ORGANIZATION_LIST, with the outer join allowing the "view all organizations" case to be handled by the flag check. When the profile option is null, the row predicate (IS NOT NULL) eliminates all rows, so the view returns nothing.

Key Columns

• ID — aliased from HRORG.ORGANIZATION_ID. The operating unit identifier, used to join back to operating-unit columns throughout Projects, XLA, and other subledger tables.
• VALUE — aliased from HRORG.NAME. The translated operating unit name, used as the displayed value in LOVs and reports.

Although the view only projects two columns, its filters implicitly depend on SEC.ORGANIZATION_ID, SEC.SECURITY_PROFILE_ID, and PROF.VIEW_ALL_ORGANIZATIONS_FLAG to perform the security enforcement.

Common Use Cases and Queries

A typical LOV or parameter validation query selects directly from the view:

• SELECT id, value FROM apps.pji_operating_units_v ORDER BY value; — populates a user-facing list of permitted operating units.
• SELECT value FROM apps.pji_operating_units_v WHERE id = :org_id; — validates that a supplied operating unit is both implemented and within the user's security scope.
• Embedding the view in a report as a security-restricted driving table, ensuring results are limited to the organizations the profile option permits.

Because results are driven by XLA_MO_SECURITY_PROFILE_LEVEL, administrators should verify that this profile is set correctly at the appropriate level (site, application, responsibility, or user) before relying on the view; an unset profile produces an empty result set. When a user is granted a "view all organizations" profile, the flag predicate permits every implemented operating unit; otherwise only the organizations listed against the assigned security profile are returned.