Setting Up PeopleSoft Integration Broker Web Services Subscriptions
Oracle delivers all PeopleSoft Pay/Bill Management EIPs with settings enabled for full functionality, with the exception of PeopleSoft Integration Broker web services. When you integrate PeopleSoft Pay/Bill Management with PeopleSoft HCM, you must activate PeopleSoft Integration Broker web services.
This topic describes how to:
Set up incremental synchronization web services.
Set up full table synchronization messages.
Activate full table publish rules.
Note: Oracle recommends that you not change the delivered values for Create Message Header and Create Message Trailers. Special logic on the PeopleSoft full message subscription to delete the existing application records occurs when a header message is encountered. Some applications use the trailer message to indicate that all data messages have been received and that the validation process should be started. The documentation for the individual message should note whether headers and trailers are not supported. Please verify that the subscribing process does not need the header or trailer process before deselecting those check boxes on a Full Sync message publish.
See the product documentation for:
PeopleTools: PeopleSoft Integration Broker
PeopleTools: Integration Broker Testing Utilities and Tools
PeopleTools: PeopleSoft Integration Broker Administration
PeopleSoft Pay/Bill Management uses the PeopleSoft Integration Broker tool to integrate PeopleSoft Pay/Bill Management tables with PeopleSoft HCM and PeopleSoft Financials (FSCM) application tables. The messages are delivered with a default status of Inactive. You must activate each message before you attempt to publish messages or subscribe to messages between databases.
Note: You must activate these messages in the HCM and FSCM databases.
To begin using PeopleSoft Integration Broker, you need to enable publishing of several web services in HCM and subscribing to those services in PeopleSoft Pay/Bill Management. For some PeopleSoft systems, the direction of the publish/subscribe rule for web services may be bidirectional or unidirectional; however, in Pay/Bill Management, the model is unidirectional so that data can be synchronized. For a given set of data, only one source for add and one source for update is available. The publish and subscribe rules may also be incremental or full table synchronization for each message.
Note: The source for publishing departments must be HCM because PeopleSoft Pay/Bill Management requires that the Company and Location fields be populated.
The following tables contain the incremental synchronization web services that update the PeopleSoft Pay/Bill Management, PeopleSoft HCM, and Financials applications every time a user changes data that is relevant to PeopleSoft Pay/Bill Management. These services are published from PeopleSoft Pay/Bill Management or PeopleSoft HCM and subscribe to some or all of the same databases. These are suggested service operations.
Set Up Tables – HCM to FIN
|
Service Operation |
Queue Name |
|---|---|
|
BUS_UNIT_HR_SYNC |
HR_SETUP |
|
CM_TYPE_SYNC |
PERSON_SETUP |
|
COMPANY_SYNC |
PERSON_SETUP |
|
COMPETENCY_SYNC1 |
PERSON_SETUP |
|
COMPETENCY_SYNC2 |
COMPETENCY |
|
COMPETENCY_SYNC3 |
COMPETENCY |
|
DEPT_SYNC |
ENTERPRISE_SETUP |
|
FREQUENCY_SYNC |
PERSON_SETUP |
|
FO_WC_CO_MOD_ SYNC |
FO_SETUP |
|
FO_WC_CO_STATE_SYNC |
FO_SETUP |
|
FO_WC_STATE_ SYNC |
FO_SETUP |
|
HOLIDAY_DATE_SYNC |
PERSON_SETUP |
|
JOBCODE_ SYNC |
PERSON_SETUP |
|
LOCATION_SYNC |
ENTERPRISE_SETUP |
|
RATING_MODEL_SYNC |
RATING_MODEL |
|
NID_TYPE_SYNC |
PERSON_SETUP |
|
PAYGROUP_SYNC |
PAYGROUP_SETUP |
|
REGULATORY_REGION_SYNC |
PERSON_SETUP |
|
TIME_REPORTING_CODE_SYNC |
TIME_AND_LABOR_SETUP |
|
SCHOOL_SYNC |
PERSON_SETUP |
Set Up Tables – FIN to HCM
|
Service Operation |
Queue Name |
|---|---|
|
ACCOUNT_CHARTFIELD_SYNC |
GL_SETUP |
|
FO_RATE_ELEM_SYNC |
FO_SETUP |
|
FO_MC_TYPE_SYNC |
FO_SETUP |
Set Up Tables – Either Way
|
Service Operation |
Queue Name |
|---|---|
|
COUNTRY_SYNC Note: This is delivered as system data. Although doing so is possible, you probably will not need to synchronize this message because you are unlikely to make changes to the Country Table. |
ENTERPRISE_SETUP |
|
CURR_QUOTE_MTHD_SYNC |
MARKET_RATES |
|
CURRENCY_SYNC Note: This is delivered as system data. Although doing so is possible, you probably will not need to synchronize this message because you are unlikely to make changes to the Currency Codes table. |
ENTERPRISE_SETUP |
|
MARKET_RATE_LOAD |
MARKET_RATE_LOAD |
|
MARKET_RATE_DEFN_SYNC |
MARKET_RATES |
|
MARKET_RATE_INDEX_SYNC |
MARKET_RATES |
|
MARKET_RATE_SYNC |
MARKET_RATES |
|
MARKET_RATE_TYPE_SYNC |
MARKET_RATES |
|
STATE_SYNC |
ENTERPRISE_SETUP |
Transactional Tables – HCM to FIN
|
Service Operation |
Queue Name |
|---|---|
|
FO_ASGN_CONFIRM |
FO_ASSIGNMENTS |
|
FO_EMPL_DATA_SYNC |
FO_SETUP |
|
PERSON_ACCOMP_SYNC |
PERSON_DATA |
|
PERSON_BASIC_SYNC |
PERSON_DATA |
|
PERSON_COMPETENCY_SYNC |
PERSON_DATA |
|
WORKFORCE_SYNC |
PERSON_DATA |
|
ACTUAL_TIME_ADD |
ACTUAL_TIME |
|
ACTUAL_TIME_BATCH_ADD |
ACTUAL_TIME |
|
ESTIMATED_TIME_BATCH_ADD |
ESTIMATED_TIME |
Transactional Tables – FIN to HCM
|
Service Operation |
Queue Name |
|---|---|
|
CUSTOMER_SYNC |
CUSTOMER |
|
FO_APP_HIRE |
FO_APP_HIRE |
|
FO_ASGN_CREATE |
FO_ASSIGNMENTS |
|
FO_ASGN_RATES_SYNC |
FO_ASSIGNMENTS |
|
FO_ASGN_UPD |
FO_ASSIGNMENTS |
|
PROJECT_ACTIVITY_SYNC |
PROJECTS_SETUP |
|
PROJECT_ACTIVITY_TEAM_SYNC |
PROJECTS_SETUP |
|
PROJECT_SYNC |
PROJECTS_SETUP |
|
PROJECT_TEAM_SYNC |
PROJECTS_SETUP |
|
FO_MC_ART_BATCH |
FO_MASS_CHANGES |
After you activate these service operations, every subsequent change to data in any of the records associated with these messages triggers the publication and subscription of the new or deleted data. The result is that Pay/Bill Management reflects the change within a few seconds.
Note: Depending upon the release versions being integrated, multiple versions of a message may be in the database. The default version is the recommended version for use. If the default version in the source database does not match the version in the target database, then either a relationship or transformation needs to be set up in the source database.
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 |
The Integration Broker full table messages are delivered with a status of Inactive. The publishing rules must be activated. Information shared by the FSCM and the HCM databases for PeopleSoft Pay/Bill Management is updated properly when the appropriate messages are activated.
For example, Oracle publishes data from the PeopleSoft HCM table CM_CLUSTER_ACMP. This table is populated with new data from PeopleSoft HCM, and old data is deleted. The data from this table is published into a CLUSTER_ACCOMP_FULLSYNC message.