0% found this document useful (0 votes)
192 views73 pages

SAP SuccessFactors Notes

The document outlines the components and processes related to SAP SuccessFactors, including submodules, login types, implementation steps, methodologies, deployment models, and data migration. It details the roles and permissions within the system, data models, and the advantages of using XML for data integration. Additionally, it provides insights into user management, profile configuration, and the creation of picklists and custom objects.

Uploaded by

sairamkaila2
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
192 views73 pages

SAP SuccessFactors Notes

The document outlines the components and processes related to SAP SuccessFactors, including submodules, login types, implementation steps, methodologies, deployment models, and data migration. It details the roles and permissions within the system, data models, and the advantages of using XML for data integration. Additionally, it provides insights into user management, profile configuration, and the creation of picklists and custom objects.

Uploaded by

sairamkaila2
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

29 JAN 2024

A. SAP SuccessFactors Submodules:


1. Employee Central – Effected Dated Entities
2. Time Off
3. Pay Roll
4. LMS
5. Compensation
6. Onboarding
7. Recruitment
8. Reporting
9. Succession & Development

B. Login types:
Provisioning Instances
Certified Consultants Admins
Creating Admins Users
Activation

Note: Things to do in provisioning:


Create Super Admin, Lang Pack
active., RBP Activation, Uploading
Data Models, Uploading Picklists (in
XML Files)

C. 7 Steps in Implementation:
1. PTO (Project team Orientation) – Taking everyone onboard
2. Requirement Gathering – Getting client needs
3. Flow chart preparation - Design
4. Implementation/Configuration
5. Iteration/Testing
6. User Acceptance Testing
7. Support & Maintenance

D. Methodologies:
Waterfall Methodology Agile Methodology
Fixed linear project management style Flexible and dynamic style

Methodology Phases
1. Preparation
2. Experiment
3. Realize
4. Deploy
1|Page
E. Deployment Models: (Interview Question)
• Talent Hybrid Models – Smaller Modules integrated into SF
• Fully Cloud HCM Module – HCM on S/4 HANA & No SF involved
• Side by Side HCM – HCM + SF (Usually EC as Core HR)

F. Data Migration/Transfer: (Interview Question)


• HCI – HANA Cloud integration (HCI): On premise to Cloud integration (Now CPI)
• PI – Process Integration – SAP and Non-SAP Integration

G. Upgrade/Release System:
Types of releases/Updates

• Important – Important to use the System properly


• Mandatory – Must update
• Recommended – It is recommended but not mandatory
All have the following:

• Details – Version details, new features


• Changelog
• Videos and PDFs for reference
Choice:

• Upgrade: Get client approval to make the upgrade regardless of the priority, in case of
mandatory convince the client
OR

• Save for later – Delay the upgrade

2|Page
30 JAN 2024

H. Data Models:
Points to remember:
o Only Provisioning consultants can Upload data models
o Data Models can be downloaded from SAP Partner edge portal as XML
(Extendable Markup Language) files by logging in with SAP Universal ID provided
to the consultant or Client
o Cannot be uploaded by anyone else
o Important for exam point of view
(So not part of our training as it is only for Certified consultants to use)
Types of Data Models:
Model Type Use/Characteristics
Corporate Data Model Everything related to company
Country Specific Data Models Address of the company – Geo-zone, country etc.
Succession Data Model Everything about employee personal details
Country Specific Succession Data Model Aadhar, PAN or Social Security etc.

I. Why SAP chose XML/ Advantages of using XML:

• Data Structure – Hierarchical Structure to represent Data


• Data Integration – Can be a standard way to integrate data between two systems
• Customization – Easy to customize
• Webservices – Communicate between systems using SOAP & REST
o SOAP – Simple Object Access Protocol
o REST – Representative State Transfer
• Data Migration – Easy to migrate data from legacy/old systems to new systems
Example:

• CDM – Employee ID, Company’s PAN no etc.


• CSF-DM – Branch at which the employee works; Company Address and local address codes
like PIN
• SDM – Employee Blood group
• CSF-DM – Aadhar No of employee
Foundation Objects: Foundation objects, such as job codes, or cost centres, are one type of
Employee Central objects, which are used to set up data across an entire organization. They are
defined and configured in the Corporate Data Model.

