Search Results hr_api_transactions




Overview
Explore in AI Chat

Overview

HR_API_TRANSACTIONS is a Human Resources (PER) transactional table in the Oracle E-Business Suite HR schema. It stores the state and context of in-progress kiosk and self-service API processes, functioning as the parent record for a discrete unit of work submitted through Oracle HRMS business process APIs. Each row represents a single transaction instance, capturing who initiated it, what product and function were invoked, the current processing status, and the reference records affected. Because HRMS business process APIs (such as the person, assignment, and compensation APIs) run asynchronously or as multi-step operations, this table provides the persistent header that coordinates those steps.

Under a heuristic Data Vault classification mined from the foreign key structure, HR_API_TRANSACTIONS is hub-leaning. In Data Vault terms it behaves as a hub: it is keyed by a single surrogate identifier and is referenced by dependent detail tables rather than being a pure association link or descriptive satellite. This classification is a modeling suggestion, not an enforced constraint.

Key Information Stored

The documented physical schema defines 34 columns. The most functionally significant are listed below.

Audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_ROLE) follow standard EBS conventions. Only TRANSACTION_ID is a documented unique business-key candidate via the primary key; the SYS_IL indexes are internal LOB indexes, not business keys.

Common Use Cases and Queries

Primary use cases include monitoring stalled or in-progress kiosk transactions, diagnosing API failures, and auditing self-service activity by creator or person.

  • Locate active transactions for a given state: SELECT transaction_id, process_name, status, transaction_state FROM hr_api_transactions WHERE transaction_state = :p_state;
  • Trace activity for a person: SELECT transaction_id, transaction_type, creation_date FROM hr_api_transactions WHERE selected_person_id = :p_person_id ORDER BY creation_date DESC;
  • Resolve the affected entity via the polymorphic reference: join TRANSACTION_REF_TABLE and TRANSACTION_REF_ID to the indicated base table.
  • Group compound operations using PARENT_TRANSACTION_ID to reconstruct the transaction tree.

Related Objects

  • HR_API_TRANSACTION_STEPS — child detail table; joins on TRANSACTION_ID (HR_API_TRANSACTION_STEPS.TRANSACTION_ID → HR_API_TRANSACTIONS.TRANSACTION_ID). Holds the individual processing steps for each transaction.
  • BEN_RPTG_GRP — referenced by HR_API_TRANSACTIONS.RPTG_GRP_ID; the reporting group associated with the transaction.
  • PER_ALL_PEOPLE_F — resolved through SELECTED_PERSON_ID and CREATOR_PERSON_ID for person-level reporting.
  • PER_ALL_ASSIGNMENTS_F — resolved through ASSIGNMENT_ID where employment terms are affected.
  • FND_USER — associated with CREATOR_PERSON_ID and audit columns to identify the acting user.