Setting Up Full Table Synchronization Messages

Full synchronization (fullsync) is a much more data-destructive activity than incremental synchronization. Incremental synchronization messages modify, delete, or add only the data that a user has affected in performing an individual transaction. Full synchronization messages first delete all of the data in the target record and then load a copy of the source record.

When using full synchronization messages, your primary concern is that you not inadvertently overwrite valid data. To prevent this from occurring, you generally should not activate full synchronization messages for any record that receives input from multiple databases.

The messages in the following table are full synchronization messages. Carefully consider the effect of activating any of these messages.

WARNING:

You should not activate any of the messages identified as FULL_SYNC or FULLSYNC unless you are absolutely certain that you want to overwrite all of the data in the records associated with the message in the database. Understanding how full synchronization messages work is especially important if the list of values in the PeopleSoft Pay/Bill Management database differ from the values in the HCM database. For example, synchronizing the locations from PeopleSoft HCM using a FULLSYNC message would overwrite all of the Financials locations with the PeopleSoft HCM locations.

The following tables contain fullsync messages that update the PeopleSoft Pay/Bill Management, PeopleSoft HCM, and Financials applications. The messages are broken out by the type of table affected, Set Up or Transactional, and the direction that the message normally flows.

Set Up Tables – HR to FIN

Service Operation Queue Name

BEN_DEFN_PGM_FULLSYNC

FO_SYNC

BUS_UNIT_HR_FULLSYNC

HR_SETUP

CM_TYPE_FULLSYNC

PERSON_SETUP

COMPANY_FULLSYNC

PERSON_SETUP

COMPETENCY_FULLSYNC1

PERSON_SETUP

COMPETENCY_FULLSYNC2

COMPETENCY

COMPETENCY_FULLSYNC3

COMPETENCY

DEPT_FULLSYNC

ENTERPRISE_SETUP

FO_COMP_RATECD_FULLSYNC

FO_SYNC

FO_EMPL_CTG_FULLSYNC

FO_SYNC

FO_GP_PYGRP_FULLSYNC

FO_SYNC

NID_TYPE_FULLSYNC

PERSON_SETUP

FO_WC_CO_MOD_FULLSYNC

FO_SETUP

FO_WC_CO_STATE_FULLSYNC

FO_SETUP

FO_WC_STATE_FULLSYNC

FO_SETUP

FREQUENCY_FULLSYNC

PERSON_SETUP

JOBCODE_FULLSYNC

PERSON_SETUP

LOCATION_FULLSYNC

ENTERPRISE_SETUP

PAYGROUP_FULLSYNC

PAYGROUP_SETUP

RATING_MODEL_FULLSYNC

RATING_MODEL

REGULATORY_REGION_FULLSYNC

PERSON_SETUP

SCHOOL_FULLSYNC

PERSON_SETUP

SCHOOL_TYPE_FULLSYNC

PERSON_SETUP

STATE_FULLSYNC

ENTERPRISE_SETUP

TAX_LOCATION1_FULLSYNC

FO_SYNC

TIME_REPORTING_CODE_FULLSYNC

TIME_AND_LABOR_SETUP

TL_TASKGRP_TBL_FULLSYNC

FO_SYNC

TL_WRKGRP_TBL_FULLSYNC

FO_SYNC

FO_CO_LOCALTAX_FULLSYNC

FO_SYNC

FO_CO_STATETAX_FULLSYNC

FO_SYNC

FO_JOBCODE_PRD_FULLSYNC

FO_SYNC

Set Up Tables – FIN to HR

Message Message Channel

ACCOUNT_CHARTFIELD_FULLSYNC

GL_SETUP

FO_RATE_ELEM_FULLSYNC

FO_SETUP

FO_MC_TYPE_SYNC

FO_SETUP

FO_MC_TYPE_FULLSYNC

FO_SETUP

Set Up Tables – Either Way

Service Operation Queue Name

COUNTRY_FULLSYNC

ENTERPRISE_SETUP

CURR_QUOTE_MTHD_FULLSYNC

MARKET_RATES

CURRENCY_FULLSYNC

ENTERPRISE_SETUP

MARKET_RATE_FULLSYNC

MARKET_RATE_LOAD

MARKET_RATE_INDEX_FULLSYNC

MARKET_RATES

MARKET_RATE_TYPE_FULLSYNC

MARKET_RATES

Once the integrated databases are set up and running with the correct sync messages activated, you should not need to run the following fullsync messages.

Transactional Tables – HCM to FIN

Service Operation Queue Name

FO_EMPL_DATA_FULLSYNC

FO_SYNC

PERSON_ACCOMP_FULLSYNC

PERSON_DATA

PERSON_BASIC_FULLSYNC

PERSON_DATA

PERSON_COMPETENCY_FULLSYNC

PERSON_DATA

WORKFORCE_FULLSYNC

PERSON_DATA

Transactional Tables – FIN to HCM

Message Message Channel

CUSTOMER_FULLSYNC

CUSTOMER

PROJECT_ACTIVITY_FULLSYNC

PROJECTS_SETUP

PROJECT_ACTIVITY_TEAM_FULLSYNC

PROJECTS_SETUP

PROJECT_FULLSYNC

PROJECTS_SETUP

PROJECT_TEAM_FULLSYNC

PROJECTS_SETUP