Enterprise Integration Points Used in PeopleSoft Time and Labor Integration

PeopleSoft Project Costing uses these application messages to integrate Financials application tables with HCM application tables:

Messages	Integration Point Name	Publisher
BUS_UNIT_PC_SYNC BUS_UNIT_PC_FULLSYNC	BUSINESS UNIT TABLE PC	Project Costing
PROJECT_SYNC PROJECT_FULLSYNC	PROJECT TABLE	Project Costing
PROJECT_ACTIVITY_SYNC PROJECT_ACTIVITY_FULLSYNC	PROJECT ACTIVITIES	Project Costing
PROJ_ACTIVITY_STATUS_SYNC PROJ_ACTIVITY_STATUS_FULLSYNC	PROJECT ACTIVITY STATUS	Project Costing
RESOURCE_TYPE_SYNC RESOURCE_TYPE_FULLSYNC	PROJECT RESOURCE TYPE	Project Costing
RES_TYPE_CAT_LINK_SYNC RES_TYPE_CAT_LINK_FULLSYNC	PROJECT TYPE-TO-CATEGORY LINK	Project Costing
RES_CAT_SUB_CAT_LINK_SYNC RES_CAT_SUB_CAT_LINK_FULLSYNC	PROJECT CATEGORY-TO-SUBCATEGORY LINK	Project Costing
RESOURCE_CAT_SYNC RESOURCE_CAT_FULLSYNC	PROJECT RESOURCE CATEGORY	Project Costing
RESOURCE_SUB_CAT_SYNC RESOURCE_SUB_CAT_FULLSYNC	PROJECT RESOURCE SUBCATEGORY	Project Costing
PROJECT_TEAM_SYNC PROJECT_TEAM_FULLSYNC	PROJECT TEAM	Project Costing
PROJECT_STATUS_DEFN_SYNC PROJECT_STATUS_DEFN_FULLSYNC	PROJECT STATUS DEFINITION	Project Costing
PROJECT_STATUS_SYNC PROJECT_STATUS_FULLSYNC	PROJECT STATUS	Project Costing
UOM_SYNC UOM_FULLSYNC	UNIT OF MEASURE	Financials to HCM
BUS_UNIT_FS_SYNC BUS_UNIT_FS_FULLSYNC	BUSINESS UNIT TABLE FS	Financials to HCM
TIME_REPORTING_CODE_SYNC TIME_REPORTING_CODE_FULLSYNC	TIME REPORTING CODES	Time and Labor
ACTUAL_TIME_ADD ACTUAL_TIME_BATCH_ADD	T&L ACTUAL TIME	Time and Labor
ESTIMATED_TIME_BATCH_ADD	T&L ESTIMATED TIME	Time and Labor
TBLSET_CONTROL_INITIALIZE SETID_INITIALIZE	TABLE SET CONTROL	Financials to HCM
ESTIMATE_FORECAST_TIME_REQUEST Publish Batch Program: PC_TL_TO_PC Subscribe Batch Program: TL_PUB_TM_AE	ESTIMATE & FORECAST TIME REQUEST	Project Costing

Note:

To research the technical details of any integration point used by PeopleSoft applications, refer to the online Interactive Services Repository found on Oracle's My Oracle Support website.

To enable the TBLSET_CONTROL_INITIALIZE service operation to publish between two databases, you must set up message chunking for the operation by record group. This process is described in these set of steps:

1. Identify the record groups that exist in both databases

2. Create a chunking rule for each record group and then add the chunking definition to the subscribing nodes of the group.

3. Enter the chunking rule you created to the full table publish rules definition for the TBLSET_CONTROL_INITIALIZE service operation.

If you are publishing to one node, this setup is sufficient; however, if you are publishing to multiple nodes, you need to add routing PeopleCode to the channel.

See Integration Interfaces: Setting Up Message Chunking.