integrating hcm 9.1 with fusion talent and workforce compensation

PeopleSoft HCM 9.1

Integrating PeopleSoft HCM 9.1 with Fusion Talent Management and Fusion Workforce Compensation

March 2012

Integrating PeopleSoft HCM 9.1 with Fusion Talent Management and Workforce Compensation

Copyright 2012, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS

Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are commercial computer software or commercial technical data pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

Hazardous Applications Notice This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.

Third Party Content, Products, and Services Disclaimer This software and documentation may provide access to or information on content, products and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third party content, products and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third party content, products or services.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

PeopleBook Update Integrating PeopleSoft HCM 9.1 with Fusion Talent Management and Fusion Workforce Compensation March 2012

Contents PeopleSoft HCM 9.1 to Fusion Talent Management and Fusion Workforce Compensation Coexistence ..... 5

Understanding the Coexistence ................................................................................................................. 5

Setting Up Domain Value Maps ................................................................................................................. 6

Understanding Domain Value Map Setup ............................................................................................... 6

Pages Used to Set Up Data Mapping ................................................................................................... 11

Reviewing Assigned Map Elements ...................................................................................................... 11

Reviewing Assigned Domain Elements ................................................................................................ 12

Importing Manually-Defined XREFs ...................................................................................................... 14

Verifying and Updating Domain Value Maps ........................................................................................ 15

Setting Up Web Services .......................................................................................................................... 15

Pages Used to Set Up Web Services ................................................................................................... 16

Activating Delivered Service Operations ............................................................................................... 17

Setting Access to Permission Lists ....................................................................................................... 19

Activating Delivered Handlers ............................................................................................................... 19

Adding a Routing .................................................................................................................................. 20

Setting Up and Managing Routing Definitions ...................................................................................... 21

Configuring Routing Connector Properties ........................................................................................... 23

Activating Queues ................................................................................................................................. 24

Updating Node Credentials ................................................................................................................... 24

Configuring Node Connector Properties ............................................................................................... 25

Updating Node Security ........................................................................................................................ 26

Managing Roles and User Profiles ........................................................................................................... 27

Pages Used to Manage Roles and User Profiles .................................................................................. 27

Confirming Permission Lists for Coexistence-Related Roles ................................................................ 28

Adding Coexistence-Related Roles to User IDs.................................................................................... 28

Creating URL Objects for the FTP Servers .............................................................................................. 29

Page Used to Create URL Objects for the FTP Servers ....................................................................... 29

Creating URL Objects ........................................................................................................................... 30

Configuring the Coexistence .................................................................................................................... 30

Copyright 2010, Oracle and/or its affiliates. All rights reserved. 3


Pages Used to Configure the Coexistence ........................................................................................... 30

Defining a Fusion Coexistence Configuration ID................................................................................... 31

Defining Fusion Integration Installation Options .................................................................................... 35

Defining the Sequence Order for Associated Job Actions and Reasons .............................................. 39

Defining a Rating Model ........................................................................................................................... 40

Page Used to Define a Rating Model .................................................................................................... 40

Defining the LANG Rating Model .......................................................................................................... 40

Sending Data to Fusion ............................................................................................................................ 42

Pages Used to Send Data to Fusion ..................................................................................................... 42

Sending Core HR Data to Fusion.......................................................................................................... 43

Migrating Profile Data to Fusion ............................................................................................................ 45

Reviewing Transformation Errors.......................................................................................................... 47

Reviewing Error Details ........................................................................................................................ 51

Receiving Data from Fusion ..................................................................................................................... 52

Understanding the Inbound Process ..................................................................................................... 53

Pages Used to Receive Data from Fusion ............................................................................................ 53

Receiving Compensation Data from Fusion .......................................................................................... 54

Deleting Compensation Data ................................................................................................................ 58

Reviewing Inbound Status and Transaction Errors ............................................................................... 60

Reviewing Inbound Errors ..................................................................................................................... 62

Correcting Inbound Errors ..................................................................................................................... 63

Reviewing a summary of Integration Object Changes .......................................................................... 65

4 Copyright 2010, Oracle and/or its affiliates. All rights reserved.


PeopleSoft HCM 9.1 to Fusion Talent Management and Fusion Workforce Compensation Coexistence This document provides an overview of the PeopleSoft side of the delivered coexistence package and discusses how to:

Set up domain value maps.

Manage web services.

Configure the coexistence.

Define a rating model.

Send data to Fusion.

Receive data from Fusion.

Understanding the Coexistence The PeopleSoft HCM 9.1 to Fusion Talent Management and Fusion Workforce Compensation coexistence enables customers to implement and maintain Fusion applications that leverage data from an established on-premise PeopleSoft HR system. This document focuses on how to set up and manage the PeopleSoft HCM 9.1 side of the coexistence.

There are three main data transfer processes that comprise the coexistence:

Sending core HR data from PeopleSoft HCM to Fusion.

Migrating profile data from PeopleSoft HCM to Fusion.

Receiving compensation data from Fusion.

Sending Core HR Data to Fusion

This process enables you to transform and send the following types of core HR data to Fusion:

Location

HR Business Unit

Department

Job Grade

Job Code

Person/Job

Department Tree



Position

Job Grade Rate

Salary

Bonus

PeopleSoft HCM 9.1 serves as the system of record for this data and the synchronization of this data with the Fusion Talent Management system occurs on a regular (e.g., daily) basis. You manage the frequency of the data synchronization between PeopleSoft HCM 9.1 and Fusion Talent Management using the PeopleTools Process Scheduler.

See Also


Migrating Profile Data

This is a one-time process that migrates the performance appraisal data from PeopleSoft HCM 9.1 to Fusion. Once that process is run, the data is maintained in the Fusion system going forward.

See Also

Migrating Profile Data to Fusion

Receiving Compensation Data

Fusion Workforce Compensation serves as the system of record for this process, which reviews and updates workforce compensation data. Through this process, Fusion Workforce Compensation passes data back to the PeopleSoft HCM 9.1 system to update employee records for future payroll processing.

It is also possible to pass bonus information from Fusion to PeopleSoft Payroll using existing integration functionality included with the PeopleSoft Variable Compensation application.

See Also

Receiving Data from Fusion

Setting Up Domain Value Maps This section provides an overview of domain value map setup and discusses how to:

Review assigned map elements.

Review assigned domain elements.

Verify and update domain value maps.

Import manually-defined XREFs.

Understanding Domain Value Map Setup Domain value maps (DVMs) are what PeopleSoft HCM uses to associate PeopleSoft objects with Fusion objects when transforming data. PeopleSoft delivers the definitions for all of these DVMs, but the customer must verify their delivered populated values. In addition, some of the delivered DVMs require that you manually set up and populate values for them.



Note. You load and manage DVM definitions and values using the PeopleSoft Application Integration Framework, which is part of Enterprise Components and is a prerequisite for the coexistence.

See Also

Enterprise Components: Application Integration Framework, Defining and Populating Value Maps, Understanding Value Maps

Delivered DVMs

