Search Results pqh_fr_validation_events




Overview
Explore in AI Chat

Overview

The PQH_FR_VALIDATION_EVENTS table is a Public Sector HR (PQH) application object residing in the HR schema. Its documented purpose is to store the details regarding events associated with a particular validation. The table functions as a transactional detail store that records individual event occurrences tied to a parent validation record, typically in support of French public sector regulatory validation processing where predefined rules are evaluated against employee or assignment data.

The table is owned by HR and is classified as VALID across both Oracle EBS 12.1.1 and 12.2.2. Under the heuristic Data Vault classification derived from its foreign key structure, PQH_FR_VALIDATION_EVENTS is satellite-leaning. In modeling terms, this suggests the table behaves as a descriptive satellite attached to a parent business entity (the validation), holding time-stamped, context-dependent attributes rather than serving as an independent hub or as a pure associative link between two business keys.

Key Information Stored

The table contains 13 documented columns. The most significant columns are:

  • VALIDATION_EVENT_ID — Surrogate primary key defined by the PQH_FR_VALIDATION_EVENTS_PK unique index. Uniquely identifies each validation event row.
  • VALIDATION_ID — Foreign key to PQH_FR_VALIDATIONS. Establishes the parent-child relationship between a validation and its events. This is the primary join column in most reporting queries.
  • EVENT_TYPE — Classifies the category of event recorded against the validation, allowing the application to distinguish event behavior at a grouped level.
  • EVENT_CODE — Provides the specific coded identifier for the event, refining the EVENT_TYPE category into discrete lookup values.
  • START_DATE and END_DATE — Define the effective period during which the event applies, supporting date-effective querying and historical reconstruction of validation state.
  • COMMENTS — Free-text annotation capturing contextual explanation for the event.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, OBJECT_VERSION_NUMBER — Standard Oracle EBS who-columns and optimistic locking column. OBJECT_VERSION_NUMBER is used by the framework to detect concurrent updates.

No business-key unique index beyond the surrogate primary key is documented. VALIDATION_ID is a non-unique foreign key, indicating many events may attach to a single validation.

Common Use Cases and Queries

Typical usage centers on tracing the sequence of events raised during a public sector validation cycle, auditing failed or expired validations, and reporting on event volume by type or code. A representative query retrieving all events for a given validation is:

  • SELECT ve.validation_event_id, ve.event_type, ve.event_code, ve.start_date, ve.end_date, ve.comments FROM pqh_fr_validation_events ve WHERE ve.validation_id = :p_validation_id ORDER BY ve.start_date

Reporting by event classification commonly joins to the parent validation table:

  • SELECT v.validation_id, ve.event_type, COUNT(*) FROM pqh_fr_validations v JOIN pqh_fr_validation_events ve ON ve.validation_id = v.validation_id GROUP BY v.validation_id, ve.event_type

Date-effective filtering (for example, active events as of a reporting date) uses START_DATE and END_DATE to bound results. Audit extracts typically select the who-columns alongside COMMENTS to establish change provenance.

Related Objects

The principal related objects are:

  • PQH_FR_VALIDATIONS — Parent table joined via PQH_FR_VALIDATION_EVENTS.VALIDATION_ID = PQH_FR_VALIDATIONS.VALIDATION_ID. This is the documented foreign key relationship from the metadata.
  • PQH_FR_VALIDATIONS_PK — The primary key constraint on the parent table, supporting the referential integrity of the relationship.
  • PQH_FR_VALIDATION_EVENTS_PK — The unique index enforcing uniqueness of VALIDATION_EVENT_ID on this table.
  • PER_ALL_PEOPLE_F and PER_ALL_ASSIGNMENTS_F — Frequently joined indirectly through validation logic to resolve the employee or assignment context of an event.
  • FND_LOOKUPS / HR_LOOKUPS — Typical source for decoding EVENT_TYPE and EVENT_CODE values into user-readable descriptions.
  • PQH_FR_VALIDATION_RESULTS and related validation-processing tables — Consulted alongside events when producing full validation outcome reporting.
  • FND_AUDIT and standard who-column views — Reference LAST_UPDATED_BY and CREATED_BY for audit trails.