Search Results chk_process_name

Overview

APPS.HR_TASKFLOW_WORKFLOW is a PL/SQL package in Oracle E-Business Suite that supports the Oracle HRMS Taskflow infrastructure, internally referred to as "HR Taskflow." The package bridges Oracle Human Resources navigation configuration data with Oracle Workflow (WF) process definitions. Its principal business function is to migrate, or "transfer," HR self-service and navigation taskflow definitions into the Workflow runtime engine so that they can be executed as standard Workflow processes.

The package is declared with AUTHID CURRENT_USER, meaning its unqualified object references resolve according to the privileges of the calling schema rather than the APPS schema owner. The header comment identifier hrtskwkf.pkh places this code within the HR Taskflow family of packages. It is classified under the ETRM API classification "OTHER," indicating it is an internal infrastructure component rather than a published, supported public API.

The package is relevant to the "transfer_workflow" search because that procedure is the principal documented entry point for converting HR navigation taskflows into Workflow-processable definitions.

Key Procedures and Functions

• TRANSFER_WORKFLOW — The central procedure. It transfers a taskflow definition identified by process item type and root process name so that the process is available to the Workflow engine. Parameters allow the caller to scope the transfer by business group, legislation code, and legislation subgroup, and the root process name is optional (defaulted), permitting broad transfers across a business group or legislation.
• CALL_TASKFLOW_FORM — Invokes the Taskflow form associated with a given Workflow item type, item key, and activity identifier. The funmode parameter controls the form invocation mode, and the procedure returns a result out parameter. This supports the runtime presentation of HR taskflows from within Workflow-driven navigation.
• CHK_PROCESS_NAME — A Boolean validation function that tests whether a given item type and process name combination represents a valid, recognized process. It is used to validate input before a transfer or launch attempt.
• GET_CONVERTED_PROCESSES — Returns a numeric count of processes that have already been converted or transferred, providing a status metric for the conversion state of HR taskflow processes.

Tables Accessed

The package reads and writes several families of tables through APPS synonyms. The HR_NAVIGATION_* tables — HR_NAVIGATION_NODES, HR_NAVIGATION_NODES_S, HR_NAVIGATION_NODE_USAGES, HR_NAVIGATION_NODE_USAGES_S, HR_NAVIGATION_PATHS, HR_NAVIGATION_PATHS_S, HR_NAVIGATION_PATHS_TL, HR_NAVIGATION_UNITS, and HR_NAVIGATION_UNITS_TL — hold the HR navigation structure, node usage, path, and translated unit definitions that represent the taskflow hierarchy. HR_WORKFLOWS and HR_WORKFLOWS_S store the Workflow definitions associated with HR processes. WF_ACTIVITIES and WF_ACTIVITIES_TL are the standard Oracle Workflow activity definition tables that receive the transferred process and activity metadata. PAY_CUSTOMIZED_RESTRICTIONS supplies payroll-related restriction rules that can affect which processes are eligible for transfer. FND_LANGUAGES is consulted to resolve language and translation context, supporting the _TL translated tables and the legislation-based scoping parameters of TRANSFER_WORKFLOW.

Usage Notes

HR_TASKFLOW_WORKFLOW is invoked as internal infrastructure rather than as a callable business API. The transfer_workflow procedure is typically executed during upgrade or implementation activities when HR taskflow definitions must be pushed into the Workflow engine, and it is commonly reached indirectly from HRMS forms, Taskflow form functions, or concurrent program logic rather than from end-user screens. Because the package is documented as referenced by zero other packages, it functions as a terminal consumer of navigation and Workflow metadata rather than a shared library. Developers extending HR self-service navigation in EBS 12.1.1 or 12.2.2 should treat this package as internal and unsupported for direct modification; any customization should be limited to invoking the documented procedures with appropriate item type, process name, business group, and legislation parameters. Validation via chk_process_name and status checking via get_converted_processes are the appropriate pre- and post-transfer checks.