SAP SuccessFactors HCM Suite CONFIDENTIAL

Q3 2018 – 2018-08-31

SAP SuccessFactors Testcases

Typographic Conventions

Type Style Description

Example Words or characters quoted from the screen. These include field names, screen titles,
pushbuttons labels, menu names, menu paths, and menu options.
Textual cross-references to other documents.

Example Emphasized words or expressions.

EXAMPLE Technical names of system objects. These include report names, program names,
transaction codes, table names, and key concepts of a programming language when they
are surrounded by body text, for example, SELECT and INCLUDE.

Example Output on the screen. This includes file and directory names and their paths, messages,
names of variables and parameters, source text, and names of installation, upgrade and
database tools.

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

<Example> Variable user entry. Angle brackets indicate that you replace these words and characters
with appropriate entries to make entries in the system.

EXAMPLE Keys on the keyboard, for example, F 2 or E N T E R .

CONFIDEN TIAL SAP SuccessFactors Testcases

2 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Typographic Conventions
What's New in this Guide

Q3 2018
The following table summarizes changes to this documentation for the Q3 2018 release.

What's new Description More Info

August 31, 2018

First Version Use the testcases provided in this document to

verify new features in the Q3 2018 release.

SAP SuccessFactors Testcases CONFIDEN TIAL

What's New in this Guide © 2018 SAP SE or an SAP affiliate company. All rights reserved. 3
Table of Contents

1 Analytics ................................................................................................................................... 7
1.1 Testcase: Check for layouts in the downloaded default BIRT templates without date/time
columns in MS Excel 2010 (.xlsx) format (AYT-16601) ..................................................................... 7
1.2 Testcase: Check for downloaded default BIRT templates with date/time columns in MS to be
opened Microsoft Excel 2010 (.xlsx) format (AYT-16601)................................................................. 8
1.3 Testcase: Check for download of custom BIRT templates to be supported in all formats (.xls,
.xlsx, pdf, ppt, run online, offline, etc.) (AYT-16601) .......................................................................... 8
1.4 Testcase: Check for downloaded reports to be in MS PowerPoint format (AYT-16601)................ 9
1.5 Testcase: Check for regressions related to Report Center particularly, Listing page, View
Schedules page and the New Schedule page. These pages have been redesigned to make them
more responsive and dynamic (AYT-18378/AYT-18421) .................................................................. 9
1.6 Testcase: Check for a valid error message to be displayed when accessing a deleted report
through the Quick Links or Favorites widget (AYT-18284/AYT-18421) ......................................... 10
1.7 Testcase: Check for filters to be retained when navigating to the Report Center list within a
session (AYT-18219/AYT-18424) ...................................................................................................... 10
1.8 Testcase: Check for reorder of pages in a Workforce Analytics report (AYT-17232/AYT-19515) 11

2 Employee Central ................................................................................................................... 12

2.1 Testcase: Check for creation of rules functions to compute the maximum total FTE and
determine the date of the maximum FTE occurrence (ECT-97363) ...............................................12
2.2 Testcase: Check for hiding EC Service Center internal notes and attachments (ECT-92450) ....12
2.3 Testcase: Check for addition of HRIS sync mapping support of User Info field and User Info
Record Key that allows users to maintain their own configurations and helps eliminate the role
of support or implementation partners to be involved in making configuration changes (ECT-
17587) ....................................................................................................................................................13
2.4 Testcase: Check for allowing the support of Dependent information model in rules (ECT-97031)
................................................................................................................................................................13
2.5 Testcase: Check for changing the hire date of employees (ECT-96786) .......................................14

3 Integration Center ................................................................................................................. 16

3.1 Testcase: Check for the addition of field filters on fields and to the parent node in case of a one
to many mapping (INT-6080) .............................................................................................................16

4 MDF ......................................................................................................................................... 17
4.1 To verify if validation message is displayed when data subject user field is changed in Manage
data page (XAF-21557) ........................................................................................................................ 17
4.2 Attachment validate with LSPD create operation (XAF-21557) ....................................................... 17

5 Onboarding ............................................................................................................................. 18
5.1 Testcase: Verify if Kentucky state withholding panel and form changes are complaint with
updates from 2018/Verify that Kentucky K-4M form is removed from ONB system due to the
newly designed K-4 form (ONB-21769 & ONB-21872/ONB-21293) ...............................................18
5.2 Testcase: Verify Voluntary self ID for disability form updates in 2018 (ONB-20962/ONB-21293)
................................................................................................................................................................19

CONFIDEN TIAL SAP SuccessFactors Testcases

4 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Table of Contents
5.3 Testcase: Check for Oklahoma state's own SWH form starting 2018 (ONB-21359/ONB-21293)
............................................................................................................................................................... 19

6 Platform - Check Tool ............................................................................................................ 21

6.1 Testcase: Check for RBP Admin's access 'Role Based Permissions' through Check Tool (PLA-
2424/PLA-462) ................................................................................................................................... 21
6.2 Testcase: Check for the existence of Everyone Group (PLA-4604/PLA-462) .............................. 21
6.3 Testcase: Check for the number of rules associated with a role is more than 100, so that
preventative or corrective measures can be taken to avoid or solve performance issues, and
misconfiguration pointed out that can be corrected by the RBP Admin without support help
(PLA-2403/PLA-462) ......................................................................................................................... 22
6.4 Testcase: Check for any RBP granted rule in a Role without Permission Group/User, so that run
time exception is avoided when these groups/users are refreshed, or target population is
calculated, and misconfiguration pointed out that can be corrected by the RBP Admin without
support help (PLA-4603/PLA-462)................................................................................................... 23
6.5 Testcase: Check for any RBP granted rule in a Role having permissions requiring target
population without Target, so that run time exception is avoided when Access groups/users are
refreshed, or target population is calculated, and misconfiguration pointed out that can be
corrected by the RBP Admin without support help (PLA-4606/PLA-462) ...................................24
6.6 Testcase: Check for total length of Access Group(s) names associated with a Rule of a Role to
be more than 1000 characters, so that possibility of breaking RBP Adhoc report can be
mitigated, and misconfiguration pointed out that can be corrected by the RBP Admin without
support help (PLA-4605/PLA-462)...................................................................................................24
6.7 Testcase: Check for total length of Target Group(s) names associated with a Rule of a Role to be
more than 1000 characters, so that possibility of breaking RBP Ad hoc Report can be mitigated,
and misconfiguration pointed out that can be corrected by the RBP Admin without support help
(PLA-4601/PLA-462) .......................................................................................................................... 25

7 Recruiting Management ........................................................................................................ 27

7.1 Testcase: Check for Talent Pools (RCM-47343) .............................................................................. 27
7.2 Testcase: Check for email campaigns (RCM-47007) ...................................................................... 27
7.3 Testcase: Check for initiating a talent pool report to show candidates in a pool and to show the
candidate's application details from the Application table (RCM-49608) .....................................29
7.4 Testcase: Check for initiating a talent pool report to show candidates in a pool and to show a
candidate's referral details from the Referral table (RCM-49608) .................................................29
7.5 Testcase: Check for initiating a candidate report to view the talent pools that the candidate is a
member of (RCM-49608) .................................................................................................................. 30
7.6 Testcase: Check for email campaign reports (RCM-49608).......................................................... 30
7.7 Testcase: Check for the user to filter the job requisitions on the job requisition summary page
through location filter criteria by using any of the location values selected for a multi select
location FO field of a job requisition and not just the primary location value (RCM-49503)........ 31
7.8 Testcase: Check for the Provisioning user to be able to define field criteria such that the
Location FO can be a parent field in the job requisition template, and if more than one "parent"
Location value is selected, the child values should be filtered accordingly at multi select (RCM-
49503) .................................................................................................................................................. 32
7.9 Testcase: Check for ODATA users to perform insert and upsert operations on job requisition
entity by allowing the OData users to pass multiple values of location for multi-select location
FO field through a new entity – location_objlist, and the existing location_obj to be supported for
both single select location FO field and the multi select location FO field (RCM-49503) .............34

SAP SuccessFactors Testcases CONFIDEN TIAL

Table of Contents © 2018 SAP SE or an SAP affiliate company. All rights reserved. 5
8 Recruiting Marketing ............................................................................................................ 39
8.1 Testcase: Check for creation of a Data Capture Form and its addition to a Landing Page (RMK-
8892 & RMK-12722) ............................................................................................................................ 39

9 Rewarding .............................................................................................................................. 42
9.1 Testcase: Check for new compensation field type to support EC mapping to translatable GO
fields (CMP-10770).............................................................................................................................. 42
9.2 Testcase: Check for Check Tool for Compensation and Variable Pay (CMP-17475) .................... 42
9.3 Testcase: Check for executive review enhancements (CMP-17259) ............................................. 42

10 Talent ..................................................................................................................................... 43
10.1 Testcase: Show Employee Profile rating information in Calibration session (CAL-5250/CAL-
5119)...................................................................................................................................................... 43
10.2 Testcase: Verify that MDF Talent Pools (latest UI version) can be activated using Upgrade
Center (SCM-12287/ SCM-10876) .................................................................................................... 44
10.3 Testcase: Information report generation for PMU external users (PMU-6147/PMU-7555) ........ 46
10.4 Testcase: Support 3 Text-Replacement Sets for Mentoring Programs - configuration (CDP-
8975)..................................................................................................................................................... 47
10.5 Testcase: Verify if a warning alert is generated while enabling the JPB profile (CDP-8665) ....... 47

