Results for “ghr_remarks”

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

Overview

GHR_REMARKS is a reference table in the HR schema belonging to the GHR — US Federal Human Resources product family within Oracle E-Business Suite. It stores the master list of standardized remarks that federal agencies apply to a Request for Personnel Action (RPA). Rather than allowing free-text comments on every personnel action, GHR_REMARKS provides a controlled vocabulary of remark codes and descriptions, which are then linked to specific RPAs through the intersection tables GHR_NOAC_REMARKS and GHR_PA_REMARKS. This design enforces consistency in federal HR documentation and supports reporting against remark categories using stable codes rather than unnormalized text.

Under the heuristic Data Vault classification mined from its foreign-key structure, GHR_REMARKS is hub-leaning. It carries a stable surrogate key (REMARK_ID) referenced by multiple downstream tables, which is characteristic of a hub. This classification should be treated as a modeling suggestion rather than a documented architectural declaration; GHR_REMARKS also carries descriptive attributes (such as CODE, DESCRIPTION, and effective-date columns) that give it satellite-like characteristics.

Key Information Stored

The documented physical schema for 12.2.2 contains 13 columns in the HR schema. The most significant are:

• REMARK_ID — surrogate primary key of GHR_REMARKS_PK; the internal identifier referenced by child tables.
• CODE — business-key candidate (unique index GHR_REMARKS_U1 alongside ZD_EDITION_NAME); the short remark code exposed to users.
• DESCRIPTION — the full text of the remark as printed on the personnel action.
• PA_NOTIFICATION_ORDERING — controls the sort sequence in which remarks appear on notifications or printed actions.
• ENABLED_FLAG — determines whether the remark is selectable on new RPAs.
• DATE_FROM / DATE_TO — effective-dating bounds controlling remark validity over time.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard EBS WHO columns used for auditing and concurrency handling.
• ZD_EDITION_NAME — edition identifier used for edition-based redefinition (EBR); both unique indexes include it, so CODE and REMARK_ID are only unique within an edition.

Common Use Cases and Queries

The primary use case is validation and lookup when building or reviewing an RPA. A typical query retrieves all active remarks currently in effect:

• Active remark picklist: SELECT remark_id, code, description FROM hr.ghr_remarks WHERE enabled_flag = 'Y' AND TRUNC(SYSDATE) BETWEEN date_from AND NVL(date_to, TRUNC(SYSDATE)) ORDER BY pa_notification_ordering;
• Remarks attached to a personnel action: join through GHR_PA_REMARKS to report all remarks recorded against an action, then resolve descriptions back to GHR_REMARKS by REMARK_ID.
• Notification generation: ordering remarks by PA_NOTIFICATION_ORDERING ensures printed actions and notifications present remarks in the agency's prescribed sequence.
• Federal reporting: grouping personnel actions by remark CODE supports audits, EEO analysis, and legal-hold reporting without parsing free text.
• Data cleanup: identifying remarks disabled (ENABLED_FLAG = 'N') yet still referenced by historical records, using outer joins from GHR_PA_REMARKS to GHR_REMARKS.

Related Objects

GHR_REMARKS is referenced by two documented child tables, both via REMARK_ID:

• GHR_NOAC_REMARKS — associates remarks with Notice of Action (NOAC) records; join on GHR_NOAC_REMARKS.REMARK_ID = GHR_REMARKS.REMARK_ID.
• GHR_PA_REMARKS — associates remarks with personnel actions; join on GHR_PA_REMARKS.REMARK_ID = GHR_REMARKS.REMARK_ID.

In practice, reporting queries traverse GHR_PA_REMARKS → GHR_REMARKS to resolve remark text, and GHR_REMARKS is used as a lookup by any federal HR UI that permits entry of remarks on an RPA. Because REMARK_ID is the shared foreign key across these relationships, referential integrity is maintained at the surrogate-key level while CODE and ZD_EDITION_NAME enforce business uniqueness within each edition.