Search Results create_hr_transaction

Overview

APPS.HR_APPRAISAL_WORKFLOW_SS is the server-side PL/SQL package that implements the workflow engine logic for the Oracle EBS Performance Management (appraisal) process. It functions as the procedural backbone of the appraisal workflow item type, supplying the functions called by Workflow Builder activity nodes at runtime. When an appraisal is initiated, routed for approval, or progressed through its lifecycle, the Oracle Workflow engine invokes procedures in this package to create the underlying HR transaction, identify and notify the correct participant (appraisee, appraiser, or reviewer), evaluate branching conditions, and commit or block workflow progress.

The package is classified under Oracle Application Object Library with an API classification of OTHER, reflecting its role as an internal workflow callback library rather than a public, documented business API. It is referenced by three other packages, indicating it sits within a broader appraisal processing framework rather than being an isolated component. The "_SS" suffix is consistent with Oracle's naming for server-side ("system") helper packages whose entry points are designed to match the standard Oracle Workflow function signature of item type, item key, activity ID, function mode, and a result returned through an OUT parameter.

Key Procedures and Functions

• CREATE_HR_TRANSACTION / COMMIT_TRANSACTION — Create and finalize the HR API transaction that persists appraisal-related data changes driven by the workflow.
• START_TRANSACTION — Initializes transaction processing when the workflow begins.
• RESET_MAIN_APPRAISER / RESET_APPR_NTF_STATUS — Reassign the primary appraiser and reset notification status flags so that re-notification or re-routing can occur.
• NOTIFY / NOTIFY_APPRAISEE_OR_APPRAISER / NOTIFY_APPRAISEE_ON_COMPLETION — Generate workflow notifications to the appropriate parties, including completion notices.
• FIND_NEXT_PARTICIPANT / BRANCH_ON_PARTICIPANT_TYPE — Determine the next participant in the appraisal chain and drive conditional branching based on participant type.
• BLOCK / PARTICIPANTS_BLOCK / APPRAISEE_OR_APPRAISER_BLOCK / APPROVALS_BLOCK — Evaluate blocking conditions that gate workflow progression, including participant-level and approval-level checks. APPROVALS_BLOCK is the procedure matched by the user's "approvals_block" search.
• GETAPPROVALBLOCKID — Retrieve the approval block identifier used to associate a blocked approval with its driving workflow context.
• BUILD_LINK — Construct the notification or navigation link embedded in workflow messages.
• SET_APPRAISAL_RFC_STATUS / SET_APPRAISAL_REJECT_STATUS — Update appraisal status for "ready for completion" and rejection outcomes.
• BUILD_MA_COMPL_LOG_MSG — Build the log message recorded when the main appraiser completes the appraisal.
• APPRAISEE_FEEDBACK_ALLOWED — Determine whether appraisee feedback is permitted at the current workflow stage.

Tables Accessed

The package operates against core Workflow and HR appraisal tables through APPS synonyms. WF_NOTIFICATIONS, WF_ITEMS, WF_ITEM_ACTIVITY_STATUSES, WF_ITEM_ATTRIBUTES, and WF_ITEM_ATTRIBUTE_VALUES are read and written to create notifications, track activity status, and store workflow item attribute values. HR_API_TRANSACTIONS holds the pending HR API transaction created and committed by CREATE_HR_TRANSACTION and COMMIT_TRANSACTION. PER_APPRAISALS and PER_PARTICIPANTS store appraisal records and the participants (appraisee, appraiser, reviewers) whose routing and notification the package manages. DUAL is used for simple expression evaluation.

Usage Notes

HR_APPRAISAL_WORKFLOW_SS is not intended to be called directly by end users or custom applications. It is invoked by the Oracle Workflow engine as the PL/SQL callback for activity nodes in the appraisal workflow item type; the item type, item key, activity ID, and function mode are passed by Workflow, and the procedure returns its result through the OUT parameter to direct subsequent branching. Typical invocation occurs when a manager submits or approves an appraisal from the Performance Management self-service pages, when notifications are generated for participants, and when approval blocking conditions must be evaluated. Customizations should avoid modifying the package body; instead, extensions should be implemented through workflow item type configuration or by wrapping documented business APIs. Because it accesses sensitive appraisal data, privileges to execute the package are restricted to the APPS schema and the workflow runtime.