SF Rules Engine AdminGuide

SuccessFactors HCM Suite August 2014 Release Document Version: 1.0 - August 22, 2014

Configuring Business Rules in SuccessFactors Administration Guide

Table of Contents 1

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1.1

About Configuring Business Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1.2

Who configures business rules using the Rules Engine?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2

Use Cases for Configuring Business Rules Using the Rules Engine. . . . . . . . . . . . . . . . . . . . . . . . . 7

2.1

Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.2

Propagation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.3

Calculation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.4

Validation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.5

Time Off. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.6

Eligibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

2.7

Defaulting Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.8

Module-Specific or Feature-Specific Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

3

Before Configuring Business Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

3.1

Assigning Role-Based Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

3.2

Creating Rule Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3.3

Setting Up Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3.4

Creating MDF Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4

General Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

5

Business Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

5.1

What are business rules?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

5.2

What are base objects?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

5.3

How do you add objects that are not related to the base object?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 5.3.1

Adding MDF Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

5.3.2

Removing MDF Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

5.3.3

Adding EC Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

5.4

What are rule types?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

5.5

What is effective dating?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

6

IF, THEN, and ELSE statements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

6.1

What are IF statements?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

6.2

What are THEN statements?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

6.3

What are ELSE statements?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

6.4

What are ELSE IF statements?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

6.5

Left Expression. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

6.6

Right Expression. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

6.7

Comparing Left and Right Expressions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

6.8

Collection Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

2

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Configuring Business Rules in SuccessFactors Table of Contents

6.9

Connecting IF Conditions with AND/OR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

6.10

System Actions for THEN and ELSE Statements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

7

Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

7.1

What are functions?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

7.2

Mapping of Data Types and Field Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

7.3

Input Parameters for Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

7.4

Function Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

7.5

7.4.1

Mathematical Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

7.4.2

Module-Specific or Feature-Specific Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

7.4.3

String Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

7.4.4

Time-Related and Date-Related Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

7.4.5

Other Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Functions A-Z. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 7.5.1

Add/Minus/Divide/Multiply. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

7.5.2

Amount from Pay Scale Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

7.5.3

Avg FTE for Accruable Period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

7.5.4

Avg FTE for Accruable Period based on Month. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

7.5.5

Avg FTE for Accrual Period. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

7.5.6

Avg FTE for Accrual Period based on Months. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

7.5.7

Calculate Balance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

7.5.8

Calculate FTE based on Standard Hours. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

7.5.9

Cap Accrual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

7.5.10

Concatenate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

7.5.11

Convert Days To YY/MM/DD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

7.5.12

Currency from Pay Scale Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

7.5.13

Date. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

7.5.14

Date Plus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

7.5.15

Day Of Month. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

7.5.16

Day Of Week. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

7.5.17

Difference In Calendar Years. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

7.5.18

Difference In Years Round Down. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

7.5.19

Difference In Years Round Up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

7.5.20

Divide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

7.5.21

Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

7.5.22

Format Number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

7.5.23

Frequency from Pay Scale Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

7.5.24

Generate External Code Time Off. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

7.5.25

Get Absence Days. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

7.5.26

Get Calendar Days. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

7.5.27

Get Completed Calendar Weeks Between ISO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

7.5.28

Get Completed Remaining Calendar Weeks ISO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Configuring Business Rules in SuccessFactors Table of Contents

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

3

7.5.29

Get Completed Weeks Between. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

7.5.30

Get First Day Of Month. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

7.5.31

Get Incumbent By Position. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

7.5.32

Get Matrix Position Code By Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

7.5.33

Get Months From Hire Date Taking Account Of Threshold. . . . . . . . . . . . . . . . . . . . . . . . . . . 69

7.5.34

Get Months Taking Account Of Threshold. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

7.5.35

Get Next Available Manager By Position. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

7.5.36

Get Next Value. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

7.5.37

Get Number Of Child Positions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

7.5.38

Get Number Of Eligible Days. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

7.5.39

Get Number Of Months From Hire Date. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

7.5.40

Get Pensionable Salary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

7.5.41

Get Pensionable Salary with Global Assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

7.5.42

Get Work History Days ADD ALL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

7.5.43

Get Work History Days CONTINUOUS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

7.5.44

Get Work History Days CURRENT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

7.5.45

