Full Table Synchronization Messages
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