PUBLIC

Document Version: Q4 2019 – 2019-11-08

Goal Management
© 2019 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

1 What is Goal Management?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

1.1 About this Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
1.2 Integrating Performance Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2 Getting Started - Configuration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.1 Recommended Goal Management Implementation Sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.2 Turning on Goal Management in Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
2.3 Importing a Goal Plan Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.4 Exporting a Goal Plan Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.5 Copying and Exporting Goals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.6 My Goals View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3 Email Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

3.1 Turning on Goal Email Notification in Admin Center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.2 Goal Modification Notification (daily). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.3 Creating a Scheduled Job for Using Goal Modification Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . .32
3.4 Adding or Removing Goal Links in Email Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

4 Goal Plan Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

4.1 File Header. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.2 Goal Plan Switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Removing the Add Personal Goal Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.3 Goal Plan Template Elements and Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.4 Usage of HTML in Goal Management Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
4.5 Goal Feedback Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
4.6 Automatic Goal Numbering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
4.7 Objective Weight Rules and Objective Count Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Objective Weight Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
Objective Count Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
4.8 Defining Category and Default-Category. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4.9 Adding Goal Wizard Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
4.10 Defining Goal Plan Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
4.11 Configuring Custom Checkbox. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
4.12 Working with the Visibility field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Configuring the Visibility field in the Goal Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
Enabling Users to Edit the Visibility Field in the Goal Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
4.13 Goal Feedback Field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Goal Details Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Goal Management
2 PUBLIC Content
4.14 Defining Column Width in Goal Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
4.15 Defining Goal Plan Field Display and Ordering in a Performance Management v12 Acceleration Form
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
4.16 Custom Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
Custom Calculation Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
Custom Calculation DTD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Calculations, Functions and Operators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
Sub-goal Auto-population Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Calculating Total Score of Goal Plan or Category. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Calculating Ratings or Scores for Sub-goals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.17 Using Goal Plan User Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

5 Goal Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
5.1 Turning on Goal Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
5.2 CSV File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
5.3 Mapping Templates to Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
5.4 End User (Non-Admin) Upload for goal Create/Update/Delete. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
5.5 Understanding Goal ID, GUID, & SUBGUID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
5.6 Import File Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Error Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
5.7 Goal Import Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
5.8 Goal Import Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
5.9 Goal Import FAQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
How to ensure importing goals respects automatic numbering?. . . . . . . . . . . . . . . . . . . . . . . . . . . 107
5.10 Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

6 Transferring Goals Between Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

7 Enabling Goal Execution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

7.1 Goal Plan Template Modifications to Enable Goal Execution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
7.2 Goal Plan Layout Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
7.3 Enabling Goal Execution in Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
7.4 Admin Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
7.5 Meeting Agenda Planner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
7.6 Useful Tips for Goal Execution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

8 Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121
8.1 What Are Role-Based Permissions?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Permission Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Permission Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Grant Permission Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .135
What are Rules in RBP?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143
8.2 Role-Based Permissions for Goal Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Goal Management
Content PUBLIC 3
8.3 Action Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
8.4 Roles in Goal Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
8.5 Field Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151
8.6 Cascader Role. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152
8.7 Table Field Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
8.8 Table Column Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
8.9 Matrix Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
8.10 Goal Execution Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
8.11 Goal Plan States. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Locking and Unlocking of a User's Goal Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Change Locked / Unlocked State on Form Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161
8.12 Settings for SuccessFactors in the Home Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

9 Goal Management Home Page Tile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

9.1 Setting up the Goals Management Home Page Tile without RBP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
9.2 Setting up the Goals Management Home Page Tile with RBP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
9.3 Accessing the Goal Management Tile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
9.4 Goal Notifications on To Do Tile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
9.5 Configuring Goal Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

10 Group Goals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

10.1 Enabling Group Goals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
10.2 Creating a Group Goal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
10.3 Assigning a Group Goal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171

11 Team Goals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

11.1 Creating a Team Goal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
11.2 Sharing or Unsharing a Team Goal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
11.3 Assigning or Unassigning a Team Goal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179
11.4 Editing or Deleting a Team Goal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

12 Editable Fields for Group Goals and Team Goals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

13 Initiatives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
13.1 Enabling Initiatives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
13.2 Creating an Initiative Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
13.3 Assigning an Initiative Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
13.4 Sharing an Initiative Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
13.5 Manage Initiatives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
13.6 Reporting on Inititatives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
13.7 Aligning Personal Goals to Assigned Initiatives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

14 Goal Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191

14.1 Mapping of Goal Library Content to Goal Plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Goal Management
4 PUBLIC Content
14.2 Goal Library File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
14.3 Importing a Goal Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

15 Creating Goals and Ratings with Achievement Lookup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

15.1 Sample Use Case. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
15.2 Metric Lookup Basics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
15.3 Calculation Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Step. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Interpolation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
15.4 Out of Bounds Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
15.5 Display Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
15.6 Automatic Rating Scale Population. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
15.7 Automatic Actual Rating Population. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
15.8 Automatic Target and Rating Scale Population. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203
15.9 Numeric vs. Text Target Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
15.10 Non-Linear Step Warning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
15.11 Detailed Miscellaneous Behaviors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
15.12 XML Example for Goals and Ratings with Achievement Lookup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
15.13 Auto-Create Target Entries for Metric (Achievement) Lookup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

16 Mass Upload for Assigning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210

16.1 Accessing Mass Assign Button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
16.2 Downloading CSV Header Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211
16.3 Running the Import Job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
16.4 Mass Assign Assumptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

17 Mobile Goals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

17.1 Enabling Mobile Goals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
17.2 Installing SAP SuccessFactors HCM Mobile Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
17.3 Accessing Goal Plan on the Mobile Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
17.4 Adding a New Goal using the Mobile Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
17.5 Editing a Goal using the Mobile Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
17.6 Deleting a Goal using the Mobile Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
17.7 Adding Comments to a Goal using the Mobile Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224
17.8 Updating or Deleting Goal Comments using the Mobile Application. . . . . . . . . . . . . . . . . . . . . . . . . . . 225
17.9 Default Values in Mobile Goals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

18 Integrating Continuous Performance Management with Goal Management. . . . . . . . . . . . . . . . . 227

19 Data Protection and Privacy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

19.1 Data Protection and Privacy Content is Centralized. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
19.2 Data Retention Management Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

20 Using the Check Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Goal Management
Content PUBLIC 5
20.1 Benefits of the Check Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
20.2 Check Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
20.3 Creating Support Tickets from the Check Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
20.4 Using the Quick Fix Feature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Goal Management
6 PUBLIC Content
What’s New in Goal Management

An overview of the most important updates made to this document in recent releases.

Q4 2019

The following table summarizes changes to this guide for the Q4 2019 release:

What's New Description More Information

November 9

Added two prerequisites for transfer­ You’re granted the permission Manage Transferring Goals Between Users [page
ring goals between users 109]
User Goal Transfer . Additionally, when
you transfer goals between users, the users
filled in the Transfer From Employee and the
Transfer To Employee fields should be in the
target population of your permission role.

Added information about the field The standard field "obj-plan-field1" reinforces Defining Goal Plan Fields [page 56]
"obj-plan-field1" messages to employees on why they are exe­
cuting on the goals assigned to them.

Added a note about DELETE action When you delete a goal library, make sure Importing a Goal Library [page 193]
you apply DELETE actions to all leaf nodes in
addition to the root node.

Q3 2019

The following table summarizes changes to this guide for the Q3 2019 release:

What's New Description More Information

August 9

Added information about unsupported Mobile Goals doesn't support Smart Goal Mobile Goals [page 214]
features in Mobile Goals Wizard and adding goal from Goal Li­
brary.

Updated the Elements of Goal Plan Tem­ You can add the element "learning-activi­ Goal Plan Template Elements and Attrib­
plate table ties template-id" to the Goal Plan Tem­ utes [page 38]
plate to associate a goal with learning ac­
tivities.

Added information about enabling Goal If you want to hide positions of users, you Using Goal Plan User Search [page 93]
Management People Selector can enable Admin Center Goal
Management Feature Settings Enable
Goal Management People Selector .

Goal Management
What’s New in Goal Management PUBLIC 7
What's New Description More Information

Added a note about using Beta Goal Im­ We’ve applied an upper limit on the total Limitations [page 108]
port number of goals you can import in one go
with the Beta Goal Import tool. Now, if
the import file contains more than
30,000 goals, the import doesn't go
through.

Added a note about seeing suggestions If you want to see suggestions from Goal Adding Goal Wizard Option [page 54]
from the Goal Library Library, you need to keep Disable
autocompletion find in the UI unchecked
in Provisioning.

Added a note about defining category in Defining at least one category is consid­ Defining Category and Default-Category
goal plan template ered a best practice. It allows customers [page 52]
to use more of the tiles from the Success­
Store since some tiles require a category
to function.

Updated the description for default-value The field types "textarea" and "bool" are Defining Goal Plan Fields [page 56]
field supported for default value.

Updated the information about removing You can remove the option to add Removing the Add Personal Goal Option
add Personal Goal option Personal Goal in the pop-up window for [page 37]
Creating a New Goal to have usuers cre­
ate library or group goals instead of per­
sonal goal.

Added information about group goals Group Goal v2 supports data synchroni­ Group Goals [page 168]
zation between Performance Manage­
ment and Goal Management while Group
Goal v1 doesn't support.

Updated limitations of initiatives You can't associate goals from goal libra­ Initiatives [page 183]
ries with initiatives upon creation. How­
ever, you can edit the goals to associate
them with initiatives later.

Q2 2019

The following table summarizes changes to this guide for the Q2 2019 release:

What's New Description More Information

May 10

Added information about GUID The GUID in the Report-Table report (also Understanding Goal ID, GUID, & SUB­
known as ad hoc report) is used for goals GUID [page 101]
through Beta Goal Import, rather than
from Goal Library.

Added information about action search Replacing Objectives with Goals in Provi­ Turning on Goal Management in Provi­
for Beta Goal Import sioning might impact action search re­ sioning [page 23]
sult.

Goal Management
8 PUBLIC What’s New in Goal Management
What's New Description More Information

Added information about goal pan tem­ The deployment descriptor in the XML File Header [page 35]
plate deployment descriptor template has been updated. Use the up­
dated deployment descriptor (the
DOCTYPE line) in your goal plan tem­
plate.

Added a topic about Goal Plan user If you are using TGM v12, you can now Using Goal Plan User Search [page 93]
search see not only names but also positions of
your managers, peers, and direct reports
with Goal Plan user search. You can also
include inactive, global assignment, and
concurrent users in your search. You
must have the User Search permission
and the Goal Plan Permissions to use the
function.

Added a topic about transferring goals As an Admin, you can transfer goals be­ Transferring Goals Between Users [page
between users tween users. 109]

Added a note about Goal Comment Noti­ If you enable Goal Comment Notification, Turning on Goal Email Notification in Ad­
fication make sure that the corresponding email min Center [page 30]
template is configured properly. Other­
wise, users might encounter error when
adding comments to goal plans.

Added information about bool field ele­ The goal plan template element type Defining Goal Plan Fields [page 56]
ment type bool is also supported. It is used for
checkboxes.

Added a topic about configuring check­ Custom checkbox field can be configured Configuring Custom Checkbox [page
box with the bool attribute for the Add Goal and Edit Goal dialogs. 70]
The type attribute bool can be used in
the field-definition to display a checkbox.

Removed a topic about legacy standard Role-based permissions are pushed to all N/A
permissions from the guide customers. The legacy standard permis­
sions are no longer relevant.

Q1 2019

The following table summarizes changes to this guide for the Q1 2019 release:

What's New Description More Information

March 09

Added information about the new-obj- If you set the new-obj-share- Goal Plan Template Elements and Attrib­
utes [page 38]
share-status-public attribute status-public attribute to "true",
the status of newly created goals is pub­
lic. If you set the attribute to "false",
the status is private.

Goal Management
What’s New in Goal Management PUBLIC 9
What's New Description More Information

Added information about the The viewdefault attribute deter­ Defining Goal Plan Fields [page 56]
viewdefault attribute mines whether or not the View Option (or
Display Option as it is sometimes called)
for this field is default on or off in the plan
view. If left unspecified, the default is
"on". For TGMv10 viewdefault is ig­
nored for 508 compliance. All the fields in
the first rows are displayed by default.

Added information about diff and NOW NOW returns the current server time. For Calculations, Functions and Operators
example, diff(NOW, d1) equals days from [page 85]
d1 to NOW

Added a topic about turning on importing If you have the Import Goals permission, Turning on Goal Import [page 95]
goals feature in Admin Center you can enable the goal importing func­
tionality directly in Admin Center and ac­
cess the Beta Goal Import option.

Added a chapter about role-based per­ Added centralized information about What Are Role-Based Permissions?
missions what is role-based permissions, and how [page 121]
to enable role-based permissions.

Updated the topic about role-based per­ Removed steps about how to grant per­ Role-Based Permissions for Goal Man­
missions in Goal Management missions. Consolidated role-based per­ agement [page 144]
missions for Goal Management.

Added a topic about how to create a If you have the New Add Group Goal Creating a Group Goal [page 170]
group goal Creation permission, and the group goal
feature is enabled in your instance, you
can create group goals on the goal plan
page.

Added a topic about how to assign a If you have the Add Group Goal Assigning a Group Goal [page 171]
group goal Assignment permission, and the group
goal feature is enabled in your instance,
you can assign group goals on the goal
plan page.

Added four topics about team goals Four new topics are added to the guide Creating a Team Goal [page 177]
about how to create, share, unshare, as­
sign, unassign, edit, and delete team Sharing or Unsharing a Team Goal [page
goals. 178]

Assigning or Unassigning a Team Goal

[page 179]

Editing or Deleting a Team Goal [page

180]

Updated the sample code for the Updated the code sample about how to Editable Fields for Group Goals and Team
cascade-update attribute configure weight so that everyone who Goals [page 181]
has proper permission can edit it for a
group goal.

Goal Management
10 PUBLIC What’s New in Goal Management
What's New Description More Information

Added four topics about how to use ini­ Four new topics are added to the guide Enabling Initiatives [page 184]
tiative groups about how to enable, create, share, as­
sign, and align personal goals to an initia­ Creating an Initiative Group [page 185]
tive group.
Assigning an Initiative Group [page 186]

Sharing an Initiative Group [page 187]

Updated two topics about initiatives Updated two topics about what is initia­ Initiatives [page 183]
tive and initiative group, and how to man­
age initiatives in general. Manage Initiatives [page 188]

Added information about subgoal per­ For subgoals, table column permissions Table Column Permissions [page 155]
missions are supported. But you cannot define
permissions according to rows.

Added two topics about goal library Two new topics are added to the guide Goal Library [page 191]
about what is goal library, and how to im­
port a goal library to your instance. Importing a Goal Library [page 193]

Updated the topic about goal library file Simplified the topic to cover only about Goal Library File [page 192]
goal library file.

Updated information about supported Column ordering is controlled through Display Configurations [page 200]
values of the order atttribute the table-column attribute <order>.
Accepted values are asc, desc, and
both. The default value is both.

Updated information about mass assign For mass assignment of goals, grant per­ Mass Upload for Assigning [page 210]
goals missions for assigning group goals and
for importing the goals in the application.

Updated topic about accessing mass as­ If you have goal importing and assigning Accessing Mass Assign Button [page 210]
sign button permissions, you can access the Mass
Assign button from the Actions drop­
down on the Goal Plan page.

Updated topic about generating CSV With proper permission, you can gener­ Downloading CSV Header Template
header template and populate it with as­ ate a CSV header tempalte by selecting [page 211]
signment information Generate CSV header from the Actions
dropdown on the goal plan page.

Updated information about Modification In the case of copying an existing goal Email Notifications [page 29]
Email Notifications from one goal plan to another goal plan,
two email notifications are sent.

Added a topic about default values in Mo­ If you have configured default values for Default Values in Mobile Goals [page 225]
bile Goals fields in a goal plan, you can now see
those default values from mobile as well.

Q4 2018

The following table summarizes changes to this guide for the Q4 2018 release:

What's New Description More Information

November 02

Goal Management
What’s New in Goal Management PUBLIC 11
What's New Description More Information

Added information about move goal up If you do any type of sorting in the goal Automatic Goal Numbering [page 46]

and move goal down functionalities plan, for example, by Goal Name, the
move goal up and move goal down func­
tionalities do not take effect. To resolve
this issue, you may reset the sorting cri­
teria by adding the obj-plan-numbering
element.

Added information about target popula­ For users who migrated from non-RBP to Role-Based Permissions for Goal Man­
tion RBP, if you cannot load the goal plan page agement [page 144]
but you have the RBP permission, the
solution is to first deselect and then rese­
lect Everyone under Target Population

through Permission Role Detail Edit

Granting . The root cause can be Target

Population query failure due to faulty
configuration or dirty data.

Added detailed Interpolation calculation When the actual achievement is not an Interpolation [page 198]

explanation and examples exact number in the metric lookup table,

and if the calculation method is interpo­
lation, then (actual_achievement - ach­
ievement_low)/ (achievement_high-ach­
ievement_low) = (actual_rating - rat­
ing_low ) / (rating_high-rating_low).

Added a topic for actual rating auto-pop­ You can configure the goal plan to calcu­ Automatic Actual Rating Population
ulation late actual ratings automatically based [page 202]
on the metric lookup table and actual
achievements.

Added information about email notifica- The Goal Modification Notification mes­ Email Notifications [page 29]
tions sage does not include feedback or com­
ments. You may check feedback and
comments from the Goal Comment Noti­
fication message.

Restructured topics related to Calcula­ The Calculation Types topic is divided Calculation Types [page 196]
tion Types into one general topic and two subtopics
for the calculation methods of step and Step [page 197]
interpolation.
Interpolation [page 198]

Goal Management
12 PUBLIC What’s New in Goal Management
What's New Description More Information

Restructured topics related to Goal Man­ The Setting Up the Goal Management Setting up the Goals Management Home
agement Home Page tile Home Page Tile topic is divided into two
Page Tile without RBP [page 163]
subtopics. The Accessing the Goal Man­
agement Tile topic is updated. All three Setting up the Goals Management Home
topics are under the Goal Management Page Tile with RBP [page 164]
Home Page Tile now.
Accessing the Goal Management Tile
[page 165]

Added information for display-alignment- The goals view displays the owner, goal Goal Plan Template Elements and Attrib­
format name, and other fields that are hard utes [page 38]
coded to display. The names view shows
the goal owner name and contains a link
to view the goal plan of the user.

Added sample code for Goal Details tab Updated the XML Snippet for the <form- Goal Details Tab [page 75]
layout> section of the Goal Plan XML to
access the threaded feedback comments
from the Goal Details tab within the Per­
formance Management form.

Added information for goal name Do not include special or non-English Goal Plan Template Elements and Attrib­
characters within the obj-plan-name tag. utes [page 38]
For example, # or é. You might encounter
error when you export the goal plan.

Added information for Goal email notifi- Updated with examples to explain the job Creating a Scheduled Job for Using Goal
cation time setting logic of Goal email notifica- Modification Notifications [page 32]
tion.

Added information for Mobile Goal The fields and sections you see that in Adding a New Goal using the Mobile Ap­
your Mobile goal are consistent with the plication [page 222]
configuration of the Goal Plan on web.

Added information about importing Updated the Goal Import example to re­ Goal Import Examples [page 103]
Goals flect that SUBGUID is needed when im­
porting Goal comments.

Added information about CSV file format Updated the description about the SUB­ CSV File Format [page 96]
GUID head type.

Added a topic about Goal Modification A Goal Modification Notification is trig­ Goal Modification Notification (daily)
Notification gered when a public goal is created, [page 31]
modified, or deleted. You can customize
Goal Modification Notification Messages
in Admin Center.

Added information about Mobile Goals The Admin Access for Goal ODATA API Enabling Mobile Goals [page 215]
Export permission is for the Data Protec­
tion Officer role only. If this permission is
enabled, mobile users can see previously
deleted goals and may encounter system
disfunction when they try to add, edit, or
delete goals on a mobile device.

Goal Management
What’s New in Goal Management PUBLIC 13
What's New Description More Information

Added information about the expand- When this attribute is set to "true", Goal Plan Template Elements and Attrib­
collapse-categories attribute user can expand/collapse categories on utes [page 38]
GM page. This attribute only works when
pager-max-objs-per-page="0".

Added a topic about turning on Goal Configure both in Admin Center and Pro­ Turning on Goal Email Notification in Ad­
email notification in Admin Center visioning to turn on Goal email notifica- min Center [page 30]
tions. In Admin Center, you can choose
Goal email notification types and cus­
tomize your email notification template.

Added a topic about adding or removing To enable a link to the Goal Plan in the Adding or Removing Goal Links in Email
Goal Plan links in Goal email notifications email notification, you must enable both Notifications [page 34]
the Consolidate by employee and the
Enable HTML email notifications in Admin
Center. You can disable either one to re­
move the link.

Added a topic about notifications on To As part of the smart suite framework, Goal Notifications on To Do Tile [page
Do tile events occur in SAP SuccessFactors Em­ 165]
ployee Central can trigger Goal Manage­
ment to do items on the To Do tile.

Added a topic about how to turn on or off You can turn on or off Goal notifications Configuring Goal Notifications [page 166]
Goal notification on To Do tile in Admin Center. Please note that turning
off Goal notifications will only stop the
display of future to do items on the To Do
tile on Home Page. Existing to do items
are not affected.

Added information about the A note is added the instructions- Goal Plan Template Elements and Attrib­
instructions-viewdefault at­ viewdefault attribute only works for utes [page 38]
tribute GM v11.

Q3 2018

The following table summarizes changes to this guide for the Q3 2018 release:

What's New Description More Information

August 03

Updated Turning on Goal Management in Added a note to clarify that a goal page Turning on Goal Management in Provi­
Provisioning loading issue can be solved by enabling sioning [page 23]
the TGM Version 10 UI option in Provi­
sioning.

Updated the Standard goal field ids table Added a note to indicate the proper UI Defining Goal Plan Fields [page 56]
and PDF print behavior with respect to
the name field and it’s position in the goal
plan layout table structure.

Goal Management
14 PUBLIC What’s New in Goal Management
What's New Description More Information

Editable Fields for Group Goals and Team Updated the configuration guide to clar­ Editable Fields for Group Goals and Team
Goals ify that Team Goals follows the same per­ Goals [page 181]
missions and behavior as Group Goals
2.0. A note was added as well to reflect
that field editability in a Team Goal with
respect to cascading follows the same
rules for Group Goals.

Updated the Defining Goal Plan Fields Added a note to clarify the existing UI be­ Defining Goal Plan Fields [page 56]
havior in the goal plan when a single long
text string is added to a field and a hori­
zontal scroll bar appears in the UI.

Usage of HTML in Goal Management Updated implementation guide to clarify Usage of HTML in Goal Management
Templates that customers edit and manage tem­ Templates [page 45]
plates in Admin Center.

Updated the Table field elements Updated the configuration guide to clar­ Defining Goal Plan Fields [page 56]
ify proper configuration for controlling
the width of the text fields within a sub­
goal table. The width attribute only works
when paired with the type of
textarea.

Updated the Goal Plan States Updated the configuration guide to clar­ Goal Plan States [page 159]
ify that when a goal state is in the locked
position, and the customer has group
goals enabled, the Add Goal button con­
tinues to appear. Group Goals does not
respect goal plan state configuration. The
customer also in this case had been
granted permission to create group
goals.

Updated the Manage Initiatives Added a note to clarify that users are rec­ Manage Initiatives [page 188]
ommended to load fewer than 100 initia­
tives in the Manage Initiatives page to en­
sure page loading performance.

Updated the What is Goal Management Added a note to clarify that modifying What is Goal Management? [page 19]
data directly might cause system mal­
function therefore not recommended.

Update the Sample Use Case Updated the configuration guide about Sample Use Case [page 195]
the capability of using calculated ratings
for Group Goals 2.0.

Goal Management
What’s New in Goal Management PUBLIC 15
What's New Description More Information

Updated the XML Example for Goals and Added the rate-on-form-option XML Example for Goals and Ratings with
Ratings with Achievement Lookup attribute of rating scale sample code. Achievement Lookup [page 206]

Updated Defining Column Width in Goal Updated the configuration guide to clar­ Defining Column Width in Goal Plan
Plan ify best practices when configuring the [page 76]
subcategory fields and more broadly how
best to configure fields in the goal plan
layout.

Updated the Custom Fields section in Updated the configuration guide to clar­ Defining Goal Plan Fields [page 56]
Defining Goal Plan Fields ify that to view custom fields in the align­
ment view requires adding the attribute
reportable to the XML template as
part of field definition.

Updated the Setting up the Goals Man­ Updated the configuration guide to clar­ Setting up the Goals Management Home
agement Home Page Tile without RBP ify that Goal Management does not sup­ Page Tile without RBP [page 163]
port the To Do tile. No due date notifica-
tion of goals shows up on the To Do tile.

Updated the Email Notifications and the Added notes to clarify that Employees Email Notifications [page 29]
Action Permissions need the Private Access permission to re­
Action Permissions [page 146]
ceive email notifications for private goals.

Subgoal Auto-population Rules Added a topic to clarify that the sub- Sub-goal Auto-population Rules [page
goals can be configured with one of the 89]
two calculation types, per column or per
row.

Updated the Detailed Miscellaneous Be­ Added information to clarify that if the Detailed Miscellaneous Behaviors [page
haviors use-min-target-as- 205]
rating="true" then the minimum
possible rating value will always be the
minimum rating. The default value of the
use-min-target-as-rating is
"false", so adding use-min-
target-as-rating="false" or
simply leaving this tag out of the XML,
the results are the same.

Goal Management
16 PUBLIC What’s New in Goal Management
Important Technical Notices

Replacement of Goal Management v11

SAP SuccessFactors Goal Management has enhanced its latest UI version, Goal Management v12, in line with the
overall SAP Fiori design standards, and is recommended for use by all customers now. All major functional gaps
between the older versions and the v12 version were closed with the Q3 2015 release.

Key Dates

● End of Development Phase: The time leading up to the end of maintenance for a feature or version. During this
time, no new features or enhancements will be delivered and only high priority bug fixes will be considered.
There is no change in customer support during this phase. Customers are encouraged to start planning their
upgrade for the feature or version.
Since Q3 2015, functional enhancements are only being made for Goal Management v12.
● End of Maintenance: The date after which no further bug fixes or patches will be delivered for the feature or
version. Customer support is limited to how-to help.
End of maintenance for Goal Management v11 is Q1 2018.
● Replacement Date: The date after which the feature or version is permanently disabled and no longer
supported.
Replacement of Goal Management v11 is planned for Q1 2019, after which Goal Management v11 will no longer
be supported.

Migrating to Goal Management v12

Making the move to Goal Management v12 is a simple upgrade of the user interface.

Go to Admin Center Upgrade Center and select the Goal Management User Interface V12 upgrade.

More Information

● Visit the SAP SuccessFactors Customer Community for all the latest updates and discussions.
● Refer to the Goal Management guide for details on setting up your system.

Goal Management
Important Technical Notices PUBLIC 17
Retirement of Goal Execution

The Goal Execution tool in Goal Management will soon be retired.

Important Dates

● End of Development Phase: The time leading up to the end of maintenance for a feature or version. During this
time, no new features or enhancements will be delivered and only high priority bug fixes will be considered.
There is no change in customer support during this phase. Customers are encouraged to start planning their
upgrade for the feature or version.
No functional enhancements are being made or planned for the Goal Execution tool. Only high priority or
critical bugs, if reported, will be fixed.
● End of Maintenance: The date after which no further bug fixes or patches will be delivered for the feature or
version. Customer support is limited to how-to help.
The end of maintenance for Goal Execution tool is planned for the second half of 2019.
● Retirement Date: The date after which the feature or version is permanently disabled and no longer
supported.
The retirement date for Goal Execution is planned for the second half of 2020.

 Note

Currently, the end of maintenance and retirement dates are tentative and subject to change.

Migration Information

The recommended replacement for Goal Execution is Continuous Performance Management. To learn more about
how you can start using this tool, see the Continuous Performance Management guide.

More Information

● Community Forum on the Retirement of Goal Execution

● Customer Community Performance and Goals Product Page
● Events/Recordings on Customer Community
● Continuous Performance Management Demo

Goal Management
18 PUBLIC Important Technical Notices
1 What is Goal Management?

SAP SuccessFactors Goal Management enables employees and managers to align individual goals with company
business objectives.

SAP SuccessFactors Goal Management helps organizations ensure that all employees are aligned and working on
the things that matter most so that the organizations can bridge the strategy and execution gap and stay on the
path to success.

What are the main features of Goal Management?

The main Goal Management (GM) features are:

● Goals Library of more than 500 SMART (Specific, Measurable, Attainable, Realistic, and Timely) goals provides
instant recommendations
● Goals can be reinforced everyday with intuitive updating of effort, success probability, and comments
● Compliance is improved by providing evidence of an objective review process. Plus, Legal Scan helps facilitate
compliance with Sarbanes-Oxley and other regulations
● Managers can set cascading goals and see individual, team, or company-wide progress.

 Note

Cascading goals allows you to edit the goal content that you copy from one user before you paste it as another
user's goal. Whereas, Linking enables you simply add a link between two existing goals of different people
without transfer of content.

 Caution

Do not try to launch the Goal Plan in an iFrame. An IFrame (Inline Frame) is an HTML document embedded
inside another HTML document on a website. The IFrame element is often used to insert content from another
source into a Web page. However, Goal Management does not support the use of IFrame.

 Caution

Do not modify data in the database which might introduce dirty data and unexpected system performance.

 Caution

To improve the performance of Goals Ad Hoc Report, the relevant logical table is refactored. After this
enhancement, you need to select data sets again when running existing Goals Ad Hoc Report. Otherwise, your
report might include the data for all goal templates. In addition, when editing and previewing the existing report,
you will also be prompted to select a data set again.

Goal Management
What is Goal Management? PUBLIC 19
1.1 About this Document

This implementation guide is intended for the following target groups:

● Professional Services consultants who implement Goal Management for customers

● Solution Consultants who set up demo systems

1.2 Integrating Performance Management

Goals in Goal Management may be used on a stand-alone basis with no other SAP SuccessFactors modules,
although typically customers purchase both Goal Management and Performance Management. Goals entered into
Goal Management may be auto-populated onto a Performance Management form.

To integrate Performance Management, the following prerequisites must be met:

● Performance Management has been configured as described in Implementing Performance Management.

Goal Management
20 PUBLIC What is Goal Management?
2 Getting Started - Configuration Overview

When configuring the template for goal plans, you will edit the goal plan XML file.

In the XML file you can do the following:

● Specify the name of the plan.

● Define the goal categories.
● Define the fields to be used in the Goal plan.
● Assign which roles have READ and WRITE permissions for each field in the goal plan.
● Assign permissions to use TGM features such as Cascade Selected, Delete Selected.
● Define the appearance of the goal in the goal plan.
● Define the appearance of the goals in a PM Form.
● Define which fields will be listed and the order in which they will appear in the Add Goal window.
● Define which fields are required. The red asterisk next to a field name indicates that the user must enter data in
the field.

 Note

Goal Management does not support competencies.

2.1 Recommended Goal Management Implementation

Sequence

To help you with your implementation, we recommend following this proven formula. This formula is based on
Professional Services expertise.

 Remember

As a customer, you do not have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner. If you are no longer working with an implementation partner, contact SAP Cloud
Support.

Step Number Name Description

1 Set up Goal Management in Provisioning The initial configuration tasks to set up Goal Management. For more
information see: Turning on Total Goal Management in Provisioning
[page 23]

Goal Management
Getting Started - Configuration Overview PUBLIC 21
Step Number Name Description

2 Download and Configure Goal Plan Tem­ Download the Goal Plan Template which is used to define the fields
plate and sections your users will fill out for their goal plans. You import
the template, review and carry out iterative edits on the XML. For
more information see:

● Importing a Goal Plan Template [page 23]

● Exporting a Goal Plan Template [page 25]

3 Define Goal Categories Create goal categories, which are used to segment the goal plan. For
more information see: Defining Category and Default-Category
[page 52]

4 Define Goal Fields and Actions Define goal fields and actions including names, start date, metrics,
and so on. You configure the visibility and function of those fields
and actions. For more information see: Goal Plan Template Elements
and Attributes [page 38]

5 Define Sub-tables: Targets, Tasks, Mile­ Define the sub-tables for the goal field definitions. For more informa­
stones, Comments tion see: Defining Goal Plan Fields [page 56]

6 Define Goal Visibility Set up goal visibility, which determines whether goals are public or
private. CSV File Format [page 96]

7 Define SMART Goal Wizard Enable the SMART Goal Wizard, if required. For more information
see: Adding Goal Wizard Option [page 54]

8 Define Goal Execution You can use goal execution to take your large, strategic company
goals and break them down so that your employees understand how
their daily tasks connect with your overall strategy. For more infor­
mation see: Enabling Goal Execution [page 111]

9 Set up Goal Library Mapping Define a goal library which can be used to create individuals goals.
For more information see: Mapping of Goal Library Content to Goal
Plans [page 191]

10 Set up Goal Alignment Goal Alignment creates the connection, sometimes called linkage,
between goals on the goal plans of people throughout a company.

11 Set up role based permissions Set up the authorization concept of role-based permissions. For
more information see: Permissions [page 121]

12 Set up field and action permissions The field and action permission definitions specify who gets to see
certain fields and actions, read and edit them. You define and config-
ure read, write, or no permission to fields and actions on the Goal
Plan by relationship to the subject of the form. For more information
see: Permissions [page 121]

13 Define Goal Plan and Form Layout Define the Plan Layout, which controls how the fields look in Goal
Management – on the Goal Plan itself. In addition, the Form Layout
controls how the goal fields will appear in the Performance Manage­
ment form, if goals are pulled from the goal plan into the PM form.
For more information see: Defining Goal Plan Fields [page 56]

Goal Management
22 PUBLIC Getting Started - Configuration Overview
2.2 Turning on Goal Management in Provisioning

When you turn on Total Goal Management for a customer, you’re turning on Total Goal Management for the entire
company. That is, any user accessing the "goals" or "objectives" hyperlink, or tab within the application will invoke
the Total Goal Management module.

1. Log in to Provisioning.
2. Select the company for which Total Goal Management should be enabled.
3. Under Edit Company Settings, select Company Settings.
4. Check the box next to Goal Management Suite and select Total Goal Management in the drop down list, and My
Goals Tab.

 Note

If the customer encounters blank page when loading Goals, select the TGM Version 10 UI option in
Provisioning as well to solve the issue. Please note that not all customers would experience the page
loading issue when the option isn’t enabled.

5. Optionally, if the customer prefers the term goal instead of objective, select Goal in the drop down next to the
Change Objective into option.

 Note

Replacing the text Objective with the text Goal in an instance can impact Action Search results. Do
thorough search result test after switching from one term to the other. You can add customized search
terms using the Manage Action Search option in Admin Center.

 Note

You can use this option when there’s only US English language needed. If there are other languages
enabled for customers, this option applies the US English term Goals to all other languages, overriding the
local translation for Objectives. The best practice is to update labels with Text Replacement.

 Remember

As a customer, you do not have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner. If you are no longer working with an implementation partner, contact SAP Cloud
Support.

2.3 Importing a Goal Plan Template

When you turn on Goal Management for a customer, you must also import a goal plan template for the company.
Otherwise, when a user tries to access Goal Management, an error appears in the browser.

There is no interface in Provisioning that allows you to edit the XML of a goal plan template. You must create and
edit your goal plan templates using an XML editor and import the goal plan to see your changes. Details for
configuring the goal plan template in an XML text file are described in this configuration guide.

Goal Management
Getting Started - Configuration Overview PUBLIC 23
  Note

Autoprovisioning is also available for some components. The Performance & Goals (Align and Perform) bundle
and includes the following components: Platform, GM, PM 360 and Calibration. Autoprovisioning allows for
these components to be turned on and a base configuration set to be available.

To import a goal plan template for a select company, follow these steps:

1. Log in to Provisioning.

 Remember

As a customer, you do not have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner. If you are no longer working with an implementation partner, contact SAP Cloud
Support.

2. Select your target company to import the Goal Management template.

3. Under the Managing Plan Template section, select Import/Update/Export Objective Plan Template.
4. Browse and select the goal template file that you prepared.
5. Click Upload.

 Note

when importing a modified goal plan template over an existing one, your changes are reflected in the
application right away, even if goals already exist within that goal plan.

Multiple Goal Plans

When multiple goal plans are imported into an instance, you can select the radio button to specify which plan is
rendered by default when you invoke Goal Management.

If you have multiple active goal plans, you can switch between plans through the Goal Plan drop down under the
Goal Plan tab.

Goal Management
24 PUBLIC Getting Started - Configuration Overview
2.4 Exporting a Goal Plan Template

You can export a goal plan template to reuse it or to update it.

You export a goal plan from the same page in Provisioning that you used to import a goal plan. To export a goal plan
template for a select company, press the icon under the Export column. Although Provisioning offers the capability
of exporting goal plan templates, you may still want to consider maintaining a source copy of your template in a file.
The primary advantage in doing so is to preserve any comments that you may have added to date and track
updates that you make to the template (for example, a change log) or to preserve comments in the template that
help distinguish one section from another.

 Note

Comments are stripped from the goal plan template when you import the template and hence any templates
that you export will not include your comments.

 Remember

As a customer, you do not have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner. If you are no longer working with an implementation partner, contact SAP Cloud
Support.

Goal Management
Getting Started - Configuration Overview PUBLIC 25
2.5 Copying and Exporting Goals

You can copy goals between goal plans as well as export the goals from a particular goal plan. For example, you
want to allow a user to copy a goal from the 2015 goal plan to the 2016 goal plan.

Copying Goals from Other Goal Plans

You can enable the wizard for copying goals between goal plans by selecting the Admin Center Goal
Management Feature Settings TGM/CDP Objective Transfer Wizard option. For example, a user can copy a goal
from the 2014 goal plan into the 2015 goal plan.

Exporting Goals from Goal Plan (End User)

Exporting goals has useful benefits in certain circumstances:

● If you need to make universal changes for a large number of goals, or update values such as dates, status, and
so on, you can export the goals, modify them, and then import them again. Using this procedure, you do not
need to repeat the same update for each individual goal.
● You can also export goals if the information needs to be consumed by another system.

A user can export the goals from a particular goal plan page based on the permissions configuration. You need to
add a new action permission export-goal in the goal plan template. The configuration is as follows:

<permission for="export-goal">
<description><![CDATA[ Employee and Employees' manager can export the goals from
the objective plan.
]]></description>
<role-name><![CDATA[EM]]></role-name>
<role-name><![CDATA[E]]></role-name>
</permission>

2.6 My Goals View

My Goals view allows you to filter your goal list to view the goals that are most important to you.

All you have to do is pick the date range or goal status you want, and the Goal Plan instantly refreshes to display
only those goals. So you see only what you want to see. Then you can work with the goals just as you always did. Or,
you can take a look at the two status charts to get a fast visual summary. When you want to see the entire Goal Plan
again, just click See All Goals and all the goals display on the Goal Plan.

The goal summary feature adds another section to the goals page called Summary.

Configuration Information

