13/4/2020:- Class 1

Success Factors
ERP: - (Enterprise Resource Planning) for company, Man, Materials and management.
By only one system ERP platform which is SAP you can manage the whole business.
SAP is highly integrated application. (System Applications Products in Data Processing)
SAP R/3 Real-time and 3 layers
1st Layer: - Graphical user Interface (GUI)
2nd Layer: - SAP Programming – Technical
3rd Layer: - ABAP – Coding & Technical
In Success Factors: - Development Community.
Database:-
SAP: - Organization Data, Master Data, Transaction Data
Success factors: - Client (Organization data)
Success factors is maintained in Objects:-
1) Foundation Objects: - A set of data that can be shared across the entire company,
Example: job codes, departments, cost centers. Foundation objects can be subdivided
into four main areas.
a) Organization structures b) Job structures c) Pay structures d) Other data objects,
such as event reasons, workflows, and dynamic roles. We define foundation objects in
the Corporate Data Model and the country-specific Corporate Data Model.
2) Generic Objects: - We use generic objects for settings and information relating to the
people working for a business. This information includes, for example, vacation and
position information. We have to enable generic objects in our installation before we
use them. We do this in Provisioning, by checking the Enable Generic Objects box. We
define generic objects in the Succession Data Model and the country-specific Succession
Data Model.
3) Employment Object: - Employment objects include job-related information about a
person, such as compensation and hire date. We define employment objects in the
Succession Data Model.
4) Personal Object: - Employment objects include job-related information about a person,
such as compensation and hire date. We define employment objects in the Succession
Data Model. Example :- Personal detail, First Name, Last Name , Address, Dependents,
Email id , Phone Number.
There are two Interface to work on in Success Factors
Provisioning – Provisioning, backend, Permission Access, XML File
Instance - Since 2014 it is being tried from Instance

Provisioning is the backend configuration tool.

An instance is the frontend (the customer's space on the SF server).
The instance is accessible to implementers, admins & end users. It is used to customize tiles,
manage permissions, oversee user information, generate reports, ...
Provisioning is accessible to implementers, SAP SF customer support. It is used to configure the
system features, turn on or off purchased modules, upload templates

1. BBP – Business Blue Print

2. Review
3. Implementation – It is front end & Backend
4. Testing
5. Go live – Training

14/4/2020:- Class 2

Employee Central: - Employee Central, It captures information about Employee profile and
Talent Information
Implementation Steps in EC: - After you get the Success factors License & log in details.
1) Provisioning System, Account – Log in to provisioning system.
2) Super Administrator – Admin user creation – through Provisioning system.
3) Load / Configure Corporate Data Model – from Succession Mgmt in Provisioning
Desktop XML.
4) Load Succession Data Model. ( Provisioning)
5) Country Specific Corporate Data Model – from Company Settings in Provisioning
6) Country Specific Succession Data Model. ( Provisioning)
7) Create/Configure Foundation Objects, XML Data Model and BCUI from Instance.
8) Propagation Rules Data Model, XML Desktop and Load into Provisioning System.
9) Load / Configure the Event Reason Derivation rules – Load into Provisioning, Later
Instance ( Events – Transfers).
10) Workflow Derivation Rules – XML to provisioning, workflow from instance itself.
11) Role based Permission Setup – Instance.
12) Importing Employee Data – Instance.
13) HRIS Synchronization Job – Provisioning System.
 14) Setup Leave of Absence / Time Off – Instance.

Provisioning System
1. Login
2. Company Settings
3. Search – Employee Central
4. Enable: - Attachment manager
5. Enable: - Employee Profile Audit
6. Enable: - Employee Foundation Objects –V2 (Version)

In provisioning, we have to go to –

Succession Planning Management --> To import or export any type of data (Corporate data
model or HRIS data model).

Data Models

Company Settings – Succession management- Import/Export Data

• Import/Export country specific XML for succession data model
• Import/Export corporate date model XML
• Import/Export country specific XML for corporate data model
• Import/Export HRIS Propagation configuration XML
• Import/Export Rules XML for event reason derivation
• Import/Export Rules XML for work Flow derivation