The following table lists the DVMs that are delivered as part of the PeopleSoft HCM 9.1 to Fusion Talent Management and Fusion Workforce Compensation coexistence. The table lists the name of each DVM along with the system object to which it pertains. In addition, the System Data column lists a code which indicates the type of values PeopleSoft delivers for it as system data. The system data codes are:

PF: The DVM has both PeopleSoft and Fusion values delivered as system data. Customers should verify the delivered values.

P: The DVM has PeopleSoft values delivered as system data. Customers should verify the delivered values and add corresponding Fusion values.

M: The DVM has no values delivered as system data and is also known as a manual XREF. Populating the values for this DVM requires setting up the date in Fusion, exporting the data to a .dat file, manually modifying the .dat file, saving it as a .csv file, and importing the values into PeopleSoft.

N: The DVM has no values delivered as system data. Customers must populate the values for this DVM using the Populate Domain Value Maps page of the PeopleSoft Application Integration Framework.

X: The DVM has no values delivered as system data. Populating the values for this DVM requires setting up the date in Fusion, exporting the data to a .dat file, manually modifying the .dat file, saving it as a .csv file, and importing the values into PeopleSoft. In addition, these DVMs need to be seeded with specific values.

See Also

Importing Manually-Defined XREFs

See Also

Enterprise Components: Application Integration Framework, Defining and Populating Value Maps, Importing Value Maps

Verifying and Updating Domain Value Maps

DVM Name Related System Object System Data

ACTION_REASON_XREF Worker M

ACTION_XREF Worker M

ADDRESS_USE_CODE Worker P

BONUS_ELEMENT_TYPE_XREF PayrollElemenEntry M

BONUS_INPUT_VALUE_XREF PayrollElemenEntry M




CountryCodeDVM Most All P

CURRENCY95CODE Many P

FREQUENCY_CODE Worker Position P

FREQUENCY_TYPE_CODE Salary P

GRADE_ACTIVE_STATUS_CODE Grade PF

JOB_ACTIVE_STATUS_CODE Job Code PF

JOB_FUNCTION_CODE Job Code P

JOB_MANAGER_LEVEL_CODE Job Code P

JOB_MEDICAL_CHECKUP_REQUIRED_CODE Job Code PF

JOB_REGULAR_FLAG_CODE Job Code P

LanguageCodeDVM Most All P

LEGAL_ENTITY_XREF Many M

LEGISLATIVE_DATA_GROUP_XREF GradeRate M

LOCATION_GEO_HIERARCHY_NODE_CODE Location P

MARITAL_STATUS Worker (Person) P*

PERSON_EMAIL_ADDRESS_TYPE_CODE Worker (Person) P

PERSON_ETHNICITY_CODE Worker (Person) N

PERSON_GENDER_CODE Worker (Person) P*

PERSON_HIGHEST_EDU_LEVEL_CODE Worker (Person) P

PERSON_NAME_PREFIX_CODE Worker (Person) P

PERSON_NAME_TYPE_CODE Worker P

PERSON_NID_TYPE_CODE Worker (Person) P

PERSON_RELIGION_CODE Worker (Person) N

PHONE_TYPE_CODE Worker (Person) P

POSITION_FULL_PART_TIME_CODE Position P

POSITION_HIRING_STATUS_CODE Position P

POSITION_SECURITY_CLEARANCE_CODE Position P

POSITION_TYPE_CODE Position P

SALARY_COMP_ACTION_REASON_CODE Salary P




SALARY_ELEMENT_TYPE_XREF Salary M

SALARY_INPUT_VALUE_XREF Salary M

SETID_XREF Many M

StateCodeDVM Location P

TALENTPROFILETYPE_XREF TalentProfileType X

TP_CI_LANGUAGE_XREF TPContentType M

TP_CI_RELATIONSHIP_CODE TPContentType/TPContentItemRelationship P

TP_CT_XREF TPContentType X

TP_IMPORTANCE_CODE TalentProfileItem P

TP_INTEREST_LEVEL_CODE TalentProfileItem P

TP_OBJECT_ASSOCIATION_XREF TalentProfile X

TP_USAGE_CODE TalentProfileType/TalentProfile P

TPINSTANCEQUALIFIERSET_IN_XREF TalentProfileInstanceQualifier X

TREE_VERSION_ACTIVE_STATUS_CODE Many PF

WORKER_ASSIGNMENT_CLASSIFICATION_CODE Worker/ Assignments P

WORKER_ASSIGNMENT_EMPLOYEE_CATEGORY_CODE Worker P

WORKER_ASSIGNMENT_STATUS_TYPE_XREF Worker M

WORKER_ASSIGNMENT_TYPE_CODE Worker P

WORKER_BARG_UNIT_CODE Worker N

WORKER_EMPL_TYPE_CODE Worker/ Assignments P

WORKER_PAYROLL_STATUS_CODE Worker P

WORKER_PERSON_TYPE_XREF Worker M

WORKER_PRIMARY_INDICATOR_CODE Worker/ Assignments P

WORKER_SYSTEM_PERSON_TYPE_CODE Worker P

WORKER_TYPE_CODE Worker P

WORKER_WORK_TERM_ASSIGNMENT_TYPE_CODE Worker P

*Indicates a DVM for which customers must map the PeopleSoft value of Unknown to Null in Fusion.

Note. This table lists only the delivered static value maps (DVMs). The PeopleSoft HCM 9.1 to Fusion Talent Management and Fusion Workforce Compensation coexistence also includes delivered dynamic value maps (cross-references) as system data, but they require no customer modification. You can use the Define Value Maps component to review the definitions of both types of delivered value maps.



Manual Setup of XREF DVMs

Delivered type M (manual XREF) and type X DVMs (for example, WORKER_PERSON_TYPE_XREF and TP_OBJECT_ASSOCIATION_XREF) require manual set up.

Note. The DVMs with the XREF suffix are static value maps. Do not confuse the _XREF suffix with the term cross-reference, which is often used synonymously with dynamic value maps when discussing the Application Integration Framework.

To manually set up and import an XREF DVM:

1. Define the object in Fusion and export the primary Fusion keys and other descriptive attributes to a .dat file. This file should contain the auto-generated GUID, Fusion key and/or user-intelligent Fusion description fields corresponding to the PeopleSoft values populated for the DVM.

2. Open the .dat file in Microsoft Excel.

3. Enter the PeopleSoft keys to map the functional Fusion description and Fusion GUID, and save the file in .csv format. Make sure you configure the .csv file following these guidelines:

a. The first row in the file must contain DVM in the first column and the name of the map to be imported in the second column.

b. Each column in the second row of the file must identify the names of the elements into which the values will be imported. Reference data is optional. To define a reference data column that will be ignored by the import process, add an asterisk (*) in front of the name, or leave the name blank.

c. Subsequent rows in the file identify the data values to be imported, and must contain the same number of columns as the second row.

Example of a correctly configured .csv file 4. Import the modified .csv file using the Import Value Maps page.

See

Importing Manually-Defined XREFs

5. Review the imported data using the Populate Domain Value Maps page to verify that it is correct.

See




