You are on page 1of 46

First-hand knowledge.

Reading Sample
Employee Central manages the various employee events and Event Reasons that
can occur during the lifecycle of an employee. New hire, transfer, promotionthe-
se are just a few of the changes Employee Central can track. We will look at the
different events and Event Reasons within Employee Central, and the workflows
that can be put in place to automate the event management and approval process.

Events and Workflows

Contents

Index

The Authors

Luke Marson, Murali Mazhavanchery, Rebecca Murray


SAP SuccessFactors Employee Central
The Comprehensive Guide
590 Pages, 2016, $79.95/79.95
ISBN 978-1-4932-1218-7

www.sap-press.com/3834
2016 by Rheinwerk Publishing, Inc. This reading sample may be distributed free of charge. In no way must the file be altered, or
individual pages be removed. The use for any commercial purpose other than promoting the book is strictly prohibited.
Employee Central manages the various employee events that occur during
Chapter 4

the lifetime of an employee. Multiple reasons can be created for each


event. Coupled with workflows, this provides an automated way to man-
age events and have them approved in a robust process.

4 Events and Workflows

An employee will typically undergo several different events throughout his or her
lifetime at an employer. This process begins immediately with a Hire event, and
may include any number of other events, such as Transfers, Promotions, Pay
Changes, and Terminations. Employee Central manages each of these events and
provides customers with the ability to define multiple Event Reasons for each
event. These Event Reasons identify the specific reason that an event took place.

Although not always directly linked, events and workflows can work mutually to
enable approval of data changes created by an event prior to the event being com-
mitted to the employees record. These workflows typically arise in ESS and MSS
scenarios. Workflows ensure that employees and managers enter the correct data,
but alsomore importantlyenable compliance with decisions that may have
financial and legal implications.

In this chapter, well look at the events provided in the system and how Event
Reasons can be created and used. Well then take a look at workflows in detail,
covering the concepts and objects that enable workflows to operate, how and
where workflows are triggered, the workflow process, and general administrative
activities.

Before we examine events and Event Reasons, we should first briefly look at the
different employee statuses that employees can have.

4.1 Employee Status


Employees can have an employee status that identifies their active or inactive sta-
tus within the organization. Employee Central provides nine employee statuses:

107
4 Events and Workflows Employee Status 4.1

Active 4.1.1 Active versus Inactive


Unpaid Leave All employee statuses consider the employee still to be active within the organi-
Paid Leave zation, with the following exceptions:

Retired Retired
Suspended Terminated
Terminated Discarded
Furlough Furlough
Discarded When an employee has any of these four statuses, he or she is considered to be
Dormant inactive. If Employee Central is integrated with other systems, such as a payroll or
a benefits system, then the employee may become inactive in those systems as
The employee statuses provided in the system cannot be changed, but the label of
well when their status changes to one of these inactive employee statuses.
each Employee Status can be changed (e.g., Paid Leave could be renamed to Paid
Leave of Absence). Retired is used with the Pensions Payouts feature, which is covered in Chapter 16,
Section 16.5.
The Employee Status can be displayed in an employees Job Information portlet
and is also visible in the History screen of that portlet. The Employee Status field
is shown in the Job Information section in Figure 4.1. 4.1.2 Employee Status Changes
The employee status of an employee cannot be changed manually: It is always
changed by an Event Reason. Event Reasons can have an employee status
assigned, although it is not mandatory. When an event occurs for an employee
and an Event Reason is selected (either manually or automatically by the system
using an Event Derivation), then the employees status will change to the status
assigned to the Event Reason. If the Event Reason has no employee status
assigned, then the employees status will remain unchanged. Lets look at two
examples:

An employee with an Active status receives a salary increase using a customer-


specific Event Reason, called Annual Salary Increase. The Annual Salary Increase
Event Reason has no employee status assigned, because a salary increase doesnt
change the status of an employee. Therefore, the employees status remains as
Active. A few months later, the employee decides to leave the company, so an
administrator performs a termination in the system with a customer-specific
Event Reason called Resignation. The Resignation Event Reason has Terminated
assigned as the employee status. Therefore, the employee becomes inactive with
the status Terminated. We will look more closely at how employee statuses are
assigned to Event Reasons in Section 4.2.1.
Figure 4.1 Job Information Portlet

108 109
4 Events and Workflows Events and Event Reasons 4.2

Now that you are familiar with employee statuses, lets move onto looking at Event Code Use
events and Event Reasons. Suspension 7 Available for manual use
only
Termination 26 Termination
4.2 Events and Event Reasons Transfer 6 Job and/or position transfer
Add Global Assignment GA Global assignment
The system provides a standard set of events, and you cannot extend this set of
events. This set of events is provided as a picklist. You can modify the event labels End Global Assignment EGA Global assignment
for each enabled language, just as other picklist labels can be renamed. Periodi- Away on Global Assignment AGA Global assignment
cally, SAP SuccessFactors may introduce new events into the system. Back from Global Assign- BGA Global assignment
ment
Table 4.1 shows the standard picklist provided as of the Q4 2015 release.
Obsolete OGA Global assignment
Event Code Use Start Pension Payout SPP Pensions payouts
Additional Job 1 Defunct Discard Pension Payout OPP Pensions payouts
Assignment 2 Defunct End Pension Payout EPP Pensions payouts
Assignment Completion 3 Defunct Start Contingent Worker SCWK Contingent Workforce
Job Change 16 Change in job Management

Completion of Probation 15 Available for manual use End Contingent Worker ECWK Contingent Workforce
only Management

Data Change 5 Miscellaneous data change Table 4.1 List of Events (Cont.)
Demotion 4 Change in job
Furlough 11 Leave of absence Before you can use an event, it must have at least one Event Reason created; we
Hire H Hire/rehire will cover how to create Event Reasons in the next section. Typically, most pro-
cesses require the system to be configured to read the appropriate event and
Job Reclassification 9 Job reclassification
Event Reasons or for Event Reasons to be selected manually. In some instances,
Leave of Absence 10 Leave of absence
events exist that either need to be assigned manually by an HR administrator or
Pay Rate Change 12 Compensation change
are legacy events (those marked as Available for manual use only in Table 4.1).
Position Change 13 Change in position or posi-
tion reclassification The events and Event Reasons selected are stored in an employees history and
Probation 14 Available for manual use can be viewed by users with appropriate permissions to view the history of the
only Job Information or Compensation Information portlets. This can be seen in Fig-
Promotion 8 Change in job ure 4.2.

Rehire R Hire/rehire Typically, around half of Employee Central customers use Event Derivation in
Return From Disability 22 Leave of absence order to have the system automatically select the event and Event Reason based
Return to Work 23 Leave of absence on the action performed by the user. This can be extremely useful for customers
that use MSS, in which having the user select the correct Event Reasons has an
Table 4.1 List of Events

110 111
4 Events and Workflows Events and Event Reasons 4.2

impact on data integrity, triggering the correct workflow, and in some cases trig- will cover this process later in this section. Please note that at some time in the
gering integrations to external systems. We will cover Event Derivation in Section future, Event Reasons will be moved onto the MDF and will then be managed in
4.2.2. Employee Files Manage Data. Figure 4.3 shows an example of an Event Reason
in the Manage Organization, Pay and Job Structures screen.

Figure 4.3 TransferDepartment Change Event Reason

SuccessFactors provides 178 Event Reasons that you can import into the sys-
tem, although these Event Reasons do not need to be uploaded if you wish to
Figure 4.2 Compensation Information History for Marcus Hoff start from scratch or you can only use a selected number of the provided Event
Reasons.
Customers can choose to have users manually select the event and Event Reason Table 4.2 provides a small selection of Events Reasons, their events, and the
instead when performing an action in the system. assigned employee status for some of the standard provided Event Reasons. As
Now, lets take a look at how Event Reasons are managed in Employee Central. we discussed in Section 4.1.2, not all Event Reasons have an employee status
assigned and this is reflected in the table.

4.2.1 Event Reasons Event Reason Event Employee Status


An Event Reason describes why an event has occurred. For example, Resignation Internal International Trans- Hire Active
may be the reason for which a Termination event has occurred. For every event fer

that occurs in the system, an Event Reason must be selected. As described in Sec- Loan from Parent Company Hire Active
tion 4.1.2, an Event Reason can also change the employee status of an employee. New Hire Hire Active

Although you cannot create events, you can create an infinite number of Event Family and Medical Leave Leave of Absence Unpaid Leave
Act
Reasons in the system. Event Reasons are Foundation Objects (we will cover
Foundation Objects in detail in Chapter 6) and are therefore created in OneAd- Long Term Disability Leave of Absence Unpaid Leave

min in Employee Files Manage Organization, Pay and Job Structures. We Table 4.2 List of Event Reasons

112 113
4 Events and Workflows Events and Event Reasons 4.2

Event Reason Event Employee Status The Termination action enables the user to select the appropriate Event Reason
from those created for the Termination event (see Figure 4.4).
Unpaid Maternity/Paternity Leave of Absence Unpaid Leave
Leave
Paid Maternity/Paternity Leave of Absence Paid Leave
Leave
Lump Sum Merit Increase Pay Rate Change
Merit Pay Rate Change
Promotion Pay Rate Change
Job Reclassification Pay Rate Change
Normal Retirement Termination Retired
Vol TerminationHealth Termination Terminated
Reasons
Inv Termination Termination Terminated
Insubordinate
Vol TerminationPersonal Termination Terminated
Inv Termination Non- Termination Terminated
Performance
TransferDepartment Transfer
Change
Reorganization Transfer

Table 4.2 List of Event Reasons (Cont.)


Figure 4.4 Event Reasons in the Termination Action

Event Reasons come into play whenever a change occurs in any fields in either
Event Reasons for the Termination events always link to the Job Information
the Job Information or Compensation Information portlets, or when certain
record and are viewable in the History screen of the Job Information portlet.
transactions run. Such changes can occur through using the Take Action option
The Event Reason for the Termination event also appears in the Employment
and selecting Change Job and Compensation Info (typically an MSS activity) or
Details portlet, as shown in Figure 4.5. The Event Reason for the Compensation
Termination, or by inserting a new record in the History screen of either the Job
Information will remain unchanged from the last change made prior to the termi-
Information portlet or the Compensation Information portlet (typically a HR
nation.
administrator activity). The New Hire and Rehire transactions also involve select-
ing Event Reasons. Now that weve looked at when Event Reasons are used, well examine at the pro-
cess of creating Event Reasons.
When a new employee is hired, the user can select any Event Reason created for
the Hire event. The same is true for a Rehire transaction and Event Reasons cre- As mentioned previously, Event Reasons are created in OneAdmin in Employee
ated for the Rehire event. Files Manage Organization, Pay and Job Structures. Remember, at some
point in the future Event Reason objects will migrate to the MDF, at which time

114 115
4 Events and Workflows Events and Event Reasons 4.2

they will be created in Employee Files Manage Data using a slightly different Event
process from the one that we will discuss here. The event for which the Event Reason is created.
Employee Status
The employee status of the employee after the event has occurred.
Follow-Up Activity in Position
For a Position Management-related Event Reason, this determines if a Position
Reclassification or Position Transfer action should occur.
Payroll Event
Used for integration to SAP ERP Payroll and Employee Central Payroll systems;
enables a Payroll Event from one of these systems to be replicated instead of
the event of the Event Reason.
Display in Internal Job History Portlet
Used to indicate if Job Information records using this Event Reason should
show on the Internal Job History portlet in the Employee Profile.

Event Reason ID, Status, and Event are mandatory fields. If you are not using
Event Derivation, then the Employee Status field must be left blank.

As a minimum, you should create Event Reasons for the following events:

Hire
Rehire
Figure 4.5 Employment Details Portlet for a Terminated Employee
Termination
Leave of Absence and Return to Work (if Leave of Absence is used)
To create a new Event Reason, select Event Reason from the list in the Create
New dropdown. Enter the start date in the Effective as of date field (typically Data Change
01/01/1900), and then enter values for the following remaining fields, which can
Once created, an Event Reason is available for use in the system. For Event Deri-
be seen in Figure 4.3:
vation, additional configuration is required, which we will cover in the next sec-
Event Reason ID tion of this chapter.
The Event Reason code.
Event Reasons can be restricted by country by creating an association between
Event Reason Name the Event Reason Foundation Object and the Country Generic Object. Once the
The name of the Event Reason. association exists, each Event Reason can be assigned to one or more countries.
Description The Event Reason will then only be available for employees of a company that has
An optional description of the Event Reason. the associated country assigned to it.
Status
Whether the Event Reason is Active or Inactive.

116 117
4 Events and Workflows Events and Event Reasons 4.2

4.2.2 Event Derivation When using workflow, the Event Reason will be shown in the Please confirm
Event Derivationtechnically known as the youCalc event rulesis a feature in your request box that displays once the Submit button is clicked (see Figure 4.7
Employee Central that enables the event and Event Reason to be derived auto- ahead).
matically within MSS depending on what field changes the user makes. This sig- Lets take a look at how this works in practice. In Figure 4.6, the user selected the
nificantly reduces user error, which can impact data accuracy and integrity, the Change Job and Compensation Info action for an employee and changed the
Job History portlet on the Employee Profile, and integrations triggered by the Department from Marketing to Alliances.
Event Reason.

Although Event Reasons are selected automatically with Event Derivations, any
user with the appropriate permissions can manually change them in the History
screen of the Job Information and Compensation Information portlets. Addition-
ally, during a Termination action the user must still manually select and Event
Reason for the Termination.

