Search Results oke_k_secured_views_pkg




Overview
Explore in AI Chat

Overview

OKE_K_SECURED_VIEWS_PKG is an Oracle E-Business Suite package owned by the APPS schema and delivered as part of the Oracle Knowledge Base (OKE) module, which underpins Oracle Contracts and related purchasing and ordering functionality. The package is classified in the ETRM metadata as an "OTHER" API, indicating that it is not a public, supported extension interface but rather an internal utility used to support the application's security architecture.

The principal business function of this package is to generate secured database views. Oracle Contracts relies on an access control model in which visibility of contract data is restricted according to configurable access rules. Rather than enforcing these rules purely at the application layer, OKE materializes them as database views that filter rows based on the compiled access rules and the attributes of the objects being secured. OKS_K_SECURED_VIEWS_PKG is the programmatic mechanism that performs this generation, ensuring that the secured views remain consistent with the access rules defined in the repository.

Key Procedures and Functions

The ETRM documentation records a single documented program unit within the package:

  • GENERATE_SECURED_VIEWS — This procedure is the sole documented entry point. It accepts the standard concurrent program parameter conventions, with output parameters for the error buffer and the return code, and performs the work of creating or regenerating the secured views used by the Knowledge Base security model. By convention, the error buffer conveys diagnostic messages and the return code signals success or failure to the calling program. The package specification header (version 120.0.12000000.1, dated January 2007) indicates a long-stable implementation that has persisted across the 12.1.1 and 12.2.2 releases.

Tables Accessed

The package is documented as referencing the following tables through APPS synonyms:

  • OKE_COMPILED_ACCESS_RULES — Stores the compiled form of the access rules that govern visibility of secured objects. This is the primary driver of the view definitions generated by the procedure.
  • OKE_OBJECT_ATTRIBUTES_B — Holds the base-table attributes of the objects subject to security. The procedure uses these attributes to determine which columns and predicates belong in each secured view.
  • FND_ORACLE_USERID — The Oracle Applications user registry. It supplies the database user identities associated with application users so that generated views can be granted or scoped appropriately.
  • FND_PRODUCT_INSTALLATIONS — Identifies which Oracle Applications products are installed and their status, allowing the procedure to determine whether the Knowledge Base and related modules are active in the current environment.
  • AD_DDL — The Applications DDL utility table used to execute dynamic DDL statements. The procedure relies on it to issue the CREATE OR REPLACE VIEW (and related) statements required to generate secured views.

Usage Notes

Because the package is classified as OTHER and exposes a single procedure that emits DDL, it is normally invoked as a concurrent program rather than called directly from forms or custom code. It is typically scheduled after access rules are modified, after patching, or during environment cloning and setup, so that the secured views reflect the current compiled rules and the current installation of OKE products. The procedure should be run with the privileges of an application user capable of issuing DDL. Customizations should avoid direct calls to the package and should instead rely on the standard concurrent program wrapper. The package is referenced by no other packages in the ETRM metadata, underscoring its role as a standalone maintenance utility for the Knowledge Base security framework.