Goal Management
26 PUBLIC Getting Started - Configuration Overview
To enable the goal filtering option, include the following XML in your TGM template: <summary-section
filter="true"/>

Disable Date Range Filter Option

The existing issue: if goal summary is enabled, goals added outside the Goal Plan date range will not display in the
plan, so users do not have a way to edit or correct the goals/dates.

Example

1. Visible Goals
1. If we create a goal with start date as 12/01/2014 and end date as 05/01/2017, it is visible as the end date is
overlapping with the date range specified in the template.
2. If we create a goal with start date as 04/03/2014 and end date as 05/01/2016, it is visible as the start date
is overlapping with the date range specified in the template.
3. If we create a goal with start date as 04/03/2014 and end date as 05/01/2015, it is visible as both the start
and the end date are overlapping with the date range specified in the template.
2. Not Visible Goals
1. If we create a goal with start date as 04/03/2010 and end date as 05/01/2011 it is not visible, as both the
start and the end date are outside the date range specified in the template
2. If we create a goal with start date as 04/03/2020 and end date as 05/01/2021 it is not visible, as both the
start and the end date are outside the date range specified in the template

A switch was added to switch on/off the date filter function. The user may list all goals with this switch, regardless
of whether or not it is in or out of the date range of the current goal plan.

Disable Date Range Filter check box in the goal summary section:

Goal Management
Getting Started - Configuration Overview PUBLIC 27
Default Setting (date range filter enabled)- note that the goals displayed are within range:

Date Range Disabled - note that the goals outside the default date range are now displayed:

Goal Management
28 PUBLIC Getting Started - Configuration Overview
3 Email Notifications

You can configure email notifications so that the target recipients can receive notifications when a goal is created,
deleted, modified, or commented upon. There are four types of Goal email notifications: Goal Creation Notification,
Goal Delete Notification, Goal Modification Notification, and Goal Comment Notification.