Pages Used to Set Up Data Mapping

Page Name Object Name Navigation Usage

Define Value Maps - Elements

EOTF_DEFINE_MAPS Enterprise Components, Integration Definitions, Transformation Framework, Define Value Maps

Review assigned map elements.

Define Value Maps Domains

EOTF_DEFINE_MAPS2 Enterprise Components, Integration Definitions, Transformation Framework, Define Value Maps, Domains

Review assigned domain elements.

Import Value Maps EOTF_MAP_IMPORT Enterprise Components, Integration Definitions, Transformation Framework, Import Value Maps

Import manually-defined XREFs.

Populate Domain Value Maps

EOTF_POPULATE_DVMS Enterprise Components, Integration Definitions, Transformation Framework, Populate Domain Value Maps

Verify and update domain value maps.

Reviewing Assigned Map Elements Access the Define Value Maps - Elements page (Enterprise Components, Integration Definitions, Transformation Framework, Define Value Maps).



Define Value Maps - Elements page PeopleSoft delivers all of the DVM definitions that are relevant to the coexistence with Fusion Talent Management and Fusion Workforce Compensation. Therefore you will typically use this page only as a reference for determining the elements that are assigned to a particular DVM.

See Also

Enterprise Components: Application Integration Framework, Defining and Populating Value Maps, Defining Value Maps

Reviewing Assigned Domain Elements Access the Define Value Maps - Domains page (Enterprise Components, Integration Definitions, Transformation Framework, Define Value Maps, Domains).



Define Value Maps - Domains page PeopleSoft delivers all of the DVM definitions that are relevant to the coexistence with Fusion Talent Management and Fusion Workforce Compensation. Therefore you will typically use this page only as a reference for determining the elements that are assigned to domains of a particular DVM.



See Also

Enterprise Components: Application Integration Framework, Defining and Populating Value Maps, Defining Value Maps

Importing Manually-Defined XREFs Access the Import Value Maps page (Enterprise Components, Integration Definitions, Transformation Framework, Import Value Maps).

Import Value Maps page To import your configured .csv files, update the fields on this page as follows:

File Name Enter the name of the file to be imported, including the path.

Import Mode Select the Values Only value.

Note. It is important that you select the Values Only value. If you were to select either of the other values, the import process would override the map definition. This would likely result in having to manually redefine the map.

Delete Map/Data Before Import

Select this check box.

Column Separator Leave this field blank.

Concatenation Separator Leave this field blank.

Import Click to initiate the Import process.

See Also

Enterprise Components: Application Integration Framework, Defining and Populating Value Maps, Importing Value Maps



Verifying and Updating Domain Value Maps Access the Populate Domain Value Map page (Enterprise Components, Integration Definitions, Transformation Framework, Populate Domain Value Maps).

Populate Domain Value Maps page A column appears on this page for each element assigned to the DVM, excluding Unique GUID, which is an element common to all DVMs. Use this page to verify delivered element values, and to add and update values to suit your business process needs.

Note. Make sure that all of the fields in all of the columns have values or you might encounter unexpected results when running the data transformation process (FT_EXTRACT). The exceptions to this are any Description or Description2 columns. Blank fields in these columns are not problematic.

See Also

Enterprise Components: Application Integration Framework, Defining and Populating Value Maps, Populating a Domain Value Map

Setting Up Web Services The files transported between the PeopleSoft environment and the Fusion environment are single compressed .zip files. The transfer of these files to and from the PeopleSoft environment is supported by PeopleSoft Integration Broker web service messages. PeopleSoft delivers the web service message structure as part of the PeopleSoft HCM 9.1 to Fusion Talent Management and Fusion Workforce Compensation coexistence, but there are several steps you must take to complete the Integration Broker configuration:

Set up and activate service operations, handlers, and routings.



Set access to permission lists.

Configure routing connector properties.

Activate queues.

Update node credentials.

Configure node connector properties.

Update node security.

Note. PeopleSoft Fusion Coexistence does not support file transfer using Oracle Universal Content Management (UCM). Oracle recommends that you use either a generic web service or a command line to transfer files to and from UCM.

Pages Used to Set Up Web Services


Service Operations - General

IB_SERVICE PeopleTools, Integration Broker, Integration Setup, Service Operations, General

Activate delivered service operations.

Web Service Access WS_ACCESS_IB Click the Service Operations Security link on the Service Operations - General page.

Set access to permission lists.

Service Operations - Handlers

IB_SERVICEHDLR PeopleTools, Integration Broker, Integration Setup, Service Operations, Handlers

Activate delivered handlers.

Service Operations - Routings

IB_SERVICERTNGS PeopleTools, Integration Broker, Integration Setup, Service Operations, Routings

Add routing definitions.

Routing Definition IB_ROUTINGDEFN PeopleTools, Integration Broker, Integration Setup, Service Operations, Routings

Click a routing link in the Name column.

Activate delivered routings.

Queue Definitions IB_QUEUEDEFN PeopleTools, Integration Broker, Integration Setup, Queues

Activate delivered queue.

Connector Properties IB_ROUTINGDEFNCON Click the Connector Properties tab from the Routing Definition page.

Configure routing connector properties.




Node Definitions IB_NODE PeopleTools, Integration Broker, Integration Setup, Node, Node Definitions

Update node credentials.

Connectors IB_NODECONN PeopleTools, Integration Broker, Integration Setup, Node, Connectors

Configure node connector properties.

WS Security IB_NODESECURITY PeopleTools, Integration Broker, Integration Setup, Node, WS Security

Update node security.

See Also

PeopleTools 8.52 PeopleBook: PeopleSoft Integration Broker, Managing Service Operations, Accessing and Viewing Service Operation Definitions

PeopleTools 8.52 PeopleBook: PeopleSoft Integration Broker, Managing Service Operation Queues, Adding Queue Definitions

PeopleTools 8.52 PeopleBook: PeopleSoft Integration Broker, Managing Service Operation Routing Definitions, Understanding Adding Routing Definitions

Activating Delivered Service Operations Access the Service Operations - General page (PeopleTools, Integration Broker, Integration Setup, Service Operations, General).



Service Operations - General page

READY_FOR_LOAD and READY_FOR_TRANSMISSION

Select the User/Password Required and Active check boxes for the READY_FOR_LOAD and READY_FOR_TRANSMISSION service operations.



WORKFORCE_SYNC

Select the Active check box for the WORKFORCE_SYNC service operation. In addition, make sure that the value in the Message.Version field is WORKFORCE_SYNC.VERSION_2.

Setting Access to Permission Lists Access the Web Service Access page (click the Service Operations Security link on the Service Operations - General page).

Web Service Access page Set the Access field to Full Access for the HCCPFT1000 permission list. Do this for the READY_TO_LOAD, READY_FOR_TRANSMISSION, and WORKFORCE_SYNC service operations.

See Also

PeopleTools 8.52: PeopleSoft Integration Broker Administration, Using the Integration Network, Setting Service Operation Permissions

Activating Delivered Handlers Access the Service Operations - Handlers page (PeopleTools, Integration Broker, Integration Setup, Service Operations, Handlers).