Get Work History Days PREVIOUS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

7.5.46

Is Employee Full Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91

7.5.47

Is Empty. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

7.5.48

Is Position Below User's Position In Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

7.5.49

Latest Date. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

7.5.50

Login User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

7.5.51

Lookup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

7.5.52

Math Expression. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

7.5.53

Minimum. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

7.5.54

Minus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

7.5.55

Multiply. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

7.5.56

Opposite Sign. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

7.5.57

Round. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

7.5.58

Timestamp Current Time UTC plus Offset Minutes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

7.5.59

Today. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

7.5.60

Treat Null As. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

7.5.61

Week Of Year ISO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102

8

Creating a Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

8.1

Specifics to EC Object Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

8.2

4

8.1.1

Which EC base object should you choose?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

8.1.2

Graphical Overview: Rule Events in Employee Central. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

8.1.3

About Model Base Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

8.1.4

Pay Component Group Sums in Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

8.1.5

Rule Example Using EC Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109

Creating a Rule That Raises a Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Configuring Business Rules in SuccessFactors Table of Contents

8.2.1

Creating a MessageDefinition Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

8.2.2

Creating a Message Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

8.2.3

Message Severity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

8.3

Creating a Rule with Lookup Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114

8.4

Creating Effective-Dated Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

8.5

Using Parent MDF Object Data in a Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

9

Copying Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

10

Assigning Rules to Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

10.1

Why assigning rules to objects?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

10.2

Assigning a Rule to an MDF Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

10.3

Assigning a Rule to an EC Object in Administration Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 10.3.1

Limitations for onView Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

10.3.2

Rule Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

11

Exporting and Importing Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

11.1

Exporting Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

11.2

Importing Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

12

Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127

12.1

Common Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

12.2

Tips for Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128

12.3

How to improve performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Configuring Business Rules in SuccessFactors Table of Contents

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

5

1

Overview

1.1

About Configuring Business Rules

You can configure the business rule logic for various modules and features using the Rules Engine. You can configure business rules that cover legal regulations ('The FLSA status is required for employees working in the USA'), company policies ('All employees moving to the London office get a compensation for the high cost of living'), or other requirements. These requirements vary from customer to customer, and also depend on how the customer has set up the system, so the rules cannot be delivered as 'out-of-the-box' rules, but have to be highly configurable. The Rules Engine is a tool that allows you to create such customer-specific rules. You define the business rules in the Rules Engine and the system executes these rules during runtime. Technically, the Rules Engine is based on the Metadata Framework (MDF), but uses its own user interface (UI) in the Administration Tools.

1.2

Who configures business rules using the Rules Engine?

There are two main areas that use the Rules Engine to create rules: Employee Central (EC) and the Metadata Framework (MDF). Both areas use different types of data objects, so you have to distinguish the following: ●

EC Objects These are objects that are delivered for Employee Central to set up company and employee data. They comprise person objects, employment objects, and foundation objects. Take a look at the Employee Central Implementation Handbook for a list of all these objects.

●

MDF Objects These are objects that are created in the Metadata Framework (MDF). As these can be used to define company data as well as employee data, they are also called 'generic objects' (GO). MDF objects are created by:

6

○

Customers The customer can enhance the business objects and their functionality delivered by creating customerspecific objects. For example, the customer can create customer-specific foundation objects.

○

Development Teams Development teams use MDF objects for new features like Time Off, Position Management and so on, where the rules have to be highly configurable so that customers can adapt them to their very specific requirements. It is recommended that you stick to the rule examples that are described in the corresponding handbook of the feature, as these have been tested thoroughly. You can find a list with features and modules that use rules under Module-Specific or Feature-Specific Rules.

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Configuring Business Rules in SuccessFactors Overview

2 Use Cases for Configuring Business Rules Using the Rules Engine 2.1

Workflow

You can define rules that automatically determine the right workflow when the manager or employee changes employee data. To achieve this, you create a workflow foundation object and assign it to the rule in the Rules Engine UI.

Note The use of workflows in the Rules Engine is currently only supported for MDF objects. You can find more information about workflows in the Metadata Framework Implementation Handbook, and an example in the Position Management handbook.

2.2

Propagation

You can define propagation rules to have the system automatically copy over the data from one field to another field. This way you can have the same data in several places of the system, while keeping just one data record.

