RDS_HCM_SFSF_ERP607V3_Quick_Guide_EN_XX.pdf

EHP1 to EHP7

for SAP ERP 6.0

PI 7.11

to PI 7.40

April 2014

English

Quick Guide for SAP ERP HCM Integration to SuccessFactors rapid-deployment solution

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany

SAP Best Practices Quick Guide for Implementing the SAP ERP HCM Integration for SuccessFactors RDS

SAP AG Page 2 of 20

Copyright

2013 SAP AG. 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.

Microsoft, Windows, Excel, Outlook, and PowerPoint

are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or

registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web

Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects Explorer,

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.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their

respective logos are trademarks or registered trademarks of SAP France in the United States and in other countries.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. 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 AG Page 3 of 20

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.

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


SAP AG Page 4 of 20

Contents 1 Solution Overview .................................................................................................. 6

2 System Setup & Preparation System Administrator ........................................... 6

2.1 Install SAP PI or SAP HCI & SAP ERP HCM 6.0 ................................................. 6

2.1.1 Release and Support Package Level ..................................................................... 6

2.1.2 Required SAP Components .................................................................................... 7

2.2 SuccessFactors - creation of Admin User ............................................................. 8

2.3 SuccessFactors - Admin User Security Access Set up ......................................... 9

2.4 SuccessFactors Additional Permissions Required .............................................. 10

2.5 SAP Notes and Messages................................................................................... 10

3 Creating User for Activation of SAP Best Practices Content .............................. 12

3.1 General Client Settings ........................................................................................ 13

3.1.1 SAP Software Change Registration (SSCR): Developer Key .............................. 13

3.1.2 Create RFC-Connection on ERP system ............................................................. 13

3.1.3 Create RFC Destinations on PI system ................................................................ 14

3.1.4 Optional: Maintain Business System .................................................................... 15

3.1.4.1 Import Business System from SLD ....................................................................... 15

4 Getting the Business Content for Activation ........................................................ 16

4.1.1 Getting the Installation Data Files ......................................................................... 16

4.1.2 Getting the Configuration Guides ......................................................................... 16

4.1.3 Activation of Scenarios ......................................................................................... 16

5 Evaluate Business Content / Processes Business Consultant ........................ 18

5.1 Review of Business Processes ........................................................................... 18

6 Select the SAP Solution Manager Template ....................................................... 18

7 Security Aspects - System Administrators .......................................................... 19

7.1 User Administration and Authentication .............................................................. 19

7.2 Roles Management ............................................................................................. 20


SAP AG Page 5 of 20

Quick Guide to Implementing the SAP ERP HCM Integration to SuccessFactors rapid-deployment solution

Purpose This quick guide provides step by step information you need to implement the SAP ERP HCM Integration to SuccessFactors rapid-deployment solution.

Before proceeding with this document you must have,

Finalized technical prerequisites

Required resources available (see involved roles)

This document does not provide a general overview and explanations of SAP Best Practices. For more information about content and positioning, see the related documentation and positioning of the content package.

This document is intended for the following project roles which already have a sound knowledge of SAP Best Practices, including the tools and documentation:

System Administrators and Basis Consultants

o System Set up & Preparation incl. troubleshooting.

Activation/Implementation Consultants (can be also Basis Consultants)

o Activation/Implementation of Business Content / Processes

Business Consultants

o Evaluate Business Content / Processes incl. troubleshooting

o FAQ and further information for extended usage the package

The following sections are assigned to the roles required for the successful installation of SAP ERP HCM Integration to SuccessFactors rapid-deployment solution

This RDS provides details of the requirements in Success Factors tenants, necessary for the integration. It assumes, however, that the SuccessFactors tenants have already been configured for the respective scenarios.

Examples of how to set up a tenant for a scenario can be found in SAP Best Practices for SuccessFactors Recruiting with SAP ERP HCM.

.


