Search Results check_txn_step_exists

Overview

APPS.HR_TRANSACTION_SS is a server-side PL/SQL package within the Oracle E-Business Suite HRMS (Human Resources Management System) technology stack. It operates as part of the Oracle HRMS Transaction framework, the infrastructure that governs self-service and professional forms-based transactions such as new hires, employee changes, terminations, and other datetracked person updates. The package encapsulates the server-side logic that validates, persists, and submits these transactions, including the management of approval workflows routed through Oracle Workflow.

The _SS suffix indicates a "Self Service" orientation, and the package declares AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user rather than its owner. It was last modified at version 120.1.12010000.2 in 2010 and is present across both EBS 12.1.1 and 12.2.2. It is referenced by 59 other packages, confirming it is a foundational component of the transaction-processing layer rather than an isolated utility.

Key Procedures and Functions

The package exposes 28 documented procedures and functions, structured around the lifecycle of an HRMS transaction and its associated workflow approval. The principal routines include:

• START_TRANSACTION — Begins a new transaction session, establishing the transaction context for subsequent operations.
• VALIDATE_TRANSACTION — Executes the datetrack and business-rule validation required before a transaction can be saved or submitted.
• SAVE_TRANSACTION_STEP — Persists individual transaction steps, using the transaction_table record type that carries parameter name, value, original value, and data type.
• COMMIT_TRANSACTION — Finalizes and writes a transaction to the base tables.
• COMMIT_APPROVAL_TRANSACTION — The routine most directly associated with the search term commit_approval_transaction. It commits a transaction that has completed or is entering the approval stage, coordinating the persistence of approval-related state alongside the transaction data.
• PROCESS_WEB_API_CALL — Supports the web/self-service entry point for transaction processing.
• RETRY_TRANSACTION and ROLLBACK_TRANSACTION — Provide error-recovery paths for failed or abandoned transactions.
• SET_SUBMIT_FOR_APPROVAL, SET_INITIAL_SAVE_FOR_LATER, SET_DELETE_SAVE_FOR_LATER, SET_SAVE_FOR_LATER, SET_SAVE_FOR_LATER_STATUS, and SET_RETURN_FOR_CORRECTION — Manage transaction disposition flags and status transitions.
• GET_TRANSACTION_ID, GET_WF_EFFECTIVE_DATE, GET_ACTIVITY_TRANS_STEP_ID, and CHECK_TXN_STEP_EXISTS — Retrieval functions for transaction, workflow, and step identifiers.
• DELETE_TRN_STEP_BY_ACT_NAME and DELETE_TRANSACTION_STEPS — Remove transaction step rows when activity is cancelled or superseded.

Tables Accessed

The package reads and writes several HRMS and Workflow tables through APPS synonyms:

• HR_API_TRANSACTIONS and HR_API_TRANSACTION_STEPS — The core transaction header and step repository.
• HR_API_TRANSACTION_VALUES — Stores the individual field values associated with each transaction step.
• WF_ITEMS and WF_ITEM_ATTRIBUTE_VALUES — Oracle Workflow tables used to track approval item status and attribute data.
• PER_APPRAISALS — Referenced in appraisal-related transaction flows.
• FND_USER and FND_FORM_FUNCTIONS — Used for user context and form/function identification.
• DBMS_SQL and PLITBLM — Dynamic SQL and PL/SQL table utilities supporting the package's bulk-fetch and dynamic processing logic.

Usage Notes

HR_TRANSACTION_SS is not typically called directly by end users. It is invoked by HRMS self-service forms and professional forms during save, submit-for-approval, and approval-completion actions, and by concurrent processes that reconcile or retry transactions. Custom code integrating with the HRMS transaction framework may call these APIs to create, save, and submit person or assignment changes, but should do so through the documented wrapper procedures rather than manipulating the underlying API tables directly. When troubleshooting COMMIT_APPROVAL_TRANSACTION issues, verify workflow item creation, attribute value population, and the value of the effective date returned by GET_WF_EFFECTIVE_DATE, as approval routing depends on these elements.