Event Derivation triggers when data changes via using the Take Action option
and selecting Change Job and Compensation Info. Any data changed in the Job
Information, Job Relationships, or Compensation Information portlets triggers
Event Derivation, although Event Reasons are not stored for changes to Job Rela-
tionships; they are merely cosmetic in nature when triggering a workflow.

Event Derivation is triggered by configurable rules. Until the Q2 2015 release, it


was only possible to configure Event Derivation in the rules XML file uploaded in
Provisioning. From the Q2 2015 release, customers have the option to have Event
Derivation rules configured and triggered using the Rules Engine. We cover the
Rules Engine in detail in Chapter 5, although we will look at configuring Event
Derivation with the Rules Engine a little later in this section.

Important!

Customers can use either XML-based rules or Rules Engine rules for Event Derivation; a
customer cannot use a combination of both. If a customer uses XML-based rules and
wishes to use the Rules Engine, that customer must have the new method enabled in Figure 4.6 Change of Department in an Employees Job Information
Provisioning and then recreate all Event Derivation trigger rules in the Rules Engine.
Next, the user scrolls to the bottom and clicks the Submit button. The workflow
Once a change has been submittedor if workflow is used, once the change has popup box (Please confirm your request) opens (Figure 4.7). In this box, you
been approved by the last approverthe change is made to the employee data can see the Event Reason for the change: TransferDepartment Change.
and the event and Event Reason are recorded against the change in the database. Subsequent workflow approval screens, like the screen shown in Figure 4.8, dis-
As mentioned previously, the event and Event Reason are then viewable in the play the Event Reason.
History screen of the relevant portlet.

118 119
4 Events and Workflows Events and Event Reasons 4.2

Configuring Event Derivation Rules


Event Derivation rules are configured in the Rules Engine, but some existing cus-
tomers may have their rules configured in the legacy method via the rules XML.
Customers may migrate to the Rules Engine-based Event Derivation at any time,
but must consider that this requires building all of the existing rules in the Rules
Engine manually.

Note

We will only cover configuring Event Derivation rules using the Rules Engine in this
chapter. An experienced implementation consultant should handle changes to XML-
based rules until you have migrated to Event Derivation using the Rules Engine.

Two steps are required to configure an Event Derivation rule:

1. Create a business rule that defines the Event Derivation trigger and the output
Event Reason.
Figure 4.7 Workflow Popup Box
2. Assign the business rule to the appropriate portlet (Job Information or Com-
pensation Information) on which it should trigger.

Lets run through these steps in detail. First, navigate to Employee Files Config-
ure Business Rules in OneAdmin to create the rule. Create a new business rule
for the specific portlet (e.g., Job Information). The IF conditions should stipulate
the trigger rules, whereas the THEN condition should set the wfConfig field to
equal the Event Reason you wish to apply.

Lets take a look at a rule example. In Figure 4.9, you can see a business rule that
sets the Event Reason field to TransferDepartment Change. The IF condition
is set to Department.Value is not equal to Department.Previous Value, so that
field will trigger whenever the Department field value is changed in an employees
Job Information.

Once created, a business rule must be assigned to either the Job Information port-
let or the Compensation Information portlet as an onSave event in OneAdmin via
Company Settings Manage Business Configuration.

Figure 4.10 shows our rule assigned to the Department field in Manage Busi-
Figure 4.8 Workflow Triggered for Change of Job Information Data ness Configuration.

Now that weve looked at how an Event Derivation works, well take a look at
enabling and then configuring Event Derivation.

120 121
4 Events and Workflows Workflows 4.3

Once the field is added, save your changes, and your Event Derivation trigger is
complete!

Additional Resources

For more information on configuring and using Event Derivation, refer to the section
Using MDF-Based Business Rules of the Employee Central Master handbook found at
http://help.sap.com/hr_ec.

Now that weve covered events and Event Reasons, lets turn our attention to
workflows.

4.3 Workflows
Figure 4.9 Department Transfer Event Derivation Rule
Whereas Event Reasons define the reason behind a particular action or event, work-
flows provide the mechanism to ensure that such actions, events, or employee mas-
ter data changes are adequately approved and auditable. Most organizations
including yoursuse some form of approval chain for certain actions or data
changes, and Employee Central has a robust framework to manage workflow
approvals. Refer back to Figure 4.8 for an example of a workflow in flight.

Workflows approvals have one or more approvers assigned, and the workflow
will route through each approver in order until the last approver has approved
the workflow. At that point, the changes that are subject to the workflow become
visible in the system (future-dated changes will be visible in History but wont
become active until the effective date of the change is reached). We recommend
that you keep your workflows simple, rather than creating large approval chains.
The more workflows that have more approvers, the less likely it is for these work-
flows to receive approval as time goes on.

In addition to approvers, workflows can also have contributors and/or CC users.


Contributors have the ability to view a workflow and to add comments to the
workflow while it is active. CC users receive a notification upon the approval of a
workflow. For each of these groupsapprovers, contributors, and CC users
there are a number of different approver types available, which we will discuss
when look at the Workflow Configuration. These approver types enable the sys-
Figure 4.10 Assigning a Rule to a Field in Manage Business Configuration tem to derive the recipient of the workflow, such as the employees manager or
the employees HR manager.

122 123
4 Events and Workflows Workflows 4.3

Workflows can be triggered on Generic Objects, effective-dated Foundation Figure 4.11 shows the triggering of a workflow after making a change on the
Objects, the New Hire, Rehire, and Internal Hire transactions, changes made to Change Job and Compensation Info screen, accessed via the Take Action but-
portlets on the Employment Information screen using the Take Action menu ton on either the Personal Information or Employment Information screen.
(including Global Assignments), or by using the Edit button on the following By clicking the View Workflow Participants button, the user can see all of the
portlets on the Personal Information screen: approvers of the workflow before submitting it, as shown in Figure 4.11. The
user also can add a comment.
National ID Information
Personal Information (including Global Information fields) Workflows, like Event Reasons, are Foundation Objects and are configured in
OneAdmin in Employee Files Manage Organization, Pay and Job Structures.
Address Information
We will cover this process in Section 4.3.3. Workflow trigger rules are set up in
Payment Information the Rules Engine, although as with Event Derivation they used to be configured in
Dependents Information an XML rules file prior to the Q2 2015 update. We will cover this in Section 4.3.4.

The Biographical Information, Work Permit Information, Contact Informa-


tion, or Primary Emergency Contact portlets on the Personal Information 4.3.1 Approver Groups
screen do not support workflows. In this section, we will discuss the two approver groups used in workflows:
Workflows also will not trigger when inserting or correcting a record on the His- Dynamic Roles and Workflow Groups, and how they can be used to identify
tory screen of a portlet. approvers, contributors, and notified individuals.

Dynamic Roles
Dynamic Roles dynamically determine the recipient, contributor, or CC role of an
individual based on defined organizational attributes. For example, you may cre-
ate a Dynamic Role called Compensation Manager through which you define the
person responsible for approving compensation changes for each division. Figure
4.12 shows an example of a Dynamic Role.

The default attributes available for Dynamic Roles include the following:

Company
Business Unit
Division
Department
Location
Cost Center
Job Classification
Pay Grade
Figure 4.11 Workflow Confirmation Popup

124 125
4 Events and Workflows Workflows 4.3

Pay Group
Position

Figure 4.12 Compensation Manager Dynamic Role

You can add other Foundation Objects, such as Event Reasons and custom Foun-
Figure 4.13 Creating a Dynamic Role
dation Objects.

For each attribute or combination of attributes selected, an approver is selected For each of these attributes, define an approver type and approver. Here, we will
by approver type. There are three approver types: define a person for each attribute (see Figure 4.14).

Person
Position
Dynamic Group

You can only use Dynamic Roles in workflows used for Employee Central objects
and the Position object.

Dynamic Roles are Foundation Objects and therefore are created in OneAdmin in
Employee Files Manage Organization, Pay and Job Structures. Use the Create
New dropdown to create a new Dynamic Role, define the ID and name, and then se-
lect the various different attributes for each approver. In Figure 4.13, we created a
new Dynamic Role called Benefits Coordinator. Here, we will define different approv-
ers if the employees organization assignment matches the following attributes:

Division is Enterprises and Location is Arlington, Virginia


Division is Enterprises and Location is Atlanta
Division is Healthcare Figure 4.14 Assigning Approvers to Attributes in a Dynamic Role

126 127
4 Events and Workflows Workflows 4.3

Now, click Save, and the Dynamic Role is created; you can see the result in Figure
4.15.

Figure 4.15 Benefits Coordinator Dynamic Role

Now that weve looked at Dynamic Roles, lets take a look at Workflow Groups.

Workflow Groups
Workflow Groupsalso known as Dynamic Groupsare groups of individuals that
all receive a workflow simultaneously. All members of a Workflow Group have
Figure 4.16 Workflow Group for the US HR Analyst Team
the ability to approve the workflow, and the workflow will be available for
approval for all group members until the first group member approves it. Once
Now that weve looked at Dynamic Roles and Workflow Groups, its time to look
approved, the workflow is no longer available for approval by other group mem-
at the Workflow Configurations themselves.
bers. Figure 4.16 shows a Workflow Group.

You create Workflow Groups in the same way as Permission Groups, which we
4.3.2 Workflow Configurations
discussed in Chapter 3, Section 3.2.1. They use the same set of fields to include
and exclude members. Workflows are defined by Workflow Configurations, which are Foundation
Objects. Technically, a workflow is made up of several Foundation Objects:
Workflow Groups are also used for contributors and CC roles. For contributors,
all members in the group will be able to comment on a workflow until it is Workflow Configuration (wfConfig)
approved. For CC roles, all members of the group will receive notification of the Workflow Step Approver (wfStepApprover)
workflow approval. Contributor Type (wfConfigContributor)
To create a Workflow Group, go to OneAdmin and select Employee Files Man- CC Role Type (wfConfigCC)
age Workflow Groups. Click the Create Group button, enter the group name,
A Workflow Configuration is broken up into four sections, represented by the
and then select the inclusion and exclusion criteria as you would when creating a
objects just listed. These sections are as follows:
Permission Group. Click Done to save the group.

128 129
4 Events and Workflows Workflows 4.3

Workflow attributes Name


Approvers The name of the workflow.

Contributors Description
An optional description of the workflow.
CC roles
Remind in Days
Figure 4.17 shows a Workflow Configuration for a Promotion workflow. The number of days after which a reminder notification is sent to the current
approver of a workflow (a reminder is sent on a recurring basis based on the
value of the field). The Reminder in Days field is used if a reminder email
should be sent by the system to the current approver of the workflow after a
certain period if no action has been taken on the workflow. The value should
be the number of days after which an email reminder is sent. A reminder email
is sent every number of days until action is taken on the email. We will cover
this in more detail in Section 4.3.7.
Is Delegate Supported
Determines whether a user can set up a workflow to be manually delegated or to
be autodelegated in his or her To Do homepage tile. Is Delegate Supported is a
Boolean field that enables the Auto Delegation option and the Delegate option
for approvers of a workflow. We will cover this in more detail in Section 4.3.8.
Alternative Workflow
Defines the workflow to use if a future-dated transaction already exists. For
example, you are making a Job Information change for an employee on July 1,
2016. A Job Information change record already exists for August 1, 2016. In
this scenario, it is possible to trigger a different workflow so that alternative
approvers can approve the workflow. This could be desired so that HR admin-
Figure 4.17 Promotion Workflow Configuration
istrators can review the change before it is approved, so that no duplicates or
contradicting changes are made that are already in the future-dated record.
In the sections that follow, we will look at each of these workflow sections in
Redirect CC Users Workflow Approval Page
greater depth, including descriptions of both Foundation Object workflows and
Defines if CC users can access the workflow approval page or if they just get a
Generic Object workflows.
notification.

Workflow Attributes
Approvers
The attributes used to define a Workflow Configuration and its overall behavior
In this part of the Workflow Configuration, each approver step is defined. Every
(not approval flow) are as follows:
approver step must be approved before the workflow is approved. If the
ID workflow cannot derive an approver, then the step is skipped, and if no approv-
The unique identifier for the Workflow Configuration.

130 131
4 Events and Workflows Workflows 4.3

