Results for “sych_user_pos_role”

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

Overview

APPS.PER_HRWF_SYNCH is an internal Oracle E-Business Suite database package that synchronizes Oracle Human Resources (HR) entity data with the Oracle Workflow directory service. Its primary role is to propagate user and role information changes originating in HR — such as person, assignment, position, and period-of-service updates — into the Workflow local tables used to resolve notification recipients and role memberships.

The package header (perhrwfs.pkh, version 120.0.12020000.3, dated 2013/05/10) declares the package with AUTHID CURRENT_USER, an explicit signal that it executes under the privileges of the invoking user and is intended strictly for internal, framework-level use. The source comments classify its access status as "Internal Table Handler Use Only", confirming that it is not a public integration API. Rather than enforcing business rules of its own, PER_HRWF_SYNCH acts as an orchestration layer that receives parameter lists from Workflow and delegates the substantive synchronization work to WF_LOCAL_SYNCH, the Workflow directory synchronization package.

The package is referenced by twelve other packages within the EBS schema, reflecting its position as a shared, low-level dependency in the HR-to-Workflow propagation chain.

Key Procedures and Functions

• CALL_BACK — A callable routine registered with WF_EVENT. Workflow's WF_EVENT.call_me_later mechanism defers invocation until the effective start date of a future-dated transaction equals SYSDATE. When invoked, CALL_BACK inspects the parameter list and routes processing to WF_LOCAL_SYNCH.propagate_user or WF_LOCAL_SYNCH.propagate_user_role as appropriate. It has no specific internal error handling; failures are surfaced to the caller.
• CHK_DATE_STATUS — A function that evaluates supplied dates relative to SYSDATE and returns a status classification of CURRENT, FUTURE, or PAST. This supports the deferred-callback logic by determining whether an event is eligible for immediate propagation.
• PER_PER_WF — Handles synchronization triggered by person-level HR changes, mapping person records into the corresponding Workflow user or role entries.
• PER_ASG_WF — Handles synchronization for assignment-level changes, propagating assignment-derived role or membership data into Workflow.
• PER_PDS_WF — Handles synchronization associated with periods of service, ensuring Workflow reflects service-related status changes relevant to user or role validity.
• SYCH_USER_POS_ROLE — Synchronizes the relationship between users, positions, and roles, keeping Workflow role membership consistent with the current HR position structure.

Tables Accessed

Table access is performed through APPS synonyms and spans both HR and Workflow schemas:

• PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, PER_PERIODS_OF_SERVICE, PER_ALL_POSITIONS, and PER_PERSON_TYPES — the HR datetracked sources of person, assignment, service, position, and person-type attributes that determine Workflow user and role state.
• FND_USER — links HR persons to application user accounts for directory propagation.
• WF_LOCAL_ROLES — the Workflow local directory table into which user and role memberships are written or refreshed.
• WF_PARAMETER_LIST_T and PLITBLM — the Workflow parameter list type and the PL/SQL index-by table used to carry event parameters between Workflow and this package.

Usage Notes

PER_HRWF_SYNCH is invoked indirectly. HR forms and the person/assignment datetrack framework raise Workflow business events; WF_EVENT then schedules or immediately calls CALL_BACK, which in turn delegates to WF_LOCAL_SYNCH. The package is also called by other packages (twelve documented referrers) during date-tracked HR transactions and concurrent synchronization processing.

Because the access status is internal table handler use only, customizations should not call these routines directly. Integrations requiring Workflow directory updates should use the supported Workflow directory service APIs (WF_LOCAL_SYNCH) or HR public APIs instead, allowing PER_HRWF_SYNCH to remain an internal implementation detail.