Results for “xla_mo_security_profile_level”

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

Overview

PJI_OPERATING_UNITS_V is a view owned by the APPS schema within the PJI - Project Intelligence product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The view is documented as an internal summarization view, meaning it consolidates and filters data from multiple underlying security and organization tables into a simplified result set. Its primary role is to return the list of operating units visible to the currently connected user, based on the value of the system profile option XLA_MO_SECURITY_PROFILE_LEVEL.

The view is tightly coupled to Oracle Subledger Accounting (XLA) multi-organization security. Rather than depending on any Project Intelligence base tables directly, it acts as a lightweight lookup that reconciles HR organizations against the implementations and security profile assignments defined for the ledger. This makes it useful in reporting and integration contexts where an application must restrict operating unit choices to only those the user is authorized to access.

Underlying Base Objects

The view text joins four documented base objects:

• HR_ALL_ORGANIZATION_UNITS_TL — the translated organization definition table, supplying the organization identifier and name.
• PA_IMPLEMENTATIONS_ALL — the Project Accounting implementations table, used to confirm that the organization corresponds to a valid operating unit.
• PER_ORGANIZATION_LIST — the security profile organization list, outer-joined to the organization identifier to enforce profile-based filtering.
• PER_SECURITY_PROFILES — the security profile header table, joined to the XLA_MO_SECURITY_PROFILE_LEVEL profile value.

The joins establish that an organization must be listed in PA_IMPLEMENTATIONS_ALL, must be represented in the security profile organization list for the active profile, and must either be flagged as view-all or appear explicitly in the organization list. Because PER_ORGANIZATION_LIST is outer-joined, organizations that are visible solely through the VIEW_ALL_ORGANIZATIONS_FLAG = 'Y' condition are still returned.

Key Columns

The view exposes two columns:

• ID — the operating unit organization identifier, sourced from HR_ALL_ORGANIZATION_UNITS_TL.ORGANIZATION_ID. This is the value passed to other queries or concurrent programs that must be constrained by operating unit.
• VALUE — the organization name, sourced from HR_ALL_ORGANIZATION_UNITS_TL.NAME. The language is restricted with USERENV('LANG') so the name is returned in the session language.

These columns follow the standard Oracle key-flex lookup convention of ID and VALUE, which allows the view to be attached to value sets, LOV definitions, and dependent parameters without additional transformation.

Common Use Cases and Queries

Typical usage is limited to resolving the set of accessible operating units for a given user session, particularly in XLA-aware reports and custom concurrent programs.

• Populating a value set or list of values for an operating unit parameter.
• Validating that a user-supplied organization identifier is within the user's security scope before executing a report.
• Driving WHERE-clause restrictions in project intelligence queries through the XLA_MO_SECURITY_PROFILE_LEVEL profile.

A representative query follows:

SELECT id, value FROM apps.pji_operating_units_v ORDER BY value;

A scoped lookup for a single organization would be written as:

SELECT value FROM apps.pji_operating_units_v WHERE id = :p_org_id;

Because the result set is already filtered by the security profile resolved through FND_PROFILE.VALUE, callers do not need to repeat the security joins. If the profile option XLA_MO_SECURITY_PROFILE_LEVEL is null for the session, the view returns no rows, which callers should handle as an indication that multi-organization security is not configured.