Service Operations - Handlers page (READY_FOR_LOAD)



Service Operations - Handlers page (WORKFORCE_SYNC)


To activate the delivered handlers for the READY_FOR_LOAD and READY_FOR_TRANSMISSION service operations, select the Active value in the Status column for each handler.

WORKFORCE_SYNC

For the WORKFORCE_SYNC service operation, select Active in the Status column for the FT_WorkforceSync handler.

Adding a Routing Access the Routings page (PeopleTools, Integration Broker, Integration Setup, Service Operations, Routings).



Routings page For the WORKFORCE_SYNC service operation, enter WORKFORCE_SYNC_LOCAL in the Routing Name field and click the ADD button. This takes you to the Routing Definitions page.

Setting Up and Managing Routing Definitions Access the Routing Definition page (click a routing link in the Name column on the Service Operations - Routings page).



Routing Definitions page (READY_FOR_LOAD)

Routing Definitions page (READY_FOR_TRANSMISSION)

Routing Definitions page (WORKFORCE_SYNC_LOCAL)




To activate the delivered routings for the READY_FOR_LOAD and READY_FOR_TRANSMISSION service operations, select the Active check box for each service operations routing.

WORKFORCE_SYNC_LOCAL

Select the Active check box to activate the WORKFORCE_SYNC_LOCAL routing. In addition, enter your local node in the Sender Node and Receiver Node fields.

Configuring Routing Connector Properties Access the Connector Properties page (click the Connector Properties tab from the Routing Definition page).

Connector Properties page Add the following connector properties for the READY_TO_LOAD routing:

Property ID Property Name Value

HEADER Content-Type text/xml

HEADER sendUncompressed Y

HTTPPROPERTY Method POST

HTTPPROPERTY SOAPUpContent Y

PRIMARYURL URL The URL that you use for your Fusion




EndPoint URL.

Activating Queues Access the Queues Definitions page (PeopleTools, Integration Broker, Integration Setup, Queues).

Queue Definitions page To activate a queue, select the Run value in the Queue Status field. In addition, ensure that the Unordered check box is selected. Make sure you do this for both the FT_WEB_SERVICES and PERSON_DATA queues.

Updating Node Credentials Access the Node Definitions page (PeopleTools, Integration Broker, Integration Setup, Nodes, Node Definitions).



Node Definitions page For the PSFT_FUSION node, make sure the values of the Authentication Option, Node Password, Default User ID, External User ID, and External Password fields match the credentials defined for your Fusion system.

Configuring Node Connector Properties Access the Connectors page (PeopleTools, Integration Broker, Integration Setup, Nodes, Connectors).



Connectors page Add the following connector properties for the PSFT_FUSION node:


HEADER Content-Type text/xml

HEADER sendUncompressed Y

HTTPPROPERTY Method POST

HTTPPROPERTY SOAPUpContent Y

PRIMARYURL URL The URL that you use for your Fusion EndPoint URL.

Updating Node Security Access the WS Security page (PeopleTools, Integration Broker, Integration Setup, Node, WS Security).



WS Security page Authentication Token Type Select the Username Token value.

Use External User ID Make sure this check box is selected.

Managing Roles and User Profiles To have access to all of the functionality associated with the PeopleSoft HCM 9.1 to Fusion Talent Management and Workforce and Compensation coexistence, user IDs must be associated with the correct permission lists and roles.

This section discusses how to:

Confirm permission lists for coexistence-related roles.

Add coexistence-related roles to user IDs.

Pages Used to Manage Roles and User Profiles


Permission Lists ROLE_CLASS PeopleTools, Security, Permissions & Roles, Roles, Permission Lists

Confirm permission lists for coexistence-related roles.




Roles USER_ROLES PeopleTools, Security, User Profiles, User Profiles, Roles

Add the coexistence-related roles to user IDs.

Confirming Permission Lists for Coexistence-Related Roles Access the Permission Lists page (PeopleTools, Security, Permissions & Roles, Roles, Permission Lists).

Permission Lists page

Fusion Integration Specialist Permission Lists

For the Fusion Integration Specialist role, confirm that the following permission lists are added in the Permission Lists group box:

HCCPFT1000 (Manage Fusion Integration)

HCCPHR3000 (Setup Workforce Tables)

EOTF_ADMIN Role Permission Lists

For the EOTF_ADMIN role, confirm that the following permission lists are added in the Permission Lists group box:

EOTF1000 (Transform Framework Setup)

EOTF1100 (Transform Framework Data Admin)

EOTF1200 (Transform Framework Runtime)

See Also

PeopleTools 8.52 PeopleBook: Security Administration, Setting Up Roles, Defining Role Options

Adding Coexistence-Related Roles to User IDs Access the Roles page (PeopleTools, Security, User Profiles, User Profiles, Roles).



Roles page For user IDs that need to be able to administrate and run the integration processes, add the Fusion Integration Specialist and HR Labor Comp Specialist roles in the User Roles group box.

For user IDs that need to be able to set up and administrate transformation maps and values, add the EOTF_ADMIN (Transform Framework Admin) role in the User Roles group box.

Note. For user IDs that need only to update domain map values, you can add the role EOTF_ANALYST (Transform Framework Analyst) instead of EOTF_ADMIN.

See Also

PeopleTools 8.52 PeopleBook: Security Administration, Administering User Profiles, Specifying User Profile Attributes

Creating URL Objects for the FTP Servers You must create a URL objects for the FTP servers used for the PeopleSoft HCM 9.1 to Fusion Talent Management and Fusion Workforce Compensation coexistence.

Page Used to Create URL Objects for the FTP Servers


URL Maintenance URL_TABLE PeopleTools, Utilities, Administration, URLs

Create URL objects for the FTP servers.



Creating URL Objects Access the URL Maintenance page (PeopleTools, Utilities, Administration, URLs).

URL Maintenance page Use this page to define a URL object for an FTP server. You must define a separate URL object for each of the FTP servers used in the coexistence.

See Also

PeopleTools 8.52 PeopleBook: System and Server Administration, Using PeopleTools Utilities, Using Administration Utilities

Configuring the Coexistence The PeopleSoft HCM 9.1 to Fusion Talent Management and Fusion Workforce Compensation coexistence includes new components that enable you to configure your coexistence. This section discusses how to:

Define a Fusion coexistence configuration ID.

Define Fusion integration installation options.

Define the sequence order for associated job actions and reasons.

Pages Used to Configure the Coexistence


Configuration FT_CONFIG Set Up HRMS, Common Definitions, Fusion Integrations, Talent/Workforce Compensation, Configure Process Options

Configure outbound/inbound file and notification options.




Fusion Integration Installation Options

FT_INSTALL Set Up HRMS, Common Definitions, Fusion Integrations, Talent/Workforce Compensation, Installation Options

Define the domains, configuration, and data filter options for your Fusion integration.

Job Action/Reason Sequence

FT_JOB_ACT_SEQ Set Up HRMS, Common Definitions, Fusion Integrations, Talent/Workforce Compensation, Job Action/Reason Sequence

