Results for “per_hrwf_synch”

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

Overview

PER_HRWF_SYNCH is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema. Its name reflects its principal purpose: synchronizing Oracle Human Resources (HR) and Oracle Workflow (WF) directory data, specifically person, assignment, position, and role information. In EBS 12.1.1 and 12.2.2, Oracle Workflow maintains its own local directory tables (WF_LOCAL_ROLES and related structures) that mirror HR data. When HR records change, the workflow directory must be refreshed so that routing, notifications, role-based approvals, and the Workflow Directory Service reflect accurate people and position data. PER_HRWF_SYNCH provides the synchronization logic that propagates HR changes into the workflow directory. It is classified as an OTHER API and is documented with eight procedures/functions. Notably, the package is not referenced by any other database object, meaning it is invoked directly by internal framework components, callbacks, or events rather than being a dependency of downstream code. Conversely, it references a substantial set of supporting packages including HR_API, HR_GENERAL, WF_DIRECTORY, WF_LOCAL_SYNCH, WF_EVENT, WF_UTIL, HR_PERSON_NAME, HR_UTILITY, and FND_DATE/FND_NUMBER utilities.

Key Procedures and Functions

The ETRM metadata documents eight procedures and functions within the package. The named units include:

• CALL_BACK — A callback routine, typically registered with a workflow synchronization process so that the package can be re-invoked or notified when synchronization steps complete or require continuation.
• CHK_DATE_STATUS — Performs date and status validation, determining whether a given HR record falls within an effective date range and carries a status eligible for synchronization.
• PER_PER_WF — Synchronizes person-level data between the HR person records and the Workflow directory.
• PER_ASG_WF — Synchronizes assignment-level data, pushing assignment information into the workflow directory.
• PER_PDS_WF — Synchronizes period-of-service data into the workflow directory context.
• SYCH_USER_POS_ROLE — Synchronizes the relationship between users, positions, and roles, aligning workflow local roles with HR position and role definitions.

The remaining documented units complement these synchronization flows. The naming convention confirms a modular design in which each HR entity (person, assignment, period of service) has a dedicated synchronization routine that ultimately feeds the Workflow Directory Service.

Tables Accessed

The package reads and manipulates data across HR and Workflow tables, referenced via APPS synonyms:

• PER_ALL_PEOPLE_F, PER_PER_SHD — Source of current and history person records used to derive directory entries.
• PER_ALL_ASSIGNMENTS_F — Provides assignment details that map people to organizations, positions, and roles.
• PER_PERIODS_OF_SERVICE — Supplies period-of-service data relevant to person status.
• PER_ALL_POSITIONS, PER_PERSON_TYPES, PER_ROLE_ROLES_V — Position definitions, person type classifications, and role-role relationships used to build role hierarchies.
• WF_LOCAL_ROLES, WF_DIRECTORY — The workflow directory target tables that are populated and refreshed.
• FND_USER — Links HR persons to application user accounts during role synchronization.
• WF_PARAMETER_LIST_T, PLITBLM — Workflow parameter and PL/SQL table utility structures used to pass data between routines.

Usage Notes

PER_HRWF_SYNCH is an internal framework package rather than an end-user API. It is most commonly triggered indirectly through Oracle Workflow background processes, HR workflow event subscriptions (WF_EVENT), and directory synchronization mechanisms that rely on WF_LOCAL_SYNCH. It may execute from a concurrent program or be invoked programmatically by HR business events that signal changes to people, assignments, or positions. Because it is not referenced by other database objects, customizations should not assume it is called by external code; instead, it is best treated as a supporting synchronization engine. When troubleshooting workflow directory discrepancies — such as missing users, stale roles, or incorrect approver routing — this package is a relevant diagnostic target. Custom code should avoid direct modification of synchronized WF_LOCAL_ROLES records and instead rely on the standard HR and Workflow synchronization flows that PER_HRWF_SYNCH implements.