SAP AG Page 6 of 20

1 Solution Overview

SAP ERP HCM Integration to SuccessFactors rapid-deployment solution.

Is based on SAP PI 7.11 to PI 7.40.

Provides an accelerated deployment of the required configuration settings.

SFSF Talent Management Suite based on the basic employee data in the integration add on (integration add-on 1.0 for SAP ERP Human Capital Management and SuccessFactors Business Execution)

SFSF Compensation Management based on the developed interfaces in the integration add-on (integration add-on 1.0 for SAP ERP Human Capital Management and SuccessFactors Business Execution)

SFSF Recruiting based on the developed interfaces in the integration add-on (integration add-on 2.0 for SAP ERP Human Capital Management and SuccessFactors Business Execution)

SFSF Workforce analytics with data from HCM exported via the integration add-on with the file based interface as implemented in integration add-on 1.0 for SAP ERP Human Capital Management and SuccessFactors Business Execution. Automation of upload via PI.

2 System Setup & Preparation System Administrator

2.1 Install SAP PI or SAP HCI & SAP ERP HCM 6.0 Prior to installing and activating an SAP rapid-deployment solution package (SAP RDS package), the target SAP Application Server (AS) must be installed with the Support Package Stack (SPS), specified in this section and the SAP Notes as specified in detail in section SAP Notes and Messages in this guide.

2.1.1 Release and Support Package Level The deliverables of SAP Best Practices packages were developed and tested in a system landscape with specific release and support package (SPS) level. If the SPS level in your system is different, there may be errors during the activation. You may be able to perform the activation activities manually using the configuration guides, but errors may still occur.

For cases when the support package levels do not match the SAP Best Practices requirements, especially when HIGHER support package levels are implemented, only LIMITED SUPPORT can be provided

Make sure that your system meets the minimum SPS level requirements. In case

your system has an exceptional SPS level compared to the SAP Best Practices requirements, only LIMITED SUPPORT can be provided.

If you need a higher SPS level in your system, for example because of additional functionality, FIRST import and activate the SAP Best Practices package on the SPS levels as mentioned below, THEN update your system to the target SPS level.

The support package levels relevant for SAP ERP HCM Integration for SuccessFactors rapid-deployment solution are listed together with the required components in chapter 2.1.2.


SAP AG Page 7 of 20

Receiving the Software at the Correct SP Level

