business process procedures - sap service …sapidp/... · web viewprocedure access the activity...

EHP0 to EHP7 for SAP ERP 6.0

June 2014

English

SAP ERP HCM: Employee Data Integration (C1G)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Building Block Configuration Guide

SAP Best Practices SAP ERP HCM: Employee Data Integration (C1G): Configuration Guide

© SAP AG of 19


Copyright

© 2014 SAP AG or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

© SAP AG of 19


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

© SAP AG of 19


Contents

1 Purpose.................................................................................................................................. 5

1.1 Using the Configuration Guide........................................................................................5

1.1.1 Base Service............................................................................................................5

1.1.2 Upgrading Module....................................................................................................6

1.1.3 Compensation Module.............................................................................................6

1.1.4 Recruiting Module....................................................................................................6

1.1.5 Go-Live Support Module..........................................................................................7

2 Integration Scenario for Employee Data.................................................................................7

2.1 Defining File Path and Name for Storing the Generated Files.........................................7

2.2 Creating Report Variant for Data Extraction....................................................................8

2.3 Specifying Allowed Variants for Delta Extraction.............................................................9

2.4 Defining Name Format for Fields FIRSTNAME and LASTNAME....................................9

2.5 Enhancement of Employee Data Extraction..................................................................10

2.6 Running Extraction of Employee Data and Organizational Data...................................10

2.7 Sync Employee Data with SuccessFactors (with Delta and Inactive Logic)..................12

2.8 Discontinue Data Extraction for Group of Employees...................................................13

2.9 Example of BADI Extension for Employee Data............................................................13

2.9.1 Example for Car License Plate...............................................................................13

© SAP AG of 19


SAP ERP HCM: Employee Data Integration

1 Purpose

This document describes the configuration and customizing steps that have to be done on the SAP ERP HCM system to customize the Integration Scenarios for Employee Data.

1.1 Using the Configuration GuideThis document is set up to support this Packaged Solution. In the following overview, you can find which module is relevant for this document:

Scop

e –

Opt

iona

l Mod

ules

Upgrade Module Compensation Module Recruiting Module

Upgrade the Integration Add-on from SP00/SP01 (File-transfer) to the SP02 Middleware based solutionMigration support for two existing BAdI (max. 4 days effort) No Go-Live support ModuleNo User Defined Options

Pay for Performance IntegrationNo User Defined Options

Recruiting Integration for Internal and External CandidatesNo User Defined Options

Go-Live Support Module:

Help transport to QA & ProdGo-Live support

Cor

e

Base Service

• Kick-off workshops, Identify the requirements and finalize scope options/ work packages, Verify the landscape, Check prerequisites for selected options

• Basic Employee data: Full employee data extraction from HCM to Successfactors

• User Defined Options: Maximum 5 simple enhancements each extracting one single HCM Infotype field for a total of 5 days of development effort, including unit test.

• Workforce Analytics: Prepare the transfer of Analytics Data from HCM to SuccessFactors Workforce Analytics

© SAP AG of 19


1.1.1 Base ServiceFor the Base Service, the following building blocks and parts have to be used:

C1F - SAP ERP HCM: Base Integration Settings

o Defining Authorizations

o Storing Credentials for Transferring Employee Data to Secure Storage

o Defining Package Size for Transferring Employee Data

C1G - SAP ERP HCM: Employee Data Integration

o Creating Report Variant for Data Extraction

o Specifying Allowed Variants for Delta Extraction

o Defining Name Format for Fields FIRSTNAME and LASTNAME

o Enhancement of Employee Data Extraction

o Running Extraction of Employee Data and Organizational Data

o Sync Employee Data with SuccessFactors (with Delta and Inactive Logic)

o Example of BADI Extension for Employee Data

C1H - SuccessFactors: Employee Profile Integration

o All parts

1.1.2 Upgrading ModuleFor the Upgrade Module, please see section 1.1.1 Base Service. The required steps are the same.

1.1.3 Compensation ModuleFor the Compensation Module, the following building blocks and parts have to be used