Changing the Visibility (For Eg, If you want to remove or change the Visibility of Paygroup.
(True – Compulsory - Required) Visible – None/Both/Edit

15/4/2020 :- Class 3
First time when we login into Instance, we will see only Manage role based permission access
Add User Name - Grant Permission
How to set User permission?
Steps - Manage Role based permission → Create Super Admin → Name → Grant Permission
How to give Permission role?
Admin Centre → Permission role list → Click from the list → Create new → Like (Admin) → Click
Permission
Manage permission group →
Create → Group name → then select → Country → Done
Legal Entity is part of Manage organization pay and job structure
Cost Centre – To calculate cost always denote with K

16/4/2020 :- Class 4

CREATING A FOUNDATION OBJECT

1. Tool search -> manage organization and pay structure

2. Select the type of foundation object (legal entity , department, business unit etc )
3. Fill the necessary details to create the foundation object
4. Click on save.

VIEWING / EDITING THE FOUNDATION OBJECT

1. Tool Search -> Manage organization and pay structure

2. In Search box select the type of foundation object
3. Enter the name of the foundation object
4. Go to “Action” and then click on “Make Correction”
5. Do the necessary corrections
6. Click on “Save Changes”

ASSOCIATION – the link of one foundation object to another foundation object

7. · Business Unit is linked with Legal Entity.

8. · Cost center is linked with Legal Entity and Business Unit.
9. · We can change the association by changing the XML file

17/4/2020 :- Class 5
Import Employee Data
There are two ways to upload the data - Provisioning & Instance
In Provisioning: - Company Settings – Succession Management
→ Succession model management → Click on Export/Import Data Model.
# The Set of Data Model will be given by the Client side.
Instance: - Update user information → Employee data import → Downloads templates → Select
Entity – Basic Import ( Remember Basic Import is the first import ) –Generate the Template –
Fill in the details in the template - then save the data in CSV format – comeback to Import Data
– select the entity – Browse and Upload your saved Data here and Import – click on Import.
We can check our file in Monitor Job for errors if we get any errors to upload the data or else
we will also get the upload report here.

(How to know what are the important field? Have to check in Foundation Data)
Important Info:-

- Event data & Personal ID entered are the predefined data for the employee data in Personal
Information.
- Visibility: - both (view & edit) , none and view (only view).
Required: - True or False.
- Associations works only for Foundation Object.
- There are 2 files we work in SF → XML (Provisioning) & CSV (Instance).
- How many options are there to perform Visibility? -→ BOTH /VIEW/NONE
- Required – True/ False.
- Configure Object Definitions: - To change the associations via Instance.
- XML File associations can be changed from HRIS Association.

- PII can be True & False (It is used to Hide and mask National ID data from SF Instance)

- Label – Change the name of the object.

- Can we change or replace legal Entity by Text? Answer – NO

- We can never change Foundation objects in label.

- For changes we need to come in XML file.

- Text Replacements for replacing the text of the objects.

For text replacement, we can direct search in tool search (Steps: - Admin center- Text
Replacements)
We can overwrite the default text of a key by typing a value in the Replace with text box.
When you click save, the application overwrites the default text for that key with your
Customized value throughout the application. You can restore the default text by clearing the
Value in the Replace with text box on clicking save.

- Changes will be in HRIS field

- How to change Visibility → Manage permission role → Permission → View/Edit
- Foundation objects is linked One to one or One to many
- Association always work with foundation date only

Configure Object Definition –-> search → Object definition→ Legal Entity → (Association) Take
action→ Make correction → Association
Upload data.
Configure Object Definitions: - We can define the objects, Associations of the objects and can
change the visibility and get the information of the objects and you can also apply rules and
check rules of the object.
Visibility can be changed from Configure object definitions in Instance, Search – Object
Definitions – Select the object – Change the API visibility.
Using Configure Object Definitions:-

For example using: - Configure Object Definitions

A. Navigate to Configure Object Definition > Search for "Object Definition"

and select an existing custom MDF object
B. Perform a change in the object (i.e; add, edit, delete a field or change the
data type to picklist) For Example :-


1. Field PositionType-mdfSystemExternalUserVisibility is removed. Removing pre-delivered
fields is not allowed.
2. Association PositionType-transitionPeriod is either removed or renamed. Removing or
renaming pre-delivered associations is not allowed.
MDF system Entity ID

C. Save
D. Navigate to Manage Configuration UI > Search for the custom MDF object
you changed
E. Note sometimes the changes did not reflect in Manage Configuration UI
(i.e; the field did not become a picklist or the new field does not reflect).

Resolution

You will need to perform a refresh of the UI via the steps below:

1. Navigate to Manage Configuration UI > Search for the configured existing

custom MDF object
2. In the Select Base Object, reselect the Base Object (just simply search
for the same object in Select Base Object). This will refresh the UI. You
will notice that the changes have reflected in the UI.
3. Click Save.
For Example: - How to modify or add an additional field to existing MDF
Foundation Object through Configure Object Definition.

In this example, we will add a custom field "Notes" to a existing Foundation

Object: "Business Unit". These steps are applicable to any available Foundation
Object.

1. Login to Success Factors as an administrative user

2. Navigate to "Admin Center"
3. Select "Company Settings" -> "Configure Object Definitions"
4. In the Search Field drop-down, select: "Object Definition". Select the
object from the second drop-down (example: "Business Unit")

The definition for Business Unit will be displayed:

To add the "Notes" field:

1. Select "Take Action" -> "Make Correction"

2. Scroll down to the last available field in the "Fields" section and enter a
name for the field (example: "cust_note")

3. Provide the length (255) and data type (STRING) of the field.
4. Select the link "Details"
5. in the Details section, provide a Label (example: "Note") and any other
parameters required.
6. Select "Done" in details
7. Select "Save" on the object definition.

The field has now been added to the Business Unit Object.

To view the changes to the Business Unit object:

1. In Admin Center, select "Manage Data"

2. In "Search" select "Business Unit" and any object from the second drop-
down.
3. Observe that the new field "Note" has been added.

ASSOCIATION – the link of one foundation object to another foundation object

· Business Unit is linked with Legal Entity
· Cost center is linked with Legal Entity and Business Unit
· We can change the association by changing the XML file

Provisioning System

1. Login
2. Company Setting
3. Search – employee central
4. A. Enable the attachment manager
B. Employee profile data audit
C. Employee central foundation object
D. Employee central foundation object V2

Event Date and Personal ID external are the predefined data for the employee data in
PERSONAL INFORMATION
Visibility – both(view and edit) , none and view(only view)
Required – true or false
Label – change the name of the object
Association works only for Foundation Object
“TEXT REPLACEMENT” for replacing the text of the objects
“CONFIGURE OBJECT DEFINITION” -for changing the association via INSTANCE
XML file – association can be changed from hris -association

POSITIONING MANAGEMENT

Ref Link :- https://blogs.sap.com/2015/03/12/the-successfactors-employee-central-

position-management-feature/

It enables job classifications to act as the source of positions and for positions to
influence manager and matrix relationship assignments.

In SuccessFactors' Employee Central, Position Management is a feature that helps create

jobs and positions to better enhance and define a business's needs.

Position Management is an important part of SuccessFactors Employee Central

Steps in Positioning Management:-

Creating sequence (To Link the Master Data)

1. ” Manage sequence” in tool search
2. Fill the details and then save
Creating Business rule
1. Tool search -> Configure Business Rule
2. Create new rule
3. Create basic rule
4. Fill the details
5. “IF” condition is “TRUE” , then click on ALWAYS TRUE , otherwise give condition
 6. Then fill the “THEN” condition
Then click on “SAVE”

How to enable position

1. Go to provisioning

2. Generic Object -> enable manage position

3. Creating sequence

4. Configure object definition – to change the GUI ( and to check it - Manage Configuration UI)

5. Create business rule

6. Configure object definition – to assign business rule and search for the Position object and
assign the business rule in it.

7. Manage position – tool search

8. Workflow approval – from the pending request – talent workflow group

Auto Generation of the RULE

1. Tool Search à Manage Position Setting

2. General Tab
3. Is the Position External Code Auto Generated – YES

These are the general important imports generally done –

1. Basic Import
2. Biographical Information
3. Personal Information
4. Employment details
5. Compensation Info

IMPORT THE FOUNDATION DATA :-

Tool search -> IMPORT FOUNDATION DATA

To download the template, click on download template
Then fill the details in the CSV file
Import the data

CHECK THE IMPORT OF THE FOUNDATION DATA

 1. Tool Search -> MONITOR JOBS
2. Download the CSV file to check for any error
3. Check the status from the monitor job

Business Configuration:-
We Change views, decide the views like personal information, organization standard, company
information, Payroll field. It allows the administrators to maintain certain aspects of Succession
Data Model directly from Admin Tools with a user friendly screens instead of using Data Models
(i.e. XML Tags & Properties).
Decisions are taken in Business Configuration UI.
Steps:-
1) Provisioning: - Enable Business Configuration in Admin Tools.
2) Instance:- Enable Manage Business Configuration in RBP (Manage Permission Role)
3) Enable Meta Data Framework & MDF Foundation Objects ( Check MDF Framework &
MDF Foundation Objects and check whether Configure Business Rule is enabled or not)

4) Manage Business Configuration – Instance

1) Employee Central

a) HRIS elements (From here we can modify the HRIS elements as per we demand)

b) HRIS actions (From here we can create or select the HRIS actions as per the
requirement)

2) Employee Profile

3) Filters

Synchronization Job in Provisioning

The Job information is stored inside the Business Configuration in two types.

1) SDM Storage : - Service Dependency Matrix ( XML to instance )

2) BCUI Storage:- Business Configuration Interface ( Instance )
3) Job Information – for employee data, collection of different field. These are independent fields.
E.g – employee profile

Steps with Screen Shot of Business Configuration UI

1. Manage Business Configuration -> Job info

 2. Then change the necessary HRIS field

Job should be run once in a day

3. Manage Role Based Permission - Manage Permission Role - Permission - > Employee

Central Date Effective - > then to the respective data field which we

Have to find to check the data entered.

 MASS CHANGE – change a particular value of any field or object

1. Tool search -> Manage Mass Change

2. Create new

Mass Changes is a tool for HR Administrators to manage changes to employees' job information
and job relationships for any user-defined selection of employees. It allows users to efficiently
execute changes to employees' attributes due to manager reassignments, or reorganizations
affecting large numbers of employees. Example: The HR Manager responsible for 40 employees
is replaced by another person. All engineers decentralized in several departments are being
centralized in a newly created unit.

The user defines a mass change in a screen consisting of:

● An employee selection using a group definition tool similar to the one that are used for
permissions.
● The effective date that determines when the determined changes should take effect.
● The list of fields to be changed, including their new value.
The mass change definition can then be saved and initiated immediately or saved and initiated
later. Initiating a mass change creates a background job that is scheduled for immediate
execution. After mass change has run, a new status is set, dependent on the result. In the event
of errors, the user can access a log to analyze the changes that failed.
1. Provisioning - Company Settings

Select Enable Generic Objects

2. Admin – Permission to Generic Objects

Grant permission to Manage Generic Objects to Admin user.

Goto Admin Tools  Role Based permission  Manage Permission Roles.

3. Role Based Permissions for Mass Changes

Grant permission to Manage Mass Changes to Admin user in Role Based Permissions Framework.

From Admin Tools Select Manage Mass Changes::

sick
 Select Create New

Create or Select an Employee Group.

For Job Information changes, Event Reason has to be defined in the Mass Change definition

All the permissions of METADATA FRAMEWORK (Generic Object) will be available in

MISCELLANEOUS PERMISSION

These are the important things to activate for an employee

1. Employee Detail

2. Concurrent Employee

3. Global Assignment Detail

For giving permission (for Concurrent Employee)

1. Manage Permission
2. Employee Data

3. Enable – “New Assignment Company”

For giving permission (for Global Assignment Detail)

1. Manage Permission

2. Employee Data

3. Enable – “Global Assignment Detail”

Data Management – to delete the record in SF

1. Tool Search -> Data Retention Management

2. Purge request

3. Fill the details accordingly

4. “Purge Request Monitor” – to monitor ta data management request

AUDIT – to view the activity log

Tool search -> Event Notification Audit Log

Event Notification Subscription – To subscribe for additional details for a particular event

Tool search -> Event Notification Subscription

For giving permission

Permission -> Manage Data Purge

GENERIC OBJECT

