Search Results ak_security_pvt




Overview
Explore in AI Chat

Overview

AK_SECURITY_PUB is a public PL/SQL package in the APPS schema that governs record-level and attribute-level security within the Oracle E-Business Suite Oracle Application Framework (OAF) and Application Object Library infrastructure. It is the principal security enforcement layer for the AK (Application Kit) component family, which drives the attribute-driven security model used by self-service applications, OAF pages, and the Oracle Applications Framework's "AK" region/repository. The package determines whether a given responsibility, user, or security group may view or modify specific attributes and items, applying exclusion rules and responsibility-based security attributes maintained in the AK security configuration tables.

The package is classified as a PUBLIC API (API classification: PUB), indicating its procedures and functions are intended for external invocation by other application code. In ETRM 12.1.1 and 12.2.2, AK_SECURITY_PUB remains VALID in the APPS schema and sits at the center of the AK security dependency graph, where it both consumes metadata tables and is consumed by a small set of tightly coupled security packages.

Key Procedures and Functions

The ETRM metadata for this object documents the package header (APPS.AK_SECURITY_PUB) and body but lists no explicitly documented standalone procedures or functions (0 total). Consequently, the specific callable units are not enumerated in the reference metadata; descriptions of individual entry points are therefore deferred to the package source rather than invented here. What is documented is the package's dependency footprint, which confirms it provides the reusable security-decision logic that other AK packages call: exclusion evaluation, responsibility security attribute resolution, and item/attribute access checks. The absence of a documented procedure list does not imply the package is empty—rather, that the ETRM extract captured only structural metadata.

Tables Accessed

AK_SECURITY_PUB references the following application tables, resolved through APPS synonyms:

  • AK_EXCLUDED_ITEMS — Stores item-level exclusion lists. The package reads this table to determine whether a particular item (attribute, region, or object) is excluded from a user's or responsibility's view, and applies those exclusions when answering access queries.
  • AK_RESP_SECURITY_ATTRIBUTES — Holds responsibility-specific security attributes that refine access decisions. The package consults this table to map a responsibility to its granted or restricted attribute set, enabling responsibility-scoped visibility rules.

In addition to these APPS-owned tables, the dependency report shows references to SYS and STANDARD objects, reflecting standard Oracle database and SQL/PLSQL language elements rather than application data.

Usage Notes

AK_SECURITY_PUB is referenced by four other packages: AK_DELETE_GRP, AK_DOWNLOAD_GRP, AK_SECURITY_GRP, and AK_SECURITY_PVT. This dependency pattern indicates the package is invoked indirectly through the AK security group of packages, which are in turn triggered by OAF page processing, the AK repository, and self-service administrative flows. AK_SECURITY_PVT acts as the private implementation tier that wraps or extends AK_SECURITY_PUB, while AK_DELETE_GRP and AK_DOWNLOAD_GRP confirm its enforcement role in delete and download operations—security checks must pass before records can be removed or exported.

Because the package is designated PUB, customizations and extensions may call it directly to replicate AK security decisions in custom OAF pages, concurrent programs, or PL/SQL validation. However, the recommended approach in both 12.1.1 and 12.2.2 is to route through the AK_SECURITY_PVT or AK_SECURITY_GRP layers so that internal caching and exclusion logic remain consistent. Note that the user search term "ak_security_pvt" maps most closely to AK_SECURITY_PVT, the private companion package; AK_SECURITY_PUB is the public counterpart that AK_SECURITY_PVT references and therefore the correct object to examine when tracing the underlying security implementation.