C1J - SAP ERP HCM: Compensation Integration

o Basic Settings

Storing Credentials for Transferring Compensation Data to Secure Storage

Defining Package Size for Transferring Compensation Data

o Integration Scenario for Compensation Data

Data Transfer SAP ERP to SuccessFactors BizX

All parts

Data Transfer from SuccessFactors BizX to SAP ERP

All parts

C1K - SuccessFactors: Compensation Integration

o All parts

© SAP AG of 19


1.1.4 Recruiting ModuleFor the Recruiting Module, the following building blocks and parts have to be used:

C1M - SAP ERP HCM: Recruiting Integration

o Basic Settings

Import Metadata from SuccessFactors

Storing Credentials for Transferring Compensation Data to Secure Storage

Defining Package Size for Transferring Compensation Data

o Integration Scenario for Compensation Data

C1N - SuccessFactors: Recruiting Integration

o All parts

1.1.5 Go-Live Support ModuleNo parts of this document are relevant for this Module.

2 Integration Scenario for Employee DataIn this section, you customize the Integration Scenarios for Employee Data.

Refer to the relevant section of the Scope Questionnaire for configuration requirements.

2.1 Defining File Path and Name for Storing the Generated Files

UseIn this Customizing activity, you define the physical file path and file name that, in your system, correspond to the logical file path and file name that will be used to store the output file for the extracted Employee Data. This file path and name will appear in the report selection screen for the Employee Data Replication and Synchronization reports. The user will not be able to change this information in the report selection screen.

In the selection screen for the extract report, there is a radio button option to complete the integration “via Middleware”. When this option is selected, a file is not generated and will not be stored to the specified directory.

Procedure1. Access the activity using one of the following navigation options:

Transaction code SPRO

IMG menu Personnel Management Integration Add-On for SAP ERP HCM and SuccessFactors BizX Integration Scenario for Employee Data Define File Path and Name for Storing the Generated Files

© SAP AG of 19


2. In dialog structure Logical File Path Definition

3. Select the logical file path HR_SFI_DIR and choose Assignment of Physical Paths to Logical Path. Choose New Entries.

4. Select the appropriate syntax group and enter the physical path under which the files generated by the data extraction report and the evaluation report are to be stored. Ensure that the path ends with <FILENAME>.

Example:

Field Value (Description)

Logical Path HR_SFI_DIR

Name HR_SFI_DIR

Syntax Group WINDOWS NT (Microsoft Windows NT)

Physical Path D:\your user\sap\your SID\your server\your directory\<FILENAME>

© SAP AG of 19


5. Choose Logical File Name Definition, Cross-Client and select the logical file HR_SFI_DIR, choose New Entries.

6. Enter the physical file name of your choice for this logical file.Choose Save

7. Save all entries before exiting.

To set up the file paths for every system properly, parameter <SYSID> can be used. In this way the distinction between productive data and test data can be made. For further information see the help of the Physical Path Name in transaction FILE.

2.2 Creating Report Variant for Data Extraction

UseIn this activity, you create a variant for the Employee Data extraction report which contains the selection parameters and field mappings required for the integration to SuccessFactors BizX.

Procedure1. Access the customizing using the following navigation option:

Transaction code SE38

© SAP AG of 19


2. Enter report used for data extraction. Only one report may be used.

a. RH_SFI_SYNCHRONIZE_EMPL_DATA – for delta data transfer (recommended for use in the RDS Solution.)

b. RH_SFI_TRIGGER_EMPL_DATA_REPL – for full file transmission

These reports CANNOT be used interchangeably. Select only one, which is used for all Employee Basic Data integration processes. We recommend the delta program RH_SFI_SYNCHRONIZE_EMPL_DATA.

3. Choose Execute.

4. Enter the report period and selection criteria for the employee population to be integrated to SuccessFactors.

5. Enter the desired default settings.

6. Complete the field selection mappings for data elements to be included in the integration by choosing a value from each drop down. Use the check box to if the field is mandatory for extraction, while the greyed out checkboxes for mandatory data cannot be maintained.