For delivery of the software, an installation number and a corresponding license agreement are required. An S-USER is required to order software in the Software Catalog or download from SAP's Software Distribution Center within SAP's Service Marketplace (SAP's SWDC in SMP). You can only order unrestricted SAP software. Contact the SAP contract department to ask for a physical shipment or create a customer message on component XX-SER-GEN-CONTR.

For downloading SPSs, use the Maintenance Optimizer within your SAP Solution Manager. You can also select relevant SPs manually one-by-one via SAP's SWDC in the SMP:

https://service.sap.com/swdc Download Support Packages and Patches Support

Packages and Patches - Browse our Download Catalog SAP Application Components SAP NETWEAVER

Only the current Service Release (SR) is delivered to SAP customers / partners via SAP's SWDC in SMP and standard delivery (for example, Software Catalogue). If you encounter the situation that the required SPS for correct SAP BP packages activation is based on SPS level LOWER than the current SR, the request for the necessary SPS is handled via a customer message. For details, see the SAP Note 925690 - Standard Ordering Procedures for SAP Software (https://service.sap.com/sap/support/notes/925690).

2.1.2 Required SAP Components

According the existing landscape SAP ERP HCM Integration for SuccessFactors rapid-deployment solution on SAP NetWeaver PI 7.3 Application server. You can find detailed information for SPS definition for the SRs of SAP NetWeaver, in SAP Note 789220 - Support Package levels for NetWeaver installations/upgrades.

The table lists the software required to implement and run the solution. This table should be interpreted as follows for these products :

(1) SAP ERP 6.0: one of the entries in the table.

(2) SAP Netweaver Process Integration one of the entires in the table or SAP HANA Cloud Integration.

(3) If you use SAP NetWeaver PI as middleware, your SAP NetWeaver PI system must have the Support Package level stated in SAP Note 1838921. In your SAP ERP system, you also need to define the access data for the System Landscape Directory (SLD) in the application Maintain SLD Access Data (transaction SLDAPICUST). For more information, look for Connecting to the System Landscape Directory in the documentation of SAP NetWeaver at http://help.sap.com.

Product Product Version Component Comments

SAP Solution Manager

SAP Solution Manager 7.1

Not applicable Optional for Solution Manager Template

SAP NetWeaver Process Integration

SAP NetWeaver Process Integration 7.1 Including Enhancement Package 1, SPS

Process Integration, Abap & Java stack (Dual Stack implementations)

(2), (3)


SAP AG Page 8 of 20

12 or higher

SAP Netweaver Process Integration

SAP NetWeaver PI 7.3 SPS 10 or 7.31 SPS 09 or 7.40 SPS 04

XI TOOLS 7.30 / 7.31 / 7.40, Java Stack only

(2), (3)

SAP HANA Cloud Integration

Process Integration

(2), Hosted by SAP Cloud Managed Services

SAP ERP 6.0 SPS: 15 (02/2009) or higher

EA-HR 600, SP 38

(1)

EHP2 FOR SAP ERP 6.0

SPS: 05 (02/2009) or higher

EA-HR 602, SP 17

(1)



EA-HR 603, SP 12

(1)



EA-HR 604, SP 05

(1)

EHP4 FOR SAP ERP 6.0 /NW 7.01


EA-HR 604, SP 05

(1)



EA-HR 605, SP 05

(1)



EA-HR 606, SP 01

(1)


SPS:01 or higher EA-HR 607, SP13 (1)

Integration add-on for SAP ERP HCM and SuccessFactors BizX 2.0

SUCCESSFACTORS HCM INTEGR 2.0

SFIHCM01 600 SP06, SFIHCM02 600 SP02, XI Content SFIHCM01 600, XI Content SFIHCM02 600

SFIHCM02 600 requires SFIHCM01 600 SP06 as pre-requisite.

See also SAP Note 1708986

SuccessFactors Business Execution Suite 1402

Usually required software components and SP levels are downloaded using the Maintenance Optimizer of SAP Solution Manager.

2.2 SuccessFactors - creation of Admin User

Use

In order to execute the configuration in an SuccessFactors instance an Admin is required.


SAP AG Page 9 of 20

Procedure

1. Log in to SuccessFactors Provisioning.

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

Transaction code N/A

Web access Provisioning --> Company Settings

3. Enter the following fields:

Admin Username Value = Admin

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 Admins email address

4. Select the Create Admin button to create the Admin user.

2.3 SuccessFactors - Admin User Security Access Set up

Use

This section describes the set up steps necessary to grant security access to the administrator userid.

Please note that once Role Based Permissions (RBP) is activated in SuccessFactors Provisioning then the Admin user role will need to be updated.

Procedure

Administrative Privilege 1. Navigate to Admin Tools > Manage Employees portlet 2. Goto Set User Permissions > Administrative Privileges 3. In the Username input box input the username of your administrator userid and press

search users 4. Click the checkbox next to the administrator user id 5. Ensure that the following permissions checkboxes are selected.

a. Manage Users b. Manage Security c. Form Template Administration d. System Properties e. Managing Documents f. Dashboards/Reports g. Managing Recruiting h. Integration Tools

6. Press the Grant Permission button to save your changes Manage Recruiting Administration

7. Navigate to Admin Tools 8. Goto Recruiting > Manage Recruiting Administration


SAP AG Page 10 of 20

9. Click on the Manage recruiting administration through individual users hyperlink 10. In the Username input box input the username of your administrator userid and press

search users 11. Click the checkbox next to the administrator user id 12. Ensure that the following permissions checkboxes are selected.

a. Manage Recruiting Sites b. Manage Offer Letter Templates c. Edit Applicant Status Configuration

13. Press the Grant Permission button to save your changes Default User Permissions

14. Navigate to Admin Tools 15. Under Manage Employee portlet goto Set User Permissions > Default User

Permissions 16. Ensure that the following permissions checkboxes are selected.

a. System Properties Permission > Picklists b. Managing Security> Proxy Management c. Reports Permissions >Reports Permission d. Create Report> Select all boxes

17. Scroll down to the bottom of the screen and press the Save Settings button

2.4 SuccessFactors Additional Permissions Required

Use

In order to execute the process integration scenarios for compensation and recruiting certain permissions will need to be added to your existing security roles. This section provides the necessary permissions that are to be added.

Procedure

Compensation Process Integration Scenario:

The Planner and Manager roles require planning permissions in order for the launched forms to be available within the inbox . This can be set under Admin tools> Compensation> Manage Compensation Planner Permission

The Manager (or Planner) role must have compensation user permissions and manage compensation permissions

Recruiting Integration Scenario:

The Recruiter role must have recruiting user permissions and manage recruiting permissions

In order for the Recruiter to see the live profile access to employee view>profile is required

The Manager role must have recruiting user permissions and manage recruiting permissions

2.5 SAP Notes and Messages If issues become apparent after shipment of this SAP Best Practices Package (and hence of this document), an SAP Note exists to document how to solve the issues.

Before you start the activation of the related rapid-deployment solution, check the latest version of the SAP solution note below to obtain updates and corrections for problems that have not become apparent until after shipment.



SAP Note #

Description Component Area Remark

1837880 SAP ERP HCM Integration for SuccessFactors rapid-deployment solution

SV-RDS-PI General Info

Always check the SAP Note of the SAP Best Practices package for updates on the implementation

The following SAP Notes must be implemented (if not stated otherwise in the SAP Note mentioned above):

SAP Note #


669669 Update the SAP Component Repository in SLD

n.a. Activation Update the Component Repository Content (CR Content) in the System Landscape Directory (SLD). Follow the instructions in the note.

836200 SAP NetWeaver 7.0: Importing Process Integration Content

n.a. Activation The software components XI CONTENT SAP APPL 6.05 SP 07 and SAP BASIS 7.3 have to be imported into the PI Enterprise Service Repository.

1578675 PI SOAP Axis receiver channel over HTTP proxy

n.a. Activation Implement via SNOTE

1712309 RH_TEXT_GET_P0001: Texts determined only in logon

SAP_HRRXX

Activation Implement via SNOTE

1824818 Error in transfer of country SFIHCM02 Activation Implement via SNOTE

1829596 SFSF integr.: Various errors in transaction HRSFI_RCT_HIRE

SFIHCM02 Activation Implement via SNOTE



SAP Note #


1911069 Workaround for issues launching the PI tools with Java 7

BC-XI-IBF Activation Use of Java 7

3 Creating User for Activation of SAP Best Practices Content

Use

In this activity, you create a user to perform the steps in the configuration guides.

Procedure

1. Access the activity using the following navigation option:

SAP Menu SAP NetWeaver PI Start page -> User Management

2. Choose Create User.

3. On the General Information tab enter Logon ID, Password and Last Name.

4. On the Assigned Roles Assign the following roles to the user:

Role Description

SAP_XI_MONITOR_J2EE

SAP_XI_ADMINISTRATOR_J2EE

SAP_SLD_CONFIGURATOR Configurator Role

SAP_XI_CONTENT_ORGANIZER_J2EE

SAP_SLD_DEVELOPER Developer role

SAP_XI_CONFIGURATOR_EXT_J2EE

SAP_XI_CONFIGURATOR_J2EE

SAP_XI_DEVELOPER_J2EE

SAP_SLD_ORGANIZER Organizer Role

5. Choose Save.

Result

A user to activate SAP Best Practices content has been created.

Above created users have Administrator roles assigned now, which gives them full authorization rights. If this authorization is not applicable to your project you have to restrict the rights of these users according to your companys security policy.



3.1 General Client Settings

3.1.1 SAP Software Change Registration (SSCR): Developer Key

Use

The user ID for activation has to be registered as a developer on SAP Service Marketplace (SAP Software Change Registration (SSCR)). For more information, see SAP Note 86161. The SSCR developer key is required because the user ID for activating the SAP rapid-deployment solution content creates and changes objects from the customer name range during the activation process. If the SAP content activation user is not registered as a developer, the automated activation process encounters errors.

Procedure

1. Log on to SAP Service Marketplace at http://service.sap.com/sscr.

2. The SAP Software Change Registration (SSCR) start page provides detailed documentation on how to obtain the SSCR developer key.

An SSCR developer key is a 20-digit key that is queried when an SAP ERP user tries to create or change an object from the customer name range FOR THE FIRST TIME. The message requesting the developer key appears once for each SAP ERP user; if registration is successful, this SAP ERP user is no longer prompted to enter a developer key. The SSCR developer key is generated from the installation number of the installation in question and the SAP ERP user name.

3.1.2 Create RFC-Connection on ERP system

This step has to be executed by an SAP Basis Consultant if an SAP ERP 6.0 system is used as backend system to connect a PI 7.3 system.

Use

The purpose of this activity is to define an RFC destination to the Integration Engine of the PI system.

Procedure

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

Menu Tools Administration Network RFC Destinations

Transaction Code SM59

2. Choose Create.

3. Enter the RFC Destinations and the Connection Type.

RFC Destination Description Connection Type

XI_INTEGRATION_ENGINE_

e.g. XI_INTEGRATION_ENGINE_X73

H

The system ID is a three-letter word.

4. On Tab Technical Setting make the following entries.

Field name Description User action and values




Target Host

Path Prefix /sap/xi/engine/?type=entry

Service No. Port or number of the PI system

e.g. 53300

5. OnTab Logon & Security check the radio buttons SAP RFC Logon and Do not send Logon Ticket and make the following entries


Client Backend client number of the PI system

e.g. 001

User UserID to access the Integration Engine of the PI system

e.g. PIAPPLUSER

Password

6. Choose Save (Ctrl+S).

7. Choose Connection Test (Ctrl+F3) to test the connection.

3.1.3 Create RFC Destinations on PI system

Use

This step has to be executed if an SAP ERP 6.0 system is used as backend system to connect a PI 7.3 system. These steps have to be executed on the PI system (AS JAVA) to connect the Integration Engine of the PI system and the SAP ERP 6.0 system.

Procedure:

1. Logon to the SAP NetWeaver Administrator using URL: http://:/nwa.

2. Access the activity using the following navigation options:

SAP Menu SAP NetWeaver Administrator -> Configuration -> Connectivity -> Destinations

3. Choose Create

4. Make the following entries


Hosting System Local Java System

Destination Name e.g. XI_ENGINE_DESTINATION_

Destination Type RFC

5. Choose Next

6. On the Connection and Transport screen make the following entries:





Load Balancing No

Target Host

System Number

System ID SID of backend system

SID

Gateway Host

Gateway Service e.g. sapgw

7. Choose Next

8. On the Logon Data screen make the following entries:


Client Backend client number

e.g. 164

User Name

Password

Destination Name This Destination

9. Choose Save.

Beside the RFC destination to the Integration Engine, there are also others RFC destinations that should be created to successful connect the SAP ERP system with the PI system. Please refer to the Config Guide SF2 for further details on the creation of these RFC destinations

3.1.4 Optional: Maintain Business System

This steps have to be executed if the Business System is not defined in the Integration Builder. The relevant Business system must be maintained in the according SLD.

3.1.4.1 Import Business System from SLD 1. In PI system access the activity using one of the following navigation options:

SAP Menu Process Integration Start Integration Builder

Transaction SXMB_IFR

Path In Integration Builder Communication Component Without

Party Right-click on Business System Assign Business System

2. Choose Continue.

3. Select the according Business System.

4. Choose Finish.



4 Getting the Business Content for Activation

4.1.1 Getting the Installation Data Files

Use

The installation content data files can be downloaded from SAP Service Marketplace. For the SAP SAP ERP HCM Integration for SuccessFactors rapid-deployment solution package a compressed file (*.tpz) has been delivered.

Procedure

The installation data files can be downloaded from the SAP Service Marketplace. Check the following link:

https://service.sap.com/swdc

Choose Installations and Upgrades -> Browse our Download Catalog -> SAP Rapid Deployment solutions -> SAP ERP HCM Integration for SuccessFactors rapid-deployment solution.

The ESR content files:

Choose Support Packages and Patches -> Search for Support Packages and Patches -> Search for: XI CONTENT RDS SF HCM

4.1.2 Getting the Configuration Guides

Use

The installation settings (configuration settings and master data) of the SAP Best Practices are described in the configuration guides.

The latest version of these documents are attached as attachment to the SAP ERP HCM Integration for SuccessFactors rapid-deployment solution support note (for details on the SAP Note number see above section SAP Notes and Messages).

4.1.3 Activation of Scenarios For an instruction on how to get information on all scenarios included in the SAP ERP HCM Integration for SuccessFactors rapid-deployment solution, see section Scenarios to be Activated above.

Activate then all Building Blocks in the the following sequence:

Scope item/ Process Description 1 2 3 4 5 6 7 8 9

Transfer of SAP ERP HCM basic employee data to SuccessFactors

SF6 SF1 C1H C1F C1E SF2 C1G

Pay-for-performance integration between SAP ERP HCM and SuccessFactors

SF6 SF1 C1H C1F C1E SF2 C1G C1K C1J

Transfer of SAP ERP HCM workforce analytics data to SuccessFactors

SF6 SF1 C1E SF3 SF2

Recruiting Integration between SuccessFactors and SAP ERP HCM

SF6 SF1 C1H C1F C1E SF2 C1G C1N C1M

Legend

PI & HCI PI only HCI only



Make the settings in the system according to the sequence of the configuration guides During the manual activation steps make sure that you use the personalized values and not the default values.You have to change the settings during the manual execution according to your requirements (do not use 1:1 the described settings in the configuration guide).

Make sure to translate the settings in the required target language(s) during the manual execution of the tasks.



5 Evaluate Business Content / Processes Business Consultant

5.1 Review of Business Processes

Details for individual scenarios are available in the Step by Step Guide in the area Discover: Communicate the Scope Business Process Documentation Page.

Depending on the scenarios you are interested in, choose the corresponding scenario link on the page. This will direct you to an HTML page with an overview of the scenario and a link to access the business process documentation.

On the Business Process Documentation Page you can also access the configuration guides of the respective scenarios.

The business process documentation (BPD) provides a detailed process step description of the business scenario.

The scenario overview document contains a graphical overview of the scenario process flow.

The configuration guide describes crucial parts of the system configuration of the respective scenario. Together with the configuration guides of the underlying building blocks, you can track which system settings have been configured. You can use the documents as described above to review the business scenarios you

are interested in. Use the business process documentation (BPD) to evaluate the

scenario in the system.

This package will not implement the above processes but enable the technology infrastructure required to implement the integration between SAP HCM and Success Factors for employee basic data integration, compensation process integration, recruiting and integration of workforce analytics data with the help of SAP ERP HCM Integration for SuccessFactors rapid-deployment solution.

6 Select the SAP Solution Manager Template Templates in SAP Solution Manager help you to carry out predefined implementation projects. The template specific to the SAP ERP HCM Integration to SuccessFactors rapid-deployment solution contains the content for the 'default' implementation of the rapid-deployment solution. Familiarize yourself with the template by reading the template description at

http://service.sap.com/solutionpackages Human Resources SAP ERP HCM Integration to SuccessFactors rapid-deployment solution

Procedure

In this step, you create an implementation project to organize your work in the SAP Solution Manager (SOLAR_PROJECT_ADMIN).

To select the rapid-deployment solution within the implementation project, carry out the following steps in transaction

1. Go to the Scope tab page.

2. Selection of rapid-deployment solution



a. In case of SAP Solution Manager 7.0 (ST 400) or SAP Solution Manager 7.1 (ST 710) < SP05

i. Select the Template Selection sub-tab page using hyperlink for further information.

ii. Search for the template SAP RDS - SAP ERP HCM Integration to SuccessFactors_V1

b. In case of SAP Solution Manager 7.1 (ST 710) use (at least SP05)

i. Select the Solution Package sub-tab page using hyperlink for further information.

ii. Search for the Solution Package SAP RDS - SAP ERP HCM Integration to SuccessFactors_V1

Check that note 1687765 (Robomate) is implemented to see Solution Package sub-tab. But this is a mandatory step to be done within SAP Solution Manager 7.1 (ST 710) SP05 upgrade.

3. Save your project.

4. A dialog box for the mapping of the Logical Components appears. Adjust the chosen Logical Component via F4 help if needed. For more information, see chapter Checking the System Landscape in SAP Solution Manager.

5. Select the business scenarios you want to copy to your implementation project.

6. Save your project.

When you save your project for the first time, you need to specify the enhancement context in which the project documents are to be saved in Knowledge Warehouse.

7. Map the logical components assigned to the process steps of the selected business scenario to your current system landscape. The system identifies missing logical components for product versions/instances required for the business processes.

8. To add the logical components to your system landscape choose the Contimue.

9. The list of logical components is updated on the System Landscape tab page.

10. Assign the systems in your system landscape to the logical components. For more information about the assigning logical components to a project see the SAP Help Portal at http://help.sap.com Application Lifecycle Management SAP Solution Manager SAP Solution Manager 7.0 EHP1 SP26 Implementing and Upgrading SAP Solutions Project Administration Create/Change Project System Landscape Tab Specify Project System Landscape Assign Logical Components to the Project.

7 Security Aspects - System Administrators This section provides an overview of the security-relevant information that applies to the deliverables of this SAP Best Practices package.

7.1 User Administration and Authentication In this chapter you will find an overview of the required users for this package



Purpose User-ID User Type

Created in Initial Password

Authorization Profile

Comment

Activation User

User ID is defined by your System-Admin.

Dialog (Type A)

Creation described in Quick Guide

Password is defined by your System Admin.

Authorization is defined by your System Admin.

You can check users using the user management administration console.

7.2 Roles Management In this chapter you will find an overview of the template roles. For details check the related product documentation.

Role Description Comment

SAP_XI_MONITOR_J2EE SAP NW PI

SAP_XI_ADMINISTRATOR_J2EE SAP NW PI

SAP_SLD_CONFIGURATOR Configurator Role SAP NW PI

SAP_XI_CONTENT_ORGANIZER_J2EE

SAP NW PI

SAP_SLD_DEVELOPER Developer role SAP NW PI

SAP_XI_CONFIGURATOR_EXT_J2EE

SAP NW PI

SAP_XI_CONFIGURATOR_J2EE SAP NW PI

SAP_XI_DEVELOPER_J2EE SAP NW PI

SAP_SLD_ORGANIZER Organizer Role SAP NW PI

You can check the roles assigned using the user management administration console.