Results for “propagate_role”

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

Overview

HZ_WF_SYNCH is a PL/SQL synchronization package in the Oracle E-Business Suite Applications (APPS) schema that bridges Oracle Trading Community Architecture (TCA) party data with the Oracle Workflow directory services schema. Its principal business function is to propagate user, person, contact, and group information maintained in the TCA model (HZ_PARTIES, HZ_RELATIONSHIPS, HZ_ORG_CONTACTS and related entities) into the Oracle Workflow local roles tables (WF_LOCAL_ROLES and WF_LOCAL_USER_ROLES) so that the Workflow notification engine can resolve roles, route notifications, and apply per-role preferences such as language, territory, e-mail address, fax, and status.

The package is classified as "OTHER" under the ETRM API classification scheme and carries the source header identifier ARHWFSNS.pls. The most recent documented revision in the source excerpt is version 120.5, dated 2005/10/06. As a foundational integration point between TCA and Workflow, it is a required dependency for any EBS module that relies on workflow-driven approvals, notifications, or role-based routing tied to customer, supplier, or employee party records.

Key Procedures and Functions

• PROPAGATE_USER_ROLE — The sole documented function. It propagates user information into the Workflow tables and returns a VARCHAR2 result. It is implemented as an event subscription handler, accepting a subscription GUID and a Workflow event payload (WF_EVENT_T), which aligns it with the Oracle Workflow Business Event System subscription model.
• PROPAGATE_ROLE — A companion propagation routine, documented with the same purpose statement: propagating user information to the Workflow tables. It is also annotated as an event subscription handler.
• SYNCHGROUPWFUSERROLE — Synchronizes a group entity with its corresponding Workflow user role representation.
• SYNCHPERSONWFROLE — Synchronizes a person party record with the corresponding Workflow role entry.
• SYNCHCONTACTWFROLE — Synchronizes a contact (organization contact) record with the associated Workflow role.
• SYNCHGROUPWFROLE — Synchronizes a group with its Workflow role definition.

The naming convention of the SYNCH* procedures indicates that each targets a distinct TCA entity type (person, contact, group) and performs the role-creation or role-update step against the Workflow directory. The two PROPAGATE* routines provide the event-driven entry points. Parameter lists are not fully documented in the excerpt and are therefore not reproduced here.

Tables Accessed

• HZ_PARTIES — The master TCA party record; source of person and organization identity attributes.
• HZ_RELATIONSHIPS — Defines party-to-party relationships used to resolve group membership and role hierarchy.
• HZ_ORG_CONTACTS — Organization contact assignments that drive contact-level role synchronization.
• HZ_CONTACT_POINTS — Contact point data (e-mail, fax, phone) copied into the Workflow role notification attributes.
• HZ_PERSON_LANGUAGE — Language preference used to populate the Workflow role LANGUAGE attribute.
• WF_LOCAL_ROLES and WF_LOCAL_USER_ROLES — Target Workflow directory tables that receive display name, description, notification preference, language, territory, e-mail, fax, status, start date, expiration date, and originating system identifier.
• WF_EVENT_T and WF_PARAMETER_LIST_T — Event payload and parameter structures consumed by the propagation handlers.
• FND_LANGUAGES — Validates or translates language codes.
• PLITBLM — The PL/SQL integer-indexed table type used for bulk synchronization operations.

Usage Notes

HZ_WF_SYNCH is not typically called directly from a form. Its documented role as an event subscription handler indicates that it is invoked by the Oracle Workflow Business Event System when a TCA-related business event is raised, most commonly via subscriptions configured against party, contact, or group events. The package is referenced by one other documented package, confirming its position as an infrastructure dependency rather than a user-facing API.

Customizations should not modify the package; extensions requiring additional synchronization attributes should use supported subscription mechanisms or wrap the public functions within a custom subscription. Because the package writes directly to WF_LOCAL_ROLES and WF_LOCAL_USER_ROLES, any manual changes to those tables may be overwritten on the next synchronization cycle. The package applies to both EBS 12.1.1 and 12.2.2, and its behavior depends on TCA data quality—particularly the presence of valid contact points, person language records, and active relationships.