11 Time ....................................................................................................................................... 48
11.1 Testcase: Check whether approver name and approval date appear in addition to the requester
name and request date (TIM-4084) .................................................................................................. 48
11.1.1 OData API for reading requester of Employee Time in Time Workbench...................... 48
11.1.2 OData API for reading workflow information of Employee Time in Time Workbench .. 49
11.1.3 Consider duration display setting of Time Type in Time Workbench .............................51
11.2 Testcase: Check for linking or grouping of different sickness leave records for Columbia (TIM-
4099) .................................................................................................................................................... 52
11.3 Testcase: Check for additional configurations for linking/grouping of sickness leave absences
for Columbia (TIM-4099).................................................................................................................... 53
11.4 Testcase: Check for setting up of templates for the Create, Edit, and Delete Notifications with
the help of Notification with Payout Rate Details, and Notification (without payout rate details)
templates (TIM-4089) ........................................................................................................................ 53
11.5 Testcase: Check for flexible configuration for Time Account Deduction Sequence (TIM-3743) 55

12 Tools ....................................................................................................................................... 57
12.1 Testcase: Check for the synchronization across instances with same CRM IDs without
Provisioning IST configuration, that is, check the sync between all instances belonging to same
customer (TLS-8928) ......................................................................................................................... 57
12.2 Testcase: Check for addition of the Business Key Details column, along with auto generated
sequence numbers for ease of identifying the required elements for synchronization (TLS-9132)
............................................................................................................................................................... 57

CONFIDEN TIAL SAP SuccessFactors Testcases

6 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Table of Contents
1 Analytics

1.1 Testcase: Check for layouts in the downloaded default

BIRT templates without date/time columns in MS Excel
2010 (.xlsx) format (AYT-16601)

Steps Results

1. Go to Report Center or the Ad Hoc Reports listing The reports without date/time columns vary in terms
page. of layouts and styles for the downloaded data.

2. Run reports, or create new reports with default The layout and styles can be enabled for such default
BIRT templates, and date/time columns in BIRT templates without date/time columns by
Microsoft Excel 2010 format. disabling the Remove Styling checkbox in the
General Info tab of the Report Creation/Edit page,
and then by running the reports.

3. Generate BIRT excel output that are Microsoft The reports with default BIRT templates open in
Excel 2010 compatible for Ad Hoc reports. other formats as well.

NOTE:
Provisioning switch must be enabled for
reports to be downloaded in Microsoft Excel
2010 (XLSX) formats.

Remember
As a customer, you do not have access
to Provisioning. To complete tasks
in Provisioning, contact your Implementation
Partner. If you are no longer working with an
Implementation Partner, contact SAP Cloud
Support.

SAP SuccessFactors Testcases CONFIDEN TIAL

Analytics © 2018 SAP SE or an SAP affiliate company. All rights reserved. 7
1.2 Testcase: Check for downloaded default BIRT templates
with date/time columns in MS to be opened Microsoft
Excel 2010 (.xlsx) format (AYT-16601)

Steps Results

1. Go to Report Center or the Ad Hoc Reports listing The default BIRT templates with date/time columns
page. open in .xlsx format and other formats as well,
2. Run reports, or create new reports with default without any or layout or styling being removed.
BIRT templates, and date/time columns in
Microsoft Excel 2010 format.

Note
If you are using Date/Time columns, clear
the Remove Styling check box on the General
tab to be able to save the report.
3. Generate 2010 compatible BIRT excel output for
Adhoc Reports.

NOTE:
Provisioning switch must be enabled for
reports to be downloaded in Microsoft Excel
2010 (XLSX) formats.

Remember
As a customer, you do not have access
to Provisioning. To complete tasks
in Provisioning, contact your Implementation
Partner. If you are no longer working with an
Implementation Partner, contact SAP Cloud
Support.

1.3 Testcase: Check for download of custom BIRT templates

to be supported in all formats (.xls, .xlsx, pdf, ppt, run
online, offline, etc.) (AYT-16601)

Steps Results

1. Go to Report Center or the Ad Hoc Reports listing The templates work as expected (according to the
page. defined custom BIRT template).

CONFIDEN TIAL SAP SuccessFactors Testcases

8 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Analytics
 Steps Results
2. Run an existing custom BIRT templates in report
listing page or upload a custom BIRT templates
and execute the reports.

Note
Most custom BIRT templates include
formatting/styling, which is lost if you select
the Remove Styling check box on the General
tab. However, if you are using Date/Time
columns, clear the Remove Styling check box
to be able to save the report.

1.4 Testcase: Check for downloaded reports to be in MS

PowerPoint format (AYT-16601)

Steps Results

1. Go to the Ad Hoc Reports listing page. The downloaded reports have the extension .PPTX,
2. Generate an Ad Hoc report (default/custom) in as it is the latest support in 4.3.2.
PPT format.

1.5 Testcase: Check for regressions related to Report Center

particularly, Listing page, View Schedules page and the
New Schedule page. These pages have been redesigned
to make them more responsive and dynamic (AYT-
18378/AYT-18421)

Steps Results

1. Log in to the instance and go to the Report Verify that all the features are accessible.
Center page.

2. Create different type of artifacts (table, canvas, The UI components resize and align according to the
tile and dashboard). browser resolution.

SAP SuccessFactors Testcases CONFIDEN TIAL

Analytics © 2018 SAP SE or an SAP affiliate company. All rights reserved. 9
 Steps Results

3. Resize the browser resolution and check that all The Report Center listing page, View Schedules page
the elements in the page are accessible. and New Schedules page adapt the theme of the
instance.
NOTE:
The components should adapt to the theme
selected for the instance.

1.6 Testcase: Check for a valid error message to be displayed

when accessing a deleted report through the Quick Links
or Favorites widget (AYT-18284/AYT-18421)

Steps Results

1. Create a report – Canvas, Dashboard, Tile and Verify that a valid message appears, which says "the
Table. report is not found indicating it may have been
2. Add the reports to the Favorites list or the Quick deleted or you have lost access and asking user to
Links. update the saved links".

3. Verify that the reports are accessible through the Verify that clicking OK on the message dialog takes
links. you back to the Report Center listing page.
4. Delete the created reports or remove the
permission for the report for a user who has
added it to Quick Links.
5. Access Quick Links and verify the error message.

1.7 Testcase: Check for filters to be retained when

navigating to the Report Center list within a session
(AYT-18219/AYT-18424)

Steps Results

1. Go to the Report Center listing page and apply The filters are retained.
sorting or/and filtering on the list.
2. Validate the list.

3. Go to the home page or any other page and The Report Center list follows the retained filters and
return to the Report Center listing page. sort order.

CONFIDEN TIAL SAP SuccessFactors Testcases

10 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Analytics
 Steps Results

NOTE:
The applied filters should be retained.
4. Validate the list.

5. Log out and log in and go to the Report Center The retained sorting or filters are in accordance with
listing page. the logged in user and not overlapping with other
6. Validate the filters and the list. users.

7. Try the same as different users and validate the

list.

1.8 Testcase: Check for reorder of pages in a Workforce

Analytics report (AYT-17232/AYT-19515)

Steps Results

1. Create a Workforce Analytics report (Report – The pages can be reordered and saved in the
Canvas). Workforce Analytics Report Canvas.
2. Add multiple pages to the report.
3. Reorder the pages through the reorder window.

4. Run the report and verify the order of the pages. The order is retained while running the report.

SAP SuccessFactors Testcases CONFIDEN TIAL

Analytics © 2018 SAP SE or an SAP affiliate company. All rights reserved. 11
2 Employee Central

2.1 Testcase: Check for creation of rules functions to

compute the maximum total FTE and determine the date
of the maximum FTE occurrence (ECT-97363)

Steps Results/Additional Information

1. Create an on save/on change rule on An error message is displaying on changing or saving

JobInformation Object. Job Information.
2. Ensure the rule executes for Concurrent
Employment add/edit scenarios. KBA Article Reference
For example: [Link]
If (MaxFTEForTimePeriod() ) > 1.5 then Raise an
Error Message
Add a Concurrent Employment for an employee
with FTE value = 2

2.2 Testcase: Check for hiding EC Service Center internal

notes and attachments (ECT-92450)

Steps Results/Additional Information

1. Log in to C4C. The note added from C4C is hidden.

2. Navigate to any tickets and add a note.
3. Log off from C4C and then login to BIZX to
check the note for the ticket.

CONFIDEN TIAL SAP SuccessFactors Testcases

12 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Employee Central
2.3 Testcase: Check for addition of HRIS sync mapping
support of User Info field and User Info Record Key that
allows users to maintain their own configurations and
helps eliminate the role of support or implementation
partners to be involved in making configuration changes
(ECT-17587)

Steps Results/Additional Information

1. Go to Admin Center > Manage Business User info field and User info Record Key are supported
Configuration > Employee Central > HRIS for sync mapping using BCUI.
Elements. For more information refer to the KBA: Manage
2. Select any HRIS element. For Example, jobInfo Business Configuration: Support for HRIS Sync
or compInfo. mappings to Userinfo Elements in BCUI
3. Select a field you want to sync to Employee
Profile. Information on the right side will show
details for the selected element.
4. Click Details corresponding to any HRIS field.
5. Scroll down to the HRIS Sync Mapping
Section.
6. In the HRIS Sync Mapping:User info field/HRIS
Sync Mapping:User info Record Key section,
select the User Info field, Entity Type, and
name if applicable.
7. Save the changes.

2.4 Testcase: Check for allowing the support of Dependent

information model in rules (ECT-97031)

Steps Results/Additional Information

1. Go to Admin Center > Manage Business The trigger rule should support newly added Base
Configuration > Employee Central > HRIS Objects: Dependents and Dependents model and
Elements. Dependent information is supported only for Personal
2. Select any HRIS element. For example, Information, National ID Card, Email Information, Home
compInfo. Address, Phone Information, and Global Information.

3. Information on the right side will show details

