Search Results build_statement_text_query

Overview

CS_KNOWLEDGE_PVT is the private implementation package for the Oracle E-Business Suite Service (CS) Knowledge Management foundation. It is classified as a PVT (private) API package, meaning its procedures and functions are intended for internal consumption by the public knowledge API layer, notably CS_KNOWLEDGE_PUB, and by dependent Service modules rather than by customer or partner extension code. The package encapsulates the business logic required to define, maintain, and query the structural building blocks of the knowledge base: elements, element types, sets, set types, set categories, element-to-set relationships, external links, and solution or statement text.

In the context of Oracle EBS 12.1.1 and 12.2.2, the package operates within the APPS schema and is a VALID, compiled PL/SQL unit. It participates in the broader Knowledge Base (CS_KB) schema objects and provides the procedural glue that translates knowledge authoring and retrieval requests into DML against the underlying CS_KB_* tables. It also supports the construction of dynamic SQL predicates used for searching and locating knowledge content, which underpins the text and keyword search facilities exposed through the Service user interface and self-service channels.

Key Procedures and Functions

The ETRM metadata documents 42 procedures and functions. Representative examples include:

• BUILD_INTERMEDIA_QUERY, BUILD_SOLUTION_TEXT_QUERY, BUILD_SIMPLE_TEXT_QUERY, BUILD_STATEMENT_TEXT_QUERY, BUILD_KEYWORD_QUERY — construct search predicates and query fragments for locating knowledge solutions based on text, statements, keywords, or intermediate combinations.
• BIND_VAR_STRING — binds a string variable into a dynamically constructed query, supporting safe parameterization of search SQL.
• CONCAT_IDS — concatenates identifier values, typically for building IN-list or set-based lookup clauses.
• IS_SET_ELE_TYPE_VALID, DOES_SET_TYPE_EXIST, DOES_ELEMENT_TYPE_EXIST — validation functions confirming that referenced set types, element types, and set-element-type combinations exist before relationships are created or changed.
• DO_ELEMENTS_EXIST_IN_SET — verifies membership of elements within a given set.
• GET_WHO — returns the standard WHO columns (created by, updated by, and related audit context) for knowledge records.
• GET_EXTERNAL_OBJ_NAMES — resolves the external object names associated with knowledge elements or links.
• DEL_ELEMENT_FROM_SET, ADD_ELEMENT_TO_SET — manage membership of elements in knowledge sets.
• ADD_EXTERNAL_LINKS, CHANGE_ELE_TYPE_LINKS, CHANGE_SET_LINKS, CHANGE_ELEMENT_LINKS, CHANGE_ELEMENT_TO_SETS — maintain the link and relationship integrity between elements, element types, sets, and set-to-element associations, ensuring referential and hierarchical consistency.

Tables Accessed

The package reads and writes the core Knowledge Base tables through APPS synonyms:

• CS_KB_ELEMENTS_B, CS_KB_ELEMENT_TYPES_B, CS_KB_ELE_TYPE_LINKS, CS_KB_ELEMENT_LINKS — element definitions, their types, and the link structure connecting elements.
• CS_KB_SETS_B, CS_KB_SETS_TL, CS_KB_SET_TYPES_B, CS_KB_SET_CATEGORIES, CS_KB_SET_LINKS — set definitions, translations, classifications, and set-level relationships.
• CS_KB_SET_ELES, CS_KB_SET_ELE_TYPES — the membership mapping between sets and their constituent elements and element types.
• CS_KB_SOLN_CATEGORIES_B — solution categorization used during retrieval and authoring.
• CS_KB_VISIBILITIES_B — visibility and access scoping for knowledge content.
• CS_KB_HISTORIES_S, CS_KB_SET_USED_HISTS — historical and usage tracking records for audit and reporting.

These objects support both transactional maintenance of knowledge structures and the search queries executed by the query-building routines.

Usage Notes

CS_KNOWLEDGE_PVT is primarily invoked indirectly. It is referenced by CS_KNOWLEDGE_PUB, the public API, and by CS_KNOWLEDGE_GRP, CS_KB_CONC_PROG_PKG, and SR_UWQ_INTEG. This pattern indicates it is called from concurrent programs (via CS_KB_CONC_PROG_PKG), from group or bulk processing logic (CS_KNOWLEDGE_GRP), and from Service request and Universal Work Queue integration flows (SR_UWQ_INTEG). Customer forms and custom code should use the public API rather than calling the PVT package directly, since private procedures may change between releases. Typical invocation paths are therefore the Service Knowledge authoring forms, knowledge search and retrieval screens, and background programs that synchronize or process knowledge content. Because it is a private package, it is not a supported extension point.