ers can be derived, then the workflow is automatically approved. For each If an Approver Role is set as an approval step in a workflow but no user is
approver step, there are several attributes to configure: assigned, then that step of the workflow will be skipped. For example, the
approval step will be skipped if Employee HR is set as the Approver Role in a
Approver Type
workflow but the employee who is the subject of the workflow doesnt have an
The type of approver selected. There are a number of approver types that deter-
mine how the approver should be selected or derived by the system. These HR manager assigned.
approver types are as follows: Context
Role: A specific Approver Role Determines whether this is the current Approver Type (Source) or future
Approver Type (Target); only triggers if the approver changes as part of the
Dynamic Role: An individual will be derived based on the criteria of the
Dynamic Role data changes that trigger the workflow. Use the Context field when the value
that is changed in the transaction is an Approver Role (excluding Self). There
Dynamic Group: A Workflow Group
are two options:
Position: The holder or holders will be selected
Source
Approver Role
Target
Dependent on the Approver Type. Use the Approver Role field to select the
value of the Role, Dynamic Role, Workflow Group, or Position once the For example, an employees manager changes. If the Approver Role field value
Approver Type is selected. When Dynamic Role, Workflow Group, or Posi- is Manager and the Context field value is Source, then the employees cur-
tion is selected in the Approver Type field, the Approver Role field values will rent manager is selected as the approver. If the Approver Role field value is
be a list of the respective objects. If Role is selected as the value of the Manager and the Context field value is Target, then the employees proposed
Approver Type field, then the Approver Role field will provide the following new manager is selected as the approver.
list of approver roles that are used to derive the approver based on the Edit Transaction
employee who is the subject of the workflow: Determines whether the approver can edit data that is part of the workflow
Self: The individual that initiated the request (Edit without Route Change), can edit the data and have the workflow
reroute all the way through the approver chain (Edit with Route Change), or
Manager: The manager of the employee
cannot edit any data (No Edit).
Managers Manager: The manager of the manager of the employee
Relationship to Approver
Employee HR: The HR manager of the employee (as defined in the Job Rela- Determines whether the Approver Type is related to the initiator of the work-
tionships portlet on the Employment Information screen) flow (Initiator) or the subject of the workflow (Employee).
Matrix Manager: The matrix manager of the employee (as defined in the No Approver Behavior
Job Relationships portlet on the Employment Information screen) What should happen if the workflow reaches an approver that cannot be
Custom Manager: The custom manager of the employee (as defined in the derived (e.g., a position with no incumbent, an employee has no manager, the
Job Relationships portlet on the Employment Information screen) employees manager has no manager, there is no HR manager assigned, etc.);
Second Manager: The second manager of the employee (as defined in the either the step is skipped (Skip this Step), or the workflow is cancelled (Stop
Job Relationships portlet on the Employment Information screen) the Workflow).

Additional Manager: The additional manager of the employee (as defined


in the Job Relationships portlet on the Employment Information screen)

132 133
4 Events and Workflows Workflows 4.3

Respect Permission Before we move onto the workflow creation process, lets take a look at Founda-
Determines whether RBP permissions are respected (Yes) or not (No) for the tion Object and Generic Object workflows.
user when viewing data in the workflow approval page.

Foundation Object and Generic Object Workflows


Contributors Foundation Object workflows have some limitations compared to workflows
As mentioned, contributors have the ability to comment on a workflow during used for Personal Information or Employment Information data changes.
the approval process. Once the workflow is approved, contributors are no longer
Workflows used for Foundation Objects only support Dynamic Group and Posi-
able to comment on it. Contributors have a similar but smaller list of fields as
tion as values for the Approver Type and Contributor Type fields. For CC users,
approvers:
the only values available for the CC Role Type fields are Dynamic Group, Posi-
Contributor Type tion, Person, and External Email.
Contributor You cannot edit or update active workflows. If the changes made by the initiator
Relationship to Approver are incorrect, then the workflow must be rejected and the correct changes made
Context by the initiator.

Respect Permission Workflows for Generic Objects do not support Dynamic Role as an Approver
Type, Contributor Type, or CC Role Type. However, there is an exception for a
The Contributor Type and Contributor fields correspond to the Approver Type
Position object.
and Approver Role fields. The Contributor Type field has the same values as the
Approver Type field, although for contributors there is an additional value avail- Next, we will look at an example while walking through the workflow creation
able: Person. This value enables you to select an individual employee in the Con- process.
tributor field.

4.3.3 Creating a Workflow


CC Roles
Now that weve reviewed the various options available when creating a work-
CC roles have an almost identical set of attributes as contributors: flow, lets take a moment to look at an example of creating a workflow in action.
CC Role Type For our example, lets create a workflow for an employee change of position. In
CC Role our workflow, we want four approvers: current HR representative, new HR rep-
Relationship to Approver resentative, new manager, and the new managers manager. We also want to
notify the current manager and notify the IT helpdesk via its shared email inbox.
Context
The workflow should also have a three-day reminder.
Respect Permission
First, lets define the attributes. These include the ID, name, and description of
Like with contributors, the CC Role Type and CC Role fields correspond to the our workflow and the reminder, delegation, alternative workflow, and CC user
Approver Type and Approver Role fields. The CC Role Type field has the same redirection page. With exception of the reminder, lets use the default values.
values as the Approver Type field, but also has the Person value as well as Figure 4.18 shows the attributes for our workflow, including the three-day
External Email. The External Email value enables a notification to be sent to reminder.
a specified email address once the workflow is approved.

134 135
4 Events and Workflows Workflows 4.3

In a similar process, define the CC users, which are the current manager and the
IT Helpdesk shared email inbox. Figure 4.20 shows the configured CC users.

Figure 4.20 CC Users in Workflow

Once youve finished the configuration, click the Save button to save the work-
flow. Figure 4.21 shows what our completed workflow looks like.

Figure 4.18 Attributes of Position Change Workflow

Next, lets define each of the approver steps. Add each step one by one, starting
with the employees current HR representative. For all approver steps, set the
Relationship to Employee field value to Employee and the Respect Permission
field value to Yes, but set different values for the Edit Transaction and No
Approver Behavior fields depending on the approver.

Figure 4.19 shows the four configured approver steps for each of the approvers
we want in our workflow: current HR representative, new HR representative,
new manager, and the new managers manager.

Figure 4.21 Finished Workflow Configuration

Figure 4.19 Approver Steps in Workflow Now that weve set up a workflow, its time to look at workflow triggers.

136 137
4 Events and Workflows Workflows 4.3

4.3.4 Creating and Assigning Workflow Triggers Well now look at the process of assigning workflows to trigger on different
No matter on which type of field or object the workflow is triggered, a business objects.
rule defines the trigger rule(s). The process is similar to creating business rules for
Event Derivation. The key difference when creating a business rule to trigger a Personal Information and Employment Information Triggers
workflow is that the THEN condition should always set the wfConfig field of the
Workflows triggered on changes to Personal Information portlets using the Edit
base object to be the workflow configuration that will be triggered (for a Model button or to Employment Information portlets using the Take Action menu
object, it should be wfConfig.Value). Figure 4.22 shows an example of this type (including Global Assignments and Pensions Payouts) use Workflow Derivation,
of business rule for an address change. the same process that is used for Event Derivation. As with Event Derivation,
workflows were triggered historically by creating rules in an XML file.

Important!

Just like with Event Derivation, customers can only use either the XML-based workflow
rules or the Rules Engine rulesnot a combination of both. If a customer currently uses
XML-based workflow rules and wishes to use the Rules Engine, the customer must have
the new method enabled in Provisioning and must then recreate all workflow trigger
rules in the Rules Engine.

Business rules created for Workflow Derivation are assigned the same way as
business rules created for Event Derivation, in OneAdmin in Company Settings
Manage Business Configuration. Assign these rules to the appropriate portlet
as required.

Many workflows trigger based on specific Event Reasons, so the IF conditions of


a business rule to trigger a workflow can reference an Event Reason, just like the
New Hire example seen in Figure 4.23. These business rules are assigned imme-
diately after the Event Derivation business rule on the Manage Business Config-
uration screen.

Figure 4.22 Workflow Trigger Rule Example New Hire and Rehire
Workflows for New Hire or Rehire are assigned to the Job Information portlet in
In order to compare new values to previous values for a field (i.e., identify if there OneAdmin in Company Settings Manage Business Configuration. A business
has been a change), use the model version of a base object. For example, to com- rule for triggering a workflow for New Hire or Rehire should use the Job Infor-
pare address fields to determine change, use the Address Model base object mation base object and have the IF conditions check if the Event Reason field is
instead of the Address base object. equal to any Event Reasons that you have configured in your system for hire or
rehire. Figure 4.23 shows an example of a New Hire workflow trigger.

138 139
4 Events and Workflows Workflows 4.3

Prior to clicking the Apply button, the Manage Parameters window should look
like Figure 4.24.

Figure 4.24 Parameters for Foundation Object Workflows

After completing the rest of the business rule information, configure the THEN
Figure 4.23 New Hire Workflow Trigger
condition to set the Workflow Configuration. Select Set in the first dropdown,
and click the + button next to the name you defined in step 4 in the second drop-
Foundation Object Triggers
down and select the field Workflow Information. Select the Workflow Config-
Foundation Objects can trigger workflows, whether traditional Foundation uration, and click the Save button. Your business rule will look similar to that
Objects or Foundation Objects that have been migrated to the MDF as Generic shown in Figure 4.25.
Objects. For Foundation Objects that have been migrated to the MDF, refer to the
following section on Generic Object triggers. In this section, we will focus on tra-
ditional Foundation Objects.

Workflows for Foundation Objects trigger whenever an object is created, modi-


fied, or deleted. It is not possible to trigger a workflow on just one of these
actions; a workflow will trigger on each of these actions as per the IF conditions
defined in the business rule.

Business rules created for Foundation Objects require adding a parameter in


order to define the workflow configuration. To do this when creating a new busi-
ness rule, follow these steps:

1. Select the base object in the Base Object field.


2. Click the Manage Parameters hyperlink.
3. In the Code column, enter the value FOWorkflow.
4. Enter a name in the Name column; this will be relevant later.
5. In the Object dropdown, select FO Workflow.
Figure 4.25 Business Rule for a Foundation Object Workflow
6. Click Apply.

140 141
4 Events and Workflows Workflows 4.3

Workflows for Foundation Objects must have the business rule assigned to the homepage and also in the Pending Request screen in Employee Files. Depending
object in the Corporate Data Model as an onSave event. An implementation con- on permissions, a user browsing the Personal Information or Employment
sultant typically performs this process. Information screens of an employee subject to a workflow may see a notifica-
tion in the portlet(s) on which the workflow was triggered. Well take a look at
each of these notification possibilities.
Generic Object Triggers
For Generic Objectsincluding Foundation Objects that have been migrated to the
MDF and Time Off objectscreate a business rule per the Personal Information or Email Notifications
Employment Information workflows and assign it to the Object Definition. Email notifications are sent out automatically for a variety of workflow-related
actions, including approvals, rejections, pending, comments, delegations, and
Assign business rules created to trigger workflows to the object definition under
more. Well cover all of these shortly. You cannot turn off email notifications for
Rules as a validateRules event. This might look like the example shown in Fig-
workflows.
ure 4.26.
Manage email notifications in OneAdmin in Company Settings E-Mail Notifi-
cation Templates Settings. There are fifteen email notification templates used
by the system, as described in Table 4.3.

Workflow Email Notification Template Scenario


Workflow Action Approval Notification Workflow requires approval
Workflow Action Rejected Notification Workflow has been rejected
Workflow Action Pending Notification Reminder for pending workflow
Workflow Action Cancelled Notification Workflow has been cancelled
Workflow Action Skipped Notification Workflow has been skipped
Workflow Comment Posted Notification Comment has been posted to workflow
Workflow Action Lock Down Notification Workflow has been locked down by an
administrator
Workflow Action Unlock Notification Workflow has been unlocked by an admin-
istrator
Workflow Action Contributor Notification Recipient is a contributor to a workflow
Figure 4.26 Business Rule Assigned to the MDF Object that has been submitted for approval
Workflow Action Cc Role Notification Notification that workflow has been
Chapter 5 covers assigning business rules to Generic Objects. approved
Workflow Step Approved Notification Workflow step has been approved
Workflow Sentback Notification Workflow has been sent back to initiator
4.3.5 Workflow Notifications
by an approver
Once a workflow is triggered, an approver is notified of the workflow by email.
In addition, the user can see the workflow listed in the To Do portlet on the Table 4.3 Workflow Email Notification Templates

142 143
4 Events and Workflows Workflows 4.3

Workflow Email Notification Template Scenario The email subject and email body are configurable for each enabled language. Fig-
ure 4.27 shows an example of the Workflow Action Approval Notification
Workflow Action Delegate Notification Workflow has been delegated
workflow email template.
Workflow Action Delegate Revoke Notifi- Workflow delegation has been revoked
cation As you can see in Figure 4.27, variable codes can insert dynamically determined
Workflow Action Delegate Decline Notifi- Workflow delegation has been declined by values into the email that the template generates. Table 4.4 lists common variable
cation the delegate codes used for workflow email notifications.

Table 4.3 Workflow Email Notification Templates (Cont.) Variable Code Definition
[[HRIS_ACTION]] Type of action
You can modify any email notification template, and can change the following
[[ACTION_TYPE]] Type of action for Foundation Object
attributes:
workflows
Priority [[EVENT]] Event for the action
Subject [[EVENT_REASON]] Event Reason for the action
Body [[EFFECTIVE_DATE]] Date that the data change/action will be
effective
[[VIEW_LINK]] Hyperlink to the workflow approval
page
[[SUBJECT_USER]] Employee who is the subject of the
workflow
[[SUBJECT_USER_ID]] User ID of the employee who is the sub-
ject of the workflow
[[PERSON_ID_EXTERNAL]] External ID of the employee who is the
subject of the workflow
[[SUBJECT_USER_LEGAL_ENTITY]] Legal Entity of the employee who is the
subject of the workflow
[[SUBJECT_USER_DEPARTMENT]] Department of the employee who is the
subject of the workflow
[[SUBJECT_USER_COSTCENTER]] Cost Center of the employee who is the
subject of the workflow
[[SUBJECT_USER_JOBCODE]] Job Code of the employee who is the
subject of the workflow
[[SUBJECT_USER_JOBTITLE]] Job Title of the employee who is the
subject of the workflow

Figure 4.27 Workflow Action Approval Notification Email Template [[RECIPIENT_NAME]] Recipient of the email

Table 4.4 Email Template Variable Codes

144 145
4 Events and Workflows Workflows 4.3

Variable Code Definition