● Goal Creation Notification alerts a user that a goal is created for him or her.
● Goal Delete Notification alerts the goal owner when the goal is deleted by another user from the goal plan.
● Goal Modification Notification (daily) messages are sent every 24 hours if changes are made to public goals
on the goal plan of the user. The message includes created, modified, and deleted goals. Users are not notified
of changes they made themselves. The Goal Modification Notification message does not include feedback or
comments. You may check feedback and comments from the Goal Comment Notification message. Valid
tokens for this message: [[LAST_EMAIL_DATE]] [[GOAL_OWNER]] [[OBJ-PLAN-NAME]] [[OBJ_LIST]]
[[SIGNATURE].

 Remember

To use the Goal Modification Notification email notification, you must have an Objective notification email
type of scheduled job created as explained in the "Creating a Scheduled Job for Using Goal Modification
Notifications [page 32]" topic.

 Note

In the case of copying an existing goal from one goal plan to another goal plan, two email notifications are
sent. One Goal Modification Notification is sent for the Goal Plan from which the Goal is copied. The other
Goal Modification Notification is sent for the Goal Plan to which the Goal is copied.

● Goal Comment Notification alerts an employee and the manager of the employee about comments added to
the Goal Plan of the employee. The message includes [[OBJ_RECIPIENT]], [[OBJ_SENDER]],
[[OBJ_NAME]], [[OBJ-PLAN-NAME]], [[OBJ_COMMENT]], and [[OBJ_COMMENT_HERE]]. This email
notification works as follows:
○ When a manager provides feedback on the goal plan of an employee, the employee receives the email
notification.
○ When an employee adds a comment in the goal plan, as a response to the feedback of the manager, the
manager receives the email notification.
○ When someone, other than the employee or the manger (e.g., matrix manager), provides feedback on the
goal plan of the employee, both the employee and the manager receive the email notification.

 Remember

In the Goal Comment Notification email template, you can include the comment token to allow the
recipients of the email notification to read the comment directly in the email message. However, this
functionality might create a conflict with your data protection and privacy compliance. If you configure the
email notification template to include [[OBJ_COMMENT]], the comment effectively lives outside of SAP
SuccessFactors once the email is sent, and it cannot be purged using the data purge options in the
application.

Goal Management
Email Notifications PUBLIC 29
  Note

Employees need the Private Access permission to receive email notifications for private goals.

3.1 Turning on Goal Email Notification in Admin Center

To turn on Goal email notifications, you must configure both in Admin Center and Provisioning. In Admin Center,
you can select Goal email notification types and customize your email notification template.

Context

The email notifications can be turned on and off in Admin Center. When any of these email notifications are
enabled, users will receive a notification when the related actions occur. For example, if Goal Comment Notification
is enabled, when an employee adds feedback to a goal plan, the line manager will receive a notification.

Procedure

1. Go to Admin Center Company Settings E-Mail Notification Templates Settings .

2. Select types of Goal email notifications that you want to enable for your Instance:

Types of Goal Email Notifications Description

Goal Creation Notification Goal Creation Notification will be sent to a user when a Goal was created for the
user.

Goal Delete Notification Goal Deletion Notification will be sent to a user when a Goal was deleted by
manager from Direct Report's goal plan view.

Goal Modification Notification Goal Modification Notification messages are sent every 24 hours to the employee
(daily) and to the manager, if changes were made to public goal on the employee's goal
plan. The message includes created, modified, and deleted goals.

 Note
You also must create a scheduled job in Provisioning for the Goal Modification
Notification to work.

Goal Comment Notification Email notifications can be sent to the employee and the employee’s direct line
manager when threaded feedback is added to a goal plan.

Goal Management
30 PUBLIC Email Notifications
 Types of Goal Email Notifications Description

 Note
If you enable Goal Comment Notification, make sure that the corresponding
email template is configured properly. Otherwise, users might encounter error
when adding comments to goal plans.

3. Click Save Notification Settings.

Results

You have successfully enabled the e-mail notifications for Goals.

Next Steps

You can further customize Goal email notification messages through E-Mail Notification Template in Admin Center.

3.2 Goal Modification Notification (daily)

A Goal Modification Notification is triggered when a public goal is created, modified, or deleted. You can customize
Goal Modification Notification messages in Admin Center.

Recepients of Goal Modification Notification

If the sender of the Goal Modification Notification is not the goal plan owner, the owner is notified. If the goal plan
owner changes his or her own goal plan, the goal plan owner receives no Goal Modification Notification. If the
sender is not the manager of the goal plan owner, the manager of the goal plan owner receives a Goal Modification
Notification.

Features Description

Set Email Priority You can set High Priority for the Goal Modification Notification.

Customize Settings for Goal Plans You can select goal plans from the list through the link.

Goal Management
Email Notifications PUBLIC 31
Features Description

Do not send notifications for: You can exclude Goal Modification Notification for these three
conditions.
● Actions to linked Goals
● Unlinking a Goal
 Note
● Actions to cascaded Goals
Choosing Actions to cascaded Goals also disables email
notifications related to updates for Group Goals 2.0 push
down fields.

Send notification for: If Private in addition to public goal is enabled and the user has
permission to access the private goals, notifications will be
sent.

Allow notification to: If Exclude "user deletions" to goals is enabled, the goal modifi-
cation notification will not have any deletion information of the
● Exclude "user deletions" to goals
goals.
● Include a manager's matrix report(s)
● Consolidate by employee If Include a manager's matrix report(s) is enabled, the manager
will receive the notification about the goals of the matrix re­
ports

If Consolidate by employee is enabled, the manager will receive

only one notification that consolidates all the notifications of
the same goal plan of the employees.

3.3 Creating a Scheduled Job for Using Goal Modification

Notifications

You must create "Goal notification email" type of scheduled job to be able to use the "Goal Modification
Notification" e-mail notifications in Goals Management.

Context

Even if you enable the "Goal Modification Notification" e-mail notifications, using the Admin Center E-Mail
Notification Templates Settings tool, the e-mail notifications will not be sent until you have a "Goal notification
email" type of scheduled job created using the Manage Scheduled Jobs tool in Provisioning.

 Remember

As a customer, you do not have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner. If you are no longer working with an implementation partner, contact SAP Cloud
Support.

Goal Management
32 PUBLIC Email Notifications
Procedure

1. Log in to Provisioning.
2. In the Managing Job Scheduler section, click Manage Scheduled Jobs. The Manage Scheduled Jobs page
appears.
3. Click the Create New Job link. The Create New Job page appears.
4. Enter a relevant Job Name. For example, enter "Scheduled Job for Goal Notification Email".
5. In Job Owner, select an admin user responsible for managing the e-mail template notifications.
6. In Job Type, select Goal notification email from the dropdown.
7. For Job Parameters, select Today.

 Note

Do not select a date range as Job Parameters, as it can interfere with the delivery of notifications, and might
cause sending of erroneous notifications to users.

8. In Occurrence, select Recurring to ensure that the Goal email notification is sent out regularly.
9. In the Recurring Pattern section, select Daily, and select 18:00 hours as the scheduled time for executing the
job.

 Note

When you select Daily as your recurring pattern with Today as the job parameter, the preferred time for the
scheduled job should be on or after 1800 hours, so that all the goal changes for the day are covered in the
e-mail notification. The Goal email notification captures only the changes between 0 a.m. and the time that
you have selected. For example, if you select 0 a.m., no changes will be captured.

10. In Start Date, enter the starting date in the <MM/DD/YYYY> format and select a time for this scheduled job.

 Note

You must NOT enter a date and time, earlier than your current date and time.

11. Select the Send E-mail when job starts check box.
12. Click Create Job. The newly created scheduled job appears in the list of jobs on the Manage Scheduled Jobs
page.
13. For your newly created scheduled job, under Actions, select Submit.

Results

You have successfully scheduled a job for the goal email notifications. This ensures the Goal Modification
Notification e-mail notifications will be sent if you enabled the e-mail notification using the Admin Center E-
Mail Notification Templates Settings tool.

Goal Management
Email Notifications PUBLIC 33
3.4 Adding or Removing Goal Links in Email Notifications

You can add or remove a Goal Plan link in the footer of an email notification.

Context

To enable a link to the Goal Plan in the email notification, you must enable both the Consolidate by employee and
the Enable HTML email notifications in Admin Center. To remove the link from the email notification, you can simply
disable either the Consolidate by employee or the Enable HTML email notifications.

Procedure

1. Go to Admin Center Company Settings E-Mail Notification Templates Settings Goal Modification
Notification (daily) .
2. Select Consolidate by employee.
3. Click Save Notification Settings.

4. Go to Admin Center Company Settings Company System and Logo Settings .

5. Select Enable HTML email notifications.
6. Click Save Company System Setting.

Results

You have successfully enabled a direct Goal Plan link in the Goal email notifications.

Goal Management
34 PUBLIC Email Notifications
4 Goal Plan Templates

Categories and fields for the users' goal plans are defined in a goal plan template.

Many of the behaviors of the Goal Management Product are configured through the Goal Management Template.
The goal plan template is specified in an XML file.

 Note

The “Swap-Goal-Link” option is not supported in the DTD for Goal Management v12.

Elements that make up a template are:

● File header
● Template Configuration Options containing Objective Plan Data including:
○ a goal plan id
○ an internal goal plan name
○ an optional goal plan description
○ a last-modified date
○ a goal plan start date
○ a goal plan due date
● an option to automatically number goals
● an option to define goal categories and a default / catch-all category
● an option to use the Goal Wizard
● options to replace text
● an option to use a goal library
● definition of the fields to be used in the goal plan and the order in which they are displayed
● permission settings for modifying a goal plan
● definition of the goals on a PM form layout
● metric lookup tables
● rules, calculations

4.1 File Header

The file header is the first element in the goal plan template.

When you download the DTD from Provisioning, you get a file that already contains the file header for you to work
with.

 Remember

As a customer, you do not have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner. If you are no longer working with an implementation partner, contact SAP Cloud
Support.

Goal Management
Goal Plan Templates PUBLIC 35
The second line of the XML file declares the DTD for the SuccessFactors Objective Management 4.0 deployment
descriptor. All such deployment descriptors must include a DOCTYPE of the following format:

<!DOCTYPE obj-plan-template PUBLIC "-//SuccessFactors, Inc.//DTD Objective Template

4.0//EN" "objective-template_4_0.dtd">

After you download the XML:

1. Download the corresponding DTD file and put them both in the same folder on your desktop.
2. Open the XML file in an editor, and swap out this chunk of text:

http://cvs/viewcvs/V4/scr/com/sf/dtd/objective-template_4_0.dtd

to replace it with the name of your DTD file that you've saved in the folder on your desktop. For example:

objective-template_4_0.dtd

This then allows you to validate your XML against the DTD.

For more details on how to configure TGM goal plan templates, refer to the objective-template_4_0.dtd. To
access the latest DTD file, depending on whether you are a partner or an internal user, use either of the following
paths:

● Partner: In the Partner Portal, Implementation Product Information DTDs

● Internal: In Sharepoint, Product Central Documents Product: Goals Category: DTD

4.2 Goal Plan Switches

Here is a table of supported switches in goal plan templates. Switches are used to turn on or off features in a goal
plan template. The default value of the switches is off.

Switches Descriptions

cascader-role If this switch is turned on, the cascader role is enabled.

cws-dispoption-competency-desc If this switch is turned on, the competency description is dis­

played by default.

turnoff-add-personal-goal-button If this switch is turned on, add personal goal button is removed
from the Goal Wizard.

percentage-value-over-100 If this switch is turned on, the figure inputted in the percentage
field can be over 100.

threaded-feedback If this switch is turned on, the threaded feedback feature is en­
abled.

continuouspm-integration If this switch is turned on, the continuouspm integration col­

umn displays.

If you have enabled Career Development Planning as well, you can refer to the Career Development Planning guide
to configure below switches:

● transcript-disable-fancy-pod

Goal Management
36 PUBLIC Goal Plan Templates
● development-scorecard-show-all-goals
● hide-position-count
● disable-jpb-profile-in-cws

4.2.1 Removing the Add Personal Goal Option

You can remove the Personal Goal button from your goal plan template.

Context

If you don’t want employees to create personal goals but rather have them create other types of goals like library or
group goals, you can remove the option to add Personal Goal in the pop-up window for Creating a New Goal by
including the turnoff-add-personal-goal-button switch in the goal plan template and setting the value to
on.

Procedure

1. Go to Provisioning Managing Plan Template Import/Update/Export Objective Plan Template .

 Remember

As a customer, you don’t have access to Provisioning. To complete tasks in Provisioning, contact your
Implementation Partner. If you are no longer working with an Implementation Partner, contact SAP Cloud
Support.

2. Export your target goal plan template.

3. Add the following code snippet to the XML file.

 Sample Code

<switches>
<switch for="turnoff-add-personal-goal-button" value="on"/>
</switches>

4. Save your changes.

5. Upload the updated goal plan template and set it as default template.

Results

The Personal Goal option is removed from your goal plan.

Goal Management
Goal Plan Templates PUBLIC 37
4.3 Goal Plan Template Elements and Attributes

You can configure your Goal Plan template to best suit the business needs of the customer. The <obj-plan-
template> tag is the root element of a Goal Plan template. It contains various elements and attributes. You can
refer to the DTD for the correct order of elements and attributes in a template and optional elements and
attributes.

An Example of Generally Used Elements

The DTD definition for the basic <obj-plan-template> XML is as follows:

<!ELEMENT obj-plan-template (obj-plan-id?, obj-plan-type?, obj-plan-name+, obj-plan-

desc?, obj-plan-lastmodified?, obj-plan-start?, obj-plan-due?, obj-plan-numbering?,
category-config?, add-wizard?, text-replacement*, obj-library?, learning-
activities?, category*, default-category?, field-definition+, permission*, field-
permission*, plan-layout, form-layout, pdf-layout?, details-layout)>
<!ATTLIST obj-plan-template
spellchk (true | false) “false”
instructions-viewdefault (on | off “off”
alerts-viewdefault (on|off “off”
cascade-parent-viewdefault (on | off | disable) “off”
cascade-child-viewdefault (on | off | disable) “off”
new-obj-share-status-public (true | false) “false”
share-confirm (true | false) “false”
unshare-confirm (true | false) “false”
allow-group-goal (true | false) “false”
goal-tree-link (true | false) “false”
pager-max-objs-per-page CDATA #IMPLIED
pager-max-page-links CDATA #IMPLIED
pager-max-children-per-parent CDATA #IMPLIED
display-alignment-format (names | goals) “names”
use-text-for-privacy (true | false) “false”
>

Elements of a Goal Plan Template

This table describes elements that you can specify in the <obj-plan-template> tag.

Elements Description Additional information

obj-plan-id The unique number that identifies the Numbers are assigned as follows:
goal plan
● 1 - 1000 for TGM
● 2001 - 3000 for IDP
● 4001 - 5000 for Learning Activity
● 5001 - 5099 for Career Worksheet

obj-plan-type Goal plan type This is used to differentiate between the types
of plans. Values for this field are:

● Business (indicates goal plan)

● Development (indicates development
plan)
● LearningActivity (indicates link between
learning and development plan)
● CareerWorksheet (used for competency
of current or future job role, short as
"CWS")

Goal Management
38 PUBLIC Goal Plan Templates
Elements Description Additional information

obj-plan-name Name of the goal plan This name appears in the UI. The user selects
the name in a drop-down.

 Note
Do not include special or non-English
characters within the obj-plan-name
tag. For example, # or é. You might en­
counter error when you export the goal
plan.

obj-plan-desc Goal plan description The description does not appear in the UI.

obj-plan-lastmodified Last-modified date This field is automatically updated when the

xml file is successfully uploaded into provision­
ing.

obj-plan-start Goal plan start date Format must be MM/DD/YYYY. This estab­
lishes the default value for the start date for
each goal.

obj-plan-due Goal plan due date Format must be MM/DD/YYYY. This estab­
lishes the default due date for each goal.

obj-plan-numbering Option to automatically number goals For further information, see Automatic Goal
Numbering [page 46]

add-wizard Option to use the Goal Wizard For further information, see Adding Goal Wiz­
ard Option [page 54]

text-replacement Option to replace text See Example below for text replacement XML

obj-library Option to use a goal library For further information, see Mapping of Goal
Library Content to Goal Plans [page 191]

category Option to define goal categories For further information, see Defining Category
and Default-Category [page 52]

default-category Option to define a default / catch-all For further information, see Defining Category
category and Default-Category [page 52]

field definition permission A list of general permissions For further information, see Defining Goal Plan
Fields [page 56]

field-permission A list of goal field permissions For further information, see Defining Goal Plan
Fields [page 56]

plan-layout The goal plan layout specification For further information, see Defining Goal Plan
Fields [page 56]

form-layout The goals that appear on a PM form For further information, see Defining Goal Plan
layout Field Display and Ordering in a Performance
Management v12 Acceleration Form [page
77]

pdf-layout Not used

details-layout Not used

Goal Management
Goal Plan Templates PUBLIC 39
Elements Description Additional information

learning-activities template-id Option to associate a goal with learn­ For further information, see Importing Learn­
ing activities ing Activity Templates.

Attributes of a Goal Plan Template

This table describes attributes that you can specify in the <obj-plan-template> tag.

Attributes Valid Values Description Default

spellchk true a Spell Check link is displayed false - if option not specified
above the field. Only applies to
fields of type textarea.

false disables spell checking for all

goals

new-obj-share-status-public true any new goals are created as false - if option not specified
shared / public goals

false goals are created as private

goals

instructions-viewdefault on sets the Display Options off - if option is not specified

checkbox to automatically dis­
play Instructions to new users  Note

off Instructions are not displayed This attribute only works

until the user selects the with GM v11. Do not use
Display Options Instructions
this attribute if you are us­
checkbox
ing GM v12.

Goal Management
40 PUBLIC Goal Plan Templates
Attributes Valid Values Description Default

alerts-viewdefault on selects the Alerts option in the on

Display Options dropdown to
automatically display alerts to
users.

 Note
In the Goal Plan XML tem­
plate, Alerts can be con­
figured to display by de­
fault. Alerts appear when
any of the following
events take place on the
Goal Plan:

● Goal is Created by
another user on your
plan
● Goal is aligned to an­
other goal by another
user
● Goal is modified by
another user
● Aligned up goal is
modified by goal
owner
● Aligned up goal is de­
leted by goal owner
● Aligned up goal is un­
aligned by another
user
● Aligned down goal is
modified by goal
owner
● Aligned down goal is
deleted by goal
owner

off on-plan alerts are not dis­

played until the user checks
the Alerts option in the Display
Options dropdown

cascade-parent-viewdefault on Current version of application off

allows only off or disable, to
off
meet accessibility require­
disable ments

cascade-child-viewdefault on Current version of application off

allows only off or disable, to
off
meet accessibility require­
disable ments

Goal Management
Goal Plan Templates PUBLIC 41
Attributes Valid Values Description Default

new-obj-share-status-public true sets new created goal as pub­ false

lic

false set new created goal as pri­

vate

expand-collapse-categories true / false when set to "true", user can

expand/collapse categories on
GM page. This attribute only
works when pager-max-objs-
per-page="0".

share-confirm true displays a Windows dialog box false - if option not specified
prompting the user to confirm
changing the state of a goal
from unshared to shared

false allows the user to change the

state of a goal from unshared
to shared without further con­
firmation

unshare-confirm true displays a Windows dialog box false - if option not specified
prompting the user to confirm
changing the state of a goal
from shared to unshared

false allows the user to change the

state of a goal from shared to
unshared without further con­
firmation

allow-group-goal true allows the goal administrator false

to create and assign group
goals: this enables goals for
workgroups reporting to the
same manager

false group goals are disabled

goal-tree-link true creates an icon that links false

users to the Goal Alignment
Spotlight report directly from
their goal plan

false the icon is not enabled

pager-max-objs-per-page <number> Sets the number of goals dis­

played per page on the goal
plan. If set to 0, all goals will be
displayed on one page.

pager-max-page-links <number> Obsolete

pager-max-children-per-pa­ <number> Obsolete

rent

Goal Management
42 PUBLIC Goal Plan Templates
Attributes Valid Values Description Default

more-details-child-format orginal displays aligned down goals as original - if option not speci­
a list, showing only the full fied
name, username and goal
See Examples below for
name. See example below for
effect of setting to original. screenshots showing the ef­
fect of different value settings.
goal-plan displays aligned down goals in
a format similar to viewing
goals in a plan. See example
below for effect of setting to
goal plan.

show-goal-id true displays 'goal-id' on the goal Default value is 'false'.

plan page as a column, goal
detail page and on the edit
goal page.

False does not display the 'goal-id'

display-alignment-format names shows the goal owner name

and contains a link to view the
goal on that user's plan.

goals displays the owner, goal name,

and other fields that are hard
coded to display.

use-text-for-privacy true Text is displayed to show goal false

as public or private. Addition­
ally, goal can be set as public
or private when goal is being
created.

false Icons are displayed to show

goal as public or private.

Goal Plan Template Examples

First Part of a Goal Plan Template

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE obj-plan-template PUBLIC "-//SuccessFactors, Inc.//DTD Objective
Template 4.0//EN""objective-template_4_0.dtd">
<obj-plan-templatespellchk="true"new-obj-share-status-public="true"instructions-
viewdefault="on"alerts-viewdefault="on"cascade-parent-viewdefault="off"cascade-
child-viewdefault="off"pager-max-objs-per-page="10"pager-max-page-links="9"pager-
max-children-per-parent="0"display-alignment-format="goals"more-details-child-
format="goal-plan"share-confirm="false"unshare-confirm="false"allow-group-
goal="true"goal-tree-link="false">
<obj-plan-id>3</obj-plan-id>
<obj-plan-type>Business</obj-plan-type>
<obj-plan-name>2006 Goals</obj-plan-name>
<obj-plan-desc><![CDATA[This is the goal plan for 2006.*]]></obj-plan-desc>*
<obj-plan-lastmodified>5/29/04 4:02 PM</obj-plan-lastmodified>
<obj-plan-start>01/01/2006</obj-plan-start>
<obj-plan-due>12/31/2006</obj-plan-due>
<obj-plan-numbering>
<obj-plan-number-format><![CDATA[#.]]></obj-plan-number-format>
<obj-plan-number-format><![CDATA[#.]]></obj-plan-number-format>
<obj-plan-number-format><![CDATA[#.]]></obj-plan-number-format>

Goal Management
Goal Plan Templates PUBLIC 43
 </obj-plan-numbering>

Text Replacement in a Goal Plan Template

</obj-plan-numbering>
<text-replacement for="Instructions">
<text><![CDATA[<P>Check out our SuccessFactors website!</P>]]></text>
</text-replacement>
<text-replacement for="category">
<text><![CDATA[Goal Classification ]]></text>
</text-replacement>
<obj-library name="SuccessFactors Library">

<text-replacement for="percentage-symbol">
<text><![CData[]></text>
<text-replacement>

Switches in a Goal Plan Template

<switches>
<switch for="percentage-value-over-100"value="on"/>
<switches>

Screenshots of the Effect of more-details-child-format

● more-details-child-format=original:

● more-details-child-format=goal-plan:

Goal Management
44 PUBLIC Goal Plan Templates
4.4 Usage of HTML in Goal Management Templates

When you are editing the Goal Management templates, make sure that you use the correct HTML formatting.

 Note

SAP SuccessFactors makes no commitments to any support services for customized HTML formatting. Test
and validate your customized HTML formatting.

You are recommended to edit and manage your Goal Plan templates in Admin Center.

4.5 Goal Feedback Configuration

The existing comment field in v12 goal plans now includes a new user interface//treatment that allows users to edit
or delete their own comments.

This feature is universal if you have comments configured in the XML form template as shown here.

Example

<field-definition id="comments" type="comment" required="false" detail="false" viewdefault="on"

showlabel="false"><field-label>comments</field-label><field-description>Public Comments</field-
description></field-definition>

Goal Management
Goal Plan Templates PUBLIC 45
  Note

The comment field is not visible in the goal when it is opened in edit mode. This is the correct and expected
behavior.

Configuration Steps

If the XML form template is configured, and <field refid="comments"/> is added under <field-permission
type="write"> to ensure write permission, the next steps are:

1. Enable Goal Management v12 in Provisioning. Make sure that you select "requires Version 12 UI framework
(Revolution)"
2. Configure a new added switch and turn it on in the goal plan template as shown here: <switches><switch
for="threaded-feedback" value="on"/></switches> . You can add the sample code between goal plan dates
and instruction sections in the goal plan templates.

 Remember

As a customer, you do not have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner. If you are no longer working with an implementation partner, contact SAP Cloud
Support.

4.6 Automatic Goal Numbering

Use the obj-plan-numbering element if you want to have goals automatically numbered in the goal plan.

If goal categories are defined, the first number segment always reflects the ordinal position of the goal category.

 Note

If you do any type of sorting in the goal plan, for example, by Goal Name, the Move goal up and Move goal down
functionalities do not take effect. To resolve this issue, you may reset the sorting criteria by adding the obj-
plan-numbering element.

If you want goal numbering enabled, you must include at least one line of obj-plan-number-format code,
similar to the following example. This example numbers the goals as 1.1, 1.2, 1.3 and so on (assuming you have one
goal category).

<obj-plan-numbering>
<obj-plan-number-format>#.</obj-plan-number-format>
</obj-plan-numbering>

Two lines of code make the goals automatically numbered in the format 1.1, 2.1, 2.2, as in the following example:

<obj-plan-numbering>
<obj-plan-number-format>#.</obj-plan-number-format>

Goal Management
46 PUBLIC Goal Plan Templates
 <obj-plan-number-format>#.</obj-plan-number-format>
</obj-plan-numbering>

If you only have two lines like the above you are essentially disabling users from being able to "indent" goals. The
buttons to left indent or right indent a goal do not appear in the set of mouse action buttons.

To enable users to indent goals to one or more levels, you must have a minimum of three code lines. For example:

<obj-plan-numbering>
<obj-plan-number-format>#.</obj-plan-number-format>
<obj-plan-number-format>#.</obj-plan-number-format>
<obj-plan-number-format>#.</obj-plan-number-format>
</obj-plan-numbering>

This XML automatically numbers goals in the plan and allows a maximum indent level of one, e.g. 1.1.1. If goal
categories are defined, the first number segment always reflects the ordinal position of the goal category.

The XML illustrated above automatically numbers goals in the plan as follows:

1.1

1.1.1

1.2

1.2.1

Users can indent goals through Action Indent goal .

4.7 Objective Weight Rules and Objective Count Rules

Attributes can be set to specify weight rules and count rules at various levels within the plan.

Not all of the attributes are included in the default XML template. To find additional required attributes and the
correct order, refer to the DTD (objective-template_4_0.dtd - see topic “File Header” for more information.)

Goal Management
Goal Plan Templates PUBLIC 47
When adding attributes for Objective Weight Rules and Objective Count Rules, it's important to ensure that the
elements are in the correct order. The following XML example shows the new attributes in the order that they can
be included.

Example

<obj-plan-template spellchk="true" new-obj-share-status-public="true" instructions-

viewdefault="on" alerts-viewdefault="on" cascade-parent-viewdefault="off" cascade-
child-viewdefault="off" pager-max-objs-per-page="4" pager-max-page-links="9" pager-
max-children-per-parent="0" display-alignment-format="goals" more-details-child-
format="goal-plan" share-confirm="false" unshare-confirm="false" allow-group-
goal="false" goal-tree-link="true" expand-collapse-categories="false" use-text-for-
privacy="true" cws-people-role="true" max-goals="10" min-goals="5" max-
weight="100.0" min-weight="40.0" max-weight-per-obj="20.0" min-weight-per-
obj="10.0" overwrite-target-population="false" swap-goal-link="false" learning-
activity-deep-link="false" show-total-goalscore="false" show-goal-id="false">

Related Information

File Header [page 35]

4.7.1 Objective Weight Rules

Minimum and maximum weights can be set per objective, per category or per plan.

The system supports configurations for the following weight rules:

● Min/Max for the sum of all goal weights in the goal plan
● Min/Max for the sum of all goal weights in a category
● Min/Max supported weight value for an individual goal

<obj-plan-template min-weight="1" max-weight= "50" min-weight-per-obj="100" max-

weight-per-obj ="120">
<category id="Customer" min-weight="1" max-weight="50">
<category-name>Customer</category-name>
</category>
</obj-plan-template>

 Tip

● You don't have to configure both a minimum and a maximum. If no maximum is required, don't include the
attribute in the goal plan template XML.
● Goal plan weight sum validation is independent of category validation (you could configure a category to
have a higher max or a lower min than the goal plan min/max.)
● Goal plan min/max has a dependency on goal plan pagination (i.e. pager-max-objs-per-page has to be
greater than 0). Otherwise, the min/max will not show up.

Goal Management
48 PUBLIC Goal Plan Templates
 ● Decimals are supported (i.e. you can set max to 100.5%, just be sure your weight field definition also
supports decimals in the field-format).
● Categories must be defined as elements in order for category level weights to be applied.
● The rules are "soft" warnings and not enforced errors, so for example, a user isn't stopped from exceeding
the maximum configured limit, but a warning appears when the min or max settings are not respected.

Display the goal plan total weight

In order to display the goal plan level weight total you have to define either a min or max for total goal plan weight. If
you don't want to have a min or a max, set the value to a large number so it won't be reached (e.g. max-
weight="9999").

Related Information

Min/Max for a Goal Plan [page 49]

Min/Max per Category [page 50]
Min/Max per Objective [page 50]

4.7.1.1 Min/Max for a Goal Plan

You can configure a min/max weight rule for the sum of all goal weights in the goal plan.

The attributes to control this are found under the main <obj-plan-template> element and are:

● max-weight
● min-weight

(For more information see “Objective Weight Rules and Objective Count Rules”.)

Example:
Configure a goal plan to have a maximum total goal weight of 100%

<!DOCTYPE obj-plan-template PUBLIC "-//SuccessFactors, Inc.//DTD Objective

Template 4.0//EN" "objective-template_4_0.dtd">
<obj-plan-template spellchk="true" new-obj-share-status-public="true"
instructions-viewdefault="off" alerts-viewdefault="on" cascade-parent-
viewdefault="on" cascade-child-viewdefault="on" pager-max-objs-per-page="10" pager-
max-page-links="9" pager-max-children-per-parent="3"
display-alignment-format="goals" more-details-child-format="goal-plan" share-
confirm="true" unshare-confirm="true" allow-group-goal="true"
goal-tree-link="true" use-text-for-privacy="false" max-weight="100">

Goal Management
Goal Plan Templates PUBLIC 49
Related Information

Objective Weight Rules and Objective Count Rules [page 47]

4.7.1.2 Min/Max per Category

You can configure a min/max weight rule for the sum of all goal weights in a category.

The attributes to control this are found under the <category> element.

 Caution

Category level support for min/max weights only works when categories are defined as elements and not when
categories are defined as field definitions.

OK: <category id="Financial">

Not OK: <field-definition id="category">

Each category can have a different min/max value.

Example:
Define that for the Financial category, goals should have a total min weight of 25% and
a total max weight of 50%

<category id="Financial" min-weight="25" max-weight="50">

<category-name>Financial</category-name>
</category>

Related Information

Defining Category and Default-Category [page 52]

4.7.1.3 Min/Max per Objective

You can configure a min/max weight rule for the weight value for an individual goal.

The attributes to control this are found under the <obj-plan-template> element. (For more information see
“Objective Weight Rules and Objective Count Rules”.)

Goal Management
50 PUBLIC Goal Plan Templates
Example:
Each goal must have a weight between 5% and 50%

<obj-plan-template spellchk="true" new-obj-share-status-public="true" instructions-

viewdefault="off" alerts-viewdefault="on" cascade-parent-viewdefault="on" cascade-
child-viewdefault="on" pager-max-objs-per-page="9999" pager-max-page-links="9"
pager-max-children-per-parent="3" display-alignment-format="goals" more-details-
child-format="goal-plan" share-confirm="true" unshare-confirm="true" allow-group-
goal="true" goal-tree-link="true" use-text-for-privacy="false" max-goals="14" min-
goals="4" min-weight="0" max-weight="100.5" min-weight-per-obj="5" max-weight-per-
obj ="50">

Related Information

Objective Weight Rules and Objective Count Rules [page 47]

4.7.2 Objective Count Rules

Min/max objective counts can be configured at both the goal plan level and the category level.

Min/Max Objective Count per Goal Plan

Attributes are included in the <obj-plan-template> element:

● max-goals
● min-goals

(For more information see “Objective Weight Rules and Objective Count Rules”.)

Configuring these attributes displays the min/max goal counts as well as a warning message when the number of
goals on a plan do not fall within this range. You do not need to configure both attributes, you can configure a goal
plan to only have a max if so desired.

Example: Each goal plan can have a maximum of 15 goals:

<obj-plan-template spellchk="true" new-obj-share-status-public="true"

instructions-viewdefault="off" alerts-viewdefault="on" cascade-parent-
viewdefault="on"
cascade-child-viewdefault="on" pager-max-objs-per-page="9999" pager-max-page-
links="9"
pager-max-children-per-parent="3" display-alignment-format="goals"
more-details-child-format="goal-plan" share-confirm="true" unshare-
confirm="true"
allow-group-goal="true" goal-tree-link="true" use-text-for-privacy="false"
max-goals="15" min-weight="0" max-weight="100.5" min-weight-per-obj="10"
max-weight-per-obj ="110">

Goal Management
Goal Plan Templates PUBLIC 51
Min/Max Objective Count per Category

Attributes are supported in the <category> element:

● max-goals
● min-goals

 Caution

Category level support for min/max objectives only works when categories are defined as elements and not
when categories are defined as field definitions.

OK: <category id="Financial">

Not OK: <field-definition id="category">

Example: The Financial category requires a maximum of 5 goals in it:

<category id="Financial" min-weight="25" max-weight="50" max-goals="5">

<category-name>Financial</category-name>
</category>

Each category can have a different min/max value.

 Tip

● The plan level and category level objective counts are independent of each other, which means that it's
possible to set conflicting limits (for example, plan max is 5 goals and category max is 10).
● Category objective count is only supported when categories are defined as elements.
● The validation provides “soft” warnings and not strictly enforced errors: in other words, nothing stops the
user from exceeding the limits configured.
● Goal plan min/max has a dependency on goal plan pagination (in other words, pager-max-objs-per-page
has to be greater than 0). Otherwise, the min/max does not show up.

Related Information

Defining Category and Default-Category [page 52]

Objective Weight Rules and Objective Count Rules [page 47]

4.8 Defining Category and Default-Category

The elements for category and default-category are used to determine sections of an objective plan to which
the objectives are allocated.

The category element defines a top-level category used to segment an objective plan. The default-category
element defines the "default" or "catch-all" category. Any objective not matching one of the explicitly defined
categories is placed in this category.

Goal Management
52 PUBLIC Goal Plan Templates
Points about defining category:

● If no category element is defined, the objective plan isn’t divided into sections.

 Note

Defining at least one category is considered a best practice. It allows customers to use more of the tiles
from the SuccessStore since some tiles require a category to function.

● If one or more category elements are present in the template, the objective plans based on the template are
divided in sections according to the categories defined.
● For each category element, there must be at least one category-name element.
● There must be one category-name element without a locale, to define the default localized name.
● To have a category pull-down element in the objective plan, and not divide the plan into sections, define a field
with the name category.

 Note

Don’t include category elements and a field called category in the same objective template.

● Note that the order of the category elements is significant: it defines the order of the sections in the goal plan.
● The & character isn’t supported in category id: to display it in the goal category label on the plan, use "&".

Points about defining default-category:

● The position of the default-category element must be after the last regular category end-tag in the XML.
The file will be invalid if default-category is inserted in between the category elements.

Sub-elements
Attribute Description

id The id attribute defines the internal name used to store and

identify the category. This name shouldn’t be localized.

category-name The category-name is the localized name of a category.

lang The optional lang attribute for category-name defines the lo­
cale of the localized name.

Example

XML Example showing category and default-category:

<category id="Customer">
<category-name>Customer</category-name>
</category>
<category id="Financial">
<category-name>Financial</category-name>
</category>
<category id="Learning and Development">
<category-name>Learning & Development</category-name>
</category>
<category id="Internal Business Operations">
<category-name>Internal Business Operations</category-name>
</category>
<default-category id="Other">

Goal Management
Goal Plan Templates PUBLIC 53
 <category-name>Other</category-name>
</default-category>

Example

XML Example showing the lang attribute:

<category id="Performance Milestones:Financial">

<category-name>Financial</category-name>
<category-name lang="fr_FR_SF">Financier</category-name>
</category>

4.9 Adding Goal Wizard Option

The optional add-wizard element provides a SMART goal wizard function in the goal plan. You can use the
function to add new goals.

Requirements for defining add-wizard are:

● You must have name, metric, start, and due fields defined in the goal plan template. Only these fields should be
required (required=true). It works better if you have just a name field and not name + description. Any
additional required fields will cause an error message on the last page of the wizard.
● Goal creators must include the E role, and must have read/write permission to these four fields.

DTD Definition:

<!ELEMENT add-wizard (include-goal-align?)>

<!ATTLIST add-wizard
mode CDATA #REQUIRED

Sub-elements:

Sub-elements
Attribute Description

Include-goal-align Allows the the user to align the goal being added with one of
their manager's goals or group goals during the Relevant step.

Example

</obj-plan-numbering>
<add-wizard mode="smart goal"/>
<text-replacement for="Instructions">
<text><![CDATA Use this worksheet to add or update goals. To quickly add a new
goal, click the Add goal
button, or browse the Hierarchy section to find an existing goal to add to
your plan]></text>

Goal Management
54 PUBLIC Goal Plan Templates
 </text-replacement>
<field-mapping src-library-field-id="Data1" dst-field-id="metric"/>*
<field-mapping src-library-field-id="Name" dst-field-id="name"/>
</obj-library>
<category id="Customer">

 Note

To see suggestions from the Goal Library, you need to keep Disable autocompletion find in the UI unchecked in
Provisioning and enable goal library in the goal plan.

 Remember

As a customer, you do not have access to Provisioning. To complete tasks in Provisioning, contact your
Implementation Partner. If you are no longer working with an Implementation Partner, contact SAP Cloud
Support.

Example:
Goal wizard with goal alignment:

<add-wizard mode="smart goal">

<include-goal-align/>
</add-wizard>

Example:
Goal wizard without goal alignment:

<add-wizard mode="smart goal"/>

Goal Management
Goal Plan Templates PUBLIC 55
4.10 Defining Goal Plan Fields

The field-definition element defines each of the fields in an objective.

Requirements for the field-definition element are:

● All fields that are used in a goal plan must be defined in this section.
● The order that the fields are defined in dictates the order that they will be displayed in the goal plan details
page and the goal edit window.
● When you add a new field or remove an existing field from the goal plan template, you need to either add or
remove the field references in these sections of the template:
○ field-definition section
○ field-permissions section
○ plan-layout section
○ form-layout section

DTD Definition:

<!ELEMENT field-definition (field-label+, field-description*,

table-row-label*, enum-value*, table-column*, default-value?, field-format?,
rating-scale?,
field-show-coaching-advisor?)><!ATTLIST field-definitionid ID #REQUIREDtype
(text | textarea | date | percent | bool | enum | table | number |
comment | rating | competencies) #REQUIREDrequired (true | false)
"false"detail (true | false) "false"viewdefault (on | off) "on"showlabel (true |
false) "false"reportable (field1 | field2 | field3 | field4 | field5 | field6 |
field7
| field8 | field9 | field10 | field11 | field12 | field13 | field14 |
field15 | field16 |
field17 | field18 | field19 | field20) #IMPLIEDfield-show-coaching-advisor
(true | false) "false">

 Remember

This code snippet is a sample configuration. The exact configuration depends on your system settings.

 Remember

When you delete a field from the Goal Plan template, using either the Admin Center Manage Templates
tool or the XML file, do remember to delete the corresponding permissions of that field from the "permissions"
section of the Goal Plan template. If you delete a field without deleting its permissions from the Goal Plan
template, you might encounter errors while using the Goal Plan.

 Note

If the content you fill in a text field is without natural spaces, the user interface does not wrap the text. For
example, if you fill in with "testesttesttesttesttesttesttestesttesttesttesttesttest", the user interface treats the
content as a single word and introduces a horizontal scroll bar instead of wrapping the text.

Goal Management
56 PUBLIC Goal Plan Templates
Field Definition Sub-elements
Attribute Description

id Defines the internal name for the field, where the data is stored
in the database. The list of standard field ids is shown below (in
the table “Standard goal field ids”. In addition you can define
custom field ids.

type Defines the type of the field. This is a combination of the

stored-data type and UI hints. The possible values for the
type attribute are:
● text: a single line of text (non-typed)
● textarea: multiple lines of text (non-typed)
● date: a date (typed)
● percent: a percent value (typed)
● enum: an enumerated type (shown as a pull-down list; see
enum fields below)
● table: a table of data
● number: a number value (typed)
● link: a link to a URL that creates a popup window
● bool: true or false (shown as a checkbox)

It is strongly recommended that you use the types as illus­

trated in the XML as these are the types that have been heavily
tested and approved. You must enter dates in date fields and
numbers in percent fields (numbers are rounded to the nearest
whole number and appended with a "%" sign).

 Note
If you define any field with type="percent" and want
users to be able to enter a value greater than 100 in that
field, remember that the value for the "percentage-
value-over-100" switch should be set to "on" in the
Goal Plan XML. Conversely, if you want to prohibit users
from entering a value greater than 100 in the percent type
fields, do not enable the "percentage-value-
over-100" switch in the Goal Plan template.

field-label The field label that is displayed in the goal plan template. It can
be configured to use whatever term the customer wants.

field-description Used to put an internal comment. It does not display in the UI.

default-value Optionally used to specify a default value.

Goal Plan Field Properties (Attributes)

Option Valid Values Description

required true ● If true, the field is required and a red

asterisk appears next to it
false ● If false, the field is not required and
the field may be left empty

detail Not used

Goal Management
Goal Plan Templates PUBLIC 57
Option Valid Values Description

viewdefault on ● The viewdefault attribute deter­

mines whether or not the View
off Option (or Display Option as it is
sometimes called) for this field is de­
fault on or off in the plan view. If left
unspecified, the default is "on".
● For TGMv10 viewdefault is ig­
nored for 508 compliance. All the
fields in the first rows are displayed
by default.

showlabel true Field labels are not displayed by default

when you view goals in the goal plan but
false
they are always displayed when you cre­
ate or edit a goal.

You may not need to display field labels if

the goal plan column headings or tasks/
targets/milestones column headings are
adequate in representing the fields dis­
played. Not showing field labels will help
reduce vertical scrolling when viewing
goals in the plan.

 Note
You should consider displaying field
labels for fields that are not in the
first row of the goal plan (first row
can be represented by plan column
headings), especially if the fields in
the non-first rows are not the table
fields (tasks/targets/milestones).

To show the field label, specify showla­

bel="true" in the field definition tag. Oth­
erwise, field labels are not displayed by
default if the attribute is omitted or set to
false, i.e. showlabel="false".

The following screenshot displays field

labels for all fields not in the first row of
the goal plan.

Goal Management
58 PUBLIC Goal Plan Templates
Option Valid Values Description

reportable true The "reportable" attribute determines

which fields are available in the Objective
false
List report. All standard fields are report­
able by default. Only additional custom
fields need the attribute reportable to be
reportable in Adhoc Reporting.

At most 20 fields across an entire com­

pany may be reportable. If a company
has more than one objective template, all
of the reportable="field1" fields must
have the same id and be of the same type
(text, date, enum, etc) across all objec­
tive plans.

Likewise for all of the reportable="field2"

and reportable="field3" fields across all
objective plans.

field-show-coaching-advisor true If true the link to the Coaching Advisor

will display above the field.
false
Only applies to fields of type textarea.

spellchk true ● If true, a Spell Check link is displayed

above the field. Only applies to fields
false of type textarea.
● If false, this disables spell checking
for all goals
● Default is false if option is not speci­
fied

Deciding what fields to include in a goal plan

It is important to determine what portlets will be used for reporting on goals. The Goal Status portlet uses the
status field.

Goal Management
Goal Plan Templates PUBLIC 59
The Goals by Completion and Goal Due Range portlets are looking for the % Complete field, as well as the Due field.
They do not recognize completed goals as they are not looking for the Status field. The Goal List View report
display options are set with certain defaults, which individual users can reset and they will "stick". The
Administrator cannot set these defaults for the entire organization. The % Complete field shown below is turned on
by default. If turned off by the user, it will stay off and the column will not appear on that report.

Standard goal fields

The standard list of fields is shown in the following table:

Goal Management
60 PUBLIC Goal Plan Templates
Standard goal field ids
Field ID Type Typical Usage / Characteristics

name text, textarea, enum Goal name, sometimes relabeled as goal

description. This is the only field that
needs to be defined.

 Note
Whenever you are using a “name”
field, the field value appears in a
larger font on the application UI only
when the field is positioned as the
first column within the goal plan ta­
ble. However, when you print the goal
plan, the “name” field value always
appears in a larger font regardless of
the field’s position within the goal
plan table.

desc text, textarea, enum Used for detailed goal description if

name is being used as a short name.

metric text, textarea, enum Used to describe how a goal will be meas­
ured, in other words, success criteria.

start date Goal start date - auto-populated with the

start date defined in the <obj-plan-start>
template tag. The format is defined by
selected language pack.

due date Goal due date - auto-populated with the

due date defined in the <obj-plan-due>
template tag. The format is defined by
the selected language pack

state enum,(use text, textarea with care) Typically presented as a drop down list of
values with colors to report the goal state
or status. It is used as such in dashboard
reports. Limited to 128 characters. Often
labeled "Status".

Goal Management
Goal Plan Templates PUBLIC 61
Field ID Type Typical Usage / Characteristics

done percent Displayed as a whole number with a

graphical "progress" bar.

 Note
If you define the "done" field with
type="percent" and want users
to be able to enter a value greater
than 100 in the "done" field, remem­
ber that the value for the
"percentage-value-
over-100" switch should be set to
"on" in the Goal Plan XML. Con­
versely, if you want to prohibit users
from entering a value greater than
100 in the "done" field, do not enable
the "percentage-value-
over-100" switch in the Goal Plan
template.

Goal Management
62 PUBLIC Goal Plan Templates
Field ID Type Typical Usage / Characteristics

weight Recommended type: number, percent The value in this field is used to auto-
populate the objective weight when the
It can also be set as enum, text, or tex­
goal is added to a PM form.
tarea.
 Note
If you define the "weight" field with
type="percent" and want users
to be able to enter a value greater
than 100 in the "done" field, remem­
ber that the value for the
"percentage-value-
over-100" switch should be set to
"on" in the Goal Plan XML. Con­
versely, if you want to prohibit users
from entering a value greater than
100 in the "weight" field, do not ena­
ble the "percentage-value-
over-100" switch in the Goal Plan
template.

 Remember
● If weight is configured as
enum, the system does not sup­
port min/max weight warnings
and cannot be used in calcu­
lated ratings.
● If weight is configured as text,
the text value entered is used
verbatim; and if configured as
text/textarea, this field will not
be supported in Ad Hoc Report­
ing, as the Sub Domain Schema
does not support non-numeric
values for this field.

tasks table A table of individual tasks supporting the

goal. (See the Table fields section for
more detail.)

targets table A table of individual targets towards ach­

ieving the goal. (See the Table fields sec­
tion for more detail.)

milestones table A table of individual milestones towards

achieving the goal. (See the Table fields
section for more detail.)

metric text Defines a measurement for the goal, for

example percentage of completion.

Goal Management
Goal Plan Templates PUBLIC 63
Field ID Type Typical Usage / Characteristics

comments comment Used to configure the layout and permis­

sion for public comments. The field is
read-only and automatically includes the
name and date stamp when the com­
ments were entered.

group-rating rating Enables group goal rating directly in the

goal, for when the goal is rated once for
all participants. This can only be modified
by the group goal owner. See Group
Goals

group-rating-comments rating Allows the group goal owner to enter rat­

ing comments. See Group Goals.

obj-plan-field1 text Reinforces messages to employees on

why they are executing on the goals as­
signed to them.

 Note
The field is introduced as a Mission
Statement, however, it can be reused
for other purpose with a different
field-label.

Field length configuration scenarios:

● Empty value: initialized as ‘0’ at backend, uses default values as described in the following table.
● 0 < X < 4000: use customized value ‘X’.
● >4000: initialized as ‘0’ at backend, uses default values as described in the following table.

In general all text fields have a default maximum length of 4000 characters. Some exceptional field types have
different maximum default lengths. According to current code logic, here are the corresponding default max length
for the respective field types:

Maximum Default Character Lengths for Different Fields

Field Type Description Maximum Field Length

TYPE_TEXT General text field 4000 Characters

OBJ_MILE_TARGET_MAX_LENGTH Milestone target 8000 Characters

OBJ_MILE_DESC_MAX_LENGTH Milestone description 2048 Characters

OBJ_MILE_ACTUAL_MAX_LENGTH Milestone actual 2048 Characters

OBJ_COMMENT_MAX_LENGTH Goal description 4000 Characters

OBJ_PLAN_DESC_MAX_LENGTH Goal plan description 2048 Characters

Goal Management
64 PUBLIC Goal Plan Templates
Table fields (Task, Milestone, Target, Acheivement Lookup)

Special fields of type table are supported: Task, Milestone, Target, and Achievement Lookup. A table field is a
collection of fields that can be repeated for each goal. For example each goal may have several Tasks or Milestones
associated with it.

You can use Permission tags to control who can create, modify, or delete rows of a table within a goal plan (see
“Table Field Permissions”). You can also set access permission for individual table columns (see “Table Column
Permissions”).

The Milestone table has the same columns as the Tasks table. In the Tasks table milestone start and due dates are
auto-populated with the same dates entered for the goal whereas in the Milestone table they are not. Typically the
milestones table validates that the start date value is earlier than the due date value. However, since you can relabel
these fields to be something like "target" and "actual", the validation may not be desirable. To fix this you can set
the optional validate-start-before-due attribute to "false" for the "start" field.

Table field types

Table Field ID Must be of type Notes

Tasks desc textarea or text Max 2048 chars

start date
Milestones
due date

done percent

target textarea or text Max 2048 chars

actual textarea or text Max 2048 chars

Targets target textarea or text

actual textarea or text

date date

Tables can be renamed. For example, you can relabel the <Task> table to be "Subgoals", "Activities", "Notes", etc.
The following columns are available for tasks, targets, and milestones. The fields must be of the type listed below.
You may use any subset of the fields for each table. You cannot add custom fields to a table. The order in which the
fields are listed determines the order in which the fields display in the UI.

Columns can be arranged in any order. You can remove columns from the table structure if the customer does not
want all the task attributes that you see listed. The column types must match those in the Table fields table shown.
Text columns have a character limit of 2048 characters. The date and percentage columns cannot be transformed
to text fields. You can change the values in the label or description tags but you must not change the ids that are
referenced as these ids are recognized by the application.

Table field elements

Description

table-row-label Displayed in the UI. The word "Add" is always prepended to the
label specified. For example "Task" would display as "Add
Task"-

Goal Management
Goal Plan Templates PUBLIC 65
 Description

table-column id This defines the internal name for the field .where the data is
stored in the database. The list of standard id fields is shown
above. You cannot add custom fields to a table.

Each table-column id has a column-label, column-description,

type attribute defining its type; and optional required and a de­
fault-value attributes similar to a field-definition. Additional at­
tributes available for the table-column id element are:

● width: The width attribute specifies the width of the col­

umn in characters. It should be specified for columns of
type "textarea" to provide enough space anticipated user
input. For all other column types, width is ignored.
● validate-start-before-due: For all table columns which
have id of start and a type of date, support another attrib­
ute, validate-start-before-due. If this attribute is set to
false, then it turns off validation enforcement of the start
date being before the due date.

column-label This is the label that identify the columns that appear in a ta­
ble. It can be configured to use what ever term the customer
wants.

column-description This is used to put an internal comment. It does not display in

the application.

default-value The default-value defines the default or initial value of a field or

column.

● For fields or columns of type="text" and "textarea", the

value is copied directly to the contents of a field in a new
goal, accounting for the locale as specified by the optional
"lang" attribute.
● For fields or columns of type="enum", "date", "percent",
"number" or "bool", the value is specified in a non-local­
ized format, and the lang attribute is not allowed.
● For "enum" fields, the contents must be "value" attribute
of one of the enum-value elements.
● For "date" attributes, the format is MM/DD/YYYY.
● For "percent" the value is an unformatted number (no "%"
sign).
● For "bool" attribute, value is either "true" or "false".

In all cases, if the value is not required, an empty default-value

tag specifies the initial value of the field is empty.

field-format The field-format defines the format of a field or column. Cur­

rently, it is only implemented for the number type as follows:

● #.00 number with 2 decimals

● integer
● '#'# prefix, formats 123 to "#123"
● #% convert to integer and append % to the end

Goal Management
66 PUBLIC Goal Plan Templates
Enum Fields

A field of type enum allows you to specify a drop down list with all the possible values for the field.

Enum Fields

enum-value The enum-value tag defines one of the possible values that
a field of <type="enum"> may have. The order of the
enum-value elements in the XML determines the order in
which the drop-down list is presented, and the collation order
for sorting by the field.

● The "value" attribute defines the non-localized, internal

string, under which the data is stored. (Use the enum-la­
bel sub-element to define localized string labels).
● The "style" attribute optionally defines the background
and text color.

enum-label This is the text that displays in the drop down list. There must
be at least one enum-label element defined per enum-
value.

Custom Fields

You have the option to define and report on custom fields that are defined in your goal plan. These are goal field
types that are not listed in the DTD. Define a custom field just as you would any of the standard fields. Custom
fields can not be a table type field. They must be of the following types: text , textarea, enum, date and percent.
Each custom field has an "id" attribute defining its internal name; a "type" attribute defining its type; and optional
"required", "field-show-coaching-advisor" attributes.

 Note

When a change is made to which field is reportable, either initially making a custom field reportable, or
changing which fields are reportable, that change affects all goals that are saved or edited from that point
forward. To retroactively apply the change to existing objectives, in Provisioning, go to the Ad-Hoc Report
Builder section, find Objective Management, and click the Synch button. This allows the new/modified custom
field to update correctly in the DB, so it can then be picked up by Ad Hoc Reports going forward.

 Remember

As a customer, you do not have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner. If you are no longer working with an implementation partner, contact SAP Cloud
Support.

 Note

The sync process may add a ‘modify’ record to the audit trail of each goal, so it is important that the ‘Goal
Modification’ email be turned off for the duration of the sync process to avoid unwanted emails.

Goal Management
Goal Plan Templates PUBLIC 67
Attribute Description

reportable Determines which fields are available in the Objective List re­
port. At most, 20 fields across an entire company may be re­
portable. If a company has more than one objective template,
all of the reportable="field1" fields must have the
same id and be of the same type (text, date, enum, etc) across
all objective plans. For example, if you have weight fields in two
different objective plan templates, each must have an identical
id (field 1, 2 or 3). Field ID will typically ensure that they are of
the same field type. You can configure to report on 20 fields
across the entire application.

 Note

After cascading goals, managers can only see standard fields defined in the DTD from their goal plans. For
managers to view custom fields in the alignment view, the attribute reportable is required in the XML
template as part of custom field definition. You may refer to the sample code below.

<field-definition id="personalmetric" type="enum" required="false" detail="false"

viewdefault="on" showlabel="false" reportable="field1" default-calc-type="step"
field-show-coaching-advisor="false" cascade-update="push-down">

Custom fields can be added using the Manage Templates tool.

URL Link Fields

The link data type allows a goal plan field to point to a link (see goal plan "Link Data" field below). This field does not
display in a Performance Review form. When an employee creates a link in the field, clicking on the link will open a
browser to display the link. To create the link in the edit screen, the link's label and URL must be specified.

To configure the link data type create a custom field using the link data type:

<field-definition id="link" type="link" required="false" detail="false"

viewdefault="on" showlabel="false" field-show-coaching-advisor="false">
<field-label>Link Data</field-label>
<field-label lang="es_ES">Actual</field-label>
</field-definition>

Comments Fields

A field of type comments includes the username and a date stamp for when the comment was entered.

Goal Management
68 PUBLIC Goal Plan Templates
 <field-definition id="comments" type="comment" required="false" detail="false"
viewdefault="on" showlabel="false">
<field-label>comments</field-label>
<field-description>Public Comments</field-description>
</field-definition>

Example:
XML Example: standard field

<field-definitionid="name" type="textarea" required="true" detail="false"

viewdefault="on" showlabel="false"
field-show-coaching-advisor="false">
<field-label>Goal Name*</field-label>
<field-description>Goal Name</field-description>
</field-definition>
<field-definition id="done" type="percent" required="true" detail="false"
viewdefault="on" showlabel="false"
field-show-coaching-advisor="false">
<field-label>% Complete</field-label>
<field-description>Percent Complete</field-description>
<default-value>0.0</default-value>
</field-definition>

Example:
XML Example: table field

<field-definition id="tasks" type="table" required="false" detail="false"

viewdefault="on" showlabel="true" field-show-coaching-advisor="false">
<field-label>Sub-Goals</field-label>
<table-row-label>Sub-Goal</table-row-label>
<table-column id="desc" type="textarea" required="true" width = 50>
<column-label>Sub-Goal Description</column-label>
<column-description>Sub-Goal Description</column-description>
</table-column>
<table-column id="done" type="percent" required="false">
<column-label>Percent Complete</column-label>
<column-description>Percent Complete</column-description>
<default-value>0</default-value>
</table-column>
<table-column id="start" type="date" required="false" validate-start-before-
due="false">
<column-label>Target Date</column-label>
<column-description>Target Date</column-description>

Goal Management
Goal Plan Templates PUBLIC 69
 </table-column>
</field-definition>

Example:
XML Example: enum field

<field-
definitionid="state"type="enum"required="false"showlabel="false"viewdefault="on">
<field-label>Status</field-label>
<enum-valuevalue="none"style="background:white;color:black;">
<enum-label>none</enum-label>
</enum-value>
<enum-value value="Will meet target" style="background:green;color:white;">
<enum-label>Will meet target</enum-label>
</enum-value>
<enum-valuevalue="Don't know"style="background:yellow;color:black;">
<enum-label>Don't know</enum-label>
</enum-value>
<enum-value value="Will not meet target"style="background:red;color:white;">
<enum-label>Will not meet target</enum-label>
</enum-value>
<enum-value value="Goal completed"style="background:blue;color:white;">
<enum-label>Goal completed</enum-label>
</enum-value>
</field-definition>

Related Information

Table Field Permissions [page 155]

Table Column Permissions [page 155]

4.11 Configuring Custom Checkbox

Custom checkbox field can be configured for the Add Goal and Edit Goal dialogs.

Context

The type attribute bool can be used in the field-definition to display a checkbox.

 Remember

As a customer, you do not have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner. If you are no longer working with an implementation partner, contact SAP Cloud
Support.

Goal Management
70 PUBLIC Goal Plan Templates
Procedure

1. Go to Provisioning Manage Plan Template Import/Update/Export Objective Plan Template .

2. Export the goal plan template that you want to add the bool attribute to.
3. Open the downloaded goal plan with an XML editor.
4. Add the bool attribute to the XML. Refer to the following code sample:

 Sample Code

<field-definition id="checkbox" type="bool" required="true" detail="false"

viewdefault="on" showlabel="true" field-show-coaching-advisor="false" cascade-
update="push-down" reportable="field10">
<field-label>Custom Checkbox</field-label>
<field-description>Checkbox for Manager</field-description>
</field-definition>

5. Save your changes and upload the XML in Provisioning.

Results

You have successfully added bool attribute to the goal plan template. You can see a custom checkbox when you
add or edit the goal plan.

4.12 Working with the Visibility field

The Visibility field in Goal Plan can be configured to display whether a goal is a private goal or a public goal.

Usually, a public goal is visible to the manager and to the other roles that have permissions to view the goal. A
private goal by contrast, is only accessible to the employee. However, it is possible to configure a Goal Plan to make
the private goal accessible to other roles (including, but not limited to, the manager or manager’s manager).

Using the use-text-for-privacy, new-obj-share-status-public, share-confirm, and the unshare-

confirm attributes, you can define whether the goals are public or private, and manage the appearance of the
Visibility field.

 Note

By default, the values of the Visibility field are "public" and "private". However, if you want to customize the UI
labels of the Visibility field values to something like "Open" and "Confidential", use the Manage Languages tool.
The message keys for the "public" and "private" labels are opublic and oprivate. Refer to the Working with
Manage Languages section of the Managing UI Labels in SAP SuccessFactors HCM Suite guide for more
information.

Configuring the Visibility field in the Goal Plan [page 72]

Goal Management
Goal Plan Templates PUBLIC 71
 You can configure the appearance and default values of the Visibility field using the use-text-for-
privacy, new-obj-share-status-public, share-confirm, and the unshare-confirm attributes in
the Goal Plan XML.

Enabling Users to Edit the Visibility Field in the Goal Plan [page 73]
You can grant user roles the permissions to edit the Visibility field, by configuring the permissions section
of the Goal Plan template to include "share" and "private-access" permissions.

4.12.1 Configuring the Visibility field in the Goal Plan

You can configure the appearance and default values of the Visibility field using the use-text-for-privacy,
new-obj-share-status-public, share-confirm, and the unshare-confirm attributes in the Goal Plan
XML.

Preferred configurations for the Visibility field

There are multiple ways to configure the Visibility field. The following table lists some valid use-cases. You can apply
any of them to your Goal Plan to best suit your business needs.

Configure the attributes as follows... Should the Goal

Plan include per­
missions for
new-obj- share and
use-text-for- share-status- unshare- private-
If you want to... privacy public share-confirm confirm access?

Hide the Visibility false false (or delete NA NA No

field the attribute from
the template)

Configure the true true true true Yes

Visibility field to be
available on the
Goal Plan and be
editable

Configure the false true true true Yes

Visibility field to ap­
pear as an icon on
the Goal Plan and
be editable

Goal Management
72 PUBLIC Goal Plan Templates
 Configure the attributes as follows... Should the Goal
Plan include per­
missions for
new-obj- share and
use-text-for- share-status- unshare- private-
If you want to... privacy public share-confirm confirm access?

Configure the true true NA NA No

Visibility field to be
available on the
Goal Plan, but as a
'read-only' field

Configure the true false true true Yes

Visibility field to be
available on the
Goal Plan, be edita­
ble, and set the
goals to be private
by default

To know more about the attributes, refer to the Global Setting Details table in the Goal Plan Template Options
topic.

Parent topic: Working with the Visibility field [page 71]

Related Information

Enabling Users to Edit the Visibility Field in the Goal Plan [page 73]
Enabling Users to Edit the Visibility Field in the Goal Plan [page 73]
Goal Plan Template Elements and Attributes [page 38]

4.12.2 Enabling Users to Edit the Visibility Field in the Goal

Plan

You can grant user roles the permissions to edit the Visibility field, by configuring the permissions section of the
Goal Plan template to include "share" and "private-access" permissions.

For example, the following code snippet can be included in the permissions section of the Goal Plan to grant edit
permissions for the Visibility fields to employees (E role) and their managers (EM role).

 Sample Code

<permission for="share">

Goal Management
Goal Plan Templates PUBLIC 73
 <description><![CDATA[Only the employee and manager may share and
unshare goals in his/her own plan.]]></description>
<role-name><![CDATA[E]]></role-name>
<role-name><![CDATA[EM]]></role-name>
</permission>
<permission for="private-access">
<description><![CDATA[Employees and their managers up the hierarchy may
view unshared/private goals. Parents of cascaded private goals can see the
children.]]></description>
<role-name><![CDATA[E]]></role-name>
<role-name><![CDATA[EM]]></role-name>
</permission>

 Note

To configure the Visibility field as a 'read-only' field, do not include the permissions for "share" and "private-
access" in the Goal Plan XML.

Parent topic: Working with the Visibility field [page 71]

Related Information

Configuring the Visibility field in the Goal Plan [page 72]

4.13 Goal Feedback Field

The comment field has been improved to allow users to edit or delete their own comments.

Users can now collapse or expand the layout and edit or delete their own comments.

 Note

● There is a 4000 character limit within the comment field.

● There is no limit on the number of comments that can be added to a particular goal.

If you have an existing goal plan and to not have comments configured to this goal plan, new comments are not
applied to the goal plan. You need to update all GM form templates before you can launch new forms. You need to
configure this feature in the XML template and in Provisioning.

 Remember

As a customer, you do not have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner. If you are no longer working with an implementation partner, contact SAP Cloud
Support.

Goal Management
74 PUBLIC Goal Plan Templates
1. Configure the field in the XML template as follows:

<field-definition id="comments" type="comment" required="false" detail="false"

viewdefault="on" showlabel="false">
<field-label>comments</field-label>
<field-description>Public Comments</field-description></field-definition>

2. In Provisioning, select Enable Goal Management V12 - requires "Version 12 UI framework (Revolution).
3. Configure the new added switch and turn it on in the goal plan template as follows:
<switches><switch for="threaded-feedback" value="on"/></switches>

4.13.1 Goal Details Tab

Of the tabs available in the Performance Management form, the Goal Details tab is the only one that is configurable.

The Other Details tab, which includes the sub goal tables, is not. You can control the order and the list of the fields
in the Goal Details tab via the Goal Plan template.

 Note

You can determine which goal plan fields appear in the Performance Management form, by defining it in the
<form-layout> section of the goal plan template.

 Example

● You can add the following XML Snippet for the <form-layout> section of the Goal Plan XML to access the
threaded feedback comments from the Goal Details tab within the Performance Management form.

<form-layout><![CDATA[## Consider displaying goal category (if applicable) if

mapping goals across all categories in one objective section #set ($group =
"name-metric")
<table width="100%" cellspacing="0" cellpadding="0">
<tr>
<td valign="top" width="50%">#if ($display.name) <b>${label.name}:</b><br>
${field.name} #end</td>
<td>&nbsp;&nbsp;&nbsp;</td>
<td valign="top" width="50%">#if ($display.metric) <b>${label.metric}:</b><br>
${field.metric} #end</td>
<td>&nbsp;&nbsp;&nbsp;</td>
<td valign="top" width="40%">#if ($display.state) <b>${label.state}:</b><br>
${field.state} #end</td>
<td>&nbsp;&nbsp;</td>
<td valign="top" width="">#if ($display.start) <b>${label.start}:</b><br>
${field.start} #end</td>
<td>&nbsp;&nbsp;</td>
<td valign="top" width="">#if ($display.due) <b>${label.due}:</b><br>
${field.due} #end</td>
<td>&nbsp;&nbsp;</td>
<td valign="top" width="50%">#if ($display.done) <b>${label.done}:</b><br>
${field.done} #end</td>
</tr>
</table>
<div class="clear">
&nbsp;
</div>
#if ($display.milestones)
<div style="display:none" id="${util.newHiddenDivId()}">
<b>${label.milestones}</b><br>
${field.milestones}

Goal Management
Goal Plan Templates PUBLIC 75
 </div>
#end
#if ($display.comments)
<div style="display:none" id="${util.newHiddenDivId()}">
<b>${label.comments}</b><br>
${field.comments}
</div>
#end
]]>
</form-layout>

● You can add the following XML Snippet in the <form-layout> section of the Goal Plan XML to display the
‘metric’ field in the Goal Details tab on the Performance Management form.

<td valign="top" width="30%">#if ($display.metric) <b>${label.metric}:</b><br>

${field.metric} #end</td>

4.14 Defining Column Width in Goal Plan

You can use the <plan-layout> section to define the column width of the tables in Goal Plan.

According to the DTD, the optional weight attribute defines a relative weight, for the layout of the column. If
present, it is converted to a percent when rendering the HTML column and subsequently allows the column to grow
and shrink with the browser. If not specified, field will only take up as much space as it requires. It is recommended
that at least one column have a non-zero weight specified.

To manage the actual width of the table define the <column weight> of each column, such that the sum of all the
column weights is equal to 100. The following example is based on a 100% table width, in which the columns are
partitioned using the weight value. In the XML snippet, the goal name column takes up 50% of the entire table,
apportioning the remaining fields at 10% each.

 Sample Code

<plan-layout>
<column weight="50.0">
<field refid="name"/>
<field refid="description"/>
</column>
<column weight="10.0">
<field refid="weight"/>
</column>
<column weight="10.0">
<field refid="start"/>
</column>
<column weight="10.0">
<field refid="due"/>
</column>
<column weight="10.0">
<field refid="state"/>
</column>
<column weight="10.0">
<field refid="metric"/>
</column>
</plan-layout>

Goal Management
76 PUBLIC Goal Plan Templates
  Note

You must allocate sufficient weight for fields. If not, the characters in the fields may miss pixels. Do not position
a sub-category field in the first column of the goal plan layout.

4.15 Defining Goal Plan Field Display and Ordering in a

Performance Management v12 Acceleration Form

In the form-layout section, you define how information is displayed in the Performance Management form.

In the goal plan XML, there is an area called <form-layout>. It used to control how the goal fields will appear in
the Performance Management v12 Acceleration form, if goals are pulled into it from the Goal Plan.

The goal plan field layout can be controlled in Performance Management v12 Acceleration for the Goal Details and
Other Details tabs. The order that you enter the fields in the <form-layout> area of the Goal Plan XML is how they
will appear in the Goal Details tab.

Example

The following XML defines a layout for displaying the goals information in the Performance Management v12
Acceleration form:

<form-layout>
<![CDATA[#set ($group = "")
<table width="100%" cellspacing="0" cellpadding="0"><tr><td valign="top"
width="50%">#if ($display.name) <b>${label.name}:</b><br>
${field.name} #end</td><td>&nbsp;</td><td>&nbsp;</td><td valign="top"
width="10%">#if ($display.state) <b>${label.state}:</b><br>
${field.state} #end</td><td>&nbsp;</td><td valign="top" width="10%">#if
($display.comments) <b>${label.comments}:</b><br>
${field.comments} #end</td><td>&nbsp;</td><td valign="top" width="20%">#if
($display.weight) <b>${label.weight}:</b><br>
${field.weight} #end</td></tr></table><table width="100%" cellspacing="0"
cellpadding="0"><tr><td valign="top"><div style="display:none" id="$
{util.newHiddenDivId()}">
#if ($display.metric) <b>${label.metric}:</b><br>
${field.metric} #end
</div></td></tr><tr><td valign="top"><div style="display:none" id="$
{util.newHiddenDivId()}">
#if ($display.link) <b>${label.link}:</b><br>
${field.link} #end
</div></td><td>&nbsp;</td><td valign="top"><div style="display:none" id="$
{util.newHiddenDivId()}">
#if ($display.actual) <b>${label.actual}:</b><br>
${field.actual} #end
</div></td><td valign="top"><div style="display:none" id="$
{util.newHiddenDivId()}"><b>${label.category}:</b><br>
${field.category}
</div></td></tr><tr><td valign="top">
#if ($display.start)
<div style="display:none" id="${util.newHiddenDivId()}"><b>${label.start}:</
b><br>
${field.start} #end

Goal Management
Goal Plan Templates PUBLIC 77
 </div></td><td>&nbsp;</td><td valign="top">
#if ($display.due)
<div style="display:none" id="${util.newHiddenDivId()}"><b>${label.due}:</
b><br>
${field.due} #end
</div></td><td>
#if ($display.done)
<div class="objPair" style="display:none" id="${util.newHiddenDivId()}"><b>$
{label.done}:</b>${field.done}<br></div>#end #if ($display.group-rating)
<div class="objPair" style="display:none" id="${util.newHiddenDivId()}"><b>$
{label.group-rating}:</b>${field.group-rating}<br></div>#end
</td></tr></table><div class="clear">
&nbsp;
</div>#if ($display.targets)
<div style="display:none" id="${util.newHiddenDivId()}"><b>${label.targets}</b><br>
${field.targets}
</div>#end]]>
</form-layout>

The following image shows how the Performance Goals section of the Performance Review form would appear:

 Note

If you are using threaded feedback, you can still add the "comment" field to the <form-layout> section, and
the threaded feedback on a goal will appear on the Performance Management form.

4.16 Custom Calculations

You can configure calculated fields, which provides a very powerful feature.

Some examples of commonly requested calculated fields are:

● Goal Score: Rating x Weight

● Run Rate: Actual / (Current Date – Start Date)
● Year End Forecast (based on current Run Rate): Run Rate x (Due Date – Start Date)
● Target Run Rate: Target / (Due Date – Start Date).

Goal Management
78 PUBLIC Goal Plan Templates
● Year End Forecast (based on Target Run Rate): Actual + (Target Run Rate x (Due Date – Current Date))
● Proposed Run Rate: (Target – Actual) / (Due Date – Current Date)

To get started, see the “Custom Calculation Example” topic, which shows examples of commonly calculated fields.

In the “Custom Calculation DTD” topic you can find details of how to use the elements in custom calculations.

Descriptions of the calculations, functions and operators that can be used with these elements are provided in the
topic “Calculations, Functions and Operators”.

There are also special case topics on “Goal Plan and/or Category Score Total” and “Sub-goal Calculated Rating”.

Below are some examples showing:

● Defining calculation
● Logical & comparison operators
● Table results

Example:
Defining Calculation

Use Case: Define a calculator that will calculate the run rate for a goal. Actual / (today - start date) represented in
months

<calculator id="runRate">
<![CDATA[actual_achievement/FUNC.diff(NOW, start, MONTH)]]>
</calculator>
<auto-population field= "run-rate" mode= "auto">
<rule><calculated-result calculator-id= "runRate"/></rule>
</auto-population>

Example:
Logical & Comparison Operators

Use Case: Define the probability of success for a goal based on the percent achievement (actual/target). If %
achievement is greater than 75%, then probability of success is High. If % achievement is between 45% and 75%
then probability of success is Medium. Anything less than 45% is Low.

<calculator id="ruleCondition1"><![CDATA[(bizx_actual/bizx_target)*100 >= 75]]></

calculator>
<calculator id="ruleCondition2"><![CDATA[(bizx_actual/bizx_target)*100 < 75 &&
(bizx_actual/bizx_target)*100 >= 45]]></calculator>
<calculator id="ruleCondition3"><![CDATA[(bizx_actual/bizx_target)*100 < 45]]></
calculator>
<auto-population field="bizx-pos" mode="auto">
<rule>
<rule-condition calculator-id="ruleCondition1"></rule-condition>
<calculated-result calculator-id="posHigh"/>
</rule>
<rule>
<rule-condition calculator-id="ruleCondition2"></rule-condition>

Goal Management
Goal Plan Templates PUBLIC 79
 <calculated-result calculator-id="posMed"/>
</rule>
<rule>
<rule-condition calculator-id="ruleCondition3"></rule-condition>
<calculated-result calculator-id="posLow"/>
</rule>
</auto-population>

Example:
Table Results

Use Case: Instead of calculating a field based on values from other fields, this use case is to populate the metric
lookup table with values based on a user's selection/entry in other fields. For example, if this goal is in category "X"
and the target baseline is "Y", then set MLT to "ABC".

<calculator id="ruleCondition1"><![CDATA[category== "Sales" && target_baseline >

500000000]]></calculator>
<calculator id="ruleCondition2"><![CDATA[category== "Sales" && target_baseline >
250000000 && target_baseline <= 500000000]]></calculator>
<auto-population field= "metric-lookup-table">
<rule>
<rule-condition calculator-id="ruleCondition1"></rule-condition>
<table-result>
<row>
<col id="achievement">75</col>
<col id="rating">25</col>
<col id="description"><![CDATA[First Point]]></col>
</row>
<row>
<col id="achievement">90</col>
<col id="rating">50</col>
<col id="description">Second Point</col>
</row>
<row>
<col id="achievement">95</col>
<col id="rating">75</col>
<col id="description"><![CDATA[Third Point]]></col>
</row>
<row>
<col id="achievement">99</col>
<col id="rating">100</col>
<col id="description"><![CDATA[Fourth Point]]></col>
</row>
<row>
<col id="achievement">100</col>
<col id="rating">110</col>
<col id="description"><![CDATA[Fifth Point]]></col>
</row>
<row>
<col id="achievement">110</col>
<col id="rating">135</col>
<col id="description"><![CDATA[Sixth Point]]></col>
</row>
</table-result>
</rule>
<rule>
<rule-condition calculator-id= "ruleCondition2"></rule-condition>
<table-result>
<row>
<col id="achievement">75</col>
<col id="rating">25</col>

Goal Management
80 PUBLIC Goal Plan Templates
 <col id="description"><![CDATA[First Point - 2nd scale]]></col>
</row>
<row>
<col id="achievement">90</col>
<col id="rating">50</col>
<col id="description">Second Point - 2nd scale</col>
</row>
<row>
<col id="achievement">95</col>
<col id="rating">75</col>
<col id="description"><![CDATA[Third Point - 2nd scale]]></col>
</row>
<row>
<col id="achievement">99</col>
<col id="rating">100</col>
<col id="description"><![CDATA[Fourth Point - 2nd scale]]></col>
</row>
<row>
<col id="achievement">100</col>
<col id="rating">110</col>
<col id="description"><![CDATA[Fifth Point - 2nd scale]]></col>
</row>
<row>
<col id= "achievement">115</col>
<col id= "rating">135</col>
<col id= "description"><![CDATA[Sixth Point - 2nd scale]]></col>
</row>
</table-result>
</rule>
</auto-population>

Related Information

Custom Calculation Example [page 81]

Custom Calculation DTD [page 82]
Calculations, Functions and Operators [page 85]
Calculating Total Score of Goal Plan or Category [page 91]
Calculating Ratings or Scores for Sub-goals [page 91]

4.16.1 Custom Calculation Example

A simple custom calculation example is provided to help you get started.

Context

Business Request: As a user, you would like to display goal scores in your goal plan.

 Note

Configure Assumption: Goal Score is Rating x Weight. In this example, we are using the standard field ids
<weight> and <rating>.

Goal Management
Goal Plan Templates PUBLIC 81
Procedure

1. Define a new field. This includes the field definition, permissions, column and form layout, and so on.

 Note

Standard Field: Use the standard field id <goal-score> if you want to have the goal score roll up to goal
plan or category level totals.

<field-definition id="goal-score" type= "number" required= "false " detail=

"false " viewdefault= "off" showlabel= "true " field-show-coaching-advisor=
"false " cascade-update= "regular">
<field-label>Score</field-label>
<field-description>Goal Score</field-description>
< default-value>0.0</default-value>
<field-format>#.#</field-format>
</field-definition>

2. Define the calculation logic for the goal score field.

Use the code below to create a calculation called “goalScore” that takes <weight>, divides it by 100 and then
multiplies the result by the <rating>:

<calculator id="goalScore">
<![CDATA[(weight/100)*rating]]>
</calculator>

3. Map the calculator to the field.

Use the code below to populate the <goal-score> field with the calculator “goalScore”:

<auto-population field="goal-score" mode= "auto">

<rule><calculated-result calculator-id= "goalScore"/></rule>
</auto-population>

4.16.2 Custom Calculation DTD

There are several elements that you can use to implement custom calculations.

The DTD Definitions for the following elements are described below:

● <calculator>
● <auto-population>
● <rule>
● <rule-condition>
● <table-result>
● <calculated-result>

For information on calculations, functions and operators that can be used with these elements, see the topic
“Calculations, Functions and Operators”.

Goal Management
82 PUBLIC Goal Plan Templates
<calculator> DTD definition:

<!ELEMENT calculator (#PCDATA)>

<!ATTLIST calculator
id CDATA #REQUIRED
>

The calculator is used for both evaluating conditions (for example, "If condition = x") as well as defining the
calculation result.

Option Description

id Identifier for the calculation logic. Used in reference by rule-

condition and calculated-result.

Example scenario: If the rating x the weight is less than 10, then calculate the rating x weight x difficulty

<calculator id="lowScoreRule"> <![CDATA[rating*weight<10]]> </calculator>

<calculator id= "lowScoreCalculation"> <![CDATA[rating*weight*difficulty]]> </
calculator>
<auto-population field= "score" mode= "auto">
<rule>
<rule-condition calculator-id= "lowScoreRule"></rule-condition>
<calculated-result calculator-id= "lowScoreCalculation"/>
</rule>
</auto-population>

<auto-population> DTD definition:

<!ELEMENT auto-population (rule+)>

<!ATTLIST auto-population
field CDATA #REQUIRED
column CDATA #IMPLIED
mode (auto | manual) "manual"
>

Option Valid Values Description

field field-definition ids Define the field that the system puts the
calculated result into.

column table-column ids Define the table column to populate with

the calculated result.

mode auto The system updates the results in real

time.

manual The system displays an update button for

the user to trigger the calculation and up­
date of the field.

Goal Management
Goal Plan Templates PUBLIC 83
<rule> DTD definition:

<!ELEMENT rule (rule-condition?,(table-result|calculated-result))>

Element Description

rule-condition Define a condition and when this condition is met, then one of
the results (table-results or calculated results) will be applied.

table-result If the rule-condition is met, or there is no rule-condition, then

populate the table (defined as the field in <auto-
population>) with values defined in this section.

calculated-result If the rule-condition is met, or there is no rule-condtion, then

populate the field using the calculator logic.

<rule-condition> DTD definition:

<!ELEMENT rule-condition (#PCDATA)> <!ATTLIST rule-condition calculator-id CDATA

#IMPLIED >

 Note

Changes to your goal plan XML

The <rule-condition> element can be written in two ways:

1. Option with the condition in the element:

<rule-condition> rating*weight>10 </rule-condition>

2. Option with the condition defined in a <calculator> element:

<calculator id=”xx”> rating*weight>10 </calculator>

…
<rule-condition calculator-id=”xx”></rule-condition>

If you define the condition within the element (Option1), when you export the goal plan template XML from the
system it moves it to a <calculator> element.

For example:

<calculator id="a92c6a26-a0a1-4f97-badb-79e225a2cc77"><![CDATA[]]></calculator>
<rule>
<rule-condition calculator-id="a92c6a26-a0a1-4f97-badb-79e225a2cc77"></rule-
condition>
<calculated-result calculator-id="lowScoreCalculation"/>
</rule>

The preferred method is to define a <calculator> and <rule-condition> element (Option 2).

Goal Management
84 PUBLIC Goal Plan Templates
<table-result> DTD Definition:

<!ELEMENT table-result (row+)>

<!ELEMENT row (col+)>
<!ELEMENT col (#PCDATA)>
<!ATTLIST col
id CDATA #REQUIRED
lang CDATA #IMPLIED
>

Element Attribute Description

row Container element that represents a new

row in the table.

col id Used to identify the <table-column>

id.

lang Used to specify which language locale

this value represents.

<calculated-result> DTD Definition:

<!ELEMENT calculated-result EMPTY>

<!ATTLIST calculated-result
calculator-id CDATA #REQUIRED
>

Option Description

calculator-id Identifier for the <calculator>.

Related Information

Calculations, Functions and Operators [page 85]

4.16.3 Calculations, Functions and Operators

Various calculations, functions and operators can be used with the Custom Calculation elements

The calculations, functions and operators are grouped in the following tables:

● Arithmetic Operators
● Arithmetic Grouping
● Built in Calculated Goal Field based on Sub-goal Table values

Goal Management
Goal Plan Templates PUBLIC 85
● Built in Sub-goal Calculated Ratings
● Built in Sub-Goal Table Functions
● Built in Rounding Functions
● Built in Date Functions
● Comparision Operators
● Logical Operators

 Note

Features of Built in functions include:

● Syntax: Built in functions are used by starting with FUNC. For example:

FUNC.sum(milestones.rating)

● Nesting: Built in functions support nesting. For example:

FUNC.multiple(milestones.rating, FUNC.divide(milestones.weight, 100))

 Restriction

FIELD SYNTAX CHANGE REQUIRED

Due to technical limitations, when field ids are used you must replace a dash "-" with an underscore "_". For
example, target_baseline > 250 (the field id is "target-baseline").

Arithmetic Operators
Can be used in both <rule-condition> and <calculator>.

Operator Description

+ Sum

- Difference

* Product

/ Quotient

Arithmetic Grouping
Can be used in both <rule-condition> and <calculator>.

Grouping Description

() Open and close parentheses to group expressions

Built in Calculated Goal Field based on Sub-goal Table values

Can be used in both <rule-condition> and <calculator>.

Function Description

sum(column) Add up values from one column in a sub-goal table (tasks/

targets/milestones). The result are stored as a goal level field.
For example, FUNC.sum(milestones.rating)

Goal Management
86 PUBLIC Goal Plan Templates
Function Description

avg(column) Average values from one column in a sub-goal table (tasks/

targets/milestones). The result are stored as a goal level field.
For example, FUNC.avg(milestones.weight)

Built in Sub-goal Calculated Ratings

Can be used in both <rule-condition> and <calculator>.

Function Description

gm_sub_goal_rating_of_milestones Calculate rating in milestone table using min/target/max

gm_sub_goal_rating_of_targets Calculate rating in target table using min/target/max

gm_sub_goal_rating_of_tasks Calculate rating in task table using min/target/max

<calculator id="milestoneRollup">
<![CDATA[FUNC.sum(milestones.score)]]>
</calculator>
<calculator id="subGoalWeightedScore">
<![CDATA[FUNC.multiple(milestones.rating, FUNC.divide(milestones.weight,
100))]]>
</calculator>
<auto-population field="actual-achievement" mode= "auto">
<rule><calculated-result calculator-id="milestoneRollup"/></rule>
</auto-population>
<auto-population field="milestones" column="rating" mode="auto">
<rule><calculated-result calculator-id="GM_SUB_GOAL_RATING_OF_MILESTONES"/></
rule>
</auto-population>
<auto-population field="milestones" column="score" mode="auto">
<rule><calculated-result calculator-id="subGoalWeightedScore"/></rule>
</auto-population>

Built in Sub-Goal Table Functions

Can be used in both <rule-condition> and <calculator>.

Function Description

add(column1, column2) For each row in a sub-goal table, add values from two columns
into a third column. The result is a column in a sub-goal row.
For example, FUNC.add(task.actual,
task.target)

add(column1, number) For each row in a sub-goal table, add a constant value (num­
ber) to a column and return the new value to a third column.
The result is a column in a sub-goal row. For example,
FUNC.add(task.actual, 100)

subtract(column1, column2) For each row in a sub-goal table, subtract values from two col­
umns (column1 - column2) into a third column. The result is a
column in a sub-goal row. For example,
FUNC.subtract(task.actual, task.target)

subtract(column1, number) For each row in a sub-goal table, subtract a constant value
(number) from a column and return the new value to a third
column. The result is a column in a sub-goal row. For exam­
ple,FUNC.subtract(task.actual, 100)

Goal Management
Goal Plan Templates PUBLIC 87
Function Description

multiple(column1, column2) For each row in a sub-goal table, multiply values from two col­
umns into a third column. The result is a column in a sub-goal
row. For example, FUNC.multiple(task.actual,
task.target)

multiple(column1, number) For each row in a sub-goal table, multiply a constant value
(number) by a column and return the new value to a third col­
umn. The result is a column in a sub-goal row. For example,
FUNC.multiple(task.actual, 100)

divide(column1, column2) For each row in a sub-goal table, divide values from two col­
umns (column1/column2) into a third column. The result is a
column in a sub-goal row. For example,
FUNC.divide(task.actual, task.target)

divide(column1, number) For each row in a sub-goal table, divide a column by a constant
value (number) and return the new value to a third column. The
result is a column in a sub-goal row. For example,
FUNC.divide(task.actual, 100)

Built in Rounding Functions

Can be used in both <rule-condition> and <calculator>.

Function Description

round (number) Returns the closest long. For example, round(1.4)=1,

round(1.5)=2

 Tip
Define Rounding Precision:

If you want to configure a rounding of 2 decimal places,

use this: round(1.234*100)/100=1.23. For 1 deci­
mal place: round(1.234*10)/10=1.2, and so on.

ceil(number) Returns the smallest double value that is greater than or equal
to the number. For example, ceil(1.2)=2

floor(number) Returns the largest double value that is less than or equal to
the number. For example, floor(1.9)=1

Built in Date Functions

Can be used in both <rule-condition> and <calculator>.

Function Description

diff(Date1, Date2) Calculates the difference between two dates (Date1 - Date2)
represented in days

diff(Date1, Date2, Unit) Calculates the difference between two dates (Date1 - Date2)
represented in defined Unit (MILLISECOND/SECOND/
MINUTE/HOUR/DAY/WEEK/MONTH/QUARTER/YEAR)

NOW Returns the current server time. For example, diff(NOW, d1)
equals days from d1 to NOW.

Goal Management
88 PUBLIC Goal Plan Templates
Comparision Operators
Can only be used in <rule-condition>.

Operator Description

== Equals

!= Does not equal

> Greater than

= Greater than or equal to

< Less than

<= Less than or equal to

Logical Operators
Can only be used in <rule-condition>.

Operator Description

&& And

|| Or

! Not

4.16.4 Sub-goal Auto-population Rules

The sub-goals can be configured with one of the two calculation types, per column or per row.

When you do calculation for sub-goals, you can use either calc-type="col" or calc-type="row". For example,
you want to auto-populate the score column in this table.

milestones due target achievement score

milestone 1 2012-03-14 100 10

milestone 2 2012-06-19 150 150

milestone 3 2012-09-14 200 300

If all the scores in the table are calculated with the same rule, for example, calculate score=achievement/
target*100%, you should use calc-type="col".

 Sample Code

<calculator id="c1">
<![CDATA[FUNC.divide(milestones.achievement,milestones.target)]]>
</calculator>
<auto-population field="milestones" column="score" mode="auto" calc-type="col">
<rule>
<calculated-result calculator-id="c1"/>
</rule>
</auto-population>

Goal Management
Goal Plan Templates PUBLIC 89
  Note

The default calculation type is per column. The calc-type="col" code can be omitted without impacting
calculation results.

If you want to apply conditional rules, for example, if you want to apply different calculation rules depending on
whether it is due or not, you should use calc-type="row".

 Sample Code

if (due>=now){
score=achievement/target*100% // if it's not due yet, take normal calculation
} else {
score=achievement/target*0.5*100% // if it's due, half the score
}

If now=2012-07-01, with the above conditional rules, you must use the calculation type of per row as below.

 Sample Code

<calculator id="a1">
<![CDATA[diff(milestones.due, now)>=0]]>
</calculator>
<calculator id="a2">
<![CDATA[milestones.achievement/milestones.target*100%]]>
</calculator>
<calculator id="b1">
<![CDATA[diff(milestones.due, now)<0]]>
</calculator>
<calculator id="b2">
<![CDATA[milestones.achievement/milestones.target*0.5*100%]]>
</calculator>
<auto-population field="milestones" column="score" mode="auto" calc-type="row">
<rule>
<rule-condition calculator-id="a1"/>
<calculated-result calculator-id="a2"/>
</rule>
<rule>
<rule-condition calculator-id="b1"/>
<calculated-result calculator-id="b2"/>
</rule>
</auto-population>

With this configuration, system calculate according to each row. The milestones.target represents only one
number.

For row 1, milestones.target=100, and the final score is 0.05 (applies b2).

For row 2, milestones.target=150, and the final score is 0.5 (applies b2).

For row 3, milestones.target=200, and the final score is 1.5 (applies a2).

Goal Management
90 PUBLIC Goal Plan Templates
4.16.5 Calculating Total Score of Goal Plan or Category

You can calculate the total score of a goal plan or just a catergory by using the show-total-goalscore attribute.
This feature is related to the calculated fields but is specific to displaying total scores.

Context

The use case is to display a goal plan total goal score (rating x weight summed up for all goals).

Procedure

1. Configure the standard field "goal-score".

You can use calculator and auto population to generate goal score to be rating x weight.
2. There is an attribute for <obj-plan-template> show-total-goalscore="true".
3. The same attribute can be applied to the <category> element show-total-goalscore="true".

Results

Formatting Total Score:

The goal plan and category total score values respect the <field-format> element of the "goal-score" field.

4.16.6 Calculating Ratings or Scores for Sub-goals

You can calculate raitings or total scores for sub-goals of a goal plan. Here are the steps and XML to achieve a sub-
goal calculated rating.

Context

Use Case: Support for calculated ratings at the sub-goal (milestone, target, task) level.

● Calculated sub-goal rating

● Calculate sub-goal score (rating x weight)
● Roll up sub-goal scores to the goal level rating

For information on the built in function for calculated sub-goal rating, see the topic “Calculations, Functions and
Operators”.

Goal Management
Goal Plan Templates PUBLIC 91
Procedure

1. Define achievement thresholds for min, target, max.

2. Define a table level min/target/max. This is required so that sub-goal ratings can support different min/
target/max and the overall rating can be normalized.
3. Enter in an actual achievement and the system calculates an interpolated rating for that sub-goal row
(displayed as the normalized rating).

Results

Required XML code:

<field-definition>
<field-label>Subobjectives</field-label>
<table-row-label>Subobjectives</table-row-label>
<table-column id="desc" type="text" required="false" cascade-update="push-down">
<column-label>Subobjective Name</column-label>
<column-description>Subobjective Name</column-description>
</table-column>
<table-column id="weight" type="percent" required="false" cascade-update="push-
down">
<column-label>Weight</column-label>
<column-description>Weight</column-description>
</table-column>
<table-column id="customNum1" type="number" required="false" cascade-
update="push-down" >
<column-label>Minimum</column-label>
<column-description>Minimum</column-description>
<rating-value>1</rating-value>
</table-column>
<table-column id="customNum2" type="number" required="false" cascade-
update="push-down">
<column-label>Target</column-label>
<column-description>Target</column-description>
<rating-value>100</rating-value>
</table-column>
<table-column id="customNum3" type="number" required="false" cascade-
update="push-down">
<column-label>Maximum</column-label>
<column-description>Maximum</column-description>
<rating-value>250</rating-value>
</table-column>
<table-column id="actualNumber" type="number" required="false" cascade-
update="push-down">
<column-label>Result</column-label>
<column-description>Result</column-description>
</table-column>
<table-column id="rating" type="number" required="false" cascade-update= "push-
down" width= "4">
<column-label>Score</column-label>
<column-description>Score</column-description>
</table-column>
<table-column id="score" type="number" required="false" cascade-update="push-
down" width= "4">
<column-label>Weighted Score</column-label>
<column-description>Weighted Score</column-description>
</table-column>
</field-definition>

Goal Management
92 PUBLIC Goal Plan Templates
Related Information

Calculations, Functions and Operators [page 85]

4.17 Using Goal Plan User Search

You can use Goal Plan user search to search goal plans of others on the Goal Plan page.

Prerequisites

● You have the User Search and the Goal Plan Permissions permissions.

Procedure

1. Go to Home Goals .
2. Click the downward arrow next to the name of the avatar on the Goal Plan page.

You can see not only names but also positions of your managers, peers, and direct reports with Goal Plan user
search.
3. Type in the combo box to search for other users.
4. You can include inactive users by selecting the Include inactive users in search checkbox.

 Note

You can see the Include inactive users in search checkbox even if they don’t have the permissions. The
required permissions only affect the search results.

Next Steps

● If you want to hide the Include inactive users in search checkbox, disable the Include Inactive Employees in the
search permission through Admin Center Manage Permission Roles Permission Administrator
Permissions Manage Users .
● If you want to hide peers in search result, enable Hide Peers through Admin Center Tools Platform
Feature Settings and save your changes.
● If you want to show matrix managers and matrix reports in search result, enable Admin Center Goal
Management Feature Settings Enable Goal Management People Selector .

Goal Management
Goal Plan Templates PUBLIC 93
  Note

When you use Goal Management People Selector, the users’ job titles, their peers, and the Include inactive
users in search checkbox are hidden.

Goal Management
94 PUBLIC Goal Plan Templates
5 Goal Import

Goal Import is one method available to create, edit or delete goals, using a flat file instead of the UI, and is available
to users in Admin Center.

There are two goal import functions: Beta Goal Import provides the newest features, and the older function Import
Goals also continues to be available since it provides other features that are not supported in the new import.

Features supported in Beta Goal Import include:

● Import of the metric lookup table

● Comments import
● Support the SuccessFactors Job Scheduler application used by SuccessFactors Professional Services and
Customer Service to schedule automated goal imports.
● Goal alignment management
● Update of goals created through the UI
● Import of a new Mission Statement
● Addition and update of Group Goals
● Set goals as read only through the import
● Enable goal plan permission association for customers with standard permissions
● Assign group goal permissions for employees in target populations

Features supported in Import Goals include:

● Defining goal plan visibility for users

● Ability to set goals as "read-only" through import

5.1 Turning on Goal Import

You can enable the importing goal functionality in Admin Center.

Prerequisites

You have the Import Goals permission.

Procedure

1. Go to Admin Center Goal Management Goal Management Feature Settings .

You can see a feature list.

Goal Management
Goal Import PUBLIC 95
2. Select Goal Import from the feature list.
3. Click Save.

4. Go back to Admin Center Goal Management .

You can now see the Beta Goal Import option.

 Note

You can see Import Goals option in Goal Management even if you do not select the Goal Import feature. But
the Import Goals option is a legacy feature with limited functions. It is recommended that you enable the
Goal Import feature and use the more powerful Beta Goal Import.

Results

You have successfully enabled goal importing feature.

5.2 CSV File Format

The goal import file is a CSV text file.

The CSV text file is comma-delimited, with string values enclosed in double quotes. The file can have any name but
should have a .csv extension. The rows must be tailored to the particular goal plan template for the
implementation. This enables accurate insertion of data into all field elements.

An import file can contain any combination of 3 possible types of rows: template associations, objectives, or table
fields (tasks, targets, or milestones, also known in some implementations as subgoals). You may find it simpler to
manage objectives and subgoals in separate import files, but they can be combined into one import file if desired.

The order of the rows within the file does not matter, except that if you are importing new tasks, targets, or
milestones, those should come after the associated parent goal rows.

Header rows should not be included; due to the flexible nature of the import structure, different lines within an
import file can have different fields. Each row is identified with a type flag in the first column. Import rows are
associated with users or groups of users with the following owner ID keys: USER_ID, USER_NAME, DEPT_NAME,
DIVISION_NAME, JOB_CODE, LOCATION_NAME, CUSTOM01, CUSTOM02, and CUSTOM03. (In some cases,
LOCALE is also supported.) For example, it is possible to create the same goal for all users in a given department
with a one-row import file.

If the source data is in MS Excel, save the file as a CSV (comma delimited) file, and watch out for these common
problems:

● String values that might have commas in them need to be explicitly quoted (e.g., "do this, do that").
● If you've used values for a key field (User ID, department, etc.) that are character values that look like numbers
("000123"), the cells in Excel need to be formatted as text so that Excel doesn't convert them to true numbers
(123).

Goal Management
96 PUBLIC Goal Import
When the goal plan CSV template is opened it will contain information similar to the screenshot below. The first 5
rows of the template represent the information and header column for this CSV file. These 5 rows should not be
modified. This includes the columns defined in the 5th row.

The header column row defines what types of values should be placed in the rows beneath them. The following
table describes the header types.

Column Description Example

^TYPE Identifies the item that the ACTION will OBJECTIVE_GROUPV2 and OBJEC­
be taken on. Valid options are: OBJEC­ TIVE_TEAM
TIVE, TASK, MILESTONE, TARGET, MET­
RICLOOKUP, OBJCOMMENT. Values are
case sensitive.

ACTION The action to take on the item identified ADD

in TYPE. Valid options are: ADD, UPDATE,
DELETE, ASSIGN, SHARE, UNSHARE,
UNASSIGN. Values are case sensitive.

SHARE is used to add co-owners in Team

Goals, and ASSIGN is used to assign the
Team Goals to the Goal Plan of someone
in the team.

ID This is the goal's internal ID and can only 12345

be created by the SAP SuccessFactors
system. This field will be used only to
identify a specific goal to be acted upon.
The import creator should only add a
value here if they want to modify a spe­
cific goal. The future goal export feature
will automatically retrieve each goals' ID
when a goal is exported.

Goal Management
Goal Import PUBLIC 97
Column Description Example

GUID Required. This is a unique code that the Imp123

import creator added to the import file to
update or delete goals at a later date and
time. The code will group one or more
goals into one action. Example, an import
file is used to push a goal to all employ­
ees in both the engineering and sales de­
partment. At a later date and time, all
these goals can be updated by one im­
port file line by specifying an action and
the GUID.

SUBGUID This is a unique code used to uniquely Subimp123

identify a row in a tablefield (TASK, MILE­
STONE, TARGET, METRICLOOKUP, OB­
JCOMMENT_comments). The SUBGUID
is used in the same way for tablefield
rows as the GUID field is used for goals.

FILTER_USERNAME This field is filtered against the employee msmith; cgrant

USERNAME field. This field can accept
multiple user names, separated by semi-
colons . Keyword "ALL" to be used to se­
lect all users. Used to determine which
users to create the goal for.

FILTER_MGR_ID This field is not currently supported. A

placeholder for future functionality.

FILTER_DEPT This field is filtered against the employee sales

DEPARTMENT field. Used to determine
which users to create the goal for.

FILTER_DIV This field is filtered against the employee EMEA

DIVISION field. Used to determine which
users to create the goal for.

FILTER_LOC This field is filtered against the employee Paris

LOCATION field. Used to determine
which users to create the goal for.

FILTER_CUSTxx This field is filtered against the employee Any text here
CUSTOMXX field. NOTE: only a max of
three custom fields can be used to filter
goal actions. Custom fields must be de­
fined in the data model under <custom-
filters>. Used to determine which users
to create the goal for.

Goal data columns always start with the string "OBJECTIVE_" followed by the field name that the goal will act on.
Columns for goal tables (i.e. Tasks, Targets, Milestones, Metric Lookup) will start with their respective table name
(TARGET_, TASK_, MILESTONE_, METRICLOOKUP_). In general, what follows will be the same as the field definition
id as defined in the goal plan. For example, to update the "metric" field in the goal plan you would put a value into
the "OBJECTIVE_metric" column of the import file.

Example of some, but clearly not all, goal fields that can be used in the goal import include:

Goal Management
98 PUBLIC Goal Import
Column Description Example

OBJECTIVE_CATEGORY Category ID as defined in the goal plan Financial

XML

OBJECTIVE_PARENTID Used to manage goal alignment. This is 3364

the internal goal ID for the goal to be
aligned up to.

OBJECTIVE_PUBLIC Define if the goal will be public or private. Y

Accepted values are (Y / N) or (1 / 0)

OBJECTIVE_name Maps to field-definition id="name". Increase Services Revenue per Account

OBJECTIVE_metric Maps to field-definition id="metric" Service Revenue per Account

OBJECTIVE_actual Maps to field-definition id="actual"

OBJECTIVE_weight Maps to field-definition id="weight"

OBJECTIVE_start Maps to field-definition id="start" 3/1/2014

OBJECTIVE_due Maps to field-definition id="due" 12/31/2014

OBJECTIVE_status Maps to field-definition id="state". Ac­

cepts the enum value.

OBJCOMMENT_comments Maps to field-definition id=" comments".

Goal comments are added as a separate
row in the CSV file with a ^TYPE of OB­
JCOMMENT.

OBJECTIVE_actual-achievement Maps to field-definition id=" actual-ach­ 500

ievement". This field is used to calculated
the goal's rating based on the metric
lookup table. Value is numeric.

TARGET_date Date column for the Target sub-goal ta­

ble. Sub-goal tables require a separate
row in the CSV file.

TARGET_target Target column of the Target sub-goal ta­

ble.

TARGET_actual Actual column of the Target sub-goal ta­

ble.

OBJECTIVE_NUMERIC_MET­ This column appears when a goal plan is Y

RIC_LOOKUP_TABLE configured with both achievement and
achievement-text. Accepted values are
Y / N or 1 / 0. A positive value (Y, 1) rep­
resents the goal uses the achievement
column and field.

OBJECTIVE_link Represents the URL field supported in a [[http://www.successfactors.com][Click

goal plan. Row value format is: [[URL] here]]
[Label]]

Goal Management
Goal Import PUBLIC 99
5.3 Mapping Templates to Users

The following applies to implementations with standard permissions. Implementations that include Role Based
Permissions (RBP) should manage goal plan permission through Admin Tools Manage Roles . In most
implementations, all users can see all active goal plan templates. However, in some implementations, users may be
limited to only seeing some of the active goal plan templates. If your implementation limits templates to certain
users, this import row type establishes the associations between selected users and goal plan templates. (If your
implementation does not limit templates to certain users, you can ignore this row type, do not use it when
importing goals.)

The format for this row type is as follows:

Column Description Example

System Field Static value indicating the import row TEMPLATE

type. For template associations, should
always be "TEMPLATE".

Owner ID Key Any one of the available owner ID types: USER_ID

USER_ID, USER_NAME, DEPT_NAME,
DIVISION_NAME, JOB_CODE, LOCA­
TION_NAME, CUSTOM01, CUSTOM02,
or CUSTOM03. Note: USERID can be
used in place of USER_ID.

Owner ID Value The value corresponding to the key user1234

types specified in column 2.

Plan ID The goal plan template ID to associate 1

with the user(s) described in the owner
ID key/value pair. Typically a number: 1,
2, 3, etc.

Action ADD (to establish the template associa­ ADD

tion for the user(s)) or REMOVE (to re­
move the association).

5.4 End User (Non-Admin) Upload for goal Create/Update/

Delete

We have to provide a special configuration in the goal plan template for the import from the goal plan feature.

<permission for="import-goal">
<description><![CDATA[ Employees' manager can import the goals from the objective
plan. ]]></description>
<role-name><![CDATA[EM]]></role-name>
<role-name><![CDATA[E]]></role-name>
</permission>

With the permission E, employee can go to his goal plan upload the goals for himself.

Goal Management
100 PUBLIC Goal Import
With the permission EM, employee's manager can go to the goal plan of his subordinate and upload the goals for
him.

 Note

For importing the new group goals in the import CSV file, we need use the TYPE as OBJECTIVE_GROUPV2. The
remaining other columns are same as Personal goals.

5.5 Understanding Goal ID, GUID, & SUBGUID

The ID, GUID and SUBGUID all specifically identify goals.

● The ID uniquely identifies a goal within the goal management system. ID is an optional field that is used when
the import file needs to update an objective or subobjective that does not have a GUID. The ID can be found in
the Goal Search report and Ad Hoc Goal Management reports as Goal ID. It is also possible to display the ID
directly in the Goal Plan. Columns that support the goal id are ID and OBJECTIVE_PARENTID.
● The GUID and SUBGUID are unique identifiers associated to a goal in a previous goal import. A GUID may be
related to one or more goals. The GUID field is mandatory for all ADD actions. The GUID cannot be changed for
a goal once created. SUBGUID uniquely identifies sub goal table entries for a goal.

The filter options (FILTER_) narrow down the goals to receive the action. If no filters are specified, then the goal
import will act on goals based only on the ID, GUID and SUBGUID ids. The behavior of the filter fields depends on
the action being performed.

 Note

The GUID in ad hoc report (Report-Table) is used for goals through Beta Goal Import, rather than from Goal
Library.

● For add actions - The filter fields determine what goals will receive the goal. Each goal that receives the new
goal will be assigned the GUID for the goal. If an employee already has a goal in their goal plan with the SAME
GUID, then that employee will NOT receive a second copy of the goal and a warning message will be displayed
saying how many employees did not receive a goal. This behavior will allow a company to rerun an import, for
example monthly, to make sure that employees who are captured by the filter receive the goal.

 Note

It is up to the import creator to keep goals with the same GUID in synch or run the risk of having different
versions of the same goal.

● For update and delete actions - All goals that match the given GUID, SUBGUID and filter fields are updated. This
means that if a GUID or SUBGUID are not given for an action, no update or delete will occur.

Some examples of how the actions are applied based on the ID, GUID, SUBGUID and FILTER fields.

Goal Management
Goal Import PUBLIC 101
Example

1. An add action has a GUID but no filters - All employee receive the goal.
2. An add action has a GUID and a filter - All employees that match the filter receive the goal. If an employee who
should receive the goal already has an existing goal with the same GUID; then that employee will not receive the
goal. This implies that the goal may be added to some employees (who did not previously have the goal and
would not be added to other employees (who already have the goal).
3. An update action has identified a GUID but no filters - All goals with the GUID will be updated.
4. An update action has identified a GUID and a filter for department - All the goals that match the GUID which are
in a specific department are updated.

5.6 Import File Processing

The import file is processed top down one action line at a time.

As each line is processed, an action is performed (either ADD, UPDATE or DELETE). As each line is processed a
check will be performed. If the action is invalid, a warning message is displayed identifying the problem import row
and the reason for the failure. If an action is valid, then the add, update or delete action will be performed. Each
action has different behavior.

● Add - The add action will add a new object which will be an objective or a table field row (where a table field is
either a task, milestone, target. For the December release, SF will also support the metric-lookup table). The
action will select one or more employees to receive the new object based on the specified filter fields (see the
action section for more details). Each employee selected by the filter field will then receive the object. The data
to be added for the object is based on the data located in each action column plus the GUID and SUBGUID.
Example, an action line will add a goal to an employee. The import file header section has four headings, name,
start date, due date and status. Each value in the action line that lines up under each heading section shall be
used to create the goal.

 Note

Any add action can potentially add more than one objective or table field row per line. Additionally, an
employee will not receive the new goal or table field row if they already have an existing objective or table
field row with the GUID or SUBGUID for the object being added.

● Update - All goals that match the given GUID, SUBGUID and filter fields are updated. This means that if a GUID
or SUBGUID are not given for an action, no update action will occur. If a field has a value of "\NULL", any data in
a field will be removed and the field will remain empty.
Using \NULL will wipe out data, but an error will be reported if the field is required; if the field is required, data
will not be removed, as required fields cannot be left empty. Leaving a cells value blank (empty - not to be
confused with \NULL) leaves data unchanged and will not overwrite with blank values.

 Note

Employees through the UI will be able to update a goal. This means that an update done through goal
import may overwrite a value that was previously updated by an employee.

● Delete - All goals that match the given GUID, SUBGUID and filter fields are deleted. This means that if a GUID or
SUBGUID are not given for an action, no update action will occur.

Goal Management
102 PUBLIC Goal Import
5.6.1 Error Handling

The import file is processed one action line at a time. As the action line is processed, one or more errors may be
returned. When an action line is processed, it will return the number of object successfully acted on and the
number of lines that could not be acted on and the reason why they could not be processed. The user that initiated
the import will receive an email with the summary and status of the import.

If errors are encountered, file processing continues. In other words, if an error is encountered on line 1 of a 100 line
file, lines 2 through 99 will still be processed.

Therefore if errors are reported, the user should fix and re-import only those lines that generated errors and not the
entire file.

Errors that can be reported include, but are not limited to:

● Invalid field Id _____

● User not found with id: _____
● Invalid date (expected MM/DD/YYYY) value for field id _____
● Invalid category
● Unable to create objective _____

The results indicate the line number with each error to help troubleshoot the problems.

5.7 Goal Import Examples

This section provides goal import examples.

Import Goal and Metric Lookup Table

OBJ_PLAN_ID: 51

OBJ_PLAN_NAME: 2008 Goal Plan with everything

DATE: Thu Nov 06 17:25:41 PST 2008

MAX_ERROR

FILTER_USER­
^TYPE ACTION ID GUID SUBGUID NAME

OBJECTIVE ADD GA-006 ALL

METRICLOOKUP ADD GA-006 MLT-0012 ALL

METRICLOOKUP ADD GA-006 MLT-002 ALL

METRICLOOKUP ADD GA-006 MLT-003 ALL

METRICLOOKUP ADD GA-006 MLT-004 ALL

Goal Management
Goal Import PUBLIC 103
 FILTER_USER­
^TYPE ACTION ID GUID SUBGUID NAME

METRICLOOKUP ADD GA-006 MLT-005 ALL

The OBJECTIVE row (row 6) will contain values for the goal and the METRICLOOKUP rows will only contain entries
in the METRICLOOKUP_ columns.

METRICLOOKUP_achievement METRICLOOKUP_rating

10 1

20 2

30 3

40 4

50 5

Import by Custom Filters

Custom filters must first be defined in the data model under <custom-filters>.

Import Goal Comments

Goal comments are entered on their own row with the type of "OBJCOMMENT". Similar to the behavior of goal
comments through the UI, goal comments cannot be updated or deleted through import. Goal comments can only
be added.

OBJ_PLAN_ID: 27

OBJ_PLAN_NAME: GM SuccessStore 2017 modified

DATE: Fri Sep 14 05:54:41 EDT 2018

MAX_ERROR

FILTER_USER­
^TYPE ACTION ID GUID SUBGUID NAME

OBJECTIVE ADD C124 admin

OBJCOMMENT ADD C124 SubimpC124 admin

Goal Management
104 PUBLIC Goal Import
The goal comment (OBJCOMMENT) row will only have an entry in the OBJCOMMENT_comments column.

Update Goal Created from UI

Updating a goal created through the goal plan UI can be done, but you have to get the internal goal ID to do that.

OBJ_PLAN_ID: 9

OBJ_PLAN_NAME: 1 Test Goal Plan

DATE: Mon Mar 02 11:04:13 MST 2009

MAX_ERROR

FILTER_USER­
^TYPE ACTION ID GUID SUBGUID NAME

OBJECTIVE UPDATE 3365 cgrant

Align Goals through Import

A goal can be aligned up to another goal by using the OBJECTIVE_PARENTID column. This column accepts the
internal goal ID of the goal to be aligned up to (the goal in the CSV file is the child goal, the goal defined in the
OBJECTIVE_PARENTID column is the parent goal). The internal goal ID is available from Reports > Classic
Reporting > Goal Search. The column is Goal Id in that report.

5.8 Goal Import Scenarios

This section describes some of the main goal import scenarios.

Create Goal Through UI, Update Goal Through Import

This is supported by updating the goal using the goal's internal ID.

1. Find the goal's internal ID through Goal Search classic report, Ad Hoc Goal Management Report, or Goal ID if
displayed directly in goal plan.
2. Download the import template CSV header.
3. Enter a row to update the goal putting the internal goal ID in the ID column.
4. Upload the import file.

Goal Management
Goal Import PUBLIC 105
Create Goal Through Import, Update Goal Through Import

There are two options in this scenario. You can either update the goal by internal goal ID as in the previous scenario,
or you can update the goal by GUID.

Create Goal Through UI, and Sub-Goal Through Import

To add subgoal tables, for example, tasks, you will need the goal's internal ID. When defining the subgoal rows,
reference the internal goal ID of the goal, the subgoal rows should be added to.

OBJ_PLAN_ID: 51

OBJ_PLAN_NAME: 2008 Goal Plan with everything

DATE: Thu Nov 06 17:25:41 PST 2008

MAX_ERROR

FILTER_USER­
^TYPE ACTION ID GUID SUBGUID NAME

METRICLOOKUP ADD 3365 MLT-001 cgrant

METRICLOOKUP ADD 3365 MLT-002 cgrant

METRICLOOKUP ADD 3365 MLT-003 cgrant

METRICLOOKUP ADD 3365 MLT-004 cgrant

METRICLOOKUP ADD 3365 MLT-005 cgrant

Create Sub-Goal Table Through Import, Update Sub-Goal Table Through Import

The update CSV file will be exactly the same as the create CSV file except the ACTION will be set to UPDATE.
Subgoal table rows are currently only updated using their SUBGUID.

Create Sub-Goal Table Through UI, Update Sub-Goal Table Through Import

Currently not supported.

Creating Goals that Use Numeric and Text Achievements in the Metric Lookup
Table

This scenario here has a goal plan configured to support both numeric and text target achievement columns in the
metric lookup table (achievement & achievement-text). When this happens, the CSV template will include an

Goal Management
106 PUBLIC Goal Import
additional column "OBJECTIVE_NUMERIC_METRIC_LOOKUP_TABLE". This column specifies for the goal which
achievement should be used in the metric lookup table (numeric/achievement or text/achievement-text).
Supported values are Y/N, 1/0. A "Y" or "1" represents that the goal will use the achievement/numeric.

5.9 Goal Import FAQ

This is a list of answers to frequently asked questions. Many of the issues below are current feature limitations that
will be addressed in future product releases.

1. A goal can be updated using either the new or old import feature, as long as you have the GUID for that goal.
2. Goals created through the UI can be updated through the import feature.
3. The read-only feature from the old goal import is not supported in the new import.
4. The new goal import can be scheduled through the SAP SuccessFactors Job Scheduler application.
5. The total number of goals being imported for all users should be limited within 30,000 goals for add, update,
delete, or assign action. It means you can have one goal in the CSV file being imported for 30,000 users, or two
goals in the CSV file being imported for 15,000 users, or overall 30,000 goals in the CSV file for different users.
6. The recommended maximum number of entries to add, update, delete, assign is 30,000. This could be 30,000
goals with no sub-goals, or 3,000 goals - each with 10 sub-goal entries (tasks, targets, milestones, metric
lookup).
7. The new goal import does not support the filter option of job code
8. The user name filter is the only filter which supports multiple entries in a single row (separated by semi-
colons). All other filter columns only support a single entry per row.
9. When updating a goal, only the fields to be updated need to be included in the goal. Leaving values blank will
not remove the data from the goal. To remove the data, place \NULL as the entry for the column.
10. Custom fields to be used as filters must be defined in the data model under <custom-filters>.
11. One goal should not be defined twice in the same CSV upload file. This means don't put one row in to add a goal
and then another row to update that same goal.
12. The calculated goal rating (generated through the metric lookup table) cannot be added/updated through the
import. To change or set the calculated rating set values for the actual achievement and metric lookup table.

5.9.1 How to ensure importing goals respects automatic

numbering?

When goals are imported, their "display order" (which is an internal column that indicates the order of each goal)
matches their original order in the CSV file. By default, goals are listed on the goal plan page according to their
"display order".

However, if goals are by default sorted by "Objective Name" this sorting criteria will override the default one (the
"display order"), and goals will no longer be listed in the order they appeared in the CSV import file.

To resolve this issue, you may reset the sorting criteria from "by Objective Name" to "by Display Order". As of now,
the only way to do so is to add the numbering feature, and click the "#" in the header to sort goals according to
their number. The number of each goal is generated according to the display order, so they're always in the same
order.

Goal Management
Goal Import PUBLIC 107
The numbering feature automatically generates a number for each goal, so you do not have to set it through goal
import.

 Note

It is important that an import file has less than 1000 goals to ensure correct ordering of goals. An import file
containing greater than 1000 goals may not follow the intended order, as the system will create a separate
background job when importing the CSV to optimize performance.

5.10 Limitations

1. The file size limit for beta goal import is 30,000 lines.

 Note

If the import file contains more than 30,000 goals or users, the import doesn't go through.

2. MS.Excel 2007 has character limit of 255 per cell, so if you open a file in excel, ensure text based fields don’t
get cut off.
3. The required format for the due date field (or any date field for that matter) is mm/dd/yyyy.
4. If you receive error “due parsing error," check to see if client has a file where the date format is yyyy-mm-dd
(confirm by opening the file in notepad).
5. WARNING: If you open the file in MS Excel, MS Excel may translate dates into the mm/dd/yyyy.

Goal Management
108 PUBLIC Goal Import
6 Transferring Goals Between Users

As an Admin, you can transfer goals between users.

Prerequisites

● The TGM/CDP Objective Transfer Wizard option is enabled in Provisioning.

 Remember

As a customer, you do not have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner. If you are no longer working with an implementation partner, contact SAP Cloud
Support.

● You’re granted the permission Manage User Goal Transfer .

● The users filled in the Transfer From Employee and the Transfer To Employee fields are in the target population
of your permission role.

Procedure

1. Go to Admin Center Goal Management Transfer Goal Between Users .

The Goal Transfer page displays.

2. Search and fill in user for Transfer From Employee through Find User.
3. Search and fill in user for Transfer To Employee through Find User.
4. Click Find Goals.

A table of goals of the "from" employee displays.

5. Select one or more goals that you want to transfer.

You can check the first checkbox in the first column to select every goal in the table all at once. You can also
select individual goals.

 Note

All comments and alignments are transferred with the goal. Do not transfer a master goal to a user who has
been assigned the goal previously.

6. Click Transfer.

A message displays informing you that the goals have been transferred successfully.

Goal Management
Transferring Goals Between Users PUBLIC 109
Results

You have successfully transferred goals between users.

Goal Management
110 PUBLIC Transferring Goals Between Users
7 Enabling Goal Execution

The following topics describe how to enable Goal Execution.

Goal Execution Dependencies and Prerequisites

The following is a list of dependencies and prerequisites for Goal Execution.

1. Goal Management is purchased and enabled.

2. The customer is utilizing goal alignment through cascading/linking (this is a dependency for the Execution
Map).
3. Goal Execution is intended for organizations that update and track goals frequently.
4. Adobe Flash Player v10 or higher is required to view the Execution Map
5. Private goals will not be viewed in any of the Execution map fields.
6. Goal Execution fields can only be utilized by one goal plan at a time.

7.1 Goal Plan Template Modifications to Enable Goal

Execution

You need to make several goal plan template modifications to enable goal execution.

Six new standard GM fields are introduced with goal execution.

1. (bizx-actual) Actual Percentage Complete

2. (bizx-target) Target Percentage Complete
3. (bizx-pos) Probability of Success
4. (bizx-strategic) Strategic/Non-Strategic Goal
5. (bizx-effort-spent) Effort Spent
6. (bizx-status-comments) Status Comments

bizx-actual

In a SMART goal, this should be the actual value of the metric that is being measured. It can be rolled-up to the goal
owner's plan as a SUM or AVERAGE. (rollup-calc-type="sum") or (rollup-calc-type="avg").

Sample XML for Goal Plan Template (using a roll-up as a sum):

<field-definition id="bizx-actual" type="number" required="false" detail="false"

viewdefault="on" showlabel="false" field-show-coaching-advisor="false" cascade-
update="rollup" show-allow-rollup-override="true" rollup-calc-type="sum">

Goal Management
Enabling Goal Execution PUBLIC 111
 <field-label>Execution Actual</field-label>
<field-label lang="de_DE_SF">Tatsächlich</field-label>
<field-label lang="es_ES">Actual</field-label>
<field-label lang="fr_FR">Réalisation</field-label>
<field-label lang="ja_JP"></field-label>
<field-label lang="ko_KR"></field-label>
<field-label lang="nl_NL">Werkelijk</field-label>
<field-label lang="pt_BR">Atual</field-label>
<field-label lang="zh_CN">????</field-label>
<field-description>Bizx Actual</field-description>
<field-description lang="fr_FR">Actuel</field-description>
</field-definition>

bizx-target

In a SMART goal, this should be the target value of the metric that is being measured. It can be rolled-up to the goal
owner's plan as a SUM or AVERAGE. (rollup-calc-type="sum") or (rollup-calc-type="avg") .

Sample XML for Goal Plan Template (using a roll-up as a sum):

<field-definition id="bizx-target" type="number" required="false" detail="false"

viewdefault="on" showlabel="false" field-show-coaching-advisor="false" cascade-
update="rollup" show-allow-rollup-override="false" rollup-calc-type="sum">
<field-label>Execution Target</field-label>
<field-label lang="de_DE_SF">Bewertungsmaßstab</field-label>
<field-label lang="es_ES">Métrica</field-label>
<field-label lang="fr_FR_SF">Mesure</field-label>
<field-label lang="ja_JP"></field-label>
<field-label lang="ko_KR"></field-label>
<field-label lang="nl_NL">Meeteenheid</field-label>
<field-label lang="pt_BR">Métrica</field-label>
<field-label lang="zh_CN">??</field-label>
<field-description>BizX Target</field-description>
<field-description lang="fr_FR">Measure</field-description>
</field-definition>

bizx-pos

Probability of Success - An indicator for a goal that a user can use to project whether or not they will be successful
in accomplishing this goal.

Currently you should ALWAYS have 3 enum values for this field and they should be indicated in the last enum
coding below.

<field-definition id="bizx-pos" type="enum" required="false" detail="false"

viewdefault="on" showlabel="false" field-show-coaching-advisor="false" cascade-
update="rollup" show-allow-rollup-override="true" rollup-calc-type="avg">
<field-label>Probability of Success</field-label>
<field-label lang="de_DE_SF"> Status</field-label>
<field-label lang="es_ES">Estatus</field-label>
<field-label lang="fr_FR_SF"> Statut</field-label>
<field-label lang="ja_JP"></field-label>
<field-label lang="ko_KR"></field-label>
<field-label lang="nl_NL">Status</field-label>
<field-label lang="pt_BR">Situação</field-label>
<field-label lang="zh_CN"></field-label>

Goal Management
112 PUBLIC Enabling Goal Execution
 <enum-value value="1" style="background:red;color:black;">
<enum-label>Low</enum-label>
</enum-value>
<enum-value value="2" style="background:yellow;color:black;">
<enum-label>Med</enum-label>
</enum-value>
<enum-value value="3" style="background:green;color:white;">
<enum-label>High</enum-label>
</enum-value>
<default-value>3</default-value>
</field-definition>

bizx-strategic

Used to identify strategic goals, currently only visible in the Execution Map.

Currently you should only have 2 values for this field and they should be:

<enum-value value="0" style="background:white;color:black;">

<enum-label>Non-strategic</enum-label>
</enum-value>
<enum-value value="1" style="background:white;color:black;">
<enum-label>Strategic</enum-label>
</enum-value>
<default-value>0</default-value>

Sample XML for Goal Plan Template:

<field-definition id="bizx-strategic" type="enum" required="false" detail="false"

viewdefault="on" showlabel="false" field-show-coaching-advisor="false" cascade-
update="push-down" show-allow-rollup-override="false" rollup-calc-type="avg">
<field-label>Strategic Goal</field-label>
<field-label lang="de_DE_SF"> Status</field-label>
<field-label lang="es_ES">Estatus</field-label>
<field-label lang="fr_FR_SF"> Statut</field-label>
<field-label lang="ja_JP"></field-label>
<field-label lang="ko_KR"></field-label>
<field-label lang="nl_NL">Status</field-label>
<field-label lang="pt_BR">Situação</field-label>
<field-label lang="zh_CN"></field-label>
<enum-value value="0" style="background:white;color:black;">
<enum-label>Non-strategic</enum-label>
</enum-value>
<enum-value value="1" style="background:white;color:black;">
<enum-label>Strategic</enum-label>
</enum-value>
<default-value>0</default-value>
</field-definition>

bizx-effort-spent

Use this standard field to control field permissions for the Effort Spent field that appears in the Goal Plan sub-tabs
called Execution Map, Status Report, and Meeting Agenda. This field will not appear in the goal plan or the goal edit
window because Effort Spent is specific to Status Reports. : Effort Spent must contain 6 enum values, there's no

Goal Management
Enabling Goal Execution PUBLIC 113
configuration support for how many intervals there are. The configuration supports the ability to change the labels
of the 5 different values (along with the label of the "no selection" value)

<field-definition id="bizx-effort-spent" type="enum" required="false"

detail="false" viewdefault="off" showlabel="true" field-show-coaching-
advisor="false">
<field-label>Effort Spent</field-label>
<field-description>Effort Spent</field-description>
<enum-value value="0" style="background:white;color:black;">
<enum-label>None</enum-label>
</enum-value>
<enum-value value="1" style="background:white;color:black;">
<enum-label>Very Little</enum-label>
</enum-value>
<enum-value value="2" style="background:white;color:black;">
<enum-label>A Little</enum-label>
</enum-value>
<enum-value value="3" style="background:white;color:black;">
<enum-label>Some</enum-label>
</enum-value>
<enum-value value="4" style="background:white;color:black;">
<enum-label>A Lot</enum-label>
</enum-value>
<enum-value value="5" style="background:white;color:black;">
<enum-label>Really A Lot</enum-label>
</enum-value>
<default-value>0</default-value>
</field-definition>

bizx-status-comments

Use this standard field to control field permissions for the Status Report Comments field that appears in the
Execution Map, Status Report, and Meeting Agenda. This field will not appear in the goal plan or the goal edit
window because Status Report Comments are specific to each Status Report.

<field-definition id="bizx-status-comments" type="textarea" required="false"

detail="false" viewdefault="on" showlabel="true" field-show-coaching-
advisor="false" cascade-update="regular">
<field-label>Status Comment</field-label>
<field-description>Status Comment</field-description>
<default-value>00.0</default-value>
</field-definition>

7.2 Goal Plan Layout Configuration

In order to have the goal execution fields show up in the goal plan, you must enter the new code in the plan layout
section of the XML.

The following code needs to be entered.

<column weight="1.0">
<field refid="bizx-actual"/>
</column>
<column weight="1.0">

Goal Management
114 PUBLIC Enabling Goal Execution
 <field refid="bizx-target"/>
</column>
<column weight="1.0">
<field refid="bizx-pos"/>
</column>
<column weight="1.0">
<field refid="bizx-strategic"/>
</column>

7.3 Enabling Goal Execution in Provisioning

You need to make changes under Provisioning to enable Goal Execution.

Under Provisioning Company Settings you will see a new section called Configure Goal Execution. Enable all
the check boxes under this section.

 Remember

As a customer, you do not have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner. If you are no longer working with an implementation partner, contact SAP Cloud
Support.

7.4 Admin Configuration

You need to make several changes in the Admin section to enable Goal Execution, if RBP (Role-Based Permission)
is not configured.

Permissions

Under Admin Company Settings Administrative Privileges you'll see a section called Manage Goal
Execution with four permissions.

Goal Management
Enabling Goal Execution PUBLIC 115
● Manage Configuration of Goal Execution - Grant this permission to an administrator who will manage
configurations. Users with this permission will see a new area in Admin Tools: Admin Goal Management
Goal Execution Settings (See Administrative Configuration for more details).
● Access Execution Map - Grant this permission to any user that should see the sub-tab Execution Map.
● Access Meeting Agenda - Grant this permission to any user that should see the sub-tab Meeting Agenda.
● Access Status Report - Grant this permission to any user that should see the sub-tab Status Report.

Administrative Configuration

Users with the "Manage Configuration of Goal Execution" permission will see this new link under the Admin page.

Goal Management
116 PUBLIC Enabling Goal Execution
Clicking on the link noted above, "Goal Execution Settings" will bring up a window that asks for the following
information:

Field Description

Goal Plan Select the goal plan to be used in the Execution Map and Status Report pages (reminder: the goal
execution fields can only view one goal plan at a time)

Start Date This date is used for sending reminder and late email notifications for the Status Report. Recom­
mendation is to use the start of the customer's fiscal year because we may introduce enhance­
ments that would use the start date with that assumption.

 Note
If there is no date entered here, you will receive an error message.

Send due notification 1 supported reminder intervals. Send an email notification x days before a status report is due. Sta­
(days) tus report due dates are calculated based on the Start Date and Interval values. You can set up to 1
reminder email.

Send late notification 1 supported over due intervals. Send an email notification x days after a status report is due. Status
(days) report due dates are calculated based on the Start Date and Interval values. You can set up to 1 re­
minder emails.

Goal Management
Enabling Goal Execution PUBLIC 117
Email Notification Templates

Four new email notification templates can be found under System E-Mail Notification Templates .

● Status Report Due Reminder - Email sent out to users who have not submitted a status report since the last
status report due interval.
● Status Report Late Reminder - Email sent to users who have not submitted a current status report
● Status Report Update Request - From the Execution Map when an update request is made, this is the content
of that email
● Status Report Submitted Notification - Email sent to the manager of an employee when they submit a status
report.

7.5 Meeting Agenda Planner

A summary of the features of the meeting agenda planner.

Users that have access to the Status Report page can also have access to the Meeting Agenda page.

Goal Management
118 PUBLIC Enabling Goal Execution
This feature will work in conjunction with the Meeting Agenda right panel section in the Execution Map. This means
that goals added from the Execution Map will be included into the Meeting Agenda page.

The basic features, and use case flow, for the enhancement are:

1. Select user(s) that you want to see goals for.

2. Filter those goals by goal attributes.
3. Sort results.
4. Generate meeting agenda (can be sent to MS Outlook to invite meeting attendees with the agenda attached).

You can also add the goal to the meeting agenda watch list.

Goal Management
Enabling Goal Execution PUBLIC 119
7.6 Useful Tips for Goal Execution

A list of useful tips for Goal Execution.

1. The Goal Execution sub tabs (Status Report; Execution Map; Meeting Agenda) are located under the GM
"Goals" tab.
2. Visibility for all 3 sub-tabs are controlled by permissions under Administrative Privileges. (This is for standard
permissions. RBP controls Goal Execution in the Manage Roles tool.)
3. Currently the Effort Spent and Probability of Success fields are only configurable in terms of label and not
values or quantities.
4. Status Report dates are "soft". We do not strictly enforce that a status report has to be submitted once a week,
or that specifically a week has to be captured. The Status Report interval under admin is only for email
notifications. Status Reports can be submitted whenever.

 Note

Goal Execution updates will only sync onto a goal plan after clicking the Send Status Update button.

5. Goal plan field permission access/visibility is respected throughout Goal Execution pages. I.e. If you're not
allowed to see the details on the goal plan you won't be able to see them in GE.
6. Effort Spent under Status Report for each goal is independent of the other goals in the status report (i.e. effort
spent doesn't have to add up to 100% for all goals in the status report).
7. Only one goal plan template is supported by Goal Execution at a time.
8. Email notifications for Status Report Submitted Notification and Update Request are required for these
features to work, otherwise an error message will display.

Goal Management
120 PUBLIC Enabling Goal Execution
8 Permissions

This chapter describes the permission settings in Goal Management and Execution.

8.1 What Are Role-Based Permissions?

Role-Based Permissions (RBP) is a security model that allows you to restrict and grant access to your SAP
SuccessFactors HXM Suite. RBP controls access to the applications that employees can see and edit. This is a
suite-wide authorization model that applies to the majority of the SAP SuccessFactors products.

Open this video in a new window

The RBP security authorization model uses groups and roles to organize employees (groups) and permissions
(roles) to control access to your system; By organizing employees into groups and permissions into roles you can
assign a group of employees the same set of permissions by assigning them a role.

 Note

RBP is approved for organizations with up to 1,500,000 employees. We’ll continue to raise this bar in the future.
When in doubt, contact SAP Cloud Support.

Role-based permissions contain three main elements: permission groups, permission roles, and target populations.

● Permission groups are a set of employees who share certain attributes such as City or Job Code and require
access to a similar set of tasks within your system.
● Permission roles are defined as a set of permissions. You can assign the permission roles you define to a
permission group, and if the role requires that you define a target population, meaning a group to perform
tasks for, you assign the target population when you define the role.
● Target populations are groups that are assigned to permission roles when the permission granted is performed
on behalf of other employees.

 Tip

We recommend that you create groups before creating roles so that during role creation, you can select the
group for which to grant the role. In addition, you need defined groups for roles that require a target population.

Permission Groups [page 122]

Permission groups are used to define groups of employees who share specific attributes. You can use
various attributes to select the group members, for example a user's department, country/region, or job
code.

Permission Roles [page 128]

RBP uses permission roles to group a set of permissions. After grouping the permissions into a role, you
can assign the role to a group of users, granting them access to certain tasks and features in your system.

Grant Permission Roles [page 135]

Goal Management
Permissions PUBLIC 121
 You can assign a permission role to everyone or to a subset of employees, determined by permission
groups, target populations, or by relationships. When defining a role in RBP, you can assign the role to a
group that you've created or you can assign roles based on hierarchical relationships. Some roles will
require that you also assign target populations, they're only necessary for certain permissions in a role and
your system will notify you when a target population is required.

What are Rules in RBP? [page 143]

Rules in RBP are used to define access to permissions in your system.

Related Information

Creating Dynamic Permission Groups [page 126]

Creating Permission Roles [page 130]
Granting Roles to Groups [page 137]

8.1.1 Permission Groups

Permission groups are used to define groups of employees who share specific attributes. You can use various
attributes to select the group members, for example a user's department, country/region, or job code.

 Example

There might be a permission group called "Human Resources in US", which lists all US-based employees who
work in the HR department. To define this group, you would specify that users must match the selection criteria
"Country/Region = United States" and "Department = HR".

 Note

The attributes or selection criteria that are available for defining groups are configurable.

In RBP, you can assign permission roles to permission groups. In addition, you use groups to define the target
population a granted user has access to.

 Example

The group "Human Resources in US" might have access to the group "US Employees".

Groups configured with criteria other than specific user names are called dynamic (as opposed to static),
which means that the assignment of employees into and out of a group is automated. For example, a group of
granted users can be “All employees in the Sales department”. As employees are transferred into and out of the
sales department, their permissions will automatically adjust. This automation will save you time and money.
This is especially beneficial for large organizations that need higher levels of administrative efficiency.

Creating Static Permission Groups [page 123]

Static permission groups are created and modified by adding individual user names to a group using an
excel spreadsheet. They store a static list of users instead of a list based on dynamically generated criteria.
Changing user information does not modify group members, you must redefine group members by
importing an updated spreadsheet.

Goal Management
122 PUBLIC Permissions
 Creating Dynamic Permission Groups [page 126]
Dynamic permission groups are generated automatically when the attributes of employees match the
group selection criteria. Administrators can create and manage dynamic permission groups for both
employees and external users.

View, Edit, Copy, and Delete Permission Groups [page 128]

You can edit, copy, and delete static or dynamic permission groups. For dynamic groups, you can also view
the group's change history.

8.1.1.1 Creating Static Permission Groups

Static permission groups are created and modified by adding individual user names to a group using an excel
spreadsheet. They store a static list of users instead of a list based on dynamically generated criteria. Changing
user information does not modify group members, you must redefine group members by importing an updated
spreadsheet.

Procedure

1. In the Admin Center, search for Manage Permission Groups.

2. Click Import Static Groups to create or modify a group.
3. Select between Full Replace or Delta Replace.
A full replace, creates or entirely replaces a group, while a delta replace adds members to an already existing
group.

4. Download a blank CSV template after you've chosen an import type. The Full Replace template has two column
headers, GROUPNAME and USERID. The Delta Replace has an additional Action column.

Goal Management
Permissions PUBLIC 123
5. For each user that you add to a group, add the group name to the GROUPNAME column and user's ID to the
USERID column.

 Note

For new users, you can create user IDs in the upload file.

 Note

Character encoding of your file should be Unicode(UTF-8). The maximum file size is 20MB. If your import
file exceeds 20MB, you can either split the file into several smaller files or request Professional Services to
modify the system configuration file.

6. Select the file with your data by clicking Choose File.

7. Click Validate File to validate file format, file size, etc.
8. If the validation is successful, click Upload to import the static permission groups.

If your file has errors, they display at the top of the Import Static Group window.

 Note

For one group type, a maximum of two jobs can run at the same time.

Results

After the upload completes, the system sends you a notification with success or error messages. Successfully
created groups display in the group list after refreshing your system.

Goal Management
124 PUBLIC Permissions
8.1.1.1.1 Adding Individual Members to Static Groups

You can add members to a static group in your system or by importing an excel file to your system.

Procedure

1. In the Admin Center, search for Manage Permission Groups.

2. Click the name of the static group you're updating.

The Permission Group screen displays.

3. To add a user to a static group, click Add User.
4. Search for the users you'd like to add to the group.

Entering keywords in the search field displays user names.

5. Select each user you want to add to the group.

Each user you select automatically displays in the right pane.

6. Click Done.

The users you selected are added to the group immediately.

Goal Management
Permissions PUBLIC 125
8.1.1.1.2 Deleting Members from Static Groups

Although you add members to a static group using a spreadsheet, you can delete static group members using the
system.

Procedure

1. In the Admin Center, search for Manage Permission Groups.

2. Click the name of the static group you're updating.

The Permission Group screen displays.

3. Select the users that you want to delete from the group.
4. Click Delete.

The list of users updates immediately.

5. Click Close.

Results

Deleted members will no longer have access to the tasks or data of the group.

8.1.1.2 Creating Dynamic Permission Groups

Dynamic permission groups are generated automatically when the attributes of employees match the group
selection criteria. Administrators can create and manage dynamic permission groups for both employees and
external users.

Procedure

1. In the Admin Center, search for Manage Permission Groups.

2. Click Create New to create a new permission group.

The Permission Group page opens.

3. Enter a name for your permission group in the Group Name field.
4. Choose a User Type for your group.

The available user types vary depending on how your system is configured. Possible values may include:
○ Employee (default)
○ External Learning User

Goal Management
126 PUBLIC Permissions
  Note

The External Learning User option is only available if you have Learning enabled in your system.

When defining a dynamic group for an external learning user, you can identify an External Source Channel to
complete the criteria for inclusion. This allows external learning users to be defined based on the source of
origin. The external source channel is only available to SAP SuccessFactors Learning customers. The External
Learning User must be enabled in Provisioning for external learner and external source channel to be available.

 Tip

When defining External Learning User groups in your system, it is recommended that you do not create
more than 50 groups.

5. Choose the group selection criteria from the People Pool, in the Choose Group Members section.

Depending on the complexity of your permission group selection criteria, you can choose multiple people
pools.

6. In the Search Results screen, enter a search term or click the  search, to display all available values.

For some categories, a smaller pop-up window appears where you can enter additional values or information,
such as Time Zone settings. If you select the Team View category, you can use hierarchical relationships to
specify the group. This allows you to apply rules such as: everybody in Carla Grant's team, all levels deep.
7. Make your selection and click Done.
8. If you want to add another condition for defining the people pool, click Add another category and choose a
category and item. If you use two or more categories, this functions as an AND operation, that is, only users are
selected who meet all selection criteria.

 Example

If you want to create a group of sales employees working in the US, you would need to choose the category
Department and select Sales. You add a second category Country and select USA.

9. Complex group definitions may require you to use multiple people pools. If you use two or more people pools,
these people pools functions as an OR operation, that is, all users are selected who fulfill the selection criteria
of at least one pool.

Click Add another People Pool and then add categories and items.

 Example

You have two different offices: An office in Chicago and an office in Boston. Each office has a Sales team and
a Finance team. You only want to include Sales employees from the Chicago office and Finance employees
from the Boston office. You'll need to create two separate pools then.

 Note

The number of people pools in a group is limited to three.

10. If there are employees you'd like to exclude from the Permission Group definition, select them in the Exclude
these people from the group section.
11. If you want to prevent the group being updated automatically when new employees match the selection
criteria, click Lock group.

Goal Management
Permissions PUBLIC 127
12. Click Done to complete the process.

8.1.1.3 View, Edit, Copy, and Delete Permission Groups

You can edit, copy, and delete static or dynamic permission groups. For dynamic groups, you can also view the
group's change history.

Context

 Note

You can only delete a permission group if it has no associated role.

Procedure

1. Go to the Admin Center Tools and search for Manage Permission Groups.
2. In the Manage Permission Groups screen, click the Take Action dropdown menu next to the permission group
you want to modify.
3. Choose the desired action.

8.1.2 Permission Roles

RBP uses permission roles to group a set of permissions. After grouping the permissions into a role, you can assign
the role to a group of users, granting them access to certain tasks and features in your system.

Permission roles consist of a set of permissions that give employees access rights to an employee or a group of
employees. As such an employee or a group that has been granted with a permission role has access to certain

Goal Management
128 PUBLIC Permissions
aspects of the SuccessFactors application or to aspects of employee data. With this access, they can perform
functions within the application for other groups of employees.

Role-based permissions allow you to grant a role to a specific employee, a manager, a group, or to all employees in
the company. The roles can provide very granular permissions, as this example illustrates:

 Example

There may be roles such as "HR Compensation and Benefits Manager", "HR Manager for Sales", and "HR
Learning and Development Manager". While all three are HR managers, their roles have been distinctly carved
out — one handling compensation and benefits, another handling the sales team, and the third handling
Learning and Development.

When your permissions roles consist of one or more permissions that require a target population, you'll need to
specify a target to complete creation of the role. Roles that require a target population will contain a permission
that gives a group access to perform actions or view information for other employees.

 Example

A Manager may have a role where one permission allows the manager to modify the salary for all of their direct
reports. In this example, the manager's direct reports represent the target population needed for the
permission role.

 Note

Customers can have as many permission roles as the company requires.

Creating Permission Roles [page 130]

Permission roles can be created for employees and for external users, such as External Learning Users.

Assigning Permissions to a Role [page 131]

After creating groups and roles, you'll need to assign permission roles to your employee groups.

View, Edit, Copy, and Delete Permission Roles [page 132]

You can edit, copy, or delete a permission role, view a summary of a permission role, and view its change
history.

Creating a New Role for External Users [page 133]

Role-based permissions support the role of External User and allows the External Learner User limited
access to complete specific tasks or training.

Goal Management
Permissions PUBLIC 129
8.1.2.1 Creating Permission Roles

Permission roles can be created for employees and for external users, such as External Learning Users.

Context

Permission roles contain a group of permissions that can be granted to an employee or a group of employees
known as the Granted Users Circle. In general, it's best practice to define your user groups before defining your
permission roles.

Procedure

1. Go to the Admin Center.

2. In the Tools Search field, select Manage Permission Roles.
3. To add a Permission Role, click the Create New button. The Permission Role Detail page opens.
4. In the Role Name field, type a name describing of what the role allows you to do.
5. In the Description field, provide a statement describing what the role allows an employee to do. Add a note
about when the role was created and by whom.
6. 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.
7. On the left side of the page, you'll see the different permission categories. Click a permission category to reveal
the different permissions.

The list of permissions associated with this category is displayed.

Goal Management
130 PUBLIC Permissions
8. Select the checkboxes next to the permissions you'd like to grant to the role.
9. Click the Done button when you finish marking your selections.
10. In the Grant this role to section, click the Add button to select the employees to be granted this permission.
11. Grant the permissions and specify the target population according to what you have defined in the workbook.
For a detailed description, see the topic on granting permission roles in the Related Links section.
12. For some permissions, it might be necessary to exclude the granted users from applying the permissions on
themselves. For this, select Exclude Granted User from having the permission access to him/herself.

 Example

If the role grants permission to edit the salary, you want to prevent the members of this permission group
to be able to edit their own salary as well.

13. Click the Done button to assign this role to the defined users. You are taken back to the Permission Role Detail
page.
14. Click the Save Changes button to complete creating the role.

Next Steps

Once this role is successfully created, the new role will be listed on the Permission Role List page.

Related Information

Grant Permission Roles [page 135]

8.1.2.2 Assigning Permissions to a Role

After creating groups and roles, you'll need to assign permission roles to your employee groups.

Procedure

1. 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.
2. On the left side of the page, you'll see the different permission categories. Click a permission category to reveal
the different permissions.

The list of permissions associated with this category is displayed.

Goal Management
Permissions PUBLIC 131
3. Select the checkboxes next to the permissions you'd like to grant to the role.
4. Click the Done button when you finish marking your selections.
5. Click Save Changes.

Next Steps

Assign a target population, if your role indicates that a target is needed.

8.1.2.3 View, Edit, Copy, and Delete Permission Roles

You can edit, copy, or delete a permission role, view a summary of a permission role, and view its change history.

Context

When you copy a role, only the permissions get copied over. You will need to manually grant employees access to
this new role.

Procedure

1. Go to the Admin Center Tools and search for Manage Permission Groups.

Goal Management
132 PUBLIC Permissions
2. In the Permission Role List screen, click the Take Action dropdown menu next to the permission role you want
to modify.
3. Choose the desired action.

8.1.2.4 Creating a New Role for External Users

Role-based permissions support the role of External User and allows the External Learner User limited access to
complete specific tasks or training.

The external user role can be granted to the Everyone (External Learner) group. Permissions for the external user
role can be set to grant access to SAP Jam and SAP SuccessFactors Login, Learning modules, and Mobile.

For complete details about External Learning, please refer to the Offering Learning to the Extended Enterprise
guide.

8.1.2.4.1 Resetting External User Password

If you have external users, consider creating a management system for them so that you can maintain their access.

Prerequisites

Enable the following option from Provisioning:

● Enable External Learning User : This allows the external users to self-register as a user and log in to access
Learning and Onboarding. Also, the option External Users from Onboarding and/or Learning (If enabled) will
appear in Reset User Password only if Enable External Learning User is enabled in Provisioning.

 Remember

As a customer, you do not have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner. If you are no longer working with an implementation partner, contact SAP Cloud
Support.

Goal Management
Permissions PUBLIC 133
Context

When you have external users in your extended enterprise, your plan for maintaining them should include: resetting
user passwords, granting access, and so on. In most cases, you manage external users as you do any other users.

One exception is target populations. External users can be a unique target population. For example, if you want to
manage external users in Onboarding, you must add All(External Onboarding User) to the target population of users
managed by the administrator.

Procedure

1. To reset an external user password, go to Admin Center Reset User Password .

The Resetting User Passwords page appears. From this page you can reset individual user password, or reset
the passwords for a group of users.
2. Select External Users from Onboarding and/or Learning (If enabled) from the Find dropdown.

Enter the First Name, Last Name, or the Username to search for the user whose password you are trying to
reset. You can filter your search further using Starts With or Exact Match.
3. When the user details appear on the screen, select the user and enter the new password in the New Password:
field and confirm the same in the Confirm Password: field.
4. Click Reset User Password.

Results

You have successfully reset the external user password.

8.1.2.4.2 Mapping External Users from Learning Sites to SAP

SuccessFactors Roles

Create a role mapping for external users so that users who log in through SAP SuccessFactors Learning sites are
granted the correct permissions.

Prerequisites

Role Based Permissions (RBP) must be enabled.

Goal Management
134 PUBLIC Permissions
Procedure

1. Log in and go to Admin Center.

2. In Tools, click See All.
3. In Search Tools, type Manage Permission Roles and then click Manage Permission Roles.
4. Click Create New Role For External User.
5. In User Type, select External Learner, and then click Done.
6. Type a name and description for the role and then click Permissions.

The Permission Settings page opens.

7. In User Permissions General User Settings , select User Login.

8. In User Permissions Learning , select Learning Access Permission.

You can select additional permissions. For example, you can grant the external users access to SAP Jam.
9. Click Done.

You return to the Permission Role Detail page.

10. Click Add.

The Grant this role to... page opens.

11. In Grant role to, select Everyone (External Learner).
12. Click Done.

You return to the Permission Role Detail page.

13. Click Save Changes.

8.1.3 Grant Permission Roles

You can assign a permission role to everyone or to a subset of employees, determined by permission groups, target
populations, or by relationships. When defining a role in RBP, you can assign the role to a group that you've created
or you can assign roles based on hierarchical relationships. Some roles will require that you also assign target
populations, they're only necessary for certain permissions in a role and your system will notify you when a target
population is required.

● Permission groups: You assign a permission role to a defined group of users. However, relationships can also
play a role here as you can define that the granted user's managers have the same permissions. You can also
define how many levels up in the hierarchy you want this permission to be granted.

Goal Management
Permissions PUBLIC 135
  Note

If you want to grant a role to a named user, you first have to create a group and add the user to this group.
Then you can grant the role to the just created group.

● Target Population: Depending on the permissions included in the role, you might also have to define the target
population. Not all permissions require you to define a target population. For example, if the permission
includes just the access to an application (such as the Learning Access Permission), there is no need to add a
target group. For certain permissions, in the Permission settings screen, a target population must be defined.
This is identified by the "t" icon next to the permission name with the following text displayed: t= Target needs
to be defined.

 Note

A target population for an external Learning user can be defined two ways:
○ Select Everyone (External Learner)
○ Select Target population of: and click Select, to select groups

● Relationships: Access groups can be defined using relationships (for example, manager-employee
relationship) that are derived from the job relationship object. These relationships can be hierarchical or non-
hierarchical. You can find more information in the following chapter Using Relationships to Grant Permissions
[page 140].

Goal Management
136 PUBLIC Permissions
●  Note

If you allow the respective managers to have the same permissions, this may have a negative impact on the
performance. The hierarchy then has to be checked whenever such a manager tries to access an element
which was permissioned this way.

8.1.3.1 Granting Roles to Groups

After creating your roles, you must assign the role to a group of employees. This ensures that employees are given
access the permissions they need to perform their tasks.

Procedure

1. Go to the Admin Center.

2. In the Tools Search, search for Manage Permission Roles.
3. Select one of the permission roles you created.
4. In the Grant this role to section of the Permission Detail screen, click Add.
5. When the Grant this role to screen displays, select Permission Group.

Goal Management
Permissions PUBLIC 137
6. Click Select to select the access groups you wish to assign to this permission role.

You can allow managers to have the same permissions and define how many levels up in the hierarchy you want
this permission to be granted. However, allowing respective managers to have the same permissions may have
a negative impact on the performance. The hierarchy then has to be checked whenever such a manager tries to
access an element which was permissioned this way.
7. Exclude Granted Users:

For some permissions, it might be necessary to exclude the granted users from applying the permissions on
themselves. For this, select Exclude Granted User from having the permission access to themselves.

 Example

If the role grants permission to edit the salary, you want to prevent the members of this permission group
to be able to edit their own salary as well.

8. Click Done to assign this role to the defined users. You are taken back to the Permission Role Detail page.
9. Click Save Changes to complete creating the role.

Next Steps

If required, assign a target population to your role.

8.1.3.2 Assigning Target Populations to a Role

Target populations are assigned to roles that require tasks to be performed on behalf of another employee.

Context

Target populations allow you to give employees such as managers and administrators access to data or tasks that
need to be maintained for other employees. Depending on the permissions included in the role, you may need to
define the target population. Not all permissions require you to define a target population. For example, if the
permission includes just the access to an application (such as the Learning Access Permission), there is no need to
add a target group. For certain permissions, in the Permission settings screen, a target population must be
defined. This is identified by the "t" icon next to the permission name with the following text displayed: t= Target
needs to be defined.

Procedure

1. Go to the Admin Center.

2. In the Tools Search, search for Manage Permission Roles.

Goal Management
138 PUBLIC Permissions
3. Select one of the permission roles you created.
4. In the Grant this role to section of the Permission Detail screen, click Add.
5. Select Everyone or choose Target population of to select a group .

6. Click Select to select the target groups that you want to assign to this permission role.
7. Exclude Granted Users:

For some permissions, it might be necessary to exclude the granted users from applying the permissions on
themselves. For this, select Exclude Granted User from having the permission access to themselves.

 Example

If the role grants permission to edit the salary, you want to prevent the members of this permission group
to be able to edit their own salary as well.

8. Click Done to assign this role to the defined users. You are taken back to the Permission Role Detail page.
9. Click Save Changes to complete creating the role.

Goal Management
Permissions PUBLIC 139
8.1.3.3 Using Relationships to Grant Permission Roles

There are relationships that can be specified through employee fields, and managed through tools, like the
employee data.

General Relationship Types: Hierarchical relationships are characterized by a reporting line between the granted
user and the target user. These are relationships between employees and their managers, and employees and their
second managers or alternate managers. Non-hierarchical relationships on the other hand are single-level
relationships. These include the relationship of an employee to the HR manager, the matrix manager and custom
manager. While each employee can have only one Manager, one Second Manager and one HR Manager, they can
have multiple Matrix Managers and Custom Managers.

Employee Central Only: If employees have global assignments (that is, a job in another country), they have both a
home manager and a host manager. In addition, they have a home HR manager and a host HR manager. All
managers need to have access to both the home jobs of the employees as well as to the host jobs of the employees.
This is covered by the following additional relationship types for global assignments:

Employee Central Only: Relationship Types for Global As­

The Five General Relationship Types signments

Manager Home Managers

Second/Alternate Manager Home HR Managers

HR Manager Host Managers

Matrix Manager Host HR Managers

Custom Manager

8.1.3.3.1 Delegate Relationship Assignments

As a delegator you can assign delegates to perform actions on your behalf that affects other employees in your
organization.

As a manager, you can use the Delegate A and Delegate B relationship roles to assign permissions to up to two
individuals for each role, allowing them to act as your delegates. The delegate users, you assign, will have access to
your direct and indirect reports and can perform tasks that have been permitted to you, while acting as your
delegates. You can assign up to two delegates per delegate role and each delegate can be given separate tasks or
permissions to cover different functional or regional areas.

 Note

You must configure Delegate relationship type in the Employee Central Picklist. After you've configured your
delegates, you'll see the option to give permissions to this relationship type in your system. For more
information about how to configure picklists, see the topic Picklist Configuration for Employee Status and Job
Relationship Type.

Goal Management
140 PUBLIC Permissions
Why would I want to use delegates?

You might use a delegate when you want to assign delegates permissions in different functional areas.

You can also assign permissions to delegates that separate functionality according to locations.

 Note

For customers still using Oracle, you may have access to configure delegate relationships in Employee Central
but the delegate relationships won't be viewable in Role-Based Permissions.

Goal Management
Permissions PUBLIC 141
8.1.3.3.2 Specifying the Hierarchy Depth

Understand how to use hiearchy depth when assigning permissions to your users.

When granting permissions using hierarchical relationships, you can specify how many levels down to go in the
hierarchy for the target population. For example, you can indicate that Managers can see performance ratings on
their direct reports (1 level deep), or allow it to go deeper into their team, that is 2 levels down or all levels.

When granting permissions to non-hierarchical relationships (HR, Matrix and Custom Managers), you can follow
this non-hierarchical relationship for only one level. Beyond the first level, you can cross over to the standard
manager hierarchy if desired to go deeper.

For example, using the Matrix Manager relationship, you can use hierarchical depth to accomplish the following:

● 1 Level Deep: Matrix Managers can view ratings information for their Matrix Reports.
● 2 Levels Deep: Matrix Managers can view ratings information for their Matrix Reports and the Direct Reports of
their Matrix Reports.
● All Levels Deep: Matrix Managers can view ratings information for their Matrix Reports (1 level deep) and the
Direct Reports, all levels deep of the manager hierarchy of their Matrix Reports.

Goal Management
142 PUBLIC Permissions
The following graphic illustrates the different hierarchical depths you can specify when you use the Matrix Manager
relationship:

8.1.4 What are Rules in RBP?

Rules in RBP are used to define access to permissions in your system.

Rules are defined by determining which permission roles you’ll assign to your groups or users. From the Permission
Role Detail screen in your system, each rule is represented by a row that contains your list of granted users or
groups and the associated target group. Depending on the complexity of the roles and access or target group
assignments, your roles could have various combinations of access and target group rules.

From your permission role detail screen, where you manage your permission roles, each row represents a rule and
each rule can have multiple access and target group associations, as detailed in the display.

Goal Management
Permissions PUBLIC 143
8.2 Role-Based Permissions for Goal Management

You can access the Goals module, and manage Goal Plans by enabling the role-based permissions for Goal
Management.

Verify that Role-based Permission, Enable Performance Management Access Permission, Enable Goal
Management Access Permission, and the related necessary permissions are enabled in Provisioning [Company]
Company Settings.

 Note

The intent behind the Enable Goal Management Access Permission option is to allow administrators the ability
to control at a more granular level, so they can decide which employees have access to Goals Management and
which do not. As of the Q3 2017 release, the ODATA APIs were updated to reflect the intent behind this switch. If
users are therefore not granted permissions to access the goal plan tab – they will not have access to any
aspects of Goal Management. We recommend that customers looking to control visibility or access to goals
should leverage the permissions within the XML

 Note

For users who migrated from non-RBP to RBP, if you cannot load the goal plan page but you have the RBP
permission, the solution is to first deselect and then reselect Everyone under Target Population through
Permission Role Detail Edit Granting . The root cause is Target Population query failure due to faulty
configuration or dirty data.

Permissions Descriptions

Objective Management Access Access the "Goals" or "Objective" module

New Group Objective Creation Create group Objectives (v2.0)

Goal Management
144 PUBLIC Permissions
Permissions Descriptions

Group Objective Assignment Assign group Objectives to other users

Target Population Assign goal permissions with respect to the group of employ­
ees selected in the target population

 Note
Do not

Access Execution Map Access Execution Map under Objective Execution

Access Meeting Agenda Access Meeting Agenda under Objective Execution

Access Status Report Access Status Report under Objective Execution

Manage Team Objective Create, edit and delete team Objective

Access to Continuous Performance Management Data Access Continuous Performance Management Achievements
and feedback received on the Achievements linked to the per­
formance goals, directly on the Objective Plan

Objective Plan Permissions Access the selected Objective Plans

Assign Team Objectives Assign team Objectives to other users

Share Team Objectives Share team Objectives with other users, making them the co-
owners of the team Objectives

Manage Initiatives Create, edit and delete Initiatives

Share Initiatives Share team Initiatives with other users, making them the co-
owners of the Initiatives

Admin Access for Goal ODATA API Export Retrieve all Objective details of other users using OData APIs,
overriding the permissions defined in the XML template.

 Note
This role-based permission has been developed exclu­
sively for the Data Protection Officer role, in accordance
with the Data Privacy and Protection regulations issued by
the European Union. The Admin Access for Goal ODATA
API Export permission must not be enabled for anyone
other than the Data Protection Officer. This permission
must not be used in any other capacity except to ensure
the Data Protection Officer has the ability to carry out the
duties prescribed under the regulation.

Import Goals Create, edit and delete goals, using an import file

Import/Export Goals library Create and edit Goal Libraries, using an import file

Manage Configuration of Goal Execution Access the Goal Execution configurations page

Goal Management Feature Settings Access the page that controls the feature settings in goal man­
agement

Goal Management
Permissions PUBLIC 145
8.3 Action Permissions

The following table describes the action permissions that you can configure for Goal Management.

Action Permissions
Action Description

Private Access (private-access) Define who has permission to see private goals, i.e. goals that
are not shared/made public.

 Note
Employees need the Private Access permission to receive
email notifications for private goals.

Create (create) Define who may insert a goal in a user's goal plan.

Delete (delete) Define who may delete a goal from a user's goal plan. Word of
caution – it is not recommended that you list no roles for this
permission. In addition, group goals will always allow the user
who created the goal to delete the goal for him or herself.

Delete Group Goals (delete-group-goal) Define who may delete a group goal from a user's goal plan.

Move Goal (move) Define who may move and indent goals within a user's goal
plan. Currently, TGM only allows users to move and indent
goals in their own plan.

Share Goal (share) Define who may mark goals as shared or unshared in a user's
goal plan. Word of Caution – currently, if you do not list any
roles for this permission, the [Make Selected Public] and
[Make Selected Private] buttons will still appear when looking
at goals in your own plan. When you press the button, a Win­
dows dialog box will appear displaying a message that you do
not have permission to perform this operation.

Cascade Pull (cascade-pull) Define who has permission to cascade goals from another us­
er's goal plan into their own plan. Currently, the only roles sup­
ported for Cascade Pull are * or no roles at all. If no roles are
listed, the [Cascade to My Plan] button will not appear when
you look at another user's goal plan.

Cascade Push (cascade-push) Define who has permission to cascade goals to another user. If
no roles are listed, the [Cascade to Others] button will not ap­
pear when you are looking at your own goal plan.

 Note
If you grant permission to the EX (Matrix Manager), this
button will appear for all users. Employees without matrix
reports will not be able to select any users, but they will
still see the Cascade button.

Goal Management
146 PUBLIC Permissions
Action Description

Align To (cascade-align) Define who has permission to align someone else's goal to a
goal of your own. This applies when two goals were created in­
dividually but you would like to link them for reporting pur­
poses. If no roles are listed the [Align To] button will not appear
when you mouse underneath a goal in someone else's goal
plan.

Unalign Parent (unalign-parent) Define who may unalign a goal that is aligned down in a user's
goal plan. Currently, TGM only allows users to unalign parent
goals in their own plan. Word of Caution – currently, if you do
not list any roles for this permission, the [Unalign] button will
still appear when looking at aligned up goals in your own plan.
When you press the button, a Windows dialog box will appear
displaying a message that you do not have permission to per­
form this operation.

Unalign Child (unalign-child) Define who may unalign a goal that is aligned down in a user's
goal plan. Currently, TGM only allows users to unalign child
goals in their own plan. Word of Caution – currently, if you do
not list any roles for this permission, the [Unalign] button will
still appear when looking at aligned down goals in your own
plan. When you press the button, a Windows dialog box will ap­
pear displaying a message that you do not have permission to
perform this operation.

Create Row (create-row) Define who has permission to create new rows in tables (Tasks,
Targets, Milestones, Achievement Lookup). Definition must in­
clude which table the permission applies to. If the permission
is not defined/included in the XML the create row permission
is granted to roles that have write field permission to the ta­
bles. To revoke create row permission from all roles define the
permission with no roles listed. Roles not included in the per­
mission definition will not have rights to create table rows.

Delete Row (delete-row) Define who has permission to delete rows in tables (Tasks, Tar­
gets, Milestones, Achievement Lookup). Definition must in­
clude which table the permission applies to. If the permission
is not defined/included in the XML the delete row permission
is granted to roles that have write field permission to the ta­
bles. To revoke delete row permission from all roles define the
permission with no roles listed. Roles not included in the per­
mission definition will not have rights to delete table rows.

Move Row (move-row) Define who has permission to move rows in tables (Tasks, Tar­
gets, Milestones, Achievement Lookup). Definition must in­
clude which table the permission applies to. If the permission
is not defined/included in the XML the move row permission is
granted to roles that have write field permission to the tables.
To revoke move row permission from all roles define the per­
mission with no roles listed. Roles not included in the permis­
sion definition will not have rights to move table rows.

 Note

The Create/Delete/Move Row permissions have a different behavior than the other Action Permissions when
the permission is not defined. When other action permissions are not defined, no role has access to that

Goal Management
Permissions PUBLIC 147
 permission. When create/delete/move row permission is not defined every role (with write permission to the
table) has access to those permissions. This was done to preserve backwards compatibility of the application.

 Note

A user with permission to add goals will automatically see a Save as New button on the goal edit page.

8.4 Roles in Goal Management

Roles are established based on what the system knows about relationships as determined by the employee data in
the instance.

They are most easily understood by breaking the letters into two parts.

1. E = Employee This is often the first part of the role code, and indicates that we are looking at the relationship of
the person to the employee. The actions we are describing will therefore impact the employee.
2. What Comes After the E. This could be the manager, direct report, HR representative, etc. The person
described in this role code is given or denied permission to impact the goals of the employee, based upon the
configurations.

Goal Management
148 PUBLIC Permissions
Current Roles in Goal Management
Role Name Description

* everyone

E employee/owner

EM employee's manager

EMM employee's second level manager

EM+ employee's manager and levels above in the reporting hierarchy

ED direct report

EDD second level direct report

ED+ any level of direct reports below in the reporting hierarchy

EMD employee's manager's direct reports, (coworkers/peers)

EX Employee’s Matrix Manager

EH employee's HR representative

F form reviewer (goal access restricted through a form only)

OP objective parent (for example, a project team lead's goal that is aligned up from a team mem­
ber's goal

OC objective child (for example, a team member's goal that is aligned down from a team lead's goal)

Cascader the person who is cascading a goal

Actions Mapped for Each Role

Goal Management
Permissions PUBLIC 149
  Note

The roles listed above are also used to set read and write permissions, when accessing goals in an individual's
Goal Plan. Currently, the only exception is that even if OC has write permission, OC cannot modify OP's goals.

Actions Mapped for Matrix Manager Roles

Matrix manager roles are also supported. The following roles have the same level of support:

● EX (matrix manager) and EM

● EY (matrixed direct report) and ED

Goal Management
150 PUBLIC Permissions
8.5 Field Permissions

Use this section of the goal plan to define which roles have read and write permissions for each field in a goal.

Field permissions are scanned in XML source order. The last applicable permission is the one used. For example, it
is not uncommon to restrict access to all fields and then selectively allow permissions.

 Note

Action Permissions should be considered when granting Field Permissions. Users who can create or cascade
goals should also be able to write to all fields or at minimum all required fields in a goal plan.

Supported field access permissions are described in the following table:

Field Permissions
Type Description

none No access to field by the specified roles is allowed.

read The user may read the fields

write The user may both read and write the fields.

description A place to store an internal comment.

role-name Each role that is granted read/write access should be enclosed

separately within its own <role-name> tag. This applies to
all permission sections of the goal plan.

field-refid Each field that the role has permission to access should be en­
closed separately within this tag.

table-col Each table column field that the role has permission to access
should be enclosed separately within this tag.

Example

XML Example: Field Permissions

<field-permission type="read">
<description>Everyone may read name and metric for shared goals</description>
<role-name>*</role-name>
<field refid="name"/>
<field refid="metric"/>
</field-permission>
<field-permission type="read"> <description>Direct reports may see all fields for
Manager's shared goals</description>
<role-name>ED</role-name>
<field refid="name"/> <field refid="desc"/><field refid="metric"/> <field
refid="state"/><field refid="due"/> <field refid="done"/><field refid="tasks"/>
</field-permission>
<field-permission type="write"> <description>The owner, manager and form reviewer
may write to all fields</description>
<role-name>E</role-name><role-name>EM</role-name> <role-name>F</role-name> <field
refid="name"/> <field refid="desc"/><field refid="metric"/> <field refid="state"/
><field refid="due"/> <field refid="done"/><field refid="tasks"/>
</field-permission>

Goal Management
Permissions PUBLIC 151
8.6 Cascader Role

You have the option to specify which goal details can become editable when an employee cascades a goal to others.

The cascading functionality has been available even before the RBP permissions were introduced, so it works in
both Legacy and RBP permission. This option gives you control over which read-only details remain read-only when
the goal gets cascaded. It also lets you create action permissions for tables (create-row, delete-row, and move-
row).

1. Cascader-role supports permissions on the following goal elements and actions for the user cascading their
goal to other employees:
1. Field permissions (standard, custom, table) <field-permission>
2. Table column permissions <table-col>
3. Action permissions for tables <permission for="">
1. Create (create-row)
2. Delete (delete-row)
3. Move (move-row)
2. When the “cascader-role” is disabled, users cascading their goal have write access to all fields and actions for
that goal regardless of goal plan permissions.
3. When the "cascader-role” is enabled, the “cascader” role controls what field can be seen and edited and what
table actions are permitted for the user who is cascading their goal.
4. Existing customers should experience no difference in the way their goal plan behaves and how the cascade
experience works. Current behavior is that the user cascading their goal has write access to all fields and
actions for that goal regardless of goal plan permissions. By default, the value of new attribute “enable-
cascader-role” is false, this is an 'opt-in' feature.
5. The customers who are not using RBP can also cascade goals by the permission configured in the goal plan
template.
In this example both employee manager and matrix manager will be able to cascade goal to their direct report
and matrix report. If the role is defined as *, then anyone can cascade goal to anyone in the company regardless
of the reporting line.

<permission for="cascade-push">
<description><![CDATA[Management hierarchy may push down through hierarchy.]]></
description>
<role-name><![CDATA[EM]]></role-name>
<role-name><![CDATA[EX]]></role-name>
</permission>

And also here is the detail matrix about cascade permission for legacy permission and RBP permission:

For example you might wish to retain restrictions on fields and not make items Read/Write when cascading:

To enable the Cascader Role functionality first set cascader-role to on in the goal template, then configure the goal
template field and action permissions. To turn on the functionality, insert the "switches" block of code in the goal
plan:

<obj-plan-start>11/01/2010</obj-plan-start>
<obj-plan-due>12/31/2011</obj-plan-due>

Goal Management
152 PUBLIC Permissions
 <obj-plan-numbering> <obj-plan-number-format><![CDATA[#.]]></obj-plan-number-
format> </obj-plan-numbering><switches> <switch for="cascader-role"
value="on"/></switches>
<add-wizard mode="smart goal">
<include-goal-align/>
</add-wizard>

You can configure the following cascader settings:

TGM Permission setting

mode Goal plan template setting RBP setting Current behavior

Legacy permission without Cascade push role setting N/A Cascade permission follows
RBP the goal plan template setting

RBP enabled instance – exam­ Cascade push role setting – The person being cascaded is Combine the goal plan tem­
ple 1 e.g. role defined as EM in the target population of the plate setting and RBP setting.
person doing the cascade ac­
Eg: Jennifer Lo is in the target
tion
population of Carla Grant
(RBP setting), and Carla Grant
have the cascade permission
(goal plan template setting),
then Carla Grant will be able to
cascade goal to Jennifer Lo.

RBP enabled instance – exam­ Cascade push role setting – The person being cascaded is Combine the goal plan tem­
ple 2 e.g. role defined as EM NOT in the target population plate setting and RBP setting.
of the person doing the cas­
Eg: Jennifer Lo is NOT in the
cade action
target population of Carla
Grant (RBP setting), and Carla
Grant have the cascade per­
mission (goal plan template
setting), then Carla Grant will
NOT be able to cascade goal
to Jennifer Lo.

1. Action permissions for tables <permission for="">

1. Create (create-row)
2. Delete (delete-row)
3. Move (move-row)
2. Field permissions (standard, custom, table) <field-permission>
3. Table column permissions <table-column>

Example

XML Example: Table Action Permissions for "cascader" Role

<permission for="create-row">

Goal Management
Permissions PUBLIC 153
 <description><![CDATA[The cascader can create a row in a field of type table then
he/she cascades a goal]]></description>
<role-name><![CDATA[cascader]]></role-name>
<field refid="tasks"/>
<field refid="targets"/>
<field refid="milestones"/>
<field refid="metric-lookup-table"/>
</permission>
<permission for="delete-row">
<description><![CDATA[The cascader can delete a row in a field of type table then
he/she cascades a goal]]></description>
<role-name><![CDATA[cascader]]></role-name>
<field refid="milestones"/>
</permission>
<permission for="move-row">
<description><![CDATA[The cascader can move a row in a field of type table then he/
she cascades a goal]]></description>
<role-name><![CDATA[cascader]]></role-name>
<field refid="milestones"/>
</permission>

Example

XML Example: Field, Table, Table Column Permissions for "cascader" Role

<!-- Field Permission Defined -->

<field-permission type="write">
<description><![CDATA[The goal owner, manager and cascader may write to all
fields]]></description>
<role-name><![CDATA[E]]></role-name>
<role-name><![CDATA[EM]]></role-name>
<role-name><![CDATA[cascader]]></role-name>
<field refid="name"/>
<field refid="desc"/>
<field refid="metric"/>
<field refid="start"/>
<field refid="due"/>
<field refid="state"/>
<field refid="tasks"/>
<field refid="milestones" />
<field refid="targets" />
<field refid="metric-lookup-table"/>
</field-permission>
<!-- Table Column Permission Defined for Cascader -->
<field-permission type="write">
<description><![CDATA[The cascader of goal may write to all below]]></description>
<role-name><![CDATA[cascader]]></role-name>
<table-col id="desc" field-refid="tasks"/>
<table-col id="start" field-refid="tasks"/>
<table-col id="due" field-refid="tasks"/>
<table-col id="done" field-refid="milestones"/>
<table-col id="achievement" field-refid="metric-lookup-table"/>
</field-permission>

Goal Management
154 PUBLIC Permissions
8.7 Table Field Permissions

Permission tags give you the ability to control who can create, modify, or delete rows of a table within a goal plan.

Supported tables are: Tasks, Targets, Milestones, and Achievement Lookup.

Here is a sample XML that can be added to your permissions section of a goal plan. In this example, everyone can
create, delete, or move rows of targets, tasks, milestones, or metric lookup tables.

Example

<permission for="create-row">
<description><![CDATA[Anyone can create row.]]></description>
<role-name><![CDATA[*]]></role-name>
<field refid="targets"/>
<field refid="tasks"/>
<field refid="milestones"/>
<field refid="metric-lookup-table"/>
</permission>< permission for="delete-row">
<description><![CDATA[Anyone can delete row.]]></description>
<role-name><![CDATA[*]]></role-name>
<field refid="targets"/>
<field refid="tasks"/>
<field refid="milestones"/>
<field refid="metric-lookup-table"/>
</permission>< permission for="move-row">
<description><![CDATA[Anyone can move row.]]></description>
<role-name><![CDATA[*]]></role-name>
<field refid="targets"/>
<field refid="tasks"/>
<field refid="milestones"/>
<field refid="metric-lookup-table"/>
</permission>

8.8 Table Column Permissions

Table column permissions allow you to define permissions for columns in the table.

Supported tables are: Tasks, Targets, Milestones, and Achievement Lookup. Listed below are some useful tips and
best practices to consider when using table column permissions.

 Note

You cannot define table permissions according to rows. Table row permissions are not supported.

1. If table column permissions are not defined, the columns will have the permission level of the table defined in
field permissions to ensure backwards compatibility.
2. Column level permissions can only be equal to or more restrictive than the field permission for the table. This
means that you cannot grant a role read permission to a table and then also try to grant that same role write

Goal Management
Permissions PUBLIC 155
 permission to columns in that table. For this scenario, grant write access to the table and then set table column
permissions to read for the columns you do not want the role to edit.
3. Required fields only apply if the role has write permission to the table column.
4. If the desired result is to hide a table from a role, instead of defining write permission for the table at the field
level and then setting all table columns to none, just define none at the table field level. Otherwise, the table
header will still appear.
5. Define table column permissions after table field permissions have been defined in the XML. This is not a
requirement but a best practice.
6. For the Achievement Lookup Table, it is not recommended to grant action permissions to roles that do not have
write permission to all columns. This can lead to undesirable behavior in the Achievement Lookup table and
calculated rating.
7. For the Achievement Lookup Table the table columns "achievement" and "achievement-text" should have the
same set of permissions.

 Note

At this time table column permissions are not supported in PM forms. This means field permissions defined for
table columns will not be respected when including a table in form-layout.

Example

XML Example: Table Column Permissions

The use case is to create a Milestone table with 4 columns: (Milestone, Start Date, Due Date, % Complete). The
manager (EM) should have full access to all columns but the Employee (E) should only have access to the %
Complete column. In this scenario the manager is responsible for setting the milestones and the employee only for
updating the percent completion for the milestones.

<field-permission type="write">
<description>Manager and Employee may write to the milestone table</description>
<role-name>E</role-name>
<role-name>EM</role-name>
<field refid="milestones"/>
</field-permission>
<field-permission type="read">
<description>Employee may only read the description, start, and due fields</
description>
<role-name>E</role-name>
<table-col id="desc" field-refid="milestones"/>
<table-col id="start" field-refid="milestones"/>
<table-col id="due" field-refid="milestones"/>
</field-permission>

8.9 Matrix Roles

1. All permissions are based on the premise, "WHO can take this action affecting the Employee's goals?" For
example:

Goal Management
156 PUBLIC Permissions
 ○ Create goals: WHO may create a goal on the Employee's goal plan?
○ Cascade-push: WHO may cascade his/her goal onto the Employee's plan?
○ Cascade-pull: WHO may acquire an employee's goal into another employee's plan?
2. Roles are case sensitive and as such must be listed in all uppercase.
3. Only those employees who have create goal permissions can copy goals from other goal plans.
4. If the weight field is in the PM form layout, make sure that the field is properly permissioned in TGM.
5. Permissions for tables (Create Row, Delete Row, Move Row) require the field to be defined in the permission.

 Note

Even if OC (objective child) is granted write permission, OC still cannot write to OP's (objective parent) goal.

Supported Matrix Manager Roles

Matrix manager roles are also supported. The following roles have the same level of support:

● EX (matrix manager) and EM

● EY (matrixed direct report) and ED

TGM Feature E EX EY

View private goals Y Y Y

Create Goals Y Y Y

Delete Goals Y Y Y

Move Goals Y Y Y

Share/Unshare Goals Y Y Y

Cascade Pull Y

Cascade Push N Y Y

Align To N Y Y

Unalign Parent Y

Unalign Child Y

Create Row Y Y Y

Delete Row Y Y Y

Move Row Y Y Y

Example

XML Example

<permission for="private-access">
<description> Employees and their managers may view unshared/private goals. </
description>

Goal Management
Permissions PUBLIC 157
 <role-name>E</role-name>
<role-name>EM</role-name></permission>
<permission for="cascade-pull">
<description Anyone may cascade a goal from anyone. </description>
<role-name>*</role-name>
</permission>

Example

XML Example: Table Action Permissions

<permission for="move-row">
<description>No one is allowed to move rows in the tasks table</description>
<field refid="tasks"/></permission>
<permission for="create-row">
<description>Only the manager can create rows in milestones table</description>
<role-name>EM</role-name>
<field refid="milestones"/></permission>

The Create/Delete/Move Row permissions have a different behavior than the other Action Permissions when the
permission is not defined. When other action permissions are not defined, no role has access to that permission.
When create/delete/move row permission is not defined every role (with write permission to the table) has access
to those permissions. This was done to preserve backwards compatibility of the application.

8.10 Goal Execution Permissions

You need to configure the permissions for the fields and actions in the new goal templates.

Field Permissions

Configuring permission control for the fields is done the same way that GM field permissions are done through the
goal plan template XML.

These permissions to read and write will need to be added to your XML coding:

<field refid="bizx-actual"/>
<field refid="bizx-target"/>
<field refid="bizx-pos"/>
<field refid="bizx-status-comments"/>
<field refid="bizx-effort-spent"/>

Action Permissions - bizx-request-update

This action permission controls who has the rights to ask the goal owner for a Status Update. "Ask Goal Owner for
Status Update" feature is located in the Execution Map.

 Note

This link will always appear in the Execution Map goal node drop-down due to system limitations. If the user
does not have sufficient permission rights the system will prevent them from using the feature but at this time

Goal Management
158 PUBLIC Permissions
 we are unable to remove the link. If this permission is left undefined the default is least permissive (no one will
have rights to use "Ask for Status Update").

<permission for="bizx-request-update">
<description><![CDATA[
Only managers and up can request a status update from the execution map
]]></description>
<role-name><![CDATA[EM+]]></role-name>
</permission>

8.11 Goal Plan States

Goal Plan States provide the ability to have more than one set of permissions. The difference between states can be
subtle or drastic depending on the customer's needs.

Goal Plan States control what field and action permissions are available. The topics describe the locking and
unlocking of goal plans for goal approval purposes.

 Note

You can have multiple Goal Plan Stages, but each plan state can only have an action to ONE next state. You
cannot have an option to go to two different states. It is a linear process, not branched.

 Note

Group Goals does not respect goal plan state configuration. If a user has group goal permission, the user can
see Add Goal button on Goal Plan page even if a goal plan is in locked status.

8.11.1 Locking and Unlocking of a User's Goal Plan

A common request from customers is the capability to lock and unlock goal plans for Goal Approval purposes.

The idea behind this feature is to allow components of the Goal to be locked once an authorized user locks the plan
(E, EM, and so on.). With this functionality, a manager could cascade a goal to an employee. The employee could
update only certain fields while the goal is locked, and update all fields or delete goals when it is in an unlocked
state.

Configuration

All of this is configured in the Goal Plan itself as described below.

 Note

Add the below configuration, after defining <field-definition> elements.

Goal Management
Permissions PUBLIC 159
1. Start with <obj-plan-states> element, this provides the ability to have different objective plan states.

<obj-plan-states>
…..
</obj-plan-states>

2. <obj-plan-states> element can have multiple <obj-plan-state> element.

○ obj-plan-state: element is used to define the single goal plan state.
○ id: attribute specifies the internal name of the plan state.
○ default: attribute specifics the default state of the objective plan and it should be true for only one plan
state.
○ state-label: element defines the name of the current state.
○ lang: attribute is used for showing the name as per the locale.

\\
<obj-plan-states>
<obj-plan-state id="A"default="true">
<state-label lang="en_GB">State-A</state-label>
<state-label lang="en_US">State-A</state-label>
…….
</ obj-plan-state>
</ obj-plan-states>
\\

3. Each <obj-plan-state> element can have its own set of action and field permissions.
We need to configure a new action permission called "Locked" that provides the ability to lock down certain
areas of the goal plan or a goal.

 Note

Group Goals and Team Goals cannot be locked down with goal plan state – it only applies to personal goals.

target-state: element specified inside "change-state" permission. It defines the objective plan state to
which the goal plan can be switched (i.e. Locked state and Unlocked state).

\\
<obj-plan-states>
<obj-plan-state id="A"default="true">
<state-label lang="en_GB">State-A</state-label>
<state-label lang="en_US">State-A</state-label>
<permission for="change-state">
<description><![CDATA[Manger may change the goal plan state to C.]]></
description>
<target-state><![CDATA[B]]></target-state>
<role-name><![CDATA[EM]]></role-name>
</permission>
<permission for="private-access">
<description><![CDATA[Employees and their managers up the reporting
chain may view unshared/private goals.]]></description>
<role-name><![CDATA[E]]></role-name
<role-name><![CDATA[EM]]></role-name>
</permission>
<permission for="delete-group-goal">
<description><![CDATA[Only the employee may delete goals in his/her own
plan.]]></description>
<role-name><![CDATA[EM]]></role-name>
</permission>
…
</permission>
</ obj-plan-state>
</ obj-plan-states>
\\

Goal Management
160 PUBLIC Permissions
  Note

You can repeat the steps to configure the multiple objective plan states under the </obj-plan-states>
element.

control-category-element

To allow for the category to have permissions, you can add the control-category-element attribute to the
XML.

For example, add:

<field-definition id="control-category-element" type="text" required="true"

detail="false" viewdefault="on" showlabel="false" field-show-coaching-
advisor="false" cascade-update="push-down">
<field-label lang="en_US">control-category-element</field-label>
<field-description>control-category-element</field-description>
</field-definition>

Then permission this field as you need, for example:

<field-permission>
<description><![CDATA[Everyone can read the category]]></description>
<role-name><![CDATA[*]]></role-name>
<field refid="control-category-element"/>
</field-permission>
<field-permission>
<description><![CDATA[HR can write to the category]]></description>
<role-name><![CDATA[EH]]></role-name>
<field refid="control-category-element"/>
</field-permission>

8.11.2 Change Locked / Unlocked State on Form Routing

We provide the ability that when a form is routed to next step, then the goal plan state of the user can be changed.

For this, we need to have the below configuration in the objective section of the PM/360 form template.

 Note

Add the below configuration after the <meta-grp-label>element in the Objective section of the form.

● obj-plan-state-change: defines the single goal plan state.

● to-step: specifies the route step ID.
● target-state: specifies the state to which the goal plan has to be switched.
● to-complete-state: Using this attribute we can decide to change the obj plan state while routing the form to
complete step.
● on-form-delete: Using this attribute we can decide to change the obj plan state while deleting the form.

Goal Management
Permissions PUBLIC 161
● id: attribute specifies the internal name of the objective plan state. It should be from one of the objective plan
state id defined in the objective template.

\\
<obj-plan-state-change to-step="Step2">
<target-state id="B"></target-state>
</obj-plan-state-change>
< obj-plan-state-change>

 Note

If we want to change the goal plan state for each route step, then add the above configuration multiple times.

\\
<obj-plan-state-change to-step="Step2">
<target-state id="B"></target-state>
</obj-plan-state-change>
<obj-plan-state-change to-step="Step3">
<target-state id="C"></target-state>
</obj-plan-state-change>
\\

When the form moves to a state where it is unlocked, the goal plan will be in an unlocked state.

We cannot specify the to-step attribute while configuring either to-complete-state or on-form-delete
attribute.

<obj-plan-state-change to-complete-state="true">
<target-state id="A"></target-state>
</obj-plan-state-change>

<obj-plan-state-change on-form-delete="true">
<target-state id="B"></target-state>
</obj-plan-state-change>

 Note

Creating a new form does not trigger a change of the goal plan state, and does not put the goal plan back into
initial state.

8.12 Settings for SuccessFactors in the Home Menu

You can disable the display of the Goal Management entries in the Home menu.

There are two ways to disable the display of the Performance and Goal Management entries in the Home navigation
menu for users or companies who do not own or access these modules. The first is accomplished via role based
permissions. The second is for instances without role based permissions, and can be done for all users by default,
or for specific users or groups of users.

Goal Management
162 PUBLIC Permissions
9 Goal Management Home Page Tile

9.1 Setting up the Goals Management Home Page Tile

without RBP

This section describes how you set up the Goals Management Home page tile without RBP (Role-based
Permission).

Prerequisites

Goal Management must be enabled in Provisioning: go to Provisioning Company Settings Goals

Framework , and select Enable Goal Management V12 — requires “Version 12 UI framework (Revolution)”.

 Remember

As a customer, you do not have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner. If you are no longer working with an implementation partner, contact SAP Cloud
Support.

Context

This is how you set up the Admin Tools when RBP is disabled.

 Note

Goal Management does not support the To Do tile. No due date notification of goals shows in the To Do tile.

Procedure

1. Login as a super admin.

2. Go to Manage Employees Set User Permissions Administrative Privileges , to grant user(cgrant) as

'Manage Homepage' permission

3. Login as cgrant, go to Admin Tool Permission to Manage Home Page

4. Select a user to grant manage home page permission - Click Grant Permission.

Goal Management
Goal Management Home Page Tile PUBLIC 163
9.2 Setting up the Goals Management Home Page Tile with
RBP

This section describes how you set up the Goals Management Home page tile with RBP.

Prerequisites

Goal Management must be enabled in Provisioning. Under Goals Framework, you need to mark Enable Goal
Management V12 [Not Ready for Sales/Production] — requires “Version 12 UI framework (Revolution)”.

 Remember

As a customer, you do not have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner. If you are no longer working with an implementation partner, contact SAP Cloud
Support.

Context

This is how you set up the Admin Tools when RBP is enabled.

Procedure

1. Log in as an admin who has permission to create a role.

2. Go to Admin Center.
3. Create a permission group includes at least a valid user.
4. Click the Manage Permission Roles link.
5. Create a new role.
6. Check the relevant user check box.

7. Log in as the user who has the Manage Homepage permission - Go to Admin Center Manage Permission
Roles Permission Settings Administrator Permissions Manage System Properties Manage Home
Page .
8. Select a user to grant manage home page permission - Click Grant Permission.

Goal Management
164 PUBLIC Goal Management Home Page Tile
9.3 Accessing the Goal Management Tile

This section describes how to enable the goals tile on the home page.

Prerequisites

You have Manage Home Page permission.

Procedure

1. Go to Admin Center Manage Home Page .

2. You can see Default, Tile Catalog, and Not Used tabs. Go to the Tile Catalog.
3. You can move the following Goal related tiles from the Tile Catalog tab to the Default tab:

Tile You can...

Objective Status get an overview of the Goals, broken down by goal status and category, on the
homepage.

Objective Status Tile get an overview of the Goals, broken down by Goal Status on the Homepage.

Overall Objective Rating Distribution see if the distribution of goal ratings for the selected people match the desired
distribution.

4. You can click Preview to check the display of your newly added tiles on Home Page.
5. Click Save in the end of the page.

Results

You have successfully added the Goals tile to the Home Page.

9.4 Goal Notifications on To Do Tile

As part of the smart suite framework, events that occur in SAP SuccessFactors Employee Central can trigger Goal
Management to-do items on the To Do tile. For example, when a new manager is created in the Employee Central,
the Goal Management module will automatically trigger a to-do item for the manager on the home page, asking the
manager to review the goal plan of the new team.

Events in Employee Central that might trigger notifications include department change, division change, and first
time manager. Here is a list of Goal Management related notifications.

Goal Management
Goal Management Home Page Tile PUBLIC 165
● User department change notification: Department changed
● User division change notification: Division changed
● First time manager notification: Review team's goal plans
● Individual contributor notification: Review team's goal plans
● User Job title change notification: Job title changed
● User LTD notification: Long term disability of manager
● User LTD notification: Long term disability of user
● Manager LOA notification: Leave of absence review
● User LOA notification: Leave of absence review
● Manager change notification: Review team's goal plans
● Manager new hire notification: New employee hired
● User STD notification: Long term disability of manager
● User STD notification: Short term disability of user

9.5 Configuring Goal Notifications

You can turn on or off Goal notifications in Admin Center.

Prerequisites

● SAP SuccessFactors Employee Central is turned on in Provisioning.

● The UI version is Home Page v3.

Procedure

1. Go to Admin Center Company Settings Notification Configuration .

2. Choose the Goals Management module from the dropdown of Filters.

You can see a list of Goal Management related notifications.

3. Select the notifications that you want to turn on.
4. Click Save.

Results

You have successfully turned on the selected Goal notifications.

Goal Management
166 PUBLIC Goal Management Home Page Tile
Next Steps

To turn off the Goal notifications, you can simply deselect from the list and save your changes. Please note that this
will only stop the display of future to do items on the To Do tile on Home Page. Existing to-do items are not affected.

Goal Management
Goal Management Home Page Tile PUBLIC 167
10 Group Goals

This section provides you with detailed information on the behavior, and configuration of the group goals feature.

Definitions

In an effort to clearly communicate the features of group goals here are some terms with definition that will be
used:

● Group Goal Owner - This is the user that has the original group goal. The employee where the group goal is
created. There is always only one group goal owner per goal.
● Group Goal Member - These are the users that have been assigned the group goal.
● Group Goal Creator - Person creating a group goal (i.e. setting the field values of the group goal).
● Group Goal Assigner - Person assigning the group goal to group goal members.

Key Benefits

The list of key benefits is based on functionality that is not available in the first version of group goals but is
supported in v2.0

● Ability to have sub-goal tables (for example tasks, targets, milestones, metric lookup) for a group goal.
● Support for calculated goal ratings using the metric lookup table.
● Ability to configure, per field, which are editable and which are read-only in a group goal (this also applies to
sub-goal tables).
● Ability to assign group goals to employees in separate target populations during mass import.
● Notifications about the employees who could not be assigned to the group goals, as they were not part of the
target population.
● Ability to import Group Goals 2.0 (via Beta Goal Import) for Add/Update/Delete actions (it is same as Personal
Goal, with the only difference that TYPE = OBJECTIVE_GROUPV2).

Potential Drawbacks

The list of potential drawbacks is based on functionality that is either available in the older version of group goals,
or just not available at all.

● Support for dynamic group goal membership - In v2.0 it's a static list of group goal members and not dynamic
based on criteria. This was the use case for the specific customer and as such what was built first.
● Cannot cascade group goals - Also not supported in v1.
● No group rating - this is supported in group goals v1. If needed in group goals v2, must use Metric Lookup Table

Goal Management
168 PUBLIC Group Goals
Comparing the Different Versions of Group Goals

Feature Group Goal v1 Group Goal v2

Changes to fields by the owner can be Yes Yes

pushed down to members

Dynamic group goal membership Yes No

Group goal membership can be modified No Yes

after initial setup

Supports tasks/targets/milestones No Yes

Supports calculated rating No Yes

Supports group rating Yes No

Fields can be made editable by group No Yes

goal members

10.1 Enabling Group Goals

The two different versions of group goals are mutually exclusive. You can only use either old, or new group goals but
not both. This applies at the company instance level.

Provisioning

Set the allow-group-goal attribute to "true" in the Goal Plan Template XML under Managing Plan Template in
Provisioning.

To enable group goals v2 turn it on under Provisioning Edit Company Settings Company Settings Goal
Frameworks Enable Group Goals 2.0 - requires "Total Goal Management"

 Remember

As a customer, you do not have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner. If you are no longer working with an implementation partner, contact SAP Cloud
Support.

Admin

Once the provisioning switch is enabled for Group Goals 2.0, you will see a new set of permissions in the
application.

In a non-RBP instance

Goal Management
Group Goals PUBLIC 169
Go to Admin Manage Security Administrative Privileges Manage Goals , and select the following two
permissions:

● New Group Goal Creation - Grant users this permission to allow them to create group goals 2.0 in their goal
plans
● Group Goal Assignment - This permission allows a user to assign a group goal to users. The group goal does not
have to be on the assigners goal plan (i.e. they can navigate to someone's goal plan that is the group goal owner
and they can assign that group goal).

In an RBP enabled instance

Grant the following permissions:

● New Add Group Goal Creation: Grant users this permission to allow them to create group goals 2.0 in their goal
plans
● New Add Group Goal Deletion: Grant users this permission to allow them to delete group goals 2.0 from their
goal plans
● Add Group Goal Assignment: This permission allows a user to assign a group goal to users. The group goal does
not have to be on the assigners goal plan (i.e. they can navigate to someone's goal plan that is the group goal
owner and they can assign that group goal).

In the XML - you must allow group goals. By default it is false, you need to make it true: allow-group-
goal="true".

10.2 Creating a Group Goal

If the group goal feature is enabled in your instance, and you have the New Add Group Goal Creation permission,
you can create a group goal in the goal plan page.

Prerequisites

● Group goal feature is enabled in the instance.

● You have the New Add Group Goal Creation permission.

Goal Management
170 PUBLIC Group Goals
Procedure

1. Go to Goals page.
2. Select a goal plan.
3. Click + Add Goal in the header.

You can see a dropdown of three ways to add goals.

4. Choose Create a New Goal.

You can see three options to create a goal: Personal Goal, Library Goal, and Group Goal.
5. Select Group Goal.

The Create a Group Goal pop-up window displays.

6. Fill in information for your group goal. For example, category, goal name, start date, and due date.
7. Click Save Changes.

Results

You have successfully added a group goal to your goal plan.

Next Steps

You can further assign the newly created group goal to your group members.

10.3 Assigning a Group Goal

If the group goal feature is enabled in your instance, and you have proper permission, you can assign group goals to
other users.

Prerequisites

● The group goal feature is enabled in your instance.

● You have the Add Group Goal Assignment permission.

Goal Management
Group Goals PUBLIC 171
Procedure

1. Go to Goals page.
2. Select a goal plan.
3. Choose one or more group goals.
4. Click Actions in the header.

You can see Assign in the dropdown. Please note if you do not have group goals in your goal plan, the Assign
button does not show.
5. Click Assign.

A Assign Goal popup window shows.

6. Select the recipients you want to assign the group goal and click Next.
7. You can doule check or edit the group goal before assigning it to the selected recipients.
8. Click Assign.

Results

You have successfully assigned the group goals to the selected recipients.

Goal Management
172 PUBLIC Group Goals
11 Team Goals

Team Goals is a feature that allows managers to create, update and assign goals for their team members, without
having to include the goals in their own Goal Plan. It effectively allows the manager to simply manage and monitor
the goals they set for their team, without having to achieve the goals directly.

 Note

'Goal' can also appear as 'Objective', depending on your 'Company Settings' in 'Provisioning'. So, in the
application, you may find 'Objective Plan' instead of 'Goal Plan', 'Launch Team Objective' instead of 'Launch
Team Goal', 'Team Objective' instead of 'Team Goal', and so on.

Overview

'Team Goals' has been designed using the existing Group Goals 2.0 framework, and supports all the features of
'Group Goals 2.0'.

 Note

To use Team Goals, ensure that you set the <allow-group-goal> attribute to "true" in your Goal Plan
template.

Major highlights of 'Team Goals' are:

● Includes all of the existing features of ‘Group Goal 2.0’ without forcing the manager to take accountability of
achieving the goals (i.e., the goals will not appear on the creator’s Goal Plan).
● Supports the ability to share assignment distribution over the team goal – effectively allowing a manager to
cascade the team goals to other managers, who may wish to assign the goals to their team

 Note

There are no separate XML tags for Team Goals, and it follows all the field level permissions configured for
Group Goals. So, when you use Team Goals and Group Goals at a time, their field level permissions will be the
same.

Prerequisites

● UI Version: GM v12
● Product Editions: Enterprise and SPRAC
● Enable the option for Generic Objects in Provisioning

Goal Management
Team Goals PUBLIC 173
  Remember

As a customer, you do not have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner. If you are no longer working with an implementation partner, contact SAP Cloud
Support.

Configuration

1. Go to Admin Center.
2. To enable Team Goals in the application, in the Tools Search field, search for Goal Management Feature Settings
and select the following options:
○ Enable Team Goals – Enables the Team Goal feature in the application, and provides permissions to grant
appropriate access.
○ Enable Delete Team Goals Share – Enables you to share Team Goals with other users, and grant them the
right to delete the Team Goals as well. This permission allows the primary owner and the co-owners of
Team Goals to delete the goals.

3. Click Save.
4. Next, to use Team Goals, you must enable the following permissions:
○ Manage Team Goals – grants permission to create, edit, and delete Team Goals
○ Assign Team Goals – grants permission to assign the Team Goals to members of your team

Goal Management
174 PUBLIC Team Goals
 ○ Share Team Goals – grants permission to share the Team Goals with other users, such that they too have
administrative control over the shared Team Goals.

 Note

The "Share Team Goals" permission is not bound by target population to facilitate co-ownership of
Team Goals between multiple managers and matrix managers.

5. Click Done and on the 'Permission Role Detail' page, click Save Changes.

You have successfully configured Team Goals in the application.

Answers to some Key Questions on Team Goals

● What is the difference between owner and co-owner of a Team Goal, and how do you recognize the
difference?
At first, the creator of the Team Goal is its only owner. The owner then shares the Team Goal with other users
and they become the co-owners. A co-owner has administrative privileges over the Team Goal, and can read,
update, and delete (if the shared owner has permissions to delete) the Team Goals. If the owner of the Team
Goal gives up access to the Team Goal, then one of the co-owners becomes the new owner. Currently, there is
no indicator to distinguish owner from co-owner. The UI only displays the user that created the Team Goal. To
view the owner and/or the co-owner(s) of a Team Goal, click the corresponding Actions link and select Share.
● Can I import/mass upload team goals?
Yes. While importing Team Goal, you need to indicate the Type=OBJECTIVE_TEAM. When the team goal is
imported, the 'created by' for the Team Goal (i.e., the Team Goal owner) will be the login user. The following
import 'ACTIONS' are supported: 'ADD', 'UPDATE', 'DELETE', 'ASSIGN', 'SHARE', 'UNSHARE', and 'UNASSIGN'.

● If an Admin creates the Team Goals using the Import Goals tool, can the Managers perform 'ADD', 'UPDATE',
'DELETE', 'ASSIGN', 'SHARE', 'UNSHARE', and 'UNASSIGN' on such Team Goals?
Yes. When the Admin imports the Team Goals, the Admin becomes the owner of the Team Goals. The Admin
can share the Team Goals with the Managers to make them the co-owners of the Team Goals. Once they
become the co-owners of the Team Goals, the Managers can perform the 'ADD', 'UPDATE', 'DELETE', 'ASSIGN',
'SHARE', 'UNSHARE', and 'UNASSIGN' actions on the Team Goals.
● Is Team Goal stored as a type of goal that we can report on, like Group vs Personal? What reporting
schema will be available for Team Goal?
At present, there is no special reporting schema for Team Goal, nor is there a separate type of ad-hoc report for
Team Goals. The Team Goal is maintained like any other goal.
● Will Team Goal replace Group Goals 1.0 or 2.0?
No. There are no plans to replace Group Goals 1.0 or 2.0 with Team Goal. The feature can be used either
independent of Group Goals or in conjunction with Group Goals.

Goal Management
Team Goals PUBLIC 175
● What happens when the owner of a Team Goal becomes inactive? Do the team members still see the
Goal? Can the administrator add a co-owner, after the owner becomes inactive?
This is more likely a unique case, where the owner has not shared the Team Goal with anyone to co-own, and
has become inactive. In such a case, the Team Goal will operate just like Group Goals 2.0 – where the employee
(team) will be able to see the assigned goal. Also, the Team Goal is accessible only to its owner and co-owners.
So, if the administrator does not own or co-own the Team Goal, the administrator cannot add a co-owner, and
the Team Goal will not be editable, accessible, or assignable any longer.
● When an Admin - the owner of a Team Goal, makes only one Manager the co-owner of that Team Goal, and
gives up ownership, the Manager automatically becomes the new owner of that Team Goal. If that
Manager becomes inactive, will the Admin be able to assume ownership of the Team Goal again?
No. Once people give up the ownership of the Team Goal, they have to request the new owner or the co-owners
of the Team Goal to grant co-ownership of the Team Goal to them.
● Is Team Goal applicable to the Development Goals? Or can you associate Learning activities to Team
Goals?
No. Currently, Team Goal is supported only in Goal Management. Neither the Team Goal is applicable to
Development Goals, nor can you associate Learning activities to it.
● Will Team Goal have dynamic functionality like assigning to all direct reports, without manually adding
and removing users?
No. On the Assign Team Goal page, your hierarchy (direct reports) appears, and you may select each assignee
individually or all your direct reports at one time. However, currently there is no support for dynamic Team Goal
membership.
● If I'm neither the owner or a co-owner of a Team Goal, can I perform the Assign, Share and Edit actions on
the Team Goal?
To work with Team Goals you can either use the application UI, wherein you click the Launch Team Goal option
on the Goal Plan and land on the Team Goal page, or use the Import Goals tool. So, if you are neither the owner
nor the co-owner of a Team Goal, the following table explains what you can possibly do or not do with the Team
Goal:

Using the application UI: Team Goal

Can you...? page Using the Import Goals tool

Assign the Team Goal No, because if you are neither the Yes. Even if you aren't the owner or co-
owner nor the co-owner of a Team Goal, owner of a Team Goal, you can assign
you cannot view it on the Team Goal the Team Goal, if you have the Assign
page. Team Goals permission enabled for
your role, and you have people in your
target population that you can assign
the Team Goal to.

Share the Team Goal No, because if you are neither the No, because only owners and co-own­
owner nor the co-owner of a Team Goal, ers enjoy the sharing privileges for a
you cannot view it on the Team Goal Team Goal.
page.

Goal Management
176 PUBLIC Team Goals
 Using the application UI: Team Goal
Can you...? page Using the Import Goals tool

Edit the Team Goal No, because if you are neither the Yes. Even if you aren't the owner or co-
owner nor the co-owner of a Team Goal, owner of a Team Goal, you can edit the
you cannot view it on the Team Goal Team Goal, if you have the Manage
page. Team Goals permission enabled for
your role.

11.1 Creating a Team Goal

You can create a team goal for your team members, without assigning the goal to yourself.

Prerequisites

● You have access to the goal plan.

● You have the Manage Team Goal permission.

Procedure

1. Go to Goals Goal Plan .

2. Select a goal plan that you want to add the team goal to from the goal plan dropdown.
3. Click the Action icon in the header.

A dropdown of actions displays.

4. Select Launch Team Goal.
The Team Goal page shows.
5. Click Create Team Goal.

A Create a Team Goal popup appears.

6. Select the goal Category, enter the Goal description, provide the Metric to measure the goal, and fill out the
other necessary details.
7. Click Save Changes.

Results

You have successfully created a team goal.

Goal Management
Team Goals PUBLIC 177
Next Steps

You can further edit, share, assign, or delete the team goal.

11.2 Sharing or Unsharing a Team Goal

You can share a team goal with other users or administrators. However, the users with whom you share the team
goal must have the Goal Plan Permission and the Manage Team Goal permission to edit the shared goals effectively.

Prerequisites

● You are the owner or co-owner of the team goal.

● You have the Share Team Goals permission.

Procedure

1. Go to Goals Goal Plan .

2. Select a goal plan from the goal plan dropdown.
3. Click the Action icon in the header.

A dropdown of actions displays.

4. Select Launch Team Goal.
The Team Goal page shows. You can see you team goal list.
5. Choose the team goal that you want to share with others and click the Actions icon.

You can see a dropdown of actions.

6. Select Share.

A Share Team Goal popup window appears.

7. Enter the Employee with whom you want to share the goals, and click the name of the employee from the
dropdown.

The employee is automatically added to the share list.

 Note

You can give up the ownership of a Team Goal you own or co-own, by unsharing it with yourself.

 Note

To share the right of deleting the Team Goal, ensure that the Enable Delete Team Goals Share option has
been enabled on the Goal Management Feature Settings page.

Goal Management
178 PUBLIC Team Goals
8. Click Done.

Results

The team goal has been successfully shared with the selected users. They are now the co-owners of the team goal.
The co-owners of the Team Goal can assign, share, edit or even delete the team goal.

11.3 Assigning or Unassigning a Team Goal

If you are the owner or co-owner of a team goal, you can assign the team goal to others who have the Goal Plan
Permission.

Prerequisites

● You are the owner or co-owner of the team goal.

● You have the Assign Team Goals permission.

Procedure

1. Go to Goals Goal Plan .

2. Select a goal plan from the goal plan dropdown.
3. Click the Action icon in the header.

A dropdown of actions displays.

4. Select Launch Team Goal.
The Team Goal page shows. You can see you team goal list.
5. Choose the team goal that you want to share with others and click the Actions icon.

You can see a dropdown of actions.

6. Select Assign.

An Assign Goal popup window appears.

7. You can choose your direct reports from the Recipient Hierarchy section, or search for other employees from
the Other Recipients section.
8. Click Next.
9. You can further edit the team goal before clicking Assign.

Goal Management
Team Goals PUBLIC 179
Results

You have successfully assigned the team goal to the recipients.

Next Steps

To unassign the team goal, click the corresponding Actions link, and select Unassign. Clear the checkboxes for the
users who do not need the team goal assignment any longer, and click Done. The team goal disappears from the
goal plan of the unassigned users.

11.4 Editing or Deleting a Team Goal

On the Team Goal page, you can create a new Team Goal, search for the existing ones, and edit, assign, unassign,
share, or delete them.

Launch a Team Goal

As a manager, when you go to the Goal Plan page, you will find the Launch Team Goal link that takes you to the team
goal page, also called the Team Goal management view page.

Edit a Team Goal

To edit the Team Goal, click the corresponding Actions link, and select Edit. Update the Team Goals as required, and
click Save Changes. The edits will reflect on the assignees' Team Goal.

Delete Team Goal

You can delete the Team Goal you have created, and if the option, Enable Delete Team Goals Share has been
enabled in Admin Center Goal Management Feature Settings , then you can also delete the Team Goal shared
with you.

To delete the Team Goal, click the corresponding Actions link, select Delete, and on the confirmation message that
appears, click OK. The Team Goal is not only deleted, but also removed from all Goal Plans, including the ones for
which the Team Goal was assigned by others.

Goal Management
180 PUBLIC Team Goals
12 Editable Fields for Group Goals and Team
Goals

One of the key benefits of group goals 2.0 is the ability to configure fields as editable to group goal members.

Two of the use cases for this are as follows:

● A department can share the same goal with shared results but each person can have a different set of tasks or
milestones for that goal. For example, Customer Success has a goal for 95% customer satisfaction. While the
result will be shared by everyone in the department, what each person does to contribute to that goal will be
different and now can be tracked individually.
● A business unit goal is again shared by everyone but the impact of this goal on a person's goal plan is different
based on that person's level in the business unit. For example, a shared goal has a bigger impact on directors
compared to associates so the weight field should be editable.

The configuration to make fields editable is an attribute of the field-definition.

Goal Plan XML Change

cascade-update (push-down | regular) "push-down"

The default behavior is "push-down" meaning that fields will behave the same as group goals v1. Group goals will be
editable to the group goal owner and read-only to group goal members. To make a field editable by group goal
members set the attribute value to "regular".

 Remember

To support auto-population of the calculated fields in group goals, the cascade-update attribute needs to be
set to push-down and not regular.

Example

Weight should be editable by everyone who has permission in a group goal.

<field-definition id="weight" type="percent" required="true" detail="true"

viewdefault="on" showlabel="true" field-show-coaching-advisor="false" cascade-
update="regular">
<field-label>Weight</field-label>
<field-description>Weight</field-description>
<default-value>0.0</default-value>
<field-format>#.#</field-format>
</field-definition>

 Note

If you define the "weight" field with type="percent" and want users to be able to enter a value greater than
100.0 in the "weight" field, remember that the value for the "percentage-value-over-100" switch should
be set to "on" in the Goal Plan XML. Conversely, if you want to prohibit users from entering a value greater than

Goal Management
Editable Fields for Group Goals and Team Goals PUBLIC 181
 100 in the "weight" field, do not enable the "percentage-value-over-100" switch in the Goal Plan
template.

Field Permissions

● When a field is set to push-down, this field will be editable by group goal or team goal owners and read only to
group goal members or team goal assignees regardless of field permissions.
● When a field is set to regular it will be editable by the assigner when they are assigning the goal and also
editable to group goal members or team goal assignees.

Goal Management
182 PUBLIC Editable Fields for Group Goals and Team Goals
13 Initiatives

You can create departmental, corporate, and division level initiatives, and allow employees to associate their
personal goals with the initiatives.

A series of Initiatives can be bundled together under a common theme called Initiative Group.

 Note

The Initiative Groups are sorted in such a way that the initiatives, which are created, edited, or assigned most
recently, appear on top of the list.

On the Manage Initiatives page, you can:

● Simplify the experience for top-down goal alignment.

● Align your goals across multiple initiative groups. For example, product management initiatives, and marketing
initiatives.
● Generate reports on goal alignment for corporate, departmental, or divisional initiatives.

Limitations

● You can't associate goals from goal libraries with initiatives upon creation. However, you can edit the goals to
associate them with initiatives later.
● You can’t assign initiatives to more than 15,000 users in a single transaction.
● Initiatives can't be imported, however, initiative groups can be imported via Import and Export Data.
● Initiatives can't be localized using 3-Tier Language Architecture.
● Initiatives aren’t integrated with Performance Management.

Answers to Some Key Questions on Initiatives

● What happens when you’re no longer assigned to the Initiative Group, but your goal was aligned to the
initiative? Does it break the goal? Does the goal stay and the Initiative is disassociated? Is this shown in
the audit trail?
Suppose that an Initiative Group is assigned to you, and you link your goal to one or more Initiatives within the
group. Later, if you’re unassigned from the Initiative Group, the Initiatives within that group no longer appears
on your Goal. The dissociation between the goal of an employee and the Initiatives isn’t indicated in the audit
trail.
● Can you link multiple Initiatives to a single Goal?
Yes. You may link as many Initiatives to a single goal, provided they’re relevant to that goal. For example, an
Initiative Group named "Customer Focus" may contain two Initiatives that center on customers – for example,
"increase customer revenue" and "meet face to face with customers". At the Goal level, you may link your Goal
to one or both Initiatives.

Goal Management
Initiatives PUBLIC 183
13.1 Enabling Initiatives

You can turn on the Initiatives function in Admin Center.

Prerequisites

● The UI version is GM v12.

● The Enable Initiatives, Enable Generic Objects, Enable the Attachment Manager, and Role-Based Permissions
options are enabled in Provisioning.
● You have the Manage Initiatives and Share Initiatives permissions.

Procedure

1. Go to Admin Center Goal Management Goal Management Feature Settings .

A list of Goal Management related settings shows.

2. Select Enable Initiatives.
3. Click Save.

Results

You have successfully enabled the Initiatives in the application.

Next Steps

You can now go to the Manage Initiatives page to use your initiatives and initiative groups.

Goal Management
184 PUBLIC Initiatives
13.2 Creating an Initiative Group

You can create an Initiative Group with a bunch of relevant Initiatives, which you can assign and share with other
employees.

Prerequisites

You have the Manage Initiatives permission.

Procedure

1. Go to Admin Center Goal Management Manage Initiatives .

The Manage Initiatives page shows.

2. Click Create Initiative Group.

The Create Initiative Group popup window appears.

3. Enter information about your initiative group.

Item Description

Initiative Group Name Give a name to your initiative group.

Initiative Group Description Describe the main purpose of the initiative group.

Active You can choose Yes to activate the initiative.

4. Click + Add Initiative to add initiatives to the initiative group.

You can add multiple initiatives to an initiative group. But please note that you are recommended to load 100 or
less initiatives in the Manage Initiatives page to ensure page loading performance. Please expect slower page
loading, or in some extreme cases, page hanging, when there are too many initiatives showing in the page.
5. Enter Initiative Name and Initiative Description.
6. Click Save.

Results

You have successfully created an initiative group with a bunch of relevant initiatives.

Next Steps

You can further edit, assign, or share the initiative group.

Goal Management
Initiatives PUBLIC 185
13.3 Assigning an Initiative Group

You can assign an Initiative Group to employees and align the Initiative Group to specific Goal Plans.

Prerequisites

You have the Manage Initiatives permission.

Procedure

1. Go to Admin Center Goal Management Manage Initiatives .

The Manage Initiatives page shows. You can see a list of initiative groups.
2. Click the Actions icon corresponding to the relevant Initiative Group, and select Assign.

The Initiative group Assignment popup window appears.

3. Under the Assign To User tab, select the users whom you want to assign the Initiative Group to.

For example, you can choose Department in the Pick a Catergory field. Click [click to edit], the Research Results
popup window shows. Enter a keyword and click the search icon. Select your target assignee group and click
Done. You can check the number of assignees you have chosen by clicking Update on the Active Group
Membership tile.
4. Under the Align With Goal Plan tab, select the goal plans that you want to align the Group Initiative with.
5. Click Done.

Results

The Initiative Group has been assigned to the selected users, and will appear on the selected Goal Plans when the
assignees add or edit a Personal Goal.

Next Steps

You can check the membership of the Initiative Group by clicking the number under Group Members.

Goal Management
186 PUBLIC Initiatives
13.4 Sharing an Initiative Group

If you are the owner or co-owner of an Initiative Group, you can share the Initiative Group and its administrative
privileges with other users or administrators.

Prerequisites

● You have the Manage Initiatives and the Share Initiatives permissions.
● The users with whom you share the Initiative Group must have the Manage Initiatives permission.

 Note

To share the right of deleting the Initiative Group, ensure that the Provisioning option, Enable Delete Team
Goals Share has been enabled.

Procedure

1. Go to Admin Center Goal Management Manage Initiatives .

The Manage Initiatives page shows. You can see a list of initiative groups.
2. Click the Actions icon corresponding to the relevant Initiative Group, and select Share.

The Share Initiative popup window appears.

3. Enter the Employee with whom you want to share the Initiatives.
4. Click the name from the dropdown. The user is automatically added to the share list.
5. Click Done.

Results

The Initiative Group has been shared with the selected users. The selected users become the co-owners of the
Initiative Group. The co-owners can assign, share, edit or even delete the Initiative Group.

Next Steps

To remove the ownership of the Initiative Group from users, you can simply click the Actions icon, select Share, and
unselect anyone whom you want to remove the ownership from, including yourself. Please note that if you are the
only owner of the Initiative Group, you cannot remove yourself. This is to ensure that the Initiative Group has at
least one owner.

Goal Management
Initiatives PUBLIC 187
13.5 Manage Initiatives

On the Manage Initiatives page, you can create Initiative Group and Initiatives, search for the existing Initiative
Groups, edit Initiatives, and assign, unassign, share, revoke or delete the Initiative Groups. The Initiative groups are
merely containers of one or more Initiatives.

 Note

You are recommended to load 100 or less initiatives in the Manage Initiatives page to ensure page loading
performance. Please expect slower page loading, or in some extreme cases, page hanging, when there are too
many initiatives showing in the page.

Here is a list of how to edit, revoke, and delete an Initiative Group. You can go to specific topics in this Chapter
for detailed procedures about creating, assigning, sharing, and aligning personal goals to Initiative Groups.

Edit an Initiative Group

To edit Initiatives, click the Actions link corresponding to the relevant 'Initiative Group', and select Edit. Update the
'Initiatives' and other details within the Initiative Group as required, and click Save. The edits reflect on the aligned
Goal Plan of the assigned users.

Revoke an Initiative Group

You can give up your ownership of the Initiative Group by revoking your access rights. Click the corresponding
Actions link, select Revoke, and on the confirmation message that appears, click Yes. The Initiative Group no longer
appears on your Manage Initiatives page. Please note that if you are the only owner of the Initiative Group, you
cannot give up your ownership. This is to ensure that the Initiative Group has at least one owner.

Delete an Initiative Group

To delete an Initiative Group you own, click the corresponding Actions link, select Delete, and on the confirmation
message that appears, click OK. The Initiative Group is not only deleted, but also removed from all Goal Plans,
including the ones with which the Initiative Group was aligned by others.

13.6 Reporting on Inititatives

You can run a variety of Ad Hoc reports on Initiatives.

The following are available report definition types available for Initiatives:

Goal Management
188 PUBLIC Initiatives
● Initiative Group: Run reports on the types of Initiative Groups and Initiatives within those groups.
● Initiative Group Share: Run reports for users who co-own for the Initiative Groups.
● Initiative Group Assign: Run reports for users who have been assigned with Initiative Groups and their
corresponding Initiatives.
● Initiative Group Align: Run reports for users who have aligned their personal Objectives (Goals) to the
assigned Initiatives. This is particularly useful to measure overall alignment of personal goals to corporate,
divisional and/or departmental initiatives.

 Note

You can construct YouCalc tiles and embed in a dashboard to gauge initiative alignment.

Example of an Ad Hoc Report on Alignment of Initiatives

Once Initiatives are aligned, you can gauge the degree of workforce alignment to those initiatives through ad-hoc
reporting. This example shows an ad-hoc report of single domain type, with Objectives that have been physically
aligned to the Initiatives.

Goal Management
Initiatives PUBLIC 189
13.7 Aligning Personal Goals to Assigned Initiatives

Once an Initiative Group has been assigned to you, and aligned to your Goal Plan, it appears on your Goal Plan
whenever you add or edit a Personal Goal. You can align your Personal Goals to specific Initiatives of the Initiative
Groups.

Prerequisites

● You have the Goal Management Access permission.

● At least one Initiative Group has been assigned to you, and aligned to one of your Goal Plans.

Procedure

1. Go to Goals Goal Plan .

2. Select the goal plan which the Initiative Group has been aligned to.
3. Align your personal goals to the assigned Initiatives.

Scenario Procedure

Edit a Personal Goal. Select Edit Goals from the dropdown of the Action menu.
The Edit Goal popup window shows. Select the initiatives
that you want to align the goal with.

Add a Personal Goal. Click + Add Goal from the header. Select Create a New Goal
from the dropdown. Select + Personal Goal. Select the initia­
tives that you want to align the goal with.

4. Click Save Changes.

Results

You have successfully aligned your personal goal to the assigned Initiative Group.

Goal Management
190 PUBLIC Initiatives
14 Goal Library

A goal library is a list of goals that the user can select and add to their goal plan or the goal plans of their direct
reports.

Goal Library supports the following features:

● A UI in Admin Center to allow an administrator to manage the goal library entries

● Support of the import and export of goal libraries for managing them
● Support the ability to select multiple goals from the library at once to be included into a goal plan

 Note

There can be several goal libraries within one instance. But a goal plan can only be linked to one unique goal
library at one time.

14.1 Mapping of Goal Library Content to Goal Plans

The obj-library & field-mapping element defines a goal library which can be used to create individuals goals.

The mapping, ID is optional, the name needs to point to the appropriate library name. The field-mapping elements
are optional. It defines how fields in the goal library are mapped to the TGM fields during goal creation. The SAP
SuccessFactorsLibrary is automatically loaded and included with TGM. You must have the English goal library when
using a goal library in other languages.

Requirements

This is used for both objective library and learning catalog.

● For Objective library mapping, id is optional, the name needs to point to the appropriate library name.
● For learning catalog, use id to point to the appropriate learning catalog, Goals may be imported into a goal plan
using a comma separated file.
● _Goal library field size limits: Goal library name, category, and goal name have a field size limit of 1024. Goal
category and goal name are represented in the "ENTRY_NAME" column of the goal library csv file format._DTD
Definition

<\!ELEMENT obj-library (field-mapping+)>

<\!ATTLIST obj-library
name CDATA #REQUIRED
id CDATA #IMPLIED>

Attributes

● src-library-field-id - ID for the column in the library that data will be copied from

Goal Management
Goal Library PUBLIC 191
● dst-field-id - Corresponds to a value in one of the existing field-definition ID from the template that data
will be copied into

Example

Standard SAP SuccessFactors Library

…
</text-replacement>
<obj-library name="SuccessFactors Library">
<field-mapping src-library-field-id="Name" dst-field-id="name"/>
<field-mapping src-library-field-id="Data1" dst-field-id="metric"/>
</obj-library>
<category id="Customer">
…

Example

Custom Goal Library

…
</text-replacement>
<obj-library name="My Goal Library" id="100">
<field-mapping src-library-field-id="Name" dst-field-id="name"/>
<field-mapping src-library-field-id="Data1" dst-field-id="metric"/>
</obj-library>
<category id="Customer">
…

14.2 Goal Library File

You can enhance the goal library to support defaults for all goal and subgoal fields.

You can include any fields that the customer requires, multiple language, and multiple libraries in the same import
file.

Here are the standard goal plan template fields that are supported:

● name
● desc
● start
● due
● done
● metric
● target-baseline
● category

Goal Management
192 PUBLIC Goal Library
● weight
● state
● comments
● goto-url
● bizx-actual
● bizx-target
● bizx-pos
● bizx-strategic

The table column fields include:

● Tasks (desc, start, due, date, done, completed, target, actual): Single and multiple tasks
● Milestones (desc, start, due, date, done, completed, target, actual): Single and multiple milestones
● Targets (date, target, actual): Single and multiple targets
● Metric Lookup (achievement, achievement-text, rating, description)

 Note

The fields that the goal library supports are not limited to these standard fields.

14.3 Importing a Goal Library

You can add one or more goal libraries to your instance in Admin Center.

Prerequisites

You have the Import/Export Goals library permission.

Procedure

1. Go to Admin Center Goal Management Import/Export Goals Library .

Goal libraries are stored in csv files. If it is your first time to import a goal library, download a template csv file to
add goals to.
2. Choose a template from the Available List of Templates dropdown.

The Default Header option generates a csv file with only the headers.
3. Click Download to download the goal library template.
4. Added necessary goal library information to the csv file.

Goal Management
Goal Library PUBLIC 193
  Note

When you delete a goal library, make sure you apply DELETE actions to all leaf nodes in addition to the root
node.

5. In the Import Objective Library by uploading a CSV file. section, click Import.

The Import Objective Library by uploading a CSV file. popup window appears.
6. Click Choose File, and select the prepared csv file.

The size of the csv file must not exceed 5 MB.

7. Click Upload.

Results

You have successfully imported a goal library to the system.

Goal Management
194 PUBLIC Goal Library
15 Creating Goals and Ratings with
Achievement Lookup

Customers can generate a calculated goal rating for a goal on a goal plan.

This calculated rating will then be pulled into PM forms for use as the rating for that goal. The purpose of this
feature is to quantify what a rating value actually means to the user in real world terms.

15.1 Sample Use Case

Here is a sample use case for goals and rating with achievement lookup.

The employee is a sales representative. One of their goals is to generate 1 million dollars of revenue this year. If they
bring in 1 million dollars, they meet their goal, and they get 3 out of 5 as a rating. If they bring in 1.25 million dollars,
they get a 4. 1.5 million is a 5. 750,000 is a 2. 500,000 a 1.

The employee now knows the targets that they must achieve and where the different cutoff points are. Let's say at
the end of the year the sales representative has generated 1.13 million dollars in revenue. Using the metric lookup
table the system calculates a rating for this goal. The rating will then be pulled into a PM form to be used as the
rating for this goal.

There are two supported calculation types: step and interpolate. In this example, the system either calculates the
goal rating to be 3 (step), or 3.52 (interpolate).

15.2 Metric Lookup Basics

You can use metric lookup table to calculate ratings of a goal. A basic metric lookup table consists four items.

A basic metric lookup table consists of the following items:

Goal Management
Creating Goals and Ratings with Achievement Lookup PUBLIC 195
1. Target levels to achieve
2. Ratings associated to those target levels
3. A place to enter the actual achieved value
4. The calculated rating that results from mapping the actual achievement in the metric lookup table.

Three types of fields (field-definition id) are required in the XML template to enable rating calculation:
rating, metric-lookup-table, and actual-achievement or actual-achievement-text.

Field Type Description

rating number Stores the rating calculated by compar­

ing the actual-achievement with the tar­
get achievement values.

metric-lookup-table table Stores the target achievement values.

actual-achievement number Stores the actual achievement value.

actual-achievement-text text

Correspondingly, three columns (table-column id) can be configured to display on the UI. A minimum of two
columns are required. One column must be the rating column. The second column is either the achievement or the
achievement-text column.

Column Type Optional or Mandatory

achievement number Optional

achievement-text text Optional

rating number Mandatory

description text Optional

The configuration for the metric lookup table applies at the goal plan level instead of the goal level. It does not mean
that every goal in a goal plan must have a calculated rating. But it does mean that you cannot have one goal
calculate a rating using step, while another goal calculates a rating using interpolation. Step and interpolation are
two calculation types.

15.3 Calculation Types

You can configure your goal plan with one of two calculation types, step or interpolation. Make sure you understand
the basics of the metric look up table before you read topics of calculation types.

The calculation configuration is defined in the field-definition for metric lookup table. Accepted values are step or
interpolate.

Goal Management
196 PUBLIC Creating Goals and Ratings with Achievement Lookup
15.3.1 Step

You can calculate actual ratings with the calculation method of step. The step calculation type treats target
achievement values as thresholds.

For example, the below Target Rating Table is your lookup table.

Target Rating Table

Target Rating

20 1

30 2

40 3

50 4

70 5

Actual Achievement Calculations

Actual Achievement Calculated Actual Rating

20 1

25 1

55 4

80 5

You can calculate the actual ratings using step based on the Target Rating Table and Actual Achievement values. In
the example, the actual achievement of an employee is 25, which is in between of the 20 threshold and the 30
threshold, the actual rating is 1.

Here is an XML example for you to configure the step calculation type. The exact configuration depends on your
system settings.

 Sample Code

<field-definition id="metric-lookup-table" type="table" required="false"

detail="false" viewdefault="on" showlabel="false"default-calc-type="step" field-
show-coaching-advisor="false">
<field-label>Achievement Lookup</field-label>
<table-row-label>Achievement Lookup Table</table-row-label>
<table-column id="achievement" type="number" required="true">
<column-label>Target Level</column-label>
<column-description>Target Level</column-description>
</table-column>
<table-column id="rating" type="number" required="true">
<column-label>Score</column-label>
<column-description>Score</column-description>
</table-column>
<table-column id="description" type="text" required="true">
<column-label>Description</column-label>
<column-description>Description</column-description>
</table-column>
<rating-scale>
<rating-scale-id>Metric Lookup Scale</rating-scale-id>
</rating-scale>
</field-definition>

Goal Management
Creating Goals and Ratings with Achievement Lookup PUBLIC 197
15.3.2 Interpolation

You can calculate proportionally accurate actual ratings with the calculation type of interpolation.

For example, the below Target Rating Table is your lookup table. In your instance, the actual achievement of an
employee is 25. This actual achievement is not an exact number in the metric lookup table. It is between 20 and 30.
If you want to calculate a proportionally accurate actual rating for this employee, you can use the interpolation
method with the following calculation formula:

(actual_achievement - achievement_low ) / (achievement_high-achievement_low) = (actual_rating - rating_low ) /

(rating_high-rating_low).

Target Rating Table

Target Rating

20 1

30 2

40 3

50 4

70 5

Actual Achievement Calculations

Actual Achievement Calculated Actual Rating

20 1

25 1.5

55 4.25

80 5

If the Actual Achievement is 25, then the Actual Rating can be calculated as: (30-20)/(2-1)=(25-20)/(Calculated
Actual Rating-1), where the Calculated Actual Rating=1.5

If the Actual Achievement is 55, then the Actual Rating can be calculated as: (70-50)/(4-3)=(55-50)/(Calculated
Actual Rating-3), where the Calculated Actual Rating=4.25

Here is an XML example for your to configure the interpolation calculation type. The exact configuration depends
on your system settings.

 Sample Code

<field-definition id="metric-lookup-table" type="table" required="false"

detail="false" viewdefault="off" showlabel="false" default-calc-
type="interpolate" field-show-coaching-advisor="false" cascade-update="push-
down" use-min-target-as-rating="true">
<field-label>Achievement Levels</field-label>
<table-row-label>Achievement Lookup Table</table-row-label>
<table-column id="achievement" type="number" required="false" cascade-
update="push-down">
<column-label>Target Level</column-label>
<column-description>Target Level</column-description>
/table-column>
<table-column id="rating" type="number" required="false" cascade-update="push-
down">
<column-label>Score</column-label>

Goal Management
198 PUBLIC Creating Goals and Ratings with Achievement Lookup
 <column-description>Score</column-description>
</table-column>
<table-column id="description" type="text" required="false" cascade-update="push-
down">
<column-label>Description</column-label>
<column-description>Description</column-description>
</table-column>
<rating-scale rate-on-form-option="false" default="true">
<rating-scale-id>OBPerformance</rating-scale-id>
</rating-scale>
</field-definition>

 Note

Interpolation does not work with actual-achievement-text. If the rating calculation is configured to use
Interpolation but the users enter text values, the Step calculation type is performed.

15.4 Out of Bounds Calculations

This section defines what the system does when the actual achievement falls outside of the range defined in the
target level rows.

Let's take the following example:

Target Rating Table

Target Rating

20 1

30 2

40 3

50 4

70 5

● Upper Bound: The system always gives the highest rating value when the actual achievement is above the
highest target level. An actual rating of 71 gets a 5.
● Lower Bound: There are two options for how the system handles actual achievements below the lowest target
level. This option is configured through the attribute use-min-target-as-rating defined in the field-
definition for the metric-lookup-table. Accepted values are true and false.
○ true – When the actual achievement falls below the lowest target level, then provide the rating associated
to the lowest target level. In the example, an actual achievement of 18 would result in a rating of 1.
○ false – When the actual achievement falls below the lowest target level, then provide a rating of 0. In the
example, an actual achievement of 18 would result in a rating of 0.

 Note

When the attribute is set to true, the rating is a value of 1 and the rating scale range is 1-5. When the attribute is
set to false and the rating is 0, then the rating scale range changes to 0-5. This could cause confusion for
customers when ratings are normalized on a Performance Management form. For example, a customer has a
goal plan with two goals on it. One goal has a rating of 1 with a scale of 1-5. The other goal has a rating of 0 with a

Goal Management
Creating Goals and Ratings with Achievement Lookup PUBLIC 199
 scale of 0-5. If the Performance Management form has a rating scale of 1-5, then both ratings are treated as a 1.
If the attribute is set to false, it is recommended that all rating scales also have a 0 entry.

15.5 Display Configurations

Here we describe the different display configurations possible for goals and ratings.

Description Column

The metric lookup table supports an additional column which represents the description of the rating value. This
column can be included through the table column id description in the metric lookup table field definition.

<table-column id="description" type="text" required="false">

<column-label>Description</column-label>
<column-description>Description</column-description>
</table-column>

Calculated Rating

The calculated rating field can be configured to display in one of the following formats. This configuration is
controlled through the <display> attribute on the rating field definition. Accepted values are:

● number – Only shows the numeric value. Interpolation calculation type will always display numeric value
regardless of the configuration option.
● text – Only the description is displayed.
● number-text – Both numeric value and description are displayed. This format only works when <default-
calc-type="step"> is configured.

The calculated goal rating displays on a Performance Management form regardless of how it was configured in the
goal plan. The rating appears the same way it does on the goal plan as it does on the Performance Management
form.

<field-definition id="rating" type="number" required="false" detail="false"

viewdefault="on" showlabel="false" field-show-coaching-advisor="false"
{color:#ff0000}display="number-text"{color}>
<field-label lang="en_US">Rating</field-label>
<field-description>Score</field-description>
<default-value>0.0</default-value>
</field-definition>

Goal Management
200 PUBLIC Creating Goals and Ratings with Achievement Lookup
Column Ordering

Column ordering controls the ascending or descending order required for numeric target levels and ratings
columns in the metric lookup table. This configuration is controlled through the table-column attribute <order>.
The system requires that values placed in those columns are in the correct order. This only applies to table-column
ID of "achievement" and "rating". Accepted values are asc, desc, and both. The default value is both.

● asc - must be of ascending order

● desc - must be of descending order
● both - can either be in ascending order or descending order

<field-definition id="metric-lookup-table" type="table" required="false"

detail="true" viewdefault="on" showlabel="true"default-calc-type="interpolate"
display="text" field-show-coaching-advisor="false">
<field-label lang="en_US">Achievement Levels</field-label>
<table-row-label>Achievement Lookup Table</table-row-label>
<table-column id="achievement" type="number" required="false" order="both">
<column-label lang="en_US">Target Level</column-label>
<column-description>Target Level</column-description>
</table-column>
<table-column id="rating" type="number" required="false" order="asc">
<column-label lang="en_US">Score</column-label>
<column-description>Score</column-description>
</table-column>
<table-column id="description" type="text" required="false">
<column-label>Description</column-label>
<column-description>Description</column-description>
</table-column>
</field-definition>

The default is to allow the achievement column to be either ascending or descending and to force the rating scale
to be ascending. It is because some achievements should result in a better rating as the achievement decreases.
For example, number of errors per 1000. Fewer errors are good and therefore should result in a better rating.

15.6 Automatic Rating Scale Population

Customers can enable calculated ratings with or without a rating scale.

This basically just pre-populates the rating column with values defined from a system rating scale.

If a default rating scale is configured, the rating scale will be displayed in the Create Goal and Edit Goalscreens
rather than as a button as shown in other sub-goals. By deleting all the rating scale rows, the metric lookup table
will be closed showing a green + button. To configure a rating scale with the calculated ratings feature, add the
'rating-scale' field to identify the rating scale you wish to use inside the field-definition for a metric-lookup-table
field. An optional default attribute can be used to specify what rating scale is the default rating scale. Possible
options are true and false. The default is true (for backwards compatibility reasons) but only the last "true" rating
scale will be the default rating scale.

Goal Management
Creating Goals and Ratings with Achievement Lookup PUBLIC 201
Example

<rating-scale default ="true">

<rating-scale-id>Metric Lookup Scale</rating-scale-id>
</rating-scale>

Customers can define more than one rating scale for the calculated ratings feature. When this happens, employees
will see a dropdown which will allow the employee to select the rating scales to be copied into the metric lookup
table.

 Note

The default rating scale is used to normalize goal ratings with Performance Management ratings. If there is no
default rating scale, the calculated rating cannot be copied across to a performance management form.

15.7 Automatic Actual Rating Population

You can configure the goal plan so that it automatically calculate actual ratings based on the metric lookup table
and actual achievements.

For example, the below Target Rating Table is your lookup table:

Target Rating Table

Target Achievement Target Rating

20 1

30 2

40 3

50 4

70 5

You want to calculate the Actual Rating in the below Actual Achievement Calculations table:

Actual Achievement Calculations

Actual Achievement Actual Rating

20

25

55

80

Goal Management
202 PUBLIC Creating Goals and Ratings with Achievement Lookup
You can populate the actual ratings automatically by adding the following configuration to your XML form:

 Sample Code

<auto-population field="rating" mode="auto">

<rule>
<calculated-result calculator-id="GM_MLT_BASED_RATING_CALCULATOR"/>
</rule>
</auto-population>

15.8 Automatic Target and Rating Scale Population

This feature primarily serves to auto populate the target levels based on configurations defined in the goal plan.

The sample use case would be: A user selects from a drop-down the rating scale/type to be used for this goal. The
user also enters a target baseline value. Based on these two selections the system will populate the metric lookup
table. The requirements to enable this feature are:

1. Define a field-definition for the target baseline

2. Configure target-to-rating mappings in the goal plan so values can be pre-populated

So the use case would be:

% of Target Baseline Rating

80% 60

90% 80

100% 100

110% 120

125% 140

Target Baseline

<field-definition id="target-baseline" type="number" required="false"

detail="false" viewdefault="on" showlabel="false" field-show-coaching-
advisor="false">
<field-label>Target Baseline</field-label>
<field-description>Target Baseline</field-description>
<default-value>0.0</default-value>
</field-definition>

Mapping XML

<metric-lookup-table-target-auto-population id="sales">
<scale-name>Sales</scale-name>
<mapping baseline-percent="80" rating="60">
<mapping-description>Worst</mapping-description>
</mapping>
<mapping baseline-percent="90" rating="80">
<mapping-description>Bad</mapping-description>
</mapping>
<mapping baseline-percent="100" rating="100">
<mapping-description>Ok</mapping-description>

Goal Management
Creating Goals and Ratings with Achievement Lookup PUBLIC 203
 </mapping>
<mapping baseline-percent="110" rating="120">
<mapping-description>Good</mapping-description>
</mapping>
<mapping baseline-percent="120" rating="140">
<mapping-description>Best</mapping-description>
</mapping>
</metric-lookup-table-target-auto-population>

 Remember

This code snippet is a sample configuration. The exact configuration depends on your system settings.

This will create the following UI:

The system calculates the target levels based on percentage of the target baseline and populates the target level
column. The system accepts multiple mappings and that will result in additional entries in the Rating Scale drop-
down in the UI.

15.9 Numeric vs. Text Target Levels

While not a commonly used configuration, the system supports the ability to enter text target achievement levels.

A goal plan can be configured to support either or both achievement types. So a single goal plan can have two goals
which use different target achievement types. The text achievement only works with calculation type "step" and is
an exact match between actual text achievement and text target level. The table-column id for text achievement is
"achievement-text" and the actual text achievement field-definition is "actual-achievement-text". When both text
and numeric achievement are configured, the user has an option to select between the two types.

Goal Management
204 PUBLIC Creating Goals and Ratings with Achievement Lookup
15.10 Non-Linear Step Warning

This feature lets customers choose to display a warning message in MLT if the achievement and rating levels are
non-linear (that is, if the slope changes between the achievement / rating values in the table).

Configuration - In the objective plan template we need to add the following configuration for enabling this feature.

 Note

This configuration will support only for “metric-lookup-table”.

<field-definition id="metric-lookup-table" type="table" required="false"

detail="false" viewdefault="on" showlabel="false"default-calc-type="interpolate"
field-show-coaching-advisor="false" cascade-update="push-down" linearity="true">
……….
< /field-definition >

15.11 Detailed Miscellaneous Behaviors

This section describes miscellaneous behaviors in goal rating calculations.

The rating is calculated when the goal is saved after any changes. If the goal plan includes the metric-lookup-table
field, validation will ensure that the user does not enter only 1 row, which would result in a rating calculation error.
However the user may opt to enter 0 rows, bypassing the automatic calculation. The logic that the application
follows when determining whether to calculate a rating is as follows:

1. If 2 or more rows are entered in the lookup table, and actual achievement has been entered, calculate the
rating.
2. If no rows are entered in the lookup table and actual achievement is 0, the rating is not calculated, and the goal
can be rated on the form just like a regular goal.

As with any fields in the TGM template, all 3 fields must be permissioned appropriately and included on the plan
and form layouts if desired. The rating field, however, will always be read-only, even if write permission is granted.
Typically, you will want to limit write permission for the metric lookup table and actual achievement to managers,
otherwise employees could essentially set their own ratings of record.

 Note

To edit goals with this configuration on a form, you must set obj-edit="popup" in the form objective section.
(The metric lookup table cannot be edited in on-form editing mode.) A rating scale does not need to be
specified in the TGM template or goal. The maximum & minimum for the rating (stored in the system to
determine normalized ratings) is determined by the possible ratings in the lookup table.

Goal Management
Creating Goals and Ratings with Achievement Lookup PUBLIC 205
Rules About the Rating Calculation

1. The field definition flag use-min-target-as-rating determines the behavior of the minimum rating value.
If use-min-target-as-rating="false" for the calculated rating field, and the value goes below the
minimum rating value, the calculated rating will be "0". If the use-min-target-as-rating="true", the
minimum possible rating value is the minimum rating. The default value of the use-min-target-as-rating
is "false", so adding use-min-target-as-rating="false" or simply leaving this code out of the XML,
the results are the same.
2. The calculated rating can never exceed the maximum rating possible in the lookup table.
3. If a rating scale is associated to the calculated rating feature, the rating scale will be automatically displayed.

15.12 XML Example for Goals and Ratings with Achievement

Lookup

The following is an example of an XML for goals and ratings with achievement lookup.

Example

XML Examples

<field-definition id="metric-lookup-table" type="table" required="false"

detail="false" viewdefault="on" showlabel="false"default-calc-type="step" field-
show-coaching-advisor="false">
<field-label>Achievement Lookup</field-label>
<table-row-label>Achievement Lookup Table</table-row-label>
<table-column id="achievement" type="number" required="true">
<column-label>Target Level</column-label>
<column-description>Target Level</column-description>
</table-column>
<table-column id="rating" type="number" required="true">
<column-label>Score</column-label>
<column-description>Score</column-description>
</table-column>
<table-column id="description" type="text" required="true">
<column-label>Description</column-label>
<column-description>Description</column-description>
</table-column>
<rating-scale>
<rating-scale-id>Metric Lookup Scale</rating-scale-id>
</rating-scale>
</field-definition>

<field-definition id="metric-lookup-table" type="table" required="false"

detail="false" viewdefault="off" showlabel="false" default-calc-type="interpolate"
field-show-coaching-advisor="false" cascade-update="push-down" use-min-target-as-
rating="true">
<field-label>Achievement Levels</field-label>
<table-row-label>Achievement Lookup Table</table-row-label>
<table-column id="achievement" type="number" required="false" cascade-update="push-
down">

Goal Management
206 PUBLIC Creating Goals and Ratings with Achievement Lookup
 <column-label>Target Level</column-label>
<column-description>Target Level</column-description>
/table-column>
<table-column id="rating" type="number" required="false" cascade-update="push-down">
<column-label>Score</column-label>
<column-description>Score</column-description>
</table-column>
<table-column id="description" type="text" required="false" cascade-update="push-
down">
<column-label>Description</column-label>
<column-description>Description</column-description>
</table-column>
<rating-scale rate-on-form-option="false" default="true">
<rating-scale-id>OBPerformance</rating-scale-id>
</rating-scale>
</field-definition>

15.13 Auto-Create Target Entries for Metric (Achievement)

Lookup

You can use this feature to auto-calculate different levels of target achievement based on the levels of percent
achievement that will be paid out for.

Goals can have a positive or a negative correlation of achievement to percent payout.

Through appropriate configuration of the goal plan, a user can select a merit guideline, which defines scores based
on % achievement of target along with a textual descriptor. Then the user enters in the target achievement level
(target baseline). Based on this information the system will automatically calculate all the appropriate target
achievement for the different levels of merit as defined in the merit guideline.

For example My generic "SALES" Merit Guideline could be:

● 80% Achievement Pays

● 60% of Bonus WORST
● 90% Achievement Pays
● 80% of Bonus BAD
● 100% Achievement Pays
● 100% of Bonus OK
● 110% Achievement Pays
● 120% of Bonus GOOD
● 200% Achievement Pays
● 140% of Bonus BEST

So when you create your goal, and set the Target Baseline and Merit Guideline, the system automatically generates
the Achievement Levels as follows: Target Baseline = $50,000 (entered)

Goal Management
Creating Goals and Ratings with Achievement Lookup PUBLIC 207
  Note

You can use multiple "Merit Guidelines" in both ascending and descending scale formats. You can choose either
Interpolated or Step achievement lookups. Any automatically calculated level or score can be overridden using
the edit scaleoption displayed directly under the Rating Scale drop-down. Maximum limit for B1009 is 100 rows.

Configuration

Configuration is done in the goal template XML (no associated admin or provisioning switches) and requires the
following settings (an example goal template XML file is attached for ease):

1. Set default-calc-type="Interpolation" or "Step".

2. Set use-min-target-as-rating=false for example.: <field-definition id="metric-lookup-table" type="table"
required="false" detail="false" viewdefault="on" showlabel="false" default-calc-type="interpolate" field-show-
coaching-advisor="false" use-min-target-as-rating="false">

Goal Management
208 PUBLIC Creating Goals and Ratings with Achievement Lookup
3. Set achievement/rating as numeric by setting: for example.: <table-column id="achievement" type="number"
required="true">
4. Set order="both" in the template for Target and Rating. For example.: <table-column id="rating"
type="number" required="true" order="both">
5. Add a Target Baseline field in the Goal Template.

<field-definition id="target-baseline" type="number" required="false"

detail="false" viewdefault="on" showlabel="false" field-show-coaching-
advisor="false">
<field-label>Target Baseline </field-label>
</field-definition>

6. Set up to autopopulate target values from the goal template:

<metric-lookup-table-target-auto-population id="sales" >

<scale-name>sales name</scale-name>
<mapping baseline-percent="80" rating="60">
<mapping-description>Worst</mapping-description>
</mapping>
<mapping baseline-percent="90" rating="80">
<mapping-description>Bad</mapping-description>
</mapping>
<mapping baseline-percent="100" rating="100">
<mapping-description>Ok</mapping-description>
</mapping>
<mapping baseline-percent="110" rating="120">
<mapping-description>Good</mapping-description>
</mapping>
<mapping baseline-percent="120" rating="140">
<mapping-description>Best</mapping-description>
</mapping>
</metric-lookup-table-target-auto-population>

Goal Management
Creating Goals and Ratings with Achievement Lookup PUBLIC 209
16 Mass Upload for Assigning

This feature enables mass upload functionality for the assigning process.

For mass assignment of goals, grant permissions for assigning group goals and for importing the goals in the
application.

You can use a CSV file to assign certain targets for specific employees in one upload step. To accomplish this
requirement, we updated the goal import (Mass Goal Import) to support an action of assign to accompany the
existing add, edit, and delete. This value option was also added to the goal import template.

Since we leveraged Goal Import, which is an Admin Tool, permissions are unrestricted. If the necessary role-based
permissions are granted to a user, the role permissions from the template are ignored (EM, EMM, EX, and so on).

The only exception is that the import does not allow the assignment of goals to the goal plan of an employee if the
goal plan is in a “locked” permission state.

16.1 Accessing Mass Assign Button

This section describes how you can access the mass assign button.

Prerequisites

You have permissions for assigning group goals and for importing the goals in the application.

Procedure

1. Go to Home Goals .

The Goal Plan page shows.

2. On the Goal Plan page, select Mass Assign from the dropdown of Actions.

The Assign Group Objective by uploading a CSV file popup window appears. The Mass Assign button is a push
feature, meaning it requires no any additional configuration to activate in addition to the permissions
mentioned.
3. Click Choose File and select the CSV file with the goals defined for mass assigning.

Select the Allow Duplicate Assignment checkbox if you want to allow for duplication.
4. Click Upload.

Goal Management
210 PUBLIC Mass Upload for Assigning
Results

You have successfully assigned goals to multiple employees.

16.2 Downloading CSV Header Template

The section describes how you can use the CSV header template.

Procedure

1. Select Goals from the Home menu.

The Goal Plan page shows.
2. Select Generate CSV header from the Actions dropdown.

The CSV header template is downloaded.

3. Open the CSV header an add assignment information.

Use the assign action option to fill in goal assignment information.

Results

You have successfully downloaded the CSV header template. You can now update the template with goal
assignment information.

Next Steps

● The FILTER_USERNAME allows the Assigner to populate one or more UserID’s. Multiple UserID’s are entered
by separating the IDs with a semi-colon.
● You can have an individual row for each FILTER_USERNAME.
● You can have an individual row each Target for each user.

Goal Management
Mass Upload for Assigning PUBLIC 211
● Fields can be populated to be included in the assignment based on permissions settings configured for the
Plan Template. For example, weights for targets can be populated in the template, and assigned to employee
assuming that the assigner has been given edit permission for the field (via the template configuration).
● When using the action of assigning, some fields can remain empty (except for ID, FILTER_USER, ACTION). If
they are not empty, then the behavior depends on the configuration of the form as to whether a field is a push
down field or not. If a field is populated for a push down field that the assigner does not have access to, the
system ignores that value.
● The assignment of new group goals allows you to make assignments to inactive users.
● The file size cannot exceed 5 MB.

16.3 Running the Import Job

This solution is implemented as an offline, scheduled job, which has a status

1. The import job gets scheduled immediately (there is no schedule setting option).
2. It runs depending on the capacity of the quartz server.
3. It is not possible to view the status of the job from the admin interface however it is possible from provisioning
to check on the status of a job (this step should not be necessary as jobs should not take a significant amount
of time to run).

 Remember

As a customer, you do not have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner. If you are no longer working with an implementation partner, contact SAP Cloud
Support.

4. When the job is complete, an email is sent to the user who initiated the import.
5. The email has details like rows added, updated, deleted. For the new “assign” action, we will include additional
messages for assigned as well.
6. If there is an error in the processing, we will include the reason for the error.
Error Examples:
○ If a user is included in FILTER_USER field that is not part of the assigned population for the assigner
○ If accidentally, a definer (or any other user) tries to perform an assign operation

Assigning the Target More than Once

Currently, from the existing user interface, we provide a warning when a user tries to assign the same goal twice,
however that does not stop the assigner from assigning twice.

In the scenario that a duplicate assignment is included in the CSV import file, then the duplicate record will get
rejected, and will be included in the e-mail report. It should be noted that in this situation, just the duplicate gets
rejected. The other valid goal/targets will continue to be processed and assigned.

We provide a check box at the import screen, which would determine whether duplicating a goal is an allowed
action during the mass assign. If checked, then the systems will allow the duplicate goals to be assigned. If
unchecked, then the system will provide an error message in the job complete e-mail.

Goal Management
212 PUBLIC Mass Upload for Assigning
16.4 Mass Assign Assumptions

The following assumptions are made when dealing with mass upload for assigning.

1. When we give ALL under FILTER_USERNAME column in the CSV, we assign the goals to all the users in the
target population.
2. To assign the goals to specific users, we give the usernames separated by a semicolon ; under
FILTER_USERNAME column in the CSV.
3. You can have an individual row for each FILTER_USERNAME if needed.
4. You can have an individual row each Target for each user if needed.
5. If we give a username under FILTER_MGR_ID column in the csv then the goal will be assigned to all the
subordinates of that user who are in target population. This assumes all the employees are part of the target
population of the assigner. If some listed employees are not part of the target population, the system will
complete the assignment for those that are, and reject the ones who are not (reported in e-mail notification).
6. If we mention FILTER_DEPT, FILTER_DIV, or FILTER_LOC, then the goal will be assigned to the entire user
matching the DIV, DEPT, LOC but who are in target population (assumes the employees are part of the target
population). These fields can be utilized independently of each other (you are not restricted to identifying
values for all the fields).
7. Other customer modules/processes are not impacted by these changes.
8. Import functionality respect plan state configuration, and will not be able to add, edit, or delete goals to an
employee plan that is in a state that is restricted from these actions (Locked Plan).

Goal Management
Mass Upload for Assigning PUBLIC 213
17 Mobile Goals

Mobile Goals are available for any customers who wish to get started with mobile goal management. The product
offers the user access to his or her goal plan and the ability to quickly update goal status fields.

What is Currently Supported

● View all active Goal Plans

● Add Goal
● Edit Goal and Delete Goal
● View all personal goals description and details
● View and Update Status related fields (percentage complete, state/status, BizX target/actual)
● View and Update Goal Name field
● Manager Access

Key Features Not Currently Supported

● Cascade/Align Goals
● Metric Look-up Tables
● Group Goals (1.0 or 2.0)
● Team Goals
● Goal Plan State/Workflow functionality (lock/unlock plans)
● Goal Execution
● Goal Library
● Smart Goal Wizard

 Note

The list of Goal Management features that are currently not supported on Mobile is not an exhaustive list.

Goal Management
214 PUBLIC Mobile Goals
17.1 Enabling Mobile Goals

You enable users to view and edit their goals and managers to access their team goals on a mobile device via the
Admin Center.

Context

Enabling mobile features applies to all mobile-enabled end-users. If you want to set up specific rights for specific
individuals or groups of people, you need to select Mobile User Permissions from the Admin Center. If a mobile
feature is enabled, only the end-users who have mobile permissions from User Permissions have access to that
feature.

 Note

The Admin Access for Goal ODATA API Export permission is for the Data Protection Officer role only. Do not
grant this permission to users other than the Data Protection Officer. If this permission is enabled, mobile users
can see previously deleted goals and may encounter system disfunction when they try to add, edit, or delete
goals on a mobile device.

Procedure

1. Go to Admin Center Mobile Enable Mobile Features .

The Mobile Settings page appears.
2. On the Enable Mobile Features tab, expand the Modules header.
The Modules section displays a list of features that you can enable.
3. Under Talent, select Goals, and on the confirmation message that appears, click Turn ON.

Results

You have successfully enabled Mobile Goals.

17.2 Installing SAP SuccessFactors HCM Mobile Application

This section describes how to install SAP SuccessFactors HCM Mobile in your mobile device.

1. Download the application from App Store or Google Play.

2. Launch the application. The Activation screen appears.

Goal Management
Mobile Goals PUBLIC 215
3. Tap Use Activation Code. An activation code appears on the Activate screen. Now, leave the mobile app at this
screen, and perform the web application-related steps.

 Note

You can alternately use the Scan QR Code option for adding the profile.

Goal Management
216 PUBLIC Mobile Goals
4. Next, you need to activate the new profile - launch the web application, and log in using the profile you want to
add to your mobile application.
5. On the top-right corner of the screen, click your username, and select Options.

Goal Management
Mobile Goals PUBLIC 217
6. On the Options page, click the Mobile tab, enter the Activation code as it appears on your mobile device, and
click Save.
7. Come back to your mobile application and complete the profile addition - under the activation code, tap
Activate.

8. On the User License screen, only if you agree to the license terms and the data privacy terms, then select both
the options, and tap I Accept. The mobile device is activated successfully.

17.3 Accessing Goal Plan on the Mobile Application

You can access your Goal Plans, and the Goal Plan of your direct reports using the SuccessFactors mobile
applications for iOS and Android.

Accessing your "Goal Plan" via the mobile application

1. Launch the SAP SuccessFactors application.

Goal Management
218 PUBLIC Mobile Goals
2. Tap Goals on the task bar.

 Note

If you do not find Goals on the task bar, tap More and then select Goals.

Your default Goal Plan appears. Tap Plans to switch to another Goal Plan.

Accessing the "Goal Plan" of your direct reports via the mobile application

Via the iOS application

1. Launch the SAP SuccessFactors application.

Goal Management
Mobile Goals PUBLIC 219
2. Tap the Team tab at the bottom of the app.

3. Tap the member of your team you want to view.

Goal Management
220 PUBLIC Mobile Goals
4. Scroll to the bottom of the screen, and tap Goals.

Via the Android application

1. Launch the SAP SuccessFactors application, and go to the Team tab.

Goal Management
Mobile Goals PUBLIC 221
2. Tap the member of the team, whose achievements you want to view. The team member's Activities view
appears.
3. Tap the Goals tab to view the Goal Plan of your direct reports.

17.4 Adding a New Goal using the Mobile Application

You can add new goals to your Goal Plan, or to the Goal Plan of your direct reports using the SuccessFactors mobile
applications for iOS and Android.

Procedure

1. On the SAP SuccessFactors mobile application, open your Goal Plan or the Goal Plan of your direct reports.
2. At the bottom of the Goal Plan, tap Add Goal. The New Goal screen appears.
3. Set the Visibility of your goal as either Public or Private, and select its Category.

 Note

The Category values depend on the configuration of your Goal Plan.

4. Enter Goal Name, and other information such as Metric, Weight, Status, Start Date, Due Date, % Complete, and
so on. If your Goal Plan configuration supports, you can also add Sub-Goals, Milestones, and Deliverables.

Goal Management
222 PUBLIC Mobile Goals
  Note

The fields and sections you see in your Mobile goal are consistent with the configuration of the Goal Plan on
web.

5. After you've filled out all the fields, tap Done to save the changes.

Results

You have successfully added a new goal to the Goal Plan.

17.5 Editing a Goal using the Mobile Application

You can edit the goals in your Goal Plan, or in the Goal Plan of your direct reports using the SuccessFactors mobile
applications for iOS and Android.

Procedure

1. On the SAP SuccessFactors mobile application, open your Goal Plan or the Goal Plan of your direct reports.
2. Tap the goal you want to edit. The Goal Detail screen appears.
3. Tap Edit to edit the goal.
4. You can change the Visibility of your goal, and edit its Category.

 Note

The Category values depend on the configuration of your Goal Plan.

5. You can edit the Goal Name, and update the values for Metric, Weight, Status, Start Date, Due Date, %
Complete, and so on. If available in your goal, you can update the Sub-Goals, Milestones, and Deliverables
sections as well.
6. After you've updated the goal, tap Done to save the changes.

Results

You have successfully updated a goal in the Goal Plan.

Goal Management
Mobile Goals PUBLIC 223
17.6 Deleting a Goal using the Mobile Application

If you have the permission, you can delete goals from your Goal Plan, or from the Goal Plan of your direct reports
using the SuccessFactors mobile applications for iOS and Android.

Procedure

1. On the SAP SuccessFactors mobile application, open your Goal Plan or the Goal Plan of your direct reports.
2. Tap the goal you want to delete. The Goal Detail screen appears.
3. Tap Delete Goal, and tap Delete to delete the goal.

17.7 Adding Comments to a Goal using the Mobile Application

If your Goal Plan permits, you can add comments to goals in your Goal Plan, or to goals in the Goal Plan of your
direct reports, using the SuccessFactors mobile applications for iOS and Android.

Context

If the Goal Plan, in use, is configured to have a comments section for each goal, you can add comments to goals in
your Goal Plan, or to goals in the Goal Plan of team members reporting to you.

Procedure

1. On the SAP SuccessFactors mobile application, open your Goal Plan or the Goal Plan of your direct reports.
2. Tap the goal you want to add a comment to. The Goal Detail screen appears.
3. Tap Add comments at the bottom of the screen to add a comment to the goal. The Add comments screen
appears.
4. Enter your comments, and tap Done.

Results

Your comment appears in the comments section of the Goal Detail screen.

Goal Management
224 PUBLIC Mobile Goals
17.8 Updating or Deleting Goal Comments using the Mobile
Application

You can easily edit or delete your comments, added to a goal, using the SuccessFactors mobile applications for iOS
and Android.

Context

If the Goal Plan, in use, is configured to have a comments section for each goal, you can add comments to goals in
your Goal Plan, or to goals in the Goal Plan of team members reporting to you. You can also edit or delete the
comments, you've added.

Procedure

1. On the SAP SuccessFactors mobile application, navigate to the goal, on which you added the comment that
you want to edit or delete.
2. Tap the goal. Your comment appears in the comments section of the Goal Detail screen appears.
3. Tap the comment, and

○ Tap Edit comments to update your comment. The Edit comments screen appears.
1. Edit your comment and tap Update.
○ Tap Delete comments to delete the comment.

Results

You have successfully updated or deleted your comment.

17.9 Default Values in Mobile Goals

If you have configured default values for fields in a goal plan, you can now see those default values from mobile as
well.

For example, configuring weight as <default-value>0.0</default-value> in the goal plan will show 0.0 as
the default weight for a goal when a new goal is created.

Supported Fields

● Category

Goal Management
Mobile Goals PUBLIC 225
● Visibility
● All goal fields
● All subgoal fields
● All customized fields

Unsupported Fields

● Comment

Goal Management
226 PUBLIC Mobile Goals
18 Integrating Continuous Performance
Management with Goal Management

You can view the Continuous Performance Achievements, along with their feedback, directly on the Goal Plan.

Prerequisites

● Continuous Performance Management must be enabled in your SAP SuccessFactors instance.

● The role based permission Access to Continuous Performance Management Data must be enabled.

Context

Procedure

1. Go to Admin Center.
2. In the Tools Search field, search for Manage Templates. The Manage Templates page appears.
3. Click the Goal Plan tab, and open the Goal Plan template, in which you want to include the Achievements.
4. Click the General Settings tab, select Display Continuous PM Achievements on your Goal Plan, and click Save.

Goal Management
Integrating Continuous Performance Management with Goal Management PUBLIC 227
Results

The Continuous Performance Management Achievements column will be available in your Goal Plan.

 Note

The number of Continuous Performance Achievements linked with each goal, appears under the CPM
Achievements column on the Goal Plan page. When you click the count under the CPM Achievements
column, a pop-up window lists out the details of the linked achievements, along with the feedback comments
received on the achievements. Please note that you can search for the linked achievements - only by their title,
not by any other metadata.

Goal Management
228 PUBLIC Integrating Continuous Performance Management with Goal Management
19 Data Protection and Privacy

19.1 Data Protection and Privacy Content is Centralized

Data protection and privacy features work best when implemented suite-wide, and not product-by-product. For this
reason, they are documented centrally.

The Setting Up and Using Data Protection and Privacy guide provides instructions for setting up and using data
protection and privacy features throughout the SAP SuccessFactors HXM Suite. Please refer to the central guide
for details.

 Note

SAP SuccessFactors values data protection as essential and is fully committed to help customers complying
with applicable regulations – including the requirements imposed by the General Data Protection Regulation
(GDPR).

By delivering features and functionalities that are designed to strengthen data protection and security
customers get valuable support in their compliance efforts. However it remains customer’s responsibility to
evaluate legal requirements and implement, configure and use the features provided by SAP SuccessFactors in
compliance with all applicable regulations.

Related Information

Setting Up and Using Data Protection and Privacy

19.2 Data Retention Management Options

Identify which data purge function in the Data Retention Management tool meets your data protection and privacy
requirements.

The Data Retention Management tool supports two different data purge functions: the newer data retention time
management (DRTM) function and legacy non-DRTM function.

 Remember

We encourage all customers to stop using the legacy purge function and start using data retention time
management (DRTM) instead. To get started using this and other data protection and privacy features, refer to
the Data Protection and Privacy guide.

Goal Management
Data Protection and Privacy PUBLIC 229
If you already use the legacy data purge function as part of your current business process and you are sure that it
meets your company's data protection and privacy requirements, you can continue to use it, as long as you aware
of its limitations.

 Note

If you are using the legacy data purge function, you can only purge a calibration session when there is at least
one facilitator assigned to the session.

 Restriction

Be aware that the legacy data purge function may not meet your data protection and privacy requirements. It
doesn't cover the entire HXM Suite and it doesn't permit you to configure retention times for different countries
or legal entities.

In the longer term, we recommend that you also consider adopting the newer solution. In the meantime, to use
legacy data purge, please refer to the guide here.

Goal Management
230 PUBLIC Data Protection and Privacy
20 Using the Check Tool

Use the check tool to find potential problems and errors in your configuration before you call support about an
issue.

Prerequisites

Enable Metadata Framework (MDF). Most customers already use MDF.

Assign Access Check Tool and Allow Configuration Export to your role in Role-Based Permissions (RBP). If you want
to use the Quick Fix feature for the checks that have it, assign the Allow Check Tool Quick Fix permission too,

● Access Check Tool authorizes users to access the tool.

● Allow Configuration Export authorizes users to attach configuration information to a ticket.
● Some checks have a quick fix, which can be used to immediately correct any issues found by that check.
Assign the Allow Check Tool Quick Fix permission to authorize users to run these quick fixes.

Procedure

1. Go to Admin Center.
2. In the tools search field, type Check Tool.
3. In Application, select the application you want to check.

 Tip

All Applications runs checks in all your applications.

For example, to run checks for Time Off, select Time Off.

You see the checks for the application you selected. The description for each check describes the situation you
hope to find in running the check. For example, in running the check Accrual lookup by seniority is consistent,
you hope to find that the lookup is indeed consistent.
4. Click the check the box at top left in the table to run all checks.
5. If you want to run only some checks, select them individually.

 Tip

To understand what a check does, right click the Check ID. The system then displays some information on
the check.

6. Click Run Checks to check your applications for the checks you selected.

Goal Management
Using the Check Tool PUBLIC 231
Next Steps

Evaluate the results and resolve the issues. If you encounter an error you cannot resolve, contact Support by
creating a ticket.

Benefits of the Check Tool [page 232]

The SAP SuccessFactors check tool helps you identify and resolve issues when your system doesn’t work
as you expect.

Check Results [page 232]

After you run checks in the check tool, it returns the results of the check so that you can resolve issues that
it found.

Creating Support Tickets from the Check Tool [page 233]

When the check tool reports a serious issue, you might need to contact Support. You can create a Support
ticket from within the check tool.

Using the Quick Fix Feature [page 234]

The Check Tool includes a Quick Fix feature that you can use to immediately correct issues found during a
check run.

20.1 Benefits of the Check Tool

The SAP SuccessFactors check tool helps you identify and resolve issues when your system doesn’t work as you
expect.

If your SAP SuccessFactors applications are behaving in unexpected ways, it is likely that it has a configuration or
data conflict: you have some data that is inconsistent or a configuration error. The check tool quickly identifies
these types of problems so that you can avoid support tickets. You might still need to create a support ticket if the
problem is severe, but even in severe cases, the check tool can save you time because it can export the results of
the check and your configuration for support. The support engineer, therefore, can identify the issue more quickly.

When you run the check tool, you see:

● A list of issues in your configuration or data and the severity of each issue.
● A solution or recommendation to address the issue.

20.2 Check Results

After you run checks in the check tool, it returns the results of the check so that you can resolve issues that it
found.

To see the results of the checks, look in the Results column. If you run the checks multiple times to see how you are
resolving issues, look in the Previous Result column to compare the current results to previous results.

Goal Management
232 PUBLIC Using the Check Tool
Possible Results of Check Tool

Result Action

No issues found If the tool cannot find issues, you see a green check mark the Result.

Issues found If the tool finds issues, it reports the number of issues and a yellow warning icon or a red alarm
icon.

● The yellow icon indicates a low severity issue. The system proposes a solution.
● The red icon indicates a high severity issue. You must take action, which could include creat­
ing a Support ticket.

Related Information

Creating Support Tickets from the Check Tool [page 233]

20.3 Creating Support Tickets from the Check Tool

When the check tool reports a serious issue, you might need to contact Support. You can create a Support ticket
from within the check tool.

Prerequisites

Run the check tool. You can find the check tool by going to Admin Center Check Tool . You create the ticket
from the results page of the tool.

Procedure

1. On the results page, look in the Result column for the errors you want to report on.

You usually contact Support for high severity issues not low severity issues.
2. Click the error in the result to open the Detailed Result.

 Note

If you cannot click the error, expand the list of checks from the Description column, and then click the error
from the Result column.

3. In Detailed Result Need Assistance? , copy the component ID.

For example, LOD-SF-EC is the component ID for Employee Central.

Goal Management
Using the Check Tool PUBLIC 233
4. Create a customer incident in the relevant category.
5. When you create the ticket, paste the component ID into the ticket.

20.4 Using the Quick Fix Feature

The Check Tool includes a Quick Fix feature that you can use to immediately correct issues found during a check
run.

Procedure

1. Run checks as described in Using the Check Tool for one or more components. The tool generates check
results, some of which might be warnings or errors.
2. Select the result of one of the checks where issues were identified. If the check includes a quick fix, you see the
four-step process at the top of the resulting window. You are in step 1, called Found Issues.
3. Choose Step 2 to proceed to Select Correction.
4. The resulting window shows one or more corrections for the issue. Select the one you want and choose Step 3
to proceed to Final Approval.
5. In the Final Approval step, you can opt to change your mind and not carry out the fix. If you want to proceed,
choose Step 4.
6. The system confirms that the fix is now running. Choose Close to complete the procedure. The system verifies
that the fix has run correctly after a short time by running the check again.

Goal Management
234 PUBLIC Using the Check Tool
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements
with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you
agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at
any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the
experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback
(e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and
phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example
code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

Goal Management
Important Disclaimers and Legal Information PUBLIC 235
www.sap.com/contactsap

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

No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.

Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.

SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.

Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.

THE BEST RUN