Note For EC objects, you can also use the HRIS propagation XML to propagate values. However, you can only propagate values from foundation objects to employment objects. This limitation does not exist in the Rules Engine. Here are some examples for typical use cases: ●

Example 1: Update Job Codes in Employee Central IF… the job code is changed in Employee Central THEN… retrieve all the job-code-related data from the job-related foundation objects to update the data in the Employee Central

●

Example 2: Propagate FLSA Status IF… the country is USA AND the job classification is changed THEN… propagate the FLSA status to jobInfo

●

Example 3: Propagate Standard Hour IF… the legal entity is changed in Employment Info THEN…

Configuring Business Rules in SuccessFactors Use Cases for Configuring Business Rules Using the Rules Engine

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

7

propagate the standard hour to Employment Info ●

Example 4: Propagate Job Code to Position You can find an example of how to propagate the job code to the Position MDF object in the Position Management handbook.

2.3

Calculation

You can define rules that automatically perform calculations using the various functions the Rules Engine supports. Here are some examples for use cases. To achieve these use cases, you can make use of mathematical functions as well as time-related and date-related functions. You can find more information about the various functions available under Function Groups. ●

Example 1: Age/Year of Service To get an employee's current age, you can calculate the difference between the current date and the employee's birth date. You can find an example rule in the Employee Central Implementation Handbook under Setting up configurable rules.

●

Example 2: Time in Job You want to calculate an employee's time in the job, following the calculation: Number of years/months/days = current date - start date of the current job classification

●

Example 3: EEO Report To fulfill equals employment opportunity (EEO) requirements, you want to calculate the following: Months remaining on visa = Expire date - current date

2.4

Validation

You can use validation rules to let the system check the user's input before saving. You can set a field to mandatory, or you can trigger error messages. ●

Example 1: Setting a Field to Mandatory IF... the country is USA THEN... the FLSA status is required

●

Example 2: Displaying Error Message IF... the national ID is not entered THEN... the message 'Please enter the national ID' is displayed

8

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Configuring Business Rules in SuccessFactors Use Cases for Configuring Business Rules Using the Rules Engine

2.5

Time Off

Time Off is a component used in Employee Central to handle all types of absence, such as vacation, sick leave, and moving house. You can update the employee’s vacation days based on the year of service, for example. You can find rule examples in the Time Off handbook.

2.6

Eligibility

You can define which employees should be included in a bonus plan or compensation planning form. To achieve this, you have to integrate the modules Variable Pay or Compensation with Employee Central. ●

Example for a Variable Pay Eligibility Rule IF... the employee was hired on or after January 1, 2008 AND belongs to the Business Unit 'Seoul-Korea' AND has either the job code 'HR Receptionist' OR the job code 'Operations Director' THEN... this employee should be eligible (for a variable pay program or bonus plan)

●

Example for a Compensation Eligibility Rule IF... the employee type does not equal Contract, Temporary or Union AND the employee is regular AND the rate type is 'Hourly' and 'Salaried' AND the hire date is after 10/01/2010 AND the rehire date is after 10/01/2010 AND the employee status is Active or STD THEN... this employee should be eligible (for a specific compensation form)

2.7

Defaulting Values

You can define default values for specific fields. Here are some typical use cases: ●

Example 1: Default National ID When the Admin adds a new employee, the national ID is filled with default values (for example, Is Primary: Yes). You can find an example rule in the Employee Central Implementation Handbook.

●

Example 2: Default Employment Details

Configuring Business Rules in SuccessFactors Use Cases for Configuring Business Rules Using the Rules Engine

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

9

If the Admin adds a new employee for the company COMP_USA, the employee is automatically eligible for stock, and the initial stock grant is set to 200. You can find an example rule in the Employee Central Implementation Handbook.

2.8

Module-Specific or Feature-Specific Rules

You can find more information about rules that are specific to modules or features in the following handbooks or guides: This handbook/guide...

Describes how to configure rules to:

Employee Central Implementation Handbook

Default values, raise messages, and send alerts and no­ tifications to workflow approvers. See chapters... ●

Setting up configurable rules

●

How do you set up alerts and notifications - Set up alerts and notifications using rules