3|Page
J. SAP SuccessFactors Employee Central Core structure

Workflow
Event Reasons*
Business Rules

*Interview Question
o Events are – Hiring of an employee, promotion, Termination etc.
o Events cannot be configured (Already configured by SAP)
o Event Reasons can be configured
Workflow is Defining Approvers
XML Validation:

Already Provided in the folder Provisioning Consultant can


XML File Edit Using XML editor
DTD File Validate Using this file

Linking a data model to a DTD: (May be an exam question)


Data Model DTD
Succession Data Model st-form.dtd
Country Specific Succession Data Model Country-Specific-fields.dtd
Corporate Data Model Corporate-datamodel.dtd
Country Specific Data Model Country-Specific-fields.dtd

XML Code:
Example:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE succession-data-model PUBLIC
"-//SuccessFactors, Inc.//DTD Succession Data Model 1.0//EN"
"http://svn/viewvc/svn/V4/trunk/src/com/sf/dtd/sf-form.dtd?view=co">
<succession-data-model>
<description>Success Factors Standard Data Model</description>
<standard-element id="userId" max-length="100" required="false" matrix-filter="false">
<label>User ID</label>

4|Page
<label xml:lang="fr-CA">ID d’utilisateur</label>
<label xml:lang="es-ES">ID de usuario</label>

<label xml:lang="zh-CN">用户标识符</label>

<label xml:lang="en-GB">User ID</label>


<label xml:lang="fr-FR">Identifiant utilisateur</label>
<label xml:lang="de-DE">Benutzerkennung</label>

<label xml:lang="ja-JP">ユーザー ID</label>

<label xml:lang="it-IT">ID utente</label>


<label xml:lang="pt-BR">ID do usuário</label>

<label xml:lang="ko-KR">사용자 ID</label>

<label xml:lang="en-US">User ID</label>


</standard-element>

Element Attribute
K. SAP Platform Overview:

Common terms used in SAP SuccessFactors:


Terms Definitions
Instance An instance is the front end or customer-facing-view, of sap successfactors
system.

Provisioning Back-end of the System on Provisional consultants can use, not client.

5|Page
Admin Centre Main Dashboard to configure and maintain the systems. Can also manage
integrations as well.

Role Based Managing the permissions assigned to users to view or change data based
Permissions (RBP) on type of user

Proxy One employee can act on behalf of another

Home Page Landing page after an employee logs into SF. Has a no.of function, tasks
and othe activities

Org Chart Interactive view of organizational Hierarchy

Picklist Dropdown or cascading menu that a user can pick from

Metadata MDF is useful to create In-App extensions and build simple apps without
Framework (MDF) writing code

User Data File It is a .csv(Comma Sepereted Value file) that can be either manually created
or from HRIS system- Helpful in Bulk updates to employee data.

Form Templates Templates


Forms Forms

Job Code This is assigned to a particular job along with required competencies to
automate performance criteria

Line of Sight Visibility of reports -eg: A manager can view reports of employees that
report to him and their details.

Rating Scales Defines rating scale (0-4 or 1-5/7 etc) useful for performance management
Role Names Three types of roles:

• ESS – Employee Self Service – View and edit personal data


• MSS – Manager Self Service – Can view reports of employees
• Admin/HR – Can Edit HR details like salary and all

Route Maps Route maps specify the order in which a form


moves from one employee to another and
what employees can do during each step.

RBP Design Framework

• Permission Group – A group of users with similar characteristic


• Permission Role – A list of permissions or transactions
• Granted User – Group of users to whom permission needs to be granted
• Target User – Group of employees on which users are granted permission
Access to Provisioning:

• Through Provisioning we can create Super Admins


• Language Packs activation – Select and Enable a language pack based on client requirement
• Role Based Permission Refresh – Refresh dynamic permission groups

6|Page
• Uploading Data models – XML editing and uploading
• Uploading Picklists – Defining elements in dropdown menu
In Provisioning:
Creating Super Admin: Company Settings → “Ctrl+F” to find Super Admin
RBP in Provisioning: In Company Settings
Activating Language Pack:

7|Page
XML Screenshots:

Corporate Data Model Succession Data Model

