THR80 2311 En-Us
THR80 2311 En-Us
.
.
PARTICIPANT HANDBOOK
INSTRUCTOR-LED TRAINING
.
Course Version: 2311
Course Duration: 5 Day(s)
Material Number: 50163983
SAP Copyrights, Trademarks and
Disclaimers
No part of this publication may be reproduced or transmitted in any form or for any
purpose without the express permission of SAP SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP SE (or an SAP
affiliate company) in Germany and other countries. Please see https://
www.sap.com/corporate/en/legal/copyright.html for additional trademark
information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary
software components of other software vendors.
National product specifications may vary.
These materials may have been machine translated and may contain grammatical
errors or inaccuracies.
These materials are provided by SAP SE or an SAP affiliate company for
informational purposes only, without representation or warranty of any kind, and SAP
SE or its affiliated companies shall not be liable for errors or omissions with respect
to the materials. The only warranties for SAP SE or SAP affiliate company products
and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be
construed as constituting an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any
course of business outlined in this document or any related presentation, or to
develop or release any functionality mentioned therein. This document, or any related
presentation, and SAP SE’s or its affiliated companies’ strategy and possible future
developments, products, and/or platform directions and functionality are all subject
to change and may be changed by SAP SE or its affiliated companies at any time for
any reason without notice. The information in this document is not a commitment,
promise, or legal obligation to deliver any material, code, or functionality. All forward-
looking statements are subject to various risks and uncertainties that could cause
actual results to differ materially from expectations. Readers are cautioned not to
place undue reliance on these forward-looking statements, which speak only as of
their dates, and they should not be relied upon in making purchasing decisions.
Typographic Conventions
Demonstration
Procedure
Warning or Caution
Hint
Facilitated Discussion
ix Course Overview
TARGET AUDIENCE
This course is intended for the following audiences:
● Application Consultant
Lesson 1
Summarizing the SuccessFactors History and Modules 3
Lesson 2
Accessing Provisioning and Instance 6
Exercise 1: Managing Provisioning Access by deleting a person from Provisioning 13
Exercise 2: Managing Support Access 15
UNIT OBJECTIVES
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Download the Course Files
● Provide a brief history of SAP SuccessFactors
● Provide an Overview of SAP SuccessFactors Modules
● Describe SAP SuccessFactors Platform Architecture
SuccessFactors History
The History of SAP SuccessFactors
SuccessFactors was founded in 2001 by Lars Dalgaard. It started as an SaaS performance
management software, but eventually expanded its offerings by providing business execution
software to customers. In February 2012, SAP acquired SuccessFactors, which it renamed to
SAP SuccessFactors. The acquisition was largely considered an opportunity to bring existing
cloud expertise to SAP’s expanding portfolio and allowed SAP to offer a full, cloud-based HCM
suite.
A social collaboration solution, called SAP Jam, was introduced as an integration option in
2012 to help improve the way employees engage with each other and make decisions in the
cloud. The tool allowed team members to share ideas, find solutions to shared business
problems, align their goals, and more.
SAP SuccessFactors again expanded its offerings to include recruitment marketing and
posting, onboarding, and workforce analytics. As of 2019, the latest release of SAP
SuccessFactors included functionality updates for the mobile app, SAP SuccessFactors
Employee Central Service Center, and the recruiting solution, just to name a few.
Architectural enhancements and a new SAP Fiori-based user interface have also been
implemented.
Platform Overview
Animation
For more information on this topic please view the animation in the lesson
Summarizing the SuccessFactors History and Modules in your online course.
The SAP SuccessFactors Platform is the building block of our application suite.
Platform capabilities are grouped under three main areas: Administration, Technology and,
User Experience. These essential platform capabilities are not module specific but can
support the operation of one or multiple modules.
LESSON SUMMARY
You should now be able to:
● Download the Course Files
● Provide a brief history of SAP SuccessFactors
● Provide an Overview of SAP SuccessFactors Modules
● Describe SAP SuccessFactors Platform Architecture
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Access an Instance
● Access Provisioning
● Control access to instances and Provisioning
● Configure changes in Provisioning that will be reflected in the instance
● Log into an SAP SuccessFactors instance
Access an Instance
An instance is the front end, or customer-facing view, of the SAP SuccessFactors system
platform. SAP SuccessFactors customers work together with Professional Services
Consultants (Implementers) to configure their own instance of SAP SuccessFactors.
Consultants, administrators, and end users see the same interface, but just like any other
system, access to tools varies depending on what has been configured.
During configuration, implementers will use the Admin Center to set up and configure some of
the basic system features in the instance. These include:
● Customizing the look and feel of the instance, including company colors, logo, and
customization of the home page
After configuration, administrators will use the Admin Center to modify any features
configured during implementation, if needed, and to initiate and manage company processes
and cycles, as well as maintain system data and users. These include:
● Launching forms
● Importing and updating user information
● Resetting user passwords and accounts
Later in this unit, you will learn more about common tasks and features in the Admin Center.
Company ID is the unique identifier of an instance. Username and Password are the login
credentials associated to each user.
Animation
For more information on this topic please view the animation in the lesson
Accessing Provisioning and Instance in your online course.
Access Provisioning
Provisioning is the key configuration tool that SAP SuccessFactors uses to control many
aspects of the customer instance. In essence, Provisioning is the back end of the system.
Note:
Customers never use Provisioning, nor do they have access to it.
Implementers, Consultants, and Support Representatives use Provisioning for the following
purposes:
● To modify company settings, such as enabling new features
● To turn purchased modules on or off
● To create administrator accounts
● To download and upload templates that contain custom configuration
● To enable language packs
On logging into Provisioning, a list of company instances is visible under the implementer’s
Provisioning account. These are the company instances that are accessible to that specific
implementer.
Select the Company Name link to start configuring the Company Settings.
Note:
Provisioning access is instance-specific. If you have more than one instance in
your SAP SuccessFactors system (Development, Test, Production), you need to
manage Provisioning access separately in each instance.
Procedure
Note:
This is the instruction, not an exercise.
2. Review a list of all the users who have Provisioning access to your instance.
You can see the following information about each user:
● ID
● Username
● Status
Note:
You can only filter using the Include operation and the equal to expression. Do
not use Exclude or change the expression type in the second dropdown menu.
c. In the text field, enter the ID of the user you want to find.
d. Select OK.
Note:
Currently, you can only filter using the Include operation and the equal to
expression. Do not use Exclude or change the expression type in the second
dropdown menu.
c. In the text field, select Active or Locked to view a list of users with that status.
d. Select OK.
5. To view more users, if the list is very long, scroll to the bottom of the page and choose
More.
Procedure
1. Go to Admin Center → Company Settings → Manage Provisioning Access.
4. Confirm that you want to remove the specified Provisioning users by selecting OK.
The specified Provisioning users can no longer access your instance from Provisioning.
Each SAP SuccessFactors user is assigned a username and password for the SAP
SuccessFactors instance of the company. Additionally, each company is assigned a URL and
Company ID. To log into SAP SuccessFactors, enter the Company ID, username, and
password when prompted on the Login screen. The look and feel of your login screen depends
on theme used in the instance.
When the users select the question mark icon from the Login page, they will have access to
the support FAQ link.
It will take them to a web page where they will get answers to the frequently asked questions
about SAP SuccessFactors. This includes information to resolve account and login issues.
Users can be logged in on multiple devices unless restricted by their company.
Now that you know the basics of how your project will run, we will dive into the technical
aspects of implementing SAP SuccessFactors.
Business Example: In this exercise you will get to know how you can manage the access to the
Provisioning.
Result
You have deleted a user from having access to the Provisioning.
Business Example: In this exercise you will get to know how you can manage the access to the
Provisioning.
b) Select one of the users by checking the box in front of the ID.
c) Click on the trash can icon and click on “OK” in the Confirmation Box.
Result
You have deleted a user from having access to the Provisioning.
Business Example
Company administrators need to know how to grant support access, revoke support access
and limit the ability for support personnel to modify Role-Based Permissions.
1. Grant support access to both Alex Anderson and SuccessFactors Admin for 24 hours. Do
not allow them to make modifications to Role-Based Permissions.
2. Use Provisioning to test Support Access for Alex Anderson and SuccessFactors Admin.
Result
You now know how to use Manage Support Access.
Business Example
Company administrators need to know how to grant support access, revoke support access
and limit the ability for support personnel to modify Role-Based Permissions.
1. Grant support access to both Alex Anderson and SuccessFactors Admin for 24 hours. Do
not allow them to make modifications to Role-Based Permissions.
a) Log into your instance. Use Action Search to navigate to Manage Support Access.
b) Click the Add button and in the User Name field enter aaaa and select Alex
Anderson.
e) Click Grant.
f) Click the Add button and in the User Name field enter sfeduadmin and select
SuccessFactors Admin.
h) Under the option Allow this user account to edit RBP settings select No.
j) Click Grant.
2. Use Provisioning to test Support Access for Alex Anderson and SuccessFactors Admin.
a) Access Provisioning and under Customer Instance Access select Log in to customer
instance.
b) In the User Name field enter aaaa and click Validate and review permissions for Alex.
c) Click Login and then click on the Main Menu. Confirm that Admin Center is not
available.
e) Access Provisioning and under Customer Instance Access select Log in to customer
instance.
f) In the User Name field enter sfeduadmin and click Validate and review permissions
for SuccessFactors Admin.
a) Click Login and then click on the Main Menu. Confirm that Admin Center is available.
d) On the Valid List tab in the row for Alex Anderson, select Edit.
e) Change the Expires On: field to one minute in the future and click Save.
f) Wait one minute and select the Expired List tab and confirm Alex has been moved to
that tab.
Result
You now know how to use Manage Support Access.
LESSON SUMMARY
You should now be able to:
● Access an Instance
● Access Provisioning
● Control access to instances and Provisioning
● Configure changes in Provisioning that will be reflected in the instance
● Log into an SAP SuccessFactors instance
Learning Assessment
1. Select the three main areas that can be used to group the Platform capabilities:
Choose the correct answers.
X A Administration
X B Employee Central
X C Technology
X D User Experience
X E Business Rules
Lesson 1
Accessing the Provisioning area 22
Exercise 3: Edit Company Settings and add a New Administrator Account in 25
Provisioning
UNIT OBJECTIVES
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Manage Company Settings in Provisioning
● Create a new admin user from Provisioning
There are many elements within Company Settings that correspond to different modules of
SAP SuccessFactors. To make it easier to find an element, use the browser search function
(Ctrl + F) and search using keywords. Once changes are made to a particular section, click the
Save Feature button for that section. You will be prompted to enter the company ID before
changes can be saved.
1. Supply the necessary details (username and password cannot be the same) and
click Create Admin.
2. Use the new credentials with the company ID to log into the front end.
If you have configured the single recipient e-mail feature the create Super Admin from
Provisioning will not be possible, and you will receive a ‘Exception in creating an Admin user:
failed to send e-mail’ message. To proceed, you may temporarily disable the feature to create
the Super Admin.
Watch the 'Create an Admin User from Provisioning' video for an in-depth explanation.
Business example
You have to access and verify Company Settings in Provisioning.
1. On the Company Settings screen, use the following details to create an Administrator
account (Scroll to the bottom of the Company Settings screen to find where to enter this
information). You can also use Ctrl+F and search for the term "Admin Username" to find
this section of Company Settings.
Admin Username - administrator plus current year (for example
administrator2023)
Admin Password - password plus current year (for example password2023)
Admin First Name – Your first name
Admin Last Name – your surname
Admin E-mail your e-mail address
Check box next to I confirm that customer has provided approval of Super Admin user
account creation.
Add your e-mail address in the Customer E-mail Address field.
Select Create Admin
Note:
If the Create Admin button is not active, make sure all fields are filled out and
then click into the Admin E-mail field (or any other field) and the button will
become active.
2. You will be asked to enter your Company ID to confirm the changes. Please refer to
Company ID by scrolling to the top of the page. You will see the Company ID listed there.
Business example
You have to access and verify Company Settings in Provisioning.
b) In the Language Packs area, ensure the English US (English US) language option is
selected. Also select Deutsch (German) and Español (Spanish). Select Save Feature at
the top of this section and enter your company ID. Note that this page has multiple
Save buttons but only one Save Feature button.
1. On the Company Settings screen, use the following details to create an Administrator
account (Scroll to the bottom of the Company Settings screen to find where to enter this
information). You can also use Ctrl+F and search for the term "Admin Username" to find
this section of Company Settings.
Note:
If the Create Admin button is not active, make sure all fields are filled out and
then click into the Admin E-mail field (or any other field) and the button will
become active.
2. You will be asked to enter your Company ID to confirm the changes. Please refer to
Company ID by scrolling to the top of the page. You will see the Company ID listed there.
LESSON SUMMARY
You should now be able to:
● Manage Company Settings in Provisioning
● Create a new admin user from Provisioning
Learning Assessment
X True
X False
Lesson 1
Getting Started with Administration 34
Exercise 4: Grant Permission to manage Role Based Permissions 45
Lesson 2
Navigating Admin Center, Tiles, and Favorites 49
Exercise 5: Navigate in Admin Center 53
UNIT OBJECTIVES
LESSON OVERVIEW
In this lesson, you will be introduced to administrator basics including system administrator
roles and responsibilities, and common terms specific to SAP SuccessFactors.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Identify Administrator Tasks
● Troubleshoot User Login Issues
● Ensure that consultants and customers use the same SAP SuccessFactors common terms
● Maintain Superadmin, security admin, and module admins
Animation
For more information on this topic please view the animation in the lesson
Getting Started with Administration in your online course.
System Administration
The following responsibilities are relevant to system administration:
● Management and oversight of user information (for example, data imports, passwords,
and notifications)
● Management of user permissions and privileges
● Management of forms, competencies, roles, and system notifications
User Support
The following responsibilities are relevant to user support:
● Provision of necessary assistance and support for all Human Resource (HR) managers
● Implementation of new functionality
● Training and communication to users of new functionality
● Provision of reporting assistance to HR and management users
● Provision of coaching assistance to managers and employees
Reset passwords
As an administrator, it is likely that resetting passwords will be part of your role. There are
three types of password resets available in SAP SuccessFactors.
1. Reset individual user password (with supplied password): To reset one user's password to
a specific new one.
2. Reset individual user password: To reset one user's password to a system-generated one.
3. Reset group of users passwords: To reset passwords for a specific group of users to
system-generated passwords at once. The number of users selected in the group will be
displayed.
The following interaction walks you through the different between those three:
Animation
For more information on this topic please view the animation in the lesson
Getting Started with Administration in your online course.
Users receive system e-mail notifications once their passwords are reset. When users log into
the system, a Password Change window pops up, requiring users to update their passwords. If
security questions have been enabled in the instance, then users will be prompted to choose
security questions before they enter the new password.
Note:
On the Reset individual user password (with supplied password) page and Reset
individual user password page, the Login Method column is available. When
resetting passwords for a group of users, the administrators can see the count of
PWD users and SSO users who are impacted. When resetting passwords for SSO
users, a message indicates that the passwords only impact Basic-Authentication
and token-based SSO.
2. You will be directed to a page in which you can filter employees by division, department,
group, or location, or simply enter their name or job code. Enter search criteria and select
Search Users.
3. The system generates a list of users that match your criteria. A locked out user is
displayed on the list with a red X in the Status column.
4. Choose the users that you would like to reset by selecting the checkbox next to their
name.
5. Select Reset Selected Users to reset and unlock their user accounts.
2. Go to Company Settings.
3. Check on the box for Enable Secondary Login Feature and choose Save.
4. Login as an Admin or guide a customer Admin through the following steps to enable
Manage Support Access:
Note:
If you make the changes yourself, you should still make sure the customer's
Admin is aware of the process. They may want to disable this access in the
future.
5. Access the role you want to add the Manage Support Access permission to.
6. Go to Manage Employees.
Note:
Best practice is to add this permission to the customer’s System
Administrator role.
If enabled, a Support Administrator may have unrestricted login access to a user account until
the access expires or until the customer disables the support access. The customer can
follow the same process but select Disable Support Access to deny us access to the user.
Once the user has been granted Support Administrator access, they can go to Provisioning,
select their customer's instance, and under the section Customer Instance Access, they can
choose Log in to customer instance.
On the Secondary Logon page, they type their username and select Login.
Note:
You must have Provisioning Access for this to work.
You can grant or remove support access using the Manage Support Access admin tool. In this
tool, there is also an option to filter user accounts that have support access called: Show
Users with Valid Support Access. With this option you can quickly filter all user accounts that
have support access.
Figure 13: Show Users with Valid Support Access in Manage Support Access
Terms Definitions
Enable Upgrade Center Permission If this feature is enabled, users can use the
tool “Upgrade Center” if the according per-
missions are enabled.
Hide Username in the UI If this feature is enabled, username won’t be
displayed in the Global Header and the em-
ployee quickcard. You cannot run a user-
name search or see the username in the
search results in the areas that have adopted
People Search, which include the Global
Header, Org Chart, People Profile, Change
Audit, and others.
Security Scan of User Inputs If this feature is enabled, user input that con-
tains the following content will be validated
and harmful content will be filtered, and rele-
vant API requests will fail.
● SQL injection Cross-site scripting (XSS)
● XML external entity (XXE) injection
● CSV injection (also referred to as formula
injection, occurs when a website embeds
untrusted input inside CSV files)
Terms Definitions
Proxy The proxy function allows one employee to
act on behalf of another.
Home Page The Home Page is the default starting page
of the SAP SuccessFactors HXM Suite. For
employees, the Home Page is the main entry
point to the SAP SuccessFactors application
and is generally the first page they see after
logging into the system. It shows pending
tasks, highlights recent activities, and helps
users access common functions or areas of
an instance quickly.
Org Chart The Org Chart provides an interactive view of
the organizational hierarchy and reporting
relationships, including matrix managers, for
your users.
Picklist A picklist is a configurable set of options from
which a user can select, typically in a drop-
down menu or smart search list.
Metadata Framework (MDF) The Meta Data Framework (MDF) is a plat-
form functionality that allows consultants
and customers to extend existing Success-
Factors HXM suite capabilities. The main
building blocks of these extensions are called
Generic Objects (GO).
User Data File (UDF) The UDF is a comma-separated value (.csv)
file and is used to add or change data for one
or more employees’ records at a time. It is
created manually or as an automated output
from your Human Resources Information
System (HRIS).
Form Templates These templates contain the layout, sections
and fields for each form. They are used to
create individual forms for the target popula-
tion.
Forms In some areas of Admin Center, forms are re-
ferred to as documents. They are created
from form templates and are used to record
information, including employee perform-
ance evaluations during review cycles.
Job Code This is a code assigned to each employee
that is often mapped to a job role. Competen-
cies are also mapped to job roles so a user’s
job code can be used to determine the cor-
rect competencies to add to a user’s per-
formance form automatically.
Terms Definitions
Line of Sight This describes the reporting visibility of an in-
dividual within SAP SuccessFactors. For ex-
ample, managers can view direct reports and
those below.
Rating Scale This determines the values, and meanings at-
tached to those values, that will be used dur-
ing performance evaluations and other areas
where ratings are required.
Role Names Role names are used in multiple modules and
control various permissions:
● E — Employee
● EM — Employee’s manager
● EH — Employee’s HR representative
Business example
Your customer wants to start with Role Based Permissions (RBP) and needs access to the
tools so they can manage Role-Based Permission access.
1. Use the Action Search to navigate to Manage Permission Roles and select the Full System
Administrator role.
Result
You have successfully searched for your admin user and granted them access to manage
Role Based Permissions.
Business example
Your customer wants to start with Role Based Permissions (RBP) and needs access to the
tools so they can manage Role-Based Permission access.
1. Use the Action Search to navigate to Manage Permission Roles and select the Full System
Administrator role.
a) Select the Permission button.
b) In the Administrator Permissions section select the Manage System Properties link.
b) Select Control Provisioning Access. This gives the ability to control which users have
Provisioning access.
c) Select Done.
c) On the Manage Role-Based Permission Access screen, verify that you see the user
administrator2023 that you created from Provisioning. Otherwise, choose Add
User.
b) Make sure that the check-boxes for Role-Based Permission Admin (view) and Role-
Based Permission Admin (Edit) are enabled for the administrator2023.
Result
You have successfully searched for your admin user and granted them access to manage
Role Based Permissions.
LESSON SUMMARY
You should now be able to:
● Identify Administrator Tasks
● Troubleshoot User Login Issues
● Ensure that consultants and customers use the same SAP SuccessFactors common terms
● Maintain Superadmin, security admin, and module admins
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Access the Administration Center
Administration Center
Access Administration Center
Employees with any administrative privileges have the Admin Center option in the Home
navigation menu as well as the Name menu.
The Administration Center page shows links only to the administrative features for which the
administrator has permission. Remember, you can only access pages which you have
permission to access.
Admin Center
Admin Center is the central access point to a wide range of administrative features and tools
that can be used to configure and maintain the SAP SuccessFactors application. Admin
Center can be used to monitor overall system health and manage cross-suite or third-party
integrations.
The Admin Center provides customers easy access to any part of their SAP SuccessFactors
system.
Admin Center
Admin Center, known as Next Gen Admin prior to the 1H 2022 release, is now the only
available version available.
Tool Search
To search for an admin tool, use the Tool Search box. When you begin to type the name of the
feature, the system automatically attempts to complete what is typed. For example, when
searching for the feature Manage Recruiting Groups, the system produces a list of possible
outcomes, with a description of the highlighted feature. Although the results when using this
tool will be similar to the results when using Action Search, the results of a Tool Search will be
more narrowly focused on results from Admin Center.
Admin Favorites
You can add tools as Favorites and see recently used tools in the Admin Center. You can also
select a tools category from the search results to see corresponding links, instead of scrolling
through the lists of links within the nested categories.
This gives Admins the ability to add more of their frequently used tools to their Favorites list,
as well as see all of the search results for a particular tool without having them separated
across the page.
Note:
Please do not enable features or provisioning switches unless asked to do so in
THR80 exercises. If you do so, some exercises will not work as expected. For
example, if you activate Employee Central, the employee import exercise in Unit
4 will not work as written.
Business Example
In this exercise you will navigate through the different tools of Admin Center to get some
familiarity with its features.
1. Log into your instance. Use Action Search to navigate to Admin Center or alternatively use
the Home navigation menu in the upper left of the page. Locate the Tools tile and type
homepage in the Search Tools field. You will see Manage Home Page as a result.
2. Now search in Action Search for homepage and notice you get more than one result. The
Tools tile will limit search results to items found in Admin Center whereas Action Search
will not.
3. Select See All on the upper right-hand corner of the Tools tile. This will show you all the
administrator tools available in the system depending on the enabled modules and
permissions granted to the logged in user.
4. Under the 360 Review section place your cursor over Manage Templates and observe the
grey star that appears. Click on it to make it a favorite. Notice that 3 stars now appear in
Tools since Manage Templates appears 4 times under 4 different sections.
5. Press the Esc key from your keyboard or select the close icon (X) in the upper right corner
of the Tools window. Manage Templates is now set to your favorites.
Note:
Please do not enable features or provisioning switches unless asked to do so in
THR80 exercises. If you do so, some exercises will not work as expected. For
example, if you activate Employee Central, the employee import exercise in Unit
4 will not work as written.
Business Example
In this exercise you will navigate through the different tools of Admin Center to get some
familiarity with its features.
1. Log into your instance. Use Action Search to navigate to Admin Center or alternatively use
the Home navigation menu in the upper left of the page. Locate the Tools tile and type
homepage in the Search Tools field. You will see Manage Home Page as a result.
2. Now search in Action Search for homepage and notice you get more than one result. The
Tools tile will limit search results to items found in Admin Center whereas Action Search
will not.
3. Select See All on the upper right-hand corner of the Tools tile. This will show you all the
administrator tools available in the system depending on the enabled modules and
permissions granted to the logged in user.
4. Under the 360 Review section place your cursor over Manage Templates and observe the
grey star that appears. Click on it to make it a favorite. Notice that 3 stars now appear in
Tools since Manage Templates appears 4 times under 4 different sections.
5. Press the Esc key from your keyboard or select the close icon (X) in the upper right corner
of the Tools window. Manage Templates is now set to your favorites.
LESSON SUMMARY
You should now be able to:
● Access the Administration Center
Learning Assessment
1. Which of the following is the customer’s space on the SuccessFactors server? It is also
referred to as the “front end.”
Choose the correct answer.
X B Instance
X C Provisioning
X D Home Page
2. Which of the following spaces on the SAP SuccessFactors server is referred to as the
“back end”?
Choose the correct answer.
X A AdminOne
X B Instance
X C Provisioning
X D Home Page
3. The customer has purchased a language pack and needs it to be enabled in the system.
Who can enable it?
Choose the correct answer.
X A End users
4. You are a consultant implementing a module for ACME Corporation and your
administrator account is locked. What can you do to recover it?
Choose the correct answer.
X D Upload templates
Lesson 1
Managing security using SAP SuccessFactors Role-Based Permissions (RBP) 60
Exercise 6: Working with Role Based Permissions 85
Lesson 2
Using Proxy Management 89
Exercise 7: Assign and Delete a Proxy 95
Lesson 3
Managing Company Systems, Logo settings, and Platform Feature Settings 99
Exercise 8: Change instance-wide settings by using Company System and Logo 103
Settings or Platform Feature Settings
UNIT OBJECTIVES
LESSON OVERVIEW
SAP SuccessFactors, Human Experience Management solutions from SAP offer various types
of administrator roles. This lesson provides an overview of administrator types, how to
manage user permissions using Role-based Permissions (RBP), and how to view permissions
for a specific user.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Manage Security with SAP SuccessFactors Role-Based Permissions (RBP)
● Create Permission Groups
● Describe SAP SuccessFactors permission roles
● Verify the roles that grant a permission with User Role Search
Administrators
SAP Successfactors offers different levels of administration to manage the amount of control
each user has in the system. There are three basic levels of system administration:
● Super Administrator
The Super Administrator is created in Provisioning. This administrator grants permission
to others to become a Super Administrator, Security Administrator, or a regular
administrator.
● Security Administrator
The Security Administrator is responsible for managing all security through roles and
permission groups in the Role-Based Permission framework.
● Administrator
An administrator is a user who has access to the Admin Center page in SAP
SuccessFactors.
When the Super Administrator logs in for the first time, only one link on the Administrator
Permissions page is visible. This is Manage Role-Based Permission Access. Choose the link to
assign an employee the permission to function as a Security Administrator.
● The role defines access to data and functionality. This is where you define what you want
your role to do in SAP SuccessFactors. For example, should the role be allowed to view
dashboards?
● Once the role is defined, you grant the role to groups of users represented by the Granted
Users circle.
● Lastly, you restrict the granted users to perform the role on target users. For example, you
may decide that managers (Granted Users circle) can view dashboards (defined in the
role) on their team Target Users circle).
● Groups can be dynamic which allows us to automate the assignment of permissions. For
example, a group of granted users can be “All employees in the Sales department”. As
employees are transferred into and out of the sales department, their permissions will
automatically adjust.
● Administrators can define many roles.
1. Create Groups: Create a group and grant it the required permission, then create groups to
be managed by users with those permissions.
2. Create a Permission Role: Define the different roles. Permission roles define access to
data and application functionality.
3. Grant the Role to a User or Group: Add the target group created in step one with the roles
created in step two. This is also referred to as linking the role to a target population.
Think of this process as who (the permission group) can do what (permission role) to, or for
whom (the target population).
The SAP SuccessFactors Role-Based Permissions implementation guide available on SAP
Help Portal holds the comprehensive list of RBPs used across the SAP Successfactors HXM
suite.
To access the features "Manage Permission Groups", "Manage Permission Roles", "User Role
Search", and "View User Permissions", users must be added to the group of users allowed to
access the feature Manage Role-Based Permission Access available from the Action Search.
When selecting Add User and granting the permission, the new user will be in the list, with
Role-Based Permission Admin box checked.
If you select the check box for Allow Access to This Page, then the users will be able to add or
remove other users from the group with access to the feature. As a security precaution, the
recommendation is to have at least two users with access to this page.
The RBP admin is not able to uncheck their own access to the page (since it will forbid them to
view this page, thus not able to grant the access back). The checkbox needs to be always
checked and not able to change (marked in gray).
A new feature added in the 1H 2022 release is RBP Notification Settings. For permission role
changes that impact a large number of access users, you can now enable double-
confirmation popups and e-mail notifications for RBP administrators. You can also set a
threshold for triggering these notifications. For example, you can set the threshold to 80%,
and notifications will be triggered if 80% or more employees are impacted by a permission
role change.
Watch the 'Manage RBP Access for a New Admin User' video for an in-depth explanation.
Permission Groups
In the SAP SuccessFactors RBP framework, permission groups are used to define groups of
employees who have the same group of permissions. For example, you can create a
permission group called US Compensation Managers to include all US-based managers who
have access to compensation information. Similarly, you can create permission groups that
define the target population accessible to a granted user group, or user. For example, a US
Employee group that the US Compensation Managers group oversees.
Permission groups also allow you to group employees who match a pre-defined condition.
You can create this condition from a single parameter such as HR for an HR department. Or
you can have multiple conditions. For example, you can create a US HR group with the
conditions of department and location, to create a group that includes only HR employees in
the US. You can add further parameters to refine the group. For example, to limit the US HR
group to include only US HR employees who have access to the financial department, this
creates US HR Finance.
Note:
SAP SuccessFactors allows administrators to manage RBP security setting
changes, such as assigning users to roles and creating permission groups,
through an Application Program Interface (API).
<dg-filters>
<my-filter>
<standard-element-ref refid="custom01"/>
<standard-element-ref refid="custom03"/>
</my-filter>
<permission-group-filter>
<standard-element-ref refid="custom02"/>
<standard-element-ref refid="custom04"/>
</permission-group-filter>
</dg-filters>
Used to specify the fields that can appear in the RBP Permission Groups UI. You specify fields
here by adding <standard-element-ref> or <hris-element-ref> sub elements (if
Employee Central is enabled).
• <my-filter>
Used to specify the fields used in the My Groups feature, which is a separate, unrelated
feature.
You can modify the parameters of a permission group at any time. The following list includes
some additional modifications:
● Permission group name
● The conditions that determine the members of the permission group
● Inclusion of members to the permission group
● Exclusion of members from the permission group
When the company goes through organizational changes that alter the access requirements
for certain systems, or groups in SAP SuccessFactors, it becomes necessary to modify
permission groups. For example, if the company merges two departments, US Finance and
Canada Finance, into a new North America Finance department, an administrator can modify
the permission group US Finance to North America Finance by including Canadian Finance
employees in the US Finance group.
Static permission group must be created by file import in Admin Center → Manage
Permission Groups → Import Static Groups.
Members can be added or deleted by editing the group through UI.
Permission Roles
RBP uses permission roles to group a set of permissions. After grouping the permissions into
a role, you can assign the role to a group of users, granting them access to certain tasks and
features in your system.
Permission roles consist of a set of permissions that give employees access rights to an
employee or a group of employees. As such, an employee or a group that has been granted a
permission role has access to certain aspects of the SuccessFactors application or to aspects
of employee data. With this access, they can perform functions within the application for
other groups of employees.
Role-Based permissions allow you to grant a role to a specific employee, a manager, a group,
or to all employees in the company. The roles can provide very granular permissions, as this
example illustrates:
Example: There may be roles such as ‘HR Compensation and Benefits Manager’, ‘HR Manager
for Sales’, and ‘HR Learning and Development Manager’. While all three are HR managers,
their roles have been distinctly carved out — one handling compensation and benefits,
another handling the sales team, and the third handling Learning and Development.
When your permissions roles consist of one or more permissions that require a target
population, you'll need to specify a target to complete creation of the role. Roles that require a
target population will contain a permission that gives a group access to perform actions or
view information for other employees.
Example: A Manager may have a role where one permission allows the manager to modify the
salary for all of their direct reports. In this example, the manager's direct reports represent
the target population needed for the permission role.
Customers can have as many permission roles as the company requires.
Figure 30: Unique Identifiers for Permission Roles and Role Assignments
This section describes SAP SuccessFactors permission roles and how to use them:
● Create permission roles
● Modify, copy, and delete permission roles
● View user permissions
In SAP SuccessFactors, permission roles control access rights that allow an employee, or
group of employees, to perform certain functions. They also control who can view the data
belonging to other employees.
Some topics to consider before granting permission roles are as follows:
● The different roles in the company
● The employees who are assigned to each role
● Whose data the employees can access
After all concerns are addressed, permission role creation is fairly easy. It is important to limit
the number of permission groups and roles that are created. If too many roles are created,
there is a risk of overlapping permissions and inconsistent access within groups. This makes
modifying and deleting permission as needs change more difficult, because each overlapping
role requires research to verify that they are all changed, or deleted to meet the new
requirements.
Note:
If you want to grant a role to a named user, you first have to create a group and
add the user to this group. Then you can grant the role to the just created group.
Target Population: Depending on the permissions included in the role, you might also have to
define the target population. Not all permissions require you to define a target population. For
example, if the permission includes just the access to an application (such as the Learning
Access Permission), there is no need to add a target group. For certain permissions, in the
Permission settings screen, a target population must be defined. This is identified by the "t"
icon next to the permission name with the following text displayed:
t = Target needs to be defined
Relationships: Access groups can be defined using relationships (for example, manager-
employee relationship). These relationships can be hierarchical or non-hierarchical.
When a permission role is assigned to everyone or to a dynamic group, you will have the
following options for the target population:
● Everyone
There is also an option to "Exclude granted users from having the permission access to
themselves". This is an interesting option for some organization when we speak of the
potential for example. A group of HR Managers should be able to see the potential information
of everyone in their location but not their own potential rating.
Figure 34: Target Population for Everyone or for a Specific Permission Group
3. In the ‘Grant this role to’ section of the Permission Detail screen, choose Add.
4. When the Grant this role to screen displays, select Permission Group.
5. Choose Select to select the access groups you wish to assign to this permission role.
You can allow managers to have the same permissions and define how many levels up in
the hierarchy you want this permission to be granted. However, allowing respective
managers to have the same permissions may have a negative impact on the performance.
The hierarchy then has to be checked whenever such a manager tries to access an
element which was permissioned this way.
6. Exclude Granted Users: For some permissions, it might be necessary to exclude the
granted users from applying the permissions on themselves. For this, select Exclude
Granted User from having the permission access to themselves.
Example:
If the role grants permission to edit the salary, you want to prevent the members of this
permission group to be able to edit their own salary as well.
7. Choose Done to assign this role to the defined users. You are taken back to the Permission
Role Detail page.
Next Steps:
If required, assign a target population to your role.
3. In the Grant this role to.... section of the Permission Detail screen, click Add.
5. Choose Select to select the target groups that you want to assign to this permission role.
7. Choose Done to assign this role to the defined users. You are taken back to the Permission
Role Detail page.
Watch the 'Create a Permission Role and Grant this Role to a Group' video for an in-depth
explanation.
The latest Role-Based Permissions now allows you to activate and deactivate role
assignments of a permission role in bulk. Previously, you could only update the status of
assignments one at a time. This will help you to manage the status of role assignments more
easily.
3. Select a Role and the Permissions and Assignments tabs will display.
If the company has complex roles and a new similar role is required, a considerable amount of
time is saved by copying and modifying an existing role, instead of creating a new one from
scratch. To do this, copy the role definition, and then add or remove permissions as the role
requires.
Note:
Since it is possible for an employee to be part of multiple permission groups
simultaneously, caution should be used when copying roles. If permissions are
overlooked, or adding or removing a permission is forgotten, the new role will not
behave as expected.
As the company grows, some permissions roles are no longer required. To ensure that an
antiquated role is not accidentally used, it is sometimes best to delete the role. Carefully
review the permissions considered for deletion and ask the following questions:
● Is anyone still using this role?
● Can the role be modified instead of deleted?
Note:
If there are users still using the role, or if it is better to modify the role, do not
delete it.
Permission Settings
The Company Info Access and User Search Role sections contain the Company Info Access
permission and User Search Target Population permission. The Company Info Access
permission controls access to the Company Info page. The User Search Target Population
permission provides a target population for any user searches that do not have a separate
permission control. It also controls access to the one box people search feature.
The following search-related features are not shown if the user does not have User Search
permission:
● The global people search feature in the top navigation user interface (UI)
● Settings → Proxy
● Settings → Groups
A permission role can have many role assignments. A Role-Based Permissions administrator
can use the search, sort, or filter functions to narrow down role assignment search in the
latest Role-Based Permissions.
For further information check: Searching, Sorting, and Filtering Role Assignments
1. Go to Admin Center.
4. In the Selection session of the tool, enter the Access Users whose roles you are
comparing.
5. Choose the Search Roles button. The search result will display which roles, if any, grant
the specified permission to either user. In the following example, you can see that both of
the selected access users have permission to view address data.
6. If a user does not have the specified permission, it is indicated as ‘no result.’
7. You can also specify one target user, in order to see whether either of the two access
users has the specified permission for the specified target.
Configuration requirements
A permission role change record is created when you add or remove permissions or role
assignments of a permission role. But only permission changes are highlighted when you
compare two versions. So, after you add a role assignment to a permission role, and compare
the current version with the previous record, no change is highlighted.
Avoid redundancy For additional roles, work on an exception basis and include only the
unique extra permissions that the role should have beyond other
roles. This practice will help reduce the number of roles in the sys-
tem, which will both be easier to maintain, and will help improve sys-
tem performance.
Note:
It is important to keep in mind that the stronger permis-
sions always wins.
No overlap between A user should not get the same permission from different roles. If
roles users have multiple roles and get the same permissions from differ-
ent roles, this slows down the system response time for these users.
Limit the number of In general, keep the number of groups and roles as low as possible.
groups and roles This will both reduce the maintenance effort and ease the trouble-
shooting in case of any issues. Remember, that you can grant a role
to multiple groups, so you do not have to duplicate roles just to as-
sign them to different groups.
From a performance point of view, we recommend a maximum of
1000 dynamic permission groups. Dynamic groups are based on
rules in contrast to static groups which contain named users. These
static groups do not count against the 1000 recommendation. Note
that this is not a hard limit, it is a guidance recommendation. The sys-
tem will allow you to exceed 1000 dynamic groups, but the conse-
quences of exceeding 1000 dynamic groups will be to reduce system
performance.
Naming Conventions Agree on a naming convention for groups and roles. This makes the
maintenance much easier, especially for large implementations. For
groups, you could, for example, use the prefixes "Granted:" and "Tar-
get:"
Meaningful Group Meaningful group and role names and role descriptions help custom-
Names, Role Names, ers to identify the correct groups and roles later during maintenance
and Role Descrip- and troubleshooting. The role descriptions should state clearly the
tions purpose of the role and not just repeat the role name. Additionally,
advise the customers that they maintain a change login the role de-
scription field. It should include the change, the date, and who made
and approved the change. The "View change history" function also
delivers this information; however, looking up the description field is
much quicker.
Governance It's key that customers define a governance on RBP as soon as possi-
ble within the project. They should define how changes to RBP will be
handled in the future: Who should be able to make changes? How can
a change be requested? Who needs to review it and needs to be in-
volved in deciding whether to make the change or not? These ques-
tions are especially important in large organizations where the de-
partments tend to be separated from each other. If one department
requests a change, this might also have an impact on other depart-
ments, so all parties need to agree on it.
Some customers may also want to introduce the concept of separa-
tion of duties for the administration of RBP. How to achieve this is de-
scribed in the Special Requirement: Separation of Duties in RBP Ad-
ministration chapter.
Run the RBP Check The RBP check tool section in this guide provides information on how
Tool to run RBP checks and maintain good system performance. This tool
provides a report that highlights all potential risks for the specific
RBP configuration settings.
Note:
E-mail Notifications: As a Role-Based Permission (RBP) administrator, you can
now enable e-mail notification for changes to large-size permission groups. A new
Role-Based Permission Notification – Group Change e-mail template is now
available under Admin Center → E-mail Notification Template → Settings.For
additional Information on E-mail Notifications, please see: Configuring E-Mail
Notifications | SAP Help Portal
You can easily check your work by viewing the permissions for a specific user in SAP
SuccessFactors. You can do this through Admin Center → Set User Permissions and using
the View User Permission function.
In the View User Permission page, search for a user or a user group with Advanced Search.
To view the permissions of a user, select View Permission.
View Permission
You can change the permissions for an individual, and then verify the change from the View
Permissions page.
Business Example
Security Administrators must know how to create and manage permission groups and
permission roles.
2. Create a Permission Role and assign the Permission Role to a Permission Group Part 1 of 2
3. Create a Permission Role and assign the Permission Role to a Permission Group Part 2 of
2
Result
You have successfully created a permission group, a permission role, and mapped the group
to the role..
Business Example
Security Administrators must know how to create and manage permission groups and
permission roles.
d) In Choose Group Members, under People Pool, select the category Department.
e) In the keyword search field, click on the magnifying glass to see the list of
departments.
j) Click close.
2. Create a Permission Role and assign the Permission Role to a Permission Group Part 1 of 2
a) Use Action Search to navigate to Manage Permission Roles.
c) Under1. Name and description in the Role Name field enter Human Resources. In the
Description field enter Human Resources Role for THR80.
e) Under User Permissions click General User Permission and check the box Select All to
select all permissions in the General User Permission category.
f) Click Done.
3. Create a Permission Role and assign the Permission Role to a Permission Group Part 2 of
2
a) Under 3. Grant this role to…click the Add… button.
b) Under 1: Define whom you want to grant this role permission to. click the Select…
button..
c) Select Human Resources. After selecting it, confirm it appears under Selected Items.
d) Click Done.
e) Under 2: Specify the target population whom the above granted users have permission
to access. select Everyone.
f) Click Done.
Result
You have successfully created a permission group, a permission role, and mapped the group
to the role..
LESSON SUMMARY
You should now be able to:
● Manage Security with SAP SuccessFactors Role-Based Permissions (RBP)
● Create Permission Groups
● Describe SAP SuccessFactors permission roles
● Verify the roles that grant a permission with User Role Search
LESSON OVERVIEW
In this lesson, you will learn how to manage proxies in SAP SuccessFactors.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Act as a proxy in SAP SuccessFactors
● Use Proxy tools to Assign and Remove Proxies
Note:
This proxy is independent from the proxy within the SAP SuccessFactors Learning
Management System (LMS). For more information on the proxy in the LMS,
please refer to the LMS training.
The proxy is the employee acting on someone's behalf; the account holder is the employee on
whose behalf the proxy is acting. For example, John will be on vacation and Sarah is assigned
to act on his behalf. John is the account holder and Sarah is the proxy. One or more proxies
can be assigned to a single account, and one employee can be assigned as a proxy for several
accounts. As an administrator, you are likely the proxy for many account holders. The proxy
can open, view, edit, and send any item to which he/she has permission as if he/she were that
account holder.
- Private Objectives
- Career Development Planning
● Reports/Dashboards
● Employee Central
● Succession Management
● Compensation
● Recruiting
Proxy Assignment
Administrators can assign proxies singly, or they can assign multiple proxies at one time.
Administrators must consider the following concerns when assigning proxies:
● The proxy is able to open, view, edit, and send any item in the account of the account
holder.
● The administrator can specify whether the proxy has access to the private goals of the
account holder.
● Where multiple proxies are assigned to an account, all the proxies can edit data at the
same time. In this case, the changes of the last proxy to save a document, overwrites the
changes made by all other proxies.
● The audit trail that automatically accompanies any action taken in SAP SuccessFactors
clearly indicates actions carried out by a proxy.
● Administrators can assign proxy rights to a user for specific tools, or areas of an account.
Additionally, for Performance Manager Forms, there is an option to select a specific form
template.
● Proxy rights can be time-based.
To start the process of assigning an individual proxy from the Action Search, go to Proxy
Management
At the top of the Proxy Management page, identify the proxy and the account holder. Select
the module(s). Optionally, select the date range. Select Save.
Note:
It is not possible to add a start or end date when a proxy is assigned from the
personal user settings. Time ranges can only be added centrally by a proxy
administrator.
Proxy Removal
To delete or remove a proxy, look up the existing proxy assignment. To do this, open the
Proxy Management page and enter a username in the Look up Existing Assignments section.
When the username is not known, choose Find User... to look it up. There are different ways to
look up existing proxy assignments:
● Search for a proxy and see all of the users to whom they have access.
● Search for an account holder and see all of the users to whom they are assigned.
Once the search is completed, the option to delete a proxy becomes available.
Figure 48: New Warning and Error Messages for Proxy Import
For further information check: Creating, Editing, or Deleting Proxy Assignments with an
Import File
Animation
For more information on this topic please view the animation in the lesson Using
Proxy Management in your online course.
The proxy import file contains column headers for USERID, ASSIGNMENT_ID_USERID,
PROXYID, ASSIGNMENT_ID_PROXYID, START_DATE(yyyy-MM-dd HH:mm),
END_DATE(yyyy-MM-dd HH:mm), All, Remove All, and individual module headers.
• USERID: is the account holder indentified by the User ID.
• PROXYID: is the proxy, identified by the User ID. Multiple proxies can be assigned to a single
account holder using the “|” (pipe symbol) between proxy USERIDs.
• ASSIGNMENT_ID_USERID and ASSIGNMENT_ID_PROXYID: Alternatively, employees can
be identified by Assignment ID instead of User ID. To use Assignment ID, leave USERID and
PROXYID blank and enter values in the ASSIGNMENT_ID_USERID and
ASSIGNMENT_ID_PROXYID columns instead.
• START_DATE(yyyy-MM-dd HH:mm) and END_DATE(yyyy-MM-dd HH:mm): These columns
are optional. For each row, set a time range for the proxy assignment. You can add a
START_DATE, an END_DATE, or both, in yyyy-MM-dd HH:mm format. By default, proxy
assignments start as soon as they’re created and have no end date. Use this option to restrict
proxy assignments to the specified time range.
• All: is used to assign proxy rights to all of the tools of the account holder within SAP
SuccessFactors.
• Remove All: deletes proxy rights of the user for the specified account holder. As of the 1H
2022 this includes the ability to remove proxy assignments for inactive users.
Tool headers allow assignment of proxy access by tool. To grant proxy access, enter YES in
the ALL column, or any of the specific tool columns. NO is implied by a blank field and is not
entered into the file. To remove proxy access, enter YES in the REMOVE_ALL column.
When the option is unchecked allowing users to assign their own proxies, an employee will
access the page to assign and remove proxies by going to the Name Menu → Settings →
Proxy. From here, the employee can Assign Proxy to allow another employee to act on his/her
behalf or Become Proxy to act as a proxy for an employee to which he/she has been granted
proxy access via Proxy Management, Proxy Import, or Assign Proxy in Settings.
When using their personal account settings, users can also restrict proxy assignments to a
specified time range when they assign a proxy to act on their behalf. They can add a start
date, an end date, or both when they assign a proxy on the Settings page. The assigned proxy
can only access their user account during the specified time range.
Many customers require that proxy assignments have an end date, for compliance purposes.
When selecting Become Proxy, the employee will then see a dropdown menu of users they
can proxy as.
Proxy Now
If the checkbox within Proxy Management, Enable Advanced Proxy Management (Proxy Now
and Proxy Import is checked, a user with proxy rights will also be able to access proxy via the
Name Menu.
Additional Information can be found in the following guide on the SAP Help Portal:
Managing and Using Proxy Assignments
Business example
Proxy access can be assigned by administrators or end users to allow employees to perform
tasks in an instance on behalf of other employees.
In this exercise, you assign a proxy to act on behalf of Manny Manager and define which
modules the proxy can access in the account. You also change the proxy setting for the
company.
2. Choose which modules that the proxy can access on behalf of Manny Manager and define
the date range.
Result
You can now assign proxy access to various modules for specific date ranges and test those
assignments.
Note:
The HR Coordinator may still proxy as Manny Manager because of the Proxy
Management permission in RBP.
Business example
Proxy access can be assigned by administrators or end users to allow employees to perform
tasks in an instance on behalf of other employees.
In this exercise, you assign a proxy to act on behalf of Manny Manager and define which
modules the proxy can access in the account. You also change the proxy setting for the
company.
b) In the field: Who will act as the proxy (username), select Find user and enter
Coordinator in the last name field.
c) Select Search.
g) In the field: What account holder will the proxy act on behalf of (username), select the
Find User button and in the Last Name field, enter Manager.
h) Select Search.
2. Choose which modules that the proxy can access on behalf of Manny Manager and define
the date range.
a) On the Proxy Management page under Grant Proxy Rights: Grant rights to the following
modules/tabs: select the checkbox next to All Modules.
b) In the Start: field, select today’s date, do not change the time and click OK.
c) In the End: field, select the last date of the current month, do not change the time and
click OK..
b) Make sure that the option Enable Advanced Proxy Management (Proxy Now and Proxy
Import) is enabled.
c) SelectBecome Proxy. Notice the only option available is Manny Manager since that is
the only proxy assignment made earlier. Select Go and then OK.
d) Select the main menu and notice that Admin Center is not available since Manny
Manager does not have that access.
b) Name Menu → Settings → Proxy. Make sure that you can also Assign a proxy by using
the Proxy Settings in the Name menu.
b) In the look up Existing Assignments section and for the Account holder (username),
use the Find User... link to select Manny Manager.
Result
You can now assign proxy access to various modules for specific date ranges and test those
assignments.
Note:
The HR Coordinator may still proxy as Manny Manager because of the Proxy
Management permission in RBP.
LESSON SUMMARY
You should now be able to:
● Act as a proxy in SAP SuccessFactors
● Use Proxy tools to Assign and Remove Proxies
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Manage Company System Settings in the Admin Center
Animation
For more information on this topic please view the animation in the lesson
Managing Company Systems, Logo settings, and Platform Feature Settings in
your online course.
Disable Proxy Access for Users without If your company chooses to only let adminis-
Proxy Rights trators make proxy assignments, this option
should be selected. If you wish to allow users
to assign their own proxies, leave this un-
checked. That is, users will be able to assign
their own proxies.
General Display Name Enabled by Default for If that option is enabled and you’ve config-
New Customers ured the Name Format for General Display
field in Legal Entity and enabled the Enable
the name format selected in Configure Peo-
ple Profile to apply globally, you can now see
the name format that you’ve configured on
UI pages of features that have adopted gen-
eral display name in Learning as well.
Enable Case-Insensitive Usernames (Note: With this setting it is possible to manage the
After you enabled case-insensitive user- case sensitivity of usernames in your compa-
names, this option will grey out, and you can ny system. You can also ensure a smoother
not disable it anymore.) integration with SAP Identity Authentication
Service (IAS) or other third parties that don't
use case-sensitive usernames.
Enable fuzzy search function for People Fuzzy search allows users to find an employ-
Search ee by a search term that has one-character
difference from the target employee name.
Enable HTML E-mail Notifications This allows SAP SuccessFactors to send for-
matted messages to users. This message is
also sent in Plain Text so it can be read by
mobile users or by users who have not al-
lowed HTML messages.
Enhanced screen reader support and key- Special settings make the SAP SuccessFac-
board navigation. tors HXM Suite easier for some people to
use, according to their personal needs. If this
setting is enabled, the two options are always
enabled (so ready to use) in the name menu/
settings/accessibility.
Everyone Can Access a Document's Revision As forms are modified and moved through
History the workflow in SAP SuccessFactors, an au-
dit trail is created. With this option selected,
all roles who participated in form actions can
access the full history of changes on the
form.
Hide Global Navigation Menu (Module Pick- This option allows to hide the Global Naviga-
er) tion menu from the common header area of
your SAP SuccessFactors system. This ena-
bles you to make your SuccessFactors sys-
tem more consistent with other SAP Cloud
solutions.
Integration with Outlook Calendar This allows users to add reminders associat-
ed with goals and forms to their Outlook Cal-
endar directly from SAP SuccessFactors by
selecting an e-mail icon.
Sanitize all rich text inputs If this feature is enabled, the user input gen-
erated through rich text editors will be sani-
tized and the content that is detected harm-
ful cannot be saved.
Show Custom Relationships in Company Or- If you have imported matrix or customer
ganization Chart (for Company Organization managers and set "ORG_CHART_DISPLAY"
Chart, Home Page, and Mobile People Pro- to "TRUE" for those managers, after you ena-
file) ble this option, matrix and custom relation-
ships display in the Company Organization
Chart, Home Page, and People Profile. To
learn how to import matrix and custom man-
agers, you can look at the Managing User In-
formation guide from the SAP Help Portal.
Show inactive user in people search (requires Both inactive and active users appear in the
Role-based Permissions) search results for different module pages
when "Show inactive user in people search
(requires Role-based Permissions)" is ena-
bled.
Show icons and use alphabetical order in the If enabled the main navigation menu will ap-
main navigation menu pear in an alphabetical order and show icons.
Business Example: In this exercise you will find out how to enable and disable settings
instance-wide.
1. “Hide the Global Navigation Menu (Module Picker)” and disable “Show icons and use
alphabetical order in the main navigation menu”.
Result
You have enabled and disabled settings instance-wide.
Business Example: In this exercise you will find out how to enable and disable settings
instance-wide.
1. “Hide the Global Navigation Menu (Module Picker)” and disable “Show icons and use
alphabetical order in the main navigation menu”.
a) Log into your instance and find the main menu available in an alphabetical order and
with icons.
c) Use Ctrl+F to search for: “Hide Global Navigation Menu (Module Picker)”.
d) Enable “Hide Global Navigation Menu (Module Picker)” by checking the box in front of
that item.
e) Scroll down to the end of the page and click on Save Company System Setting.
f) Note that after saving the setting, the main menu is not available anymore.
g) Use Ctrl+F to search for: “Hide Global Navigation Menu (Module Picker)”.
h) Disable “Hide Global Navigation Menu (Module Picker)” by checking the box in front of
that item.
i) Scroll down to the end of the page and click on Save Company System Setting.
j) Note that after saving the setting, the main menu is available again.
k) Use Ctrl+F to search for: “Show icons and use alphabetical order in the main
navigation menu”.
l) Disable “Show icons and use alphabetical order in the main navigation menu”.
m) Scroll down to the end of the page and click on Save Company System Setting.
n) To test your settings, click on the main menu and note that the alphabetical order and
the icons in the main menu is gone.
d) Enable “Hide Username in the UI” by checking the box in front of that item.
e) Scroll down to the end of the page and click on Save and in the Message Box on OK.
g) To test your settings , log back into your instance and click on the Name Menu. Note
that for the HR Coordinator no username is shown anymore.
Result
You have enabled and disabled settings instance-wide.
LESSON SUMMARY
You should now be able to:
● Manage Company System Settings in the Admin Center
Learning Assessment
X True
X False
X B Yes, permission roles are very easy to set up and do not require much
consideration.
X C Yes, permission roles are fairly easy to set up when the company’s roles have been
considered and the question of who should have access to specific types of data have
been addressed.
4. By default, when administrators assign proxy assignments start as soon as they are
created and they automatically end one month after. Determine whether this statement is
true or false.
Choose the correct answer.
X A True
X B False
Lesson 1
Using Admin Alerts 111
Exercise 9: How to use an Admin Alert 113
Lesson 2
Using Check Tool to validate configuration 116
Exercise 10: Verify Permissions with the Configuration Check Tool 119
Lesson 3
Modifying System Access Settings 124
Exercise 11: Password and Login Policy Settings, Reset Passwords and Reset User 127
Account
Lesson 4
Defining Jobs in the Schedule Job Manager 131
Exercise 12: Use Scheduled Job Manager 135
Lesson 5
Running the Execution Manager 139
Exercise 13: How to use the Execution Manager 141
Lesson 6
Using the Upgrade Center 145
Exercise 14: Upgrade the system and save an upgrade item for later 149
UNIT OBJECTIVES
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Use Admin Alerts
Admin Alerts
To use this feature, you need the Administrator Permissions → Admin Alerts → Configure
Alert Types permission.
You can now configure the system to automatically acknowledge (auto-acknowledge) specific
admin alerts after a defined amount of time.
For some admin alert types, the module specific applications have enabled the feature to
acknowledge alerts. This is applicable for the following alert types:
● Time Valuation
● Periodic Time Account Update
● Employee Time Calendar Creation
● Termination End Handling Alert
● Processing Paired Time Events for Time Sheet
● Absence Segmentation
● Reallocate Absences
● Time Collector
For these alert types, you can now define an amount of time after which an alert is
acknowledged automatically (auto-acknowledged). The applications define a maximum value
after that, an alert is auto-acknowledged.
Up to the maximum value, you can configure the system individually with an amount of time
specific to your requirements. After that, an alert is set to auto-acknowledged.
In the current version, the alert table includes an Auto-Acknowledged column. In the
Configure Alert Type popup, you can now set the number of days after which alerts are auto-
acknowledged. There's also a Retract Acknowledgment feature that you can use to revoke the
auto-acknowledgment.
Business example
Company administrators need to know how to track and resolve system issues using Admin
Alerts.
Result
You now know how to access and configure Admin Alerts.
Business example
Company administrators need to know how to track and resolve system issues using Admin
Alerts.
b) In the Admin Alert Type field select MDF Data Volume – Picklist Values (0).
e) Click OK.
f) Select Information and review the Description field for this type of alert.
g) Click Close.
Result
You now know how to access and configure Admin Alerts.
LESSON SUMMARY
You should now be able to:
● Use Admin Alerts
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Verify that the configuration is valid using the Configuration Check Tool
Why is it important?
This list provides a useful in-product support documentation summary for any user wanting
to understand the full capabilities of the Check Tool. No information is provided to the user
that would not normally be shared via standard SAP help documentation channels.
Module Check ID
User Management PurgeECDataForExternalLearnersCheckExecutor
Time Off TimeAccountAccrualWithEmptyPeriodIds
To-Do Foundation ReportTimestampInconsistenciesForTodos
To-Do Foundation ReportTodoEntryNotDecorated
Onboarding ONB2CheckProcessTriggerObjectExists
As a prerequisite please have the following Role-Based Permissions in the Check Tool
enabled:
● Access Check Tool
● Allow Configuration Export
● Allow Check Tool Quick Fix
The Quick Fix button is displayed under Proposed Solution, on the Result tab. Selecting the
Quick Fix starts a 3-step-wizard to initiate the automated fix.
To set the required permissions, go to the Admin Center and select Set User Permissions →
Manage Permission Roles. Select the role for which you want to maintain the permission,
choose Permission, then scroll down until you see the Check Tool role. Make the appropriate
settings.
Watch the 'Run a Check in the Check Tool' video for an in-depth explanation.
Business example
Some of your colleagues are reporting errors when running ad-hoc reports. Your task is to
troubleshoot and resolve the issue or raise a ticket.
Before you start, make sure you have the required permissions to access the Configuration
Check tool as described in previous lesson. If needed, add permissions to the Administrators
group. Remember: Once permissions are added, you will need to log out and log back in to the
system for changes to take effect.
3. Look at the detailed results and decide what next steps to take.
Result
On completion of the check, the Configuration Check tool displays results.
The results can be any of these:
● The yellow icon is a warning that something not too serious is wrong. The system
proposes a solution.
● The red icon indicates that the problem is serious. You must take action, which might
include creating a Support ticket.
If creating a customer incident make sure it is under the relevant category, and do provide
the component value you copied from the Need Assistance? section as shown below:
Business example
Some of your colleagues are reporting errors when running ad-hoc reports. Your task is to
troubleshoot and resolve the issue or raise a ticket.
Before you start, make sure you have the required permissions to access the Configuration
Check tool as described in previous lesson. If needed, add permissions to the Administrators
group. Remember: Once permissions are added, you will need to log out and log back in to the
system for changes to take effect.
Note:
You can run as many checks as you want. The Run Checks button at
bottom right gets updated to tell you how many you have selected.
3. Look at the detailed results and decide what next steps to take.
Result
On completion of the check, the Configuration Check tool displays results.
The results can be any of these:
● The yellow icon is a warning that something not too serious is wrong. The system
proposes a solution.
● The red icon indicates that the problem is serious. You must take action, which might
include creating a Support ticket.
If creating a customer incident make sure it is under the relevant category, and do provide
the component value you copied from the Need Assistance? section as shown below:
LESSON SUMMARY
You should now be able to:
● Verify that the configuration is valid using the Configuration Check Tool
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Modify password and login policy settings
To create security questions for the user to respond to, select the Manage security questions
link.
Complete the interaction below to see other options to adjust the Password Policy Settings.
Animation
For more information on this topic please view the animation in the lesson
Modifying System Access Settings in your online course.
CAPTCHA. To disable this option, select N/A from the dropdown. This option was created to
prevent the potential risk of flooding e-mails to users or e-mail servers.
Figure 54: Additional Options for Password & Login Policy Settings
Figure 55: Label Enhancement of Setting Expiration of Password Link in Welcome Emails
Business Example
Company administrators need to know how to modify Password & Login Policy Settings as
outlined in the Managing User Information guide on the SAP Help Portal. This can speed up
testing and development cycles in development and training environments even if these
settings are not used in production environments. Company administrators also need to be
able to reset user passwords to test changes made in Password & Login Policy Settings.
Note:
If you are performing exercises using a system provided via Learning System
Access, please do not perform the Modify Password Settings portion of this
exercise. Doing so will force a reset of all user passwords including the admin user
and this will disrupt access to your Learning System.
1. Use Reset User Passwords to attempt to reset the password for Alex Anderson to
Password1. Confirm that this password does not meet password policy requirements.
1. Modify Settings in Password & Login Policy Settings Disable Minimum and Maximum
Password Ages. Disable Maximum Successive Failed Login Attempts.
1. Use Reset User Passwords to reset the password for Alex Anderson to Password 1.
1. Test the change and confirm that Alex is asked to change the password on initial login.
Result
You now know how to configure Password and Login Policy Settings and how to reset a user
password.
Business Example
Company administrators need to know how to modify Password & Login Policy Settings as
outlined in the Managing User Information guide on the SAP Help Portal. This can speed up
testing and development cycles in development and training environments even if these
settings are not used in production environments. Company administrators also need to be
able to reset user passwords to test changes made in Password & Login Policy Settings.
Note:
If you are performing exercises using a system provided via Learning System
Access, please do not perform the Modify Password Settings portion of this
exercise. Doing so will force a reset of all user passwords including the admin user
and this will disrupt access to your Learning System.
1. Use Reset User Passwords to attempt to reset the password for Alex Anderson to
Password1. Confirm that this password does not meet password policy requirements.
a) Use Action Search to navigate to Reset User Passwords.
b) If not already selected, select the option Reset individual user password (with supplied
password).
c) In the First Name field enter Alex and wait for the option of Alex Anderson to appear
in yellow. Select that option and confirm all 4 fields are populated with Alex’s data. Or
you can type A in the First Name field and click Search Users to get the same result.
d) In the results table, select the radio button in the row for Alex Anderson.
e) In the New Password field type Password1 and in the Confirm Password field type the
same.
g) Confirm you get the following message in red: Password entered does not meet the
password policy requirements or does not match the confirm password. Please try
again.
1. Modify Settings in Password & Login Policy Settings Disable Minimum and Maximum
Password Ages. Disable Maximum Successive Failed Login Attempts.
f) Scroll to the bottom of the page and click Set Password & Login Policy.
g) Confirm you get the following message in green near the top of the page: Password &
Login Policy Saved.
1. Use Reset User Passwords to reset the password for Alex Anderson to Password 1.
a) Use Action Search to navigate to Reset User Passwords.
b) If not already selected, select the option Reset individual user password (with supplied
password).
c) In the First Name field enter Alex and wait for the option of Alex Anderson to appear in
yellow. Select that option and confirm all 4 fields are populated with Alex’s data. Or you
can type A in the First Name field and click Search Users to get the same result.
d) In the results table, select the radio button in the row for Alex Anderson.
e) In the New Password field type Password1 and in the Confirm Password field type the
same.
g) Confirm you get the following message in green: The number of users whose
passwords have been reset is 1.
h) If you get the same error message from Task 1, repeat the process and use
Password2. Continue this process with successive passwords (Password3,
Password4, etc.) until you are able to reset the password successfully. After the first
successful reset, use the next successive password to reset your password for the
second time. After the second successful reset, reset your password back to
Password1.
i) If the previous step fails, repeat Task 2 and then repeat Task 3
1. Test the change and confirm that Alex is asked to change the password on initial login.
a) Select the name menu in the upper right corner of the page and select Log Out.
d) Select the name menu in the upper right corner of the page and select Log Out.
Result
You now know how to configure Password and Login Policy Settings and how to reset a user
password.
LESSON SUMMARY
You should now be able to:
● Modify password and login policy settings
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Work with Schedule Job Manager
Note:
As a customer, you don't have access to Provisioning. To complete tasks in
Provisioning, contact your implementation partner or Account Executive. For any
non-implementation tasks, contact Product Support.
Scheduled Job Manager isn't intended to fully replace all of the functionality in Provisioning.
It's only intended to provide customer administrators with self-service access to some job
types, for some actions. We continue to add support for more job types over time, but some
job types are only available in Provisioning. To view a list of job types that support monitoring,
go to the Job Monitor tab and open the Job Type menu. If the job type you're looking for isn't
listed, contact Product Support.
Scheduled Job Manager doesn't support terminating or interrupting jobs. Also, available
actions vary for each supported job type. For example, for some job types you can create and
submit a job request, but you can't run the job immediately. For other job types, you can only
monitor the job execution, but the job itself has to be set up initially in Provisioning.
For additional information please see the Managing Scheduled Jobs guide on the SAP Help
Portal.
Business Example
Company administrators need to know how to schedule and monitor various jobs using
Scheduled Job Manager as outlined in the Managing Scheduled Jobs guide on the SAP Help
Portal.
1. Use the Scheduled Job Manager and Job Scheduler to create a Job Request of type
Business Configuration Audit Job for the Object Type Standard Element.
1. Use the Scheduled Job Manager and Job Scheduler to run the job now.
1. Use the Scheduled Job Manager and Job Monitor to monitor the job, download the results
and review them.
1. Use the Scheduled Job Manager and Job Scheduler to modify the Business Configuration
Audit Job.
Result
You now know how to schedule and monitor various jobs using Scheduled Job Manager.
Business Example
Company administrators need to know how to schedule and monitor various jobs using
Scheduled Job Manager as outlined in the Managing Scheduled Jobs guide on the SAP Help
Portal.
1. Use the Scheduled Job Manager and Job Scheduler to create a Job Request of type
Business Configuration Audit Job for the Object Type Standard Element.
a) Use Action Search to navigate to Scheduled Job Manager and select the Job Scheduler
tab.
Field Value
Job Name Business Configuration Audit Job
i. Occurrence: Recurring
f) Click Submit
1. Use the Scheduled Job Manager and Job Scheduler to run the job now.
a) Use Action Search to navigate to Scheduled Job Manager and select the Job Scheduler
tab.
b) In the Actions column, click the Actions button and select Run It Now.
c) Click OK.
1. Use the Scheduled Job Manager and Job Monitor to monitor the job, download the results
and review them.
a) Use Action Search to navigate to Scheduled Job Manager and select the Job Monitor
tab.
b) In the Job Name column look for Business Configuration Audit Job. If you do not see it,
wait one minute and click the Go button in the upper right corner or refresh the
browser.
c) Once the job appears go to the Actions column for the job and select View Details.
d) On the Run Details window, select Download Status to download a csv file with details
about the job. It will be titled jobResponse plus a number like jobResponse2121.
e) Open the file in Excel or other application that handles csv files and review the content
in column F. We will work with Standard Elements again in a future exercise.
1. Use the Scheduled Job Manager and Job Scheduler to modify the Business Configuration
Audit Job.
a) Use Action Search to navigate to Scheduled Job Manager and select the Job Scheduler
tab.
b) In the Actions column, click the Actions button and select Cancel.
c) Click OK.
d) In the Actions column, click the Actions button and select Edit.
f) Click Submit.
g) Optional: repeat Tasks 2 and 3 and review columns J and R in the csv file.
Result
You now know how to schedule and monitor various jobs using Scheduled Job Manager.
LESSON SUMMARY
You should now be able to:
● Work with Schedule Job Manager
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Deploy the Execution Manager
Execution Manager
The Execution Manager Dashboard shows you the status of scheduled jobs and integrations
to quickly identify and troubleshoot errors.
You can view the number of jobs and integrations that have occurred in the past twenty-four
hours, seven days, or fifteen days and whether they resulted in success or error. The
Execution Manager logs are retained for a duration of 15 days, by default. Logs that are older
than the retention period are automatically removed from the system. Execution Manager is
included as part of Next Gen Admin. It doesn’t need to be enabled separately, but you do need
to grant the appropriate permissions.
on the Admin Center page.On the Execution Manager page, you can select a time frame and
see how many successful or failed custom integrations occurred during that time frame. You
can view the exact date and time of execution and other event details, to help you
troubleshoot any errors.
Scheduled Job Tab
You can view the status of recent jobs on the Scheduled Jobs tile on the Admin Center page.
On the Execution Manager page, you can select a time frame and see how many successful or
failed jobs occurred during that time frame. You can view the exact date and time of execution
and other event details, to help you troubleshoot any errors.
Middleware Integrations Tab
You can view the status of middleware integrations on this tab. Middleware integrations allow
for communications between disparate systems and SuccessFactors uses OData APIs.
Pre-Delivered Integrations Tab
When the endpoint is triggered for an event subscription which is created in Event
Subscription Management or Intelligent Services Center, you can monitor the integration in
Execution Manager under the Pre-Delivered Integrations tab. You can check using the name
of the event subscription. Along with external event integrations, you can also monitor other
real-time integrations under the Pre-Delivered Integrations tab.
For more information see the Using Admin Center guide on the SAP Help Portal.
Business Example
Company administrators need to know how to monitor and manage notifications in Execution
Manager for Integration Center, Scheduled Job, Middleware Integrations and Pre-Delivered
Integrations as outlined in the Using Admin Center guide on the SAP Help Portal.
Use the Execution Manager to monitor scheduled jobs and to manage notifications.
Result
You now know how to monitor and manage notifications in Execution Manager.
Business Example
Company administrators need to know how to monitor and manage notifications in Execution
Manager for Integration Center, Scheduled Job, Middleware Integrations and Pre-Delivered
Integrations as outlined in the Using Admin Center guide on the SAP Help Portal.
Use the Execution Manager to monitor scheduled jobs and to manage notifications.
e) Select the green bar representing the first job you ran in the previous exercise Using
Scheduled Job Manager.
g) On the Event Details page click the down arrow on the upper right to download a csv
file with the details of this Business Configuration Audit Job. It will be titled eventLog_
plus a number like eventLog_5570.
h) Open the file in Excel or other application that handles csv files and review the content.
i) Select the < next to Event Details to return to the Execution Manager main page.
Fields Value
Process State Completed Successfully and In Progress
Fields Value
Process Definition Name Business Configuration Audit Job -
( BCUIAudit )
g) Click Save.
h) Optional: rerun the job from the Using Scheduled Job Manager exercise to generate an
email.
Result
You now know how to monitor and manage notifications in Execution Manager.
LESSON SUMMARY
You should now be able to:
● Deploy the Execution Manager
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Use navigation tools to access the Upgrade Center
Note:
The Upgrade Center does NOT allow you to perform upgrades that you have not
been granted permission to perform. Although any administrative user can
access the Upgrade Center page itself, each individual upgrade is governed by
the appropriate system permissions. If you do not have the appropriate
permission, you can view information about an upgrade, but you cannot use it to
enable the feature.
The Upgrade Center is a universal feature of the Admin Center and is available in both
versions of the Admin Center. In OneAdmin, select the button in the Upgrade Center portlet to
access the page. In Next Gen Admin, you can use the Release Center tile on the admin home
page to scroll through the most important recent upgrades. To access the full Upgrade
Center, you can use search, or select See More on the Release Center tile, then go to the
Upgrade Center tab.
This is an example of the full Upgrade Center page:
1. Go to Admin Center → Tools → Manage Permission Roles and select the role to which you
want to grant permission.
2. Select the Admin Center Permissions tab, in the Administrator Permissions section.
Watch the 'Permissions for the Upgrade Center' video for an in-depth explanation.
the same way as in the Legacy UI, allowing you to scroll through a number of highlighted
features and access the Upgrade Center for more information. The Release Center content
always appears first on the tile carousel, with a See More link that points to the Release Center
page.
You still can access the Upgrade Center in a number of ways, as follows:
● You can scroll through the carousel on the Release Center tile and view other optional
upgrades, as before. From there, you can access the Upgrade Center page directly.
● You can use the tool search to find the Release Center in both UI versions and access the
Upgrade Center page.
● If you are using action search, you can link to both the Upgrade Center and Release Center
directly from the global search box.
● From the OneAdmin UI, you can still see an Upgrade Center portlet that links to the
Upgrade Center page, as before.
● You can link between the Upgrade Center and Release Center, using the tabs on both
pages.
Watch the 'Using the Upgrade Center' video for an in-depth explanation.
Business Example: In this exercise you will learn how to handle the Upgrade Center.
Result
You have upgraded the system, undid the upgrade and saved one item to upgrade later.
Business Example: In this exercise you will learn how to handle the Upgrade Center.
c) Under “Optional Upgrade” find “Intelligence Service” and click below on “Learn More &
Upgrade Now”.
d) Become familiar with the description of the upgrade, note how many customers did
already the upgrade and read the note.
e) Scroll down to the bottom of the page and click on “Upgrade Now” and on “Yes” and
“OK” in the confirmation box.
f) On the page “Upgrade Center” click on the link “View Recently Completed Upgrades”
and find the upgrade “Intelligent Services” that you just saved for later.
g) In the column “Action” click on the link “Undo” and on “Undo” and “OK” in the
confirmation box.
h) Note in the column “Current Status”, that the undo was successful and in the column
“Actions”, that you can run the upgrade again (the upgrade can also be seen again
under the “Recommended Upgrades” on the “Upgrade Center” page).
c) Under “Optional Upgrade” find “Latest Goal Management” and click below on “Learn
More & Upgrade Now”.
d) Note that this upgrade cannot be undone once it is installed (red note in the
description says: “Warning: This upgrade CANNOT be undone. You CANNOT revert
back to an older version.”.
e) Click on “Save for later” and on “Yes” and “OK” in the confirmation box.
f) On the page “Upgrade Center” click on the link “View Saved for Later Items” and find
the upgrade “Latest Goal Management” that you just saved for later.
Result
You have upgraded the system, undid the upgrade and saved one item to upgrade later.
LESSON SUMMARY
You should now be able to:
● Use navigation tools to access the Upgrade Center
Learning Assessment
1. There can be a permission in Manage Permission Roles for the Upgrade Center.
Choose the correct answer.
X A True
X B False
2. The Configuration Check tool can identify a configuration issue as well as suggest a
solution.
Determine whether this statement is true or false.
X True
X False
Lesson 1
Using Action Search, other Searches, and Custom Navigation 158
Exercise 15: Enable Fuzzy and Inactive Users Search 165
Exercise 16: Configure Custom Navigation 167
Lesson 2
Using the Org Chart 170
Exercise 17: Display photos on the Org Chart 171
Lesson 3
Accessing Built-In Support 174
Exercise 18: Use the Built-In Support 175
Lesson 4
Customizing the Home Page 179
Exercise 19: Working with custom cards 195
Lesson 5
Navigating with Quick Cards 203
Exercise 20: How to manage Quick Cards 205
Lesson 6
Managing Mobile Settings 209
Exercise 21: Configure Mobile Access Features 217
Lesson 7
Implementing e-mail notifications 220
Exercise 22: Edit the E-mail Notification Settings 225
Lesson 8
Customizing the SAP SuccessFactors instance 229
Exercise 23: Apply, create and delete a Theme 233
Lesson 9
Lesson 10
Using the Manage Languages Tool 243
Exercise 25: Manage Languages 251
Lesson 11
Implementing translations 255
Exercise 26: Implement Translations 271
Lesson 12
Customizing Company Dictionary, Spell Check and Legal Scan 274
Exercise 27: Add a word in the Company Dictionary 275
Lesson 13
Maintaining the Company Logo 279
UNIT OBJECTIVES
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Modify People Search and Action Search
● Maintain Custom Navigations
At the top of the page, a search bar allows users to search for an action or for people.
So when you search for "Mike adam", Person A appears in your search results. When you
search for "Mike Willi", Person B appears in your search results. When you search for "Mi
*ams", both Person A and Person B appear in your search results. When you search for "*ike
Adams", neither Person A nor Person B appears in your search results
For further information check: Allowing Special Characters in Search Queries
Fuzzy search allows you to find an employee by a search term that has one character
difference from the target employee name. The new feature applies to the following scenarios
when searching employees:
• One missing or redundant character. If you search for "Joerg", the results also return "Jörg",
and vice versa.
• One misspelled character. If you search for "ALLEX", the search results also return "Alex"
and “Allen”, and vice versa.
Prerequisites:
• User Search permission is granted in RBP.
• Enable Solr People Search is enabled in Provisioning.
Note:
In the 2H 2019 Release (also called the 1911 release) a change was made to the
Company System and Logo Settings page and the Company Logo field was made
a required field. For this reason if the URL of the Company Logo field is blank and
you attempt to save changes you will get an error. To fix this you can follow the
steps in the following Knowledge Base Article (KBA): 2888435 - Cannot save
changes on Company System and Logo Settings due to the error "Specify a
company logo URL"
By default, inactive users are not included in People Search results. Use this configuration
option to include them.
This company-level setting does not affect search functions on People Profile or Employee
Directory. Likewise, feature settings and permissions used to control search functions on
People Profile or Employee Directory, such as the Role-Based Permission Include Inactive
Employees in the search, do not affect People Search.
Future hires are also displayed as inactive users in the People Search results in the Global
Header.
Note:
People Search uses the company-level Show inactive user in people search
(requires Role-based Permissions) setting only and not Role-Based Permissions.
You cannot restrict the visibility of inactive users in People Search based on
permission role.
Action Search
Action Search is a feature designed to facilitate navigation and enhance overall system
usability.
As an End User, you can use Action Search to find dozens of common actions directly in the
search bar at the top of the page. You can use natural language to describe what you want to
do, and then select from a list of suggested actions.
As an administrator, you can use Action Search to access your Admin Center as well. You can
also do the following:
● Create a search for relevant actions based on keywords and synonyms.
● Manage and configure your own action keywords and custom links.
As an administrator, you can access Admin Center → Company Settings → Manage Action
Search to customize the ways in which users find actions from the search bar in the page
header. You can enable or disable actions, and add your own search terms or search labels,
both for standard actions and your own custom actions.
There are a number of predefined actions and paraphrases within SAP SuccessFactors. If you
would like for users to have additional key words or paraphrases to search by, you can add
your own Custom Paraphrase within a specific Action.
For example, as an administrator, you may refer to Role-Based Permissions as RBPs. In
Action Search, you can add RBP as a searchable paraphrase from Action Search. To do this,
choose Action from the list on the left side of the page. Then choose the Add custom
paraphrases option. Type in the new paraphrase under When the user searches for any of
these… and the option you’d like to display in the search results under Display this
paraphrase. Then click Save.
Note:
You can find out more about People Search andAction Search by reviewing the
documentation on the SAP Help Portal
As configuration requirement, the instance is set up for SAP Cloud Identity Services - Identity
Authentication service (IAS) and Joule. Joule is enabled. To set the permission go to “General
User Permission” and enable “Access to Joule permission”.
For the latest updates on the availability of Joule, refer to KBA 3390798 - Joule availability in
SAP SuccessFactors Information published on SAP site.
Customize Navigation
Custom Navigations provide the ability to navigate to a new location, such as an external URL
or a custom report, which is not accessible using default system options. Custom Navigations
can appear in Action Search, the main Navigation Menu, People Profile "Jump To" and
"Employee Records," and from "Take Action" and "Go To" within an employee quick card. This
gives companies great flexibility in customizing their instance of SAP SuccessFactors, as they
can now seamlessly provide quick access to other tools outside of SAP SuccessFactors,
centralizing the workspace.
Custom navigation must be enabled in Provisioning.
To configure Custom Navigations in the instance, navigate to Admin Center → Company
Settings → Configure Custom Navigation. The following table describes the configuration
options:
Field Description
Menu Item Label This is how the link appears in the user interface. For custom ac-
tions, this becomes the "display label" in Action Search.
ID This can be any text or numeric value. You can use any convention
you wish, but every custom navigation link, regardless of its location
or locations, must have a unique ID.
Link Type Custom actions created in Action Search do not reflect these set-
tings. Action Search only supports "same browser" behavior. Both
internal and external custom navigation actions open in the same
browser tab.
For other custom links, you can select the following:
● Internal Link
● Used with a SAP SuccessFactors deep link in URL field
● External Link - Same Browser
● Used with an external URL. Opens in the same browser window.
● External Link - New Browser
● Used with an external URL. Opens in a new browser window.
URL Enter the URL or deep link that you want to make available in action
search.
Menu Location To create a custom action, select Action Search in the dropdown
menu. For custom actions, it is recommended that you only select
one location, Action Search, in this menu. This is due to the fact that
localization and link types are handled differently in action search
than with other custom link locations. For other link locations, you
can select one or more locations.
Permissions This dropdown displays the permission roles and groups configured
in RBP. Only those selected will see the Custom Navigation.
Business Example: In this exercise you will learn how to enable the Fuzzy and the Inactive
Users Search.
1. On “Company Systems and Logo Settings”, enable the Fuzzy and Inactive User Search.
Result
You have enabled Fuzzy and Inactive User Search.
Business Example: In this exercise you will learn how to enable the Fuzzy and the Inactive
Users Search.
1. On “Company Systems and Logo Settings”, enable the Fuzzy and Inactive User Search.
a) Log into your instance. Use Action Search to search for “Super” and note, that there
were no results.
c) Use Ctrl+F to search for “fuzzy” and find “Enable fuzzy search function for People
Search”.
d) Enable “Enable fuzzy search function for People Search” by checking the box in front
of the line.
e) Use Ctrl+F to search for “show inactive” and find “Show inactive user in people search
(requires Role-based Permissions)”.
g) Scroll down to the end of the page and click on “Save Company System Settings”.
h) To test your settings, use Action Search to search for “Super” and note that you find a
user “super admin” that has the status inactive.
Result
You have enabled Fuzzy and Inactive User Search.
Business Example: In this exercise you will learn how to configure a customer specific
navigation.
Result
You have configured a customer specific navigation by adding a customer specific item to the
main menu.
Business Example: In this exercise you will learn how to configure a customer specific
navigation.
Note:
This tool is only available if exercise 3 was done already.
f) Select as Menu Location “Top Navigation” by checking the box in front of this option.
g) Select as Permission “Select all”, click on “Save” and on “OK” in the confirmation box.
h) To test your settings, log out and log back into the system and click on the main menu
where you will find a new item called “Company Website”.
Result
You have configured a customer specific navigation by adding a customer specific item to the
main menu.
LESSON SUMMARY
You should now be able to:
● Modify People Search and Action Search
● Maintain Custom Navigations
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Configure Org Chart settings using Org Chart Configuration
Business Example: In this exercise you will learn how to configure the Org Chart.
Result
You have configured the Org Chart by disabling photos.
Business Example: In this exercise you will learn how to configure the Org Chart.
b) Note that you can see a photo of HR Coordinator om the Org Chart.
d) In “Basic org chart” disable “Display Photo” by clicking on the white hook in the blue
box
e) Click on “Save” at the end of the options and note the green hint that says “* Changes
saved successfully”.
f) Test your new setting by using Action Search to navigate to View Org Chart. Note that
there is no photo of HR Coordinator on the Org Chart anymore.
Result
You have configured the Org Chart by disabling photos.
LESSON SUMMARY
You should now be able to:
● Configure Org Chart settings using Org Chart Configuration
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Use Built in Support
using the (Built-In Support) icon in the page header. To access the Built-In Support side
In-Product Support
In-Product Support (displayed as support sidebar at the right of your screen) provides an
integrated in-product dashboard for administrators to submit and manage customer issues.
Administrators are offered support from within the product:
● Centralize the knowledge base
● Submit new cases, including video capture
● Access case administration
● Provide context to issue diagnosis to support customer services
Note:
The Support Sidebar is accessed from any page in the Suite.
The In-Product Support can be disabled from the Action Search → Platform Feature Settings.
Business Example
Company administrators need to know how to use and explain the features of Built-In Support
as outlined in the Using Admin Center guide on the SAP Help Portal.
Result
You now know how to use Built-In Support to search for information. You can explore the
other tutorials to learn how to create support cases with S/P-user IDs.
Business Example
Company administrators need to know how to use and explain the features of Built-In Support
as outlined in the Using Admin Center guide on the SAP Help Portal.
b) View the Welcome to Built-In Support video and step through the onboarding steps by
clicking Next after reading each screen.
c) Find the entry titled Action Search Configuration Tool and select it.
d) Confirm that a new browser window opens displaying the Configuring Action Search
guide on the SAP Help Portal and that it opens to the topic on Action Search
Configuration Tool.
c) Find the entry titled Joule in SAP SuccessFactors and select it.
d) Confirm that a new browser window opens displaying the Using Admin Center guide on
the SAP Help Portal and that it opens to the topic on Joule in SAP SuccessFactors.
d) Review the tutorial titled Best Practice Guide for the Search Functionality or other
tutorials of interest.
Result
You now know how to use Built-In Support to search for information. You can explore the
other tutorials to learn how to create support cases with S/P-user IDs.
LESSON SUMMARY
You should now be able to:
● Use Built in Support
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Describe the Home Page
● Use Manage Home Page feature to customize the Home page
Home Page
The SuccessFactors Home page is the default start page of the SAP SuccessFactors HXM
Suite. On the home page you can view pending deadlines, outstanding issues, and valuable
team metrics and business analytics. It provides an overview of activity across the SAP
SuccessFactors HXM Suite and helps you to take action quickly when necessary.
The Navigation Menu (also referred to as the Main Menu) is available as a dropdown menu in
the upper-left corner, and displays the modules to which you have access. Depending on a
user’s role within the organization, they may see different options in the menu. For example,
an administrator will see Admin Center, but a basic End User will not. This access is
determined by permissions and/or system configuration.
Note:
The top name of the Navigation Menu changes as you move throughout the
system to indicate the page you are viewing.
Settings
The Settings link from the name dropdown menu allows users to manage their personal
settings and preferences. This includes passwords, notifications, language, forms, proxy
assignment, groups, and mobile access. To access the Settings page, choose the Name menu
and select Settings from the dropdown menu.
You can set a number of individual options using the Settings page:
● Password change, if applicable. This option is not applicable if your company uses single
sign-on (SSO).
● Security question selection, if applicable. This option is available if security questions are
enabled under Company Settings.
● Receipt of notifications from the system, if applicable. This is an optional function for ALL
notifications and is available depending on your system settings.
● Language preference selection, if applicable. This only applies if your instance is a
multilingual implementation.
● Proxy assignment, if applicable. You can assign proxies if this feature is turned on and
become a proxy if you are assigned as a proxy.
Note:
The settings for your instance of SAP SuccessFactors vary depending on your
global settings. The listed options might or might not be accessible.
Home Page
The Home page is the default start page of the SAP SuccessFactors HXM Suite. For
employees, the Home page is the main entry point to the SAP SuccessFactors application and
generally the first page we see after logging in. It shows pending tasks, highlights, recent
activities and help users to take action quickly.
The Home page contains tiles that can be customized using the Manage Home Page feature.
As an administrator, you can set up the Home page to display Tiles with key information for
employees.
There are currently two available versions of the Home page.
• The legacy home page is in deprecation and will be deleted. Customers are encourage to use
the latest home page.
• The latest home page, also called the re-imagined home page is intended to replace the
legacy experience. The latest home page is available to all customers.
Note:
The legacy home page reached end of maintenance on May 21st, 2021 and was
planned for removal during the 1H 2022 Release. You can see the latest
information about this on the SAP Customer Community:
Migration to Reimagined Home Page June 2022 – Innovation Alert
Additionally you can review the Home Page Guide on the SAP Portal:
Managing the Home Page
Additionally, although SAP will update product documentation with every release, Knowledge
Base Articles or KBAs may take a while to be updated especially for changes that impact
several KBAs. Consultants should consider this when searching for answers using KBAs. For
example, Home Page Tiles have been replaced by Cards even though as of the 1H 2022
release there are active KBAs that mention tiles. Checking KBA publish dates can be used in
these cases to help consultants gauge the accuracy of various KBAs. Here are two examples:
● 2442975 - Birthday and Work Anniversary Tile in SuccessFactors
● 3193391 - Birthday/Work Anniversary Cards are showing blank in Latest Home Page
The first KBA is older and should be retired in the near future (before the end of 2022). So it is
always important to view the latest version of the implementation guides as well as access the
What's New Viewer tool:
What's New Viewer
Deprecation details
We’ve redesigned the home page experience so that it's simpler, more engaging, faster to
load, and available on all devices. It includes a simplified administration experience as well.
You can upgrade to the latest home page today, using the Upgrade Center. We encourage you
to review the available information and begin planning to adopt the latest home page for your
organization.
Caution:
This change impacts all customers who don't adopt the latest home page before
automatic migrations begin.
If you don't adopt the latest home page before your scheduled migration date, it's likely to
result in a suboptimal initial experience for your organization. If we automatically upgrade
your system:
● The home page doesn't fully reflect your theming and branding.
● The banner image is the default image, rather than one you've chosen.
● All available quick actions are shown, even ones you may not want to use.
● The last 16 custom cards imported are shown first, rather than ones you've chosen to
prioritize.
● All imported custom cards show a default image, rather than one you've chosen.
● All custom cards are the large size by default.
● All grouping of custom cards into sections on the legacy home page is lost. All custom
cards appear together under the heading Organizational Updates and there's no more
Role-Based Permission controlling visibility at the section level. The target group is
configured at the card level only.
Although you can use the latest home page with only custom content, it's most useful with
system-generated content.
The following product areas currently show content on the latest home page:
● Compensation, including Variable Pay and Spot Awards
● Employee Central Payroll
● Employee Central Time Off and Time Sheet
● Performance and Goals, including Goal Management, Continuous Performance
Management, and Continuous Feedback
● Onboarding
● Recruiting
Survey cards appear on their own, near the top of the page.
Quick Actions
By default, all available quick actions are selected. As an administrator, you can choose to
hide the ones you do not want to use, except Favorites and Saved for Later, which are always
visible. There is a maximum number of 16 quick actions that can be visible on your home
page.
On Manage Home Page select the pen icon for the Quick Actions.
Deselect the quick actions that you do not want to use. You can always select any quick action
to show it again.
Choose Save.
Quick Actions are visible based on role-based permission and system configuration. If
configured in the system and relevant to a person's role, the following quick actions are
available:
● Create Activity quick action enables you to create an activity in Continuous Performance
Management.
● Report Center quick action takes you to the Report Center page.
● Favorites quick action enables you to review a list of available links and select your
favorites, so that you have quick access to them on the Home page.
● My Team quick action enables managers to review information about their team of direct
reports and take necessary action.
● Clock Time quick action enables you to clock in and clock out.
● Complete Payroll Tasks quick action takes you to your payroll tasks. It enables you to view
the list of employee events and the corresponding infotypes that should be updated or
maintained for payroll requirements. You can view task details and set the status of the
payroll tasks.
● Delegate Workflows quick action enables you to assign a delegatee to process your
workflows during a specified period.
● My Profile quick action takes you to your People Profile.
● Org Chart quick action takes you to the company organization chart.
● View Admin Alerts quick action takes you to Admin Alerts.
● View Team Absences quick action takes you to the absence calendar for your team.
Administrators can add custom links to the Favorites quick action on the latest home page.
Custom links are optional. If you add them or import them from the legacy home page, they're
included in the Available list, along with the standard links we provide by default. You can
configure one or more target groups who can see each link. You can also add a localized link
name and description for each language in the system.
The available list on the Favorites quick action is alphabetical to make it easier to scan.
After a card type is disabled, you can delete all existing cards of that type by going to
Scheduled Job Manager Job Scheduler Create Job Request and selecting the job type Delete
Cards from Database. When the job is executed, all existing cards of that type are deleted
from the database and removed from the user interface. In the following example, only the
Goals card type is available in the job parameters because it's the only card type that's
disabled in the system.
Note:
You can only disable card types that are listed on the Manage Card Settings page.
If a card type isn’t listed, its visibility isn’t configurable, and it can't be disabled.
You can only delete existing cards if the card type has been disabled on the
Manage Card Settings page first. If a card type isn't listed in the job scheduler,
either it hasn't been disabled yet or its visibility isn’t configurable, and it can't be
deleted.
option enables administrators to prevent mobile app users from seeing web links that don't
work.
Note:
Not all to-do tasks are shown on the latest home page. All the to-do tasks are
visible in the page header and it is possible to complete them from the to-do panel
on any page.
● The My Team reminder card in the For You Today section informs you when your direct
reports have tasks that are overdue or due in the next seven days. Use the card to send
them an e-mail reminder.
● The Birthday and Work Anniversary cards remind you when a team member has an
upcoming milestone. A first reminder appears on the first day of the month, for all
birthdays and work anniversaries on your team in the coming month. A second reminder
appears on the day of the milestone.
● The Approvals section enables you to quickly approve and decline requests from your
team or about members of your team.
● The View Team Absences quick action enables you to see the absence calendar for your
team.
● The Delegate Workflows quick action enables you to assign a delegatee to process your
workflows during a specified period.
● The Org Chart quick action enables you to access the company organization chart.
● The Report Center quick action takes you to the Report Center page.
Figure 79: Manager Quick Actions - My Team, Org Chart and Report Center
UI integration cards
As of 1H 2023 release, users can add the following UI integration cards into their workspaces
after administrators download the new content package named "HR Cards from Home Page"
and enable the corresponding cards it contains.
● Compensation Statement
● Spot Award Congratulations
● Time for a break?
● Activity
● Goals
● Job Application
● Compliance Forms
● Help Us to Know You Better
● Onboarding Guide
Business example
You can add or edit custom cards that are shown in the Organization Updates section on the
latest home page. Custom cards display custom content on the latest home page, for a
specific audience or date range. You can have a maximum of 100 custom cards on the
Manage Home Page screen. A maximum of 16 custom cards can appear on the Home page
itself, for any one user.
2. Choose Add Card to create a new card or the pen icon to edit an existing one.
Note:
To edit an existing card, skip steps that are already done, make your edits, and
advance to the end of the wizard to save your changes.
4. To show the card on the home page, set the Enabled switch to On. Otherwise, keep it set to
Off until you are ready.
6. Enter a title for the card. You can also enter a subtitle. The values you enter are used by
the default locale. Choose the globe icon to add translations for other languages in the
system.
7. Browse to an image for the thumbnail and select it. For best results, follow onscreen
recommendations for image file size and aspect ratio. The preview pane displays a
preview of the card as it appears on the home page.
9. Choose a Target behavior from the dropdown menu to specify what happens when you
interact with the card.
Note:
When you choose this option, the card executes any code in a JavaScript file
that you provide. You're responsible for the quality and security of the code.
We don't provide support for any issues that result from custom JavaScript
code.
12. If you selected E-mail, enter e-mail addresses for one or more recipients of the e-mail
opened by the card.
13. If you selected JavaScript URL, enter the URL of the JavaScript file.
14. If you're already familiar with how to use business rules with custom cards and you've
already created the necessary rules, you can set the Rule-based switch to On and specify
different rules to trigger different target behaviors. Otherwise, keep the switch set to Off
for now and set up the rest of the card. Then set up rule-based content later.
Result
As a result, the custom card is shown in the Organizational Updates section of the home page,
for the specified target group and during the specified dates.
you might decide to prioritize content aimed at one target group (such as managers) over
another (such as individual contributors).
3. Choose Save → OK to save changes. You can also choose Cancel → OK to revert changes
and restore the previously saved order.
Result
As a result, custom cards are displayed in the Organizational Updates section in the order you
set, for the relevant target groups and at the specified times.
Note:
Remember that a maximum of 16 custom cards can appear on the home page
itself, for any one user.
Business example
You can add or edit custom cards that are shown in the Organization Updates section on the
latest home page. Custom cards display custom content on the latest home page, for a
specific audience or date range. You can have a maximum of 100 custom cards on the
Manage Home Page screen. A maximum of 16 custom cards can appear on the Home page
itself, for any one user.
2. Choose Add Card to create a new card or the pen icon to edit an existing one.
Note:
To edit an existing card, skip steps that are already done, make your edits, and
advance to the end of the wizard to save your changes.
4. To show the card on the home page, set the Enabled switch to On. Otherwise, keep it set to
Off until you are ready.
6. Enter a title for the card. You can also enter a subtitle. The values you enter are used by
the default locale. Choose the globe icon to add translations for other languages in the
system.
7. Browse to an image for the thumbnail and select it. For best results, follow onscreen
recommendations for image file size and aspect ratio. The preview pane displays a
preview of the card as it appears on the home page.
9. Choose a Target behavior from the dropdown menu to specify what happens when you
interact with the card.
a) Choose Popover to open more content in a dialog window.
d) Choose No Target if you don't want the card to be interactive. It's just a title, subtitle,
and image.
Note:
When you choose this option, the card executes any code in a JavaScript file
that you provide. You're responsible for the quality and security of the code.
We don't provide support for any issues that result from custom JavaScript
code.
ii. Select No Template to start with a blank text box in the text editor.
iii. Select Raw HTML to enter custom HTML, without a text editor.
iv. Select Video File to embed a video file stored on a private site, such as your
company intranet. Typically, it ends with a video file extension, such as .mp4.
b) Language:
Choose the language of your content. You can add content in different languages for
the same custom card.
c) Content:
Enter the content of the popover dialog, in the selected language.
d) URL:
For the Video File or Iframe options, enter the URL for the content you want to display.
b) Open Link in New Window/Tab: Select this option to open the target URL in a new tab
or window.
12. If you selected E-mail, enter e-mail addresses for one or more recipients of the e-mail
opened by the card.
13. If you selected JavaScript URL, enter the URL of the JavaScript file.
14. If you're already familiar with how to use business rules with custom cards and you've
already created the necessary rules, you can set the Rule-based switch to On and specify
different rules to trigger different target behaviors. Otherwise, keep the switch set to Off
for now and set up the rest of the card. Then set up rule-based content later.
b) Choose Always to always show the card on the home page, for selected groups, or
choose a Date Range when the card is shown.
Result
As a result, the custom card is shown in the Organizational Updates section of the home page,
for the specified target group and during the specified dates.
b) Highlight a table row by selecting it with a mouse or Spacebar. Then use “Move up”
and “Move down” icons to change the order.
3. Choose Save → OK to save changes. You can also choose Cancel → OK to revert changes
and restore the previously saved order.
Result
As a result, custom cards are displayed in the Organizational Updates section in the order you
set, for the relevant target groups and at the specified times.
Note:
Remember that a maximum of 16 custom cards can appear on the home page
itself, for any one user.
LESSON SUMMARY
You should now be able to:
● Describe the Home Page
● Use Manage Home Page feature to customize the Home page
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Navigate in the Application with the Quick Cards
Quick Cards
Quick cards display basic information about employees in the system such as phone
numbers, e-mail addresses, titles, and locations.
Quick cards are available in several places within the application, and you can display them as
follows:
● By hovering over an employee’s name, like in People Search;
● By selecting on an employee’s name, like in performance forms; or
● By choosing on the small Rolodex-card icons shown next to each employee’s name in
certain areas of the tool like Calibration sessions.
Quick cards are a convenient way to find information about employees in a single place
including contact information and team size. With the take action option available on quick
cards, users can navigate to other areas in the system that contain additional employee
information.
There are some specificities to keep in mind when using quick cards:
● Content in quick cards is dynamic and most content is not customizable.
● You will not see links to content that you do not have permission to see, so all security
permissions are respected in quick cards.
● Some links can be enabled or disabled.
On the right-hand side, you can see the differences in Barry’s quick card when it is accessed
by two different users. The first is an administrator with full permissions and the second is a
different administrator with fewer permissions. Therefore, fewer links are available.
Business Example
Company administrators need to know how to configure options that will impact employee
quickcards as outlined in the Implementing People Search Search guide and in other guides
within SAP SuccessFactors Platform on the SAP Help Portal.
1. Disable quickcard view from Company System and Logo Settings and test the change in
Action Search.
3. Disable the ability to see usernames in the quickcard and Action Search.
4. Re-enable the ability to see usernames in the quickcard and Action Search.
Result
You now know how to configure some options related to Quickcards.
Note:
Do not confuse Employee Quickcards with Talent Cards.
Business Example
Company administrators need to know how to configure options that will impact employee
quickcards as outlined in the Implementing People Search Search guide and in other guides
within SAP SuccessFactors Platform on the SAP Help Portal.
1. Disable quickcard view from Company System and Logo Settings and test the change in
Action Search.
a) Use Action Search to navigate to Company System and Logo Settings.
b) Locate the option Selecting a user from global header search will show the quickcard,
uncheck this option and click Save Company System Setting.
c) Confirm the message Company System Setting Saved. appears at the top of the page.
e) In Action Search enter Alex Anderson and move your cursor over the image of Alex.
Notice no additional windows appear.
b) Locate the option Selecting a user from global header search will show the quickcard,
check this option and click Save Company System Setting.
c) Confirm the message Company System Setting Saved. appears at the top of the page.
e) In Action Search enter Alex Anderson and move your cursor over the image of Alex.
Notice an additional window appear titled Employment Details.
f) Select the link at the bottom of the card titled Show Actions and Links.
g) Click Links and then select Succession Org Chart. Confirm you are brought to the CEO
position in the company that is currently occupied by Alex Anderson.
3. Disable the ability to see usernames in the quickcard and Action Search.
a) Use Action Search to navigate to Platform Feature Settings.
b) Locate the option Hide Username in the UI, check this option and click Save.
e) In Action Search enterAlex Anderson and notice that you see an image of Alex and his
position of CEO but you do not see username aaaa.
f)
4. Re-enable the ability to see usernames in the quickcard and Action Search.
a) Use Action Search to navigate to Platform Feature Settings.
b) Locate the option Hide Username in the UI, uncheck this option and click Save.
Result
You now know how to configure some options related to Quickcards.
Note:
Do not confuse Employee Quickcards with Talent Cards.
LESSON SUMMARY
You should now be able to:
● Navigate in the Application with the Quick Cards
LESSON OVERVIEW
In this lesson, you will learn how to manage mobile settings.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Enable Mobile Functionality
● Add Mobile Users
● Manage Mobile Settings
Mobile settings are enabled by going to Action Search → Enable Mobile Features, and
selecting the mobile features you wish to enable. This functionality helps you to select which
modules are available to your mobile users. The features include: having a mobile access code
to access a mobile device and enabling mobile advertisements.
The Enable Mobile Feature has the following distinct sections:
● Mobile Specific: The features in this section allow you to view and control basic mobile
functionality. (For example, Theming, on device support, PIN, and so on)
● Modules: In this section, you can view all the SAP SuccessFactors modules that are
currently deployed in your instance and have mobile capabilities available.
Checking the checkbox will turn ON the functionality for all authorized mobile users.
Unchecking the checkbox will turn OFF the functionality for all authorized mobile users.
Mobile features
Note:
Push notifications are only sup-
ported in the current version of
iOS and Android SAP Success-
Factors Mobile apps.
Module Description
SAP SuccessFactors currently supports the most popular mobile platforms in the market. As
an administrator, you can enable or disable mobile settings for the employees of your
company. Mobile features are accessed through the SAP SuccessFactors Human eXperience
Management (HXM) apps.
Mobile administration is simplified and aggregated in the Mobile Administration Panel. In this
panel you will see four main features that will help you deploy and manage Mobile for your
company:
● Enable Mobile Features
● Manage Permission Roles
● E-mail Template Notifications
● Manage Mobile Users
In this section, you learn how to enable mobile features, select mobile access permissions,
and how to deactivate mobile devices.
To specify which users can access their SAP SuccessFactors account, navigate to Action
Search → Manage Permission Roles → select the role you want to grant mobile access to
→ Permission... → General User Permission → Mobile Access, and then choose the
permission role you want to allow your users to access.
To have a controlled rolled out strategy, follow the steps above, but instead of selecting All
Employees, select the groups targeted for rollout. You can create a new specific “Mobile”
group if needed. You can give mobile access rights to as many groups of users as you wish,
and gradually roll out mobile access to different groups of users.
The Mobile E-mail Notification feature simplifies the mobile user activation process and raises
awareness of the new mobile capabilities among your workforce, we created a Mobile E-mail
Notification feature. This feature enables you to customize an e-mail template that will be
used to send a single e-mail notification to all users who have been granted mobile access.
When users receive the e-mail they see two links. When the links in the e-mail are selected
from their mobile devices, the users can perform the following functions:
● Download and install the SAP SuccessFactors mobile application from the corresponding
app store. This redirecting is automatic, based on the mobile operating system that is
detected.
● Activate the mobile application from the device. This process leverages the regular SAP
SuccessFactors web application login mechanism.
Select E-mail Notification Template Settings and turn on the Mobile Activation Notification e-
mail template that is now displayed at the bottom of the page as desired.
You can activate the mobile device of a user by going to Settings → Mobile and entering the
device activation code. After the device is activated, a list of devices associated with that user
and the option to deactivate that device will be listed.
Follow this one time process to sync your SAP SuccessFactors Mobile app with your SAP
SuccessFactors HXM account. Follow the step-by-step screens on your smartphone to
generate your unique activation code:
Business example
Demonstrate how to enable access for a mobile device user.
Business example
Demonstrate how to enable access for a mobile device user.
b) On the Permission Role List screen, in the Permission Role column, choose Full System
Administrator.
d) In the Permission Setting dialog box, in the User Permission list choose General User
Permission.
e) In the General User Permission section, verify that the Mobile Access check-box is
selected or activate it if it is not the case.
f) Choose Done.
h) If you made changes, don't forget to logout and login to ensure the changes are
applied correctly.
j) In the Mobile specific tab, activate the check-boxes for Notifications and Org Chart.
Each time choose Turn ON and OK.
k) For the Modules, activate Goal Management and Career Development Planning. Each
time, select Turn ON and OK.
LESSON SUMMARY
You should now be able to:
● Enable Mobile Functionality
● Add Mobile Users
● Manage Mobile Settings
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Make changes to e-mail templates
● Manage communications in SAP SuccessFactors with triggered e-mail notifications
1. To turn on a notification for all users, select the checkbox next to the notification. To turn
off a notification for all users, deselect the checkbox next to the notification.
When e-mail notifications are enabled and users have the appropriate permissions, the users
have the option to turn them on or off.
To Enable and Disable a Notification
E-mail notifications are generated from pre-configured templates in SAP SuccessFactors.
Here, you can enable and disable event-triggered notifications, as well as edit the signature,
message body, and other options associated with the notifications.
● To enable or turn a notification on for all users, select the checkbox next to the notification.
● To disable or turn a notification off for all users, deselect the checkbox next to the
notification.
● When finished, choose Save Notification Settings at the bottom of the page.
If e-mail notifications are enabled, users may have the option to turn them on or off depending
on how their company’s instance is configured, and/or if that permission is granted to users.
Note:
If a user chooses not to receive e-mail, this applies to all SAP SuccessFactors
notifications.
You can also use this option to troubleshoot when users indicate that they are not receiving
system e-mails, and can turn them back on.
Configuration Requirements
Digital Assistant is only available for a few Early Adopter customers. These customers must
have enabled the latest home page.
Business Example
In this exercise, you modify template settings in E-Mail Notification Templates and turn off e-
mail notifications.
2. Choose Welcome Message Notification with Reset Password Support and set the e-mail
priority.
Result
You modified template settings in E-Mail Notifications Templates.
1. Check the setting for E-mail Notifications in Company System and Logo Settings to
understand why you are able to switch off E-mail Notifications in the Setting of the Name
Menu.
Business Example
In this exercise, you modify template settings in E-Mail Notification Templates and turn off e-
mail notifications.
b) On the E-Mail Notifications Templates make sure that the following notification are
enabled:
2. Choose Welcome Message Notification with Reset Password Support and set the e-mail
priority.
a) Select the Set E-mail Priority, High Priority checkbox.
c) In the E-mail Subject field enter the following subject line: Welcome to
SuccessFactors!.
[[SIGNATURE]]
f) Verify that the new E-mail Subject and E-mail Body appear in welcome e-mail.
Result
You modified template settings in E-Mail Notifications Templates.
1. Check the setting for E-mail Notifications in Company System and Logo Settings to
understand why you are able to switch off E-mail Notifications in the Setting of the Name
Menu.
a) Via Action Search go to Company System and Logo Settings.
b) Make sure that the option: "This option allows a company-wide setting on whether
users will receive E-mail notifications. If 'checked', all users will receive E-mail on all
workflow related process. If not checked, each user has an option to turn notification
on/off." is not enabled. This means, that every user can decide if E-mail notification is
desired.
c) In the top right corner, open the Profile icon for your user.
d) Choose Settings.
e) Choose Notifications.
h) Choose OK.
LESSON SUMMARY
You should now be able to:
● Make changes to e-mail templates
● Manage communications in SAP SuccessFactors with triggered e-mail notifications
LESSON OVERVIEW
In this lesson, you will learn how to customize and manage the SAP SuccessFactors Instance.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Customize the SAP SuccessFactors application themes
Animation
For more information on this topic please view the animation in the lesson
Customizing the SAP SuccessFactors instance in your online course.
1 Search You can search for a theme by starting to type its name
or by filtering on locked (standard) or unlocked (custom)
themes.
2 Edit You can edit the custom themes by selecting the theme
names. The standard theme names appear in a lighter
color and are associated with a lock icon because they
cannot be edited.
3 Default There can only be one default theme per instance. This is
the theme that will be visible to the employees unless
there are in a group added in the column “Visible to”.
4 Visible to You can add groups of employees who will see a theme
different than the default theme.
The field used to group user to theme can be selected
from Provisioning > Company Settings > Field used to
group users to themes. There are three options: depart-
ment, division, and location.
5 Revert To stop testing the theme, you can choose Revert from
the options menu.
6 Duplicate This option allows you to copy an existing theme and is
used to create a new theme by changing the existing
theme.
7 Delete Choosing this option will delete the theme. Only custom
themes can be deleted.
8 Save or Cancel These buttons allow you to save or cancel the changes
based on your decision. They are always visible at the
bottom of the browser and you do not need to scroll
down to utilize them.
9 Save or Cancel These buttons allow you to save or cancel the changes
based on your decision. They are always visible at the
bottom of the browser and you do not need to scroll
down to utilize them.
These options give customers the capabilities to make the latest home page more consistent
with other pages in the application.
Note:
You cannot change the text color or background color of home page cards.
Changes to typography, visual treatment, and spacing have an impact on the overall layout
and location of elements on the page. If you run automated tests that are based onscreen
coordinates, they may be impacted by the Horizon theme.
For further information check: Horizon Visual Theme for SAP Fiori
Business example
Themes determine the colors and look of your SuccessFactors instance. Your company
theme was created during configuration; however, you can edit and modify it. You can
customize how screens display across your company, or you can choose to have screens
display differently according to group.
Result
You have Applied, Created, and Deleted a Theme.
Business example
Themes determine the colors and look of your SuccessFactors instance. Your company
theme was created during configuration; however, you can edit and modify it. You can
customize how screens display across your company, or you can choose to have screens
display differently according to group.
b) On the Manage Themes screen, choose the “SAP Fiori with Morning Horizon (light)”
radio button in the Default column to set this as the default theme.
c) Select Save.
b) On the Manage Themes screen, click on the three dots at the right-hand side of “SAP
Fiori with Morning Horizon (light)” and choose Duplicate.
c) On the Create a Theme screen and in the Theme name field, enter SF Theme.
f) Choose the Generate button to create additional shades based on the #9C81AA color
value. Then choose Generate again in the popup window.
g) Choose Save and then choose Save again in the popup window.
b) Choose the SF Theme radio button to make this the default theme.
b) Select the theme that was the default before you created your custom theme and
make it the default again. Global Training Theme II is usually the default theme.
e) Go back to the Theme Manager and delete the theme you created in the previous
exercise SF Theme. Select the 3 buttons to the right of the theme you want to delete.
Result
You have Applied, Created, and Deleted a Theme.
LESSON SUMMARY
You should now be able to:
● Customize the SAP SuccessFactors application themes
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Replace system text with Text Replacement
Note:
In the Text Replacement tool, the list of UI labels available for customization
differs from one language to another. For example, a UI label that can be
customized in English US may not be available for customization in French.
The custom UI labels that you define on the Text Replacement page override the default
values of the UI labels, wherever they appear in the application.
While there are many options to change system texts in Text Replacement in the English
language, the other languages do not necessarily have so many options. When using Text
Replacement it is important to understand that you are only doing a text substitution, which
does not change anything regarding the language specific grammar in the associated string. It
is possible to create linguistic issues if the custom UI labels are used incorrectly.
Business example
The company culture requires the use of company-specific terms instead of some of the
words used in SuccessFactors. You are assigned the task of customizing the text replacement
settings.
In this exercise, you customize the text for your SuccessFactors instance, and display the
customized text to verify the text replacement.
1. Change the variants of the word employee with the associate following the table below:
2. Display the customized text to verify the text replacement. (Please note: you may need to
log out and back in to see the changes.).
3. Revert the changes you have made by deleting all the variants of the word associate in the
customized text column.
Result
You customized the text for your SuccessFactors instance and verified the display of the
replacement text.
Business example
The company culture requires the use of company-specific terms instead of some of the
words used in SuccessFactors. You are assigned the task of customizing the text replacement
settings.
In this exercise, you customize the text for your SuccessFactors instance, and display the
customized text to verify the text replacement.
1. Change the variants of the word employee with the associate following the table below:
b) On the Text Replacement screen, enter the data in the table provided.
c) Choose Save.
2. Display the customized text to verify the text replacement. (Please note: you may need to
log out and back in to see the changes.).
a) On the Home page screen, choose the Home dropdown menu.
b) Verify that the option My Employee File is now called My Associate File.
3. Revert the changes you have made by deleting all the variants of the word associate in the
customized text column.
Result
You customized the text for your SuccessFactors instance and verified the display of the
replacement text.
LESSON SUMMARY
You should now be able to:
● Replace system text with Text Replacement
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Replace System Text with Manage Languages
Manage Languages
Use the Manage Languages tool to overwrite UI label values in any language (US English or
any language that SAP SuccessFactors currently supports).
The manage language change requests typically arise in two situations:
• You want to change default values of UI text (for example, system text) to better reflect your
particular business practices and culture.
• There is an issue with system text (for example, grammar, syntax or key terms). Manage
Languages allows for a quicker turnaround while waiting for the system text to be updated in a
subsequent patch or release.
Limitations
● Value replacement limit: You can overwrite up to 10,000 values per locale using Manage
Languages. The default replacement limit is set to 25 values, which you can manually
increase up to 10,000 using the Update option at the bottom of the page.
● Custom language pack CSV file size limit: The CSV file size limit is 10 MB. If you try
uploading a file that is anything more than 10MB, the system will time out and the file will
not be uploaded.
● Text substitution syntax: You need the text substitution syntax to replace a word
throughout the system. Otherwise, each string that includes the string will need to be
replaced through Manage Languages.
How can customers change a label in a specific locale that is not available in Text
Replacement?
Customers can use the Manage Languages tool from Admin Center to overwrite UI label
values in any languages supported by SAP SuccessFactors. The Manage Languages tool is
particularly useful in two situations:
● Default values of system text can be changed to better reflect a particular business
practices and culture.
● There is an issue with the current system text (grammar, syntax, key terms, and so on.).
Manage Languages allows for a quick turnaround while waiting for the system text to be
updated in a subsequent patch or release. Customers should still contact Customer
Support so that the issues can be addressed with system level text in future builds.
Prerequisites
There are two prerequisites that should be enabled in Provisioning → Company Settings:
1. Language Packs
The other prerequisite is the Text Replacement permission in RBP. From the Action Search →
Manage Permission Role → Administrator Permissions → Manage System Properties → Text
Replacement.
Limitations
● Value replacement limit: It is possible to overwrite up to 10,000 values per locale using
Manage Languages. The default replacement limit is set to 100 values. This can manually
be increased up to 10,000 using the Update option at the bottom of the Manage
Languages page.
● Custom language pack CSV file size limit: The CSV file size limit is 10 MB. If the file
represents more than 10 MB, the system will time out and the file will not be uploaded.
● Text substitution syntax: You need the text substitution syntax to replace a word
throughout the system. Otherwise, each string that includes that string will need to be
replaced through Manage Languages.
● Changing labels does not update the language phrasing used within the Mobile Application
at this time.
Procedure
1. Identify the token for the system text you want to replace using English Debug. From the
name menu, go to Settings → Change Language → English Debug → Switch .
2. Go to the page where you would like to change the label. In this example, we will change the
label for the home page from the main navigation menu. Get the value between the colons. In
this example it will be: COMMON_HOME_TAB
3. Go back to the name menu → Settings → Change Language and select again your default
language and choose Switch.
4. From the Action Search go to Manage Languages.
5. If a custom locale does not exist, you will need to create one. Under the Action column,
choose Add custom locale corresponding to the language pack.
6. It is required to enter a new name for the custom language pack such as English US
Custom, and choose OK. The custom language pack gets appended to the original language
pack.
7. A “+” button in now available in front the language for which you created a custom locale.
Select it.
9. Save the file on your computer. In the first row, the word Key will already be in the column
A. Add the locale code in the column B. In this example, it is en_US. Then in the second row,
add your key COMMON_HOME_TAB and the label you would like to see, for example Renamed
Home Page.
10. Save the file as a V2. It is important to keep the .csv format. Then, import it and upload it in
the system using theUpload custom label option. Select the file you created.
11. A message will indicate that the file was uploaded successfully. Choose OK.
12. In order to test the changes, make sure that you use the language for which you made the
change. You need to log out and go back to the instance and it some cases it can be helpful to
close your browser completely or even delete the cache.
Caution:
IMPORTANT NOTE
Be careful!
When keys already exist in this file and you want to make more changes to other
system text, always download the latest file for the custom label from the system
and add the new key to the list but keep those that are already there when you
upload. If you just put the one that you want to change in this file and remove the
other keys, you will delete the customization put in place for the other keys.
When keys already exist, the cell 1B will have the language code an underscore
and the company ID of the instance in which you make the change. To be able to
upload this file back into the system, you will only need to keep the language
code in this cell and therefore remove the last underscore and the company ID.
1. Download the CSV file of the original language pack. It has all the default system labels.
2. Save the file in a folder where you can find it easily on your computer. You can open your
CSV file with Open Office, Notepad or Notepad++. This file, which is the original CSV file,
contains the entire list of key values (Key) and their corresponding UI labels. The file should
look like the screenshot above.
Business Example: In this exercise you will learn how to change words in the system.
Result
You have changed a word in the system.
Business Example: In this exercise you will learn how to change words in the system.
c) Under “Debugging” find “English Debug” and enable it by clicking in the Actions
column on the word “Enable”.
g) Back on the Home Page note that the technical name for the salutation in the banner is
called “HOME_V4_Salutation_Morning”, “HOME_V4_Salutation_Afternoon” or
“HOME_V4_Salutation_Evening” (depending on time of the day).
k) Under “Locale List” find “English US (English US)” and click on “Actions” in the column
“Action”.
l) Click on “Download Default Labels” and note that a csv-file called “en_US_default.csv”
was downloaded on your computer.
m) Open this csv-file and note that the first column is the “Key” and the second column is
the language that will be modified.
Note:
Please always use Open Office to open, edit and save csv-files for
SuccessFactors. This is because Microsoft Excel corrupts special
characters within some languages. Open Office allows you to work with all
of your files (particularly .csv) without corrupting characters.
i. HOME_V4_Salutation_Morning
ii. HOME_V4_Salutation_Afternoon
iii. HOME_V4_Salutation_Evening
o) Copy those three rows into a new csv-file and name the file “Salutations_THR80.csv”.
p) Add a new row at the top of this file and in the first column enter “Key” and in the
second column enter “en_US”.
r) Log into your instance and use Action Search to navigate to Manage Languages.
s) Under “Locale List” find “English US (English US)” and click on “Actions” in the column
“Actions”.
u) In the column “To-Do” click on “Upload now” and search for the csv-file
“Salutations_THR80.csv”. Click on open to start the upload and click on “OK” in the
confirmation box.
v) Refresh the page and check if the import was successful in the column “Custom
Translation” by clicking on the link “THR80_Custom”. Look for the success in the
“Validation of Last Upload”.
w) est your changes to the text: Go back to the Homepage via the main menu and note
that the salutation in the banner is changed to “Welcome to THR80”.
Result
You have changed a word in the system.
LESSON SUMMARY
You should now be able to:
● Replace System Text with Manage Languages
LESSON OVERVIEW
Consultants do not start the translation work until there has been sign-off of final
configuration. This lesson provides an overview of the translation process and walks you
through the step-by-step process. The steps in the translation process include gathering
requirements in a translation workbook, turning on language packs, and configuring
translations in Provisioning, Admin Center, and XML.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Implement translations to configuration labels
● Collect requirements in the Translation Workbook
● Set up languages in Provisioning
● Configure the Succession Data Model XML file in for translations
● Implement translations in People Profile
● Get every detail finalized and tested in the default language (English) first.
It is crucial that all configuration is complete before the start of translations. If your
customer continues to make changes to functionality and the default (English) labels, it is
impossible to keep the configuration workbook up-to-date. Finalize all labels and features
and conduct sufficient testing before the start of translations.
● The customer is responsible for providing translation, while the consultants provide the
workbook.
SAP SuccessFactors does not provide translation services. It is the customer’s
responsibility to provide translations and test these translations against their
configuration. Do not attempt to translate anything for the customer.
● Review the SAP SuccessFactors Offerings per Language Pack and the Detailed Language
Matrix on Partner Portal.
These matrices show the module support and feature support per language pack. Not all
modules or features are supported in all languages. Do not assume that the Writing
Assistant, Spell Check, Legal Scan, and so on, are supported for all languages.
● Get organized.
It is in your best interest to be very organized when coordinating translations. Plan ahead
to spend sufficient time gathering configured text and labels into the translation workbook
file. Make sure that the customer has also planned ahead for all resources to be dedicated
to translations and testing during this time. Be mindful of local holidays and vacation
schedules. For example, many employees in China take extended holidays in January or
February, and many employees in Germany take extended holidays in August. Ensure that
everyone on the project has set aside the time to meet the project milestones. Stick to the
plan. If you do not consolidate your documentation or milestones, it is extremely difficult to
stay in control of the process.
Translation process
If you configure a module in the default language (English), you need to translate it. When you
go to translate the label, you must go to the source where you configured it. The translation
process for each module varies. For labels that are visible in People Profile, translations can
come from the Succession Data Model, BCUI, Picklist Center, or Configure People Profile.
Text Replacement, Rating Scales, Route Maps, Configure Employee Files all control labels
directly where you configured the default language (English).
● In-App Translation
Edits are made within the application. Home page tiles, the Help & Tutorials page, and the
Company Resources page are translated by an administrator directly on the page.
Hint:
When configuring translations, do not forget to download backup copies before,
during, and after you translate a file. If you are translating something directly in
the application, you should save a copy in the configuration workbook before and
after you translate the text.
Note:
When configuring translations, you will most likely have to use Open Office. This is
because Microsoft Excel corrupts special characters within some languages. Open
Office allows you to work with all of your files (particularly .csv) without corrupting
characters. In addition, be aware that if you do not have all language packs
properly installed on your computer, you may have issues working with some
languages.
Language packs
The consultant verifies the language packs included in the contracts. The SuccessFactors
Statement of Work or Schedule A documents list out the languages that the consultant is
responsible for implementing
After a language pack is enabled, the language appears within Languages under the Settings
menu.
Company Resources
To set the language for the Company Resources page, proceed as follows:
Hint:
During the implementation project, this can be a task to delegate to the customer
project team in order to encourage the customer to learn more about the
system.
To set the language for the Help & Tutorials page, proceed as follows:
Note:
Help and Tutorials feature will be deleted on November 15, 2024.
Hint:
During the implementation project, this can be a task to delegate to the customer
project team in order to encourage the customer to learn more about the
system.
Hint:
During the implementation project, this can be a task to delegate to the customer
project team in order to encourage the customer to learn more about the
system.
Customer testing
The customer is responsible for testing the instance and consolidating all feedback or
changes by the agreed upon due date. Consultants can provide guidelines, but customers are
responsible for creating test scripts and conducting thorough testing. It is important for the
customer to keep testers focused on the language only, and not consider any feedback about
the configuration decisions or the process design. These topics are appropriate for iterative
testing and user acceptance testing (UAT), but not for translation testing.
After receiving configuration sign-off, consultants are responsible for providing the
translation workbook. The consultants fill out the template with the configured text and labels
for their customer in the default language (English). A translation workbook template is
available on PartnerEdge → Implement → Tools & Assets → Tools & Assets → Foundation
→ Configuration Workbooks.
Hint:
This is a good point in the translation process to make backup copies of all form
templates, goal plan templates, data models, and other files to be translated. For
areas that cannot be downloaded easily, take screenshots of the default
language (English) text and save them all in one file.
Workbooks are Microsoft Excel files with tabs for each template and module.
The consultant is responsible for filling out the workbook with the English or default language
translations. Go through each template and list every field name, introductory text, and label
that you configured. Put them in the workbook in the “English” column of the table. In each
additional column header, enter the customer’s language packs. Repeat for every template
and module that you are responsible for translating.
The Project Plan tab is provided if you want to enter the due dates for each milestone of the
translation process.
The Testing Plan tab is provided for the customer to outline their test plan. SAP
SuccessFactors does not provide test scripts for customers.
Review your customer’s configuration in the test instance from end to end, ensuring that you
have not missed any text. It can be difficult to go back and retrieve additional translations that
were missed.
If your configuration contains HTML, such as hyperlinks, bullets, and line breaks, be sure to
highlight this text in a bold red font. Include instructions for all translators to leave this text
intact and translate around it. If a translator happens to delete or overwrite your HTML, it is
going to be impossible for you to re-create the proper HTML structure and there are going to
be errors in your template.
After completing the translation workbook, the next steps are as follows:
1. Send the workbook to the customer by e-mail, or post the workbook to the customer’s
SharePoint site.
2. Provide the due date for workbook completion. Provide clear instructions for the customer
to translate the text in each language and provide one consolidated file back to you by the
agreed upon due date. You are not responsible for consolidating the translators’
responses. The customer must coordinate this and ensure that their translators are
following your instructions.
3. Customer must coordinate translations of all text in the workbook and maintain these
translations in one file.
4. Customer fills out the language translations and sends it back to the consultant.
5. Review the workbook that the customer has provided keeping the following questions in
mind:
● Did the translators translate all labels and text in all languages?
6. If necessary, alert the customer of any translations that were missed, HTML that was
corrupted, and so on. Do this before you begin working on configuration of the languages.
Translation configuration
When one file with all translations has been provided by the customer, you can begin to
configure the translations. You configure the translation in a test instance. It is important that
you always translate everything in the test instance before you move into the production
environment.
Customer approval
When a customer requests a change to system text, or the inclusion of text that is not found
within the workbook, the customer should use the Translation Feedback template that is
available on SharePoint and Partner Portal. Ask the project team to verify all system text
changes from language testers and ensure that the text is not listed somewhere in the
workbook. The project team should also filter out changes that are not essential and
communicate with their testers before sending you unnecessary requests.
The customer must provide you with the following:
● A full-page screenshot of the areas where they see this text.
● The current English text.
● The current {LANGUAGE} text in its entirety. Full sentences or paragraphs are required.
● Their proposed changes in entirety. Full sentences or paragraphs are required.
Remind customers that you do not speak all of the languages that they have purchased and
therefore require very detailed requests with screenshots for all questions or system text
changes. In addition, remind the customers that not all system text changes can be made.
To find the list of language packs, log into Provisioning and choose Company Settings. When
the instance is created through Auto-Provisioning, languages should be enabled
automatically. If they are not enabled, select the checkbox next to the language packs that
you must enable, and then choose Save.
XML template
For Goal Management translations, in the code (Goal Plan name, categories, field labels, and
so on) when you find English text that was configured, copy the tag and add the relevant
language tag, for example, lang=“de_DE”.
When you are configuring Employee Profile Translations, configure Standard Elements and
Background Elements directly in the Succession Data Model. You must add a row with a label
for each element. For background elements, every column label is also translated in the data
model.
Hint:
Copy and paste errors happen. Save and upload the data model frequently so
that you do not spend a long time configuring only to receive an error message
due to something that may not be easy to spot. At a minimum, you should back
up your data model before, during, and after your translation work.
Watch the 'Translate Fields in the Profile' video for an in-depth explanation.
Watch the 'Translate Picklist Values and Test the Translations' video for an in-depth
explanation.
Business Example: In this exercise you will learn, how to translate a data field name in the
People Profile.
Result
You have translated a data field name.
Business Example: In this exercise you will learn, how to translate a data field name in the
People Profile.
d) Note that “Français (French)” is added to your languages in the column “Locale”.
f) At the left side under “Employee Profile” click on the link “Standard” to collapse the
column and click on “First Name”.
g) Click on “Take Action” and “Make Correction” and on the global icon next to “Label”.
h) Enter “Prenom” in field next to “French (France)” and click on “Done” and on “Save”.
k) In the main menu click on “Mon dossier d'employé“ and note, that “First Name” is
translated to “Prenom”.
l) To switch back to English languages click on the name menu and on “Paramètres”.
Result
You have translated a data field name.
LESSON SUMMARY
You should now be able to:
● Implement translations to configuration labels
● Collect requirements in the Translation Workbook
● Set up languages in Provisioning
● Configure the Succession Data Model XML file in for translations
● Implement translations in People Profile
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Update Company Dictionary
● Modify Legal Scan Library
4. Choose Add.
5. When the textbox is populated with the company name, choose Done.
Business Example: In this exercise you will learn, how to manage the Company Dictionary.
Result
You have managed the Company Dictionary.
Business Example: In this exercise you will learn, how to manage the Company Dictionary.
c) Type SuccessFactors into the blank field and click on “Add” and “Done”.
b) Set the radio button to “Download Company Dictionary File” and click on “Download”.
d) Open the txt-file on your computer and note, that the word “SuccessFactors” is
already in the Company Dictionary (because of task 1 of this exercise).
e) Add the word “SAP” on a new line and save the file.
f) Log into your instance. Use Action Search to navigate to Company Dictionary.
g) Set the radio button to “Import a word list (words separated by newlines) File” and
click on “Choose file”.
Result
You have managed the Company Dictionary.
LESSON SUMMARY
You should now be able to:
● Update Company Dictionary
● Modify Legal Scan Library
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Set up a Company Logo
Note:
We recommend that you have your logo hosted on SAP SuccessFactors servers to
ensure a secure and consistent environment. For best results, we recommend
your logo be prepared as follows:
● File format: Transparent GIF
● Pixels: 210 wide x 40 high
● Color mode: RGB
Note:
Using this method can cause warning messages to display for your users, as SAP
SuccessFactors is a secure website and your logo is posted on a site outside of
that secure environment.
LESSON SUMMARY
You should now be able to:
● Set up a Company Logo
Learning Assessment
X A A tool to replace “system” text when that text is not available for replacement via
Text Replacement in Admin Center.
X B A configuration choice for a customer to select one template that will display labels
in the local language of each user.
3. With Manage Languages, you should exercise caution when modifying system text and
limit changes when possible.
Determine whether this statement is true or false.
X True
X False
4. Where does an end user in the instance choose the language they wish to work in?
Choose the correct answer.
5. For which of the following does the consultant enter the translations directly in Admin
Center?
Choose the correct answers.
X A Rating Scales
X B Route Maps
X C Text Replacement
X D Employee Profile
6. Consultants must be able to speak and read the languages for which the customer has
purchased language packs.
Determine whether this statement is true or false.
X True
X False
9. Enabling language packs turns on translations for basic system text, error messages, and
menu labels.
Determine whether this statement is true or false.
X True
X False
X A Consultant
X B Customer
X C SAP QA Team
Lesson 1
Configuring Succession Data Model and Configure People Profile 287
Exercise 28: Working with the Data Model 315
Lesson 2
Managing Business Configuration 323
Exercise 29: Modify the Succession Data Model with Business Configuration UI 325
Lesson 3
Maintaining Picklists in the Picklist Center 328
Exercise 30: Create a New Picklist for a Standard Element 335
Lesson 4
Managing the User Data File 340
Exercise 31: Manage Employees and Import Permissions 357
Exercise 32: Maintain employee records in the User Data File 359
UNIT OBJECTIVES
LESSON OVERVIEW
In this lesson, you will learn how to use XML in SAP SuccessFactors.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Modify the Extensible Markup Language (XML) files
● Validate the Extensible Markup Language (XML) file with a Document Type Definition
(DTD) file
● Verify that the Extensible Markup Language (XML) file is well-formed
● Define the key Extensible Markup Language (XML) terms
● Configure the Succession Data Model to Make Changes in SAP SuccessFactors
● Import and Export the Succession Data Model XML in Provisioning
● Download the Succession Data Model from Admin Center
● Navigate in the Different Elements of the Succession Data Model
● Use Admin Center and Succession Data Model to configure People Profile
● Configure standard elements in People Profile
● Configure Custom Fields
● Manage the People Profile using the Configure People Profile tool
● Maintain the People Profile using Header Settings
● Hide, show, and upload a photo into People Profile
● Run Batch Upload and Batch Export processes
XML
XML is an abbreviation for eXtensible Markup Language which is one of many markup
languages devised for different purposes. It was designed primarily to transmit data between
disparate computer systems that would normally not be able to interact. It is sometimes
described as a bridge language because it can be used as a common language that two
computer systems can use to communicate with each other. XML is special because it does
not contain predefined tags. XML tags are defined only by the user and this is what makes it
an extensible language.
A further advantage of XML as a language is that it is fairly easy for humans to read and
understand.
HTML is another markup language that is widely known since it is used for building web
pages. While XML and HTML have some similarities in the syntax they use, they are designed
to meet different business needs. HTML is designed to display data in a Web browser whereas
XML’s objective is to store and transmit data. But they are both forms of SGML, or
Standardized Generalized Markup Language, which is itself a standard.
XML is widely used and there are several resources on the web to help people learn basics
about the language. One particularly helpful website, W3 Schools, has an excellent tutorial on
XML:
W3 Schools XML Tutorial
XML Tree
XML is structured into a tree where the family members are called elements. An element
describes the data that it contains. The first element in an XML document is called the root
element. Elements can contain sub-elements and can also have attributes. Sub-elements are
often referred to as child elements. Child elements are always nested inside of parent
elements.
An XML tree always starts with a root element. As in a family, XML has parents and children.
Sample XML
Two other topics that are crucial to working with XML are tags and attributes.
Tags
Tags are used to identify elements not only to humans but to computers that must read XML.
The easiest way to understand tags is to see some examples. The following is an example
taken from W3Schools:
● <note>
● <to>Jane</to>
● <from>John</from>
● <heading>Reminder</heading>
● </note>
In the code above there are several pairs of tags. Each starting tag has a matching ending tag.
For example, <note> is a starting or opening tag and </note> is an ending or closing tag.
The difference is that the closing tag has a / in it whereas the opening tag does not. So this
example has 10 tags. Those 10 tags also help define 5 elements (note, to, from, heading and
body). The <note> element is a parent that contains 4 child elements (to, from, heading and
body). We can see this because the note opening and closing tags surround our encapsulate
all of the other elements.
Attributes
Attributes can be added to elements to help better describe them or make them more flexible.
For example, if we want to have different types of notes that are different colors, we can
modify the code of the earlier example and add an attribute for color:
● <note color="blue">
● <to>Jane</to>
● <from>John</from>
● <heading>Reminder</heading>
● </note>
In the example above, color is an attribute of the element <note> and blue is the value of that
attribute. Attributes are always surrounded by quotation marks.
<!DOCTYPE note
[
<!ELEMENT note (to,from,heading,body)>
<!ATTLIST note type (personal|business) personal>
<!ELEMENT to (#PCDATA)>
<!ELEMENT from (#PCDATA)>
<!ELEMENT heading (#PCDATA)>
<!ELEMENT body (#PCDATA)>
]>
The above DTD can be referenced by an XML document intended to be used as a note. A note
based on this definition has a root element <note> and it must have 4 additional elements
defined (to, from, heading and body). Additionally, the <note> element has an attribute
called type that will allow it to be either a personal or business note. The following XML
document references this DTD and is well formed and valid:
XML Validation
When working with XML, it is also important to understand the two kinds of XML validation.
Well-formed XML means that the document follows the correct XML syntax. There are some
rules to XML, and you can see these five conditions in the figure, XML Validation.
Valid XML is more rigorous. Valid XML is both well-formed and follows all of the rules that you
set out in your DTD. The good news is that your XML editor checks for this automatically
when you choose Validate.
XML Vocabulary
Review the following terms used in XML throughout People Profile.
Term Definition
Note:
Even if you have already downloaded a file from an instance, before beginning
work on a data model xml file, always download a new version of the file. It is
possible that there have been changes to the file since you last worked on it,
especially if other consultants work for the same customer or if the customer uses
BCUI.
5. Choose the appropriate option for the action you want to perform:
● To Export the xml file, use the radio button by Export. Choose Submit.
● To import, use the radio button by Import. Use the Browse function to find the file on
your local machine and then choose Submit.
Note:
The version control does not record changes made from BCUI, but only pertains
to data model loaded via Provisioning.
Some customers want to download the complete Succession Data Model XML for backups
prior to a release, as a security requirement for monthly backups or for other integration
purposes.
Users need to have the permission Export Succession Data Model available in Manage
Permission Role under the Admin Center Permissions category.
Animation
For more information on this topic please view the animation in the lesson
Configuring Succession Data Model and Configure People Profile in your online
course.
Standard Elements in the Succession Data Model define the fields that are seen in People
Profile in SAP SuccessFactors. These are fields where there is a one to one relationship
between the field and the data.
Defining these fields in the xml will allow the users to modify their default behavior such as
making it a picklist or modifying its label. Some of the Standard elements are also those
where data can be imported/exported via the User Data File.
There are several predefined fields. It is possible to modify the label. It is even possible to use
a field for a purpose other than that intended by SAP SuccessFactors. However, it is not
recommended, so do it only after careful consideration. The length or type of the field may be
restricted and may not suit its new purpose. Also, while the use may seem to work now, it can
have consequences downstream that may not be correctable. There are 15 custom Standard
Elements available to you besides the predefined ones and those should suffice for most
requirements.
Userinfo Elements
Userinfo Elements can be used in the Profile and other areas like Recruiting.
Userinfo elements can be associated with a picklist and if the attribute reportable is defined,
they can be made reportable.
People Profile
SAP SuccessFactors People Profile connects employees and supports talent decisions by
delivering relevant, community-enriched employee information through an integrated
repository.
With People Profile, you can view and edit a person's entire profile on one simple,
consolidated page and take immediate action. You can quickly find the most important or
most recent information and drill down to see more detail when needed. The responsive SAP
Fiori design means that People Profile adjusts to fit your device, for optimal viewing on
desktop, tablet, or smartphone.
Administrators can use a convenient drag-and-drop configuration tool to set up People Profile
for your company. You can select which data fields to highlight at the top of the page and
control the layout and organization of profile content for your company. Visibility of employee
data on the profile is controlled by Role-Based Permissions.
The People Profile page is organized into sections, subsections, and blocks. Related
information is grouped together in "blocks" and appears directly on the page background.
Details are hidden at first view, to reduce clutter and make the page easier to scan quickly.
You can expand or collapse subsections and blocks to show or hide details as needed.
1. In the upper left-hand corner of your instance, choose the Navigation Menu and choose My
Employee File.
3. You can see your personal information, such as name, e-mail, location, and so on. The
fields listed in this portlet vary depending on your company’s configuration as well as your
permission level.
Profile header
The People Profile includes a configurable page header that displays the profile photo and
basic information about an employee.
As you scroll down the page, the header then reduces into a collapsed state and sticks to the
top of the page, for easier navigation, as shown here.
Information blocks
The People Profile page is made up of the ‘profile header’ and one or more profile ‘sections’.
Each section consists of one or more ‘subsections.’ Each subsection, in turn, consists of
either one or two ‘blocks.’
Some blocks are predefined and are not configurable, such as the Succession block, while
other blocks are customizable and allow you to configure which data to display, such as User
Info or Background blocks.
Most blocks take up one column of a two-column subsection. So, in most cases, you can fit
two blocks in each subsection. Some blocks, such as Badges or Skills, take up the full width of
the subsection.
The Standard Elements are the fields that you see in your instance, such as name, hire date,
address, phone number, and so on. Defining the fields can include changing the labels as well
as determining if a field is required. You will then configure the permissions for the Standard
Elements. This helps the system determine who has access to each field and the level of
access, read or write. For example, an employee may be able to see, but not edit his or her
hire date.
If you want custom-filtering fields, these are maintained in the data model as well.
Once you have made the appropriate changes to the data model and imported the file, you
can change the field order within Admin Center.
Note:
To make updates to the data model, you must open the XML file with an XML
editor. Oxygen and Notepad++ are very popular throughout the industry. XMLPad
is a Windows only software and is available for download online using CNET.
When reviewing the XML Data Model, you will see three primary elements:
● Standard Elements: Used to define the fields and labels used in the Employee Profile.
● Background Elements: Used to define data field mappings to the SM_Background table
(no updates to this element will be made in this course).
● Custom Filters: Used to turn one or more of the 15 custom fields into a filter that can be
used in the system for tasks, such as reporting.
When working with data models in SAP SuccessFactors, there are some file management
considerations. First, we have created a folder specifically for the versions of the data model.
In the figure, File Management of the Data Model, file A is our original data model. This is the
backup and should never be edited. Files B and C are version one and version two of the data
model file. Using Save As and creating file versions is a best practice when working with SAP
SuccessFactors data models and should always be followed.
Figure 139: Import and Export the Data Model From Provisioning
The Succession Data Model is located in Provisioning under the header Succession
Management. It is very important to note that the data model is a single file that overwrites
upon upload. When downloading and making changes to a data model, it is crucial that you
back up the original data model and use very strict version control to avoid time-consuming or
critical errors, particularly when working in a customer environment. To download the
Succession Data Model from your instance, proceed as follows:
It is possible to back up multiple versions of the Succession Data Model in Provisioning and
restore a version for the instance. This feature helps protect the configuration and track data
model changes. In case of issue, it can speed up the instance recovery.
Comments can be added during the import. It is then easy to download a certain version.
The system keeps up to 100 versions of the Succession Data Model backup. Earlier versions
are deleted when the limit is reached.
Note:
The version control does not record changes made from BCUI, but only pertains
to data model loaded via Provisioning.
Standard Elements
The Standard Elements are where we define the standard, single value fields that are seen in
the Personal Information section of the People Profile. Each of the fields that we see in the
Personal Information portlet relates to a Standard Element in the data model. For example,
the Last Name field is controlled by the Standard Element that begins on line 13 in this sample
data model. The order of the elements, however, is not defined within this data model.
Many elements (fields) already exist in the data model downloaded from Provisioning. You
can search for these elements using the search functionality of your XML editor. One of the
first and most common tasks requested is to change the label of a standard element. For
example, if the default label for the first element is Username but you would like it to read
Login, proceed as follows:
2. Look for the <label> tags and update the text in between those tags to say Login.
When configuring a Standard Element, other common changes include the following:
● Making a field a required field, by setting the required attribute to “true”.
● Changing labels to reflect multiple languages.
● Adding a picklist to a field.
Configuration Testing
To see the changes reflected in your instance, you must save a new version of your data
model and then import the file into Provisioning. Follow the same instructions as when you
downloaded the file; however, this time, simply choose Import File. Once you receive the
message that your template has successfully uploaded, you can log onto your instance to see
the updates.
Watch the 'Change a Label in the Profile from the Data Model' video for an in-depth
explanation.
1. In your data model, change the label to meet the customer’s requirements.
2. In Admin Center, configure the People Profile to include the new custom field.
The following image illustrates how the above profile is configured in the Configure People
Profile admin tool.
Note:
Although a new section called "Section 2" has been added, it currently does not
contain any information blocks and, therefore, does not yet appear in the profile UI
above.
the information that appears in the profile header, set the data source and date range for
ratings data, and add localized translations of custom labels.
To access the configuration tool, you can use search or go to Admin Center → Employee
Files → Configure People Profile.
2. Select the desired settings. For a description of each setting, see the link below.
Setting Description
Configure Header Fields Opens a dialog that allows you to configure
which data fields are displayed in the profile
header. See Configuring Header Fields for
details.
Allow employees to edit background image If checked, users can upload their own back-
ground "cover" image to their profile header.
Disable background image uploading by em- If you check both this option and the Allow
ployees employees to edit background image option,
users change their background image only by
choosing one from the image library.
Manage background image library Opens the existing Manage Background Im-
age Library dialog, which allows you to man-
age the images from which users can select a
background "cover" image for use in their
profile header.
Allow employees to upload an audio file for Enable the "My Name" feature, allowing
name pronunciation users to upload a short audio clip or enter a
phonetic spelling to show how their names
are pronounced. To enable this feature, ad-
mins are also required to accept a user
agreement acknowledging that all media
content is stored in the SAP data-center in
Germany. Users aren't presented with this
agreement.
Allow employees to upload an About Me vid- Enable the "About Me" feature, allowing
eo users to upload a short video about them-
selves. To enable the "About Me" feature, ad-
mins are also required to accept a user
agreement acknowledging that all media
content is stored in the SAP data-center in
Germany. Users aren't presented with this
agreement.
Allow employees to enter an introductory If checked, users can enter a short text about
text themselves, of up to 500 characters, which is
visible in the profile header.
Set all fields as expanded by default If checked, when employees access the Peo-
ple Profile page, all the content that they
have permission to access on the page is dis-
played. Employees can choose to show less
or more content in blocks as needed.
Choose the name format displayed on the You can select one of the name formats con-
profile. figured in SAP SuccessFactors Employee
Central to display in the profile header.
3. In the Configure Header Fields dialog, select one of the Custom Field checkboxes.
You can decide whether to hide or show the employee profile photo in the header of the
People Profile.
The profile photo is treated like any other employee data field in the header, such as the
employee's job title or location. As with other data fields, you can control visibility of the
profile photo in the header in two ways as follows:
● If you want to remove the photo from the header entirely for all users, uncheck the Photo
checkbox in the Configure Header Fields dialog box.
● If you want the photo to be visible to some users of your system, but not to others, check
the Photo checkbox in the Configure Header Fields dialog box, and then control the
visibility of the photo with Role-Based Permissions.
● Users can also hover over the place where the photo should be.
With either option, users will be able to select an image stored on their computer or drag and
drop an image. The following file formats are supported: JPG, JPEG or PNG. The file size
should not be larger than 2MB and an aspect ratio 3:4 is recommended.
Batch upload
● The photos should be uploaded to a directory on the ftp site configured by SuccessFactors
operations for use with your instance. It will typically be /photos.
As with all other photos, JPEG file format is recommended, and should adhere to the same
size and dimension guidelines described above.
● In addition, a csv file must accompany the photos to map the photo filenames to the
username of the employee they correspond to.
Load the csv file into the same /photos folder as the images. The csv file should be named
"employee_photos_yymmdd.csv", where yymmdd is the year, month, and day that the file
is loaded.
The csv file should include a header of "Username" followed by "Filename". The following
figure shows an example.
● You can upload employee photos in ZIP files. This option is off by default.
● There is also an option to delete each photo file from the FTP site immediately after it is
imported, including ZIP files. Always select this option if using a SuccessFactors FTP
server.
● After the upload completes an e-mail will be sent to the administrator named in the
scheduled task.
● Important: at this time there is a limit of 5,000 photo files that can be processed in a single
pass. If you have more than 5,000 photos to upload, make sure that they are separated
into different CSV files and different scheduled uploads.
Note:
We no longer support the upload of photos hosted at an external URL.
Batch export
With the export, the exported files include a csv file with two columns the username and the
file name and the related employee photos.
The exported files will be stored on and FTP server according to the job configuration.
Note:
If the user does not have photo, it will not be included in the exported files. The
exported files could be reused for batch with the upload employee photos job in
Provisioning.
● Every customer is entitled to have two SFTP accounts for Bizx, One for Test/Preview and
one for Production.
● In order to have an SFTP account created for themselves, customers can contact
customer support. Credentials can only be shared to an e-mail address from within the
Company Domain.
Business example
You are required to make changes to People Profile. You must first download the data model
from Provisioning and then download the DTD file from Course Files.
Note:
In this step, you create an XML file that is required for subsequent exercises in the
course.
Use the sf-form.dtd available in the Course Files you downloaded at the beginning
of this training.
2. Select your company instance, download and save the data file.
1. Make sure the sf-form.dtd file is in the same folder as your XML file.
3. Open the file you saved in the previous task, change the DTD file path. You must change
the DTD file path to refer to a DTD in your local folder instead of referring to the internal
svn repository for SAP SuccessFactors since you cannot access that location. Validate the
XML after the change.
1. Open the data model file and change the Country label to Country of Residence.
2. Search for the standard element ID custom01, and change the label from Customizable
Field 1 to Region.
3. Search the standard element with the ID custom02, and change the label from
Customizable Field 2 to Marital Status.
4. Validate your changes and save the data model as a new version (_V2 in the name).
5. In Provisioning, import your updated data model. You may see warning messages but the
system should indicate "Template(s) has(have) been uploaded and saved.”
2. Use the Action Search to navigate to Configure People Profile or on the Admin Center
screen, navigate to Employee Files → Configure People Profile.
3. On the Profile Section, choose the Personal Information sub-section and Personal
Information block.
5. Add Region and Martial Status in the list of fields and move it under the Last Name field.
Business example
You are required to make changes to People Profile. You must first download the data model
from Provisioning and then download the DTD file from Course Files.
Note:
In this step, you create an XML file that is required for subsequent exercises in the
course.
Use the sf-form.dtd available in the Course Files you downloaded at the beginning
of this training.
2. Select your company instance, download and save the data file.
a) Choose your Company Name.
c) On the Import/Export Data Model screen, select the Export file (Select ‘Save’, not
Open’) radio button.
d) Choose Submit.
f) In the Save As dialog box, specify where you want to save your file.
g) Choose Save.
The file is saved as an XML file. Make a note of the file location, you will need it in the
next exercise.
1. Make sure the sf-form.dtd file is in the same folder as your XML file.
3. Open the file you saved in the previous task, change the DTD file path. You must change
the DTD file path to refer to a DTD in your local folder instead of referring to the internal
svn repository for SAP SuccessFactors since you cannot access that location. Validate the
XML after the change.
a) In the XML editor, choose File → Open.
b) Navigate to the location where you previously saved the data file.
Note:
The link points to an internal SAP SF repository built in Apache Subversion
(abbreviation svn) that external users cannot access.
d) To validate the XML code, from the menu, choose XML → Validate.
1. Open the data model file and change the Country label to Country of Residence.
a) Open the data file you saved in a previous exercise.
b) Search the XML document for the standard element with the ID country.
c) Change the label for this element from Country to Country of Residence.
2. Search for the standard element ID custom01, and change the label from Customizable
Field 1 to Region.
a) Search the XML document for the standard element ID custom01.
3. Search the standard element with the ID custom02, and change the label from
Customizable Field 2 to Marital Status.
a) Search the XML document for the standard element ID custom02.
b) Change the label for custom02 from Customizable Field 2 to Marital Status.
4. Validate your changes and save the data model as a new version (_V2 in the name).
a) From the menu bar, choose XML → Validate.
If there are any errors, review your configurations and update as required.
c) Since version control is very important, be sure to save the file as a new version.
5. In Provisioning, import your updated data model. You may see warning messages but the
system should indicate "Template(s) has(have) been uploaded and saved.”
a) Log in to Provisioning.
d) On the Import/Export Data Model screen, select the Import File radio button and then
Choose File .
e) On the Choose File to Upload dialog box, navigate to the file you saved previously and
choose Open.
2. Use the Action Search to navigate to Configure People Profile or on the Admin Center
screen, navigate to Employee Files → Configure People Profile.
3. On the Profile Section, choose the Personal Information sub-section and Personal
Information block.
5. Add Region and Martial Status in the list of fields and move it under the Last Name field.
LESSON SUMMARY
You should now be able to:
● Modify the Extensible Markup Language (XML) files
● Validate the Extensible Markup Language (XML) file with a Document Type Definition
(DTD) file
● Verify that the Extensible Markup Language (XML) file is well-formed
● Define the key Extensible Markup Language (XML) terms
● Configure the Succession Data Model to Make Changes in SAP SuccessFactors
● Import and Export the Succession Data Model XML in Provisioning
● Download the Succession Data Model from Admin Center
● Navigate in the Different Elements of the Succession Data Model
● Use Admin Center and Succession Data Model to configure People Profile
● Configure standard elements in People Profile
● Configure Custom Fields
● Manage the People Profile using the Configure People Profile tool
● Maintain the People Profile using Header Settings
● Hide, show, and upload a photo into People Profile
● Run Batch Upload and Batch Export processes
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Manage Business Configuration
For more information see the Implementing and Managing Business Configuration (BCUI) on
the SAP Help Portal.
Business example
The customer wants to make an adjustment to the profile. You will use BCUI to adjust the
label of a custom field and link that field to an existing picklist.
2. Change the label for the custom02 field from Marital Status to Matrimonial Status.
4. Test your modifications from the end user view in My Employee Files.
Business example
The customer wants to make an adjustment to the profile. You will use BCUI to adjust the
label of a custom field and link that field to an existing picklist.
2. Change the label for the custom02 field from Marital Status to Matrimonial Status.
a) Select Standard to open the list of standard elements.
b) Select custom02 and modify the label from Marital Status to Matrimonial Status.
b) Select Save.
4. Test your modifications from the end user view in My Employee Files.
a) From the main navigation menu go to My Employee File.
c) Verify that the Marital Status field was changed to Matrimonial Status and that it is now
associated with a picklist.
LESSON SUMMARY
You should now be able to:
● Manage Business Configuration
LESSON OVERVIEW
This lesson provides an introduction to picklists in SAP SuccessFactors. The lesson includes
information on how to add, edit, export, and import picklists.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Maintain picklists using the Picklist Center
A picklist is a configurable set of options from which a user can select, typically in a dropdown
menu or smart search list. You can define the picklists used in your system to limit the values
a user can enter in a form, preventing them from entering an invalid value. Picklists can also
have a "parent-child" relationship, in which options in the child picklist are associated with
options in the parent picklist. These are also called "cascading picklists".
For example, in places where users must select a country, they might also need to select a
state or province within that country. Rather than have one very long list of all the possible
states and provinces in all countries, you want the options in the State picklist to be
dependent on the Country selection. In this way, users can only choose a state or province
that is within the country they selected. To do this, you would set up the Country picklist as
the "parent" and each corresponding State or Province picklist as its "children".
Historically, picklists in different SAP SuccessFactors solutions have been managed using
different tools: the Picklists import/export tool for legacy picklists and the Metadata
Framework (MDF) tools for MDF picklists. Management of legacy picklists is cumbersome
and error prone.
Picklist Center
As an administrator, you can manage picklists using the Picklist Center. In order to do that,
you will need Picklist Management and Picklist Mappings Set Up permission.
Picklists, picklist versions, or picklist values cannot be deleted. You can only deactivate a
picklist, picklist version, or picklist value.
Picklists can also be imported and exported. If your instance has been migrated to MDF
picklists, you can see the new required field LegacyPicklistID added to the exported CSV file
and the picklist import template.
Picklist Fields
Field Description
Code Unique business key that is used to identify the picklist.
(If you are familiar with legacy picklists, this is the equiv-
alent of the picklist ID.)
Parent Picklist A picklist can have a parent picklist. For example, if only
certain states can be chosen when a specific country is
selected, the Country picklist is the parent of the State
picklist. When legacy picklists are migrated to MDF pick-
lists, an optionId is generated for existing MDF picklist
values. For legacy picklist options that have been mi-
grated, the existing optionId is stored in the mapping ta-
ble.
Display Order Order in which the picklist values are listed in the picklist
dropdown, for example, alphabetically or numerically.
Name Unique name of the picklist. For example, if the picklist
is for the type of address (home, mailing, business, bill-
ing, and so on), you could name the picklist "Address
Type".
Status Specifies whether the picklist is active or inactive, that
is, whether it is available for use.
Effective Start Date A picklist can have different sets of picklist values for
different start dates.
Example: To add a new value New York to the Location
picklist but you want this picklist to be available for this
location after January 1, 2017. Enter in 01/01/2017 as
the effective date, the picklist with the new value is
available after January 1, 2017.
Note:
At this stage, Employee Central UI does not
respect MDF picklist effective dating.
Legacy Picklist ID The legacy picklist IDs can be edited from the Picklist
Center after the migration to MDF.
Instance sync on picklists is no longer allowed if the
combinations of external code and legacy picklist ID in
source and target instance do not match. You can edit
the legacy picklist ID to make sure that they match. The
legacy picklist ID must be unique across all picklists.
Watch the 'Associate a Picklist to a field in the SDM' video for an in-depth explanation.
Exporting picklists allow you to migrate the picklists from one instance to another with the
existing configurations. To export picklists:
2. From the Select the action to perform dropdown, select Export Data. A field corresponding
to Export Data appears.
4. From the Include Dependencies dropdown, select Yes to include the dependencies or No
to not include the dependencies.
5. To export the Entity ID and Record ID, select Yes from the Include Immutable IDs
dropdown otherwise select No.
6. To export the reference objects, select No from the Exclude reference objects dropdown
else select Yes.
7. To export all the picklists, select Yes from the Select all data records dropdown. If you
select No, a Select Objects dropdown appears. Here, you can specify which specific
picklists you want to export.
8. Click Export.
An export job is triggered. You can track the status of this job from the Action Search →
Monitor Jobs. When the status of this job is Completed, you can download the picklist
package using the Download Status link.
Note:
The results of the export of picklist values may differ from the values shown in
Picklist Center due to the selection of effective start date of the values. The export
will always show all the records of all the effective dates that exists.
Similar to export, you can also import your picklist. Once you are done making changes to the
exported picklist, you can import it back. You can import a picklist in two ways - CSV import
and ZIP import.
Select the type of import relevant to your situation:
● Use CSV import if you want to make minor changes like - updating existing values,
changing a label or adding values to the picklist.
● Use ZIP import if you want to do full purge or change the picklist headers and values
separately. For more information about this second option, please review the
Implementing the Metadata Framework (MDF) guide on the Help Portal.
2. Select Import Data from the Select the action to perform drop-down list. Fields
corresponding to Import Data appear and by default CSV File tab is selected.
4. Select Choose File to select the CSV file to import in the File field.
5. Specify the file encoding from the File Encoding dropdown list.
Note:
You are not allowed to use Full Purge in CSV format as it leads to data loss. For
example, if a picklist is referenced by an object, then after the full purge the
reference goes off.
7. Select Yes to remove redundant effective-dated records from the Suppress Redundant
Date-Effective Records dropdown list. Otherwise, select No.
8. Choose Business Key or External Code as the Key preference. Make sure that you select
the same key preference as the one you chose when you exported the picklist.
9. Choose Yes in the Use Locale Format and select the locale in the Locale field. Otherwise,
choose No.
10. Choose Yes in the Enable Decimal Round Option field if you want to round decimal values.
Otherwise, choose No.
11. Choose User Id or Assignment ID as the Identity type. Make sure that you select the same
identity type as the one you chose when you exported the picklist.
12. Choose Import and check the import status in the Monitor Job tool.
Business example
Your customer has decided to attach a picklist to the Region field in People Profile. You are
creating a new picklist in Picklist Center. In the next exercise, you will learn to create a link
between the Region field and this new picklist.
4. Choose Save.
5. Each time, choose the + icon to add a picklist value and add the following regions:
Note:
This exercise depends on the Succession Data Model XML file configured
previously.
1. In your XML editor, open the XML file from previous exercises and add a picklist reference
to Region picklist.
2. Validate your changes and save your updated version of the data model.
3. Upload the new version of the Succession Data Model and test the modification in your
instance.
Business example
Your customer has decided to attach a picklist to the Region field in People Profile. You are
creating a new picklist in Picklist Center. In the next exercise, you will learn to create a link
between the Region field and this new picklist.
4. Choose Save.
5. Each time, choose the + icon to add a picklist value and add the following regions:
Note:
This exercise depends on the Succession Data Model XML file configured
previously.
1. In your XML editor, open the XML file from previous exercises and add a picklist reference
to Region picklist.
a) Choose File → Open.
d) Insert a blank line after the </label> tag and before the </standardelement> tag.
2. Validate your changes and save your updated version of the data model.
a) From the menu bar, choose XML → Validate.
b) If there are any errors, review your configurations and update as required.
e) Choose Save.
3. Upload the new version of the Succession Data Model and test the modification in your
instance.
a) Go to Provisioning → Import/Export Data Model.
b) Make sure that the radio button Import File is selected and browse for your latest
Succession Data Model xml.
c) Choose Submit.
d) Log in to your instance and go to the Profile. Edit the Personal Information and make
sure that the Region field is connected to a picklist.
LESSON SUMMARY
You should now be able to:
● Maintain picklists using the Picklist Center
LESSON OVERVIEW
In this lesson, you will learn how to manage the User Data File (UDF) and how to edit and send
notifications to users.
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Access required permissions to import employees
● Maintain user data with the User Data File and Admin Center
This permission does not necessarily come from RBP. There is a tool called Manage Employee
Import available from the Action Search. We simply need to find the user, define the target
population, and select Save Definition For Selected Users.
If the customer wants to manage this permission from RBP, we simply need to activate the
switch Enable Control on Employee Import in Role-Based Permissions available from the
Action Search > Platform Feature Settings.
Caution:
Any changes made using the Admin Center links are overwritten by the import
process if the .csv file is not updated, with the manually imported information, for
the next import.
Data export
Exporting data allows you to download a list of existing users in your SAP SuccessFactors
system. You can use this file as the basis for updating or importing user information.
To export the UDF, on the Admin Center page, select Update User Information, then locate
and select Employee Export.
You can export a list of existing users in SAP SuccessFactors in the .csv format. This is the
most commonly selected format, as it allows you to easily modify the data using Microsoft
Excel.
Best Practice
It is recommended that the existing UDF is downloaded before making changes and importing
them. Using a stored file on a local drive increases the risk of being out of sync with the
current system data, either due to manual updates that have occurred since the last import,
or automated imports.
After selecting the format of the export file, you can specify additional export options:
● Valid users only
Select to export only active users from SAP SuccessFactors in the import file.
● Short format: only system fields
Select to show only the required fields, omitting any empty or custom fields.
Note:
Do not select Short Format if you want to include user compensation data.
Next, specify the file language format and batch or scheduled processing options:
● Character Encoding
If you are using languages with specific character types (for example, Chinese or
Japanese), you can select the appropriate encoding type from the dropdown menu so the
system recognizes the characters.
● Export as a batch process
Select this option if you have a large number of employees. It allows you to continue
working in the system as the export is being run. You will receive a notification when the file
is ready to download.
Select this option to include compensation data about the employees in the export file.
Selecting provides additional options.
Once the file is downloaded, you can open the file to make changes and additions to the data.
When you are finished, save the new data file as a .csv file. So that you have the original data
file as a backup, SAP SuccessFactors recommends that the new file is saved with a new file
name.
The UDF consists of standard data elements, which include the required fields, filter fields,
and optional fields. Fields vary depending on your configuration and modules.
These fields are displayed throughout SAP SuccessFactors and are used for filtering within
reports and permissions. Additional filter fields are created by a SAP SuccessFactors
Consultant during implementation.
The Job Code field is optional and is used to associate an individual with competencies. Job
Codes are assigned to employees and correspond to the job role that is set up within the
system. You can associate a job role with a set of competencies.
There are also 15 custom fields that can be used for other data you need to bring into SAP
SuccessFactors.
The .csv template for your instance was provided to your company during configuration.
However, you can download the template at any time using the Employee Export feature.
Rows 1 and 2, System ID and Label respectively, must be preserved, including all the required
columns in the template. You can rename Row 2 labels during system configuration. Save the
file format as a .csv file.
File behavior
When the UDF is uploaded, SAP SuccessFactors searches the records in the file and only
makes changes to data in SAP SuccessFactors where the USERID field matches a USERID in
the system. When SAP SuccessFactors encounters a USERID that currently does not exist in
the system, it is considered a new user and is added to the system as such. When the UDF
does not contain a record for an existing user in the system, no changes are made.
Adding New Users using the UDF
To add new users, add a new row to the UDF. Complete the required fields and import the file
into the system. File behavior determines that the system does not recognize the new USERID
and adds this record as a new user.
Changing User Data using the UDF
To change user information using the UDF, you must first export the current data from the
system, edit the records that require editing, and then import the updated UDF. File behavior
determines that the system recognizes the USERID of the changed user and changes the
information accordingly in the system.
Inactivating a User using the UDF
To inactivate a user you follow similar steps as when changing user data. In this case, the
STATUS of the user is changed. To inactivate a user, SAP SuccessFactors recommends that
the current data is exported from the system. Edit the STATUS field for the appropriate user
to inactive, and import the updated file into the system. File behavior determines that the
system recognizes the USERID of the inactivated user and inactivates the user in the system.
Note:
Setting the record of a user to inactive freezes the user account in its current
state, this means you cannot make changes to the account.
After making changes to the UDF, you must import it into SAP SuccessFactors for processing
by the system. This import can be performed manually through Admin Center or
automatically through FTP.
a. Send welcome e-mail to new users: The e-mail template needs to be enabled
beforehand. If it is not yet enabled, a warning is displayed.
b. Validate Manager and HR fields: To ensure that each employee record has a valid
manager and HR representative.
Note:
Employee Import cannot be used to import inactive users to the system
d. Re-activate purged users: To reactivate purged users in the system if the users are
active in the user data file.
After the file is uploaded, the SAP SuccessFactors user database is updated with the
information from the file. An e-mail notification is sent with the results of the upload, including
any errors. If the updates include manager changes, another e-mail notification with the
results of document transfer is sent and it includes the list of users whose forms have been
transferred or failed to transfer.
If any errors occurred, you need to correct them in the file and then upload it again. If that
does not resolve the problem, contact SAP Cloud Support.
Employee Import files can be scanned in instances with our without Employee Central. For
example, fields containing cross-site scripting are detected, skipped, and reported in the
import status e-mail.
In Admin Center, use the Manage Users link to make quick, one-off changes to user records.
For example, you can use this link to change data to correct information that was imported
either manually or via FTP. Such changes can include the following tasks:
● Initiating manager changes and transfer forms from an old to a new manager
● Modifying the status of a user to active or inactive
● Changing the name of a user
It is recommended that administrators perform periodic exports of all three data files and
save these outside of the application, in case there is a need to refer to historical data and/or
need to restore old records that are deleted by mistake.
It is also recommended that before any manual import of any profile data, a backup is
exported first. This way if a mistake is made (usually with the Import by overwriting existing
data option), then this can easily be recovered.
All the options and file types mentioned in this section also apply to the FTP process.
In the Import Extended User Information or Export Extended User Information page, the
system displays the settings defined for the last import or export. So it is not necessary to
reset all the settings for each import or export. This mitigates the risk of data loss caused by
incorrect settings.
Note:
When importing background information, you also have the option to overwrite
the data of users in the import file so that for only the users listed in the import file,
their background data is replaced by the corresponding data in the file. This type
of import Overwrite the data of users in the import file only affects these specified
users' background elements that are included in the import file.
User Management
On the Admin Center page, locate the Manage Employees section and navigate to Update User
Information → Manager Users to perform the following actions:
● Add New Users: Click Add New Users to enter information about a new user in the text
fields provided. Save changes.
● Change User Data: Click the name of the user to edit the information for that individual. In
the Edit User window, scroll through the data to find the fields to change, for example, the
name of the user, manager, address, status (active or inactive). Make the edits. Save the
changes.
Once the SuccessFactors system is live, admins need to perform ongoing administrative and
maintenance activities to keep it running smoothly. Among these activities, an essential one is
user information management, which involves actions like adding users, managing user
accounts, and updating user information. You need to ensure that all user fields your
company needs are included and defined with required information in the data model.
Make sure that you have included all user data fields in the data model for your system.
Setting up data model with required information is a standard part of nearly all SAP
SuccessFactors implementations.
If you want to configure changes and add user data fields in the data model, you can use the
Business Configuration UI (BCUI). This tool enables you to maintain the data model from your
end-user UI, instead of maintaining these elements in the XML file and contacting SAP Could
Support who has access to Provisioning.
Assignment ID
Assignment ID is an identifier assigned to a person to define the relationship between the
person and a company. You can use it to identify users and change it if needed.
Note:
Currently, assignment ID is NOT supported in some SAP SuccessFactors areas,
for example, Learning, Compensation, Onboarding, Recruiting Management, and
data protection and privacy features. This might cause display inconsistencies
across the suite. Before you change assignment IDs, we recommend that you
contact SAP Professional Services to evaluate the risks associated with the
inconsistencies. If changing assignment IDs isn't an option for you and you still
have the business need to change user IDs, raise a support ticket to initiate the
user ID conversion process.
The system automatically generates assignment IDs for users created prior to the Q3 2019
release, and their default values are the same as the current user IDs. However, in the
Employee Central-enabled instances, if you have used a business rule to generate assignment
IDs, the system then creates assignment IDs based on the rule and the assignment IDs might
be different from the user IDs. When you create new users using the user management tools
such as Employee Import, Manage Users, or OData APIs, assignment IDs for these users are
also added to the system.
Assignment ID can be changed ONLY through the convertAssignmentIdExternal function
import.
Table 10:
Field Description Can this ID be Relationship between
changed? these IDs
1. You can Manage Basic User Data by using the UI ‘Manage Users’ tool.
3. Another tool to use for managing users by import is ‘Import Extended User Information’
tool which can be used to import more granular data for live profile information in CSV file.
Refer to the following table to choose the correct user management tool depending on your
system configuration.
Table 11:
If you want to... Use this tool for users that are man- Use this tool for users that
aged in Employee Central are NOT managed in Em-
ployee Central
Add or update extend- Import Extended User Information, Import Extended User In-
ed user information Import Employee Data->Extended Im- formation
port, or Import Employee Data ->
Background Import
Business example
In this exercise, you will find the Admin User and verify their permission to manage the
Employee Import Privilege, for all divisions, all departments, and all locations.
1. Find the HR Coordinator and verify their permission to manage the Employee Import
Privilege.
Result
You found the admin user and updated their permission to manage the Employee Import
Privilege, for all divisions, all departments, and all locations.
Note:
Repeat this process again to ensure your changes are saved by the system. Often
the change is not saved even though the confirmation message appears that
states the changes have been saved.
Business example
In this exercise, you will find the Admin User and verify their permission to manage the
Employee Import Privilege, for all divisions, all departments, and all locations.
1. Find the HR Coordinator and verify their permission to manage the Employee Import
Privilege.
a) Use the Action Search to navigate to Manage Employee Import.
b) On the Manage Employee Import Privilege screen. Add HR as the first name and then
choose Search Users.
c) Scroll to the table, and verify that the checkbox Manage Employee Import is selected.
g) If you made any changes, save your work by selecting the Save Definition For Selected
Users button.
Result
You found the admin user and updated their permission to manage the Employee Import
Privilege, for all divisions, all departments, and all locations.
Note:
Repeat this process again to ensure your changes are saved by the system. Often
the change is not saved even though the confirmation message appears that
states the changes have been saved.
Business example
You need to make changes to an existing data file. Best practice advice is to export the
relevant file from your instance, before making data changes.
Result
You exported the existing User Data File from your instance, and saved it to your desktop.
3. Copy the data from the StarterUDF into the UserDirectory file and change the e-mail
addresses in column H to your e-mail address.
4. Save the UserDirectory file as a version 2 (_V2) and make sure you use the CSV format
(not the Excel format).
Result
You successfully modified the User Data File.
2. Verify the message and solve the issue accordingly in your csv file. Adding the Job Code of
IC to HR Coordinator and any other users that do not have a Job Code should solve the
issue.
4. In the Action Search window, enter Manage Users and verify that Alex Anderson has been
successfully created. There may be a slight delay.
Business example
You need to make changes to an existing data file. Best practice advice is to export the
relevant file from your instance, before making data changes.
Result
The Download Complete dialog box appears.
Result
You exported the existing User Data File from your instance, and saved it to your desktop.
3. Copy the data from the StarterUDF into the UserDirectory file and change the e-mail
addresses in column H to your e-mail address.
4. Save the UserDirectory file as a version 2 (_V2) and make sure you use the CSV format
(not the Excel format).
Result
You successfully modified the User Data File.
d) Choose Open.
Alternatively, you can use the keyboard shortcut, Alt+O.
e) On the Import Users screen, select Use a system generated random password.
g) Make sure that the checkbox Validate Manager and HR fields. is activated.
2. Verify the message and solve the issue accordingly in your csv file. Adding the Job Code of
IC to HR Coordinator and any other users that do not have a Job Code should solve the
issue.
b) To select the file to upload, in the Choose File to Upload dialog box, choose the relevant
filename.
c) Choose Open.
Alternatively, you can use the keyboard shortcut, Alt+O.
d) On the Import Users screen, choose the Import User File button.
4. In the Action Search window, enter Manage Users and verify that Alex Anderson has been
successfully created. There may be a slight delay.
LESSON SUMMARY
You should now be able to:
● Access required permissions to import employees
● Maintain user data with the User Data File and Admin Center
Learning Assessment
1. Well-formed XML has correct syntax; valid XML has correct syntax and follows the DTD.
Determine whether this statement is true or false.
X True
X False
X D Connects managers and external partners in the area of sales growth and
performance.
3. Your customer wants to change the People Profile text from Department to Team. In the
data model XML file, which of the following elements will need to be modified?
Choose the correct answer.
X A Field id
X B Label
X C Permission
X D Filter field
4. What type of element do we use to configure the photo in the Succession Data Model?
Choose the correct answer.
X A Standard element
X B Userinfo element
X C HRIS element
Lesson 1
Defining Metadata Framework (MDF) objects 369
Lesson 2
Configuring MDF objects 373
Exercise 33: Create a new company car object 383
Lesson 3
Creating and triggering Business Rules 389
Exercise 34: Create Message Definitions and Business Rules and then attach the 405
Business Rule
Lesson 4
Managing the Succession Data Model with the Business Configuration Tool and MDF Blocks 411
Exercise 35: Change the people profile by using Manage Configuration UI 423
UNIT OBJECTIVES
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Understand the Metadata Framework to maintain (MDF) objects
● Enable MDF and assign permissions for access
MDF Overview
The data volume information is collected periodically for every company in the production
environment and is available for viewing with proper permission. Alternatively, you can also
export the data volume information with Import and Export Data.
● MDF Audit Data Volume: Use this object to check the volumes of audit data available for a
given MDF object.
● MDF Association Data Volume: Use this object to check the volumes of association data
available for a given MDF object.
● MDF Transactional Data Volume: Use this object to check the volumes of transactional
data available for a given MDF object. Transactional data refers to the day-to-day business
data that's available in a system.
Using MDF, you can easily extend Employee Central (EC) entities for customers. It allows you
to customize objects and behavior needed to meet customer needs. Several key applications
of SAP SuccessFactors suite like Position Management, Time Off, and Manage Business
Configuration (BCUI) are built using MDF capabilities.
The tools used to manage MDF Objects are available at Admin Center.
Administrators are able to create 250 custom MDF objects by default. This limit can be raised
to 400 from Provisioning → Company Settings.
MDF components
MDF has several different layers. The most basic layer is the Object Definition. This is where
all the configuration decisions for an object is made and where the object is “built”. Object
behavior, fields, associations, and security are all set within the object definition.
Once the object definition is built, you can then add business logic to the object. This is done
using Business Rules. Business Rules can be used to default data, set values based on data
chosen, raise informational or error messages, and trigger actions to occur when data
records are saved or deleted.
Once the object is built and business logic is integrated, you can start to import, create, and
manage data related to that object.
Finally, you can create different “views” or UI’s for your object. Within the Configuration UI,
you can change the layout of the object, add or remove fields, update labels, and add text or
hyperlinks to the object view.
Note:
Do not turn on these switches in Provisioning for your THR80 training instance
as it will interfere with completion of the labs. For example, employee imports
work differently when Employee Central is active.
Grant Permissions
Access to tools to manage MDF configuration and Data is controlled by (RBP). Once MDF is
enabled you need to grant access to it by granting specific RBP permissions.
3. Choose Permission.
4.
Navigate to the Metadata Framework section and choose all permissions you would like to
grant to that role. To learn more about these permissions you can review the following
guide on the SAP Help Portal:
Note:
There are other RBP sections that allow a user to work with objects that have
been built using MDF (for example, Miscellaneous Permissions or Manage
Time Off). Some of these permissions like Manage Position might not be
available for you if related features are not enabled from Provisioning.
5.
In the Miscellaneous Permissions section, you can grant access to tools that manage data,
as well as the ability to view, edit, import, and export data for specific MDF objects. There
is also an option ‘Field Level Overrides’ to define a more restrictive permissions (no access
or read only) on specific fields for an object. To learn more about these permissions you
can review the following guide on the SAP Help Portal and related KBA (SAP Knowledge
Base Article):
● 2094229 - Field Level Overrides Permission for MDF objects - Metadata Framework
LESSON SUMMARY
You should now be able to:
● Understand the Metadata Framework to maintain (MDF) objects
● Enable MDF and assign permissions for access
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Describe options for configuring MDF objects
Use the Action Search to navigate to the Configure Object Definition tool and select Create
New: Object Definition.
Once a new object definition is opened, the different areas that can be configured are
displayed.
Object details
This section determines the overall behavior of the Generic Object (GO).
● Code: Unique identifier for Object. All custom objects created are automatically prefixed
with cust_.
● Effective Dating: This defines if object instance can have only single record or multiple
records based on different dates. Please do not confuse this with audit, which can be
enabled irrespective of configuration of this field.
Available Options:
No Selection: With this option system will behave as if you selected V1.1.
V1.0: System fields which are not of much use, will be exposed in oData API.
V1.1: System fields will not be exposed on oData API. This is recommended option if you are
creating a new object.
● Subject User Field: This defines which field contains subject user information for the
object, which is then used to determine workflow routing. Only fields which are of Data
Type User can be used for this configuration. If the External Code field is defined with Data
Type User, it will be used as default value for this configuration.
● Workflow Routing: This allows workflow routing to the object. If you select a workflow
configuration record, then the corresponding workflow will be triggered for any operation
done on an object instance. Workflow Routing requires Employee Central Foundation
Objects feature to be enabled in Provisioning.
● Pending Data: This lets you control if changes must be available with or without approval. If
you have chosen a Workflow Routing that involves an approval and you want changes to
take effect only after approval, set this field to Yes.
● To do Category: This is used when Pending Data is set to Yes. This determines what
subsection of the To Do list workflow approvers will see notifications for this Generic
Object (GO) on the Home Page.
● Object Category: There are different object categories available to determine the type of
data that an object represents: Uncategorized, Configuration, User Transactional, Non-
User Transactional and Technical.
Fields
This section allows you to manage the object fields and their attributes. By default only a few
field attributes are visible on the default UI and to see the full configuration options, choose
the Details link next to each field row.
The attributes that appear on Configure Object Definition page while you add fields to your
object definition are listed below. Based on the data type of the field, field attributes differ.
● Name: This is the identifier for the field and must be unique within current object definition
including association names. The application automatically appends “cust_” in front of the
name of any custom field.
● Maximum Length: Applicable only for String, Translatable, Number, and Decimal Data
Type. This defines how many characters can be entered for this field. The default length for
fields is 255 for String and Translatable, 38 for Number, and 21 for Decimal but it can be
changed by end user. The maximum allowed value for pre-delivered field can vary from
one object to another object and controlled by different applications.
● Data Type: This determines what kind of values can be supplied for a field. There are
several different Data Types to choose from. These include:
- String: Accepts any text.
- Translatable: Same as String but value entered can be translated into available
languages. Number:
- Number: Accepts only number without decimal values. The display of this field value will
be determined based on the logged-in user’s chosen locale.
- Decimal: Accept number along with decimal values. The display of this field value will be
determined based on the logged-in user’s chosen locale.
- Auto Number: System automatically generates a new number for each record. This
field should always be set as read-only. The end user must not be allowed to enter
values manually.
- Boolean: Provides Yes or No as the allowed values.
- Picklist: Users must choose an option from pre-defined values configured in a picklist.
- Generic Object: Create reference to another Generic Object and the end user can select
any instance of referenced GO while entering data.
- Foundation Object: Create reference to Employee Central Foundation Objects. Location
is one example of an EC Foundation Object which are managed outside of MDF.
Data Source: This field is used only for pre-delivered fields and cannot be changed by end
users.
User: References any active or inactive user in the system.
Date: Accepts date information. The display of this field value is determined based on the
logged-in user’s chosen locale.
DateTime: Accepts both date and time information (hours, minutes and seconds).
Time: Accept only time information (hours, minutes, seconds)
Attachment: Allows uploading a document or file to object instance.
● Valid Values Source: This attribute is applicable only for Data Type Picklist, Generic Object,
Foundation Object and Data Source. Enter the id/code of referenced object. To reference
a field to the Country Generic object, you would enter a value as ‘Country’. For a picklist
configuration, consider the following example: The Position object has a field called
Criticality and you want to create a connection between that field and an MDF picklist. You
will first need to determine the code of the picklist that you want to link to that field in the
Picklist Center and then specify the Picklist code in the Valid Values Source of the
Criticality field in the Position object.
● Hide Old Value: For Effective Dated Object, field values which are changed from previous
effective dated records are shown along with old value with strikethrough. If this is set to
Yes, then the old value will not be displayed.
● Decimal Precision: Applicable only for Decimal Data Type. This specifies how many digits
past the decimal point is allowed.
● Show Trailing Zeros: Applicable for Decimal Data Type. If set to Yes, it will show trailing
zeros for decimal precision if number of digits after decimal are not matching the Decimal
Precision.
● Include Inactive Users: Applicable only for User Data Type. If the value is set to Yes, then
inactive users will be included for selection. Default value is No.
● UI Field Renderer: This field can change UI behavior. For example, setting value
displayPickListWithoutExternalCode will hide Code for picklist dropdown and using
displayGOWithoutExternalCode will hide external code for GO selection. Please note these
are pre-delivered values and are applicable for specific data type. If applied incorrectly, it
will result in undesired behavior or application errors.
● Transient: Set to Yes to make the field transient. Values of transient field are not stored in
the database but are populated at runtime in the user interface. Usually, this is done with
the help of rules. For example, the age of a person is based on the Date of Birth.
● Help Text: This is a translatable option. If a value is provided it will display an icon next to
the field to show the instruction.
● Private or Sensitive Information: You can hide sensitive information on the UI to avoid
accidentally exposing the value. If you set this to Yes, asterisks (*****) will be shown in
place of actual value. The user needs to select the field and confirm their intent to show the
values on the UI.
● Default Value: You can set a default value for that field. Not all data types support this
configuration.
● Hide Seconds: Used for the DateTime and Time data types. It removes the seconds
information if set to Yes.
● Required: If set to Yes, the field is mandatory, and the user must enter a value before a
record can be saved.
● Visibility: Determines if field is Editable, Read Only, or Not Visible on the UI.
● Status: Field can be set as Active or Inactive. Inactive fields aren’t available in the system.
Please note a customer defined field cannot be set to inactive.
● Label: A translatable field which allows you to change the field label displayed on the UI and
other areas of the application.
● End Of Period: Applicable only for DateTime data type. This is to distinguish between if
00:00:00 is the start of a date or the end of a date.
● Log Read Access: Enable if a field needs to be tracked for Read Access. This feature is not
yet available.
● Database Field Name: Read-only field and determined by system.
● Rules: This section allows to add one or more Business Rules to the field. When a field
value is changed these rules are triggered.
● Field Criteria: Allows you to restrict the possible values for the field by specifying the
related fields under this section.
● Condition/ Condition Values: Allows you to show or hide the field based on a value entered
on an other field available on the object.
Watch the 'Connecting an MDF Object with a Picklist' video for an in-depth explanation.
Watch the 'Change a Label for a field in an MDF Object' video for an in-depth explanation.
Associations
Associations define a relationship between two objects. The type of association determines
what kind of relationship two objects have and what is their behavior. MDF supports
associations between Generic Objects or between a Generic Object and a Employee Central
Foundation object.
For any type of association, the relationship can be “One to Many” or “One to One”. For
example, a Division may have a “One to Many” relationship to a Business Unit. A Location can
only have one Geozone associated with it; this is a One to One association.
MDF supports the following association types:
1. Valid When (VW): For this association type, associated objects have their own lifecycle
and exist without the object that is currently being configured. Valid when associations are
often used to create filtering capabilities between fields on a given object. For example, in
the Employee’s Job Information you have Business Unit and Division fields. When you
select the Division field, you want to see valid division values which are applicable for
selected Business Unit. But Divisions and Business Units can be maintained independently
from the employee’s record. In this case, you would define a Valid When association on
Division referencing ‘Business Unit’.
2. Composite: This association type creates a parent-child relationship. The entity being
associated is a child entity and it cannot exist outside the parent object. The child object
must have effective dating ‘From Parent’ for this association type. Also the child object
can be association with only one parent object.
For example, the picklist values are child entity of the picklist entity. It would not make
sense to create Picklist Value entity that does not exist with a picklist entity (the parent).
3. Join by Column (JBC): This association type allows you to associate two objects with a
One to One Relationship which one object always has reference to the other object. Set
one field of the parent object definition as the source object column and one field of the
child object definition as the destination object column, then join-by-column association
will make the value of these two object columns reference each other.
For example, a Person could be one object which represents a real person and Personal
Information could be another object which stores information about the person. The
Person and Personal Information objects could be One to One composite relationship. In
that case the Personal Information cannot exist without a Person.
However, if the association was a one to one JBC association, a user would be able to
maintain personal information outside the person object. In this configuration, you would
configure the External Code of Person to reference the External Code of Person
Information object.
Note:
You are not allowed to define Join By Column associations for custom MDF
objects.
Search
You can define fields that can be used to do search for an MDF object instance. Each of the
fields added to this section will be included in searching on different places in application. In
the field, enter the names of the fields and/or association that you want to make searchable.
You can also use the field reference to include in search. For example if you have Object with a
Country field which refers to country object you can add cust_country.code to search based
on the country code.
When a field is associated with a picklist, you can add the field name + “.label” like in the
screenshot.
Security
Setting up security allows you to control which users can view, edit, or import/export data for
an object or field. With MDF you can set up security at the object or field level. For objects and
fields, you can control access based on RBP roles within the system.
Optionally, you can define which fields in the object definition are used to determine the target
population in Role-Based Permissions. You can specify any user field in the current object
definition as the RBP Subject User Field. The value of the specified RBP Subject User Field can
then be used to create user-based permission groups in RBP. You can use any field in the
current object definition of the type ‘user’ as the RBP Subject User Field. It does not have to
be the externalCode.
● Secured: This determines whether the object uses RBP to set security. If you choose Yes,
then within RBP Permission Roles, you can set object and/or field permissions. If you
choose No, the object is not available within RBP Permissions Roles.
Note:
Don't select Custom. The option isn't supported and will be removed in future
releases.
This Secured field is set to Yes by default for creating custom objects. This is
recommended to keep all custom objects as Secured=Yes so that RBP
permissions must be granted before the object can be accessed. You can grant
access to non-secured objects (Secured=No) using the Metadata Framework
permission for "Access to Non - RBP Secured Objects".
● Permission Category: This specifies what area of the Permissions section in the RBP
Permission Role the object can be found.
● RBP Subject User Field: Specify a required user field of the current object definition. The
value of this field is used to set up target population in RBP.
Once the MDF object definition is created, you can create object instances of that definition in
your application. Creating an instance of an MDF object is the way to populate the object with
data. From the Action Search go to Manage Data. The search results in Manage Data display
records that are created and those that are pending for approval in a configured workflow.
Watch the 'Import and Export Data for an MDF Object' video for an in-depth explanation.
Note:
Change History | SAP Help Portal
Business example
You need to create a Generic Object to capture the details around company cars. It must
include the following fields:
● Employee Name
● Effective as of
● Model
● Year
● Purchase Date
1. Use the Action Search to navigate to the Configure Object Definitions tool.
3. To create your Company Car Object, use the information provided in the tables below.
Table 13:
Field Details
Field Name Data Type Required Label
externalCode User Yes Employee Name
Field Details
Field Name Data Type Required Label
externalName Hide this field by se-
lecting Details and
for the Visibility, se-
lecting "Not Visible".
effectiveStartDate Date Yes Effective as of
Create the three custom fields below. Please note that the prefix “cust_” will automati-
cally be added to all custom field names and cannot be deleted.
model String Yes Model
year Number No Year
purchase_date Date Yes Date Purchased/
Leased
Business example
You need to create a Generic Object to capture the details around company cars. It must
include the following fields:
● Employee Name
● Effective as of
● Model
● Year
● Purchase Date
1. Use the Action Search to navigate to the Configure Object Definitions tool.
3. To create your Company Car Object, use the information provided in the tables below.
Table 13:
Field Details
Field Name Data Type Required Label
externalCode User Yes Employee Name
Field Details
Field Name Data Type Required Label
externalName Hide this field by se-
lecting Details and
for the Visibility, se-
lecting "Not Visible".
effectiveStartDate Date Yes Effective as of
Create the three custom fields below. Please note that the prefix “cust_” will automati-
cally be added to all custom field names and cannot be deleted.
model String Yes Model
year Number No Year
purchase_date Date Yes Date Purchased/
Leased
b) In the confirmation popup window indicating that the externalName is set to Not
Visible, select Yes.
d) Find the Company Car Object and select the permissions: View Current, View History,
Create, Insert, Correct, Delete, Import/Export.
f) Log out and go back to the instance in order to make sure that permissions are
reflected.
d) Select the first day of the current month for the Effective as of field.
g) For the date Purchase/Leased field, indicate the first day of the current year.
h) Select Save.
LESSON SUMMARY
You should now be able to:
● Describe options for configuring MDF objects
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Create Business Rules using the Rules Engine
● Identify use cases for configuring Business Rules using the Rules Engine
● Define when rules are triggered
You can configure the business rule logic for various modules and features using the Rules
Engine.
Business rules can cover legal regulations ('The FLSA status is required for employees
working in the USA'), company policies ('All employees moving to the London office get a
compensation for the high cost of living'), or other requirements. Because of specific
customer requirements, rules are highly customizable and based on the previous
configuration decisions customers have made.
The Rules Engine provides an easy-to-use tool to dynamically configure and manage the
customer, country, or scenario specific business logic that needs to occur within GO.
Business Rules are defined in the Rules Engine and the system executes these rules during
runtime. Technically, the Rules Engine is based on the Metadata Framework (MDF), but uses
its own administrative tool, Configure Business Rules.
Rules can be used to add validation to details entered by a user or autofill some field data (for
example, time zone information can be auto filled based on location information).
There are two ways to define rules:
Rule events
Business Rules could be attached to different events. These events include the following:
● Initialize Rules: Initialization rules are triggered before all other rules; such rules are useful
to autofill default values for different fields. They only run when a new record is created
(initialized).
● Validate Rules: Validate rules are triggered after a change to an object is submitted but
before the change is saved. You can use these rules to validate field values entered by
user. These are executed before Save Rules. When you import MDF data using the Import
and Export Data UI, the validate operation triggers the validate rules associated with the
MDF objects and returns errors found in the data. Administrators can then catch any data
issues through validation and correct them before importing it. In fact, the validate rules
are executed during both validate and import operations.
● Save Rules: Save rules are triggered when a user saves changes. You can use these rules
to populate or change field values before saving and they are based on user inputs values.
For example, you want to auto populate region field based on country values selection.
● Post Save Rules: Post Save rules are triggered after changes to an object have been saved.
These rules are used when you want to send an alert message to the user. They are not
used to set a field value.
● Change Rules (onChange): They are used at the field level. Objects cannot be associated
with change rules. Change rules are triggered when a value for a particular field is changed.
You can use these rules to populate another field after the change. For example, you can
populate the Country field with a certain value based on a change to the Position field.
● Delete Rules: Deletion rules are triggered after an object record is deleted.
● On Load Rules: On Load rules are UI specific rules that get executed once the UI is loaded.
An example could be calculating total salary based on different fields available on given
object.
● UI Rules: These rules are applicable only for a UI built in the tool Configurable UI. These are
UI specific rules to make certain field required, visible or hide based on certain condition.
Such rules will not be applied when a user does the import.
Note:
Warning messages from the validate and save rules are shown before workflow
confirmation messages from workflow rule execution.
Identify Use Cases for Configuring Business Rules Using the Rules Engine
1. Workflow: You can define rules that automatically determine the right workflow when the
manager or employee changes employee data. To achieve this, you create a workflow
foundation object and assign it to the rule in the Rules Engine UI. For example, you can
trigger an alternate workflow if the salary increase is over 10%.
2. Propagation: You can define propagation rules to have the system automatically copy
over the data from one field to another field. This way you can have the same data in
several places of the system, while keeping just one data record. For example, you can
propagate the job code to the Position MDF object.
3. Calculations: You can define rules that automatically perform calculations using the
various functions the Rules Engine supports. For example, you can get an employee's
current age by calculating the difference between the current date and the employee's
birth date.
4. Validation: You can use validation rules to let the system check the user's input before
saving. You can set a field to mandatory, or you can trigger error messages. For example,
IF... the country is USA, THEN... the FLSA status is required.
5. Eligibility: You can define which employees should be included in a bonus plan or
compensation planning form. To achieve this, you have to integrate the modules Variable
Pay or Compensation with Employee Central. For example, the rule could be:
IF... the employee type does not equal Contract, Temporary or Union
AND the employee is regular
AND the rate type is 'Hourly' and 'Salaried'
AND the hire date is after 10/01/2010
AND the rehire date is after 10/01/2010
AND the employee status is Active or STD
THEN... this employee should be eligible (for a specific compensation form)
6. Defaulting Values: You can define default values for specific fields. For example, if the
Admin adds a new employee for the company COMP_USA, the employee is automatically
eligible for stock, and the initial stock grant is set to 200.
Note:
We recommend that any objects used for a rule should not be RBP-secured
otherwise, depending on the permissions they've been assigned, certain users
might not be able to run the rule.
1. Use the action search to navigate to the Manage Permission Roles tool.
2. On the Permission Role List page, under Permission Role, choose Permission Role for
which you want to manage the permissions. The Permission Role Detail page opens.
3. In the Permission settings section, choose the Permission button to specify the
permission you want to assign to the role. The Permission Settings window opens.
● Configure Object Definitions: You need this permission to be able to create rule types
and lookup tables.
● Access to Business Rule Execution Log: You need this permission to be able to access
the log that shows how business rules are executed.
● Configure Business Rules: This is the only permission used directly for the Rule Engine.
You need this authorization to be able to access the Rules Engine UI.
● Manage Data:
You need this permission to be able to create MessageDefinitions for raising messages.
Manage Sequence: You need this permission to be able to create Sequence objects for
defining sequences.
Both MessageDefinitions and Sequence objects are MDF objects.
Procedure:
2. In Picklist Center use the search bar to find the Rule Type (RuleType) picklist and select
the effective start date (Jan 1, 1900).
5. In the Values section, enter an external code for the rule type you want to create.
When you create rules for the following modules or features, it is important that you stick
to the spelling and capitalization of the external code of the rule type, as they have a
specific function:
For this module or feature… …enter exactly this external Here's why:
code:
Compensation, integrated with compensationEligibility From the compen-
Employee Central sation screens for
eligibility rules, the
user can select only
the rules assigned
to this rule type.
Variable Pay, integrated with Em- varpayEligibility From the variable
ployee Central pay screens for eli-
gibility rules, the
user can select only
the rules assigned
to this rule type.
Mass Changes (in Employee Cen- massChange You can create
tral) rules on the Mass
Changes page.
6. Enter a label.
Business Rules are created and managed using the Business Rules Admin tool in Admin
Center. You can use this tool to create new rules, view/edit or deleting existing rules in the
system.
Note:
The Business Rules Admin User Interface (UI) has been enhanced to make it
possible to delete a single rule as well as several rules completely using the
checkbox to the left of the rule. One or more rules can be selected to be deleted. If
the user selects a rule to be deleted, it will be checked if the rule is still assigned in
the system. Assigned rules cannot be deleted and will prompt an error message to
forbid deletion and must be unassigned in order to delete them. Unassigned rules
and rules based on Basic rule scenario can be deleted. For rules based on Basic
rule scenario, the system cannot protect the user from deleting a rule which is
assigned so deleting a rule based on Basic rule scenario should be treated with
caution.
Rule scenario
A rule scenario is a rule object you can use to help you create rules correctly, based on the
rule context and parameters for a given scenario. When you select a rule scenario, the screen
changes and offers the basic elements of the chosen scenario.
There are application-specific scenarios and the legacy basic scenario.
Note:
When you select the Basic rule scenario to create a business rule, you now receive
the warning that the Basic rule scenario will be deprecated and that you should
choose an application-specific scenario instead. You should only continue with the
Basic scenario in cases where none of the application-specific scenarios meet
your needs.For more information about the deprecation of the Basic rule scenario,
refer to the Deprecation of Basic Rule Creation topic. Rules based on application-
specific rule scenarios have reduced risk of misconfiguration and the process of
rule creation is simpler.
Most legacy business rules have been created with the default Basic scenario. Since the basic
scenario doesn’t provide any guidance about the various objects, parameters, and actions
you can use to configure the rule, the resulting rules can often produce errors. As such,
SuccessFactors recommend that you use application-specific rule scenarios instead.
The scenarios available in your system are displayed when you create a new rule under Admin
Center → Configure Business Rules, where they’re categorized by application. Here you can
see only the scenarios for the applications that you've enabled in the system.
When you choose your rule scenario, you must fill in some rule details before you can
continue to the If/Then logic.
● Rule Name: This is the label of the rule that will display in search tools.
● Rule ID: The rule id is the unique identifier for the rule. The rule name is automatically
copied into the rule id, however it is best practice to not have any spaces in your rule id.
● Start Date: This is the effective start date for your rule. Rules can only be triggered after
this date. The default value is 01/01/1900.
● Rule Type: For the Basic Scenario, rule types can be used to organize your business rules.
Any values added to the RuleType picklist will display here. Rule Types are optional.
● Description: This is an optional field that you can use to provide more context around the
business use for the rule.
● Base Object: Select an object that the rule is based on. The base object defines which fields
and related objects you can select when creating the rule.
Base objects
Base objects are the starting point for your rule. They correspond to the data objects available
in the system, which are either EC objects (foundation objects, employment objects, or
person objects) or MDF objects (GO). The base object defines the subject of your rule. You
can use the fields, attributes, and related data objects of the base object as input.
For example, if you want to create a rule that is triggered when the employee status is
changed, you choose Job Information as base object, as the employee status field is part of
the Job Information EC object.
For application-specific scenarios, the scenario defines the base object, or limits which base
objects you can choose when you're creating a rule.
For the legacy basic rule scenarios, there's no guidance in the system as to which is the right
base object for your use case. Please make sure to refer to the application-specific
documentation for more information on which base object to choose. For basic rule
scenarios, you have to assign the rule to the base object used in the rule.
Note:
To find out which fields are part of which EC object (which corresponds to an HRIS
element), refer to the data object tables of the Employee Central Implementation
Handbook. To find out which fields are parts of which MDF object, you can look up
the object in the MDF UI.
If Then Logic
IF statements are the part of the rule that describe which condition has to be met before the
system actions defined in the THEN statement are executed.
THEN statements define how the system reacts to the conditions contained in the IF
statement of the rule. For example, an error message is raised, a field is set to a specific value,
or new data is created. ELSE statements define how the system reacts if the IF condition is
not true. The THEN statement is then skipped and the system executes what is defined in the
ELSE statement.
Define rule statements following the logic "A is equal to B", with A being the left expression,
and B being the right expression, connected by the comparison operator "is equal to". Left
and right expressions are available in the IF section and the THEN section for the Set action. In
general, the dropdown list for the right expression contains the same values as the left
expression but limited to the entities that have the same field type as the left expression. In
addition, there are some options in the dropdown list specific to the right expression.
In the dropdown list of the left expression, you can select:
In the dropdown menu of the right expression, you can select the following:
● Field type
● Fields assigned to the base object or the other added objects that have the same field type
as the left expression
● Functions that are available for the field type of the selected left expression
● Variables
● Current User
● Effective Date
● Null
Comparison operators
Comparison operators are used to define the relationship between values in the left and the
right expression of a business rule.
The following comparison operators are supported:
Is before Date
Is on or before Date
Is after Date
Is on or after Date
Collection filters
Collection filters are used to get a unique value from a list of values. This is relevant when
there is a parent-child relationship between data objects.
In the following business example, Job Relationship is the child of Job Information, which is
the parent object. This means you can have multiple Job Relationships for a single
employment. You use a collection filter to define which Job Relationship should be used in the
rule, for example the HR Manager.
In the Rules Engine, collection filters ask you to select a unique value (Select….where…).
Function
A function performs a specific task on the data object or field of a rule. Functions help you to
define more complex rules that perform calculations or application-specific tasks. In the
system, you can identify functions by the brackets that follow the function name; for example,
Add().
Rule events
When a user is assigning a rule, there is a new guided rule registration process to see all
possible rule assignment options and go to the target page to assign the rule. This supports
users in assigning rules to the right place in the system. This is only available for rules based
on a rule scenario.
When assigning a business rule to an object or xml element, you need to define if the rule
should be triggered before, during, or after a change is made. There are different types of rule
events that define when a rule on an EC Object is triggered:
● onInit: This event triggers a rule as soon as a new entity is created. For Employee Central,
OnInit rules work only in Hire/Rehire scenarios and for legacy foundation objects. Since
these rules are for new hires, they do not work for existing users.
● onSave: This rule event is triggered when a user tries to save changes to an object. You can
use these rules to check related field values for correctness. For example, a field could
become required as a consequence of a save. You can also use this to create or updated
data.
● onChange: This rule event triggers a rule as soon as the user makes a change to a field.
The rule triggers while the record is being filled out, not when the Save button is triggered.
●
Note:
Attaching business rules to fields is the equivalent of an onChange rule event.
Rules can also be triggered on the Field level by configuring it within the details section of the
triggering field. Keep in mind only the onChange rule event can be used on the field level.
For example, if you want to autofill an employee’s current location and division within a MDF
Object, you would add the rule to the “trigger” field, which in this case would be the Employee
field. The location and division fields would be filled as soon as the employee field was
completed or edited.
Note:
You need the Access to Business Rule Execution Log permission before you can
use the log. This permission belongs to the Metadata Framework group.
There are two separate permissions: one to create the rule trace, and another to
both create the rule trace and view the resulting log. Since the log can contain
potentially sensitive data on your users, we recommend that you only assign the
view permission to the necessary people.
Once you have the permission, you need to define any rule traces you want to use.
1. Use the Action Search to navigate to the Business Rule Execution Log.
Note:
You can set up a rule trace for a maximum time period of two days. This is
to ensure that only new and up-to-date traces are active in the system at
any particular time.
Note:
"User" here refers to the user who is executing the rule, not the user whose
data is evaluated or changed by the rule.
If you want to trace all rules for the specified user, just leave this field empty.
When you save the rule trace definition, the trace will start on the specified start date. If you
have the necessary authorization, you can return to the Business Rule Execution Log and
choose Download to see the content of the log. You can also edit existing rule traces using the
Take Action option.
Note:
● The log file for a rule trace has a maximum threshold of 1MB. If the log file
exceeds this threshold, entries within the log file will be deleted. As such, if you
want to trace several large or complex rules we recommend that you use a
separate rule trace for each one.
● You can delete the log file whenever you don't need it anymore. However, the
rule trace definition will remain.
Note:
A list of rules including their rule assignments can be exported as a CSV file to get
an overview of where the rules are used.
Business example
You need to ensure car objects you create follow certain rules like having manufacturing
dates in the past and not in the future.
1. Use the Action Search to navigate to the Configure Business Rules tool.
a. Table 14:
Field Value
Rule Name Company Car ERROR
Rule ID companyCarError
Base Object Company Car
1. Use the Action Search to navigate to the Configure Object Definitions tool.
Business example
You need to ensure car objects you create follow certain rules like having manufacturing
dates in the past and not in the future.
1. Use the Action Search to navigate to the Configure Business Rules tool.
a. Table 14:
Field Value
Rule Name Company Car ERROR
Rule ID companyCarError
Base Object Company Car
d) Select Continue.
d) Choose is after.
f) Choose Today(), you may need to scroll down in the list to see it.
k) Choose the entry for the message created in the last exercise.
m) Choose Error.
1. Use the Action Search to navigate to the Configure Object Definitions tool.
d) Select Save.
e) Select OK.
LESSON SUMMARY
You should now be able to:
● Create Business Rules using the Rules Engine
● Identify use cases for configuring Business Rules using the Rules Engine
● Define when rules are triggered
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Modify the profile with Business Configuration UI (BCUI)
● Add permissions for BCUI
● Update the Succession Data Model with BCUI
● Customize People Profile with MDF blocks
Limitations
Before setting up the Business Configuration UI, the following limitations should be
considered:
Before the customer can use the Business Configuration UI (BCUI), you have to upload the
data models the customer wants to use. It is recommended that you also download already
existing succession data models for backup purposes.
The XML must be loaded after you have activated the switch in Provisioning → Company
Setting: Enable Business Configuration in Admin Tools.
The customer can only assign picklists from BCUI after these picklists have been created
from the Picklist Center. The customer cannot directly create picklists from BCUI.
If the upload fails, the reason is displayed. Resolve the issue and upload the data model again.
Note:
Do not upload another data model until the upload and synchronization of the
current data model is completed. Doing so may cause differences between BCUI
and the Succession Data Model.
Note:
BCUI sync job does not have e-mail support for additional recipients or job
monitoring.
Choose Create Job. You are taken to Manage Schedule Jobs page.
2) Run the Job.
From Provisioning, go to Manage Scheduled Jobs.
From the list of jobs, search for the job you created.
In the Actions column for this job, select Submit to run the job based on scheduled time or
select Run It now to run the job immediately.
A job is triggered.
What to do when the Succession Data Model and Metadata Framework are not in sync?
While using BCUI, some inconsistencies may be found where the Succession Data Model is
not in sync with MDF.
In order to resolve inconsistencies, you can try the following:
● If fields added from BCUI are not present in Admin Center > Manage Permission roles, you
can export and reimport the Succession Data Model again.
● If BCUI is locked, it might be due to the Succession Data Model and MDF are not in sync.
Upload the SDM again and check if BCUI is unlocked. If not, manually trigger the MDF
Object Definition to DB Sync job from Provisioning.
● When you manually add the fields in the Data Model XML but they do not appear in BCUI,
you are advised to refresh the metadata using the tool in Admin Center > OData API
Metadata Refresh and Export.
● Manage Configuration UI
● Configure Object Definitions
Caution: When you disable a standard element, the element is deactivated and removed from
the Succession Data Model. As a result, this element is no longer part of any XML download or
export. We suggest you test this change before disabling any HRIS elements in a production
system.
Checking Permissions
When you enable a standard element, verify that the correct permissions have been applied to
the activated element (field), otherwise it will remain invisible. Permissions used for Employee
Profile in Platform are located in Employee Data permissions section in RBP.
Adding a Picklist to Standard Element
CSV picklists can be added to standard elements using BCUI. Once you select any standard
element, one of the available options is Picklist. Simply open the dropdown list and choose
your picklist and save your changes.
In order to make field visible on your People profile, or change the order of the fields, use
Configure People Profile tool as explained in previous module.
3. Choose the required object in Select Base Object drop down and enter the ID of your
choice for the UI you are creating. Once a Base Object is selected, a default view is created
with all fields and first level composite children as group.
When you hover over a group, you can see the toolbar options as highlighted on the
screenshot:
• Add Field - Select this toolbar item to add a field to the group.
• Add Link - Select this toolbar item to add a link at access a URL to the group.
• Add Group - Select this toolbar item to add a group to the group.
• Edit Properties - Select this toolbar item to open the Properties for the group.
• Delete - Select this toolbar item to delete the group.
4. Once the configuration is complete choose the Save button to save the Config UI for the
MDF object.
2. In the Search area for Available Blocks, look for “Live Profile MDF Information” block. It will
appear if you search “MDF”.
3. Drag and drop the block into the desired available space.
Once the above steps are completed, the block will appear on the Profile Page if the
person viewing the profile has the appropriate permissions.
In this exercise you will learn how to change the People Profile by using Manage Business
Configuration to add an MDF object.
Result
You have changed the People Profile by using Manage Business Configuration.
In this exercise you will learn how to change the People Profile by using Manage Business
Configuration to add an MDF object.
b) Click on “Create New”, enter an “Id” of your choice (e.g. Company Car) and select in
“Select Base Object” the object “Company Car”, that you created in a previous
exercise.
c) Click on “Save”.
e) Under “Available Blocks” on the right side, search for the area “Custom Blocks” and
choose “Live Profile MDF Information”.
f) Drag and drop the block in the section “Profile” in the subsection “Personal
Information” into the placeholder “Place block here” and click on “Save” at the right
side.
g) To test your settings choose from the main menu “My Employee File” and find the
MDF object “Company Car” in the section “Profile” in the subsection “Personal
Information”.
Result
You have changed the People Profile by using Manage Business Configuration.
LESSON SUMMARY
You should now be able to:
● Modify the profile with Business Configuration UI (BCUI)
● Add permissions for BCUI
● Update the Succession Data Model with BCUI
● Customize People Profile with MDF blocks
Learning Assessment
X A Business Object
X B Generic Object
X C Business Rule
X D Generic Rule
X A XML
X B DTD
X C Manage Data
X A Provisioning
X B The Instance
Lesson 1
Introducing THR98 Topics 431
UNIT OBJECTIVES
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Describe Succession Data Model Advanced Features
● Explain reports in the self-service reporting solutions
● Describe the Job Description Manager and Job Profile Builder
● Introduce Talent Intelligence Hub in SAP SuccessFactors
● Understand Opportunity Marketplace in SAP SuccessFactors
● Define Dynamic Teams in SAP SuccessFactors
● Explain Configuration Transport Center in SAP SuccessFactors
● Setting up Instance Sync and Instance Refresh in SAP SuccessFactors
● Illustrate Intelligent Services and OData APIs in SAP SuccessFactors
● Appreciate Document Management in SAP SuccessFactors
● Define Data Protection and Privacy in SAP SuccessFactors
● Outline Accessibility in SAP SuccessFactors
The reporting solutions in People Analytics offer both simple lists, and more advanced cross-
tabs/pivots, which can be combined with charting and formatting into multi-page reports for
distribution within the company. The report output formats include Adobe PDF, Microsoft
Word, Microsoft PowerPoint, and Microsoft Excel. You can manage the access to build and
run reports by granting the permissions only to authorized users.
Report templates are available for all core areas of the SAP SuccessFactors suite, including
Performance, Goals, Succession, Recruiting, and Employee Central. Templates are being
continually scoped and added.
The reporting capabilities in SAP SuccessFactors also allows users to build interactive
dashboards and tiles, which enable managers to view a summary of information for their
teams.
Note:
Several SAP SuccessFactors solutions have their own reporting tools accessible
outside of People Analytics. To know more about module-specific reporting tools,
refer to the product specific guides in the SAP Help Portal.
Report Center
Report Center consolidates report builder tools into a modern interface where you can build
and run reports.
Report Center centralizes all the reporting components from different reporting options in
SAP SuccessFactors. The report types are Tiles, Dashboards, Table, Canvas, and Story
reports. Report Center allows you to edit and run reports from a central location.
You can learn more about People Analytics and Report Center in the THR98 course.
Opportunity Marketplace
Opportunity Marketplace takes advantage of sophisticated technologies, such as artificial
intelligence and machine learning algorithms, in recommending opportunities tailored for
employees’ growth and development.
These opportunities originate from SAP SuccessFactors Career Development Planning,
Learning, and Recruiting and are offered in the form of action cards. Users can take action
directly on the cards to respond to the recommended opportunities.
Learn more about Opportunity Marketplace in THR98: SAP SuccessFactors Platform
Advanced Academy.
Dynamic Teams
The Dynamic Teams module enables people in your organization to create and manage
dynamic teams and then define objectives and key results for the team.
A dynamic team is an informal team that demonstrates agility and adaptability in how it
forms, works, and disbands. A dynamic team isn't defined by the formal organizational
hierarchy and reporting structure. Instead, it's formed by people coming together for a
specific purpose. For example, it can be a cross-functional team, made up of people in
different job roles, from different parts of the organization. Or it can be a project team, formed
to complete a specific project and then disbanded.
Key capabilities of Dynamic Teams include:
● Objectives and Key Results (OKR)
Learn more about Dynamic Teams in THR98: SAP SuccessFactors Platform Advanced
Academy.
Learn more about Configuration Transport Center in THR98: SAP SuccessFactors Platform
Advanced Academy.
Note:
The Instance Synchronization Tool will be deleted in 2H 2024. We encourage you
to start using Configuration Transport Center for your business scenario. Using
Configuration Transport Center, you can view, download, and transport
configurations from one tenant to another.
The Instance Refresh tool helps you to create a replication request of SAP SuccessFactors
HXM Suite (also known as BizX comprised of Employee Central, Compensation, Performance
& Goals, Succession & Development, and Recruiting) and monitor the status of the request
from the source to target instance.
The Instance Refresh tool helps you to create a replication request of SAP SuccessFactors
HXM Suite (also known as BizX comprised of Employee Central, Compensation, Performance
& Goals, Succession & Development, and Recruiting) and monitor the status of the request
from the source to target instance.
Note:
Replication does not include everything in the instance. We do remove some
attachments, audit logs, and so on.
The Instance Refresh tool cannot be used for cloning.
Learn more about Instance Sync and Instance Refresh in THR98: SAP SuccessFactors
Platform Advanced Academy.
Document Management
SAP SuccessFactors document management tools enable administrators to manage
document attachments centrally for the HXM Suite.
People can upload documents attachments on several screens in the SAP SuccessFactors
HXM Suite, such as the candidate profile or employee profile. Administrators can use
document management tools to view and manage these documents centrally.
As an administrator, you can use the Manage Documents page in Admin Center to perform a
variety of tasks, including:
LESSON SUMMARY
You should now be able to:
● Describe Succession Data Model Advanced Features
● Explain reports in the self-service reporting solutions
● Describe the Job Description Manager and Job Profile Builder
● Introduce Talent Intelligence Hub in SAP SuccessFactors
● Understand Opportunity Marketplace in SAP SuccessFactors
● Define Dynamic Teams in SAP SuccessFactors
● Explain Configuration Transport Center in SAP SuccessFactors
● Setting up Instance Sync and Instance Refresh in SAP SuccessFactors
● Illustrate Intelligent Services and OData APIs in SAP SuccessFactors
● Appreciate Document Management in SAP SuccessFactors
● Define Data Protection and Privacy in SAP SuccessFactors
● Outline Accessibility in SAP SuccessFactors
Learning Assessment
1. Which of the following is NOT discussed in the THR98: SAP SuccessFactors Platform
Advanced Academy?
Choose the correct answers.
X B Opportunity Marketplace
X C Time Management
X D Dynamic Teams
Lesson 1
Accessing important resources 443
Lesson 2
Understanding release updates and the What's New Viewer 453
UNIT OBJECTIVES
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Access available resources to support SAP SuccessFactors solutions
● Connect to SAP solutions using SAP Cloud Identity Authentication Service (IAS)
● Access the SAP Help Portal
● Finding the SAP Help Portal
The SAP Help Portal and the Support Portal are two areas customers can go to get questions
answered. You will also find the information on these pages helpful during configuration.
● Guides
● Discussion Board
Used with customers to identify their needs. You are responsible for:
● Explaining the options available in the configuration workbook
● Providing feedback and suggestions
● Configuring the instance to match customer requests documented in the configuration
workbook after sign-off
The data protection and privacy features include, for instance, the ability to report on
personal data changes and the capacity to report on all the data subject’s personal data
available in the application. Customers will also have options to configure data retention rules
at country level for active and inactive employees that will permanently purge personal data
from SAP SuccessFactors applications.
It is the customer’s responsibility to adopt the features that they deem appropriate. More
information can be found on the SAP Help Portal.
Additional resources
There are a number of additional resources that provide more information about SAP
SuccessFactors:
● SAP SuccessFactors, An SAP Company
● Road map explorer
● Online system help
● Task-specific lab guides
● SAP SuccessFactors Customer Community
You may also post ideas for enhancements on product-specific Q&A boards, and "Kudo"
other ideas that you like. Enhancement ideas with the most kudos often become part of the
product roadmap for future releases.
Note:
Access the SAP SuccessFactors Community.
IDPs are created by the SAP Product Management Advisory & Partner Success team and
written in collaboration with learning partners and SAP Professional Services based on
experience gathered from implementation projects. They have been reviewed by SAP Product
Managers and Architects.
All IDPs are currently housed within the Customer Community: https://
community.successfactors.com/t5/Implementation-Design-Principles/ct-p/
ImplementationDesignPrinciples
Empowerment Center
The Empowerment Center in the SAP SuccessFactors Community page, provides a great set
of resources and tools to help navigate your Customer Journey. Whether you are new to
SuccessFactors or have already implemented the whole suite, it is your guide to tools and
resources.
Feel free to look ahead or behind to enable yourself with any/all of the resources and come
back often as new tools and resources are regularly made available!
Note:
The Implementation Guides for each module can be found on the SAP Help
Portal and should be the number one tool on how to implement the different
modules. Access the SAP SuccessFactors Help Portal.
SAP Notes
SAP Notes describe a software issue and its solution. They include a description of the
symptoms, the cause of the error, and the SAP release and support package level in which the
error occurs. Depending on the type of error, an SAP Note may also include workarounds and
links to support packages that solve the problem. Most SAP Notes contain coding
corrections.
Here are some of the key points to keep in mind:
● 80% of SAP Notes contain coding corrections.
● It solves complex technical issues.
● Most SAP Notes contain the description of the issue from a business perspective as well as
the technical solution.
● There is an implementation tool for the coding corrections is available to help customer to
implement SAP Notes.
● It is translated into English, German, and Japanese.
The SAP Support Knowledge Base Search, found in the SAP ONE Support Launchpad, allows
you to search a variety of repositories; including SAP Notes, SAP Knowledge Base Articles
(KBAs), SAP Community content, and more. You can access the KBAs.
When you log into the Cloud Availability Center you will see the status of your Production
environment. Test, QA, and Preview environments are not accessible yet. Other SAP cloud
products such as SAP Business ByDesign, SAP Hybris Cloud for Customer, SAP Integrated
Business Planning, SAP S/4HANA Cloud, and SAP Cloud Platform Integration are not yet
visible in the Cloud Availability Center.
Note:
The Cloud Availability Center tile replaced the Cloud Status Dashboard and
Maintenance Schedule tiles. However, the Cloud Status Dashboard and the
Maintenance Dashboard are still available but will be retired in Q4.
You can find more information about cloud product availability and maintenance at the Cloud
Availability Center.
5. Choose the Home icon in the upper left of the Launchpad. You will now see the tile on your
Launchpad home page.
IAS can be set up to require different login methods, such as password, two-factor
authentication, or Social Sign On, based on risk-based rules.
Administrators are able to migrate from a legacy authentication service to IAS using a feature
in the Upgrade Center. For the moment, customers are not obliged to have IAS but it will
become mandatory following a phased migration plan.
More information about IAS is available in the SAP Help Portal.
Watch the Navigation in the Help Portal video for an in-depth explanation.
Configuration Requirements
Digital Assistant is only available for a few Early Adopter customers. These customers must
have enabled the latest home page
LESSON SUMMARY
You should now be able to:
● Access available resources to support SAP SuccessFactors solutions
● Connect to SAP solutions using SAP Cloud Identity Authentication Service (IAS)
● Access the SAP Help Portal
● Finding the SAP Help Portal
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Stay current with the SAP SuccessFactors solutions
● Maintain knowledge with the release updates via the What's New Viewer
After the restricted-use phase, the unrestricted-use phase begins on the general availability
date communicated to customers beforehand. The general availability date marks the point in
time when the cloud solution is available for productive use for the first time.
In-between releases containing corrections for issues are continuously provided through fixes
and patches.
SAP SuccessFactors Solutions releases follow the ‘One service for all customers’ approach
which means that:
● All customers are on the same version
● Critical issues are resolved through emergency fixes
● Other important issues are fixed through weekly patches
In general, cloud services are available and maintained as long as customers are subscribed
to them.
Note:
Stay current by accessing the latest release information on SAP SuccessFactors.
Note:
The release communication process as described may change over time. So keep
yourself up-to-date on the SAP’s release strategy.
Related Resources
You can find detailed information about the SAP’s release, upgrade, and maintenance
strategy on the SAP Maintenance Information portal.
Patches
SAP SuccessFactors periodically releases updates to correct issues or add new features for
SAP SuccessFactors products. You can visit the SAP SuccessFactors Community Portal to
access the latest SAP SuccessFactors patch information.
It is also available to S-users, along with all release details and resources on the SAP
SuccessFactors Community.
Animation
For more information on this topic please view the animation in the lesson
Understanding release updates and the What's New Viewer in your online course.
1. Search: Search is a great option if you know what you are looking for and want to find it
quickly. For example, you can search by keyword or reference number.
2. Filter: You can use one or more of the following filters to narrow the list.
a. Module: This filter is used to limit the release items to specific products or modules.
b. Feature: This filter is used to find the release items related to a set of features within or
across solutions.
c. Type: This filter is used to look at release items based on whether they are a change or
something new.
d. Lifecycle: This filter is used to limit the release items based on their availability status.
• Release items with Full Availability are available to all customers, subject to their
configuration type. Most release items are fully available.
• Release items with Limited Availability are only available to a subset of customers,
usually because they require an additional agreement.
e. Major or Minor: This filter is used to identify items based on their impact on the
business.
f. Configuration Type: This filter is used to limit release items to those with a specific
configuration type (universal, admin opt-in, and so on).
g. Software Version: This filter is used to limit the release items to those in the release
you’re adopting. By default, the viewer is pre-filtered to the current release. We keep older
versions in the viewer so that you can go back and see all changes to a feature or module
over time.
h. Latest Document Revision: This filter refers to What’s New itself, not the corresponding
guide. It tells you when that particular What’s New Viewer item was last updated.
i. Valid From and Valid To: These filters show you items with a Valid as Of date within a
specified date range. This date corresponds to when the features goes to production.
3. Table rows per page: It is possible to select how many rows to display in each page of the
table. Options range from 25 and all rows per page. When you download the What’s New
Viewer content, the system only includes the items displayed on the current page.
4. Download the content: You can download the content of the table as a .csv file and use
your favorite spreadsheet tool to open and edit it. You can also download it as a .pdf file.
There are two things to note about the download options.
a. First, the download will only include the items displayed on the current page of the
viewer. If you would like to download the complete set of release items in the viewer,
choose to display all entries in the table first.
b. Second, the download only includes the text displayed in each row. This means the
actual links to topics and demos are not included in the download files.
5. Share: You can use the Share feature to e-mail a link to your colleagues. If you’ve applied
filters to the table before sharing it, those filters will still be in place when the recipients
follow the link. Should the recipients wish to view all the release items, they easily can by
simply clearing the filters.
6. Show or Hide Columns: We can choose the columns to display in the What’s New Viewer.
When you download the What’s New Viewer's content, the system includes all columns
regardless of your column display settings.
7. Sort: We can sort items in ascending or descending order in any of the columns.
8. Links to full topics: Each row in the What’s New Viewer table represents a full release
information topic. To view the full topic, choose the See More link. To get back to the table
from the topic, use your browser’s back button.
Figure 215: Example from the What's New Viewer – Technical Details and Related Information
Note:
Be sure to review the deprecated items for this release using the What's New
Viewer and filtering by Lifecycle:DeprecatedandRelease.
LESSON SUMMARY
You should now be able to:
● Stay current with the SAP SuccessFactors solutions
● Maintain knowledge with the release updates via the What's New Viewer
Learning Assessment
1. During an SAP SuccessFactors HXM Product implementation, what is the document used
to capture the customer’s requirements in a standardized format for each module?
Choose the correct answer.
X A Kickoff Deck
X B Configuration Workbook
X C Project Log