...of the Employee Central Implementation Handbook. Position Management Handbook

Propagate job code fields to Position Management

Time Off Handbook

Define accrual rules and accrual eligibility

Advances Implementation Handbook

Define eligibility rules for Advances

Employee Central - Compensation Integration Hand­ book

Define eligibility rules for compensation plans

Employee Central - Variable Pay Integration Handbook

Define eligibility rules for variable pay programs and bonus plans

Mass Changes

Update employee fields after a reorganization in a legal entity

Note Mass Changes uses its own user interface (UI) for creating mass change rules.

10

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Configuring Business Rules in SuccessFactors Use Cases for Configuring Business Rules Using the Rules Engine

3

Before Configuring Business Rules

There are some settings you need to make before you can configure business rules using the Rules Engine.

3.1

Assigning Role-Based Permissions

You can only create rules if you have the corresponding permissions.

Procedure Here's how you assign the corresponding permissions for creating rules: 1.

Go to Administration Tools.

2.

In the Manage Employees portlet, select

3.

On the Permission Role List page, under Permission Role, click the permission role for which you want to manage the permissions. The Permission Role Detail page opens.

4.

In the Permission settings section, click the Permission… button to specify the permission you want to assign to the role. The Permission Settings window opens.

5.

In the Administrator Permissions section, click on Metadata Framework.

6.

Select all the checkboxes on the right side of the dialog.

Set User Permissions

Manage Permission Roles .

Here's some information on what the permissions are used for:

7.

○

Configure Object Definitions You need this authorization to be able to create rule types and lookup tables.

○

Configure Business Rules This is the only permission used directly for the Rule Engine. You need this authorization to be able to access the Rules Engine UI.

○

Manage Data You need this authorization to be able to create MessageDefinitions for raising messages. You need this authorization also to be able to create Sequence objects for defining sequences. Both MessageDefinitions and Sequence objects are MDF objects.

○

Import permission on Metadata Framework You need this authorization to be able to import and export data for generic objects or business rules using the Import and Export Data link in the Administration Tools.

Save your changes.

Configuring Business Rules in SuccessFactors Before Configuring Business Rules

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

11

3.2

Creating Rule Types

You have to assign a rule type to every rule you create.

Procedure To create a rule type: 1.

Go to Administration Tools.

2.

In the Company Processes & Cycles portlet, select

3.

Click Search: Picklist and select RuleType (RuleType) from the dropdown list.

4.

Click the Insert New Record button.

5.

As Effective Start Date, enter 01/01/1900.

Company Settings

Configure Object Definitions .

If you enter a later date, you have to keep in mind that effective-dated rules only work if the rule type is active on or before the date when the rule becomes effective. For example, if you change the Job Info record in the past, but the rule type is only valid as of today, the rule is not triggered. 6.

In the Values section, enter an external code for the rule type you want to create. When you create rules for the following modules or features, it is important that you stick to the spelling and capitalization of the external code of the rule type, as they have a specific function: For this module or fea­ ture…

…enter exactly this ex­ ternal code:

Here's why:

Compensation, inte­ grated with Employee Central

compensationEligibility

From the compensation screens for eligibility rules, the user can select only the rules assigned to this rule type.

Variable Pay, integrated with Employee Central

varpayEligibility

From the variable pay screens for eligibility rules, the user can select only the rules assigned to this rule type.

Mass Changes (in Em­ ployee Central)

massChange

You can create rules on the Mass Changes page.

For all other use cases, you can create your own rule types even if there is no specific behaviour defined for them yet. However, we suggest you use the rule type to sort the rules according to their purpose, for example, to differentiate Time Off rules from Position Management rules. 7.

Enter a label.

8.

Select the status Active.

9.

Save your changes.

12

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Configuring Business Rules in SuccessFactors Before Configuring Business Rules

3.3

Setting Up Employee Central

When you want to set up rules for Employee Central, you need to have set up the following before you can create rules for EC objects: ●

Corporate Data Model

●

Succession Data Model

●

Country-specific data models

●

Picklists

●

Foundation and employee data

●

Business Configuration UI (BCUI)

Note The Business Configuration UI allows you to assign rules to employment and person objects from the Administration Tools. See also: Assigning a Rule to an EC Object in Administration Tools. For more information, please refer to the Employee Central Implementation Handbook.

