Search Results cs_kb_profiles_pkg




Overview
Explore in AI Chat

Overview

CS_KB_PROFILES_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It is classified in the ETRM repository under the generic API classification of OTHER, indicating that it is an internal support package rather than a public, fully versioned API intended for customer extension. The package is declared with AUTHID CURRENT_USER, meaning that its SQL statements execute under the privileges of the calling user rather than the package owner, a characteristic typical of helper logic invoked from within the Applications security and personalization framework.

The business function of the package is to answer membership questions about the current or specified user. Specifically, it determines whether a given user is associated with a particular knowledge category or with a particular product and product organization. These evaluations support profile-driven personalization in the Oracle Knowledge Base and related interaction-center components, where content visibility and default behavior are governed by the profiles assigned to a user through the JTF personalization infrastructure. The package therefore acts as a thin, reusable membership test layer over the underlying profile data model.

Key Procedures and Functions

The documented package specification exposes two functions. Both return a NUMBER, which in EBS convention represents a Boolean-style result where the value is interpreted by the caller as true or false.

  • ISCATEGORYMEMBER — Evaluates whether the identified user belongs to or is otherwise associated with the specified knowledge category. Callers pass a user identifier and a category identifier, and the function returns the membership result. This function underpins category-level filtering of knowledge content based on the user's assigned profiles.
  • ISPRODUCTMEMBER — Evaluates whether the identified user is associated with the specified product within a given product organization. It accepts the user, the product, and the product organization as identifying inputs and returns the membership result. The inclusion of the organization identifier reflects the multi-organization product model used by Oracle inventory and service applications.

No other procedures or functions are documented in the ETRM entry for this package. The specification body ends after ISPRODUCTMEMBER, confirming that the published interface is limited to these two membership checks.

Tables Accessed

The package reads the JTF personalization tables through APPS synonyms. These tables are the persistence layer for user-level profile attributes and the profiles to which those attributes belong.

  • JTF_PERZ_DATA — Stores personalized data values associated with users or other entities. The package uses it to retrieve the attribute values that determine membership.
  • JTF_PERZ_DATA_ATTRIB — Defines the attributes attached to personalized data records; it provides the metadata that maps stored values to the category or product dimensions being tested.
  • JTF_PERZ_PROFILE — Holds the profile definitions themselves, allowing the package to resolve which attributes and values are relevant to a given profile-driven membership decision.

Access is read-oriented: the functions interrogate these tables to derive a membership answer and do not, per the documented interface, create or modify profile data.

Usage Notes

CS_KB_PROFILES_PKG is an internal utility rather than an end-user-facing API. It is not exposed through a standard concurrent program, and it carries no formal API version designation in the ETRM classification. Its practical consumers are Oracle application forms and other PL/SQL packages that need a single-call membership test while rendering knowledge content or applying profile-driven defaults.

The metadata records that the package is referenced by one other package, confirming its role as a dependent helper rather than a top-level entry point. Custom developers who need to reproduce this behavior should treat the package as undocumented and subject to change; the two functions may be referenced defensively, but Oracle does not commit to their stability across patch levels in the same way it does for registered public APIs. Because the package executes with AUTHID CURRENT_USER, callers must have the necessary privileges on the underlying JTF tables for the membership checks to succeed.