Search Results hr_api_transaction_values_pk




Overview
Explore in AI Chat

Overview

The HR_API_TRANSACTION_VALUES table is a core data structure within the Oracle E-Business Suite Human Resources (PER) module. It is documented as storing "Kiosk workflow data columns and values," which identifies it as the persistence layer for the transient data captured and manipulated during a self-service or kiosk-style transaction. In Oracle EBS 12.1.1 and 12.2.2, the HR APIs that drive kiosk and self-service workflows assemble a set of named parameters, each of which is bound to a value. HR_API_TRANSACTION_VALUES is the table that materializes those bindings, holding one row per column or parameter within a given transaction step.

The object carries 18 documented columns and is owned by the HR schema, with a status of VALID in the ETRM reference for 12.2.2. Its structural relationship to HR_API_TRANSACTION_STEPS indicates that the value rows are organized hierarchically by step. Based on the foreign-key topology – a single parent reference to HR_API_TRANSACTION_STEPS and downstream references from tables such as PQH_SS_VALUE_HISTORY – the heuristic Data Vault classification is satellite-leaning. This suggests the table is best modeled as a satellite attached to the transaction step hub or link, rather than as an independent hub, because its identity and semantic context are derived from the parent step.

Key Information Stored

The most important columns fall into three groups: identity, parameter definition, and value payload.

This tri-typed value pattern (current, original, previous) is unusual and reflects the need to track how kiosk transaction data evolves across a workflow before the transaction is finalized.

Common Use Cases and Queries

Typical usage centers on diagnosing and reporting self-service transactions. A common pattern joins the value table to its parent step to reconstruct a transaction:

  • Reconstructing a transaction step's parameter set by selecting NAME, DATATYPE, and the matching typed value column filtered on TRANSACTION_STEP_ID.
  • Auditing changes by comparing VARCHAR2_VALUE or NUMBER_VALUE against ORIGINAL_ and PREVIOUS_ counterparts.
  • Reporting on pending kiosk transactions by aggregating value rows per TRANSACTION_STEP_ID.

A representative SQL pattern:

  • SELECT v.NAME, v.DATATYPE, v.VARCHAR2_VALUE, v.NUMBER_VALUE, v.DATE_VALUE FROM hr.hr_api_transaction_values v WHERE v.TRANSACTION_STEP_ID = :step_id;

Related Objects

  • HR_API_TRANSACTION_STEPS – parent table joined on HR_API_TRANSACTION_VALUES.TRANSACTION_STEP_ID = HR_API_TRANSACTION_STEPS.TRANSACTION_STEP_ID.
  • PQH_SS_VALUE_HISTORY – references this table via TRANSACTION_VALUE_ID, capturing value history for self-service transactions.
  • HR_API_TRANSACTION_VALUES_PK – the primary-key index enforcing uniqueness on TRANSACTION_VALUE_ID.
  • The HR kiosk and self-service workflow APIs that populate these value rows during transaction processing.