business process proceduressapidp/... · web view2014-05-05 · type style description example...

EHP0 to EHP7 for SAP ERP 6.0

June 2014

English

SuccessFactors: Employee Profile Integration (C1H)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Building Block Configuration Guide

SAP Best Practices SuccessFactors: Employee Data Integration (C1H): Configuration Guide

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 13


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 13


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...........................................................................................6

2 Prerequisites........................................................................................................................... 7

3 User Settings.......................................................................................................................... 7

3.1 API URL.......................................................................................................................... 7

3.2 Enable Webservices SFAPI............................................................................................7

3.3 Data Model Configuration................................................................................................7

3.4 Creating SuccessFactors API user..................................................................................8

3.4.1 Use........................................................................................................................... 8

3.4.2 Use........................................................................................................................... 9

3.4.3 Procedure................................................................................................................. 9

3.5 SuccessFactors – Set API Login Exceptions...................................................................9

3.5.1 Use........................................................................................................................... 9

3.5.2 Procedure................................................................................................................. 9

3.6 SuccessFactors Proxy Settings.......................................................................................9

3.6.1 Use......................................................................................................................... 10

3.6.2 Procedure...............................................................................................................10

© SAP AG of 13


SuccessFactors: Employee Data Integration

1 Purpose This document describes the steps that have to be done on the SuccessFactors system to customize the Integration Scenarios for Employee Data.

1.1 Using the Configuration Guide This 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 13


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

© SAP AG of 13


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 Data 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 13


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 PrerequisitesBefore implementing employee data integration in SuccessFactors you will need the following:

1.Access to SuccessFactors provisioning

2.Administrator access to SuccessFactors tenant

3 User Settings

3.1 API URL1. Access the activity using one of the following navigation options:

Transaction code

N/A

Web access

https://partners.successfactors.com/productcentral/PSDocuments/SFAPI_Functional_Guide.pdf

© SAP AG of 13




2. Find the correct API endpoint URL for the customer system

3. This URL is used in the SAP Netweaver PI settings.

See SFAPI Endpoint URLs for a list of the URLs per datacenter. Enter the /sfapi/v1/soap version (for SOAP version 1.1).

For example: https://api.successfactors.eu/sfapi/v1/soap

3.2 Enable Webservices SFAPI1. Access the activity using one of the following navigation options:

Transaction code N/A

Web access Provisioning Tool Company Settings Web Services

© SAP AG of 13


2. In the section, enable the ‘SFAPI and SFAPI Adhoc Feature‘ by choosing the checkbox.

3. Choose save.

3.3 Data Model ConfigurationIf you have already implemented configuration guide (C1I) the following steps are not required.

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


Web access Provisioning Tool Succession Management Import/Export Data Model

© SAP AG of 13


2. Select Import radio button

3. Use the Browse button to search for the appropriate .xml file. You should load the C1H_succession-data-model.xml file.

4. Select Submit to upload the C1H_succession-data-model

5. A message “templates have been uploaded and saved” will appear showing successful uploading

SAP designed the integration based on the SuccessFactors file based integration, and depends on the maximum values advertised in our file import documentation. This integration requires that the maximum length values match the fields being imported from SAP.

The xml template delivered comes with all the max lengths set for the standard elements

Ensure all the "max-length" attribute value of the standard elements matches the maximum characters from the MAX CHRS values in the PM Data Integration document accessed via the partner portal –

https:// connect.successfactors.com/partnerportal/Documents/PM+Data+Integration.docx

3.4 Creating SuccessFactors API user3.4.1 UseThis step is required to set up a API user in order for the integration scenarios between SAP ERP HCM and SuccessFactors to be executed using SAP Netweaver (NW) PI connections. Once the API user is created it should be passed onto your SAP NW PI consultant who will require this to complete the SAP NW PI configurations.

1. Log on to the SuccessFactors Provisioning

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


Web access Provisioning Company Settings

Create a user account that will be used by the SAP system to connect to the SuccessFactors API.

3. Enter the following fields:

Admin Username Value = sap_api_user

Admin Password Enter password that is suitable according to your company policy

Admin First Name Enter the first name for the Admin User

Admin Last Name Enter the last name name for the Admin User

Admin Email Enter the email address

© SAP AG of 13

https://connect.successfactors.com/partnerportal/Documents/PM+Data+Integration.docx

https://connect.successfactors.com/partnerportal/Documents/PM+Data+Integration.docx


4. Select the “Create Admin” button to create the API user.

Suggested naming conventions are: UserId: "sap_api_user". Username "sap_api_user".

Create a strong password for this account, and the following information will need to be entered in basic settings section of the SAP Integration configuration

SuccessFactors - API Security Access Set up

3.4.2 UseThis section describes the set up steps necessary to grant security access to the sap api userid created in the step above.

Please note that once Role Based Permissions (RBP) is activated in SuccessFactors Provisioning then the API user role will need to be updated as per the RBP role set up requirements.

The configuration steps might depend on the Packaged Solution you are implementing. Therefore please check your Prerequisite Matrix. The activation of RBP is covered in configuration guide (FC7).

3.4.3 Procedure1. Log on to the SuccessFactor as Admin

2. Navigate to Admin Tools > Goto Set User Permissions > SFAPI Login Permission> Manage SFAPI Login Permission

3. Search for the SAP API User created the step above

4. Select checkbox for Select All

5. Select Grant Permissions

6. Navigate to Admin Tools > Goto Set User Permissions > Default User Permissions

7. Under Report Permissions, select Reports Permission

8. Under SFAPI Retrieve Job Applicant Permission, Select SFAPI Retrieve Job Applicant Permission

9. Under Run Reports, Select Run All Reports, Run Recruiting V2 Report, Run Recruiting V2 Secured Report, Run Employee Profile Report, Run Compensation Planning Report

10. Select the Save Settings button

11. Navigate to Admin Tools > Recruiting>Recruiting Permissions

12. Select the option Manage recruiting permissions through individual users and select the Search Users button

13. Select the SAP API User created and grant permissions for all SFAPI functionalities (18 total)

3.5 SuccessFactors – Set API Login Exceptions3.5.1 UseThis section describes the set up steps necessary to ensure the password for the API user does not expire

3.5.2 Procedure1. Log on to the SuccessFactor as Admin user

© SAP AG of 13


2. Admin Tools > Company Settings>Password & Login Policy Settings > Set API Login Exceptions > Add > Set the following settings

3. Username - The API user

4. Maximum password age (days) – Set to -1 days

5. IP address restrictions – Designated IP address(es) or address range from which the API user is being accessed from. This is can be used to ensure that the API user is only called from designated sources.

3.6 SuccessFactors Proxy Settings 3.6.1 UseThis section describes the set up steps necessary to active the proxy management in SuccessFactors

3.6.2 Procedure1. Log on to Provisioning for the company instance

2. Select checkbox for Enable Proxy Feature

3. Choose Save.

4. Log on to the SuccessFactor as Admin user

5. Navigate to Admin Tools > Manage Employees Porlet, Select Proxy Management

6. Under Change the proxy settings for the company select checkbox for Enable Advanced Proxy Management (Proxy Now and Proxy Import)

7. Select the Save Proxy Settings button

© SAP AG of 13