Search Results xla_mo_security_profile_level




Overview

AP_SEC_V is a security-oriented view owned by the APPS schema within the Oracle E-Business Suite Payables (AP) module. Its documented purpose is narrow and well defined: it restricts the querying user to records associated with the organizations and security profile assigned to that user, rather than exposing the full set of payable records. In this sense AP_SEC_V functions as a row-level access filter that can be joined into custom reports, concurrent programs, or integration queries to enforce data segregation by operating unit and organization.

The view is particularly relevant to environments implementing Multi-Org Access Control (MOAC). The user search term xla_mo_security_profile_level corresponds directly to the profile option referenced inside the view definition, confirming that AP_SEC_V is driven by the Subledger Accounting (XLA) security profile setting. The view returns a single column of ORG_ID values that represent the set of organizations the current user is authorized to see, allowing downstream queries to constrain results accordingly.

Underlying Base Objects

AP_SEC_V is a UNION-based view constructed from two branches. The first branch selects from the DUAL synonym, deriving an ORG_ID value from the USERENV('CLIENT_INFO') session context. It extracts the first character and the first ten characters of CLIENT_INFO, treating a leading space as NULL, and wraps the result in NVL(..., -99). The value -99 acts as a sentinel indicating that no organization context has been established for the session.

The second branch selects ORGANIZATION_ID from the PER_ORGANIZATION_LIST synonym, filtered by SECURITY_PROFILE_ID equal to FND_PROFILE.VALUE('XLA_MO_SECURITY_PROFILE_LEVEL'). This is the core of the MOAC enforcement: PER_ORGANIZATION_LIST resolves the organizations mapped to the security profile currently active for the user, and FND_PROFILE (the profile option package) supplies the active XLA security profile level. The documented dependencies are therefore FND_PROFILE (PACKAGE), PER_ORGANIZATION_LIST (SYNONYM), and DUAL (SYNONYM).

Key Columns

The view exposes a single documented column, ORG_ID. Its meaning is consistent across both UNION branches: it carries an organization identifier that the user is permitted to access. The value may originate either from the session-level CLIENT_INFO context (the current operating unit being processed) or from the organizations enumerated through the user's XLA MO security profile. The sentinel value -99 is emitted when CLIENT_INFO does not yield a usable organization, and this value should generally be excluded or handled explicitly in consuming queries.

Common Use Cases and Queries

The principal use case is enforcing organization-level security in custom Payables extracts and reports. A typical pattern joins AP_SEC_V to an organization-identified payables table to limit results to the authorized set.

  • Restricting an invoice or payment listing to a user's permitted organizations by joining on ORG_ID.
  • Populating a parameter list or LOV for organization selection within a custom concurrent program.
  • Validating that a given organization is within the caller's security profile before allowing a transaction.
  • Debugging MOAC behavior when reports return unexpected rows, by inspecting which ORG_ID values AP_SEC_V yields.

A representative query retrieves the authorized organizations for the current session:

SELECT ORG_ID FROM APPS.AP_SEC_V WHERE ORG_ID <> -99;

To constrain a Payables query, the view can be joined directly:

SELECT a.invoice_num, a.org_id
FROM APPS.AP_INVOICES_ALL a, APPS.AP_SEC_V s
WHERE a.org_id = s.org_id AND s.org_id <> -99;

Because the view is thin and depends on session context and profile settings, results vary by user session and must always be evaluated in the context of the active responsibility, operating unit, and XLA MO security profile configuration. The documented ETRM metadata confirms the structure across 12.1.1 and 12.2.2, with the same ORG_ID column and base object dependencies.