for the selected element. For more information, refer to the KBA: 2676341 - How
4. Go to Trigger Rules section. to configure and set Business Rules to trigger in
Dependents Information

SAP SuccessFactors Testcases CONFIDEN TIAL

Employee Central © 2018 SAP SE or an SAP affiliate company. All rights reserved. 13
 Steps Results/Additional Information
5. From the Base Object dropdown, select a base
object.
6. From the Event Type dropdown, select the
event type on which the rule gets triggered.
7. From the Rules dropdown, select any one
from the existing rules. The rules get filtered
based on the Base Object selected.
8. Click Save to save your changes.

2.5 Testcase: Check for changing the hire date of employees

(ECT-96786)

Steps Results/Additional Information

Prerequisite:

Set up permissions for the Hire Date Correction feature in Manage Permission Roles under Metadata
Framework as described in KBA-2636395.

1. In the Admin Center, in the Tools search The hire date of the employee is changed successfully.
for Hire Date Correction. If the action search is Elements which can be updated through the Hire Date
not activated, go to Manage Data > Create Correction are as follows:
New Hire → Hire Date Correction.
· Employment Information
2. In the Correction Name field, enter a unique
· Job Information
name for this object.
· Compensation Information
3. Enter the employee name. The original hire
date is retrieved. · Recurring Pay Components

4. Enter the new hire date. · Job Relationships

5. Save your changes. · Personal Information

· Global Information
· Address Information
· Dependents Information
· Dependents Information - Personal Information
· Dependents Information - Global Information
· Dependents Information - Address Information
· Recurring Deductions
· Payment Information

CONFIDEN TIAL SAP SuccessFactors Testcases

14 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Employee Central
 Steps Results/Additional Information

Note
The old Hire Date must be the same for all of
them to be updated.
Please see KBA-2636395 for additional information as
well as current limitations of the feature.

SAP SuccessFactors Testcases CONFIDEN TIAL

Employee Central © 2018 SAP SE or an SAP affiliate company. All rights reserved. 15
3 Integration Center

3.1 Testcase: Check for the addition of field filters on fields

and to the parent node in case of a one to many mapping
(INT-6080)

Steps Results

1. Create a CSV Outbound Integration by selecting The displayed results are in accordance with the
an entity (say PerPerson) and a few fields. applied filters, that is, specific to the first name or
2. Click on Add Field option on the Configure field email type selected from dropdown
page and search for First Name.
3. Expand the Field Filter arrow on the same page
and select a field filter by clicking the radio
button and selecting a value from dropdown (say
Last).
4. Click Add Association and check the data on the
Configure field page.
5. Select other field filter options from dropdown
for different fields and entities (for example,
select the 1:M mapping node for a navigable field
(EmailNav) and click on Change Association.
Expand Field Filters and provide a condition).
6. Try the same for other types of integrations (say
XML, JSON). Expand Field Filters and provide
EmailType "is equal to" <emailType> condition.

CONFIDEN TIAL SAP SuccessFactors Testcases

16 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Integration Center
4 MDF

4.1 To verify if validation message is displayed when data

subject user field is changed in Manage data page (XAF-
21557)

Steps Result/Additional Information

Prerequisites:
There is an object existing for which LSDP config in already created and the data subject is set to user data
type and there is data entered for that object.

1. Navigate to Manage data. create a record for the The record should be saved successfully.
object with some value for data subject user field
and save.

2. Click on make correction and change the data The validation message should be displayed saying
subject user field to some other value and save. that the data subject user field cannot be changed.

4.2 Attachment validate with LSPD create operation (XAF-

21557)

Steps Result/Additional Information

1. Create an object definition with an attachment The object should be created successfully.
field and user field.

2. Add some records for the above object in The records must be added successfully.
manage data page and save.

3. Create an LSPD config for the above object with The LSPD should be created.
the user field as the data subject field.

4. Check the attachment details in attach content The attachment details should be updated
table - owner_id and owner_id_type. successfully.

SAP SuccessFactors Testcases CONFIDEN TIAL

MDF © 2018 SAP SE or an SAP affiliate company. All rights reserved. 17
5 Onboarding

5.1 Testcase: Verify if Kentucky state withholding panel and

form changes are complaint with updates from
2018/Verify that Kentucky K-4M form is removed from
ONB system due to the newly designed K-4 form (ONB-
21769 & ONB-21872/ONB-21293)

Steps Result/Additional Information

1. Log in to Onboarding as a Manager Verify that the login is successful.

2. Go to Home > Onboarding > Process. Verify that the process starts successfully.
3. Initiate PHV process.

4. In the Job Location panel, select the location that Verify that the Manager can select the location and
is mapped to Kentucky. complete the PHV step.
5. Complete the PHV step.

6. Proceed to the NES step. Verify that the Manager can initiate the NES Process
7. Select Kentucky as the state for physical and Kentucky Withholding form follows the W-4
address. withholding form.

8. Look out for Withholding forms.

9. Check the Kentucky state withholding form K-4 Verify the Kentucky state withholding form K-4 panel
panel. has the text update as per attachments.

10. Compare the KY_K_4 form format in the Verify that the format is correct.
application is same as the government form.

11. Check Kentucky KY-K-4M form at Employee Verify that the form is disabled in the system.
signature step.

Note: Due to the newly designed K-4 form,

Kentucky no longer requires the K-4M form
to be populated.

CONFIDEN TIAL SAP SuccessFactors Testcases

18 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Onboarding
5.2 Testcase: Verify Voluntary self ID for disability form
updates in 2018 (ONB-20962/ONB-21293)

Steps Result/Additional Information

Pre-requisites:
· KMS_NewEmployeeEeoInformationForm feature must be enabled.

1. Log in to Onboarding as a Manager. Verify that the login is successful.

2. Go to Home > Onboarding > Process. Verify that the process starts successfully.
3. Initiate PHV step.

4. On Job Location panel, select country mapped to Verify that the Manager can select the location and
US and complete the step. complete the PHV step.

5. Start NES through the link included in the Verify that the Manager can initiate the NES Process
welcome mail. and the link refers to 2018 form.
6. Select resident country as US.
7. Go to Disability Status panel.
8. Click Voluntary Self-Identification of Disability
and check the new disability form.

9. Go to Signature. Verify that the latest form issued in 2018 appears for
10. Check for latest Voluntary Self-Identification of employee signature.
Disability form.

5.3 Testcase: Check for Oklahoma state's own SWH form

starting 2018 (ONB-21359/ONB-21293)

Steps Result/Additional Information

1. Log in to Onboarding as a Manager. Verify that the login is successful.

2. Go to Home > Onboarding > Process. Verify that the process starts successfully.
3. Initiate PHV step.

4. In the Job Location panel, select the location that Verify that Manager can select the location and
is mapped to Oklahoma. complete PHV step.
5. Complete the PHV step.

6. Proceed with NES step. Verify that the Manager can initiate the NES Process
7. Select Oklahoma as physical address. and Oklahoma Withholding form should follow the W-
4 withholding form.
8. Look out for Withholding forms.

SAP SuccessFactors Testcases CONFIDEN TIAL

Onboarding © 2018 SAP SE or an SAP affiliate company. All rights reserved. 19
 Steps Result/Additional Information

9. Check the new Oklahoma State Withholding Verify that the new Oklahoma State Withholding Form
Form OK W-4 panel as per the attached OK W-4 panel appears and is as per requirements
requirement spreadsheet. included in the spreadsheet.

10. Fill the necessary data. Verify that the new form OK_W_4 appears at
11. Go to Signature. signature and data captured is appropriate.

12. Check OK_W_4 form at Employee Signature

step.

CONFIDEN TIAL SAP SuccessFactors Testcases

20 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Onboarding
6 Platform - Check Tool

6.1 Testcase: Check for RBP Admin's access 'Role Based

Permissions' through Check Tool (PLA-2424/PLA-462)

Steps Result/Additional Information

Prerequisites:
Prepare an RBP Admin.

1. Go to Admin Center > Company Settings > Check · Role Based Permissions shows in the Check Tool
Tools. list.
2. Select Role Based Permissions in the Application · For RBP Check Tool UI, 7 checks should be
drop down of Check Tool. visible on expanding.
3. Expand Role-Based Permissions. · Dynamic Groups.
4. Expand Dynamic Groups. · Everyone group exists.
5. Expand Permissions. · Permissions
· Number of rules associated with a role exceeds
100.
· Roles exist that are not associated with access
permission groups or users.
· Roles exist without target population defined.
· The access group names associated with a rule
exceeds 1000 characters.
· The target group names associated with a rule
exceeds 1000 characters.
· Users have been granted the same permission
more than 30 times.

6. Go to Admin Center > Company Settings > Check · Role Based Permissions doesn't show in the
Tools. check Tool list.

6.2 Testcase: Check for the existence of Everyone Group

(PLA-4604/PLA-462)

SAP SuccessFactors Testcases CONFIDEN TIAL

Platform - Check Tool © 2018 SAP SE or an SAP affiliate company. All rights reserved. 21
 Steps Result/Additional Information

Prerequisites:
Prepare an RBP Admin.

1. Go to Admin Center > Company Settings > Check Everyone/LMS everyone group/ONB everyone
Tools. group.
2. Verify if the Everyone group exists. If Everyone Group does not exist, it will show 1 issue
found.
3. Click to select checkbox.
If everyone group exists, it will show No issue found.
4. Run 1 check.

6.3 Testcase: Check for the number of rules associated with

a role is more than 100, so that preventative or corrective
measures can be taken to avoid or solve performance
issues, and misconfiguration pointed out that can be
corrected by the RBP Admin without support help (PLA-
2403/PLA-462)

Steps Result/Additional Information

Prerequisites:
Prepare an RBP Admin.