[[CURRENT_OWNER]] Current approver of the workflow or the
user that rejected a workflow
[[APPROVAL_CHAIN]] Workflow approval chain up to the cur-
rent approver
[[CREATED_USER]] User who initiated the workflow
[[CREATED_USER_EMAIL]] Email of the user who initiated the
workflow
[[CREATED_TIME]] The date and time when the workflow
was initiated
[[RECENTLY_APPROVED_BY]] The most recent approver of the work-
flow
[[RECENTLY_APPROVED_BY_COMMENT]] Any comments by the most recent
approver of the workflow
[[RECENT_APPROVAL_DATE]] The date of the most recent approval of
the workflow
[[RECENT_COMMENT_POSTED]] The comment that was posted on a
workflow
[[RECENT_COMMENT_POSTED_BY]] User that posted a comment
[[RECENT_COMMENT_POSTED_DATE]] The date that the comment was posted Figure 4.28 Workflow Action Approval Notification Email
by the user
[[SENTBACK_BY]] User that sent back the workflow Now that weve looked at workflow notification emails, lets take a look at how
[[SENTBACK_BY_COMMENT]] Comments by the user that sent back workflow notifications appear in the system itself.
the workflow
[[REJECTED_BY]] User that rejected the workflow To Do Tile
[[REJECTED_BY_COMMENT]] Comments by the user that rejected the
The To Do tile on the homepage highlights a variety of outstanding tasks and
workflow
notifications for a user, including workflow notifications. All workflows that
[[DELEGATOR]] User who is delegating the workflow
require action by the user appear in the To Do tile with their due dates. Typically,
[[DELEGATEE]] User who has been delegated the work- the due date for workflows is TODAY. By selecting a workflow in the To Do tile,
flow
a user can view the workflow approval page. Figure 4.29 shows the To Do tile.
Table 4.4 Email Template Variable Codes (Cont.)

Figure 4.28 shows the email generated by the system for the Workflow Action
Approval Notification email template.

146 147
4 Events and Workflows Workflows 4.3

Figure 4.29 To Do Tile


Figure 4.30 Pending Requests Screen

Pending Requests Access the Workflow Approval screen by clicking the appropriate hyperlink.
The Pending Requests screen in the Employee Files menu provides workflow
approvers and initiatorsas well as contributors and individuals assigned as CC
Portlet Notifications
userswith the ability to view a variety of requests that they have submitted or
are part of. The Pending Requests screen is broken up into four portlets: If a user has the appropriate permissions, he or she will see a notification in a
portlet in the Personal Information or Employment Information screens on
Requests Waiting for My Approval which a workflow has been submitted. This looks like the example seen in Figure
Submitted workflows that require approval by the user 4.31. Once the workflow is approved, this notification will disappear.
Requests Still In Progress that I Approved
Active workflows that the user has approved
My Requests Waiting for Approval
Workflows that the user has submitted that are still active and waiting to be
approved
My Notifications Figure 4.31 Pending Workflow Notification in Job Information Portlet

Workflows for which the user is a CC user


Click the hyperlink to view the Workflow Approval screen.
Figure 4.30 shows the Pending Requests screen.

148 149
4 Events and Workflows Workflows 4.3

Now that weve covered how users are notified of workflow requests, lets take a Workflow Details
look at the approval process itself. Shows the data changes made that are being approved in the workflow (subject
to permissions, if configured).

4.3.6 Workflow Approval Process Comment


Allows the approver or contributor to add comments to the workflow, which
Once a workflow has been submitted and an approver notified, its time for the
will appear in the Activity log.
approver to approve the workflow. An approver accesses the workflow approval
screen from the hyperlink found in the email notification, To Do tile, or Pending Approval Options
Requests screen. The workflow approval screen usually looks like the screen Provides options for the approver to approve the workflow, cancel it or send it
shown in Figure 4.32. back to the initiator, delegate the workflow (if configured), or make changes to
the data being approved (if configured), or for the initiator to withdraw the
request. The approval options provide the approver with the ability to perform
a number of actions on the workflow, some of which depend on the settings
made on the Workflow Configuration covered in Section 4.3.2. These options
include the following:
Approve: Approves the workflow step
Send Back: Sends the workflow back to the initiator
Delegate: Allows the user to delegate the workflow to another user
Update: Allows the user to make changes to the data being approved
Withdraw: Only available for the initiator; enables the initiator to cancel
the workflow request
Activity
Displays a log of all activities on the workflow, such as comments, approvals,
and delegations.
User who is subject of the workflow
Shows a brief overview about the user who is the subject of the workflow.

Once the approver has approved the workflow, it will move to the next
approver in the approval chain. If the approver is the last approver in the
Figure 4.32 Workflow Approval Screen
approval chain, then the entire workflow is approved and the changes become
active in the system.
The screen contains six areas (listed counter-clockwise):
Now, lets take a look at setting reminders for workflows.
Workflow Overview
Lists the Event Reason/action, initiator, date of submission, effective date of the
action, and hyperlink to view the workflow participants.

150 151
4 Events and Workflows Workflows 4.3

4.3.7 Setting Reminders Manual delegation


Email reminders can be set up in the system by setting a value in the Remind in Auto delegation
Days field in the Workflow Configuration(s) for which you would like email
Enable both manual delegation and auto delegation for each workflow by setting
reminders to be sent. When set with a value (in days), the system will send an
the Is Delegate Supported field to Yes on the appropriate workflow configuration.
email reminder to the current approver of the workflow after the number of days
defined in this field if no action has been taken on the workflow. The system Lets look at each type of delegation.
determines action as activities such as adding a comment, changing an approver,
and approving the workflow.
Manual Delegation
The reminder email is sent again after the same number of days and will con- Manual delegation allows the delegator to manually delegate a workflow to a del-
tinue to be sent out the number of days specified until action is taken. For exam- egatee within the workflow approval screen by selecting the Delegate option at
ple, if the value of the Remind in Days field is set to 5, then a reminder email the bottom of the screen, as shown in Figure 4.32. The delegator selects the Del-
will be sent five days after the workflow has been received by the approver. A egate option and then selects the user to be the delegatee in the Delegate
reminder email will then be sent to the approver every five days until action is Request popup window, as shown in Figure 4.33. The delegator then clicks the
taken on the workflow. Send button and is asked to confirm the action by clicking the Delegate button.
The content of reminder emails are sent using the Workflow Action Pending Noti-
fication email template. If the workflow is sent back to the initiator and a reminder
is triggered, the system will use the Workflow Sentback Notification email notifi-
cation template. See Section 4.3.5 for details on workflow notifications.

In order to send reminder emails, a quartz job needs to be set up in Provisioning.


Note that a global value can be set on the quartz job that is effective for all work-
flows, irrespective of what is put into the Remind in Days field of any workflow.

4.3.8 Delegation
Delegation of workflows is possible, enabling another user (delegatee) to receive
and approve a workflow instead of the original approver (delegator). A delegatee
can reject the delegation and return the workflow back to the delegator. Once a
workflow has been delegated, it cannot be delegated further by the delegatee. If
a delegatee becomes inactive (i.e., he or she is terminated or retires), then the del-
egation will be cancelled and the delegator will become the approver of any
active workflows. Figure 4.33 Manually Delegating a Workflow

Delegated workflows appear in the delegates To Do tile and in the Pending


After the delegator clicks the Delegate button, the delegatee will be made the
Requests screen.
approver of this step of the workflow, and a notification will be sent that the del-
There are two types of delegation: egate has been delegated a workflow to approve. The email notification will use

152 153
4 Events and Workflows Workflows 4.3

the Workflow Action Delegate Notification template. See Section 4.3.5 for details
on workflow notifications.

Auto Delegation
Auto delegation automatically redirects an approvers workflows to a specified
delegatee. This could be useful for an executive delegating his or her workflows
to an executive assistant or a manager delegating workflows while on vacation,
for example. Auto delegation is effective for all workflow approvals required after
it has been enabled by the delegator and is not effective for existing workflows
that require approval by the delegator. Any active workflows need to be dele-
gated manually by the approver.

Set up auto delegation with the Auto Delegate option in the My Info Links part
of the My Info tile on the homepage (accessed by clicking the cog icon on the My
Info tile), as shown in Figure 4.34.

Figure 4.35 Configure Delegation of Workflows Popup

To cancel an auto delegation, select the Auto Delegate option in the My Info
Links part of the My Info tile on the homepage, uncheck the Delegate my
approvals checkbox, and then click the Save button.

Now that weve covered delegation, lets look at the workflow audit trail.

4.3.9 Workflow Audit Trail


You can view the workflow approval audit trail for data changes in the Address,
Personal Information, Job Information, Job Relationships, and Compensation
Information portlets by navigating to the History screen of the portlet, selecting
Figure 4.34 My Info Links Tile the appropriate record, clicking the Take Action button, and selecting the View
Approval History option. The View Approval History option only displays for
After selecting this option, the Configure Delegation of Workflows popup records approved by a workflow. Figure 4.36 shows the workflow approval
window opens, as shown in Figure 4.35. Here, the user should select the Dele- audit trail.
gate my approvals checkbox and then find the user who will be the delegatee for
all of the delegators workflows. Once complete, clicking the Save button will Now, lets look at administering workflows.
save the delegation.

154 155
4 Events and Workflows Workflows 4.3

or she wishes to view. Figure 4.37 shows the popup and all of the search criteria.
At least one search criteria must be selected, and any combination can be used.

Figure 4.36 Workflow Approval History

4.3.10 Administering Workflows


There are several options in OneAdmin to administer workflows and associated
configurations:

Manage Workflow Requests Figure 4.37 Workflow Search Criteria

Manage workflow requests with invalid approvers


The user can choose from the following search options:
Manage Workflow Groups
Requested By
Invalid User in Dynamic Role
Initiator of the workflow
Manage Organization, Pay and Job Structures
Requested For
Manage Data (for Auto Delegate Configuration) The employee who is the subject of the workflow
Lets briefly explore each of these options and their capabilities. Request Type
The Event Reason that was triggered

Manage Workflow Requests Request Status


The status of the workflow; choose from the following:
The Manage Workflow Requests transaction provides administrators with the
ability to administer active and inactive workflows in the system. It covers all Initialized: This is unused
workflows with a subject user (i.e., it does not show Foundation Object work- Pending: The workflow is pending approval
flows). Access it from the Employee Files menu in OneAdmin. First, the Manage Completed: Approved workflows
Workflow Requests transaction presents the user with the Search Workflow
Rejected: Rejected workflows
Requests popup, which enables the user to select the type of workflows that he

156 157
4 Events and Workflows Workflows 4.3

Cancelled: Cancelled workflows Actions


Locked: Locked workflows A list of actions to take on the workflow

Sentback: Workflows that have been sent back Stalled For Days
The number of days for which the workflow has been stalled (i.e., no action has
Effective Date From and Effective Date To
been taken)
Date that the changes become effective once approved
Requested Start Date and Requested End Date There are several actions available for each workflow. When you click the Take
Date the workflow was initiated Action button in the Action column, a menu of six options opens. When you
select an option, you will see a popup box in which to take the action. The six
If Pending or Sentback is selected for the Request Status, then a new field is dis- options are as follows:
played: Stalled for Days. This field allows the user to search for workflows that
Lock Down
have been stalled for a specific number of days. The value entered is the mini-
Lock down the workflow so it is no longer active
mum number of days for which a workflow has been stalled. For example, if you
enter 20 as the value, any workflows that have been stalled for twenty days or Add Another Approver
more will be displayed. Add an additional approver to the workflow
Change Approvers
Now, lets go through a quick example. If you wanted to search for all active
Change the current and any subsequent approvers
workflows that were pending approval, you would open the Request Status
dropdown, select Initialized, and click the Search button. Remove Approvers
Remove any approvers after the current approver (the current approver cannot
After you enter search criteria and click the Search button, you will see a list of be removed)
workflows that meet the criteria. Figure 4.38 shows a list of workflows that meet
Route Request
the example criteria.
Reroute the workflow to a future approver
Decline
Reject the workflow

Figure 4.39 shows an approver change in progress after selecting Change


Approvers.

Figure 4.38 Active Workflows in PENDING Status

The table of results has several columns, many of which are included in the search
criteria. View the workflow by clicking the hyperlinked value in the Request Type
column. There also are two columns to the right side of the table:

Figure 4.39 Changing a Workflow Approver

158 159
4 Events and Workflows Workflows 4.3

Manage Workflow Requests with Invalid Approvers


The Manage workflow requests with invalid approvers transaction located in
the Employee Files menu in OneAdmin provides the user with a list of workflows
that have an approver assigned who is no longer active in the system (i.e., the
user has been terminated). Figure 4.40 shows the list of workflows with invalid
approvers. Figure 4.41 Dynamic Roles with Invalid Users

Figure 4.40 Workflows with Invalid Approvers

The list looks similar to the list shown in Manage Workflow Requests. As in
that transaction, view the workflow by clicking the hyperlinked value in the
Request Type column. The list of actions in the Take Action menu are also the
Figure 4.42 Dynamic Role with Invalid Approvers
same. By using this menu, you can change the invalid approver or reroute the
workflow to the next approver in the chain.
Manage Organization, Pay, and Job Structures
Manage Workflow Configurations in the Manage Organization, Pay and Job
Manage Workflow Groups
Structures transaction is covered in Section 4.3.3.
Manage Workflow Groups in the Manage Workflow Groups transaction cov-
ered in Section 4.3.1.
Manage Data (Auto Delegate Configuration)
Configurations for each auto delegation can be viewed, modified, and deleted in
Invalid User in Dynamic Role
OneAdmin in Employee Files Manage Data. Select Auto Delegate Config as
The Invalid User in Dynamic Role transaction displays a list of all Dynamic the object type in the Search dropdown and a selectable list of users that have
Roles with an inactive user assigned as an approver. The transaction is located in enabled auto delegation will appear in the subsequent column. The list displays
the Employee Files menu in OneAdmin. users with both active and previous auto delegations.
The list (shown in Figure 4.41) has two columns, one that displays the Dynamic Once loaded, you can modify the Auto Delegation Configuration to add, mod-
Roles with invalid approvers and one that displays the invalid user(s) in the ify, or remove an auto delegation. Figure 4.43 shows an example of an auto del-
Dynamic Roles. egation enabled for Alexander Thompson.
Clicking on the hyperlink of the Dynamic Role opens it, as shown in Figure 4.42.
Here, the invalid approvers can be viewed and corrected.

