Training Material CUSTOMER

Contents
SAP Model Company for HR
1 JunePurpose
2017
Update Personal Information
Error! Bookmark not defined.
1.1English (UK)
Purpose of the Document Error! Bookmark
not defined.
1.2. Purpose of New Hire / Rehire Error! Bookmark ID:
not defined.

2 Prerequisites Error! Bookmark not defined.

2.1 Configuration Error! Bookmark not defined.
2.2 System Access Error! Bookmark not defined.
2.3 Master Data, Organizational Data, and Other
Data Error! Bookmark not defined.
2.4 Business Conditions Error! Bookmark not
Table of Contents
defined.

3.
1 Overview
Purpose Table Error! Bookmark not defined. 4
1.1 Purpose of the Document 4
4.
1.2 Process
Purpose Steps
of Update Personal Information 4 4
4.1. Add New Employee Error! Bookmark not
2 defined.
Prerequisites 5
2.1 4.1.1.
Roles Entering Hiring Data Error! 5
2.2 Bookmark not defined.
Master Data, Organizational Data, and Other Data 5
2.3 4.1.2. Viewing
Business Employee Position
Conditions 5
Details Error! Bookmark not
3 defined.
Overview Table 6
4.2. Rehire Error! Bookmark not defined.
4.2.1.
4 Entering Rehiring Data
Testing the Process Steps Error! Bookmark not 7
4.1 defined.
Entering Data Change in Employee File 7
4.2.1.1.
4.2 Updating Position
Maintenance Details Personal
of Employee’s Error! Bookmark
Information 14
not defined.

Document History
Revision Change Date Description

V1 June 26, 2017 First version created

3
1 Purpose

1.1 Purpose of the Document

This document provides a detailed procedure for testing the scope item Update Personal Information.

1.2 Purpose of Update Personal Information

This document describes how an employee’s file can be updated and/or viewed within the SuccessFactors Employee Central system.
As example, we consider maintenance of data related to the employee's personal information, namely Home Address, Primary Emergency Contact, and marital status.

4
 2. Prerequisites

This section summarizes all prerequisites needed to conduct the test in terms of system, user, master data, organizational data, and other test data and business conditions.

2.1 Roles
For non-standard users, the following roles must be assigned in SuccessFactors to the system user(s) testing this scenario.

Business Role Permission Role

HR Administrator For testing purposes: Super_Admin

2.2 Master Data, Organizational Data, and Other Data

The organizational structure and master data of your company has been created in your system during implementation. The organizational structure reflects the structure of
your company and includes the company, cost centre and location in the system. It is part of the corporate data model and is pre-delivered as a starting point in Employee
Central.

2.3 Business Conditions

Before this scope item can be tested, the following business conditions must be met.

Business Condition Comment

1 Employees must have been hired (or rehired) and already exist in the system. Refer to the appropriate step of scope item New Hire / Rehire.

2 One administrator user with the complete access to all employee views and fields Permission Role Super_Admin can be used as reference.
must exist.

5
 3. Overview Table

The scope item Data Change Employee File consists of several process steps provided in the table below.

Process Step UI Business Condition Business Transact Expected Results

Type Role ion Code
Enter Data Change in SFSF Changes in the employee’s file are HR Success The employee’s home address and primary emergency contact have
Employee File EC UI required. Administrator Factors been updated.
URL

Maintenance of Employee’s Personal Information

Enter Change in SFSF The employee has changed his or HR Success Changes in the employee’s personal information have been
Personal Information EC UI her name, marital status, and so on. Administrator Factors performed.
URL

6
 4. Testing the Process Steps
This section describes test procedures for each process step that belongs to this scope item.
The test should take around 30 minutes.

4.1 Entering Data Change in Employee File

Purpose

The HR administrator enters a data change in the Employee File for an employee.
In this document, we consider two examples of data that is changed for the employee: the home address and the data of the person to be contacted in case of emergency.

Procedure

1. Log on to SFSF EC as HR administrator.

2. Search for the employee for which you want to perform the change and click on his name to access the Employee Profile.

7
3. Select the Personal Information portlet in the Employee Profile. In the different sections view the employee’s data as of today or view the history of the data by
selecting the History link where available.

4. Select the Edit link for the section you need to change, for example the Home Address.

8
5. Specify the effective date of change.

9
6. Make the changes as appropriate

10
7. Click on the SAVE button. The following message will appear.

8. Select the Edit link for the section you need to change, for example the Primary Emergency Contact.

11
9. In the Primary Emergency Contact portlet make following entries:
 Relationship: select from drop-down, for example Spouse
 Name: enter name of person to be contacted in case of emergency
 Primary: select from drop-down, for example Yes
 Phone: enter phone number of emergency contact
 Email: enter e-mail of emergency contact
 Dependent: select from drop-down, for example Yes

12
10. Select the Details link (as in the above screenshot) and in the following screen you are required to provide the complete address of the emergency contact:
 Copy Address from Employee: select Yes from drop-down

Note
In case you choose No, it is recommended that you add the address details of the emergency contact person.

11. Choose the SAVE button.

Note
The employee can view his or her current data as well as historical data in his or her own Employee File. For this, he or she needs the appropriate permission role
Employee (self-service).

13
4.2. Maintenance of Employee’s Personal Information
In case, the employee changes his or her name, for example due to a change in marital status, the employee’s record needs to be updated accordingly in the SuccessFactors
Employee Central system.

Purpose

The HR administrator enters in the system the relevant change in the personal information of an employee. These changes may refer to changes in naming and marital status.

Procedure

1. Log on to SFSF EC as HR administrator.

2. Search for the employee for which you want to perform the change and click on his name to access the Employee Profile.

14
3. Scroll down to the Personal Information section in the Personal Information portlet and click on the Edit button.

4. Enter Effective date of change.

15
5. Scroll down to the marital status field that you wish to change.

6. Make the change by selecting the new value from the drop-down menu.

16
7. Choose the SAVE button.

17
www.sap.com/contactsap

© 2017 SAP SE 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 SE
or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks of
SAP SE (or an SAP affiliate company) in Germany and other
countries. Please see http://global.sap.com/corporate-
en/legal/copyright/index.epx#trademark for additional trademark
information and notices.
Some software products marketed by SAP SE and its distributors
contain proprietary software components of other software
vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company
for informational purposes only, without representation or warranty
of any kind, and SAP SE or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only
warranties for SAP SE or SAP affiliate company 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.
In particular, SAP SE or its affiliated companies have no obligation to
pursue any course of business outlined in this document or any
related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and
SAP SE’s or its affiliated companies’ strategy and possible future
developments, products, and/or platform directions and
functionality are all subject to change and may be changed by SAP
SE or its affiliated companies at any time for any reason without
notice. The information in this document is not a commitment,
promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various
risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place
undue reliance on these forward-looking statements, which speak
only as of their dates, and they should not be relied upon in making
purchasing decisions.

18