3.4

Creating MDF Objects

When you want to set up rules for MDF objects, such as for Position Management, Time Off, or for customerspecific MDF objects, you need to have set up the MDF objects for these features before you can create rules for them. For more information, please refer to the module-specific or feature-specific handbooks or guides, and the Metadata Framework Implementation Handbook.

Configuring Business Rules in SuccessFactors Before Configuring Business Rules

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

13

4

General Limitations

Here's a list of the general limitations that apply to the Rules Engine at the moment: No localization of decimal formats Currently, there is no localization of decimal formats. That means that, irrespective of the logon language, you always have to use the US format when you enter decimal numbers in a rule (for example, 0.2 - using a dot to indicate the decimal). No test run Currently, there is no test run tool that helps you prevent or find errors that would cause the rule to fail. Refer to Common Errors for some tips and tricks on how to prevent errors.

14

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Configuring Business Rules in SuccessFactors General Limitations

5

Business Rules

5.1

What are business rules?

Business rules are a way to add application logic to determine the outcome of a change made to particular data in the system. Rules follow the logic 'If this data is changed in a certain way, then the system reacts in this way.' Here is an example for a rule in plain language: IF… the company is SAP_USA AND the employee is eligible for stock THEN… the initial stock grant is set to 200. This is what this rule looks like in the system:

A rule consists of the following parts: ●

Information about the rule object itself (Rule ID, Rule Name, Rule Type)

●

Objects and fields that determine what can be defined in the rule (defined by Base Object, Manage Parameters)

●

IF statement You can enter only one IF statement, but you can add multiple conditions in one IF statement. You can also add ELSE IF statements (see below).

●

THEN statements You can add several THEN statements for one rule.

●

ELSE statements You can add several ELSE statements for one rule. The ELSE statement follows the THEN statement (IF THEN - ELSE).

●

ELSE IF statements You can add several ELSE IF statements for one rule. The ELSE IF statement follows the THEN statement.

Configuring Business Rules in SuccessFactors Business Rules

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

15

In the following chapters, you can find more information about the different parts of a rule.

5.2

What are base objects?

Base objects are the starting point for your rule. They correspond mainly to the data objects available in the system, which are either EC objects (foundation objects, employment objects, or person objects) or MDF objects. The base object defines what kind of input you can use for the rule. You can use the fields, attributes, and related data objects of the base object as input. For example, if you want to create a rule that is triggered when the employee status is changed, you choose Job Information as base object, as the employee status field is part of the Job Information EC object.

Note To find out which fields are part of which EC object (which corresponds to an HRIS element), refer to the data object tables of the Employee Central Implementation Handbook. To find out which fields are parts of which MDF object, you can look up the object in the MDF UI.

What types of base objects exist? Here's a list of the base objects you can choose from: Base object

Description

EC object (person or employ­ ment object)

These base objects refer to HRIS elements that are displayed as portlets on the user interface of Employee Central (EC). They correspond to the person and employment objects used in EC. The names of these base objects are de­ rived from the HRIS-element labels in the Succession Data Model. You can find a complete list of these HRIS elements and their standard labels in the Employee Central Implementation Handbook, under Setting up the Succes­ sion Data Model.

For example: ●

Compensation Information

●

Job Information

Person and employment objects are used to store employee data. Foundation object, for example: ●

Cost Center

●

Department

These base objects refer to HRIS elements that can be defined on the Manage Organization, Job and Pay Structures page. The names of these base objects are derived from the HRIS-element labels in the Corporate Data Model. You can find a complete list of these HRIS elements and their standard labels in the Employee Central Implementation Handbook, under Setting up the Cor­ porate Data Model. Foundation objects are used to store company data.

16

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Configuring Business Rules in SuccessFactors Business Rules

Base object

Description

Employee Information

This base object refers to the Add New Employee page. It is a composite of the different EC objects that are displayed on this page. Rules that use this base object are only triggered for changes made from the Add New Employee page.

[EC object] Model

The Model base objects are used to set field properties for EC objects (for ex­ ample, making a field mandatory, or hiding fields). Each EC object is defined ([person or employment object] once as a base object, and then as a Model base object. In addition, there is a Model) Model base object for changes made from the Add New Employee page (Employee Information Model). For example: ●

