Search Results update_statement_admin

Overview

The APPS.CS_KB_ELEMENTS_AUDIT_PKG package body is a valid, compiled PL/SQL unit in the Oracle E-Business Suite Applications schema. It belongs to the Oracle Service (CS) Knowledge Base module and supplies the audit-oriented processing logic for Knowledge Base "elements" — the discrete, versioned content records that comprise solution articles, questions, notes, and related knowledge documents. The package encapsulates the business rules that decide whether an element is a duplicate on creation or update, that resolve an element's logical number and latest version identifier, and that persist element statements and large text (CLOB) bodies. It also records and retrieves the standard "Who" auditing columns and provides the routines used to obsolete statements that are no longer referenced.

Functionally, the package acts as a controlled layer over the Knowledge Base element tables rather than a general-purpose API. Its procedures are consumed by the Knowledge Base authoring and maintenance flows, and it enforces duplication checks before write operations are committed to the base, translation, and security-denormalized tables.

Key Procedures and Functions

The documented interface exposes sixteen procedures and functions. The duplication functions — IS_ELEMENT_CREATED_DUP, IS_ELEMENT_DUP, and IS_ELEMENT_UPDATED_DUP — test whether a proposed element, or a proposed modification to an existing element, collides with an element already present in the repository. GET_ELEMENT_NUMBER and GET_LATEST_VERSION_ID resolve the element's logical number and its current highest version identifier respectively, supporting caller logic that must identify a specific revision. GET_WHO retrieves the standard creation and update audit attributes for an element.

The write routines are grouped by content type: CREATE_ELEMENT, UPDATE_ELEMENT, and DELETE_ELEMENT manage standard element records, while CREATE_ELEMENT_CLOB and UPDATE_ELEMENT_CLOB handle large-text element bodies. Similarly, CREATE_STATEMENT and UPDATE_STATEMENT insert and revise statements, with UPDATE_STATEMENT_ADMIN providing the administrative variant of statement maintenance. CREATE_CLOB supplies CLOB persistence for statement content, and OBSOLETE_UNUSED_STATEMENTS retires statement rows that are no longer in active use. Together these routines form the persistence and housekeeping surface for element and statement data in the Knowledge Base.

Tables Accessed

The package reads and writes the principal Knowledge Base element tables through APPS synonyms. CS_KB_ELEMENTS_B, CS_KB_ELEMENTS_TL, and CS_KB_ELEMENTS_S hold base, translated, and security/denormalized element data; CS_KB_ELEMENT_NUMBER_S, referenced directly in the search term cs_kb_element_number_s, supports element number sequencing and lookup. CS_KB_ELEMENT_TYPES_B defines element types, CS_KB_ELEMENT_LINKS stores relationships between elements, and CS_KB_CAT_GROUP_DENORM maintains the denormalized category grouping used for fast retrieval.

Set-related structures — CS_KB_SETS_B, CS_KB_SETS_VL, CS_KB_SET_CATEGORIES, and CS_KB_SET_ELES — govern how elements are grouped into sets and categories. Supporting technology tables and utilities include DBMS_LOB for CLOB manipulation and DUAL for singleton queries. The package also depends on infrastructure packages such as FND_API, FND_FILE, FND_GLOBAL, FND_LOG, FND_MESSAGE, FND_MSG_PUB, FND_PROFILE, CS_KB_SECURITY_PVT, CS_KB_ELEMENTS_PKG, and CS_KB_SYNC_INDEX_PKG, which together provide error handling, logging, security checks, and index synchronization.

Usage Notes

In Oracle EBS 12.1.1 and 12.2.2, CS_KB_ELEMENTS_AUDIT_PKG is invoked indirectly by the Knowledge Base authoring forms and by concurrent or batch maintenance programs that create, revise, or retire element statements. It is not referenced by any database object outside the APPS schema groupings noted above, and its audit routines are typically called from custom extensions that need element-level duplicate validation or statement retirement before committing to the element tables. Because the package spans base, translation, and CLOB storage, callers should treat each procedure as a transactional unit and allow the underlying FND message and logging framework to surface validation errors.