Define the inbound interface sequence order for associated job actions and reasons.

Defining a Fusion Coexistence Configuration ID Access the Configuration page (Set Up HRMS, Common Definitions, Fusion Integrations, Talent/Workforce Compensation, Configure Process Options).

Configuration page (1 of 2)



Configuration page (2 of 2) Use this page to create configuration IDs to define different default processing options for both outbound and inbound data processing. You can then use these configuration IDs to specify processing options for the various coexistence run control pages.



Integration Type Select which type of integration you are configuring. Values are:

Inbound: Integration for incoming data from Fusion Workforce Compensation.

Outbound: Integration for data transformation and extract to send to Fusion.

This selection affects which fields appear in the File Options and Notification Options group box. If you select Inbound, the group box containing the File Location and Zip File Name fields is labeled Manual Load File Options and the Receive Zip File from FTP Server check box appears in the File Options group box. In addition, the check box that appears in the Notification Options group box is labeled Send Email on Successful File Load.

If you select Outbound, the group box containing the File Location and Zip File Name fields is labeled Create File Options and the Send Zip File from FTP Server check box appears in the File Options group box. In addition, two check boxes appear in the Notification Options group box labeled Send Email upon Receiving Acknowledgement Message and Send Email Notification of File Creation Summary.

File Options

The purpose of the fields in this group box depends on whether you are configuring an inbound or outbound integration. If you are configuring an inbound integration, these fields define how and from where you are receiving information from Fusion. If you are configuring an outbound integration, these fields define how and to where you are sending information to Fusion.

File Location Enter the existing file location used for the integration process.

For the outbound process, this is the location where the system creates output files and the resulting zip file.

For the inbound process, this is the location from which the system receives, extracts, and processes the inbound zip file.

Therefore, the file location needs to be read-writable by the process.

Note. The file location must be local to the PS scheduler server. In other words, it must be accessible at run time.



Zip File Name Enter the name of the zip file that contains data received from Fusion or data that you send to Fusion.

The zip file name can contain the following value place holders, which are replaced by actual values at run time:

%processinstance: The process instance of the process.

%runcontrol: The run control ID of the process.

%userid: The ID of the user who runs the process.

%date: The date of zip file creation.

%time: The time of zip file creation.

%yyyymmdd: The date of zip file creation in yyyymmdd format.

%hhmmss: The time of zip file creation in hhmmss format.

Note. The outbound zip file name must have the .zip extension, in lower case. Therefore, when you save the page, the system validates the name and updates it to include a lower case .zip if necessary.

You can override the zip file name specified for a configuration ID on the run control pages using the Output Zip File Override field.

Send Zip File to FTP Server Select to enter FTP server details for sending data to Fusion. If you select this check box, the FTP Server URL ID and FTP Server Path fields appear.

In production, this check box should remain selected to automatically send the outbound data to the Fusion FTP server. If this option is deselected then the program creates the zip file, but does not send the file to the Fusion FTP server. Instead, the file is placed in the location specified in the File Location field.

You might deselect this check box during test or to otherwise inspect the file before sending it to Fusion.

In addition, the system does not call the web services used to communicate the creation of the file when this option is deselected.



Receive Zip File from FTP Server

If you select this check box, the system automatically retrieves the inbound zip file from the FTP server from the path specified in the FTP Server Path field and moves it to the location specified in the File Location field. If you deselect this check box, the system expects that the inbound zip file has already been copied into the file location.

Note. If you use the web service to automatically load the file, the system uses the inbound default configuration ID specified on the Fusion Integration Installation Options.

Typically you will want to select this check box and provide the FTP information on that configuration ID in order to automatically retrieve the file from the FTP server.

FTP Server URL ID Enter the URL ID of the FTP server to which you send data bound for Fusion or from which you receive data from Fusion.

FTP Server Path Enter the path of the FTP server to which you send data bound for Fusion or from which you receive data from Fusion.

Notification Options

The types of notifications that you can enable in this group box depend on whether the integration is inbound or outbound. Selecting any of the Send Email check boxes enables you to enter the subject, sender, recipients, and message text for the associated notification email.

Send Email on Successful File Load

Select to send a notification email whenever incoming files are loaded successfully.

Send Email upon Receiving Acknowledgment Message

Select to send a notification email whenever the system receives an acknowledgement from Fusion that the outgoing file was received.

Send Email Notification of File Creation Summary

Select to send a notification email with a summary of information regarding the creation of each outgoing zip file.

Send Email on Errors

Unlike the other notifications, emails sent when the system encounters errors with the sending or receiving of zip files are not optional. Enter the subject, sender, recipients, and message text for the error message.

Defining Fusion Integration Installation Options Access the Fusion Integration Installation Options page (Set Up HRMS, Common Definitions, Fusion Integrations, Talent/Workforce Compensation, Installation Options).



Fusion Integration Installation Options page

Note. This page is required setup for Fusion integration.

PeopleSoft Domain The value in this field should be PSFT to correspond to the values used in the Application Integration Framework. All of the DVMs and XREFs are delivered with the PSFT domain value.

If you change this value, then you must update the PeopleSoft domain definitions for all of the corresponding DVMs and XREFs.

Fusion Domain This value in this field should be FusionTalent to correspond to the values used in the Application Integration Framework. All of the DVMs and XREFs are delivered with the FusionTalent domain value.

If you change this value then you must update the Fusion domain definitions for all of the corresponding DVMs and XREFs.

Primary Mailing Address Type

Select the address type that the system uses to determine the primary mailing address for employees.

The system uses this value as the default mailing address on the Fusion employee HR address record. In addition, the system uses this value to set the Person Address default in Fusion.

Department Hierarchy Tree The system uses the value you enter here to determine the manager for employees in specific cases.

The system determines an employees manager based on:

1. The supervisor ID in the Job record.

2. The manager of the department if there is no supervisor ID in the Job record.

3. If the manager from steps 1 and 2 is the same as the employee, the system uses the department hierarchy tree specified here to find the parent department and retrieve the manager of the parent department.

Inbound Default Config ID (inbound default configuration ID)

Enter the ID of the default inbound configuration you want the system to use for inbound web service calls.

See Also

Receiving Data from Fusion



Data Filter Options

The fields in this group box enable you to filter the employee data that the system extracts, transforms, and sends to Fusion when you run the FT_EXTRACT process.

Note. Control data is not affected by these filter options.

See Also


Point in Time The system extracts and publishes data only for employees whose HR Status is Active as of the date you enter here or later.

Company Data Filter Option Define how the system filters by company when it extracts and publishes data to Fusion. Values are:

All: The system extracts and publishes data for all companies.

Specify: The system extracts and publishes data only for the companies that you specify in the Company Data Filters grid, which becomes available when you select this value.

Reg Region Data Filter Option (regulatory region data filter option)

Define how the system filters by regulatory region when it extracts and publishes data to Fusion. Values are:

All: The system extracts and publishes data for all regulatory regions.

Specify: The system extracts and publishes data only for the regulatory regions that you specify in the Regulatory Region Data Filters grid, which becomes available when you select this value.