Compensation Information Model

●

Job Information Model

●

Personal Information Model

MDF objects, for example: ●

Position

●

Advance

●

Alternate Cost Distribution

All MDF objects existing in the system are listed here as base objects. They refer to: ●

Features that are based on the Metadata Framework, like Position Man­ agement, Advances, and so on

●

MDF objects created by the customer, for example, to be used as custom foundation objects

For more information about how base objects are used in rules, see Creating a Rule with EC Objects.

5.3 How do you add objects that are not related to the base object? You can create rules that span across several data objects, even when these have no relationship with the base object. This is like a cross-reference to an unrelated data object. How you add additional objects depends on whether the object you want to add is an EC object or an MDF object.

5.3.1

Adding MDF Objects

You can add MDF objects that are not related to the base object using the Manage Parameters link in the Rules Engine.

Procedure 1.

Go to Administration Tools.

Configuring Business Rules in SuccessFactors Business Rules

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

17

2.

In the Company Processes & Cycles portlet, select

3.

You can either:

Company Settings

○

Create a new rule by clicking Create New Rule.

○

Search for an existing rule, and edit the rule by clicking

Take Action

Configure Business Rules .

Make Correction .

4.

Click the Manage Parameters link:

5.

In the dialog box that opens, click Add New Parameter.

6.

In the Code field, enter a unique external code for the data object you are adding. For module-specific or feature-specific rules, you often have to stick exactly to the code that the development team has used in their coding. Refer to the corresponding handbooks for more information.

7.

In the Name field, enter a name or description for the data object. This does not have to be unique. For module-specific or feature-specific rules, you often have to stick exactly to the name that the development team has used in their coding. Refer to the corresponding handbooks for more information.

8.

In the Object field, select the MDF object you want to reference to. Here's an example, where you add the Alert MDF object:

9.

Click Apply.

Results The object you added now shows up in the left expression at the bottom of the dropdown list as in this example, where the MDF object Alert was added:

18

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Configuring Business Rules in SuccessFactors Business Rules

5.3.2

Removing MDF Objects

You can remove MDF objects that you have added to an unrelated base object using the Manage Parameters link. This only removes the MDF object from the dropdown lists used to navigate to the data objects and fields in the Rules Engine, it does not delete the MDF object.

Procedure 1.

Go to Administration Tools.

2.

In the Company Processes & Cycles portlet, select

3.

Search for the corresponding rule, and edit the rule by clicking

4.

Click the Manage Parameters link:

Configuring Business Rules in SuccessFactors Business Rules

Company Settings

Configure Business Rules .

Take Action

Make Correction .

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

19

5.

In the dialog box that opens, click the Remove icon next to the MDF object that has been added to the rule.

6.

Click Apply.

Results You can no longer navigate to the MDF object and its fields that are not related to the base object.

5.3.3

Adding EC Objects

You can define cross-portlet rules to determine that the change in one portlet (for example, Job Information) leads to a change in another portlet (for example, Compensation). You use the Employment Details object to navigate from the base object to an unrelated EC object. Here's an example of such a rule where the pay component is pro-rated: On the UI, the change happens in the Job Information portlet, but the update of fields is done in the Compensation portlet. In the IF or THEN statements, you select first the Employment Details object and then the corresponding EC object that is not related to the base object.

Please note the following limitations for cross-portlet rules: ●

You have to use an onSave event.

●

In the THEN condition, you can only refer to the following employment objects:

20

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Configuring Business Rules in SuccessFactors Business Rules

○

Employment Details (employmentInfo HRIS element)

○

Job Information (jobInfo HRIS element)

○

Compensation Information (compInfo HRIS element)

○

Compensation (payComponentRecurring HRIS element)

○

Spot Bonus (payComponentNonRecurring HRIS element)

○

Job Relationships (jobRelationsInfo HRIS element)

The following applies for all other event types or data objects: The THEN condition of the rule has to refer to a field that is part of the current entity, meaning the HRIS element that you assign the rule to in the data model. The IF condition can refer to data objects or fields that are not part of the current entity itself, which means it can refer to some HRIS element other than the one the rule is assigned to in the data model. Example: ●