7. After all extraction parameters are defined, choose Save.

8. Enter a variant name and description and choose Save.

After defining the variant in step 2.3Specifying Allowed Variants for Delta Extraction, the variant can be used when synching employee data.

These steps must be completed identically in each system where the extract reports are executed (Development, Test, Production, and so on.)

There may be one variant for all German employees and another variant for all American employees. You may also create a variant for individual or groups of Organizational Units or Personnel Areas.

2.3 Specifying Allowed Variants for Delta Extraction

UseIn this Customizing activity, you define which extraction variants which will be available for use in the report Sync Employee Data with SuccessFactors for the Delta and Inactive Processes (RH_SFI_SYNCHRONIZE_EMPL_DATA). A variant MUST be specified at runtime for proper functioning of the report. Only those variants identified in this configuration step will be available for selection by the user.

Procedure1. Access the customizing using the following navigation:

IMG menu Personnel Management Integration Add-On for SAP ERP HCM and SuccessFactors BizX Integration Scenario for Employee Data Specify Allowed Variants for Delta Extraction

© SAP AG of 19


2. Choose New Entries

3. From the dropdown, select the appropriate variant(s) which are permissible for use in the program Sync Employee Data with SFSF (RH_SFI_SYNCHRONIZE_EMPL_DATA.

4. Save your entries

2.4 Defining Name Format for Fields FIRSTNAME and LASTNAME

UseIn this Customizing activity, you can specify by country the format for extraction of employee data for the fields FIRSTNAME and LASTNAME to be used in the Employee Data extraction reports.

The fields FIRSTNAME and LASTNAME are mandatory fields in SuccessFactors BizX.

If the format for the FIRSTNAME and LASTNAME has already been defined as part of the existing HCM implementation, this configuration step is not needed. If no specific name format is defined for the HCM implementation, the extract program will default to use of PA0002-VORNA and –NACHN. Otherwise, you may define a name-format specific for the integration using the name formats:

Field FIRSTNAME: 71

Field LASTNAME: 72

Example:

Format Prefix Name Form. Seq.no. Field name Conversion

71 0002 0 1 VORNA

72 0002 0 1 VORSW

72 0002 0 2 NACHN

© SAP AG of 19


Procedure1. Access the data using the following navigation option:

IMG menu Personnel Management Integration Add-On for SAP ERP HCM and SuccessFactors BizX Integration Scenario for Employee Data Define Name Format for Fields FIRSTNAME and LASTNAME

2. Enter the country grouping.

3. Choose New Entries.

4. Enter the Format.

5. Enter the Prefix (Infotype).

6. Enter the Name Format.

7. Enter the Sequence.

8. Enter the Field Name.

9. Enter the conversion for the field editing (Refer to the SAP Help for the specific values for this entry).

10. Save your entries.

2.5 Enhancement of Employee Data Extraction1. Access the data using the following navigation option:

IMG menu Personnel Management Integration Add-On for SAP ERP HCM and SuccessFactors BizX Integration Scenario for Employee Data Enhance Extraction for Employee Data

This customizing refers to adding custom fields to the Employee Data extract report. You can supplement the extraction of employee data beyond using the fields CUSTOM01 – CUSTOM15 by adding customer-specific fields. A detailed description is provided with the IMG activity documentation. Refer to Chapter ‘2.9 Example of BADI Extension for Employee Data’ as the method ‘GET_VALUE_FOR_ENHANCED_FIELD’ is also available to define the data retrieval for customer-specific fields.

2.6 Running Extraction of Employee Data and Organizational Data

UseIn this Customizing activity, you schedule a background job for the extract report to regularly extract data from the SAP ERP system.

There are two reports available to send employee data to SuccessFactors.

Extraction of Employee Data for SuccessFactors (RH_SFI_TRIGGER_EMPL_DATA_REPL)

This report extracts a full data file for all selected employees each time the report is run. This is not the report used for the RDS solution

Sync Employee Data with SuccessFactors (with Delta and Inactive Logic) (RH_SFI_SYNCHRONIZE_EMPL_DATA)

© SAP AG of 19


This report is used to perform a delta data extraction. During the initial run for an employee, a full record is extracted. During each subsequent run, the report extracts only the employees whose data has changed compared with the last run of the report. The report also ensures that employees who are no longer contained in the selection area receive the status Inactive. (for example, because they switch to an enterprise area for which integration with SuccessFactors is not planned).

For more information you may refer to the help documentation for the individual reports.

You cannot use both reports interchangeably.

ProcedureIn this activity, a background batch job is created and scheduled to run the extract report.

This step must be executed in every environment in the landscape (Development, Test, Productive, and so on.)

1. Access the data using one of the following navigation options:Transaction code

SM36

IMG menu Personnel Management Integration Add-On for SAP ERP HCM and SuccessFactors BizX Integration Scenario for Employee Data Run Extraction of Employee Data and Organizational Data

© SAP AG of 19


2. Execute the IMG line.

3. Define the job name, job class, and if necessary, execution server and spool recipient.

4. Choose Start Condition

5. For a scheduled periodic job:

a. Choose Date/Time.

b. Enter the desired execution date.

c. Choose Periodic job check box.

d. Choose Period Values and select the desired frequency.

e. Choose Save.

6. Choose Step to specify the program to be executed in the batch job,

a. Choose the integration program name RH_SFI_SYCHRONIZE_EMPL_DATA and the desired variant:

b. Choose Save.

If you are using the report RH_SFI_SYNCHRONIZE_EMPL_DATA, you will need to specify the allowed extraction variants in configuration. Ensure that you have performed the Customizing activity Specify Allowed Variants for Delta Extraction in section 2.3

If you have already extracted data using one of the reports, we recommend that you do not change the settings used for the report or the variant used for the following reasons:

The data extracted from the ERP system forms the basis for workflow, authorizations, and reporting in SuccessFactors BizX. If you change the settings for a repeated extraction of data, you may generate new objects in SuccessFactors BizX and may, for example, need to modify authorizations accordingly.

2.7 Sync Employee Data with SuccessFactors (with Delta and Inactive Logic)

UseThis report extracts data from the SAP ERP system so that it is available in SuccessFactors Business Execution (BizX) for Talent Management processes.

During each run, the report extracts only the data for the selected employees that has changed compared with the last run.

Procedure

This step has to be executed in every system (Development, Test, Productive, and so on.)

1. Start the program by using the following transaction:

Transaction code HRSFI_SYNCH_EMP_DATA

© SAP AG of 19


2. Select the desired Reporting Period. You can specify the current day (Today) or any key date or period for which the data is to be extracted. Default is Today.

3. Select the selection criteria at the section Selection Criteria

You specify for which employees the data is to be extracted. You can show other selection fields that the report class HRSFI_SY provides.

The default entry for the employment status is 3. This means that the report selects only employees for whom the employment status is Active. We recommend that you retain this setting since SuccessFactors BizX can only process employee data that has been transferred with the status Active at least once. Initially, you cannot transfer any employees with a status other than Active to SuccessFactors BizX. Employees will only be transferred to SuccessFactors BizX as Inactive if you have already transferred data for them as active employees and their employment status changes.

4. Default Settings. Make the following settings:

a. Do NOT enter the Extraction Variant here. The extraction variant will be automatically filled once the variant of the report is saved.Do NOT activate the field Forced Synchronization. This field should only be used when the program runs manually.

b. Choose the option Middleware and not the option File Transfer with Path.

c. Add an E-mail address of choice.

d. Choose an Extraction Language of choice.Caution: once you have extracted data in a particular language, we strongly recommend that you do not change the extraction language.

e. Activate the Field Log Error Messages only. In that case the output logging is reduced in size and Succes and Warning messages are not shown.

5. Define which Fields you want to use to extract the data.

6. Save the selections into a variant by using the Save button or use <Cntr+S>.

7. Give the variant a desirable Variant name and Description. The variant name should be identical as set up in the paragraph 2.2.

8. Save the variant by using the Save button or use <Cntr+S>.

2.8 Discontinue Data Extraction for Group of Employees

IMG menu Personnel Management → Integration Add-On for SAP ERP HCM and SuccessFactors BizX Integration Scenario for Employee Data Discontinue Data Extraction for Group of Employees

© SAP AG of 19


Use

Use this report very carefully. It is used to clean-up the table used for delta-handling and inactivates the chosen variant for all future use. Review the documentation for the report RH_SFI_WITHDRAW_VARIANT.

In this customizing activity, you will execute the report Discontinue Data Sync (RH_SFI_WITHDRAW_VARIANT) with SuccessFactors BizX for a group of employees. To set all of the employees that are contained in the selection extraction variant of the report Sync Employee Data (RH_SFI_SYNCHRONIZE_EMPL_DATA) to the status of Inactive in SuccessFactors.

For example, this is useful if you want to exclude a group of employees for which you have previously transferred data to SuccessFactors BizX from the data transfer in future. Such as if you no longer want to have information transferred for a specific Org Unit or Personnel Area.

2.9 Example of BADI Extension for Employee Data2.9.1 Example for Car License Plate

1. Open Customizing.

Open the Customizing with transaction /nSPRO and hereafter the following IMG activity:

IMG menu Personnel Management Integration Add-On for SAP ERP HCM and SuccessFactors BizX Integration Scenario for Employee Data Business Add-Ins (BAdIs) BAdI: Replication of Employee Data

© SAP AG of 19


2. Creating all development objects

Create an implementation by ticking the Create icon on the “BAdI Implementation” window:

Afterwards, an information message is displayed that can be closed. In the second window, the “Enhancement Implementation”, “Short Text” fields must be defined as follows: Enhancement Implementation: ZHRSFI_CAR_LIC_PLATE Short Text: < Define a useful description >

The next screen requests to define the “BAdI Implementation” as follows: BAdI-Implementation: HRSFI_CAR_LIC_PLATE Implementation Class: ZCL_HRSFI_CAR_LIC_PLATE

When defining a meaningful name in Z-namespace, you should consider to use the prefix “ZCL_” for the class-name of field “Implementation Class” (for naming convention purposes). Consider the following example values in the table to complete that window:

Column ValueBAdI Implementation HRSFI_CAR_LIC_PLATE Implementation Class ZCL_HRSFI_CAR_LIC_PLATE BAdI Definition HRSFI_B_EMPL_DATA_REPLICATION

(out of select list)

© SAP AG of 19


After selecting the green check mark, all relevant development objects are created.

3. Individual source code

Shortly after the creation of the development objects is done successfully, the customer-specific source code can be implemented. Once the Enhancement Implementation ZHRSFI_CAR_LIC_PLATE is opened, the method IF_HRSFI_EMPL_DATA_REPLICATION~GET_CUSTOM01 needs to be opened by a double-click.

On the next screen, the following source code can be implemented to export the License Plate data:

METHOD if_hrsfi_empl_data_replication~get_custom01.

DATA: BEGIN OF ls_p0032, pernr TYPE persno, kfzkz TYPE kfzkz20, END OF ls_p0032.

SELECT SINGLE * FROM pa0032 INTO CORRESPONDING FIELDS OF ls_p0032 WHERE pernr = iv_pernr.

IF sy-subrc = 0. rv_value = ls_p0032-kfzkz. ENDIF.

ENDMETHOD.

The Car License Plate is loaded out of Infotype 32/database table pa0032 and is then transferred to the exporting parameter rv_value, which is the result of this method.

4. Testing the implementation

By running transaction /nSA38 and then program RH_SFI_SYNCHRONIZE_EMPL_DATA , a selection screen is displayed. On this screen, the option “Own implementation” has to be selected out of the dropdown list “Custom 1”.

After the report was started by choosing F8, a log is displayed that indicates the success of this program.

© SAP AG of 19

business process procedures - sap service …sapidp/... · web viewprocedure access the activity...

Documents