Search Results hr_transaction_ss




Overview
Explore in AI Chat

Overview

APPS.HR_TRANSACTION_SS is a server-side PL/SQL package body in Oracle E-Business Suite (validated across 12.1.1 and 12.2.2) that provides the transaction management foundation for the self-service Human Resources flows delivered through Oracle Approvals Management (AME) and Oracle Workflow. Its central responsibility is to encapsulate the lifecycle of an HR self-service transaction: creating the transaction envelope, recording each step, validating the proposed change, persisting save-for-later state, submitting for approval, committing or rolling back, and retrying after an error. Because the package exposes a coordinated set of routines rather than a single API, it functions as the internal engine behind web-based HR actions such as new-hire registration, person and assignment changes, and appraisal submissions. The ETRM record classifies it as an OTHER-type API owned by APPS and confirms it is referenced by 59 other database objects, underscoring its role as a shared service in the HR self-service stack.

Key Procedures and Functions

Twenty-eight documented procedures and functions are organized around the transaction lifecycle:

Tables Accessed

The package reads and writes the core self-service transaction tables through APPS synonyms. HR_API_TRANSACTIONS holds the transaction header, while HR_API_TRANSACTION_STEPS and HR_API_TRANSACTION_VALUES store individual step definitions and their captured values. Workflow integration relies on WF_ITEMS and WF_ITEM_ATTRIBUTE_VALUES to persist item state and attribute data. FND_FORM_FUNCTIONS supplies the form function context for the invoked web action, and FND_USER resolves the acting user. PER_APPRAISALS supports appraisal-related transactions. DBMS_SQL and PLITBLM are used for dynamic SQL and PL/SQL table handling.

Usage Notes

HR_TRANSACTION_SS is typically invoked indirectly. Self-service forms (for example, person or assignment management) and the Oracle Workflow approval process call it through the HR_TRANSACTION_SWI and HR_TRANSACTION_API layers. Related packages including HR_APPROVAL_SS, HR_PROCESS_PERSON_SS, HR_NEW_USER_REG_SS, HR_APPRAISAL_WORKFLOW_SS, and PQH_SS_WORKFLOW depend on it, and it reaches AME through AME_API and AME_UTIL. Custom integrations rarely call it directly; where needed, the recommended pattern is to drive transactions through the supported HR_TRANSACTION_API and SWI interfaces so that step, approval, and rollback semantics remain intact.