160 161
4 Events and Workflows

Figure 4.43 Auto Delegate Config Object

Use the Take Action button to modify or delete an existing auto delegation. To
create a new auto delegation, select Auto Delegate Config in the Create New
dropdown, enter the necessary details, and click Save.

4.4 Summary
In this chapter, we examined employee status, events, Event Reasons, and work-
flows. We discussed how these concepts are used, when they are used, and how
they are configured. We also demonstrated how they support the different pro-
cesses in the system and enable employee history and approvals to be accurate
and logical.

In the next chapter, well take a deep dive into the extensibility options in
Employee Central and how you can leverage these to create new objects, screens,
and applications for your system.

162
Contents

Foreword ......................................................................................................... 17
Preface ............................................................................................................. 19
Introduction ..................................................................................................... 25

PART I Foundations

1 Employee Central Basics ........................................................... 35


1.1 Globalization and Localization ....................................................... 36
1.2 Data Models .................................................................................. 38
1.2.1 Succession Data Model .................................................... 39
1.2.2 Corporate Data Model ..................................................... 40
1.2.3 Country-Specific Succession Data Model .......................... 41
1.2.4 Country-Specific Corporate Data Model ........................... 41
1.3 OneAdmin ..................................................................................... 42
1.4 Foundation Objects ....................................................................... 42
1.4.1 Organizational Structures ................................................. 43
1.4.2 Job Structures .................................................................. 43
1.4.3 Pay Structures .................................................................. 44
1.4.4 Miscellaneous Foundation Objects ................................... 45
1.5 Employee Interface, Information, and Maintenance ....................... 46
1.5.1 Employee Profile .............................................................. 46
1.5.2 People Profile ................................................................... 47
1.5.3 Quickcard ........................................................................ 48
1.5.4 Employee Files ................................................................. 48
1.6 Transactions and Self-Services ....................................................... 49
1.7 Events and Workflows ................................................................... 50
1.8 Extensibility ................................................................................... 50
1.9 Business Configuration UI .............................................................. 52
1.10 HRIS Sync ...................................................................................... 53
1.11 Reporting ...................................................................................... 54
1.12 Deployment Models for SAP Customers ........................................ 54
1.13 Summary ....................................................................................... 57

2 Implementation Steps and Considerations .............................. 59


2.1 Implementation Considerations ..................................................... 59
2.1.1 Project Checklist .............................................................. 60

7
Contents Contents

2.1.2 Project Team Structure ..................................................... 61 4.3.2 Workflow Configurations .................................................. 129
2.1.3 Project Methodology ....................................................... 63 4.3.3 Creating a Workflow ........................................................ 135
2.1.4 Project Delivery ................................................................ 69 4.3.4 Creating and Assigning Workflow Triggers ........................ 138
2.1.5 Working with Third-Party Providers .................................. 70 4.3.5 Workflow Notifications .................................................... 142
2.2 Setting Up Employee Central ......................................................... 70 4.3.6 Workflow Approval Process ............................................. 150
2.2.1 Setup Checklist ................................................................. 70 4.3.7 Setting Reminders ............................................................ 152
2.2.2 Provisioning ..................................................................... 72 4.3.8 Delegation ....................................................................... 152
2.2.3 Admin Center ................................................................... 73 4.3.9 Workflow Audit Trail ........................................................ 155
2.3 Post-Implementation and Ongoing Administration ........................ 76 4.3.10 Administering Workflows ................................................. 156
2.3.1 SAP SuccessFactors Support ............................................. 77 4.4 Summary ....................................................................................... 162
2.3.2 Post-Implementation System Maintenance ....................... 78
2.4 Implementation Resources ............................................................ 78
5 Extensibility ............................................................................... 163
2.4.1 Customer Administrator Resources ................................... 79
2.4.2 Implementer Resources .................................................... 80 5.1 Metadata Framework .................................................................... 164
2.5 Summary ....................................................................................... 82 5.1.1 Creation Scenarios for Generic Objects ............................. 166
5.1.2 Parent and Child Associations .......................................... 168
3 Role-Based Permissions ............................................................ 83 5.1.3 Creating and Maintaining Object Definitions .................... 168
5.1.4 MDF Picklists ................................................................... 174
3.1 Overview ....................................................................................... 83 5.1.5 Creating a UI for Maintaining Generic Object Data ........... 177
3.1.1 Groups and Roles ............................................................. 84 5.1.6 Maintaining Generic Object Data ..................................... 182
3.1.2 Administrators .................................................................. 84 5.2 Business Rules ............................................................................... 184
3.2 Creating Groups and Roles ............................................................ 87 5.3 Extension Center ........................................................................... 189
3.2.1 Defining Groups ............................................................... 87 5.4 SAP HANA Cloud Platform ............................................................ 189
3.2.2 Creating Roles .................................................................. 90 5.5 Summary ....................................................................................... 192
3.2.3 Assigning Roles to Groups ................................................ 91
3.3 Permissions ................................................................................... 92
6 Foundation Objects ................................................................... 193
3.3.1 Common User Permissions ............................................... 93
3.3.2 Administrator Permissions ................................................ 103 6.1 Basics ............................................................................................ 193
3.4 Scenarios for Creating Roles ........................................................... 105 6.1.1 Structures and Key Terms ................................................. 194
3.5 Summary ....................................................................................... 106 6.1.2 Foundation Objects versus MDF Foundation Objects ....... 196
6.2 Categories ..................................................................................... 197
4 Events and Workflows .............................................................. 107 6.2.1 Organizational .................................................................. 198
6.2.2 Job ................................................................................... 199
4.1 Employee Status ............................................................................ 107 6.2.3 Pay ................................................................................... 200
4.1.1 Active versus Inactive ....................................................... 109 6.3 Associations and Propagation ........................................................ 203
4.1.2 Employee Status Changes ................................................. 109 6.3.1 Associations ..................................................................... 203
4.2 Events and Event Reasons .............................................................. 110 6.3.2 Propagation ..................................................................... 203
4.2.1 Event Reasons .................................................................. 112 6.4 Configuration ................................................................................ 205
4.2.2 Event Derivation .............................................................. 118 6.4.1 Corporate Data Models .................................................... 205
4.3 Workflows ..................................................................................... 123 6.4.2 Configuring MDF Foundation Objects and Object
4.3.1 Approver Groups .............................................................. 125 Definitions ....................................................................... 209

8 9
Contents Contents

6.5 Creating Foundation Object Data .................................................. 212 8.3.4 Making Mass Changes on Positions .................................. 290
6.5.1 Importing Templates ........................................................ 213 8.3.5 Maintaining Hierarchies ................................................... 292
6.5.2 Manual Creation .............................................................. 216 8.3.6 Maintaining the Stable Headcount Area ........................... 293
6.6 Extending Foundation Objects ....................................................... 220 8.3.7 Using Right to Return ....................................................... 294
6.7 Summary ....................................................................................... 221 8.4 Position Management in Other SAP SuccessFactors
Applications .................................................................................. 295
8.4.1 Using Positions in SAP SuccessFactors Succession &
7 Data Imports and Data Migration ............................................ 223
Development ................................................................... 295
7.1 Importing Data .............................................................................. 224 8.4.2 Creating Requisitions from Positions ................................ 296
7.1.1 Processes and Considerations ........................................... 224 8.4.3 Job Profiles and Positions ................................................. 296
7.1.2 Import Templates ............................................................. 232 8.5 Summary ....................................................................................... 297
7.1.3 Types ............................................................................... 235
7.1.4 Scheduling Imports .......................................................... 256 9 Employee Data .......................................................................... 299
7.1.5 Advanced Import Errors ................................................... 257
7.2 Exporting Data .............................................................................. 262 9.1 Views ............................................................................................ 299
7.2.1 Types ............................................................................... 262 9.1.1 Public Profile .................................................................... 303
7.2.2 Scheduling Exports ........................................................... 264 9.1.2 Personal Information ........................................................ 305
7.3 Data Migration from SAP ERP HCM ............................................... 265 9.1.3 Employment Information ................................................. 312
7.3.1 SAP ERP to Employee Central Data Migration 9.1.4 Other Views ..................................................................... 319
Rapid-Deployment Solution ............................................. 266 9.2 History and Audit Trail ................................................................... 321
7.3.2 Integration Add-On for SAP ERP and Employee Central ... 270 9.2.1 History within Employee Central ...................................... 321
7.4 Summary ....................................................................................... 271 9.2.2 Audit Trail ........................................................................ 323
9.3 Self-Services .................................................................................. 324
9.3.1 Employee Self-Services ..................................................... 325
PART II Features and Functionality 9.3.2 Manager Self-Services ...................................................... 327
9.4 Transactions .................................................................................. 330
8 Position Management ............................................................... 275 9.4.1 New Hire ......................................................................... 330
9.4.2 Transfers .......................................................................... 331
8.1 Implicit Position Management ....................................................... 276
9.4.3 Promotions ...................................................................... 331
8.2 Positions Overview ........................................................................ 277
9.4.4 Reclassification ................................................................. 331
8.2.1 Structure .......................................................................... 279
9.4.5 Job Changes ..................................................................... 332
8.2.2 Types ............................................................................... 280
9.4.6 Compensation Changes .................................................... 332
8.2.3 Position Org Chart ............................................................ 280
9.4.7 Leave of Absence ............................................................. 332
8.2.4 Position Entry Date and Time in Position .......................... 283
9.4.8 Terminations/Retire .......................................................... 333
8.2.5 Security ............................................................................ 283
9.5 Configuration ................................................................................ 333
8.2.6 Full-Time Equivalent ........................................................ 284
9.5.1 XML Data Models ............................................................ 334
8.2.7 Mass Positions ................................................................. 285
9.5.2 Data Model Structure ....................................................... 334
8.3 Setting Up Position Management .................................................. 286
9.5.3 Manage Business Configuration ........................................ 336
8.3.1 Filtering Positions ............................................................. 287
9.5.4 Best Practices and Considerations ..................................... 338
8.3.2 Synchronizing Positions and Incumbents .......................... 287
9.6 Summary ....................................................................................... 339
8.3.3 Transferring and Reclassifying Positions ............................ 289

10 11
Contents Contents

12.3 SAP Fieldglass Integration ............................................................. 399


10 Employee Time, Absences, and Benefits ................................... 341 12.4 Summary ....................................................................................... 400
10.1 Time Management Overview ......................................................... 341
10.1.1 Objects ............................................................................ 342 13 Mass Changes ........................................................................... 401
10.1.2 Profiles ............................................................................. 347
10.2 Payroll Time Sheet ......................................................................... 347 13.1 Employee Data Mass Changes ....................................................... 401
10.2.1 Composition ..................................................................... 348 13.1.1 Capabilities ...................................................................... 402
10.2.2 Setup ............................................................................... 349 13.1.2 Limitations ....................................................................... 402
10.2.3 Using Payroll Time Sheet .................................................. 350 13.2 Performing Mass Changes .............................................................. 403
10.3 Time Off ........................................................................................ 354 13.2.1 When to Use Mass Changes ............................................. 403
10.3.1 Setup ............................................................................... 354 13.2.2 Preparing to Use Mass Changes ........................................ 404
10.3.2 Features and Functions ..................................................... 358 13.3 Using Manage Mass Changes ......................................................... 406
10.3.3 User Groups ..................................................................... 362 13.3.1 Set Up Mass Change ........................................................ 406
10.4 Global Benefits .............................................................................. 370 13.3.2 Execute Mass Change ....................................................... 410
10.4.1 Types of Benefits .............................................................. 371 13.4 Summary ....................................................................................... 410
10.4.2 Setup ............................................................................... 372
10.4.3 Using Global Benefits ....................................................... 374
14 Advances and Deductions ......................................................... 411
10.5 Summary ....................................................................................... 378
14.1 Advances ....................................................................................... 411
14.1.1 Setting Up Eligibilities ...................................................... 412
11 Global Assignments .................................................................. 379
14.1.2 Requesting an Advance .................................................... 418
11.1 Setting Up Global Assignments ...................................................... 379 14.1.3 Viewing Advances ............................................................ 419
11.1.1 Provisioning ..................................................................... 380 14.1.4 Advances Objects ............................................................. 420
11.1.2 Picklist Values .................................................................. 380 14.1.5 Setting Up Advances ........................................................ 420
11.1.3 Events and Event Reasons ................................................ 380 14.2 Deductions .................................................................................... 423
11.1.4 Global Assignments Configuration .................................... 381 14.2.1 One-Time Deductions ...................................................... 424
11.1.5 Role-Based Permissions .................................................... 381 14.2.2 Recurring Deductions ....................................................... 425
11.1.6 Workflows, Alerts, and Notifications ................................ 383 14.2.3 Deductions Objects .......................................................... 426
11.2 Sending an Employee on a Global Assignment ............................... 383 14.2.4 Setting Up Deductions ..................................................... 427
11.3 Managing Home and Expatriate Global Assignments ..................... 386 14.3 Summary ....................................................................................... 430
11.4 Ending a Global Assignment .......................................................... 389
11.5 Using SAP SuccessFactors while on Global Assignment .................. 391
15 Employee Central Payroll .......................................................... 431
11.6 Summary ....................................................................................... 391
15.1 Overview ....................................................................................... 431
15.2 Processes ....................................................................................... 432
12 Contingent Workforce Management ........................................ 393
15.3 Access ........................................................................................... 433
12.1 Configuration ................................................................................ 394 15.4 Self-Service Transactions ................................................................ 434
12.1.1 Vendor and Work Order ................................................... 394 15.4.1 Employee Self-Services ..................................................... 434
12.1.2 Contingent Lifecycle ......................................................... 396 15.4.2 Manager Self-Services ...................................................... 435
12.1.3 Importing Contingent Workforce Information .................. 397 15.5 Payroll Control Center ................................................................... 437
12.2 Viewing a Contingent Worker ........................................................ 397 15.6 Summary ....................................................................................... 439

12 13
Contents Contents

18.3 Using SAP SuccessFactors Mobile .................................................. 484


16 Other Features and Functionality ............................................. 441 18.3.1 Employee Self-Services ..................................................... 485
16.1 Pay Scale Structure ........................................................................ 441 18.3.2 Manager Self-Services ...................................................... 488
16.2 Concurrent Employment ................................................................ 443 18.3.3 Time Off ........................................................................... 490
16.3 Document Generation ................................................................... 445 18.3.4 Other Features ................................................................. 493
16.3.1 Creating a Document Template ........................................ 446 18.4 Summary ....................................................................................... 494
16.3.2 Mapping Fields ................................................................ 448
16.3.3 Generating a Document ................................................... 449
16.4 Alternative Cost Distribution ......................................................... 451 PART III Integrating Employee Central with Other Systems
16.5 Pensions Payouts ........................................................................... 453
19 Integration ................................................................................. 497
16.6 Summary ....................................................................................... 455
19.1 Integration Overview ..................................................................... 498
17 Reporting ................................................................................... 457 19.1.1 Packaged Integrations ...................................................... 499
19.1.2 Integration Technology .................................................... 502
17.1 Report Components ...................................................................... 457 19.1.3 PI Pass Through ................................................................ 503
17.2 Reporting Methods ....................................................................... 459 19.2 Integration with SAP ..................................................................... 504
17.3 Legacy Ad Hoc Reporting .............................................................. 460 19.2.1 Integration Considerations ............................................... 505
17.4 Online Report Designer ................................................................. 461 19.2.2 Employee Data ................................................................. 507
17.4.1 Implementation ............................................................... 463 19.2.3 Organizational Data ......................................................... 513
17.4.2 Running Reports .............................................................. 464 19.2.4 Cost Center Data .............................................................. 518
17.5 Operational Data Store .................................................................. 464 19.2.5 Employee Central Payroll .................................................. 521
17.6 Employee Central Advanced Reporting .......................................... 465 19.2.6 SAP Identity Management ................................................ 527
17.6.1 Standard-Delivered Reports ............................................. 465 19.2.7 Side-by-Side ..................................................................... 530
17.6.2 Custom Reports ................................................................ 466 19.2.8 SAP Business ByDesign ..................................................... 534
17.7 Creating Reports ............................................................................ 468 19.3 Integration with Third-Party Solutions ........................................... 536
17.7.1 Creating a New Report ..................................................... 468 19.3.1 Time and Attendance ....................................................... 537
17.7.2 Adding a Component to a Report ..................................... 469 19.3.2 Benefits ............................................................................ 539
17.7.3 Creating a Component ..................................................... 470 19.3.3 Payroll BPO ...................................................................... 541
17.7.4 Setting Up a Pivot Query .................................................. 473 19.3.4 Microsoft Active Directory ............................................... 543
17.7.5 Completing a Report ........................................................ 474 19.3.5 IBM Kenexa Talent Management Suite ............................. 544
17.7.6 Sharing a Report ............................................................... 475 19.4 SAP SuccessFactors HCM Suite Integration .................................... 545
17.8 Scheduling Reports ........................................................................ 475 19.4.1 User Data File ................................................................. 546
17.8.1 Creating a Bundle ............................................................. 476 19.4.2 SAP SuccessFactors Compensation and Variable Pay ......... 546
17.8.2 Adding Items to a Bundle ................................................. 476 19.4.3 SAP SuccessFactors Recruiting .......................................... 547
17.8.3 Scheduling a Bundle ......................................................... 477 19.4.4 SAP SuccessFactors Onboarding ....................................... 548
17.9 Summary ....................................................................................... 478 19.4.5 SAP SuccessFactors Succession Planning ........................... 548
19.5 Integration Center ......................................................................... 549
19.6 External Event Framework ............................................................. 551
18 Mobile ....................................................................................... 479
19.7 Adapters ........................................................................................ 553
18.1 Enabling Features .......................................................................... 481 19.8 APIs .............................................................................................. 554
18.2 Activation and Deactivation ........................................................... 482 19.8.1 OData API ........................................................................ 555

14 15
Contents

19.8.2 Compound Employee API ................................................ 556


19.9 Standard Integration Templates ..................................................... 558
19.10 Employee Delta Export .................................................................. 560
19.11 Employee Central Payroll Integration ............................................. 561
19.11.1 BSI ................................................................................... 562
19.11.2 Web Services .................................................................... 563
19.12 Summary ....................................................................................... 563

Conclusion ....................................................................................................... 565


The Authors ..................................................................................................... 573
Index................................................................................................................. 575

16
Index

[OPERATOR], 241 Alternative workflow, 131


&&NO_OVERWRITE&&, 228 Amount posted, 359
Analytics, 327
Android devices, 480
A Annual salary, 200
AON Hewitt, 500, 539
Accruals, 358359 API, 164, 497, 554
parameters, 359 audit log, 556
rules, 359 dictionary, 556
Accumulation for advances, 420 option profile, 556
Action, 145 visibility, 169, 549
Active, 109 Apple iOS devices, 480
Ad hoc reporting, 54, 461 Approvals, 296
Adapters, 553 options, 151
Add Employment Details portlet, 443 Approvers, 123, 125, 131, 136
Add user, 86 invalid, 160
Address role, 132
formats, 36 types, 126, 132
portlet, 300, 307 Associations, 203, 208
Admin Alerts, 75 parent and child, 168
Admin Center, 70, 73, 196, 336 Asynchronous, 227
history, 73 Audit, 324
Admin Tools, 73 trail, 321, 323
Administrator, 62, 84 Auto-delegation, 153154
permissions, 103 configuration, 161
ADP GlobalView, 500, 541 Auto-recovery, 413
Advanced Reporting, 54, 433, 460, 465, 467 Auxiliary team members, 63
country-specific reports, 465
custom reports, 466
schematic, 466 B
standard reports, 465
Advances, 411, 415, 420 Badges, 393, 479, 486
objects, 420 BAdI, 271, 507
request, 418 EX_ECPAO_EMP_USYID_PRN_UNM_MAP,
rules, 417 532
setup, 420 ODTF_CC_REPLICAT_IDOCS_MODIFY, 521
type, 413 Bank transfer, 311
viewing, 419 basePayComponentGroup, 227
AdvancesInstallments, 420 Basic
Alerts, 383, 390 import, 246, 250
Allowances, 348, 371 organization chart, 281
Alternate address, 308 Beneficiaries, 247
Alternative Cost Distribution, 441, 451 Benefit, 165, 484
portlet, 452 claim, 376377

575
Index Index

Benefit (Cont.) Checklist, 60 Cost center, 43, 199, 451, 499 Data (Cont.)
coordinator, 126, 376 Checks, 311 field mapping, 520 migration, 66, 223, 265
enrollment, 372, 375 Claims portlet, 374, 377 integration prerequisites, 518 numbers, 472
entities, 372 Cloud, 27 integration process, 519 preparation, 270
programs, 371, 376 Cloud Learning Center, 79, 568 costCenterManager, 226 propagation, 257
types, 371 Column, 467 Country-specific behavior, 279 report, 269
Benefitfocus, 500, 539 Compa Ratio, 45, 285 Country-Specific Corporate Data Model, 41, SAP ERP HCM migration, 265
Benefits-in-kind, 371 Company, 198, 209, 287 71, 206, 208 text, 472
Biographical Information, 247 settings, 72, 191 Country-Specific Succession Data Model, 41, transform, 269
Blackberry devices, 480 system and logo settings, 230 71, 334 type, 171
Boolean, 171 trainers, 63 Create New Rule, 185 Data model, 38
fields, 234 Compensation, 44, 318, 467 Cross Application Time Sheet (CATS), 507 structure, 334
BSI, 562 changes, 332 CSV, 224, 503 types, 39
BSI eFormsFactory, 432, 562 manager, 125 file, 243 Decimal precision, 422
BSI TaxFactory SaaS, 432, 562 Compensation Information portlet, 112, 248, import templates, 233 Deductions, 44, 411, 416, 423
Bundle, 476 251, 317, 329, 454 Currency, 45 objects, 426
add items, 476 Components, 457 Current Benefits, 374 one time, 424, 429
schedule, 477 create, 470 Custom Pay Components, 429
Business new, 469 associations, 517 Pay Scale Structure, 430
attributes, 278 Compound Employee API (CE API), 554, 556 calculations, 462 permissions, 429
drivers, 27 entities, 557 fields, 208, 517 recurring, 425
email address, 94 Concatenation, 473 objects, 517 setup, 427
events, 276 Concurrent employment, 26, 441, 443 person, 166 user interface, 427
lead, 62 Conditional association, 279 Customer workflow, 429
objects, 166 Configuration, 66 resources, 79 Delegation, 151152
rules, 139140, 184, 221, 394 table, 166 team, 6162 types, 152
specialists/generalists, 62 Configuration UI, 177, 179, 240, 263 Customer Community, 79 Dell Boomi AtomSphere, 29, 270, 497, 499,
unit, 198 deductions, 427 Customer Welcome Kit, 69 502, 554, 558
Business Configuration UI (BCUI), 52, 336 Configure Deduction Screen IDs, 426, 429 Department, 43, 198, 203
screen, 336 Consolidated, 56 change, 119
Business Process Outsourcing (BPO), 541 Contact Information portlet, 124 D Dependencies, 241
Business Unit, 43, 225226 Context, 133 Dependents
Contingent worker, 393 Data consolidated, 249
add, 396 date, 472 management, 99, 454
C permissions, 396 date formats, 231 portlet, 311, 327
person model, 394 entry, 348, 351 Deployment models, 54
Calculated viewing, 397 export types, 262 Destination, 477
columns, 471472 Contingent Workforce Management, 393 extract and clean, 269 Direct
mapping, 448 configuration, 394 IF/THEN/ELSE, 472 deposit, 95, 254, 311
Calendar, 358 contingent lifecycle, 396 import, 223224 mapping, 448
Candidate Profile, 547 Event Reasons, 396 import characters, 231 Display order, 176
Category, 467 import employee data, 397 import order, 225 Distributed, 56
CC Contributors, 123, 128, 134 import processes, 224 Division, 43, 126, 198, 203, 226
attributes, 134 attributes, 134 import types, 235 Document Generation, 441, 445, 449
roles, 128, 134, 202 key fields, 230 Document template
type, 134
users, 123, 137 mapping, 270 creation, 446
Corporate Data Model, 40, 71, 142, 188, 203,
Change template, 407, 410 migrartion analysis, 268 fields, 447
205
Character set, 338 mapping fields, 448
structure, 206

576 577
Index Index

