Results for “create_hr_directory_services”

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

Overview

APPS.HR_WORKFLOW_SERVICE is a PL/SQL package body in the Oracle E-Business Suite Oracle HRMS (Human Resources) product family that provides a service layer between Oracle HRMS business entities and the Oracle Workflow engine. Its purpose is to create, interrogate, and manipulate Workflow process instances and activity attributes on behalf of HRMS functionality such as HR self-service, iRecruitment, and the HR API transaction framework. The package encapsulates common Workflow coding patterns — attribute existence checks, activity type validation, web page and window title resolution, and process lifecycle operations — so that other HRMS modules do not manipulate the Workflow schema directly.

The source header indicates the shipped file is hrwfserv.pkb, version 120.10.12020000.2, last revised in July 2012, consistent with the 12.1.1 and 12.2.2 release lines. The package is classified as OTHER in the E-TRM repository, meaning it is a supporting utility package rather than a formal public API, and it is referenced by eight other packages in the applications schema.

Key Procedures and Functions

The package body contains 25 documented procedures and functions. They fall into several functional groupings.

• Activity attribute handling — GET_ITEM_ATTR_EXPANDED_INFO, GET_ACT_ATTR_EXPANDED_INFO, and CHECK_ACTIVITY_TYPE_ATTRS retrieve expanded attribute information for workflow items and activities and validate that attributes are valid for a given activity type. These are the functions most directly relevant to searches on activity_attribute, because they resolve WF_ACTIVITY_ATTRIBUTES and WF_ACTIVITY_ATTR_VALUES content for a running process.
• Web page and window configuration — HR_WEB_PAGE, CHECK_WEB_PAGE_CODE, GET_WEB_PAGE_CODE, CHECK_HR_WINDOW_TITLE, and GET_HR_WINDOW_TITLE validate and return the OAF/Forms web page codes and window titles used when a Workflow notification routes the user into an HRMS page.
• Activity re-entry control — CHECK_ACTIVITY_REENTRY and GET_ACTIVITY_REENTRY_VALUE determine whether an activity may be re-entered and return the configured re-entry value.
• Process lifecycle — CREATE_PROCESS, CONTINUE_PROCESS, and TRANSITION_ACTIVITY create a Workflow process instance, advance it, and transition it to a new activity.
• Process and item maintenance — CHECK_ACTIVE_WF_ITEMS, GET_ACTIVE_WF_ITEMS, REMOVE_DEFUNCT_PROCESS, and START_CLEANUP_PROCESS identify and purge obsolete or defunct process instances; BLOCK is a utility used to suspend processing.
• HR directory and user checks — CREATE_HR_DIRECTORY_SERVICES and CHECK_USERNM_EXISTS_SUBJ_APRV support HR directory services and subject-approval user name validation.

Tables Accessed

The package reads and writes a defined set of HRMS and Workflow tables through APPS synonyms. On the Workflow side it uses WF_ITEMS, WF_ITEM_ATTRIBUTES, WF_ITEM_ATTRIBUTE_VALUES, WF_ACTIVITY_ATTRIBUTES, WF_ACTIVITY_ATTR_VALUES, and WF_PROCESS_ACTIVITIES to locate item and activity attributes and to drive process navigation. The private helper function ITEM_ATTRIBUTE_EXISTS, for example, queries WF_ITEM_ATTRIBUTE_VALUES by item type, item key, and attribute name. HRMS tables include PER_ALL_PEOPLE_F, PER_ADDRESSES, PER_APPRAISALS, and IRC_OFFERS, which supply the person, address, appraisal, and offer context attached to a workflow item. Transactional and session data come from HR_API_TRANSACTIONS, HR_API_TRANSACTION_STEPS, HR_API_TRANSACTION_VALUES, HR_WORKFLOW_ITEM_KEY_S, and ICX_SESSIONS.

Usage Notes

HR_WORKFLOW_SERVICE is invoked indirectly rather than by end users. HRMS forms, OAF pages, and concurrent programs call it when they need to start or advance a workflow, resolve an activity attribute for a notification, or validate the web page code bound to an activity. The HR API transaction framework relies on it when transaction steps are converted into workflow items. Customizations that extend HRMS workflows should call the documented procedures rather than querying the Workflow tables directly, since the package centralizes the attribute-existence and activity-validity logic that the Workflow engine depends on. Because it is an OTHER-classified package, its signatures are not guaranteed as a public API across releases and should be reviewed before upgrade from 12.1.1 to 12.2.2.