Search Results hr_api_transaction_steps




Overview
Explore in AI Chat

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

Overview

The HR_API_TRANSACTION_STEPS table is a core data object within the Oracle E-Business Suite Human Resources (PER) product module. It stores the individual workflow step rows that make up a kiosk-style transaction, forming the granular, ordered components processed within a single HR API transaction. Each row represents one discrete step within a larger transactional unit, capturing the API to be invoked, its sequencing, and a broad set of generic key/value attributes that support flexible, self-describing processing.

In Data Vault modeling terms, this object is classified heuristically as satellite-leaning. This suggests it functions primarily as a descriptive, attribute-bearing structure attached to a parent transaction entity rather than acting as an independent hub of business keys. Its surrogate key and dependent relationship to HR_API_TRANSACTIONS reinforce that the table is best modeled as a detail or satellite component of the transaction hub. The object resides in the HR schema and holds a fully documented, VALID schema of 56 physical columns in ETRM 12.2.2.

Key Information Stored

The table is anchored by its surrogate primary key, TRANSACTION_STEP_ID, defined through the unique index HR_API_TRANSACTION_STEPS_PK. This column is the sole documented unique business-key candidate; all other attributes are descriptive or foreign-referencing.

Common Use Cases and Queries

The table is most often queried to inspect the step-by-step composition of an HR API transaction, to troubleshoot failed kiosk or self-service workflows, and to report on API invocation sequences. Because steps carry a PROCESSING_ORDER, they are frequently retrieved in sequence for a given transaction.

A typical query retrieving all steps for one transaction, joined to its parent, follows:

  • SELECT s.transaction_step_id, s.api_name, s.processing_order, s.object_state FROM hr.hr_api_transaction_steps s WHERE s.transaction_id = :p_transaction_id ORDER BY s.processing_order;
  • SELECT s.transaction_id, t.api_name, s.api_name step_api, s.item_type, s.item_key FROM hr.hr_api_transaction_steps s JOIN hr.hr_api_transactions t ON s.transaction_id = t.transaction_id;

Reporting scenarios commonly aggregate steps by API_NAME or OBJECT_STATE to measure throughput and error rates, while diagnostic queries join to HR_API_TRANSACTION_VALUES to resolve the generic INFORMATION columns into specific field values.

Related Objects

The following objects are the most significant dependencies derived from the documented foreign-key relationships:

  • HR_API_TRANSACTIONS — Parent table; joined via HR_API_TRANSACTION_STEPS.TRANSACTION_ID to HR_API_TRANSACTIONS.TRANSACTION_ID.
  • HR_API_TRANSACTION_VALUES — Child table referencing this object through TRANSACTION_STEP_ID.
  • HR_API_TRANSACTIONS_PK — Primary-key constraint supporting the parent linkage.
  • HR_API_TRANSACTION_STEPS_PK — Unique index and primary-key constraint on TRANSACTION_STEP_ID.
  • PER API (HR_API) Framework — The application logic that reads and processes these steps during transaction execution.