Note. Currently, it is only possible to specify US regulatory regions.

Set ID Data Filter Option Define how the system filters by set ID when it extracts and publishes data to Fusion. Values are:

All: The system extracts and publishes data for all set IDs.

Specify: The system extracts and publishes data only for the set IDs that you specify in the Set ID Data Filters grid, which becomes available when you select this value.



Group Data Filter Option Define how the system filters by Groups when it extracts and publishes data to Fusion. Values are:

All: The system extracts and publishes data for all groups.

Specify...: The system extracts and publishes data only for the group IDs that you specify in the Group Data Filters grid, which becomes available when you select this value.

Note. The system extracts and publishes data only for employees whose HR status is Active on or before the date in the Refinement Date field.

Note. In selecting your data filters, make sure that the assignment supervisors for the filtered employees also meet your filter criteria. If the assignment supervisors do not meet the filter criteria, the system automatically selects the employees that reference those assignment supervisors for data transformation.

To identify the supervisors of the filtered employees, you need to reference those employees assignment records.

Defining the Sequence Order for Associated Job Actions and Reasons Access the Job Action/Reason Sequence page (Set Up HRMS, Common Definitions, Fusion Integrations, Talent/Workforce Compensation, Job Action/Reason Sequence).

Job Action/Reason Sequence page This page is required only for receiving inbound compensation data from Fusion. Fusion can send multiple job actions and reasons back from Workforce Compensation. This page defines the sequence in which the system processes changes. The sequence is by action and action reason (reason code). Add all of the job actions and corresponding reason codes used by the inbound process.



Defining a Rating Model Prior to migrating profile data to Fusion, you must define a specific rating model. The rating model represents a set of numeric codes for ranking an employees degree of expertise or experience in a competency. This section discusses how to define the LANG rating model.

Page Used to Define a Rating Model


Rating Model RATING_MDL_TBL Set Up HRMS, Product Related, Profile Management, Content Catalog, Rating Model

Define the LANG rating model.

Defining the LANG Rating Model Access the Rating Model page (Set Up HRMS, Product Related, Profile Management, Content Catalog, Rating Model).

Rating Model page: General tab Create a rating model with the name LANG and enter the following values:

Rating Model Description

Effective Date Enter an effective date of 01/01/1900.

Status Set the status to Active.

Description Enter a description of Language Ratings.



Short Description Enter a short description of Language.

Review Band Leave this check box deselected.

General Tab

Enter three rows with the following values:

Rating Description Short Description Numeric Rating

1 1 - Low Low 1.00

2 2 - Moderate Moderate 2.00

3 3 - High High 3.00

Note. Leave the Career Strength/Development field blank for all three rows.

Rating Model page: Review Points tab

Review Points Tab

Enter the following values for the three ratings you entered on the General tab:

Rating Review Points From Points To Points Eligibility Points

1 1 0 0 0.0



Rating Review Points From Points To Points Eligibility Points

2 2 0 0 0.0

3 3 0 0 0.0

See Also

PeopleSoft Human Resources 9.1 PeopleBook: Manage Competencies, Setting Up Competencies and Accomplishments, Setting Up Competencies

Sending Data to Fusion This section discusses how to:

Send core HR data to Fusion.

Review transformation errors.

Review error details.

Migrate profile data to Fusion.

Pages Used to Send Data to Fusion


Transformation Process FT_XTRCT_RUN_CNTL Workforce Administration, Collective Processes, Fusion Integration, Talent/Workforce Compensation, Send HR Data to Fusion

Send core HR data to Fusion.

Talent Profile Migration Process

FT_X_RUN_CNTL_TP Workforce Administration, Collective Processes, Fusion Integration, Talent/Workforce Compensation, Migrate Profile Data

Migrate Profile data to Fusion.

Error Summary FT_ERR_LOG_REVIEW Workforce Administration, Collective Processes, Fusion Integration, Talent/Workforce Compensation, Transformation Error Log

Review transformation errors for inbound and outbound processes.

Error Data FT_ERR_DATA_REVIEW Click an Error Data link on the Error Summary page.

Review the details for a specific error.



Sending Core HR Data to Fusion Access the Transformation Process page (Workforce Administration, Collective Processes, Fusion Integration, Talent/Workforce Compensation, Send HR Data to Fusion).

Transformation Process page

Process Request Parameters

Use the fields in this group box to define the high level parameters for the transformation process.

Note. The Process Frequency group box is a standard component of run control pages for Application Engine processes. You will almost always want the Always Process radio button selected.

Request ID Enter a unique ID for the request.



Description Enter an optional description for the transformation process run.

Configuration ID Enter an outbound configuration ID. This ID instructs the system what to name the resulting zip file along with where to post it. It also defines the notification options.

See Also

Defining a Fusion Coexistence Configuration ID

Output Zip File Override If you want to enter a file name that is different than the one specified by the selected configuration ID, enter it here.


Transformation Processes

The fields in this group box determine the type of core HR data that the system processes when you click the Run button.

Select Select this check box next to each type of core HR data you want included in the transformation process.

Process Lists the different processes for core HR data that can be included in the overall transformation process.

There is a separate Application Engine process for each item listed here. Each process generates one or more flat files. FT_EXTRACT is the controlling program that calls each Application Engine process you select here.

Description Enter an optional description for the transformation process run.

TM (Talent Management) and WFC (Workforce Compensation)

Indicate whether the data type applies to Fusion Talent Management or Fusion Workforce Compensation.

Process Dependency Lists dependencies for certain types of data transformation. Pay close attention to these dependencies when selecting which types of data to include in the transformation.



Running the Transformation Process

Click the Run button to initiate the FT_EXTRACT Application Engine process. This process calls the Application Engine processes you select in the Transformation Processes group box to extract the specified data. It then transforms the data into a format readable by Fusion Talent Management and Fusion Workforce Compensation and posts it as a single zip file to the FTP server defined by the specified configuration ID.

You can review any errors that the process encounters on the Error Summary page. After reviewing those errors, you can rerun the FT_EXTRACT process if necessary.

Note. The FT_EXTRACT process filters the extracted employee data based on the data filter options defined on the Fusion Integration Installation Options page. It does not, however, apply these data filter options to control data.

Note. The FT_EXTRACT process does not support data values that contain the pipe (|) character.

See Also

Defining Fusion Integration Installation Options

Reviewing Transformation Errors

Migrating Profile Data to Fusion Access the Talent Profile Migration Process page (Workforce Administration, Collective Processes, Fusion Integration, Migrate Profile Data).

Talent Profile Migration Process page



Run the talent profile migration process

Once you run the Talent Profile Migration process (FT_EXTRCT_TP), the Run button becomes unavailable. This is because you typically run this process only once. If it becomes necessary to run this process again, select the Run the talent profile migration process to re-enable the Run button.

Note. The system does not pass any changes to profile data to Fusion after you have migrated your profile data from PeopleSoft HCM to Fusion. If you need to resend data for an employee, you must first set the FT_PROF_MIGR_DATE to Null on the FT_XTRCT_EMPLID record for that employee.