8|Page
31 JAN 2024
Product Login Page:

Dashboard

9|Page
Proxy Management:(Action Search →Proxy Management)

User Search Window (Find User in the above window)

10 | P a g e
Batch Importing: (Action Search → Grant Proxy Import)

How it is mapped:

Interview Questions:
USERID: Whose Account a Proxy can access
PROXYID: Who can access another user’s account
ASSIGNMENT_ID_USERID and ASSIGNMENT_ID_PROXYID: Use these instead of their
namesakes (Only one of those fields must be filled)

EDIT and Delete:

Role Based Permissions:


Creating Dynamic Group: (Action Search---→Manage Permission Groups→Create New)

11 | P a g e
Give a unique group name
Define Conditions for group (Inclusion and exclusion)
It Can be Department, country or Nationality or mix of several conditions
Can also be different people pools
E.g.: Office A has Sales and Fin Dept and So does Office B; To include Sales A & Fin B use two pools

12 | P a g e
Create Permission Role: (Level of User ESS, MSS or Admin and extent)
(Action Search→Manage Permission Role)

We can create new permission role and the 2nd image comes up
We can name to the role and provide description-name must be unique.
13 | P a g e
Define the permissions they have access to (Image below)

It can be user permissions or administration Permissions depending on the person’s role or client.
Then we grant permission in that we have to give Granted group and target groups.
These groups are created from “Manage Permission Groups”

14 | P a g e
Theme Manager: (Action Search → Theme Manager)

Can Change Colors and edit images except Banner which is in “Manage Home page”
Home page Management

15 | P a g e
Banner Image 19:6 for desktop and 3:4 for Mobile – 1080P.

Quick Actions:
Note: Choose standard or custom quick actions you want to show on the home page and the order you
want them to appear in. You can create and enable up to 5 custom quick actions. People can see up to
16 quick actions on the home page in total, the top 14 enabled quick actions that are visible to them,
in the order below, plus 2 standard quick actions for Reminders and Favorites. To change the order,
you can drag and drop them with a mouse or use the More Actions menu.

16 | P a g e
Favorites:
Where to find favorites:

Managing Favorites:

Surveys: (Done later)

17 | P a g e
Organizational Updates

18 | P a g e
01 FEB 2024
Three types of profiles:
Employee Profile: Own Profile
Public Profile: Searchable Profile
People Profile: (Configure) What profiles are being configured

Add new employee:


One employee at a time: (Must fill all the mandatory details to add)

19 | P a g e
Batch Import or Uploading a lot of employees into the system:
Step 1: Download “Basic Import” template .csv file

Step 2: In the downloaded .csv file, two rows are already filled with details:
o 1st Row: “Identifier row” for System to recognize and fill in the appropriate value
o 2nd Row: “Label Row” can be edited in “Manage Business Config.” to make changes;
this is for our understanding

Step 3: Fill the details of the employee to with Status being “Active” for working and “Inactive” for
left employees and so on; Manager and HR user codes etc.
Note: Incase no manager is known it must be “NO_MANAGER” and “NO_HR” to proceed; they can
be updated later.

Step 4: Once filled the file must be uploaded to the system and validated for any errors like incorrect
employee ID and duplicate employees etc.
20 | P a g e
Step 5: Schedule Job Manager can provide report/status on uploads – How many successes or failure.

Step 6: Once validated and imported we can check employee details in Search action

21 | P a g e
Send User Welcome email
Group Mail

Individual Mail

22 | P a g e
Export Employee detail: (Search Action→Employee Export)

.ZIP file with .csv file is downloaded

23 | P a g e
Configure People Profile:

Custom Section Creation:

Step 1 Configure object definition


Object definition
Give the details
Change the same in the
Label “Company Car Venu”
details
Refer Image in Step 1 for details

Step 2 Permission role


Human Resources Venu
Permissions
Miscellaneous permission
Search for the object created Company Car Venu
Give the permission
Save Changed

Update in details Label as well

Step 3 Manage UI configuration


Create New
ID VENUCAR124
Base object Company Car Venu
Select add group
Drag and drop the required field in the required
place

Edit Properties
Change the title name
Employee details

Save

