Results for “cs_kb_integration_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.CS_KB_INTEGRATION_V view is a Service (CS) module integration object within Oracle E-Business Suite 12.1.1 and 12.2.2. It provides a unified, read-only projection that joins JTF Notes records with Knowledge Management element links and set links, exposing both note-based and element-based knowledge content through a single interface. The view is catalogued as VALID in the ETRM metadata with the description: "View combines JTF notes with knowledge management element links and set links. Used by Knowledge Management for integration from any application module."

In practice, CS_KB_INTEGRATION_V acts as a normalization layer. Rather than requiring consuming modules to query JTF_NOTES_B, CS_KB_ELEMENT_LINKS, and the associated type/lookup tables individually, the view presents a consistent row shape with metadata columns such as RECORD_SOURCE_TYPE, TRUE_STMT, and creation/audit attributes. This supports the Oracle Knowledge Management integration framework, allowing notes and knowledge elements to be surfaced together for search, retrieval, and display from any application module that calls into the knowledge base.

Underlying Base Objects

The view is defined over both JTF note structures and CS knowledge base structures, joined through lookup and type tables. The documented referenced base objects include:

• JTF_NOTES_B and JTF_NOTES_TL — the base and translated note tables.
• CS_KB_ELEMENTS_B and CS_KB_ELEMENTS_TL — knowledge element base and translation tables.
• CS_KB_ELEMENT_LINKS and CS_KB_ELE_TYPE_LINKS — linkage tables connecting elements to application objects and note types.
• CS_KB_ELEMENT_TYPES_B and CS_KB_ELEMENT_TYPES_TL — element type definitions.
• CS_KB_SETS_B, CS_KB_SETS_TL, CS_KB_SET_LINKS, CS_KB_SET_TYPES_B, CS_KB_SET_TYPES_TL — knowledge set and set-type structures.
• FND_LOOKUP_VALUES / FND_LOOKUPS — lookup meanings for note types.
• FND_GLOBAL — session environment functions (USERENV('LANG')).
• JTF_OBJECTS_B — source application object codes.

The view union-all combines a note branch (JTF_NOTES_B joined to note translations, element-type links, element types, and note-type lookups) with an element branch (CS_KB_ELEMENT_LINKS joined to element, element-type, and object metadata). Both branches are restricted to the session language via USERENV('LANG'), ensuring translated content is returned in the caller's locale.

Key Columns

• ROW_ID / ID — the source row identifier and primary key of the note or element.
• APP_OBJ_ID / APP_OBJ_CODE — the source application object identifier and code the record is attached to.
• NOTE_TYPE_CODE / NOTE_TYPE_MEANING — the note type lookup code and its translated meaning.
• KB_TYPE_ID / KB_TYPE_MEANING — the knowledge element type identifier and name.
• STATUS — note status where applicable.
• NOTE — the note text or element name content.
• TRUE_STMT — a 'T'/'F' flag derived from the link type, indicating a true or false relationship.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns carried from the source record.
• RECORD_SOURCE_TYPE — discriminator returning 'JTF_NOTE' or 'KB_ELEM' to indicate which branch produced the row.

Common Use Cases and Queries

Typical scenarios include retrieving all knowledge content attached to a given application object, reporting note and element counts by type, and feeding an integration interface that must present notes and knowledge elements uniformly.

Example: list all knowledge records for a specific source object.

SELECT id, record_source_type, app_obj_code, kb_type_meaning, note
FROM   apps.cs_kb_integration_v
WHERE  app_obj_code = :p_object_code
ORDER BY creation_date DESC;

Example: count records by knowledge source type.

SELECT record_source_type, COUNT(*)
FROM   apps.cs_kb_integration_v
GROUP BY record_source_type;

Because the view includes both element links and set links and filters on USERENV('LANG'), queries execute under APPS credentials and return locale-appropriate translations. It should be treated as a read-only integration surface rather than a maintenance object.