Request ID Enter a unique request ID for the migration.

Description Enter an optional description for the migration.

Configuration ID Enter an outbound configuration ID. This ID instructs the system what to name the resulting zip file along with where to post it.

See Also


Output Zip File Override If you want to enter a file name that is different than the one specified by the selected configuration ID, enter it here.


Email Recipients Override If you want to enter an email recipient that is different than the one specified for email notifications upon file creation.

Profile Data Only and Profile and Appraisal Data

Select whether the process migrates profile data only or both profile and appraisal data.

Running the Migration Process

Click the Run button to initiate the FT_EXTRCT_TP Application Engine process. This process extracts profile data and appraisal data, transforms it into a format readable by Fusion Talent Management and Fusion Workforce Compensation and posts it as a single zip file to the FTP server defined by the specified configuration ID.



Note. The FT_EXTRCT_TP process filters the extracted employee-related talent profiles based on the data filter options defined on the Fusion Integration Installation Options page. It does not use these data filter options, however, when extracting non-employee-related talent profiles or talent profile content data.

Reviewing Transformation Errors Access the Error Summary page (Workforce Administration, Collective Processes, Fusion Integration, Talent/Workforce Compensation, Transformation Error Log).



Error Summary page

Display Criteria

Use the fields in this group box to filter and sort the errors that the system displays in the Error Summary group box.



Integration Type Select whether you want to view errors for Inbound or Outbound processes. If you select Inbound, the Run ID field becomes available.

Note. Although the Error Summary page is documented within the context of sending data to Fusion, it can also be used to view inbound process errors resulting from the retrieval of data from Fusion.

Run ID Enter a specific run ID for which you want to view errors.

Note. This field applies to inbound errors only. It represents the Fusion Workforce Compensation process run ID.

Run Control ID Enter a specific run control ID for which you want to view errors.

Process Instance Enter a specific process instance for which you want to view errors.

Error Type Select the type of errors you want to view. Possible values are:

Unable to load DVM map

Duplicate Content Item Name

Unable to map the DVM value(s)

Employee with multiple jobs

Entire object bypassed

Missing reference object

Multiple Salary Bases

Position override

Reference to object in error

Unable to load XREF map

Unable to map the XREF

Map Name Enter a specific value map for which you want to view errors.



Show Summary by Object Select to group the errors in the Error Summary group box by Integration Object. This check box is selected by default. If you deselect it, the system groups the errors by Map Name and Source Value(s). In addition, deselecting this check box causes the Integration Object and Show Required Fields Only to become unavailable.

Integration Object Select a specific integration object for which you want to view errors.

Show Required Fields Only Select to view only those errors that have a value of Yes in the Required column.

Display Summary Click to display the errors that meet your selected display criteria.

Clear Display Click to hide the Error Summary group box.

Error Summary

This group box displays all errors that meet your selected display criteria when you click the Display Summary button.

Error Type Lists the type of error. Possible values are:

Unable to load DVM map

Duplicate Content Item Name

Unable to map the DVM value(s)

Employee with multiple jobs

Entire object bypassed

Missing reference object

Multiple Salary Bases

Position override

Reference to object in error

Unable to load XREF map

Unable to map the XREF

Map Name Lists the name of the value map associated with the error. If this name is displayed as a link, you can click it to access the Populate Domain Value Maps page.

See Also




Source Value(s) Lists the original source value associated with the error.

Integration Object Lists the integration object associated with the error. The integration object represents the type of data being processed and whether it was outbound or inbound.

Source Record Lists the table that originally contained the data associated with the error.

Required Indicates whether the error row is associated with data that is required in order for the integration object to be sent to Fusion.

If the value for a row is No, the system sets the target value to Null and allows the associated integration object to be sent to Fusion.

Rows with a value of Yes (sometimes referred to as hard errors) prevent the system from sending the associated integration object to Fusion.

Error Count Lists the actual number of errors associated with an error row in the summary.

Error Data Click this link for an error row to access the Error Data page.

Understanding Transformation Errors

The following table provides explanations of the transformation errors that the FT_EXTRACT process can generate.

Transformation Error Explanation

Unable to load DVM map This error type is for future use.

Duplicate Content Item Name Two JPM Catalog Item rows have the same Catalog Item Type (JPM_CAT_TYPE) value. The system bypassed these rows and did not send them to Fusion.

Unable to map the DVM value(s) While loading data into the .DAT output files, the process found no Fusion DVM map values that corresponded to the values set in the Populate Domain Value Maps page for a PeopleSoft object value.

For example, let us assume that the LEGAL_ENTITY_XREF DVM has map values defined for the following companies: PSI, CWB, HX1, and GBI. While loading the .DAT files, the FT_EXTRACT process encounters a row of data with a company value of ACC. The process logs this row of data with the Unable to map the DVM value(s) error type.

Employee with multiple jobs The process encountered an employee with two or more active jobs (PeopleSoft HCM accommodates employees with multiple jobs, but Fusion does not).

Entire object bypassed One of the object rows, for example, Department, Location, or Assignment contained an error that forced the process to bypass it. Fusion cannot load incomplete data, so even if only one of the object rows contained an error, the



Transformation Error Explanation

system bypassed the entire object and all of its rows to avoid sending incomplete data to Fusion.

Missing reference object The process encountered an object that references another object that is missing and/or has not been part of the migration process.

Multiple Salary Bases An employees current active row included two or more compensation rows (PeopleSoft HCM accommodates employees with multiple compensation rows, but Fusion does not).

Termination row updates The process encountered an employee with an action row before a termination row on the same day. In this case, the process sends only the termination row to Fusion.

Position override The process encountered an employee with overridden Position data.

Reference to object in error A current row for an object contained a reference to an object that is to be bypassed and there is a reference to this object in another object.

Unable to load XREF map This error type is for future use.

Unable to map the XREF While loading data into the .DAT output files for an object the process found no GUID for an object referenced by the original object.

Reviewing Error Details Access the Error Data page (click an Error Data link on the Error Summary page).

Reviewing Error Data page This page displays all of the information displayed on the Error Summary page for the error row along with the Source Key Value(s) for the error, which you can use to locate the row in the source record.

Receiving Data from Fusion This section provides an overview of the inbound data process and discusses how to:

Receive compensation data from Fusion.



Delete compensation data.

Review inbound status and transaction errors.

Reviewing inbound errors.

Correcting inbound errors.

Reviewing a summary of integration object changes.

Understanding the Inbound Process The typical process flow for moving data from Fusion Workforce Compensation to PeopleSoft HCM 9.1 is as follows:

1. A Fusion administrator posts a zipped file of the Fusion Workforce Compensation data to the outgoing directory of the FTP server.

2. Fusion Workforce Compensation initiates the READY_FOR_TRANSMISSION asynchronous web service call to notify PeopleSoft HCM 9.1 that the file is available.

3. PeopleSoft HCM 9.1 retrieves the zipped file from the FTP server and extracts the data into staging tables.

4. A PeopleSoft HCM 9.1 administrator uses the Inbound Data Process page to transform and load the data from the staging tables into the application source tables.

