Setting Up Workflow Directory Synchronization

As Oracle Trading Community Architecture (TCA) is a source of Oracle Workflow user and role information, the information stored in the TCA tables must be synchronized with the denormalized information in the Workflow local tables. TCA stores information regarding people in the Workflow Directory Services (WFDS) from the TCA data model. The data is kept in synchronization with the actual TCA tables using the Business Event system and internal functionality. The Workflow local synchronization APIs are used to perform this synchronization.

There are two methods of synchronization.

For more information, see: Setting Up an Oracle Workflow Directory Service.

Attribute Mapping for Workflow Roles

Workflow Directory role attributes are mapped with Oracle Trading Community Architecture (TCA) attributes in the Workflow Directory Services synchronization.

Role Mapping for Person Parties

Workflow Table: HZ_PARTY_WF_ROLES_V

Related TCA Entity Tables:

This table displays the columns in the related TCA Bulk Synchronization view (HZ_PARTY_WF_ROLES_V).

Column Person Party
Name Person Party ID (HZ_PARTY)
Display Name Person Party Name
Description Person Party Name
E-mail Address Person Party Primary E-mail Address
Notification Preference From Person Party Primary E-mail Contact Point
If there is no e-mail format mentioned for the primary e-mail address or if there is no e-mail address, the notification preference is set to Query.
Language Person Party Primary Language
Territory From Primary Language
Fax Null
Original System Ref HZ_PARTY
Original System Ref ID Person Party ID
Status Person Party Status
Start Date NULL
Expiration Date NULL
User Flag Y

Note: The Person Party Primary E-mail Address entity is denormalized onto the HZ_PARTIES from HZ_CONTACT_POINTS tables.

For Person Party Status, A is treated as ACTIVE, while any other letter is considered as INACTIVE.

Note: As the role mappings is done for person parties, a user record is simply a role record with user_flag set to Y.

Role Mapping for Contacts

Contacts are Person parties that represent other Person or Organization parties.

Workflow Table: HZ_PARTY_WF_ROLES_V

Related TCA Entity Tables:

This table displays the columns in the related TCA Bulk Synchronization view (HZ_PARTY_WF_ROLES_V).

Column Contact
Name Relationship Party ID (HZ_PARTY)
Display Name Person Party Name (Subject)
Description Relationship Party Name
E-mail Address Relationship Party Primary E-mail Address
Notification Preference From Relationship Party Primary E-mail Contact Point
If there is no e-mail format mentioned for the primary e-mail address or if there is no e-mail address, the notification preference is set to Query.
Language Subject Party Primary Language
Territory From Primary Language of Subject Party
Fax NULL
Original System Ref HZ_PARTY
Original System Ref ID Relationship Party ID
Status Relationship Party Status
Start Date Relationship Start Date
Expiration Date Relationship End Date
User Flag Y

Note: The Relationship Party Primary E-mail Address entity is denormalized onto the HZ_PARTIES from HZ_CONTACT_POINTS tables.

For Relationship Party Status, A is treated as ACTIVE, while any other letter is considered as INACTIVE.

Note: As the role mappings is done for contacts, a user record is simply a role record with user_flag set to Y.

Role Mapping for Group Parties

Workflow Table: HZ_GROUP_WF_ROLES_V

Related TCA Entity Tables:

This table displays the columns in the related TCA Bulk Synchronization view (HZ_GROUP_WF_ROLES_V).

Column Group Party
Name Group Party ID (HZ_GROUP)
Display Name Group Party Name
Description Group Party Mission Statement
E-mail Address Group Party Primary E-mail Address
Notification Preference From Group Party Primary E-mail Contact Point
If there is no e-mail format mentioned for the primary e-mail address or if there is no e-mail address, the notification preference is set to Query.
Language Group Party Primary Language
Territory From Primary Language
Fax NULL
Original System Ref HZ_PARTY
Original System Ref ID Group Party ID
Status Group Party Status
Start Date NULL
Expiration Date NULL
User Flag N

Note: The Group Party Primary E-mail Address entity is denormalized onto the HZ_PARTIES from HZ_CONTACT_POINTS tables.

For Group Party Status, A is treated as ACTIVE, while any other letter is considered as INACTIVE.

Attribute Mapping for Workflow User Roles

The Workflow (WF) User Roles represent the mappings between Workflow Users and Workflow Roles.

For example, the various persons forming a Group party represent the User Roles for that Group party. Each user in the role receives a separate copy of the notification when Expand Roles is checked on a Workflow Notification.

Note: Workflow Users participate in their own roles. The WF_USER_ROLES table has a record for TCA Person Parties, since they are created with the User Flag set to Y.

User Role Mapping for Group Parties

Related TCA Entity Tables:

This table displays the columns in the related TCA Bulk Synchronization view (HZ_GROUP_WF_USER_ROLES_V).

Column Person Party
User Name Person Party ID (HZ_PARTY)
User Orig System HZ_PARTY
User Orig System ID Person Party ID
Role Name Relationship Party ID (HZ_GROUP)
Role Orig System HZ_GROUP
Role Orig System ID Group's Party ID
Start Date NULL
Expiration Date NULL

Note: The subject party is a Person and the object party is a Group.

User Role Mapping for Person and Contact Parties

Related TCA Entity Tables: HZ_PARTIES

This table displays the columns in the related TCA Bulk Synchronization view (HZ_PARTY_WF_USER_ROLES_V).

Column Person Party
User Name Party ID (HZ_PARTY)
User Orig System HZ_PARTY
User Orig System ID Party ID
Role Name Party ID (HZ_PARTY)
Role Orig System HZ_PARTY
Role Orig System ID Party ID
Start Date Relationship Start Date
Expiration Date Relationship End Date