Base Object: Employment Details

●

IF condition: JobInformation.company is equal to USA (Note that Job Information is a different HRIS element than Employment Details.)

●

THEN condition: Eligible for Stock is equal to Yes (Note that Eligible for Stock is an HRIS field of the Employment Details HRIS element. You should not select a different HRIS element, such as JobInformation.EventDate, because such a rule would not be triggered.)

5.4

What are rule types?

Rule types are a way to sort the rules into different groups. Development can then add logic for specific rule types in the coding. At the moment, rule types are used for filtering the rules that are displayed in specific modules or features. When you create rules for the following modules or features, it is important that you stick to the spelling and capitalization of the external code of the rule type, as they have a specific purpose: For this module or fea­ ture…

…enter exactly this exter­ Here's why: nal code:

Compensation, integrated with Employee Central

compensationEligibility

From the compensation screens for eligibility rules, the user can select only the rules assigned to this rule type.

Variable Pay, integrated with Employee Central

varpayEligibility

From the variable pay screens for eligibility rules, the user can select only the rules assigned to this rule type.

Mass Changes (in Em­ ployee Central)

massChange

You can create rules on the Mass Changes page.

For all other use cases, you can create your own rule types even if there is no specific purpose defined by development for them yet. However, we suggest you use the rule type to sort the rules according to what they are used for, for example, to differentiate Time Off rules from Position Management rules. See also Creating Rule Types for information about how to create a rule type.

Configuring Business Rules in SuccessFactors Business Rules

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

21

5.5

What is effective dating?

In business rules, effective dating means entering a date from which you want the rule to take effect. You do this in the Start Date field of a rule. Here's an example:

You need to note a few things about effective dates: ●

When you create a new rule, the system defaults January 1, 1900, as the effective date.

●

If you have rules in your system from an earlier release and upgrade to a later one, a migration script runs automatically, setting the effective date in your rules to January 1, 1900.

You can overwrite the default effective date with the date that suits your requirements.

22

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Configuring Business Rules in SuccessFactors Business Rules

6

IF, THEN, and ELSE statements

6.1

What are IF statements?

IF statements are the part of the rule that describe which condition has to be met before the system actions defined in the THEN statement are executed.

Is it possible to have a rule without IF statements? It is possible to create a rule without IF statements by selecting the Always True checkbox. This removes all IF conditions. For example, if you want to default values or set field properties that are displayed to the user as soon as the user opens a page, you do not need to enter an IF statement. Here's an example:

Configuring Business Rules in SuccessFactors IF, THEN, and ELSE statements

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

23

6.2

What are THEN statements?

THEN statements define how the system reacts to the conditions contained in the IF statement of the rule. For example, an error message is raised, a field is set to a specific value, or new data is created.

Is it possible to have a rule without THEN statements? It is possible to create rules that have only IF statements if the system's reaction is defined by a module or feature. For example, in eligibility rules for variable pay, you want to filter the employees that are eligible to take part in a variable pay program or bonus plan. Such a rule consists only of IF conditions as in this example: IF... the employee was hired on or after January 1, 2008 AND belongs to the Business Unit 'Seoul-Korea' AND has either the job code 'HR Receptionist' OR the job code 'Operations Director' THEN... this employee should be eligible (for a variable pay program or bonus plan) For which variable pay program or bonus plan the employee is then eligible for is defined in the variable pay module, therefore you do not enter a THEN statement in the rule itself.

6.3

What are ELSE statements?

ELSE statements define how the system reacts if the IF condition is not true. The THEN statement is then skipped and the system executes what is defined in the ELSE statement. ELSE statements allow you also to combine multiple rules in the same rule. For example, you can combine the following two rules into one using the ELSE statement: First rule: IF Country = USA THEN set EEO Category to EEO-US1 Second rule: IF Country is not equal to USA THEN set Notes = Non-USA Combined to one rule: IF Country = USA

24

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Configuring Business Rules in SuccessFactors IF, THEN, and ELSE statements

THEN set EEO Category to EEO-US1 ELSE set Notes = Non-USA Here's another example, showing what a rule in Time Off might look like. It shows that employees in the USA get 12 days of a particular leave type. Employees in other locations get 25 days.