Optionally, a PeopleSoft HCM 9.1 administrator can bypass the automatic loading of the file via web service messages and manually load the file using the Inbound Data Process page.

Note. The inbound process loads bonus data into the PS_VC_AWARD table. To pay out these bonuses, however, you must define an ad-hoc Variable Compensation plan in PeopleSoft 9.1 Variable Compensation and set up an integration between PeopleSoft 9.1 Variable Compensation and your PeopleSoft payroll application (PeopleSoft Payroll for North America or PeopleSoft Global Payroll).

See Also

Receiving Compensation Data from Fusion

PeopleSoft HR 9.1 PeopleBook: Manage Variable Compensation, Managing Awards Approval and Payout, Integrating with Payroll Applications

Pages Used to Receive Data from Fusion


Inbound Data Process FT_XTRT_I_RUN_CNTL Workforce Administration, Collective Processes, Fusion Integration, Talent/Workforce Compensation, Receive Comp Data from Fusion

Receive Compensation data from Fusion.




Cancel Compensation Data

FT_XTRT_I_D_RUNCNT Workforce Administration, Collective Processes, Fusion Integration, Talent/Workforce Compensation, Cancel Compensation Data

Delete Compensation data from inbound staging tables.

Inbound Status Monitor FT_CWBOBJ_INSTATUS Workforce Administration, Collective Processes, Fusion Integration, Talent/Workforce Compensation, Inbound Status Monitor

Review inbound status and transaction errors.

Detail

FT_VC_AWARD_DTL

FT_SALARY_DTL

FT_ASGN_AUDIT_DTL

Click the View Error(s) link on the Inbound Status Monitor page.

Review errors associated with an inbound integration object.

Detail

FT_VC_AWARD_SEC

FT_SAL_DETAIL_SEC

FT_ASGN_AUDIT_SEC

Click the View/Update link on the Detail page.

Correct errors to inbound integration objects.

Audit Report

FT_VC_AWARD_SUM

FT_SAL_AUD_RPT

FT_ASGN_AUDIT_SUM

Click the Audit Report link on the Inbound Status page.

Review a summary of integration object changes.

Receiving Compensation Data from Fusion Access the Inbound Data Process page (Workforce Administration, Collective Processes, Fusion Integration, Talent/Workforce Compensation, Receive Comp Data from Fusion).



Inbound Data Process page (file not loaded) This is how the page appears if the data has not yet been loaded to the staging tables for the selected run control ID, either manually, or via web services.

Note. The Process Frequency group box is a standard component of run control pages for Application Engine processes. You will almost always want the Always Process radio button selected.

Configuration Option

Configuration ID Enter an inbound configuration ID. This ID instructs the system how and where to find the posted zipped file containing the Fusion Workforce Compensation data.

See Also


Inbound Zip File Override If you want to enter a file name that is different than the one specified by the selected configuration ID, enter it here.



Process List

Select the check box next to the type of Fusion Workforce Compensation data you want to load into the staging tables. Your options are: Assignment and Salary and Bonus.

Process Action

Only one process action is available: Manual Load File.

Loading the File

Click the Run button to run the FT_LOAD Application Engine process. With the Manual Load File check box selected, this process loads the data from the zipped Fusion Workforce Compensation file to staging tables within PeopleSoft HCM 9.1.

Inbound Data Process page (file loaded)



This is how the page appears if the data has already been loaded to the staging tables for the selected run control ID, either manually, or via web services.


Run ID Displays the unique Fusion process run ID.

Process Status Displays the status of the data retrieved from Fusion Workforce Compensation. Possible values are:

Not Processed

Loaded from File

Transformed

Previewed

Manually Posted

Posted

Plan Name and Plan Description

Displays the name and description of the Fusion Workforce Compensation plan.

Period Name, Period Start Date, and Period End Date

Displays the name of the focal cycle period along with its starting and ending date.

Process List

Indicates the type of compensation data included in the process. This system uses the Logical Business Object (LBO) list included in the inbound web service message to determine which integration objects are included.

Process Action

Transform Data Select to transform the data in the staging tables to a format readable by PeopleSoft HCM 9.1.

Load Data Select to load the data into the PeopleSoft application source tables. If you select this option, the Preview Mode and Commit/Post Mode options become available.

If you select this check box and run the process for data that has not yet been transformed, the system will not load the data and give you and display a message.



Preview Mode Selecting this option enables you to preview and validate the data before actually loading it into the application source tables.

You use the Inbound Status Monitor page to preview and validate the data.

See Also

Reviewing Inbound Status and Transaction Errors

Commit/Post Mode Select to commit to loading the data into the application source tables.

Transforming and Loading Data

Click Run to initiate the FT_LOAD process. Depending on which process actions you select, this process transforms the data in the staging tables and/or loads it into the application source tables.

Deleting Compensation Data Access the Cancel Compensation Data page (Workforce Administration, Collective Processes, Fusion Integration, Talent/Workforce Compensation, Cancel Compensation Data).



Cancel Compensation Data page


Run ID Enter the unique Fusion process run ID for which you are deleting data.

Process Status Displays the status of the data retrieved from Fusion Workforce Compensation.

Plan Name and Plan Description

Displays the name and description of the Fusion Workforce Compensation plan.

Period Name, Period Start Date, and Period End Date

Displays the name of the focal cycle period along with its starting and ending date.

Process List

Indicates the type of compensation data included in the process.



Confirm Action

Select the Delete Data check box to confirm that you want to delete the data from the selected run ID. If you click the Run button while this check box is deselected, the system gives you a warning message and does not allow you to initiate the process.

Deleting Data

Click the Run button to initiate the FT_LOAD process. With the Delete Data check box selected, the system deletes the data associated with the selected run ID from the staging tables.

Note. This process has no effect on data that has already been loaded from the staging tables to the PeopleSoft application source tables.

Reviewing Inbound Status and Transaction Errors Access the Inbound Status Monitor page (Workforce Administration, Collective Processes, Fusion Integration, Talent/Workforce Compensation, Inbound Status Monitor).

Inbound Status Monitor page

Search Criteria

Use the fields in this group box to filter the process runs displayed in the Inbound Status Information group box.

Date From and Date To Use these fields to set a date range for the Fusion periods that you want to display.

Integration Object Select the specific type of data you want to view.

Run ID Enter the unique Fusion process run ID that you want to view.

Plan Name Enter the name of the Fusion Workforce Compensation plan for which you want to view inbound process runs.



Process Status Select the status for which you want to view inbound process runs.

Error Rows Only Select to display only the inbound process runs with errors.

Search Click to display the inbound process runs that match your search criteria.

Clear Click to clear the fields in the Search Criteria group box.

Inbound Status Information

This group box displays the inbound process runs that meet your specified search criteria.

Period Start Date, and Period End Date

Displays the start and end date of the focal cycle period.

Run

integrating hcm 9.1 with fusion talent and workforce compensation

Documents

oracle andor

general use

safe use

oracle parkway

oracle usa

dangerous applications

applicable government

license terms