1. Go to Admin Center > Company Settings > Check No issue found, or 1 issue found shows in Check Tool
Tools. page.
2. Verify if number of rules associated with a role
exceeds 100.
3. Click to select checkbox.
4. Run 1 check.

5. Prepare one role, number of rules greater/less

than 100
a. A role has rule count < 100
b. One role has rule count > 100

6. Prepare multiple roles, some role's rule number Previous Result will show 2 issues found in the Check
greater than 100. Tool page.
Multiple roles have rule count > 100 Click Previous Result. Role2 and Role3 are listed
role1: 100 rules there.
role2: 101 rules

CONFIDEN TIAL SAP SuccessFactors Testcases

22 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Platform - Check Tool
 Steps Result/Additional Information
role3: 102 rules
role4: Without rule
role5: 50 active rules, 52 inactive rules

6.4 Testcase: Check for any RBP granted rule in a Role

without Permission Group/User, so that run time
exception is avoided when these groups/users are
refreshed, or target population is calculated, and
misconfiguration pointed out that can be corrected by
the RBP Admin without support help (PLA-4603/PLA-
462)

Steps Result/Additional Information

Prerequisites:
Prepare an RBP Admin.

1. Go to Admin Center > Company Settings > Check

Tools.
2. Verify if roles exist that are not associated with
access permission groups or users.
3. Click to select checkbox.
4. Run 1 check.

5. Prepare no rule without AG group in any role. No issue found.

6. Prepare one rule without AG group in one role. Previous Result will show 1 issue found in the Check
Tool page.
Click Previous Result. Roles Not Associated With
Permission Groups/Users result check. Role name
should be listed there.

SAP SuccessFactors Testcases CONFIDEN TIAL

Platform - Check Tool © 2018 SAP SE or an SAP affiliate company. All rights reserved. 23
6.5 Testcase: Check for any RBP granted rule in a Role
having permissions requiring target population without
Target, so that run time exception is avoided when
Access groups/users are refreshed, or target population
is calculated, and misconfiguration pointed out that can
be corrected by the RBP Admin without support help
(PLA-4606/PLA-462)

Steps Result/Additional Information

Prerequisites:
Prepare an RBP Admin.

1. Go to Admin Center > Company Settings > Check

Tools.
2. Verify if roles exist without target population
defined.
3. Click to select checkbox.
4. Run 1 check.

5. Prepare no rule without TG group in any role. No issue found.

6. Prepare multiple rules without target group Previous Result will show 3 issues found in the Check
role1: one rule without TG Tool page.
role2: one rule with TG, one rule without TG Click Previous Result. Role1, Role2 and Role3 are
role3: two rules without TG listed there.
role4: without rule

6.6 Testcase: Check for total length of Access Group(s)

names associated with a Rule of a Role to be more than
1000 characters, so that possibility of breaking RBP
Adhoc report can be mitigated, and misconfiguration
pointed out that can be corrected by the RBP Admin
without support help (PLA-4605/PLA-462)

CONFIDEN TIAL SAP SuccessFactors Testcases

24 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Platform - Check Tool
 Steps Result/Additional Information

Prerequisites:
Prepare an RBP Admin.

1. Go to Admin Center > Company Settings > Check

Tools.
2. Verify if the access group names associated with
a rule exceeds 1000 characters.
3. Click to select checkbox.
4. Run 1 check.

5. Prepare one role, two rules, every access group No issue found.
length < 1000, total access group length > 1000

6. Prepare one role, two rules, every access group 1 issue found. Clicking on 1 issue found link will show
length > 1000 the role with the issue, and then clicking on this role
will show yellow Group/User granted with role
permission and Target population.

6.7 Testcase: Check for total length of Target Group(s)

names associated with a Rule of a Role to be more than
1000 characters, so that possibility of breaking RBP Ad
hoc Report can be mitigated, and misconfiguration
pointed out that can be corrected by the RBP Admin
without support help (PLA-4601/PLA-462)

Steps Result/Additional Information

Prerequisites:
Prepare an RBP Admin.

1. Go to Admin Center > Company Settings > Check

Tools.
2. Verify if the target group names associated with
a rule exceeds 1000 characters.
3. Click to select checkbox.
4. Run 1 check.

5. Prepare one role, two rules, every target group No issue found.
length < 1000, total access group length > 1000

SAP SuccessFactors Testcases CONFIDEN TIAL

Platform - Check Tool © 2018 SAP SE or an SAP affiliate company. All rights reserved. 25
 Steps Result/Additional Information

6. Prepare one role, two rules, every tg length > 1 issue found. Clicking on 1 issue found link will show
1000 the role with the issue, and then clicking on this role
will show yellow Group/User granted with role
permission and Target population.

CONFIDEN TIAL SAP SuccessFactors Testcases

26 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Platform - Check Tool
7 Recruiting Management

7.1 Testcase: Check for Talent Pools (RCM-47343)

Steps Results/Additional Information

1. Create a talent pool without pipeline. Talent pool should be created successfully.

2. Create a talent pool with pipeline. Talent pool should be created with pipeline successfully.

Verify that you should be able to edit the pool

3. Edit the talent pool. successfully.

· Candidates should be added to the pool

successfully.
· On viewing the talent pool, the candidates added to
the pool should be listed.

4. Search for candidates and add them to a Note

talent pool. If pool had pipeline, pipeline should be
5. View the talent pool details. displayed while viewing pool details.

· In the candidate profile, there should be a talent

6. Search for a candidate who was added to the pool portlet and the
pool and view the candidate details · Pools to which they belong should be listed.

Pool should be archived successfully and should not be

listed in talent pool page.
User should not be able to see this pool while adding the
candidates.
7. Archive the talent pool by choosing Talent Also, the talent pool should not be listed when filter
pool->Search for the pool->Select the pool - criteria for Talent pool is selected in Keyword and Item
>Actions icon -> Archive. Search page.

7.2 Testcase: Check for email campaigns (RCM-47007)

Steps Results/Additional Information

1. Create an email campaign.

2. Provide inputs to all the required fields and · The campaign gets saved successfully with the
save it. details provided.

SAP SuccessFactors Testcases CONFIDEN TIAL

Recruiting Management © 2018 SAP SE or an SAP affiliate company. All rights reserved. 27
 Steps Results/Additional Information
3. Select a brand for the campaign. · The campaign should be listed when it is searched
from the Marketing tab.

4. Go to Marketing ->Search for the campaign

and click it.
5. Make some changes to the campaign and The user should be able to make changes to the
save. campaign and save them successfully.

6. Add some candidates to the campaign by

searching for candidates from Candidate
Search page.
7. In the Candidate Search page, select Click
Actions -> Add to email campaign.
8. In the campaign page, click on Manually Candidates are added successfully to campaign.
Added Recipients.

9. Add candidates belonging to a talent pool to

the campaign by going to Talent Pools->
Select a pool -> Actions-> Add to campaign.
10. In the campaign, click Talent Pools to
manually add them.

11. Send the created campaign mail to the Candidates belonging to the pool are added
recipients. successfully to the campaign.
12. View the details of the sent campaign.

13. Search for a candidate who was the recipient · Campaign is sent successfully.
of the campaign was sent through Candidate · Campaign status is changed to Sent once the
Search. campaign is sent. This can be checked from the
14. Click on the candidate profile. Marketing tab.

· Campaign details are shown.

· Activity status of the campaign recipients and the
number of recipients to whom the campaign was
sent should be displayed.
· Additional details such as campaign content,
status, description should also be displayed.
· The campaign details are shown in the candidate
profile in the Campaign dialog box.
15. Go to Marketing à Create a campaign by
providing the required fields and Save. Search · Campaign should be deleted successfully.
for the campaign à Click on Actions icon à · The report should be generated successfully with
Delete Campaign proper values from all the 3 tables.

CONFIDEN TIAL SAP SuccessFactors Testcases

28 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Recruiting Management
7.3 Testcase: Check for initiating a talent pool report to
show candidates in a pool and to show the candidate's
application details from the Application table (RCM-
49608)

Steps Results/Additional Information

1. Log in to the application. The report should be generated successfully with

2. Go to Adhoc Reports. proper values from all the 3 tables.

3. Initiate a Recruiting V2 report.

4. Add Pool Name from Talent Pool.
5. Add Candidate ID and Pool Member Status
from Pool Member.
6. Add Candidate First Name, Last Name fields
from Candidate.
7. Add Application ID, Job Req ID, Application
Status and other Standard and Custom fields
from Application.
8. Generate a report.

7.4 Testcase: Check for initiating a talent pool report to

show candidates in a pool and to show a candidate's
referral details from the Referral table (RCM-49608)

Steps Results/Additional Information

1. Log in to the application. The report should be generated successfully with

2. Go to Adhoc Reports. proper values from all the 3 tables.

3. Initiate a Recruiting V2 report.

4. Add Pool Name from Talent Pool.
5. Add Candidate ID and Pool Member Status
from Pool Member.
6. Add Candidate First Name, Last Name fields
from Candidate.
7. Add Referral ID, Referred By and other
columns from Referral.
8. Generate a report.

SAP SuccessFactors Testcases CONFIDEN TIAL

Recruiting Management © 2018 SAP SE or an SAP affiliate company. All rights reserved. 29
7.5 Testcase: Check for initiating a candidate report to view
the talent pools that the candidate is a member of (RCM-
49608)

Steps Results/Additional Information

1. Log in to the application. The report should be generated successfully with

2. Go to Adhoc Reports. proper values from all the 3 tables.

3. Initiate a Recruiting V2 report.

4. Add Candidate First Name, Last Name fields
from Candidate.
5. Add Pool Name and Pool Member Status from
Pool Member.
6. Generate a report.

