Search Results hr_comments




Overview
Explore in AI Chat

Overview

HR_COMMENTS is a table in the HR schema of Oracle E-Business Suite, classified under the PER (Human Resources) product module. It serves as the central repository for comments within the Oracle HRMS data model. Unlike transactional tables that capture events or balances, HR_COMMENTS functions as a general-purpose text storage facility, allowing comment text to be associated with records in other tables through the SOURCE_TABLE_NAME column. This design pattern enables the application to attach free-form annotations to a wide range of human resources entities without requiring a dedicated comments column on each underlying table.

The object holds a VALID status in the ETRM reference for both 12.1.1 and 12.2.2. Its documented physical schema in 12.2.2 contains eight columns, with the primary key HR_COMMENTS_PK defined on COMMENT_ID. The heuristic Data Vault classification mined from the foreign key structure is standalone. In Data Vault modeling terms, this suggests the table may be treated as an independent hub-like structure rather than a dependent satellite or link, since no foreign key relationships to other tables were detected in the documented metadata. Modelers should treat this as a modeling suggestion only, since the absence of documented foreign keys does not preclude logical references through the SOURCE_TABLE_NAME column.

Key Information Stored

The eight documented columns capture identity, audit, and content information:

  • COMMENT_ID — the surrogate primary key, generated to uniquely identify each comment row and forming the basis of the HR_COMMENTS_PK unique index.
  • SOURCE_TABLE_NAME — identifies the originating table or entity to which the comment belongs. This is the principal business-key candidate for locating comments in context, since it directs consumers to the correct parent record type.
  • COMMENT_TEXT — the actual free-form comment content, stored as the substantive payload of the row. A supplemental LOB segment (evidenced by the SYS_IL index on column eight) supports the text storage.
  • CREATION_DATE and CREATED_BY — the standard WHO columns recording when and by which user the comment was first created.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — audit columns capturing the most recent modification timestamp, the responsible user, and the login session that performed the update.

No additional business-key unique indexes beyond HR_COMMENTS_PK are documented, so COMMENT_ID remains the sole guaranteed unique identifier.

Common Use Cases and Queries

Typical usage involves retrieving or auditing comments tied to specific HR entities. A common query pattern filters by the sourcing table and joins to the relevant business object:

  • Scenario 1 — Retrieve comments for a given entity type: SELECT comment_id, comment_text, created_by, creation_date FROM hr.hr_comments WHERE source_table_name = :table_name ORDER BY creation_date DESC;
  • Scenario 2 — Audit who last touched a comment: SELECT comment_id, last_updated_by, last_update_date, last_update_login FROM hr.hr_comments WHERE trunc(last_update_date) = trunc(sysdate);
  • Scenario 3 — Reporting volume by source: aggregate COUNT(*) grouped by SOURCE_TABLE_NAME to understand comment distribution across modules.

Because comments are text-based, downstream reporting often extracts COMMENT_TEXT into data marts for analysis or inclusion in employee documentation packs.

Related Objects

The documented metadata records no foreign key relationships, consistent with the standalone Data Vault classification. Logical dependencies are therefore driven by the SOURCE_TABLE_NAME value rather than physical constraints:

Consumers should join HR_COMMENTS to these objects using application logic keyed on SOURCE_TABLE_NAME, since no formal referential integrity is documented.