To enable GENERIC OBJECT (All the generic objects can be viewed through CONFIGURE
OBJECT DEFINITION

1. Enable “Generic Object” via provisioning

2. “Employee Central Extensions using MDF” – to set the limit of the number of generic object,
which can be changed via provisioning

3. Permission -> Manage permission role -> System admin -> Permission -> “Metadata
Framework” -> Activate all the fields

Creating “Configure Object Definition “

1. Tool search -> Configure Object Definition

2. Create New

3. External Code, External Name and EffectiveStartDate – these three will be default

4. Create the field as per required with format – “cust_name”

5. Security - > Secured (YES)

Change Interface

1. Tool search -> Manage Configuration UI

2. Put ID as per choice

3. Select base object as the name of the generic object

4. Create group as per the field and the user

Permission to the generic object

1. Permission -> miscellaneous permission

2. Find the generic object (cust_name)

3. Enable the fields accordingly

4. Then save

Configure People Profile: - We can change the views and set the UI as per the requirements.

1. Employee files

2. Configure employee files

3. Add new view

4. Dashboard -> insert portlet -> add and create -> live profile mdf information -> portlet title ->
cust_name

Organisation data – the data regarding to the company

 Master data – core data according to the type of job (Eg. – employee data for HR , sales data
for Marketing) . Master Data is created once and very little change happens in master data and
change happens on demand

Transaction Data - new technical transaction functions according to the type of job. It is
changed frequently on usual basis. (E.g. – attendance, salary, leaves, orders etc.)

Behaviour levels of the framework – 1. Context of the data 2. Data type 3.Implementation of
data

WORKFLOW - It is an important part of Employee Central because it defines the approval

authorisation . It is always attached with EVENT REASON .

(XFR Rule - it signifies that if any one of the condition is true , then it will show result )

Provisioning -
1. Go to Succession Management
2. Export the workflow derivation rule

Steps to create dynamic group -

1. Tool Search -> Manage workflow group
2. Create New Group ( Company / User based )

Steps to create Event Reason -

1. Tool Search -> Manage Organisation and pay structure
2. Create New -> Event Reason

Steps to create workflow

1. Tool Search -> Manage Organisation and pay structure
2. Create New -> Workflow
3. Give the details of APPROVER,CONTRIBUTOR and CC

Steps to create Dynamic Role -

1. Tool Search -> Manage Organisation and pay structure
2. Create New -> Dynamic Role
3. Fill the details

Steps to create Business Rule -

1. Tool search -> Configure Business Rule

2. Create new rule

3. Create basic rule

4. Fill the details

5. “IF” condition is “TRUE” , then click on ALWAYS TRUE , otherwise give condition
6. Then fill the “THEN” condition

7. Then click on “SAVE”

Assign the rule -

1. Tool Search -> Manage Business Configuration

2. Go to HRIS field
3. Go to “Job Info”/ the required field
4. In the “rule” section , add the rule in Job information model / personal information
model / the required field
5. Click on SAVE

Testing the workflow -

1. Tool Search -> “Add New Employee”

2. Fill the required information of the new hire
3. Then click on SAVE

You will see that the pending request of the WORKFLOW is forwarded to the dynamic
group for further approval in Action Tab in SF, Once the request is approved, the new
employee will be hired . After the approval we can check the employee details from
“Search for action or people”.

REPORTING

1. Enable “Online Reporting” from provisioning

2. Admin Center -> Reporting
3. Click on “New ”
4. Select the type of report, reason of report etc

Reporting: - You can check reports – My Reports – All reports , Single Domain or Multiple
and you can check why you are creating the reports For Eg. RBP – Permission Reports ,
you also import it from here. You an generate report like Employee Calibration Report

EMPLOYEE EXPORT

1. Admin Center - Tool search -> Employee Export

2. Select the type
3. Download User file.

From here you can check whether employees are inactive or active in the system.

REHIRE INACTIVE EMPLOYEE

1. Tool Search-> Rehire Inactive Employee

2. Fill the details ( same as hiring new employee)
3. Click on SAVE
Note: - To activate inactive user, we have to enable “enable inactive internal user” from
provisioning.

MANAGE DASHBOARD

1. Tool search -> Manage dashboards

2. Click on the desired function based on the user defined

It is used to Administer Analytics Tiles and dashboards. Use this to build new analytics Tiles and
dashboard from SuccessStore and Upload YouCalc files. Combine tiles to create dashboards,
configure options in the dashboard filter panel and push analytics tiles to mobile devices.

Features are – Manage Standard Dashboard and YouCalc- Manage Tile based Dashboard-
Manage Dashboard Filters- Manage Date Ranges.

ADHOC REPORT

1. Tool Search -> Manage Ad Hoc Report – ( Unplanned Activity).

Note: - Manage Ad Hoc Reports (Please make sure that you read the linked implementation
guide before making or changing these settings) .

You can also manage all Ad Hoc Report Related Permissions from here.

Provisioning Questions comes for this as is there any setting of Reporting in Provisioning.

Provisioning you will have to enable Online Report Designer.

Provisioning – Enable Inactive Internal user ( To search Inactive users in the system)

EMPLOYEE CENTRAL SETTINGS:- Admin Center – Manage Employee Central Settings

Admin Center- Tool Search , to switch on & off the setting of For Eg:- Time Off, Time Sheet
Settings ( You can enable it from Instance through Manage Employee Central Settings).

Which data are included in MDF ?

1. Generic Object
2. Business Rule
3. BCUI
4. Association of Generic Object
5. Dashboard Design
6. Portlet Design, View Design
7. Screen Design
 8. Miscellaneous Permission
9. Workflow for Generic Object and Foundation Object
10. Positioning.

MOBILE CONFIGURATION

Since Success Factor is a cloud based platform, you can open it on mobile.
Go to “Mobile”-> Manage mobile users for adding the mobile.

(Enable the Mobile Feature – Mobile Specifications – You can control the user – Navigation –
Admin – Enable Mobile users. You can also check (Email Notifications, Mobile Themes,
Modules, Manage users, Export users).

12.05.2020 Class

Time Off:-

Time off – Meta data framework

The Absence management of Success factors is known as Time off

1. Holiday calendar
2. Work schedule - Job information ( 1 to 3 Holiday Calendar, Work Schedule & Time Profile)
3. Time profile
4. Account eligibility status
5. Time account
6. Period ending processing rule

Holiday calendar - Combination of different individual holiday elements/ records. To ensure that
country/region specific tool applying to the employees are taken into account when the employee
requests time off.

Steps:-
1. Build holiday then group holiday calendar

2. Work schedule – login time, log out time, break, emp grp, location, holiday calendar,
working condition.

3. Time profile- time type ex leave. This time profile will be used in time accounts for
balancing processing/ accrual creation.

4. Accrual in time sheet- daily, weekly, monthly, yearly calculation for time recording
 Time account - connecting to time type for employee, For Eg. – Vacation or in other words it is
connecting the time type to the employee (e.g - vacation)
It records the Time Type

Manage time off structure

1. Holiday
2. Permission
3. User/location
4. Load data

1st step- provisioning activate- enable time off

2nd step- permission- employee view- manage time off, time off

3rd step- employee central effective dated entities- holiday calendar and work schedules
4th step- administrative permission- manage time off. Manage time

CREATING HOLIDAY

1. Tool search -> Manage time off structure

2. Holiday in create new
3. After creating holiday …..
4. Create new -> Holiday calendar
5. Assign holiday to the particular date
6. Creating work schedule -> Create new - > Work schedule
7. Fill the details
8. Creating Time account Type
9. Create new -> Time account type
10. Create new -> time type ( *we have to create the counting method for applying it )
11. Creating time profile ->Assigning the time type to the time profile.

Explanations:-

 TIME TYPE – These are nothing but the different leave types in your organization
eg. Annual Leave, Study Leave etc.

 TIME ACCOUNT TYPE – Some of the leaves need to accrue a certain amount of
balance regularly. Hence we need to attach the Time Account Type which acts as a
Leave Bucket for that particular Time Type. For E.g. Annual leave is entitled to
accrue 20 days every year.

 TIME PROFILE – Simply put, it’s a bundle of leave types which will be assigned to
an employee.

 TIME ACCOUNT – Once we assign the leave types to an employee, we have time
account for each leave type, depending upon the type of account. It acts as a holder of
balances for each employee.

 PERIOD END PROCESSING – When an employee needs to close the current time
account and move on to the next years’ time account , the Period End Processing comes
into picture. You can now decide what the process of carry forwarding for a particular
leave type can be.
  MANUAL ADJUSTMENTS – In case the balance of an employee needs to be
corrected, this feature can be used by an Admin to manually add or deduct the balance of
that particular employee’s Time Account.

Important Link: - https://blogs.sap.com/2015/10/16/ec-time-off-for-on-time-hr-management/

Time Off :- We are creating a record.

Payroll & Time Management – is a part of Job Information and it is a part of MDF

Time off configuration

Time profile

Time type

Event reason (optional) 95%

Work flow

Business rule

Workflow attached with business rule then this business rule will be attached in configure object
definition and time type.

Holiday configuration

Holiday, holiday calendar, time acc`

Integration b/w EC payroll and time –

step 1 - SAP system configuration

Step2 - replication target system

Step3 - data replication configuration

Steps for Time Off Configuration Steps :-

1st Step: - Create Time Account type

2nd Step: - Time Type Create and assign it to Time Account in Manage Data.

3rd Steps: - Manage organization Pay & Job Structure – Create Workflow for Time off.
4th Step: - Create Event Reason (Time Off ) in Manage Org. Pay & Job Structure.

5th Step: - Configure Business Rule:- Workflow attached with business rule then this business
rule will be attached in configure object definition and time type.
Base Object for Rule is Employee Time – Create rule Time Type rule and assigning the rule to
time type and workflow
If (Employee Time to time type)
Then (Employee time to Workflow)
6th Step: - Configure Object Definitions – Object definitions – Employee Time – Save rule – Time
off rule.
7Th Step:- Come to Manage Date – Search the Time Type – Assign the Time Type Created and
assign your workflow which you created
After this to check you can make changes to any employee’s Job Information and update.
Class 16.05.2020
Time Sheet Configuration: - In Time Sheet configuration one thing is very important that is
Data Republication Configuration,

It is integration for all Assignments which we have created like

Country/ Region Assignment , Pay group Assignment ,Time Type Assignment , Company Assignment &
Employee Class Assignment. It is essential for Time Sheet Configuration.

For prepairing Time Sheet you need to create a Workschedule.

Integration Between EC Payroll & Time – (Time recording admission, How time recordings
admissibility is configured are also defined here). The Successfactors system doesn’t have
recording system in its own so it used the SAP Systems for recordings.
Then Come to Admin Tool – Tool Search – Manage Data
Step 1 :- SAP System Configuration ( Time recording kaise hoga )
Step 2:- Replication Target System ( We check whether it is relevant for ERP,Payroll or
not )
Step 3:- Data Replication Configuration
SAP System Configuration :- Integration between EC Payroll & Time Sheet.
Click on Create New: - and will ask for System Name – System URL & Client.
What is SAP Client ID :- Client here is referred as the Database in which Database we are
working.
SAP Client – 000-999 – These are Data base
Development Server: - Client ID – 101 Development Team work in this Server, they will work as
Blue print, 102 Testing, 103- Sandbox ( Common Client and 95% of Implementations happen in
this).
Quality: - Client ID – 201,202 Development Team or Testing.
Production: - 301 – if we are using SAP in office for working.
IDES (Internet Demonstration & Evaluation System) :- Client ID – 800 , this is used for
Demonstration purposes which we are used in trainings.
Class:- 18.05.2020

Note :- For Time Profile – It consists of all types of time types.

Manage Data – Employee time –
For Timesheet Configuration – Create Works chedule – Manage permissons – Enable time off
and Enable Time Tracker.
Then Configure the object Employee Time in Configure Object Definitions – Employee Time
Sheet Entry
Note :- The time profile contains all kinds of Time Types.

Overtime Calculation in Time Sheet in Success factors:-

Step 1 – Configure Time Types (Always Remember for One Event there will be 1 Time Type needed so
here , for Overtime Calculation we need One Event ,one Time Type _that is Regular Working Hours, on
the Basis of this Working time, Time Type, the Over time will be calculated ) ( Created Time Type –
Regular_Anuj)

Step 2 – Configure Time Type Group Time type here implies as the input of working hours and here we
will use 3 kinds Regular Working Hours’ Time, Working hours Below 8, Overtime Hours.

Created Reg_work_A, Below_8_An , Overtime_An

Step4 – Configure Time Valuation – it is the object which will help us to segregate the regular working
hours and the Overtime hours. ( In this option take Aggregate Input Times & Split so that system can
determine which attendance are more than 8 hours and which are less than 8 hours). Created ,
Time_VL_AN

Fill in the details Valuation Method, Threshold, Type, Fixed Value, Threshold Value-40.

Fill in the Time Type Group below – Take the regular Time Type group below 8 hours & fill in the details
in Time Type Group Above – Take below Time type group.

Step 5 – Create the Time Recording Profile: - Assign the Time Valuation (Created Over_An).

Step 6- Create Time Profile: - Create Over Time profile. ( Mark the Leave type as Favourite) Created
Over_Time.

We are not given the access to Employee Job Information ( Gareth Roberts)
Now search any Employees Job Information and Make changes inside the Time recording profiles and
Time Management fields, Now you can change informations in – Job Informations, Time Management
fields, Default Overtime Compensation Variant, Payouts & Time Off.

Next Step :- Time Recording Profile:- Again and created Record_An

( It is created to identify how time is recorded and different leave types and assign the Time Valuation.

Next Step :- Time Record Admissibility :- How much amendments in system its allowed and can be
done it records that , For Eg. Time Recording Admissibility: 4 Past Weeks / Amendments Allowed
(4WK_AMEND_YES)

After this we can make changes to Employees Job Information in time Management or Time
recording profile. with these records.
Note for Knowledge :- Employees Working time can be classified as below
Employee Working Time :- These are all part of Employee Working time.
1) Working Hours (2) Training or knowledge Transfer (3) Business Conference (4) Client Visit (5)
Business Continuity Plan.
If suppose if an employee has worked more than 40 hours per week , then the extra hours will
be treated as overtime and Employee will be treated as overtime and Employee will be paid
50% more than his/her wages rates.
 Class 21.05.2020
Whatever configurations we will be doing in Time Management it will be assigned to the
Employees Job Information.
Time Profile: - It records the time types and all information’s and leaves, all time types, and they
are assigned in Time profile.
Time Type:- What all scenarios are there, all leaves are created in Time Types, Leaves ,
Holidays , all Leaves , Holidays , Assignments.
Work Schedule:- Shift Timings
Account Eligibility Status: - Unforeseen situations Calculations, like Pregnancy ETC.
Time Account:- it is like which type of Time Recording is done or ho raha hain.
Some example of Time Account types.
Positive Time: - Calculation of breaks. Deviation in (Chutti) Leaves and Overtimes.
Negative Time: - Call Centers – Counting every second
Clock with Time or Clock without time
Accrual in Time Sheet- Daily, Weekly, monthly, Yearly calculation of Time recording.

Class 22.05.2020
Sick Leave Configuration & Configure Absence Management:-
Create Holiday- Holiday Calender – Time Account type – Create Time Type - Then assign the
Time Type to Time Account Type –
Create a Time profile and assign all the Time Types in it –
Create Event Reason for Sick Leave with Event reason as Leave of Absence ( Absence20) –
Create a Workflow for Sick Leave of Absence ( Sick_Wr_Anu) –
Create a Rule for Sick Rule( Employee Time) – and assign the Rule with Sick leave, Location,
Workflow , Event Reason –
Assign the Rule in Configure Object Definitions ( employee time objects ) ,
Then also configure the Sick Leave to Time Type.
Class: - 23.05.2020
Time Sheet Configuration:-
For Time Sheet Configuration we need integration
Data Replication Configuration: - it is the Integration between Time sheet, payroll and EC)
First we will have to activate and Define it in Replication Target System
Data Replication – Replication Target System – SAP System Configuration – and then Data
Replication Configuration.
Note:- Only your Absence and Overtime are the Deviations.

Replication Target System: TimeSh-A (TimeSh-A)Take Action

* External Code TimeSh-APrevious value.
SAP System Configuration S4 Hana-anuj (S4 Hana-anuj)Previous value.

Previous value.
* Relevant for ERP Integration YesPrevious value.
* External Name TimeSh-APrevious value.

Previous value.
* Relevant for Payroll Integration YesPrevious value.
Replication Time Offset in Minutes 60

Steps _ Manage Data - SAP System Configuration –

Assign it to Replication Target System –
and then Integrate it in Data Replication Configuration (Assign all the Time Types which you created
Earlier).
Note :- Timesheet Only calculates the deviation in Absence & Overtime.

Note:- If you want changes in Time Sheet Objects

We will do it from Configure Object Definitions – Employee Time Sheet Entry – and make
changes in the objects as required.

Note :- If You want to configure that a Manager can use the Time Sheet of Employees
Set User Permissions- Manage Permisson Role – Super Admin User – Employee Views -
And Now Enable – Time Sheet - Time Tracker.

Note :- For giving Permissions for Time Management in Success Factors.

Enable – Time Management in Provisioning
Then Manage Permission Role – RBP- Enable Employee Central Effective Dating Entities
Activate Holidays – Holiday Calendar – Time Recordings – Time Off
Then for Administrative Permissions – Manage Time off – Manage Permissions.

Class: - 26.05.2020
Time Off Collision: - It is used to configure overlapping of leaves. It is used so that the system can do
the overlapping of leaves.
For Eg:- An employee has already apply for Vacation from 21st of May – 27th May and on 20th May he got
sick and he tried to apply for sick leaves from 21st , however in the system the leaves for Vacation is
already been applied earlier by that employee and hence system will not allow the employee to apply
sick leaves , so for this Time Off Collison is required.
Tool search – Manage Data – Time Management Collison Resolution.

Steps :- Manage Data

Time Type collision Group
Assign it in Time Management Collison Resolution

TIME OFF COLLISION

1. Go to Manage Data
2. Create - time type collision group
3. Create - Time Management Collision Resolution
4. Add Incoming grouping
5. Keep specific grouping to - all others
6. After that we can assign it to the TIME PROFILE (editing the particular leave time type
attached in the time profile )

TIME LIUE OFF

1. Create time type

2. Create time account type
3. Create time profile
4. Create time type group ( we have to create two group - base price with factor 1 and premium
price with factor 0.5)
5. Create time valuation.

TOiL(Time off in Lieu) It is a regular time account and the leave taken from it is a regular absence.
If you have the roles set up such that system(RBP) allow colleagues to create absences, then colleagues
can also book those leaves and it can be made to go for approval.
But at the moment, it is not possible to restrict that to certain time types only. If your colleagues may
create absences for you, then they can create all existing types.
To provide colleagues to add leaves to other's account you would require to provide appropriate Role-
based permission same as admins/managers.

Time Off in Lieu :- If suppose in a company X an employee is working for 9 hours everyday and the
company wants divide it suppose 3 hours Training, 4 hours Work and 2 hours OT so that he can get paid
for it for 2 hours in OT and 4 hours he can get an Earned Leave later. In simple words if you want to
divide the Overtime hours in Leaves (Earned leave) and Payments ( OT-wage).
Definition: - Time off in lieu allows you to post calculated overtime into a time account based
on time recording profile settings. Employees can request specific absences that deduct time
off in lieu from time accounts

Steps for Time Off in Lieu:-

Step 1 :- Create Time Account Type :- Created Timeoff_Lieu

Step 2:- Create 3 time Types :- Time off, ( Time_lieu) , Vacation ( Vacation_34) , Regular Working
hours ( Reg_Work_An)

Step 3:- Create a Time Profile Created ( Time_Lieu) and assign all the Time Types in it, Inside the
Time profile, Assign the Time Account Type.

Then Default Import Attendance, type is the one which we have created Time Type (
Reg_Wrk_An) . In Main Absence Type: - Vacation_34 , then main attendance Time Type –
Reg_Wrk_An and now assign all the Time Types which we created in below option Available
Time Types Time off, ( Time_lieu) , Vacation ( Vacation_34) , Regular Working hours
( Reg_Work_An)

And assign all the time types below. Time Profile Created here by me as ( Time_Lieu)

Step 4:- Create Time Type Groups, we need to create 4 Time Type Groups here.
(1) Input Overtime (2) Regular working Hours (3) OT_Base & (4) OT_Premium

Here we Created Time Type Groups

1) Input_OT_A (Input_OT) assign the Regular Work hours, Time type in it.

2)Time Type Group to calculate Regular working hours , I created ( Reg_Wrk_A).

3) OT_base_An ( OT base _To calculate overtime base hours, how many hours an employee has
worked more than regular working hours and the employee will be paid accordingly).

4) OT_Pre_An ( OT Premium_To calculate overtime premium hours, how many hours an

employee has worked more than a normal and as per that he / she will get an leave).

Step 5:- Time Valuation :- We need to create two Time Valuations here 1) Overtime base 2)
Overtime premium

Time Valuation 1:-

Time Valuation: OT_BASE_AN (OT_BASE_AN)

External Name OT_BASE_AN

Valuation Type Aggregate Input Groups and Split Previous value.

Threshold Group

Valuation Method Valuate Per Day Previous value.

Threshold Type Fixed Value

Threshold Value 8

Time Type Group Below Reg_Work_A (Reg)

Time Type Group Above OT_base_An (OT_base_An)

External Code OT_BASE_AN

And in below option assign the Time Type Group

Input_OT_A (Input_OT)Previous value.

Time Valuation 2:- for Calculating the Overtime Premium

We Created the name as OT_Pre_An

Then the make the entires as below

External Name OT_Pre_An

Valuation Type Aggregate Input Groups and Split

Threshold Group

Valuation Method Valuate Per Day

Threshold Type Fixed Value

Threshold Value 2

Time Type Group Below OT_base_An (OT_base_An)

Time Type Group Above OT_Pre_An (OT_Pre_An)

External Code OT_Pre_An

And assign the Time Type Group for OT_Base below

OT_base_An (OT_base_An)Previous value.

Step 6 :- Create a Time Recording Profile as below

Time Recording Profile: OT_An (OT_An)

External Name OT_An
 Time Valuation Period Default (DEFAULTPERIOD)

Time Recording Variant Duration

Time Recording Method Positive

Workflow Configuration

External Code OT_An

Time Valuation
OT_BASE_AN (OT_BASE_AN)

OT_Pre_An (OT_Pre_An)

Here we are assigning the Two Time Valuations which we have created one for OT_Base & OT_Pre.

we change changes these information’s and update it in any Employee’s Job Information under the Option
- Time Information.

CONFIGURE ABSENCE MANAGEMENT

1. Create event reason

2. Create workflow

FLOATING HOLIDAY / OPTIONAL HOLIDAY - The uncertain holiday which comes uncertain
and not fixed to a specific date and can be changed based on the organisation or any authority.

1. Holiday calender (holiday class - none )

2. Create time account type
3. Type of time account type - recurring……..accrual frequency - annual , accrual rule
4. Create time type
5. Assign time account type to the time type

To create rule -

A. Go to “Time Management” in the rule section

B. Then select “Accrual”
C. Condition - If the employee status of an employee
( If - user - job information - employee status )
D. In the THEN condition - we have to CREATE the condition
( Time account - time account details - ……)
Below is the configuration for the THEN condition
 E. Assign the rule after saving in the accrual rule
F. If you want to create and assign any hire or termination rule , then you can do it from the
BASIC rule
G.

LEAVE ENCASHMENT

1. Give Permission - manage time off - enable manage payout

2. Manage organisation - pay component
3. Create pay component ( pay amount type - number …. In earning - yes …. Frequency -
daily )
4. Assign the pay component in the time account type assigned to the time type in the time
profile

COMPO - OFF

1. Create time account type (account creation - permanent, level of accrual automation -
automation, accrual frequency - daily )
2. Then create time type ( classification - absence)
3. Create accrual rule ( to add balances to comp off quota )
Conditions to be checked -
a) has the employer worked today ?
b) is today a non working day for the employee as per work schedule?
c) is today a holiday for the employee as per holiday calender?
4. Create a take rule to throw an error message if satisfies below conditions -
Conditions -
a) comp off date is blank or not
 b) if the employee has already taken comp off on the particular date or not
c) comp off against that date is expired or not
5. Extend the accrual rule with condition -
If the employer has not avail the comp off with the expiry (say 30 days ), then one
negative value should be added to the comp off quota calculation to reduce the comp
off

IF CONDITION OF ACCRUAL RULE

THEN CONDITION OF ACCRUAL RULE

PAYROLL

1. We have to give permission . For that -

2. Tool Search - Manage employee central settings
3. Enable “deduction management” and “Advance”
4. Tool search - configure people profile
5. Enable “Current Advance” and “Eligibility for Advance”
6. Go to RBP - employee view -enable “employment”
7. Enable Manage Advance - set the required settings
8. Now configuration part -
9. Tool search - Manage advance object
10. And create Ëligibility for advances ( Advance type - required pay component
11. To configure rule - “Advance Management” in rule section - Advance eligibility rule
12. Advance Eligibility rule

Class:- 03.06.2020

Payroll
Loans & Advances
Loans: - Employees are eligible for Home Loans, the request amount should not be more than
the eligibility amount as per the Pay Grade.
Advances: - Employees are eligible to request max one month salary advance before going to
Vacation, if they already have any advance or loan which is pending to be paid back, no new
advance can be requested.

Enable Advances from Manage Employee Central Setting – Enable Advances from Manage
People Profile – Maintain RBP – Configure Eligibility for Advances.
Important Objects for Advances / Loans: - Eligibility for Advances – Accumulation for Advances
– Non Recurring Payment – Payment and Deduction Pay Components.

Business Configuration Tool:-

How to enable Manage Business Configuration UI (BCUI) – EC :- BCUI for the SDM is a powerful Admin tool allowing
administrators to maintain certain elements of the SDM using their end-user UI, instead of
asking SuccessFactors staff to maintain these elements in the XML configuration files.
Job should be run once in a day
EC Alerts & Notifications:-

In Success Factors Employee Central you can configure To-Do alerts and email notifications that are
automatically triggered when a certain criteria is true – e. g. HR Manager is notified 30 days before an
employee’s probation period ends by displaying a “Take Action” event on HR Managers homepage. Another
user (e.g. Manager) will get an email notification regarding the ending probation period.

In our example we will describe all necessary steps how to set up an EC Alert and Notification for a Probation
Period End warning.

1 Define Alert and Notification Message

In Manage Data you can create a new Alert Message for which you can define an alert header and an alert
description. It is recommended to expand the maximum length of the alert description field to 4,000
characters. If needed, you have the possibility to translate the alert header and alert description into another
language which is active in your current system. For the translation
use alertHeaderLocalized and alertDescriptionLocalized fields.
Note:
for EC Alerts and Notifications you can only use the following tags:
Subject user in the format [[SUBJECT_USER]]
Event reason in the format [[EVENT_REASON]]
Effective date in the format [[EFFECTIVE_DATE]]
2 Configure Alert Workflow
Within the Alert Workflow (Manage Organization, Pay and Job Structures) you can configure which users get
the alert and which users the notification:
 The Cc users receive an email notification

 The workflow step approvers receive an alert on their To-Do list (Take Action)
Note:
If you assign only workflow step approvers to a workflow only To-Do items (Take Action) are triggered as
alerts. If you only assign Cc users to a workflow only email notification are sent. For EC Alerts the
Contributor assignment in a workflow has no effect and is not needed.
3 Alert Business Rule
In a specific Business Rule you define by which criteria (e.g. 30 days before Probation Period ends) the Alert
and Notification message should be triggered. And which Alert Workflow is assigned to the rule and which
users will receive an email notification or alert in their To-Do list (Take Action).
In our example we used the as a base object as the Probation Period End Date is configured under Job
Information. Make sure you add the Alert object as an additional object to your Probation End Period Warning
Business Rule. Furthermore you have to set this Business Rule on saveAlert in the Job Information portlet in
your Succession Data Model. As well you have to configure a recurring Scheduled Job in Provisioning for EC
Alerts and Notifications.
Note:
EC Alerts can be used within the following portlets:
Compensation
Employment Information
Global Assignments
Job Information
Non-Recurring Pay Component
Recurring Pay Component
Work Permit
Time Off

Ref Link: - https://www.cloudhr.org/employee-central-alerts-notifications/

Concurrent Employment:-

Concurrent employment details.

Step1- provisioning

Step2- RBP-Manage Permission Role- System Admin- Permission- Employee details- New assignment (search)- view
and edit. Click.

Step3 now u can do change on any position.

Global assignment

Step1 provisioning

Step2- RBP-management permission role- system admin- permission- employee details- global assinment- view
and edit.

Step3 u can change any position.

Data management- data retention management, purge request monitor.

Meta data- step1 provisioning -click on generic obj- serach for mdf- 25,50,75 mdf object creation- choose field
according to your scenario.

Step2- rbp-managme role based permission- sytem admin- permission- meta data frame work- select all- done.
Step3- configure obj definition- obj definition (all are the generic obj)- create- fill all required details.

Step4- Manage confi ui- create- id- (emp_training)- base details- object definition id.

Step5- grant view- RBP- manage permission role- system admin- permission- misc permission- (emp_training) click
to enable- done.

Step6 employee files- configure emp data- new view- dash board- insert portlet- add and create.

Business Configuration UI :- BCUI & Manage Business Configurations

The Business Configuration UI (BCUI) under “Admin Tools>Company Settings>Manage

Business Configuration” allows administrators to maintain certain aspects(common tasks) of
Succession Data Model directly from Admin Tools with a user friendly screens instead of using
data models(i.e XML tags and properties).

Though the number of things that can be done using BCUI are limited,
there are some pretty decent options that would let “Administrators” do
without depending on SF Experts who have access to Provisioning. The
following scenarios can be handled using BCUI –

 Changing Labels of fields under various portlets

 Adding new translations or Changing existing translations of fields
under various portlets
 Adding custom fields
 Changing the display sequence of the fields
  Changing properties of fields(like making fields as editable or read-
only;) activating/enabling unused fields, making fields
mandatory/non-mandatory, attaching picklists to the fields, setting
maximum length of the fields, setting “Allow import” flag to the
fields, etc)
 Adding “HRIS Sync Mapping” to the fields(Note: There are certain
limitations which would be discussed in the later part of this blog)
 Adding “Trigger Rules” to the fields and person objects(HRIS
Elements in XML – Portlets in plain language e.g. Compensation
Information, Employment Information, etc)

Limitations –
1. BCUI is really a smart way to configure screens, in other words, BCUI
is a better way to configure “Data Models” instead of using XML
configuration (which seems to be like more of a technical approach than
a user-friendly approach).As said in the introduction, the BCUI only lets us
maintain Succession Data Model and Employee Profile; this tool currently
doesn’t support “Corporate Data Model” or other data models, which to
me is a big gap. I wish to use this Easy to use Screens (In near future SAP
may migrate the existing corporate data model objects to MDF Objects
[as it did for Cost Center recently], but still want all corporate data model
objects [like Legal Entity, Business Unit, Division, Location, Department,
etc] to be listed under the “Employee Profile” node) to configure all kinds
of data models without opening XML files any more. If SAP-SF migrates
completely to BCUI for configuration activity, there would be no headache
of maintaining versions of XML files any more. Especially if you were
making minor changes to the screen.
2. BCUI still doesn’t support certain XML Tags like “<format-group>”,
“format”, “display-format” which can be done with ease using XML –

Though this is not a common scenario (where we add these kinds of data
validations using XML Tags), I am definitely looking ahead for SAP-SF to
introduce some kind of provision in BCUI to support these kind of unique
XML Tags (either by extending by introducing few additional fields in the
“Details” pop-up of the fields or by allowing us to maintain few XML tags
manually using BCUI).
3. Though BCUI supports HRIS Sync to the HRIS fields that transports
data from Employee Central to Employee profile, BCUI doesn’t support
HRIS Sync mapping for Country specific fields of Succession Data Model.
We would still have to rely on country specific succession data model
(XML file based configuration) to achieve this mapping. I would expect to
extend BCUI to support this missing functionality.
4. Userinfo-element aka User Info fields are user-defined fields in
Employee Profile. BCUI currently doesn’t support HRIS Sync mapping of
HRIS fields to
these User Info fields. We should still rely on traditional XML
configuration to achieve this HRIS Sync mapping –
5. There could be a possible conflict between BCUI and XML
Configuration. Let’s say, we enable BCUI using provisioning and we made
the changes as
shown below –
Day 1: Download Succession data model
Day 2: Activate BCUI framework in provisioning
Day 3: Made couple of changes to “Employment Information” using BCUI.
Day 4: Upload Succession data model that was downloaded on Day 1
Result: You lose changes done on Day 3 using BCUI.
Not sure if I could call this point as a limitation, but it could create a
possible conflict if one is not careful with the changes done using BCUI
and upload/download process of XML Data models. I would heed the
wonderful advice that was mentioned in the Implementation guide –
 MASS CHANGE – change a particular value of any field or object

1. Tool search -> Manage Mass Change

2. Create new

Mass Changes is a tool for HR Administrators to manage changes to employees' job information
and job relationships for any user-defined selection of employees. It allows users to efficiently
execute changes to employees' attributes due to manager reassignments, or reorganizations
affecting large numbers of employees. Example: The HR Manager responsible for 40 employees
is replaced by another person. All engineers decentralized in several departments are being
centralized in a newly created unit.

The user defines a mass change in a screen consisting of:

● An employee selection using a group definition tool similar to the one that are used for
permissions.
● The effective date that determines when the determined changes should take effect.
● The list of fields to be changed, including their new value.
The mass change definition can then be saved and initiated immediately or saved and initiated
later. Initiating a mass change creates a background job that is scheduled for immediate
execution. After mass change has run, a new status is set, dependent on the result. In the event
of errors, the user can access a log to analyze the changes that failed.

1. Provisioning - Company Settings

Select Enable Generic Objects

2. Admin – Permission to Generic Objects

Grant permission to Manage Generic Objects to Admin user.

Goto Admin Tools  Role Based permission  Manage Permission Roles.

3. Role Based Permissions for Mass Changes

Grant permission to Manage Mass Changes to Admin user in Role Based Permissions Framework.

From Admin Tools Select Manage Mass Changes::

 sick

Select Create New

Create or Select an Employee Group.

For Job Information changes, Event Reason has to be defined in the Mass Change definition

How to create a Custom MDF Portlet in the Employee/People Profile

Ref Link: - https://apps.support.sap.com/sap/support/knowledge/en/2208066

Resolution
 Custom Portlet UI for displaying the data from the MDF Object can be
created using the Manage Configuration UI tool in Meta Data Framework
 To add the custom MDF Portlet in the Profile section, follow the steps
below:

For People Profile Page (PP3) Instances

1. Navigate to Admin Center > Tool Search > Configure People Profile
2. In the Search area for Available blocks, look for "Live Profile MDF
Information" block. (It should appear if you search "mdf")
3. Drag and drop the porltet into the desired available space as shown in
below screenshot

4. Select the UI screen Id and click on Save button as shown in screenshot

below:

5. Once the above steps are completed, the portlet will start to appear on the
Profile Page. If the custom block is not part of a standard portlet, normal
RBP behavior applies.

For Employee Profile, v12 Instances

1. Navigate to Admin Center > Employee Files > Configure Employee Files:

2. If you wish to add the MDF UI Portlet in the new layout in the Employee
Profile section, click on Add New View OR if you wish to add the MDF UI
Portlet in the existing editable layouts choose from the list available.

3. Click on Insert Portlet and click on Create & Add button for the Live
Profile MDF Information

4. Give a title to the portlet and select the MDF Screen ID of the required
MDF Object and click on Save and then Save Dashboard. This is the ID
that was given in the Manage Configuration UI page.
 5. Once the above settings are completed, grant access to the newly created
MDF Portlet UI by enabling the checkbox for the newly created Employee
Layout in Manage Permission Roles > Permission > Employee Views

Note: Live Profile MDF Portlet in Employee Profile Section can be created only
for Objects that have externalCode set as User data type, otherwise you will
not get the option to select the Screen ID in the screenshot above.

2152252 - How to configure MDF portlets in Employee Profile

1. Why was this feature created?

This feature was created to support the growing extensibility needs of our
customers. Customers will leverage the MDF platform to extend objects and
create applications beyond what the core BizX platform offers. In many cases,
these objects are user centric. As customers use BizX as their core HRIS
platform and main hub for information it becomes increasingly important that
employees are able to view this information within Employee Profile.

2. What does this feature do?

This feature allows administrators to add MDF Generic objects (with a primary
key of userid) to be a portlet in the Employee Profile.

3. What are the perquisites?

The customer must have the following enabled:

1) V12 UI

2) V12 Profile

3) Enable Generic Objects

4. How does it work?

This feature works in 2 parts. First, you’ll have to setup an MDF object.

4.1 Setting up an MDF Object

Create an object in “Configure Object Definitions”

On the right hand side, click in the “Create New” input field and select Object
Definition. Keep in mind that the Employee Profile will only pull in MDF Object
Definitions that have an ExternalCode of DataType=User.

Once you have an Object Definition , you will create a View in the Manage Config
UI. Link the object you just created.

After creating the Object Definition and View, you can create an instance for
that object. This can be done in Manage Data

5.2 Configure Employee Files

Once the MDF UI is setup, you can add this portlet to the Profile, Scorecard or
Custom View.

After navigating to Configure Employee Files, click on Add Portlet within User
Element

Click on Create & Add for MDF Object

Add in the details and select the configurable UI you would like to pull from.
Keep in mind that the dropdown list will only show those with an externalcode of
datatype=USER.

5.3 Permissions

The Employee Profile will follow the RBP permission scheme that is set for the
MDF Object.

5.4 Employee Profile View

Ref Link: - https://apps.support.sap.com/sap/support/knowledge/en/2152252

2285593 - Adding an Association from Custom Foundation Object to a Legacy Foundation
Object (GO to FO) - Employee Central
To be able to associate a Generic Object (Child) with a Legacy Foundation
Object (Parent) you will need to create an MDF Wrapper object, and use that as
your association on the Custom Foundation Object (GO). Please follow the steps
below to accomplish this.

The following actions do not require a Support Incident, and can be executed by
an Admin User. A few things to remember here before getting started -:

1. Start Simple! Try not to do everything at once on your 1st try. Keep it
simple, get the basic configuration working, and then work to expand to
the more complex scenarios.
2. Always start in your Test/Sandbox instance - never start in a
QA/Production instance.
3. Ensure that you follow the below steps and create your working object
first, before trying any custom configurations, as it is much simpler to get
the basic object working and then build up to the intended configuration
instead of doing it all in 1 step (as mistakes can be made which could lead
to errors/inconsistent behaviours).

You will need the following Administrative Permission to access the following
Admin Center UI's to complete this task -:

 Configure Object Definitions

 Manage Data
 Manage Business Configuration

Example Association Configuration - Room Number (Child) to

Location (Parent)

1) We assume that the "Room / Floor Number" Custom Foundation Object (GO)
has already been created and added to Job Information configuration as well as
permissioned correctly in RBP. (Please refer to article 2285199 which is tagged
in the References section at the bottom of this KBA, which details how to create
a Custom Foundation Object)

2) To add an association from a Custom foundation Object (Child) to a Legacy

Foundation Object (Parent), you will need to utilize one of the pre-delivered
Wrapper objects, which are needed to associate a GO (Child) with FO (Parent). In
our case we are associating to Location, so we will use the pre-delivered
"Location Wrapper (FOWLocation)" -:
3) We assign this Wrapper object as the Association on our Custom Foundation
Object (GO/Generic Object), with the following criteria and then Save the
change. Make sure to note down the Association Name for use in a later step!
(cust_toLocation) -:

 Association Name = Call it something sensible - such as toLocation

 Multiplicity = One to Many
 Destination Object = Location Wrapper
 Type = Composite

'

4) Next we need to add the Field Criteria information to the "Floor / Room
Number" field to ensure the values are correctly filtered based on the Location
selection. Please navigate to Admin Center > Manage Business Configuration.
Select jobInfo element and Take Action > Make Correction. Find the custom-
string field that the "Room / Floor Number" Custom Foundation Object (GO) has
been assigned to and click "Details".

 Destination Field Value = location (Field Identifier for Parent field in

Job Information)
 Source Field Name = cust_toLocation.externalCode (The reason we
use externalCode here is because in the Wrapper object, the
"externalCode" field is set as type "Foundation Object"

5) Once the Field Criteria has been set, click Finished and Save.

6) Next you need to go to Admin Center > Manage Data and create some values
for your Custom Foundation Object including specifying their associated
Location value -:

7) Once completed, navigate to My Employee Files > Search for a Test user and
navigate to their Employment Information page. Final check to make is to ensure
your association is working correctly. You can use History > Insert New
Record/Make Correction for a quick test. Select a Department and then choose a
Sub Department option

8) Before deploying the same solution to a Production instance, please ensure

you test the changes thoroughly in a Test instance. Meaning; ensure the
filtering/Value Help works in all available UI's (History, MSS UI, etc). Make sure
that when assigning permission that the relative roles have access to view/edit
data in this field. And verify any workflows triggered off of changing this field are
triggered accordingly.

Ref Link: - https://apps.support.sap.com/sap/support/knowledge/en/2285593

THR081 2011. Sap Certified Application Associate SAP SF EC 2h/2020

Visit: - SAP Test Center

Syllabus you need to focus:-

 Explain Employee Central Core as an HRIS, including features and functions from both an end-
user and implementation viewpoint
 Manage user security using Role-Based Permissions (RBP)
 Implement Foundation Object Management
 Configure Employee Data
 Set up Advanced Foundation Object and Employee Data Management
 Update Self-Service and Workflows
 Customize Objects and Rule Management in the Instance
 Describe and setup Position Management
 Final Course Assessment

As per the Ref Link: - https://training.sap.com/certification/c_thr81_2011-sap-certified-application-

associate---sap-successfactors-employee-central-2h2020-g/
Module