Is it possible to have a rule without ELSE statements? You only use ELSE statements if you want to define how the system should react if the IF condition is not met. If you do not define an ELSE statement, and the IF condition is not met, the rule is not executed.

Configuring Business Rules in SuccessFactors IF, THEN, and ELSE statements

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

25

6.4

What are ELSE IF statements?

ELSE IF statements allow you to combine several conditions in the same rule. Only the statements following the first condition that is true are executed. All other statements are skipped. Here's an example:

6.5

Left Expression

A left expression is the part of a rule statement that is compared to the right expression. In the dropdown menu of the left expression, you can select: ●

Data Related to the Base Object This can be one of the following: ○

26

Fields assigned to the base object as configured in the data model (for EC objects) or the object definition (for MDF objects)

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Configuring Business Rules in SuccessFactors IF, THEN, and ELSE statements

Note You can select only fields that have been defined as visible. ○

Data objects and their fields that have one-to-one or one-to-many relationship with the base object These are indicated by a plus sign next to the data object. Example: You have selected Time Account as base object. In the left expression, you can navigate to the data object Time Account Details, as this has a one-to-many relationship with Time Account. Other related data objects are Time Account Type and User.

●

Functions Functions are used to set up more sophisticated rules that include mathematical calculations and formulas, for example. You can identify functions by the brackets that follow the function name; for example, Add(). You can find all available functions under Function Groups.

●

Additional MDF Objects MDF objects that have no relationship with the base object are listed at the bottom of the dropdown list as in this example, where you reference the Alert MDF object:

Configuring Business Rules in SuccessFactors IF, THEN, and ELSE statements

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

27

You have to add the data object that is not part of the base object to be able to refer to it in the rule. For information about how this is done, refer to Adding MDF Objects. ●

Current User This option is only available for EC objects. The user information is derived from the base object. For example, if the base object is Job Information, then the current user for the Job Information is passed to the Rules Engine as part of the base object. Select Context to navigate to the current user as in this example:

●

Effective Date This option is available for those EC objects that are effective dated, as well as for all MDF objects.

28

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Configuring Business Rules in SuccessFactors IF, THEN, and ELSE statements

Select Context to navigate to the effective date as in this example:

6.6

Right Expression

A right expression is the part of a rule statement that is compared to the left expression. In the dropdown menu of the right expression, you can select: ●

Field Type Select the field type when you want to enter or select a specific value. In our example, you select the Date field type and then a specific date:

●

Fields assigned to the base object that have the same field type as the left expression

Note You can select only fields that have been defined as visible. ●

Functions that are available for the field type of the selected left expression Functions are used to set up more sophisticated rules that include mathematical calculations and formulas, for example. You can identify functions by the brackets that follow the function name; for example, Add(). You can find all available functions under Function Groups.

●

Additional MDF Objects MDF objects that have no relationship with the base object are listed at the bottom of the dropdown list as in this example, where you reference the Alert MDF object:

Configuring Business Rules in SuccessFactors IF, THEN, and ELSE statements

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

29

You have to add the data object that is not part of the base object to be able to refer to it in the rule. For information about how this is done, refer to Adding MDF Objects.

30

○

Current User This option is only available for EC objects. The user information is derived from the base object. For example, if the base object is Job Information, then the current user for the Job Information is passed to the Rules Engine as part of the base object. Select Context to navigate to the current user as in this example:

○

Effective Date This option is available for those EC objects that are effective dated, as well as for all MDF objects.

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

Configuring Business Rules in SuccessFactors IF, THEN, and ELSE statements

Select Context to navigate to the effective date as in this example:

●

Null Select Null as in this example when you want to set the field values back to null:

6.7

Comparing Left and Right Expressions

You can select comparative operands for a rule statement to define the relationship between the left and the right expression of a rule statement. The following comparative operands are supported: This comparative operand...

Is supported for these field types:

Is equal to

All field types

Is not equal to

All field types

Is greater than: >

Date, Number, Decimal

Configuring Business Rules in SuccessFactors IF, THEN, and ELSE statements

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

31

This comparative operand...

Is supported for these field types:

Is less than: <

Date, Number, Decimal

Is greater than or equal: >=

Date, Number, Decimal

Is less than or equal: