Search Results set_subledger_security

Overview

XLA_SECURITY_PKG is the Oracle Subledger Accounting (SLA) security package responsible for implementing Transaction Security on accounting events. Its source file, xlacmsec.pkb, resides in the APPS schema and is shipped as part of the applications codebase (header revision 120.24, dated 2006). The package provides the runtime infrastructure that restricts which subledger transactions a given user or responsibility is permitted to view or process within SLA inquiry and processing screens.

The package has evolved substantially since its creation in February 2001. Early releases exposed a set_security_context API following the original security approach. In April 2002 the approach was reworked for Oracle 9i, replacing the original context API with set_context and set_product_security. Subsequent revisions (November 2002 through October 2003, including bug 3173884) reworked the package into a working implementation, modified set_subledger_security, added and later removed an install_security procedure and an xla_security_policy object, and renamed the profile option code for the "SLA: Use Transaction Security" profile. In February and March 2004, local trace procedures and FND_LOG instrumentation were added (bug 3416534), including a p_module parameter on the TRACE calls.

Key Procedures and Functions

• SET_SECURITY_CONTEXT — Establishes the security context used by downstream SLA code. It is the entry point through which the package applies the active transaction security configuration to the current session, enabling or bypassing row-level restrictions according to the "SLA: Use Transaction Security" profile option. This is the API most relevant to the search term "set_subledger_security," since it is the documented companion routine for context establishment.
• SET_SUBLEDGER_SECURITY — Applies security rules at the subledger level, determining which subledger data a user may access based on the configured security policy. This procedure was explicitly modified in the November 2002 rework, reflecting its central role in filtering accounting events by the user's authorized subledger scope.

The ETRM metadata documents three procedures/functions in total; the two named above are the explicitly listed security APIs, with the third entry being an internal or auxiliary routine associated with the same package. No parameter lists are published in the ETRM excerpt, and none should be inferred.

Tables Accessed

• FND_APPLICATION — Resolves application identifiers and names, needed to map subledger products to their owning application during security evaluation.
• FND_MO_PRODUCT_INIT — Stores product initialization metadata used to determine the products participating in the security model.
• DBA_POLICIES and DBA_POLICY_GROUPS — Provide the Oracle Virtual Private Database (VPD) policy definitions and policy groups that the package manages or references when enforcing row-level security.
• DBMS_RLS — The Oracle-supplied package invoked to add, enable, disable, or refresh VPD policies dynamically at runtime.
• PLITBLM — The PL/SQL table (index-by table) utility package used for in-memory collection handling within the security routines.

Usage Notes

XLA_SECURITY_PKG is an internal SLA infrastructure package rather than a public API. It is invoked indirectly by SLA forms and concurrent programs whenever transaction security must be enforced, and it is referenced by 30 other packages in the EBS codebase, confirming its role as a shared security service. Customers and partners should not call these procedures directly from custom code, because the calling contract and the underlying VPD policy architecture are version-dependent and were revised repeatedly between 12.1.1 and 12.2.2. Any customization involving subledger-level security should be implemented through the supported profile option ("SLA: Use Transaction Security") and the standard security setup screens, allowing XLA_SECURITY_PKG to apply the context and subledger security implicitly.