Results for “transaction_group”

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

Overview

PQH_SS_TRANSACTION_HISTORY is a self-service transaction history table owned by the HR schema within the Public Sector HR (PQH) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It records the audit trail of self-service transactions initiated by employees, managers, and HR administrators through the Oracle Self-Service HR (SSHR) framework, also known as the Manager and Employee Self-Service (MSS/ESS) pages. Each row captures a discrete transactional item — such as a promotion, transfer, termination, or assignment change — along with the identifiers required to reconstruct which person initiated it, which assignment was affected, and what workflow or approval process routed it.

The table is classified as standalone under the heuristic Data Vault classification mined from its foreign key structure. In Data Vault modeling terms, this suggests the table behaves less as a pure hub-and-satellite chain and more as a self-contained transaction ledger: its surrogate primary key does not serve as a hub business key distributed to many downstream satellites, and its outbound foreign keys are limited. Analysts modeling this object for a data warehouse may therefore treat it as a source for a single satellite or transaction fact, rather than as the anchor of an extended link structure.

Key Information Stored

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

• TRANSACTION_HISTORY_ID — the surrogate primary key, enforced by unique index PQH_SS_TRANSACTION_HISTORY_PK. This is the only documented business-key candidate.
• CREATOR_PERSON_ID — the person who initiated the self-service transaction.
• SELECTED_PERSON_ID — the person the transaction was performed for, which may differ from the creator in manager-initiated scenarios.
• ASSIGNMENT_ID — the assignment affected by the transaction.
• ITEM_TYPE and ITEM_KEY — classify the transactional item and identify its underlying record.
• APPROVAL_ITEM_TYPE and APPROVAL_ITEM_KEY — describe the approval artifact generated for the transaction.
• PROCESS_NAME — the name of the workflow or business process handling the transaction.
• FUNCTION_ID, RPTG_GRP_ID, and PLAN_ID — reference functional configuration, reporting groups, and plans relevant to the transaction context.
• TRANSACTION_GROUP and TRANSACTION_IDENTIFIER — group related transactions and uniquely identify the transaction across the self-service framework.
• Standard audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical usage includes auditing self-service activity for a person or assignment, tracing approval routing, and building HR analytics on transaction volumes. A representative query lists transactions for a specific assignment over a date range:

SELECT transaction_history_id,
       creator_person_id,
       selected_person_id,
       item_type,
       process_name,
       creation_date
FROM   hr.pqh_ss_transaction_history
WHERE  assignment_id = :p_assignment_id
AND    creation_date BETWEEN :p_start AND :p_end
ORDER BY creation_date DESC;

To analyze approval workload, analysts commonly group by APPROVAL_ITEM_TYPE and PROCESS_NAME. For reporting groups, a join on RPTG_GRP_ID surfaces the reporting context. Because the table is a standalone ledger, aggregated extracts typically feed HR dashboards or compliance audits rather than supporting complex multi-hop joins.

Related Objects

• AR_TRANSACTION_HISTORY_ALL — referenced via TRANSACTION_HISTORY_ID; links the self-service record to the broader transaction history framework.
• BEN_RPTG_GRP — referenced via RPTG_GRP_ID; defines the reporting group applied to the transaction.
• PER_ALL_ASSIGNMENTS_F — joined on ASSIGNMENT_ID for assignment details.
• PER_ALL_PEOPLE_F — joined on CREATOR_PERSON_ID and SELECTED_PERSON_ID for person attributes.
• WF_ITEMS / WF_PROCESS_ACTIVITIES — joined on ITEM_KEY and ITEM_TYPE to trace workflow progress.
• PQH_SS_* SSHR views — self-service pages consuming this history for display.