Application Message Subscriptions that Integrate with PeopleSoft HCM

When you use PeopleSoft HCM as the employee source database, PeopleSoft HCM uses application messages to send selected data to PeopleSoft Resource Management data tables, which are used to populate resource profiles. PeopleSoft Resource Management depends on the accuracy and timeliness of the information that is stored in the resource profiles. Because PeopleSoft HCM data is subject to continuous change, application messages provide the vehicle to keep the data current across the enterprise.

This section discusses:

  • Shared data between PeopleSoft HCM and Resource Management.

  • Incremental synchronization messages.

  • Full table synchronization messages.

For the integration between PeopleSoft HCM and PeopleSoft Resource Management, HCM is the publisher of changes to data, and Resource Management is the subscriber. This diagram illustrates the data-sharing process:

This diagram illustrates the data-sharing process:

 Sharing data between PeopleSoft HRMS and PeopleSoft Resource Management

To use PeopleSoft application messages, you must activate the Publication and Subscription services on the PeopleSoft Resource Management and PeopleSoft HCM application servers.

If you integrate PeopleSoft Resource Management with PeopleSoft HCM, you must also activate the data synchronization application messages.

If you use PeopleSoft Resource Management without an integrated HCM, the data synchronization application messages should not be activated.

PeopleSoft Resource Management utilizes application messages to integrate PeopleSoft Resource Management tables with PeopleSoft HCM application tables. The messages are delivered with a default status of inactive. You must activate each message before attempting to publish messages or subscribe to messages between databases.

The direction of the publish and subscribe rule for each message may be bidirectional or unidirectional. The publish and subscribe rule may also be incremental or full table synchronization for each message.

Bidirectional, Incremental Messages—General Data Synchronization

When you use PeopleSoft HCM with PeopleSoft Resource Management, you install two databases, HCM and Financials, and synchronize fundamental, general data records across the two databases. If you update the records in both databases and then make a change in PeopleSoft Resource Management, the change is published back to PeopleSoft HCM, and vice versa. This type of data synchronization is called bidirectional incremental messaging.

The following list shows the bidirectional, incremental synchronization messages to activate in the HCM and Financials databases. You must activate and execute the messages in this list.

Note: Oracle recommends that you do not implement the messages as bidirectional. If you set up the incremental messages as bidirectional, you may have data validation issues if you update the same record in each database at the same time. It is better to set up one database as the master so that all updates can occur in one place. The messages can then be set up as unidirectional and published to the subscribing database:

  • DEPT_SYNC

  • LOCATION_SYNC

Unidirectional, Incremental Messages - PeopleSoft Resource Management-Specific Synchronization

The following list contains the incremental synchronization messages that update the PeopleSoft Resource Management application every time a user changes PeopleSoft HCM data that is relevant to Resource Management. These messages are published from PeopleSoft HCM to PeopleSoft Resource Management, which means that HCM is always the source of data. Do not modify data in the Financials database that is transmitted through these messages from PeopleSoft HCM.

Once you activate these messages in PeopleSoft HCM and PeopleSoft Resource Management, every subsequent change to HCM data in any of the records that are associated with these messages triggers the publication and subscription of the new, modified, or deleted data. The result is that PeopleSoft Resource Management reflects the change within a few seconds.

This is a list of the unidirectional, incremental synchronization messages that you must activate in the HCM and Financials databases:

  • BUS_UNIT_HR_SYNC

  • CLUSTER_ACCOMP_SYNC

  • CLUSTER_COMP_SYNC

  • CM_TYPE_SYNC

  • COMPETENCY_SYNC1

  • COMPETENCY_SYNC2

  • COMPETENCY_SYNC3

  • FREQUENCY_SYNC

  • HOLIDAY_DATE_SYNC

  • JOBCODE_SYNC

  • JOB_FAMILY_SYNC

  • PERSON_ACCOMP_SYNC

  • PERSON_COMPETENCY_SYNC

  • PERSON_BASIC_SYNC

  • PERSON_VISA_CITIZEN_SYNC

  • RATING_MODEL_SYNC

  • ROLE_ACCOMP_SYNC

  • ROLE_CLUSTER_SYNC

  • ROLE_COMP_SYNC

  • ROLE_SYNC

  • SCHOOL_SYNC

  • WORKFORCE_SYNC