7.6 Testcase: Check for email campaign reports (RCM-

49608)

Steps Results/Additional Information

1. Generate Reports for: · The data should be populated in the corresponding

· Email Campaign columns and should be appearing from the
Recruiting->Marketing->Email Campaign form.
· Email Campaign Content
· The data should be populated in the corresponding
2. Generate Reports for:
columns and should be appearing from the
· Email Campaign Pool Recruiting->Marketing->Email Campaign form and
· Email Campaign Pool Extension Talent Pool data linked to that Campaign.
3. Generate Reports for: · The data should be populated in the corresponding
· Email Campaign Recipient columns and should be appearing from the
Recruiting->Marketing->Email Campaign form and
· Email Campaign Recipient Activity
Talent Pool data linked to that Campaign and
Candidate Data for the Recipients linked to that
Campaign directly or through Pools.

CONFIDEN TIAL SAP SuccessFactors Testcases

30 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Recruiting Management
7.7 Testcase: Check for the user to filter the job requisitions
on the job requisition summary page through location
filter criteria by using any of the location values selected
for a multi select location FO field of a job requisition and
not just the primary location value (RCM-49503)

Steps Results/Additional Information

1. Log in to the application and go to the Job The location FO column on the Job Requisition
Requisition Summary page. Summary page shows the number of locations selected
2. Create a job requisition with multi select for the job requisition.
location FO field.
3. Select more than one value for the location FO
field and save the changes.
4. Go back to the Job Requisition Summary
page.

5. Click on the filter options button on the Job All the job requisitions having the value chosen in the
Requisition Summary page to open the filter filter options as location should be displayed in the list
options popup. of jobs.
6. Choose one of the values selected for the job
requisition – location FO field and click on
Update.

7. Repeat the above steps for primary location The job requisition should be removed from the filtered
value and ensure that the job requisitions are list on the Job Requisition Summary page as the value is
listed appropriately when the job requisition removed from the job requisition.
location FO filter is applied on the primary
value selected for a job requisition.
8. Perform this validation for single select
location FO field as well, that is, ensure that
the job requisitions with single select location
FO field having the filtered location value are
also displayed in the list.
9. After applying the location FO filter Job
Requisition Summary page, go to one of the
job requisitions and remove the selected
location FO value.

10. Create a job requisition using the option Copy The results are displayed correctly, that is, if the filter
from existing job requisition. value is same as one of the values selected for a job
11. Use the filter option Location and choose a requisition's location FO field, the job requisition should
value. be displayed in the results.

SAP SuccessFactors Testcases CONFIDEN TIAL

Recruiting Management © 2018 SAP SE or an SAP affiliate company. All rights reserved. 31
7.8 Testcase: Check for the Provisioning user to be able to
define field criteria such that the Location FO can be a
parent field in the job requisition template, and if more
than one "parent" Location value is selected, the child
values should be filtered accordingly at multi select
(RCM-49503)

Steps Results/Additional Information

1. Configure a job requisition template with field The job requisition is uploaded successfully
criteria such that the location FO can be a
parent field in the job requisition template.

Remember
As a customer, you do not have access
to Provisioning. To complete tasks
in Provisioning, contact your
Implementation Partner. If you are no
longer working with an Implementation
Partner, contact SAP Cloud Support.

2. Create a job requisition using this template The child field values are displayed appropriately based
and select multiple values for Location FO on the values selected for location FO parent field, that
parent field. is, if there are two values selected for location FO parent
field, the child values of both the values should be
displayed for the child field.

3. Remove one of the selected values of Location Once the parent field value (location FO ) is unselected,
FO field. its corresponding child value should also be removed
from the dropdown list of the child field and the child
field selection should be cleared.

4. Configure the location FO field as a child of

one field and parent of another field.

5. Select a value for the parent field. · The child field – location FO fetches the values
based on the parent field selection.
· The child field of location FO also fetches the values
based on the selection of the location FO field.

6. Remove the value of the parent field and · The behavior should remain consistent for the
ensure that its corresponding child field single select location FO field as well, that is, when
(location FO) gets cleared. the parent field value is set to None or changed, its
corresponding child fields should get cleared
without any highlight on the cleared fields.
· There is no message displayed stating that the
values have been deleted.

CONFIDEN TIAL SAP SuccessFactors Testcases

32 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Recruiting Management
 Steps Results/Additional Information

7. Save a job requisition by choosing the values The job requisition is saved successfully with the
for all the cascaded FO/GO fields. selected values.

8. Select all the values of the location FO field. · The loading time should be considered while
enabling the child field, that is, the child field should
not be enabled until all the values of location FO
field are loaded and selected.
· Child values should be populated for all the values
of location FO field in case of selecting all.
·

9. Change the job start date. · This action should remove the values of the location
FO field and its corresponding child fields as well.
· If the selected location FO value becomes inactive
for the job start date, ensure that there is an
appropriate error message stating that there are
invalid entries in the job requisition. This validation
should happen for the child values as well.

10. If there are multiple parents for a field, ensure The child values are populated based on the multiple
that the child field gets enabled for value value selection on location FO field and any other parent
selection only after all the parent field values field value selected.
are selected.
11. If location FO is one of the parent, select
multiple values for location FO field.

12. If there are multiple versions of location and The labels of the location FO field and its corresponding
its corresponding child fields, ensure that the child field value are picked from the valid version as on
labels of the values selected for location FO today. Also, the associations should be picked from the
field are picked from the current active/valid latest active versions.
version.
13. Ensure that the labels of the values for child
fields are also picked from the latest active
version.
RBP Permissions
· When location FO field does not have RBP –
visible permission, ensure that the child field
dropdown should not list any value.
· When location FO field has RBP visible
permission but does not have read or write
permission, child field does not display any
value in the dropdown.

SAP SuccessFactors Testcases CONFIDEN TIAL

Recruiting Management © 2018 SAP SE or an SAP affiliate company. All rights reserved. 33
 Steps Results/Additional Information
· When location FO field has RBP Permission
But only read permission, ensure that the child
field displays the values based on the location
FO values already selected.
Change in association when job start date is not
given:
1. Create a job requisition without entering a
value for job start date.
2. Create multiple versions of location.

7.9 Testcase: Check for ODATA users to perform insert and

upsert operations on job requisition entity by allowing
the OData users to pass multiple values of location for
multi-select location FO field through a new entity –
location_objlist, and the existing location_obj to be
supported for both single select location FO field and the
multi select location FO field (RCM-49503)

Steps Results/Additional Information