24 | P a g e
Step 4 Make Visibility
Configure people profiles
New Section
Employee Personal Details Employee data
Scroll down
Live profile MDF Information

MDF SCREEN ID VENUCAR124

Save

Step 5 Permission role


Permission roles
permissions
employee view
give permissions
Save

Output Go to Employee profile & Check

25 | P a g e
Step 1: Defining Custom object (A Unique code must be given by us in the image)

Step 2: Assign Permission to view/edit the custom section for people profile: (Allow users and
Admins to view/edit or delete details on profiles)

26 | P a g e
Step 3: Manage UI Configuration: Customize how it looks in front end

We give ID here and save it in “Configure Object Definition” in “Default Screen” (VENUCAR124)
refer step 1 image.
Step 4: Assigning MDF object screen Id to People profile

In Configure People profile we can add “Live MDF Block” to any section or create new section and
give there.
I gave it in Job Information → Test MDF → Live Profile MDF Information → Screen ID

Result Screen: in Public Profile of “Venu Gopal Veeraghanta”

Step 5: Assigning permission for employees to view and edit information for the object from their
own profile

Reason: the employee cannot view this without giving permission so on an ESS level we must repeat
step 2 to allow employees to view and edit the company car details.
Search Action → Manage Permission Roles → Go to the employee role (ESS Level) whatever
defined → Miscellaneous Permissions → Company Car Venu → Assign appropriate permissions.

27 | P a g e
Manage Badges: Search Action → Manage Badges

Custom Badges:
Create new Badge
Select or upload an icon for the badge and give a name
Active and Inactive Badges:
Inactive badges are grey (Team work) and active ones are colored (Barbie)

28 | P a g e
02 FEB 2023
Picklist Creation:(Drop Down Menu)
1. Search Action → Picklist Centre

2. Click “+” icon beside search box to start creating new picklist

3. After giving details, we can add values (office location pick list Hyderabad, Bangalore,
Chennai etc. are values we can add)

29 | P a g e
The values are as follows

4. Now create child pick list for Branches = Madhapur, Hitech city, Indiranagar, Yelahanka etc.

30 | P a g e
5. Now we can create new object in “Configure Object Definition” and in fields give data type
as “picklist” and in Valid Value Sources give “picklist ID”.

31 | P a g e
Final Object looks like:

6. Now Permission must be given to you to view/edit the object in “Manage Permission Roles”
and System admin role

32 | P a g e
7. Check UI by Searching for “Manage Configuration UI” and searching for “Office Location”

8. In “Manage Data” we can see if the list is active and has the values we given

33 | P a g e
MDF Object Configuration:

For a field we can define a data type e.g.: DOB is Date data type; Name is a string; Age is a Numeric
List of Data types:

Data types Comment

Attachment Allow attachments to be uploaded when given permission

Auto Complete Gets filled from system based on given parameters

Auto Number A number is filled by the system based on parameters

Boolean Yes or No options to given field

CLOB Not usually used in EC

Date Can enter date only

DateTime Date and time can be entered

Decimal A decimal can be given

Enum

Foundation
Object

Generic Object

Number
A numeric value can be given

A picklist is created at “Picklist Centre” and can be added here with its’ id in
Picklist
Valid value source. [Dropdown Menu]

String Any kind of input can be given

Time Time can be given

Translatable Given data can be translated

User Search for User

Documentation:
https://help.sap.com/docs/SAP_SUCCESSFACTORS_PLATFORM/d599f15995d348a1b45ba5603e2
aba9b/55a30a6eca14441f921b4c6f159fbe2d.html?locale=en-US

34 | P a g e
Association in MDF Objects:
This association means adding a relation to the current object with another object it can be 3 ways

MDF Association Comment

Composite Can be 1:1 or 1: Many but the association must be parent and child effective date
must be of parent
e.g.: Legal Entity will be associated with BU, Branches, Offices and locations etc.
here legal entity is parent
Another Explanation: When the child object cannot exist independently form the
parent object

Valid When Effective date is basic and 1: many associations is possible


Another Explanation: Both Objects can be independent despite the association then
this is used

Join By Column 1:1 association only and there must be commonness e.g.: personal details and person
details have overlapping details only these can be associated in this way

Images:

35 | P a g e
Note:
Association between parent and child object must be done from child only i.e. S/O Siva Rama Kumar
is present in Venu’s profile only, not the other way around.
Name mut be Cust_to<Parent Object name> and Destination object also “Parent Object name”

36 | P a g e
Finding the Association:
Manage Configuration UI

Manage Data:

Composite and JBC are not defined properly

37 | P a g e
05 Feb 2024

Creating Company Structure Configuration:


Here we are giving Legal entity>BU>Division>Department and Sub division
Click Add “+” in the first screen and get this dialogue box give a structure id and Name

Starting will look like

Now Add other child entities as mentioned earlier

38 | P a g e
Customize the color and what is displayed in Structure Overview*

Final Structure:

39 | P a g e
Entering Data:
In Manage Data enter the Legal Entity and other details

Final Structure

40 | P a g e
Manage Position: (Giving Position Code by System)
Step 1: Sequence
Create “Sequence” in “Manage Data” give Sequence ID and some value 1000 is e.g.

Step 2: Create Business Rule:


We have to create business rule to Assign Alphanumeric code automatically
Configure Business Rule and click “+” to create new business rule and Choose basic rule to
start with
Note: Basic Rule is being phased out and all the rules will be preconfigured by SAP
Give rule id and other details as follows: (Base Object must be “Position”

41 | P a g e
Configure the Business Rule as follows

Here if the Position code for a position is Zero for Microsoft Corp. then the company ID
generated will be “MSFTCORP1000” and so on. That is the condition for business rule
Step 3: In manage UI configuration we will disable the ability to manually add code and give
the screen id as Default screen in Obj Definition.
Step 4: Give the Business rules in the configuration Obj Definition in Save Rules at the
bottom of the object “Position”

Once the rules are set you can enter position details in the next step.

42 | P a g e
Step 5: Enter data in “Manage Position” and you will automatically get the data:

Here since we disabled it in UI we cannot enter code itself but after filling all the other details
we get code automatically as follows:

43 | P a g e
Types of MDF Associations:
• MDF to MDF: Legal Entity to Business Unit both are generic objects
• XML to MDF: Location to Legal Entity where first one is XML defined FO and LE is
MDF
• XML to XML: This Association is between two XML FO’s such as Location and
Geo-zones
• MDF to XML is non standard association and not frequently used
Field Criteria is defined by giving Field criteria settings in Configure Object Definition
(COD) and the rules are as follows:
In the example we are giving field criteria to “Department” in “Position Mangement” within
position MDF object.
We already assigned association with division parent and now must give field criteria in
“Division” and name it “Cust_toDivision.internalid” and destination field as “Division” and
save.
Here I am facing issue with server as it is showing error while saving position object will try
again in the weekend.

44 | P a g e
06 FEB 2024
Configure Alert Message:
Alert Message is a notification sent by the system to an approver to get their attention
towards an action performed by a User.

Base Objects of employee data that require alert message are (Generally):
• Job Information
• Employment Info
• Compensation
• Work Permit
• Recurring Pay & Non-Recurring Pay
• Global Assignments
Business Example: Alert User when their Contract is expiring
Now let Us Configure an alert Message:
Step 1: Creating Alert Message ID (Alert Message is an MDF object)
We define alert message. Here I am creating a message for change in “Position” made by a
user and it needs approval

45 | P a g e
Step 2: Creating Workflow (Workflow is a Foundation object)
We can add workflow by going to “Manage Organization, pay & Job Structure” and Create New
“Workflow Configuration”

Note : Both HR and HR Manager will get notified and they can approve

46 | P a g e
Step 3: Create Business Rules

Step 5: Add the rule to base object Manage Business Config.

47 | P a g e
Step 6: Synchronize the rule with base object

48 | P a g e
View User Permissions:
Search Action → View user permission and search for user

49 | P a g e
Reset User Password:

Reset individual user password (with supplied password) & Reset individual user password

Reset group of users passwords.

50 | P a g e
Reser User Accounts

Password & Login Policy

51 | P a g e
Static Group import:

52 | P a g e
Company Settings in Instance:
There are two types of settings in Instance for Company Settings:
1. Company Systems and Logo Settings
2. Platform Feature Settings
Scan the QR code or click on the link :

53 | P a g e
07 FEB 2024

Event Reason:

Must Practice Derivation and Business Rule

54 | P a g e
Creating new FO Objects in “Manage Organisation, Pay and Structure”
Pay grade

Pay Component

Pay Component Group:

Pay Scale:

55 | P a g e
The Following Objects are MDF Objects and to create data for this “Manage Data”
Job Function:

Job Classification

56 | P a g e
Exercise Examples:
Page 87

57 | P a g e
Page 96:

58 | P a g e
08 FEB 2024

Check Tool:(Page 119-THR 80)

Use the code in red box for Support to get quicker results

59 | P a g e
Reporting:
Search Action → Go to Reports Centre
Employee Central only uses table type of reports and Reporting is one of the modules

Domain:

60 | P a g e
List of Domains

61 | P a g e
Report for Single Domain(Employee Profile)

Report for Cross Domain

Multidomain Example

62 | P a g e
Interview Questions for Reports
Table export is in PDF, Excel, PDF and PPT formats only
Data domains can be in three types

Text Replacement
Search Action → Text Replacement

63 | P a g e
Business Rule Scenario:
ABC Ltd wants the Marriage Date in Employee Personal Info to be visible only when the employee’s
Marital status is set to “Married”
Business Rule:

Synchronizing With the object by assigning to “Personalinfo” in Manage Business Confi.”

64 | P a g e
Assignment THR 80 Pg: 168
Configure Custom Navigation: (Company Website ID 49)

Configure Org Chart: THR 80 -172 pg

View Org Chart

View Org Chart


without Photo

Organization Updates in Home Page

65 | P a g e
Email Notifications Settings:

66 | P a g e
09 FEB 2024

Position to Job Info Synchronization is done by


Creating rule in “Configure Business Rule”

Assigning the rule:


In “Position Management Settings” → “Synchronization”

67 | P a g e
12 FEB 2024

Event Reason - Derivation Rule Screenshot

Mass Data Change Through Business Rule:

68 | P a g e
Position Management Settings:

1
2

69 | P a g e
7

Position Management Settings and Explanation (Mine)

Position Management
Explanation
Settings
General PM Settings like when a position must be flagged as "To Be
General
Hired"
Hierarchy Position Hierarchy Settings
Synchronization Synchronise Job info to Position and vice versa
UI Customization How the front-end screen would look like in "Manage Position"
Set rules for an employee to return to a position after a long leave
Right to return
or a global assignment through Business rules
Probation period where new and old employee work for same
Transition Period
position and old emp leaves after probation period
Integration Integration with recruitment module through Business rules
Import How the system functions during import of positions

70 | P a g e
Position Management Settings and Explanation (System)

Position Management Settings Explanation


You can use the options on this tab to regulate general
General
behaviour in Position Management.
You can use the options on this tab to determine whether and
Hierarchy how changes to one hierarchy are reflected in the other
hierarchy.
You can use the options on this tab to determine whether and
Synchronization how changes to attributes of Position or Job Info are reflected in
the other direction.
You can use the options on this tab to determine how your UI
UI Customization
behaves.
You can use the options on this tab to regulate the right to
return from a leave of absence or global assignment. You only
Right to return
need them if you’re using Position Management in conjunction
with Time Off, Global Assignments or Higher Duty Assignments.
You can use the options on this tab to determine whether a
transition period for positions is allowed or not. With a
transition period, you can define a period in which a position
can be overstaffed by incumbent or FTE. This means that you
can assign a successor to a position while the employee who is
Transition Period
leaving the position is still assigned even if the position is
overstaffed as a result. You can either switch on this feature
globally for all positions with this option or you can use the
options in the “Position Type” if the feature should only be
relevant for a group of positions.
You can use the option on this tab to configure the integration
Integration
with Recruiting Management.
You can use the options on this tab to configure how the system
Import
behaves in import scenarios.

71 | P a g e
13 FEB 2024

Recruitment Integration:

Rule for Deriving Job Requisition Template ID

Field Mapping Rule to Create Job Requisition from Position

72 | P a g e
Manage Mass Changes through Instance:
Search Action → Manage Mass Changes

Excecuted Screen:

There is more if scrolled down

73 | P a g e

You might also like