Dormant, 386 Employee Central (Cont.) Employee Files, 48, 125, 166, 300, 369, 386, externalCode, 170, 231
Draft Amendment, 352 globalization, 25 436, 448 externalName, 170, 359
Dynamic history, 321 Employee Profile, 46, 93 Extract-transform-load (ETL), 223
content, 445, 448 IBM Kenexa Talent Management Suite inte- Employee records, 325
group, 126, 283 gration, 544 update, 96, 329
role, 125, 127, 160, 202 import data, 271 Employee Self-Service (ESS), 26 F
role assignment, 46 integration, 497 Employee Time Valuation Result (ETVR), 346
integration add-on, 270 Employer benefits, 437 Facilities, 393
integration with SAP, 504 Employment, 39, 166, 467 Failed, 292
E Job Aids, 569 audit, 324 Field, 210
Microsoft Active Directory integration, 543 details, 245, 247, 252, 443 attributes, 171
Eclipse, 190 mobile, 479 objects, 39, 166 criteria, 172
Edit, 94 new features, 30 Employment Details portlet, 95, 115, 329 formatting, 462
ownership, 475 payroll BPO integrations, 541 import error, 259 labels, 338
transaction, 133, 136 portlets, 300 Employment Information portlet, 312 lengths, 505
EEO Information, 314 release cycle, 2930 triggers, 139 mapping, 266, 270, 448, 515, 532
Effective-dated, 169, 194, 242, 302, 408 SAP Fieldglass, 394 employmentInfo, 335, 396 File
entities, 98 SAP SuccessFactors HCM Suite integration, End Contingent Worker (ECWK), 396 encoding, 244
effectiveStartDate, 170 545 end-date, 233 encoding formats, 227
Eligibility, 412 setup, 70 Enrollments portlet, 374 Filters, 471
create, 413 setup checklist, 70 Enterprise support, 77 Financial Unit, 43
criteria, 422 third-party integration, 536 Enumeration field, 259 Flow layout, 180
for advances, 415, 419420 UI, 439 foField, 240
ESS, 105, 325, 433434, 439, 479, 485
optional fields, 414 Employee Central Payroll, 431, 499, 524, 537, foObjectID, 239
changes, 326
rules, 417 540 FoTranslation, 238
Event Calendar, 75
Email notifications, 143, 483 foType, 239
access, 433 Event Derivation, 111, 118, 254
Foundation Data, 195
attributes, 144 data migration, 267 rules, 121
import, 213, 215, 236, 238
variable code, 145 HR Administrators, 569 Event Reason, 50, 110, 112113, 119, 201,
load template, 213
Emergency Contacts portlet, 248, 310 integrations, 521, 561 402, 404
Foundation Object, 38, 42, 71, 193, 467
EmpJob, 555 Payroll Results Export, 525 field, 121
associations, 208
Employee processes, 432 objects, 237
benefits, 194
absences, 341 user access points, 433 Events, 50, 107, 110
Boolean field, 234
benefits, 341 Employee data, 68, 93, 299, 499 Executed, 292
categories, 197
global assignment, 383 best practices, 338 Execution Manager, 550 configuration, 205
groups, 407 configuration, 333 Export CSV import templates, 236
import and export, 256, 265 CSV import templates, 249 data, 262 custom, 166
records, 101 delta replication, 507 Employee Delta Export, 263 data, 42, 212
search, 493 export, 265 live profile, 265 data imports, 235
status, 107, 314, 380 field mapping, 508 scheduling, 264 existing entry, 217
time, 341 import, 245, 257 specify options, 262 extending, 220
Time Off, 362 import errors, 258 types, 262 import errors, 257
views, 101 integration, 507 Extensibility, 26, 50 importing templates, 213
Employee Central, 25 integration prerequisites, 507 Extension, 163, 189190 integration, 515
basic concepts, 35 integration process, 507 package, 190 job, 197, 199
benefits integration, 539 mass changes, 401 Extension Center, 189 Location, 195
configuration, 35 template rules, 250 Extensions Marketplace, 191 managing data, 216
enhancements, 31 Employee Delta Export, 54, 263, 560 External Event Framework, 551 manual creation, 216
functionality, 26 External ID, 145 mapping, 518

578 579
Index Index

Foundation Object (Cont.) Global assignments (Cont.) I Integration (Cont.)


miscellaneous, 45, 197 ending, 389 Employee Central to SAP ERP, 508
new entry, 216 ending manually, 390 IBM Kenexa Talent Management, 500, 544 employee data, 507
organizational structure, 198 expatriate, 386 ID, 207 Employee Delta Export, 560
pay, 197, 200 home, 386 If/Then/Else statements, 462 IBM Kenexa Talent Management Suite, 544
structure and terms, 194 module, 379 Immutable IDs, 264 Microsoft Active Directory, 543
template rules, 237 picklist values, 380 Implementation, 59 middleware, 500
templates, 78 setup, 379 considerations, 59 overview, 498
workflow action, 145 transaction screen, 383 consultant, 87 payroll BPO, 541
workflow triggers, 140 using SAP SuccessFactors, 391 project team leader, 61 SAP Fieldglass, 394, 399
workflows, 135, 141 workflows, alerts, notifications, 383 resources, 78 SAP SuccessFactors HCM Suite, 545
Foundation Tables, 195 Global Benefits, 244, 341, 370, 380 sequence, 70 technology, 502
fractionQuantity, 242 setup, 372 team, 6061, 64 templates, 558
Framework attributes, 278 usage, 374 third-party providers, 70 testing, 67
Frequency, 45, 225, 477 view, 372 Implementer resources, 80 third-party, 500, 536
Full Cloud HCM, 55, 499 Global Information, 41, 247 Import WorkForce Software EmpCenter, 537
Full days, 355 Global Job Catalog Exercise, 332 Integration Center, 75, 549550
advanced errors, 257
Full Purge, 214, 228, 244245, 247 Globalization, 36 Integration-Platform-as-a-Service (IPaaS), 502
attachments, 253
Full-time equivalent (FTE), 284 Go-live, 68 Intelligent services, 551
background, 247
Granted users, 91, 283 Interest type, 414
data, 224
Internal Release Readiness (IRR) Sessions and
Group, 84 errors, 258
Documents, 82
G define, 87 extended, 247
Internal restructuring, 402
definition, 87, 407 Foundation Data, 104
Introductory call, 60
Generic Object, 39, 49, 142, 164, 172, 188, type, 89 internal system error, 258
Is Delegate Supported, 131
196 live profile, 257
is_contingent_worker, 396
attachments, 242 processing time, 255
isPrimary, 260
attributes, 164 H scheduling, 256
Iteration, 66
Boolean field, 234 templates, 232
create, 166 Headcount, 285 translations, 104
create and maintain data, 182 Hide Old Value, 172 unknown error, 258
creating a UI, 177 Hierarchy, 231 Incremental Load, 214, 228, 244245, 254
J
CVS import templates, 241 adaptation settings, 293 Incumbent, 282 Job, 200
data, 240 Higher grades, 96 Infotypes, 267, 432 code, 145
data imports, 240 Hire details, 315 initializeRules, 173, 188 information, 118
export data, 263 History, 321 Initiation documentation, 60 relationship, 118
fields, 232 changes, 322 Innovation, 28 structures, 43, 161
Global Assignment configuration, 381 Holiday Calendar, 344, 347, 357, 362 InProgress, 292 title, 145
import data, 227 Home address, 41, 307, 326 Installment frequency, 413 Job Changes portlet, 332
import errors, 259 Host employment, 383, 388 Insurance, 371 Job Class portlet, 200
template rules, 242 HR Integration, 497 Job Classification portlet, 36, 200
triggers, 142 actions, 96 adapters, 553 Job Code Default Data (JCDD), 544
workflows, 135, 164 business drivers, 27 add-on for SAP ERP and SAP SuccessFactors Job Code porlet, 200
Geozone, 199, 208, 225 HR administrators Employee Central, 265 Job Function portlet, 200
Global Assignment Details portlet, 387 Time Off, 369 API, 554 Job History portlet, 247
Global assignments, 26, 95, 166, 247, 294, HRIS, 28 benefits, 539 Job Information portlet, 37, 52, 108, 251,
379, 443 elements, 40, 196, 206, 217, 266, 335 considerations, 505 313314, 328, 402, 404
details, 384 field, 196, 207 Employee Central and SAP, 504 import error, 259
edit, 389 HRIS Sync, 53, 257 Employee Central Payroll, 561 sections, 314

580 581
Index Index

Job Market Category, 220 Manage (Cont.) Metadata Framework (MDF), 3940, 104, NGA Payroll Exchange, 500, 541
Job Profile Builder, 44 Foundation Objects, 104 163164, 188, 190, 396 mapping, 541
Job profiles, 296 integration tools, 104 data import, 257 Non-Recurring Payment, 420
Job Relationships portlet, 261, 316, 402, 404, permission groups and roles, 85 employee and benefits, 341 Notifications, 383, 390
409 user, 103 Foundation Object, 196, 203, 209, 219
workflow requests, 156 Pay Scale Structure, 442
Manage Global Assignment Details portlet, Picklists, 174, 234 O
K 385 Position Management, 275
Manage Mass Changes, 78, 104, 401402 screen ID, 181 Object Definition, 164165, 240, 423
Kick-off meeting, 60, 63, 65 capabilities, 402 Microsoft Active Directory, 500, 543 configuration, 209
KPI, 438 RBP settings, 405 Microsoft Excel, 263, 561 configure, 104
Kronos Widget, 538 run, 410 Middleware, 497 create and maintain, 168
Kronos Workforce Central, 500, 537 scenarios, 404 limitations, 505 modifying, 211
Kronos Workforce Ready, 538 setup, 406 Miscellaneous permissions, 102 Object references and associations, 232
usage, 406 Mobile, 27, 479 OData API, 190, 554555
Manage Pending Hires, 103 device management, 482 On-call duty, 348
L Manage Time Off, 320 features, 482 onChange, 51, 289
Manager Self-Service (MSS), 26 options, 484 On-device support, 482
label, 206 Managers manager, 132 security, 482 One Time Deduction User portlet, 425426
Language-dependent name fields, 516 Manual delegation, 153 team, 489 OneAdmin, 30, 42, 73, 115, 225, 278, 380
Launch phase, 68 Mapping, 270 user permissions, 483 applications, 74
tasks, 68 statement, 212 workflow approval, 490 document template, 446
Lead technical consultant, 62 tables, 505 Monitor jobs, 227 mobile, 481
Leave of absence, 95, 294, 327, 329, 332, Mash-ups, 432 MSS, 90, 105, 325, 327328, 401, 433435, Success Store, 427
360361 Mass 480, 488 workflow administration, 156
Legacy Ad Hoc Reporting, 459460, 468 change, 291 Multiplicity, 173 OnEdit, 188
Legacy picklists, 234 job, 404 Multi-tenant, 25 One-time deduction, 424, 426
Legal Entity, 36, 43, 145, 198, 232, 414 positions, 285 My Info Links tile, 154 OneTimeDeductionItem, 426
Licensing, 29 Mass changes, 26, 358, 401, 408 My Meetings, 486 OneTimeDeductionReplication, 426
LinkedIn, 569 area, 409 My Notifications, 148 One-to-Many, 173
Lists, 457 definitions, 405 My Profile tile, 485 One-to-One, 173
Localization, 27, 36 field name, 409 My Requests Waiting for Approval, 148 Ongoing administration, 76
Location, 199, 204 limitations, 402 My Team tile, 368 onInit, 51, 188
change, 409 name, 407 Online Report Designer (ORD), 54, 459, 463,
locationGroup, 199, 206 new value, 409 465, 468, 476
Lock down, 159 performing, 403 N benefits, 461
Lookup table, 166 preparation, 404 implementation, 463
setup, 406 National ID, 41, 300 running reports, 464
transaction report, 410 formats, 36 onSave, 51, 188
M usage, 403 import errors, 260 onView, 188
Maternity leave, 342 Nationality Operational Data Store (ODS), 54, 460, 526
Main functional consultant/solution architect, Matrix invalid country, 258 Opt-in, 30
61 manager, 132 Networking Lunch, 190 Opt-out, 30
Make Amendment, 352 relationships, 280, 284 New hire, 139, 184, 330, 338 Org Chart, 304, 480, 485
Manage maximumFractionDigits, 207 workflow trigger, 140 contingent worker, 397
business configuration, 105 max-length, 207 Next Gen Admin, 42, 75 Organizational
compensation, 103 mdfSystemStatus, 240 setup, 76 details, 180
features, 481 NGA euHReka, 500, 541 hierarchy, 280

582 583
Index Index

Organizational (Cont.) Payroll Control Center, 437, 439 Pivot Positions (Cont.)
realignment, 402 Payroll Information view, 434 charts, 458, 470 transfers, 289
structures, 43 Payroll Time Sheet, 341, 347 query, 473 types, 280
Organizational data, 499 approval workflow, 353 tables, 458, 470 Positive time recording, 347
Foundation Object integration, 516 composition, 348 Platform-as-a-Service (PaaS), 189 Post-implementation, 76
integration, 513 configuration steps, 349 Platinum/Premium Experience Plan Support, system maintenance, 78
integration prerequisites, 514 employees, 351 77 Posting
integration process, 514 managers, 352 Portlets, 99 date, 359
Organizational Information portlet, 314 objects, 345 description, 181 type, 360
Organizational Management (OM), 513 setup, 349 notifications, 149 unit, 360
Overtime usage, 350 title, 181 postSaveRules, 174, 188
hours, 342 Pending Position Information portlet, 314 Preferred Care Support, 77
recording, 347 data, 170 Position Management, 50, 185, 275, 517 Preferred language, 326
requests, 148, 319 attributes, 278 Pretty Good Privacy (PGP), 503
Pension Payouts, 247, 371, 441, 453 benefits, 275 Primary Emergency Contact portlet, 124
P People Profile, 47, 398 history, 275 Primary flag, 261
contingent worker, 397 implicit, 276 Project
Packaged integrations, 499 People scope, 471 implicit guidelines, 277 checklist, 60, 64
Page Views, 75 Period end processing, 358359 SAP SuccessFactors applications, 295 delivery, 69
monitoring, 78 options, 359 manager, 64
settings, 231, 286, 292
Paid leave, 108 Permanent account, 344 methodology, 63
Position Org Chart, 280
Parent fields, 517 Permissions, 26, 92, 421 plan, 60, 69
security, 283
parentPickList, 176 category, 173 tasks and time estimates, 60
Position Sync, 288
parentPickListValue, 176 common, 93 team structure, 61
Positions, 126, 277
Partial days, 355 group, 89, 91 timeline, 60
access, 284
Pay Calendar, 201 settings, 99 Project Team Orientation (PTO) training, 60,
actions, 289
Pay Component, 98, 200, 217, 225, 412, 424, PerNationalId, 555 64
control, 285
442 PerPerson, 555 Promotions, 130, 331
effective-dated, 281
Pay Component Group, 98, 201, 226 Person, 126, 324, 467 Propagation, 203
entry date, 283
Pay Component Non-Recurring, 249 ID, 308 forward, 230
filter, 287
Pay Component Recurring, 248 object, 38, 188 statement, 212
hierarchy, 280, 292
Pay Grade, 45, 201, 203, 414 Person Info portlet, 308 Propagation Data Model, 204, 212
Person Relationship portlet, 247 implicit, 278 configuration, 212
Pay Group, 201, 225
Pay Range, 45, 201 Personal Contacts portlet, 310 job profiles, 296 mapping, 212
Pay Scale, 403 Personal Documents Information, 248 mass changes, 290 Propagation Rules Data Model, 71
Pay Scale Structure, 45, 423, 441 Personal Information portlet, 37, 100, 247, matrix relationships, 280 Provisioning, 35, 7072, 118, 152, 335, 380
Pay slip, 435 301, 305306, 418 Object Definition, 278 Propagation Data Model, 205
Pay Structures, 44 country-specific, 307 parent, 279 settings, 7273
Pay Targets, 318 global, 307 permissions, 284 Public Profile, 303304, 369
Payment Information portlet, 186, 312 triggers, 139 propagation, 288 Publisher, 551
Payment methods, 311 Personally Identifiable Information (PII), 207, reclassification, 289 Purge type, 244
Payment Mode, 419 306 requisitions, 296
Payroll Personnel Administration (PA), 507 Right to Return, 294
administrator, 438 Picklists, 3637, 110, 506 security, 283 Q
engine, 431 legacy, 234 shared, 280
errors, 438 MDF, 234 stable headcount, 293 Quality gate (q gate), 64
event, 117 payment mode, 421 structure, 279 Query, 457, 470
managers, 432 payroll configuration, 244 synchronization, 287 build, 471
transactions, 433 template, 71 time, 283 Quickcard, 48, 418