Full synchronization is a much more data-destructive activity than incremental synchronization. Incremental synchronization messages modify, delete, or add only the data that changed as a result of an individual transaction. Full synchronization messages first delete all of the data that is in the target record in PeopleSoft Resource Management and then load a copy of the source record from PeopleSoft HCM.

Note: There is an exception to the above statement. If you select the installation option to maintain non-employees in HCM and Financials databases, the full synchronization process does not update non-employee data for employee IDs that originate in PeopleSoft Resource Management. In this case the process only updates employee and non-employee data that originates in PeopleSoft HCM.

An understanding of how full synchronization messages work is especially important if the list of departments or locations in the Financials database is different from the one that is in the HCM database. Synchronizing departments by using a FULLSYNC message from PeopleSoft HCM to PeopleSoft Resource Management overwrites all of the Resource Management departments with the PeopleSoft HCM departments. Such an action would damage the Financials database and require that the Departments table (DEPT_TBL) be restored from a backup that you made prior to the full synchronization.

Warning! Oracle recommends that you only use full synchronization messages during implementation. If there is existing data in the Financials database records and you use full synchronization messages, you will overwrite PeopleSoft Resource Management data that is associated with the message. Also, it is recommended that you only implement full synchronization messages as unidirectional with one database as a publisher and another as a subscriber.

For example, users can add or change values in the Departments table and Location table (LOCATION_TBL) from a page in the Financials database as well as the HCM database, but full synchronization messages copy data from PeopleSoft HCM to PeopleSoft Resource Management only. Therefore, any changes that a user makes directly in PeopleSoft Resource Management are eliminated when a full synchronization message is published from PeopleSoft HCM and subscribed to by Resource Management.

Full table synchronization messages are delivered with a status of inactive. The publishing rules must be activated. Information that is to be shared by the Financials and HCM databases is updated properly when the appropriate messages are activated.

Warning! PeopleSoft recommends that you do not activate full synchronization messages for any record that receives input from more than one database. Carefully consider the impact of activating any of these messages. If you activate a message that is appended with FULL_SYNC, FULLSYNC, or FULLSYNCn, you overwrite all of the data in the Financials database tables that is associated with the message, other than non-employee data that originates in PeopleSoft Resource Management.

Unidirectional, Full Synchronization Messages

The following list contains the unidirectional, full synchronization messages that you must activate in the HCM and Financials databases. When activated and executed, these messages overwrite all of the data that is associated with them in the Financials database with the data in the HCM database. Exceptions are preceded by an asterisk (*), which indicates that if you maintain non-employees in PeopleSoft Resource Management, the PeopleSoft HCM data does not overwrite the Resource Management data for non-employees that originates in Resource Management:

  • BUS_UNIT_HR_FULLSYNC

  • CLUSTER_ACCOMP_FULLSYNC

  • CLUSTER_COMP_FULLSYNC

  • CM_TYPE_FULLSYNC

  • COMPETENCY_FULLSYNC1

  • COMPETENCY_FULLSYNC2

  • COMPETENCY_FULLSYNC3

  • FREQUENCY_FULLSYNC

  • HOLIDAY_DATE_FULLSYNC

  • JOBCODE_FULLSYNC

  • JOB_FAMILY_FULLSYNC

  • * PERSON_ACCOMP_FULLSYNC

  • * PERSON_BASIC_FULLSYNC

  • * PERSON_COMPETENCY_FULLSYNC

  • * PERSON_VISA_CITIZEN_FULLSYNC1

  • RATING_MODEL_FULLSYNC

  • ROLE_ACCOMP_FULLSYNC

  • ROLE_CLUSTER_FULLSYNC

  • ROLE_COMP_FULLSYNC

  • ROLE_FULLSYNC

  • SCHOOL_FULLSYNC

  • * WORKFORCE_FULLSYNC

A Caution Regarding Bidirectional, Full Synchronization Enterprise Messages

You must also activate and execute the messages that are in the following table, but it is recommended that you do not implement the messages as bidirectional. The full synchronization messages that you implement in PeopleSoft Resource Management should be unidirectional because you only set up one database as a publisher and the other as a subscriber. If you set up full synchronization messages as bidirectional, you may overwrite unique values that are entered in each database and should not be synchronized:

  • DEPT_FULLSYNC

  • LOCATION_FULLSYNC