1. Insert a few job requisitions through ODATA The job requisition is created successfully with the list of
with the Job Requisition template having location values passed through the OData payload.
location FO field configured as single select the value associated with primary attribute is marked as
field. primary location in the job requisition.
2. Insert a few more job requisitions having multi
select location FO field configured in the
template.
3. Perform INSERT operation on job requisition
having multi-select location FO field.
4. Use the newly introduced entity –
location_objlist to pass multiple location
values for the multi-select location FO field.
5. Also ensure one of the values is associated
with a primary attribute as shown in the
sample request below:
Sample Request:
{
"templateId": "2583",

CONFIDEN TIAL SAP SuccessFactors Testcases

34 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Recruiting Management
 Steps Results/Additional Information

"recruiter": {
"userName": "athompson"
},
"jobReqLocale":{
"jobTitle":"sprint4 demo - job : june12th ",
"externalTitle":"sprint4 demo - job"
},
"location_objlist": [
{
"isPrimary" : false,
"value" :
{
"externalCode": "location10"
}
},
{
"isPrimary" : false,
"value" :
{
"externalCode": "location25"
}
},
{
"isPrimary" : true,
"value" :
{
"externalCode": "location50"
}
}
],

"division_obj" : { "externalCode":"demo b1808

div26" }

6. Perform INSERT operation on job requisition

having multi-select location FO field.

SAP SuccessFactors Testcases CONFIDEN TIAL

Recruiting Management © 2018 SAP SE or an SAP affiliate company. All rights reserved. 35
 Steps Results/Additional Information
7. Use the entity – location_obj to insert a single
location FO value as shown in the sample
request below:
Sample Request:
{
"templateId": "2585",
"originator": {
"userName": "cgrant"
},

"jobReqLocale":{
"jobTitle":"new odata multi location",
"externalTitle":"odata multi location”
},
"legalEntity_obj": {
"externalCode": "APAC_FIN"
},
"location_obj": {
"externalCode": "demo b1808 location501"
},
"customf3": {
"externalCode": "ASIA"
}

8. Insert multiselect location FO job using The job requisition insert fails with an appropriate error
location_objlist entity by passing few invalid message stating the location values are invalid.
location values in the payload.

9. Insert job requisitions by passing values for · The insert is successful if the values passed for
multi-select location FO field and its location FO and its child field are associated to each
corresponding child field. other.
· The insert fails if the values of parent and child
fields do not have valid associations.

10. Insert a multi-select job requisition by passing · There is an appropriate error message stating both
multiple values – each value associated with a the entities cannot be used together in the same
different entity ( location_obj, location_objList payload.
)

CONFIDEN TIAL SAP SuccessFactors Testcases

36 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Recruiting Management
 Steps Results/Additional Information

11. Perform INSERT operation on job requisition The job requisition insert fails with a message stating
having multi-select location FO field. that multiple values cannot be passed in the payload, as
12. Use the newly introduced entity – it is a single select location FO field.
location_objlist to pass multiple location
values for the multi-select location FO field.
Sample Request:
{
"templateId": "2583",

"recruiter": {
"userName": "athompson"
},
"jobReqLocale":{
"jobTitle":"sprint4 demo - job : june12th ",
"externalTitle":"sprint4 demo - job"
},

"location_objlist": [
{
"isPrimary" : false,
"value" :
{
"externalCode": "location10"
}
},
{
"isPrimary" : false,
"value" :
{
"externalCode": "location25"
}
},
{
"isPrimary" : true,
"value" :
{
"externalCode": "location50"
}
}

SAP SuccessFactors Testcases CONFIDEN TIAL

Recruiting Management © 2018 SAP SE or an SAP affiliate company. All rights reserved. 37
 Steps Results/Additional Information
],

"division_obj" : { "externalCode":"demo b1808

div26" }

13. Remove multiple values from the payload and The job requisition is inserted successfully with the one
pass only one location value using location value passed via location_objlist entity in the
location_objlist with primary attribute set to OData payload.
“true”.

14. Insert a single select location FO job · The job requisition is inserted successfully with the
requisition with location_obj entity to pass location value passed through the payload.
single location value.

15. Perform UPSERT operation on one of the · The job requisition is updated with the location
existing multiselect location FO field by value passed via the OData payload – location_obj
passing location value via location_obj (old entity.
entity). · The multiple values of the job requisition are
overridden with the one value passed through the
payload.

CONFIDEN TIAL SAP SuccessFactors Testcases

38 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Recruiting Management
8 Recruiting Marketing

8.1 Testcase: Check for creation of a Data Capture Form and

its addition to a Landing Page (RMK-8892 & RMK-12722)

Steps Result/Additional Information

Prerequisites:
1. All necessary CRM configurations are setup.

2. Go to Command Center for the environment under Verify the Use CRM checkbox is selected and saved.
test.
3. Select RCMRMKCSB01.
4. Select Site > Site Setup > Settings.

5. Open a browser and go to: [Link]

[Link]/login?company=RCMRMKCS
B01&password=pwd1&username=athompson.

6. Select Admin Center > Manage Career Site Builder A page displays showing a header for Career Site
link. Builder.

7. Click Global to expand the section. Data Capture Forms is not listed on the left
navigation selection.

8. Click on the Data Capture Form. The Data Capture Form List opens.

9. Click the + (add) to create a new data capture

form.

10. Complete all required fields and click Save. The Data Capture Form is saved successfully.

11. Set the Is Active status to reflect Yes.

12. Click the Layout tab.

13. Click the + (add) and add all necessary fields from The following fields should be available for the user
the selection list and click Save on the upper right to select: First Name, Last Name, Email, Country
corner of the page and Phone and the Data Capture Form is saved
successfully.

14. Click Pages to expand the section.

15. Click the Landing page.

16. Click (en_US) English (United States) locale.

17. Click on Main Brand. The Landing Page List page opens with no issues.

18. Click the + (add).

SAP SuccessFactors Testcases CONFIDEN TIAL

Recruiting Marketing © 2018 SAP SE or an SAP affiliate company. All rights reserved. 39
 Steps Result/Additional Information

19. Enter any text in the Name field.

20. Select any locale from the dropdown.

21. Select any brand from the dropdown.

22. Click Save. The Landing Page Editor page opens and opens to
the Details tab by default.

23. Select Is Active to Yes.

24. Click Publish on the upper right corner of the page. A successful save message is displayed.

25. Click the Column 1 tab.

26. Click Add Component. The Data Capture Form is listed on the component
selection list.

27. Select the Data Capture Form from the list. The grayscale image is added.

28. Click the Data Capture Form grayscale image. The Data Capture Form page opens with a Details,
Styles and DPCS tabs.

29. Click the Details tab.

30. Click the Data Capture Form dropdown and select

the form that was added above.

31. Enter any text in the Data Capture Form Header.

32. Enter any text in the Data Capture Form

Instructions.

33. Click the Styles tab.

34. Select any color from the Body Background color

palette.

35. Select any color from the Button Highlight color

palette.

36. Select any color from the Button Background

palette.

37. Select any color from the Required Field Identifier

palette.

38. Select any field alignment from the Field

Alignment dropdown.

39. Click Publish on the upper right corner of the page. A new window open with a preview of the Landing
Page.
The Data Capture From is displayed correctly on the
Landing Page.
The Landing Page name is listed in the URL.

CONFIDEN TIAL SAP SuccessFactors Testcases

40 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Recruiting Marketing
 Steps Result/Additional Information
The Data Capture Form Header is present on the
preview page for each column.
The fonts are displayed correctly on the forms.
The sizes are displayed correctly on the forms.
The alignments are displayed correctly on the
forms.
The colors are displayed correctly on the forms.
The body background is displayed correctly on each
column.
The button highlight is displayed correctly on each
column.
The button background is displayed correctly on
each column.
The required field identifier is displayed correctly on
each column.
The field alignment is displayed correctly on each
column.

40. Complete all fields on the Data Capture Form and The form is submitted successfully and a thank you
click Submit. message is displayed.

SAP SuccessFactors Testcases CONFIDEN TIAL

Recruiting Marketing © 2018 SAP SE or an SAP affiliate company. All rights reserved. 41
9 Rewarding

9.1 Testcase: Check for new compensation field type to

support EC mapping to translatable GO fields (CMP-
10770)

Steps Result/Additional Information

1. Map EC translatable fields to compensation This field should show the label in the logged in user's
translatable fields and launch the worksheet. locale.

9.2 Testcase: Check for Check Tool for Compensation and

Variable Pay (CMP-17475)

Steps Result/Additional Information

1. Test the newly added checks for worksheet data Check Tool should return the issues with the user
and template formulas. data or template formula configuration.

9.3 Testcase: Check for executive review enhancements

(CMP-17259)

Steps Result/Additional Information

1. Show or hide the executive review export option Both the features should work as expected.
by enabling this feature in action for all plans -
company settings and selecting the correct RBP
permissions.
2. Show or hide the email notification settings by
selecting the template level switch in template
level - advanced settings.

CONFIDEN TIAL SAP SuccessFactors Testcases

42 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Rewarding
10 Talent

10.1 Testcase: Show Employee Profile rating information in

Calibration session (CAL-5250/CAL-5119)

Steps Results/Additional Information

Prerequisites:
Assume that employee A has the following Employee Profile rating:
· Type: sysOverallPerformance
· Time: <2018.02.01-2018.10.31>

1. Log in to the application as Calibration Verify that the Calibration session has been
Admin. activated, successfully.
2. Go to Admin Center > Manage Calibration
Templates.
3. Create a new Calibration template.
4. Set proper Review Period on the Basic Info tab.
Example: 2018.01.01-2018.12.31

Note:
Ensure that start date and end date of
employee A’ Employee Profile rating are
both within the Review Period.
5. Go to the Data tab, select Employee Profile as
the data source.
6. Select several rating types, including
sysOverallPerformance.
7. Configure the other settings in the Calibration
template and save it.
8. Go to Admin Center > Manage Calibration
Sessions section.
9. Create a new Calibration session.
10. Add several subjects to that session, including
employee A.
11. Activate that session.

12. Go to Calibration and open that session. Verify that Source Rating Information appears in the
13. Click the List view. More actions for employee A.

14. Click Source Rating Information. Verify that the Rating Information (including Rating
Type, Source, Rating, Start Date, End Date and

SAP SuccessFactors Testcases CONFIDEN TIAL

Talent © 2018 SAP SE or an SAP affiliate company. All rights reserved. 43
 Steps Results/Additional Information
Modification Date attributes) appearing in a new pop-
up is correct.
Note: Rating type should be selectable if more than
one valid Employee Profile rating types are fetched
into this session.

15. Click the Bin view. Verify that Rating information appears correctly on
the Source Rating Information window, as it appears
for the List view.

Note:
Only one rating type used by the current Bin
view appears in the Source Rating
Information window.

16. Click the Matrix view. Verify that Rating information appears correctly on
the Source Rating Information window, as it appears
for the List view.

Note:
Only two rating types used by current matrix
view will be displayed in Source Rating
Information window.

10.2 Testcase: Verify that MDF Talent Pools (latest UI version)

can be activated using Upgrade Center (SCM-12287/
SCM-10876)

Steps Result/Additional Information

Prerequisites:
· Enable Generic Objects
· Use v12 UI framework

1. In Provisioning, ensure that New MDF pool-based Verify if MDF Talent Pool for Succession Planning
Succession Planning and Enable Fiori-style UI are appears under Optional Upgrades.
not enabled for MDF Talent Pools under
Succession nomination.

Remember
As a customer, you do not have access
to Provisioning. To complete tasks

CONFIDEN TIAL SAP SuccessFactors Testcases

44 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Talent
 Steps Result/Additional Information
in Provisioning, contact your Implementation
Partner. If you are no longer working with an
Implementation Partner, contact SAP Cloud
Support.
2. Log in to the application as Succession Admin.
3. Go to Admin Center > Release Center > Upgrade
Center.
4. Select Succession in the Filter list.

5. Select MDF Talent Pool for Succession Planning. Verify if MDF Talent Pool for Succession Planning
6. Click Upgrade Now. appears in the list of Completed Upgrades.

7. Log out, wait for two minutes, and then log in to Verify the following:
the application. Go to Provisioning and check if New MDF pool-based
Succession Planning and Enable Fiori-style UI controls
have been automatically enabled for MDF Talent
Pools.

Remember
As a customer, you do not have access
to Provisioning. To complete tasks
in Provisioning, contact your Implementation
Partner. If you are no longer working with an
Implementation Partner, contact SAP Cloud
Support.

8. Go to Admin Center > Manage Permission Roles Verify that the Talent Pools tab appears. Go to the
> [Role] > Permission > Permission Settings. The Talent Pool page and verify that you see the new Fiori
Permission settings dialog appears. UI.
9. On the Succession Planners tab, select View
Talent Pool nominations and Add/Edit/Delete
Talent Pool nominations.
10. On the Miscellaneous Permissions tab, under
TalentPool, select View Current, View History,
Create and other proper permissions.
11. Click Done, and then click Save Changes.
12. Log out and log in to the application
13. Go to the Succession page.

14. Go to Admin Center > Upgrade Center > View Verify the following.
completed upgrades. Go to Provisioning and check if New MDF pool-based
15. Select MDF Talent Pool for Succession Planning. Succession Planning and Enable Fiori-style UI controls
16. Click Undo. are automatically disabled for MDF Talent Pools.

SAP SuccessFactors Testcases CONFIDEN TIAL

Talent © 2018 SAP SE or an SAP affiliate company. All rights reserved. 45
 Steps Result/Additional Information

Remember
As a customer, you do not have access
to Provisioning. To complete tasks
in Provisioning, contact your Implementation
Partner. If you are no longer working with an
Implementation Partner, contact SAP Cloud
Support.

17. Log out and log in to the application. Verify that the Talent pool page does not appear.
18. Go to the Succession page.

10.3 Testcase: Information report generation for PMU

external users (PMU-6147/PMU-7555)

Steps Result/Additional Information

Prerequisites:
1. Go to Admin Center > Manage Permission Roles > [Role] > Permission > Permission Settings. The
Permission settings dialog appears.
2. Check the following configurations: Admin Center Permissions > Enable Information on Data Subject.
3. Create a Performance Review form and send Ask for Feedback request to an external user.
4. The external user replies to the email.

1. Go to Admin Center > Data Subject Information > The external user's information (external id, name,
Data Subject, and search for the external user. email address) and related field label name should be
2. Generate the report. displayed properly in the report.

3. Go to the Reports tab.

4. Download the PDF and Microsoft Excel report
file.
Result: Verify that the external user's information
(external id, name, email address) and related field
label name appears properly in the report.

CONFIDEN TIAL SAP SuccessFactors Testcases

46 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Talent
10.4 Testcase: Support 3 Text-Replacement Sets for
Mentoring Programs - configuration (CDP-8975)

Steps Result/Additional Information

Prerequisites:
· The Manage Languages tool is available in Admin Center.

1. Log in to the System as a Mentoring Program Verify if you can edit, save or cancel the settings in
Admin. the Text Replacement Configuration tab.
2. Go to Admin Center > Manage Mentoring For more information refer to the Managing Custom
Programs. Program Types with Text Replacement section of the
3. Click Settings to access the Mentoring Program Mentoring guide.
Configuration page.
4. Click the Text Replacement Configuration tab.

10.5 Testcase: Verify if a warning alert is generated while

enabling the JPB profile (CDP-8665)

Steps Result/Additional Information

Prerequisites:
· Ensure disable-jpb-profile-in-cws is set as off or the switch is not set in career worksheet template.
· Ensure JDM2.0 enabled in system.

1. Go to Admin Center > Check Tool. Verify that a warning link appears on clicking the link.
2. Execute the check for Careerworksheet.

SAP SuccessFactors Testcases CONFIDEN TIAL

Talent © 2018 SAP SE or an SAP affiliate company. All rights reserved. 47
11 Time

11.1 Testcase: Check whether approver name and approval

date appear in addition to the requester name and
request date (TIM-4084)

The Time Workbench in UI v3 did not provide full feature parity to the old Manage Time Off administrator screen in
UI v12. This has now been changed. For leave requests in the Time Workbench, in addition to the requester name
and request date the approver name and approval date are now displayed as well.

11.1.1 OData API for reading requester of Employee Time in

Time Workbench

Steps Result/Additional Information

Goals
The requester is the person of the created by field in the corresponding employee time. For this person first
name and last name should be shown on the workbench in the Time Recordings tab.
· Subgoal1: Request an employee time for yourself. Go to the workbench of this user. The requester name
should be shown correctly as the name the workbench has been opened for.
· Subgoal2: Request an employee time for another user - not for yourself. Go to the workbench of the user
you requested the employee time for. The requester name should be shown correctly. It should not be the
same as the one the workbench is shown for, but the one who requested the employee time.
Prerequisites:
· Ensure Time Off is enabled and admin has all permissions for all Time Types.
· Ensure admin has permission to access Time Off Workbench.

1. Log in to the application as Admin. Login successful.

2. Go to Employee File of an Employee Employee File loads.

3. Click Administer Time. Time Off Workbench loads, Time Records Tab loads

4. Create a new Absence. Absence created and has status "Approved"

5. Check the Absence request. The "Requester" column shows the full name of the
Admin user for the new Absence request.

6. Proxy as above Employee. People Profile loads

CONFIDEN TIAL SAP SuccessFactors Testcases

48 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Time
 Steps Result/Additional Information

7. Click Time Off tile Time Off ESS loads

8. Create a new Absence. Absence created

9. Log in to the application as Admin or "become Login successful

Self".

10. Go to Employee File of above Employee. Time Off Workbench loads, Time Records Tab loads

11. Check the Absence request. In the new Absence request the full name of the
employee appears in the "Requester" column

11.1.2 OData API for reading workflow information of

Employee Time in Time Workbench

Steps Result/Additional Information

Goals
Time Off Workbench, Time Recordings Tab shows for each Absence Request the Absence Request View
Dialog. The Dialog shall show (besides other information) Requester (name), Requested On (date), Approval
Status, Approver (name) and Approved On (date).
· Subgoal1: No workflow, request Absence - Requester = full name, Requested On = requesting date,
Approval Status = Approved Automatically, no Approver, no Approved On.
· Subgoal2: No workflow, cancel Absence - Requester = full name, Requested On = requesting date,
Approval Status = Canceled Without Workflow, Canceled By = full name, Canceled On = date of
cancellation.
· Subgoal3: Workflow, request Absence - Requester = full name, Requested On = requesting date,
Approval Status = Pending, To Be Approved by = full name, no Approved On.
· Subgoal4: Workflow, approve Absence - Requester = full name, Requested On = requesting date,
Approval Status = Approved, Approved by = full name, Approved On = date of approval.
· Subgoal5: Workflow, cancel Absence - Requester = full name, Requested On = requesting date, Approval
Status = Cancellation Pending, To Be Approved by = full name, No Approved On.
· Subgoal6: Workflow, approve cancellation - Requester = full name, Requested On = date of requesting,
Approval Status = Canceled, Cancelation Approved by = full name, Cancelation Approved On = date of
cancel approval.
Prerequisites:
· Ensure Time Off is enabled and admin has all permissions for all Time Types.
· Ensure admin has permission to access Time Off Workbench.
· Ensure one Time Type has no Workflow.
· Ensure one Time Type has approval Workflow and cancelation Workflow.

1. Log in to the application as Admin. Login successful.

SAP SuccessFactors Testcases CONFIDEN TIAL

Time © 2018 SAP SE or an SAP affiliate company. All rights reserved. 49
 Steps Result/Additional Information

2. Go to Employee File of an Employee Employee File loads.

3. Click Administer Time. Time Off Workbench loads, Time Records Tab loads

4. Create new Absence with Time Type "no Absence created and has status "Approved"
Workflow".

5. Check View Absence Popover. Requester = full name of Admin, Requested On =

requesting date, Approval Status = Approved
Automatically, no Approver, no Approved On.

6. Cancel Absence "no Workflow". Absence has status "Canceled"

7. Check View Absence Popover. Requester = full name of Admin, Requested On =

requesting date, Approval Status = Canceled Without
Workflow, Canceled By = full name of Employee,
Canceled On = date of cancellation.

8. Create new Absence with Time Type "with Absence created and has status "Pending"
Workflow".

9. Check View Absence Popover. Requester = full name of Admin, Requested On =

requesting date, Approval Status = Pending, To Be
Approved by = full name of Manager, no Approved
On

10. Proxy as Manager, search for ToDo and approve Time Off Request is approved
Time Off Request.

11. Proxy as Employee and click Time Off Tile Time Off Workbench loads

12. Check View Absence Popover. Requester = full name of Admin, Requested On =
requesting date, Approval Status = Approved,
Approved by = full name of Manager, Approved On =
date of approval.

13. Cancel Absence "with Workflow". Absence has status "Cancellation Pending"

14. Check View Absence Popover. Requester = full name of Admin, Requested On =
requesting date, Approval Status = Cancellation
Pending, To Be Approved by = full name of Manager,
No Approved On.

15. Proxy as Manager, search for ToDo and approve Time Off Request cancelation is approved
Time Off Request Cancelation.

16. Become Self, search for Employee and click Time Off Workbench loads
Administer Time.

17. Check View Absence Popover. Requester = full name of Admin, Requested On =
date of requesting, Approval Status = Canceled,
Cancelation Approved by = full name of Manager,
Cancelation Approved On = date of cancel approval

CONFIDEN TIAL SAP SuccessFactors Testcases

50 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Time
11.1.3 Consider duration display setting of Time Type in Time
Workbench

Steps Result/Additional Information

Goals
The Time Type setting "duration display according to" should be considered correctly on the workbench tab
"Time Recordings".
· Subgoal1: If the Time Type setting shows "Calendar Days", the workbench should show the difference in
calendar days between start date and end date. If this is a one day absence, difference in calendar days is
shown as 1.
· Subgoal2: If the Time Type setting shows "Work Schedule", the workbench should show the taken Days /
Hours, which are stored in quantity in days / quantity in hours field in the corresponding employee time.
· Subgoal3: If the Time Type setting shows "Deduction Quantity", the workbench should show the content
of the "deduction quantity" field in the corresponding employee time.
· +Subgoal4*: The field displayQuantity should not be visible on Workflow UI.
Prerequisites:
· Ensure that on a time profile, there are time types assigned that consider Duration Display According To
Work Schedule, Calendar Days, Deduction Quantity.

1. Log in as a user that has workbench permission. Login should be successful, and navigation should be
2. Go to Administer Time. successful.

3. Create an absence for time type with Duration Absence can be saved and the taken column in the
Display According to Calendar Days. time records table is displayed correct.
For an absence less than one day: decimal fraction is
shown.
For an absence with undetermined end date true:
Unknown label is shown.
For a multiple day absence: The diff between start
date and end date is shown.

4. Create an absence for time type with Duration Check the value that was deducted from the time
Display According to Deduction Quantity. account via time accounts tab.
The deducted value should be the same as in the
taken column in time recordings tab.

5. Create an absence for time type with Duration Ensure that the default behavior has not changed.
Display According to Work Schedule.

6. Open the absence view dialog. Ensure that the taken field in the dialog has the same
value as in the table.

SAP SuccessFactors Testcases CONFIDEN TIAL

Time © 2018 SAP SE or an SAP affiliate company. All rights reserved. 51
11.2 Testcase: Check for linking or grouping of different
sickness leave records for Columbia (TIM-4099)

In Colombia it is necessary to “link” different absence sickness records that got the same illness cause together.
This is relevant for payroll sickness payment calculations. This information is replicated to EC Payroll into the
infotype 2001, field “KENN1”.

Note:
Before testing this enhancement, please refer to the following Knowledge Base Article (KBA):
[Link] The KBA goes through the test step-by-step,
and also outlines the limitations.

Steps Result/Additional Information

Prerequisites:
· Ensure that the user under test belongs to Columbia.
· Ensure that the user has a time type of country Columbia and absence type sickness assigned to his time
profile.

1. Go to workbench as Admin. The reason and absence to be linked are listed. And
2. Choose a time type of sickness and country linking is available only in workbench and not on ESS
Columbia. cases.

3. Click Link Additional Absence. The reason and absence to be

linked are listed.

4. Select the Reason dropdown. The Identical option is available for sickness for
country Columbia.

5. Select the absences to be linked. The absences to be linked lists only the sick leaves of
country Columbia.

6. Click Remove Link in the absence form. It removes these two fields from the form and Link
Additional Absence appears again.

CONFIDEN TIAL SAP SuccessFactors Testcases

52 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Time
11.3 Testcase: Check for additional configurations for
linking/grouping of sickness leave absences for
Columbia (TIM-4099)

Steps Result/Additional Information

1. Edit an already linked absence. Link additional absence is not available.

2. Click the Linked Absence icon in the workbench. The linked absence details are displayed in a popup.

3. Click Unlink while editing a linked absence. The system asks for a confirmation and then unlinks
the absence.

4. Select a Colombia time type which is not a · The link absence option is unavailable.
sickness time type. · The linking works fine for all Permitted Fraction
For Unit Hour & Permitted Fractions For Unit Day.
· Linking works fine for undetermined end date as
well.
· Linking works fine for Leave Of Absence for
sickness and Colombia as well.
· Linking with recurring absences works fine.

11.4 Testcase: Check for setting up of templates for the

Create, Edit, and Delete Notifications with the help of
Notification with Payout Rate Details, and Notification
(without payout rate details) templates (TIM-4089)

Employees will now receive more accurate and informative email notifications depending on whether the
administrator has created, edited, or deleted a time account payout. Therefore, templates for the Create, Edit,
and Delete Notifications need to be set up.

For each case (Create, Edit, Delete), there are two templates: Notification With Payout Rate Details, and
Notification (without payout rate details). ‘Payout rate details’ is referring to the monetary valuation of the
number of hours or days which are deducted from the time account for payout.

Whether the monetary valuation happens already in Employee Central or only later in Payroll depends on the set-
up of the pay component which is used for time account payout.

SAP SuccessFactors Testcases CONFIDEN TIAL

Time © 2018 SAP SE or an SAP affiliate company. All rights reserved. 53
If a pay component with monetary valuation is used, payout rate details can be determined in EC, and thus the
Notification With Payout Rate Details will be generated.
Else, if a pay component which has the number of hours or days only is used, payout rate details are not available
in EC, and thus only the simple Notifcation will be generated.

So, depending on the set-up of their pay components for time account payout, customers need to configure either
one or the other set of notification templates, or possibly both. This configuration task is described in the Time Off
Implementation Guide, section 5.3.3 Setting Up Email Notifications for Time Off.

Note:
Before testing these enhancements, please refer to the following Knowledge Base Article (KBA):
[Link] The KBA answers frequently asked questions
about how to set up the templates for separate email notifications which will now be sent to the
respective employees during creation, edit and deletion of time account payout records.

Steps Result/Additional Information

1. Check that New Payout mail notifications are Mail notifications are created.
created based on the new Email Template for
Create Operation [Accounts Payout tab/Manage
data/oData/import].

2. Check that New Payout mail notifications are Mail notifications are created.
created based on the new Email Template for
Edit Operation [Accounts Payout tab/Manage
data/oData/import].

3. Check that New Payout mail notifications are Mail notifications are created.
created based on the new Email Template for
Delete Operation [Accounts Payout tab/Manage
data/import].

4. Check that New Payout mail notifications are Mail notifications are created.
created based on the new Email Template for
Create Operation [Time Accounts tab].

5. Check that New Payout mail notifications are Mail notifications are created.
created based on the new Email Template for
Create Operation [Termination screen].

6. Check that all the new tags that have been added Mail notifications are created.
as part of Payout notification are resolved while
sending a notification mail.

7. Change the locale of the Admin to some other Mail notifications are created.
language and check that mail notification follows
the Admin's locale.

CONFIDEN TIAL SAP SuccessFactors Testcases

54 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Time
11.5 Testcase: Check for flexible configuration for Time
Account Deduction Sequence (TIM-3743)

When one leave type deducts two or more different time accounts, and time account balances from previous year
exist, customers got the requirement to have the time account with the earliest expiry date to be deducted first. A
posting order based on time account type is not sufficient here, but in addition the configuration possibility to
choose the time account that expires first is required.
Hence not only the order how the deduction sequence is defined in the posting rule is necessary, but also a
configuration which time account shall be deducted first when in addition a remaining balance in same time
account type but from a previous period exist.

Note:
Before testing this enhancement, please refer to the following Knowledge Base Article (KBA):
[Link] The KBA goes through the test step-by-step and
explains how to do it.

Steps Result/Additional Information

1. Verify that a new mandatory field Posting Priority

is added to the Time Types.

2. Select Posting Priority as Post to time accounts Conditional field Posting Order appears in Time Type.
by defined time account type period.

3. Verify the new field values for Bookable Period

(aka expiry date) are added to Posting Order in
Time Account Type, and user is able to select it.
· NEWEST_FIRST: Newest First By Validity Period
· OLDEST_FIRST: Oldest First By Validity Period
· NEWEST_FIRST_BY_BOOKABLE_PERIOD:
Newest First By Bookable Period
· OLDEST_FIRST_BY_BOOKABLE_PERIOD: Oldest
First By Bookable Period

Prerequisites:
In Time Type, select Posting Priority as Post to time accounts by posting rules only.

4. Select Posting Priority as Post to time accounts Bookings on time accounts happen correctly.
by posting rules only in Time Type.

SAP SuccessFactors Testcases CONFIDEN TIAL

Time © 2018 SAP SE or an SAP affiliate company. All rights reserved. 55
 Steps Result/Additional Information
If you select Post to time accounts by posting
rules only, deductions from the relevant time
accounts are posted according to the following
priorities:
· In the order of the time account types listed
under the time type’s posting rules.
· In the posting order for time accounts specified
at each time account type.

Prerequisites:
At Time Type, select Posting Priority as Post to time accounts by defined time account type period.

5. Select Posting Priority as Post to time accounts Bookings on time accounts happen correctly.
by defined time account type period in Time Type.
Note:
If you select Post to time accounts by defined
time account type period, you need to
specify a suitable value for the Posting Order
field at the time type level as well.
6. Deductions from the relevant time accounts are
posted according to the following priorities:
· In the posting order for time accounts specified
at the time type.
· In the order of the time account types listed
under the time type’s posting rules.
· In the posting order for time accounts specified
at each time account type.

CONFIDEN TIAL SAP SuccessFactors Testcases

56 © 2018 SAP SE or an SAP affiliate company. All rights reserved. Time
12 Tools

12.1 Testcase: Check for the synchronization across instances

with same CRM IDs without Provisioning IST
configuration, that is, check the sync between all
instances belonging to same customer (TLS-8928)

Steps Result/Additional Information

1. Log in to the application. The synchronization between all instances belonging

to the same customer is successful.
Note:
Before synchronization, CRM IDs for the
instances need to be updated.
2. Verify that sync is successful within DC and
across DC without Provisioning configuration.
3. Verify sync of existing packages.

12.2 Testcase: Check for addition of the Business Key Details

column, along with auto generated sequence numbers for
ease of identifying the required elements for
synchronization (TLS-9132)

Steps Result/Additional Information

1. Create an MDF Object Definition with external The MDF Data selection page shows additional
code as auto number, define its business keys business key details for Auto Numbered Object
and create its MDF Data. Definitions. Also, the sync of MDF Data for Auto
2. Perform sync of MDF Data. numbered MDF Object Definition with business keys
is successful.

SAP SuccessFactors Testcases CONFIDEN TIAL

Tools © 2018 SAP SE or an SAP affiliate company. All rights reserved. 57
[Link]/contactsap

© 2018 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.
The information contained herein may be changed without prior
notice. 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 or its affiliated companies shall not be liable for
errors or omissions with respect to the materials. The only
warranties for SAP 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.
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. All other product and service names mentioned are the
trademarks of their respective companies. Please see
[Link]/corporate-en/legal/copyright/[Link] for
additional trademark information and notices.