584 585
Index Index

R Reports (Cont.) SAP BusinessObjects Business Intelligence, SAP Product Management, 28


new, 468 269 SAP Service Marketplace, 35, 81, 236, 567
Range Penetration, 45, 285 properties, 474 SAP BusinessObjects Web Intelligence, 269 SAP SuccessFactors, 25
Rapid-Deployment Solution (RDS), 266 scheduling, 475 SAP Community Network, 567, 569 blog, 570
RBP, 4849, 71, 73, 78, 83, 295, 327, 402 share, 475 SAP Customer SharePoint, 60 integration, 29
employee groups, 407 Request SAP Data Services, 266 strategy and roadmap, 28
framework, 83 for, 157 SAP Employee Health and Safety Management UI, 164
global assignments, 381 status, 157 (EHSM), 507 SAP SuccessFactors Community, 567568
mass changes, 405 type, 157 SAP Enterprise Portal, 527 SAP SuccessFactors Compensation, 546
positions, 283 Requests Still In Progress that I Approved, 148 SAP ERP SAP SuccessFactors Employee Central Admin-
Realize phase, 66 Requests Waiting for My Approval, 148 custom attributes, 500 istration, 569
activities, 66 Required, 207 modules, 507 SAP SuccessFactors Employee Central Project
Real-time synchronous, 227 fields, 338 SAP ERP to SAP SuccessFactors Employee Team Orientation, 569
Recipients, 477 Requirements gathering, 205 Central Data Migration Rapid-Deployment SAP SuccessFactors HCM Suite, 25
workshops, 65 Solution (RDS), 265 SAP SuccessFactors Mobile, 479
Reclassification, 289, 331
Requisition Field Association (RFA), 544 SAP ERP FI-CO, 433, 518 activation and deactivation, 482
Recovery
Requisitions, 296 SAP ERP HCM, 25, 56, 432 enabling, 481
format, 416
Resource data extraction, 270 features, 479
mode, 413
booking, 64 Employe Central RDS migration, 266
Recovery Pay Component, 416 use, 484
loading, 506 integration add-on, 270
Recurring account, 344 SAP SuccessFactors Onboarding, 548
Respect permission, 134 migration objects, 267
Recurring Deduction portlet, 426, 429 SAP SuccessFactors Partner Portal, 567
Retention bonus, 200 SAP ERP Payroll, 431432, 499
Recurring Pay Component, 251 SAP SuccessFactors Recruiting, 481, 547
Retired, 333, 453 SAP Experts, 570
RecurringDeductionReplication, 427 SAP SuccessFactors Succession Management,
Retroactive changes, 352 SAP Fieldglass, 394, 399, 504
RecurringDeductionTime, 427 285
Right to Return, 294 data objects, 399
Reference objects, 264 SAP SuccessFactors Succession Planning, 548
global assignments, 294 Foundation Objects, 399
Regular positions, 280 SAP SuccessFactors Support, 7677, 80
leave of absence, 294 SAP Fiori, 47
Regular working hours, 342 SAP SuccessFactors team, 61
Roles, 84, 132, 382 SAP Governance, Risk, and Compliance (GRC),
Rehire, 139 SAP SuccessFactors Workforce Analytics
assign to group, 87, 91 499, 504
Reimbursements, 371 assignment, 327 SAP GUI, 433 (WFA), 223, 500
Relationship to approver, 133 create, 87, 90 SAP HANA, 464465 SAP SuccessFactors YouTube channel, 570
Relationships, 279 name, 90 SAP HANA Cloud Integration (HCI), 29, 270, SAP/Partner Portal, 60, 81
Remind in Days, 131 scenarios, 105 399, 497, 499500, 502 SAPUI5, 47, 437
Report Designer, 462 supplement, 105 SAP HANA Cloud Platform (HCP), 50, 163, saveAlert, 188
Reporting, 26, 37, 54, 78, 263, 324, 327, 457 Route request, 159 189, 191 saveRules, 173, 188
components, 457 Rules, 51, 142, 172, 184, 287 SAP Help Portal, 81, 567 Schedule, 292, 477
cross-module, 462 assigning, 188 SAP Identity Management (IDM), 499, 527 Scheduled jobs, 75, 264
custom, 66 details, 185 Employee Central system of initiation, 529 monitoring, 78
data export, 264 execution, 230 integration, 527 Scope of work (SOW), 60
hierarchy, 231, 292 Rules Engine, 51, 118, 184, 275, 359, 546 system of initiation, 529 Scorecard, 479
methods, 459 SAP Jam, 480481, 567 Search options, 157
query, 457 feed, 484 SearchSAP, 570
Reports, 457, 474 S groups, 81 Security, 42
add components, 469 SAP Launch, 63, 70 administrator, 85
creation, 468 Salary range, 199 phases, 64 Self-service, 324
custom, 466 Sales cycle, 60 SAP ONE Support Portal, 507 transactions, 49, 434
headers, 462 SAP Business ByDesign, 60 SAP PartnerEdge, 567 Sequence number, 258
list, 458 code mapping, 536 SAP Process Integration (PI), 497 Service Event Bus (SEB), 551
manage, 469 integration, 534535 pass through, 503 Service transition, 60

586 587
Index Index

Setting reminders, 152 Talent, 55 Time Off (Cont.) User Data File (UDF), 47, 246, 262, 546
SF notifications, 482 Talent Hybrid deployment, 462, 531 employees, 358 User experience (UX), 39
Shared positions, 280 Talent Insight, 500 features, 369 User interface (UI), 483
showTrailingZeros, 207 Talent Management, 84 HR administrators, 523 User permissions, 39
Sick time, 342 Target integration, 360 Users Sys Info, 172
Side-by-Side deployment, 55, 499, 530 population, 91, 283 leave of absence, 355
Consolidated, 530, 532 users, 244 manage, 367, 370
Distributed, 531 Tax managers, 346, 367 V
field mapping, 532 portlet, 434 objects, 355, 359
integration, 530 withholding forms, 354 period end processing, 492 Valid Values Source, 37
standard fields, 533 Team requesting, 362363 validateRules, 173, 188
Social calendar, 471 screen, 354, 491 Validations, 270
accounts, 309 view, 201 setup, 362 Value mapping, 240, 513
insurance, 435 Team Absence Calendar, 362, 365, 368, 480, user groups, 345 value.<locale>, 240
Social Security, 435 492 Time Pay Type, 346 value.defaultValue, 48
Software development kit (SDK), 190 access, 364 Time Profile, 345, 347, 356 Variable Pay, 394, 546
Software-as-a-Service (SaaS), 25, 64 Technical Time Recording Admissibility, 345 Vendor, 395, 399
benefits, 27 resources, 62 Time Recording Profiles, 347, 350 Vendor management systems (VMS), 67
Spot Bonus portlet, 95, 318, 329, 490 team members, 549 Time Sheet, 349, 351 Verify phase, 67
SSO, 462 Technical Wage Types, 60 buttons, 351 tasks, 94
Stable headcount, 293 Templates employees, 521 Views, 155, 299, 433
Stalled for Days, 159 catalog, 213 integration, 345 approval history, 48
Standard load, 329 Time Type Group, 342 Virtual Private Network (VPN), 207
integration templates, 558 Terminate/Retire portlet, 453 Time Types, 345, 350, 355, 361 Visibility, 200, 234
view, 473 Termination, 115, 315, 333, 505 Time Valuations, 358
Start Contingent Worker (SCWK), 396 details, 247, 260 Time values, 147
start-date, 233 record, 26 To Do portlet, 74, 367 W
Static group, 89 Testing, 482 Total cost of ownership (TCO), 480
Statuses Theming, 536 Touchbase, 79, 486 Web Dynpro, 534, 563
active vs. inactive, 109 Third-party integration, 500 Transaction, 96, 330 Web services, 348
Subscribers, 551 Thomsons Online Benefits, 230, 539 future-dated, 97 Week Summary, 138, 351
Success Store, 243244, 428 Threadpool, 369 pending approval, 170 wfConfig, 138
SuccessFactors Delivery Toolkit, 69 Time Account Postings, 366 SLG1, 49 What-you-see-is-what-you-get (WYSIWYG)
SuccessFactors Support Resource Kit, 77 Time Account Snapshot, 343 transactionSequence, 242, 289 editor, 151
Succession Data Model, 39, 71, 334 Time Account Types, 320, 355356 Transfers, 172, 289, 331, 338 Withdraw, 394
Succession planning, 85, 295 Time Accounts, 314, 320, 343 Translatable, 337 Work
Super administrator, 86, 105, 287 Time Information, 26, 347 Translations, 166, 338 order, 95, 395
Supervisor, 84 Time Management, 51, 185, 341342 Tuition Reimbursement, 178, 373 permit, 186
System objects, 347 Configuration UI, 570 schedule, 344, 347, 357, 421
attributes, 28 profiles, 50 Twitter, 538 Work Permit Info portlet, 124, 253, 309, 326
engagement, 467 Time Off, 166, 341, 354, 366, 480, 484, 490, Workflow
521 approval history, 414
account details, 359 U exception, 45
T accruals, 367 Workflow Action Pending notification, 129
approval, 358 UI mash-up, 30 Workflow Configuration, 129, 202, 226
Table, 512 assignment, 358 Universal features, 30 sections, 202
PAOCFEC_EEKEYMAP, 125 configuration, 362 Upgrade Center, 67, 74, 80, 394 Workflow Contributors, 139, 226
Take Action, 183, 393 User Acceptance Testing (UAT), 39 Workflow Derivation, 402

588 589
Index

Workflow Groups, 160 groups, 160


Workflow Rules Data Model, 152 invalid approvers, 160
Workflow Step Approver (wfStepApprover), manage requests, 153
140 manual delegation, 142
Workflow triggers notifications, 136
Foundation Objects, 142 position change, 170
Generic Objects, 98 routing, 157
Workflows, 50, 107, 123, 152, 158, 221, 383 search criteria, 138
active, 156 triggers, 462
administration, 156 WorkForce Software EmpCenter, 537
approval history, 150 integration, 538
approval process, 155 WorkForce Software WebClock, 435
audit trail, 154 Working hours, 334
auto delegation, 151
comments, 135
creation, 152 X
delegation, 143
email notification templates, 128 XML data models, 118, 196, 206

590
First-hand knowledge.

Luke Marson is a C-level leader, architect, principal


consultant, and globally-recognized expert for SAP
SuccessFactors HCM suite solutions and is a Certified
Professional in Employee Central. In addition to being
an author, writer, speaker, and go-to individual on
HCM and SAP SuccessFactors topics, he is also an SAP
Mentor program alumni and an Americas SAP Users
Group (ASUG) volunteer.

Murali Mazhavanchery is the senior director of pro-


duct management at SAP focusing on Employee Cen-
tral design and development. He has over 15 years of
HRIS project management experience. Murali has been
in around HR functionality for all his professional life.
In his past roles, he was an industrial relations manager,
an HCM systems implementation consultant, and has
now transitioned to building software.

Rebecca Murray iis an experienced HCM consultant


and a partner at Cultiv8 Consulting. She specializes
in the design and integration of HRIS and talent ma-
nagement solutions including both SAP ERP HCM and
SAP SuccessFactors. Rebecca has completed numerous
global and multi-national implementations in both SAP
ERP HCM and SAP SuccessFactors and is considered a
thought leader in the field of Employee Central.
Luke Marson, Murali Mazhavanchery, Rebecca Murray
SAP SuccessFactors Employee Central We hope you have enjoyed this reading sample. You may recommend
The Comprehensive Guide or pass it on to others, but only in its entirety, including all pages. This
reading sample and all its parts are protected by copyright law. All usage
590 Pages, 2016, $79.95/79.95
and exploitation rights are reserved by the author and the publisher.
ISBN 978-1-4932-1218-7
2016 by Rheinwerk Publishing, Inc. This reading sample may be distributed free of charge. In no way must the file be alte-

www.sap-press.com/3834 red, or individual pages be removed. The use for any commercial purpose other than promoting the book is strictly prohibited.