Search Results pqh_de_operations




Overview
Explore in AI Chat

Overview

The PQH_DE_OPERATIONS table is a transaction and configuration data object owned by the HR schema within the Oracle E-Business Suite, and it belongs to the PQH — Public Sector HR product family. In the ETRM 12.2.2 physical schema the table is documented as DE - Operations, where "DE" refers to the Public Sector Human Resources process known as Document Employment or, in certain deployments, Data Element processing. The table serves as a reference repository of discrete operations that the Public Sector HR subsystem records and executes against employee assignment, position, and budget data.

The object is documented with a heuristic Data Vault classification of standalone. This suggests that, from a modeling perspective, PQH_DE_OPERATIONS behaves as a self-contained reference entity rather than as a hub, link, or satellite connected to a broader integration fabric. The absence of mined foreign-key relationships reinforces that classification: the table does not participate in declared parent-child joins within the ETRM relational graph, and it is typically consumed as a lookup or staging source by concurrent programs and forms rather than as a detail table within a normalized entity hierarchy.

Key Information Stored

The table's documented physical structure contains nine columns. The most significant are summarized below.

  • OPERATION_ID — The surrogate primary key, enforced by the PQH_DE_OPERATIONS_PK constraint and backed by the unique index PQH_DE_OPERATIONS. This column is the canonical identifier used by every consumer of the table.
  • OPERATION_NUMBER — A human-readable business-key candidate. The unique index on OPERATION_ID is the only documented unique index, but OPERATION_NUMBER functions as the natural key by which users and programs typically reference an operation.
  • DESCRIPTION — The free-text label describing the operation, used in list-of-values prompts, reports, and audit output.
  • OBJECT_VERSION_NUMBER — The standard EBS optimistic-locking column, incremented on every update to detect concurrent modification.
  • CREATED_BY, CREATION_DATE — The standard WHO audit columns recording the creating user and timestamp.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard WHO audit columns recording the last modifying user, timestamp, and login session.

The surrogate key OPERATION_ID should be treated as the join and reference column throughout; the business-key candidate OPERATION_NUMBER is the appropriate column for user-facing lookups and cross-system mapping.

Common Use Cases and Queries

Typical consumers of PQH_DE_OPERATIONS include Public Sector HR concurrent programs, Oracle Forms-based maintenance screens, and reporting queries that resolve an operation identifier to a readable description.

A standard resolution query joining the operation to its audit context:

SELECT operation_id,
       operation_number,
       description,
       last_updated_by,
       last_update_date
  FROM   hr.pqh_de_operations
 WHERE  operation_number = :p_number;

A driver query used when feeding a downstream validation routine or a staging extract:

SELECT o.operation_id,
       o.operation_number,
       o.description
  FROM   hr.pqh_de_operations o
 WHERE  o.last_update_date >= :p_last_run
 ORDER  BY o.operation_number;

Because the table is classified as standalone, reporting models should treat it as a dimension or code-lookup source rather than as a fact table. Extract, transform, and load routines populating a data warehouse typically promote OPERATION_ID to the dimension surrogate key and OPERATION_NUMBER to the natural business key.

Related Objects

The ETRM relationship data documents no foreign keys from PQH_DE_OPERATIONS, consistent with its standalone classification. The following objects are the most significant consumers or logical associates in the Public Sector HR arena, joined on OPERATION_ID or OPERATION_NUMBER where the surrounding PQH model permits.

  • PQH_DE_OPERATIONS_PK — The primary key constraint on OPERATION_ID; the authoritative uniqueness guarantee.
  • PQH_DE_OPERATIONS (unique index) — The unique index on OPERATION_ID used for index-based access paths.
  • HR.PER_ALL_PEOPLE_F — The person/assignment master most commonly referenced when operation records are attached to an employee in Public Sector HR flows.
  • HR.PER_ALL_ASSIGNMENTS_F — The assignment table against which operational actions are frequently validated.
  • PQH_DE_OPERATION_UNITS — A logical companion table where per-unit operation attributes are held; joined on OPERATION_ID at the application layer.
  • FND_LOOKUP_VALUES — Provides the standard EBS lookup mechanism when operation types or statuses are configured outside the DESCRIPTION column.
  • FND_CONCURRENT_REQUESTS — The driver of any batch process that consumes or maintains operation records.

Consultants maintaining this table should preserve the WHO audit columns and the OBJECT_VERSION_NUMBER value on every update, as EBS forms rely on them for concurrency control.