Results for “entry_date”

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

Overview

CS_KB_HISTORIES_B is the base table for the Oracle E-Business Suite Service (CS) Knowledge Base history function. It is owned by the CS schema and carries a status of VALID in both Oracle EBS 12.1.1 and 12.2.2. In functional terms, this table stores the header record for a Knowledge Base history entry — a single logical revision, snapshot, or event that groups the changes, elements, and set associations relevant to a Knowledge Base article at a point in time. Rather than holding the full body of an article, it anchors the history metadata: who created the history entry, when the entry occurred, and which security group governs visibility.

Consistent with a Data Vault modeling heuristic mined from its foreign key structure, CS_KB_HISTORIES_B is classified as hub-leaning. Its primary key, CS_KB_HISTORIES_B_PK on HISTORY_ID, is a surrogate identifier that is referenced by multiple child tables. This positions the table as a central rallying point — a hub — around which history-related satellites and detail tables cluster. Designers mapping this schema into a Data Vault or dimensional model would typically treat HISTORY_ID as the hub key, with descriptive attributes carried in satellites and multilingual text held in companion tables.

Key Information Stored

The documented physical schema for 12.2.2 lists 26 columns. The most significant are:

• HISTORY_ID — the surrogate primary key (CS_KB_HISTORIES_B_PK). This is the join key referenced by all child history tables. A unique index, CS_KB_HISTORIES_B_U1, also exists on HISTORY_ID, confirming it as the sole documented business-key candidate.
• HISTORY_NAME — the user-facing label for the history entry.
• USER_ID — the user responsible for the history record; foreign key to FND_USER.
• ENTRY_DATE — the functional timestamp of when the history entry was logged, distinct from the standard audit columns.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, controlling record-level visibility.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard EBS audit trail columns, populated by the application framework.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the prescribed DFF (Descriptive Flexfield) container, provided for customer extensibility.

The multilingual descriptive text associated with each history is not stored here; it resides in CS_KB_HISTORIES_TL, joined on HISTORY_ID, which is the standard EBS translation-table pattern.

Common Use Cases and Queries

The primary use case is audit and change tracking for Knowledge Base content: surfacing which knowledge entries changed, who performed the change, and when. A typical query joins the base table to FND_USER to resolve the actor and to the translation table to retrieve the display name:

SELECT h.HISTORY_ID, t.HISTORY_NAME, u.USER_NAME, h.ENTRY_DATE
FROM CS_KB_HISTORIES_B h,
     CS_KB_HISTORIES_TL t,
     FND_USER u
WHERE h.HISTORY_ID = t.HISTORY_ID
  AND h.USER_ID = u.USER_ID
  AND t.LANGUAGE = USERENV('LANG');

Other scenarios include: reconstructing the sequence of article revisions over a date range using ENTRY_DATE; enforcing security-group filtering in custom Knowledge Base reports by joining FND_SECURITY_GROUPS on SECURITY_GROUP_ID; and reconstructing element-level or set-level change detail by joining the child change-history tables. Reporting consumers (OBIEE, BI Publisher, or custom concurrent programs) typically treat this table as the driver of a history header of a transactional history report.

Related Objects

The following related objects are documented through the foreign key and primary key relationship data:

• FND_USER — referenced by CS_KB_HISTORIES_B.USER_ID; resolves the user who created or owns the history entry.
• FND_SECURITY_GROUPS — referenced by CS_KB_HISTORIES_B.SECURITY_GROUP_ID; governs functional security visibility.
• CS_KB_SET_CHG_HISTS — child table referencing CS_KB_HISTORIES_B.HISTORY_ID via its own HISTORY_ID; records set-level change details.
• CS_KB_ELE_CHG_HISTS — child table referencing HISTORY_ID; records element-level change details.
• CS_KB_HISTORIES_TL — the multilingual translation table keyed to HISTORY_ID.
• CS_KB_SET_USED_HISTS — child table keyed to HISTORY_ID; records set-usage history associated with the entry.