Implementing Goal

Management
SuccessFactors, May 2014
Table of Contents
1 Change History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 What is Goal Management?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

2.1 About this Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
2.2 Integrating Performance Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

3 Getting Started - Configuration Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3.1 Recommended Goal Management Implementation Sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3.2 Turning on Goal Management in Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
3.3 Importing a Goal Plan Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.4 Exporting a Goal Plan Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.5 Copying and Exporting Goals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.6 My Goals View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
3.7 Email Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

4 Goal Plan Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

4.1 File Header. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.2 Goal Plan Template Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.3 Automatic Goal Numbering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.4 Objective Weight Rules and Objective Count Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.4.1 Objective Weight Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.4.2 Objective Count Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.5 Defining Category and Default-Category. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.6 Goal Wizard Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.7 Defining Goal Plan Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.8 Defining Goal Display for PM Forms (v11 only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
4.9 Custom Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
4.9.1 Custom Calculation Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
4.9.2 Custom Calculation DTD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
4.9.3 Calculations, Functions and Operators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
4.9.4 Special Case - Goal Plan and/or Category Score Total. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
4.9.5 Special Case - Sub-goal Calculated Rating. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

5 Goal Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

5.1 Enabling and Accessing Goal Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
5.2 CSV File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
5.3 Mapping Templates to Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
5.4 End User (Non-Admin) Upload for goal Create/Update/Delete. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
5.5 Understanding Goal ID, GUID, & SUBGUID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
5.6 Import File Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Implementing Goal Management

2 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Table of Contents
 5.6.1 Error Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
5.7 Goal Import Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
5.8 Goal Import Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
5.9 Goal Import FAQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
5.10 Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

6 Enabling Goal Execution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

6.1 Goal Plan Template Modifications to Enable Goal Execution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
6.2 Goal Plan Layout Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
6.3 Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
6.4 Admin Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
6.5 Meeting Agenda Planner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
6.6 Useful Tips for Goal Execution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

7 Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
7.1 Settings for SuccessFactors in the Home Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
7.1.1 Goal Management Module Permission (RBP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
7.1.2 Goal Management Module Permission (Standard Permissions). . . . . . . . . . . . . . . . . . . . . . . 91
7.2 Roles in Goal Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
7.3 Action Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
7.4 Field Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
7.5 Cascader Role. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99
7.6 Table Field Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
7.7 Table Column Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
7.8 Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
7.9 Goal Execution Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
7.10 Goal Plan States. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
7.10.1 Locking and Unlocking of a User's Goal Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
7.10.2 Change Locked / Unlocked State on Form Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

8 Setting up the Goals Management Home Page Tile without RBP. . . . . . . . . . . . . . . . . . . . . . . . . 111
Setting up the Goals Management Home Page Tile with RBP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

9 Accessing the Goal Management Tile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

10 Group Goals Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

10.1 Enabling Group Goals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
10.2 Using Group Goals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
10.3 Configuring Editable Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

11 Mapping of Goal Library Content to Goal Plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

11.1 Enhancing the Goal Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

12 Creating Goals and Ratings with Achievement Lookup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Implementing Goal Management

Table of Contents © 2014 SAP AG or an SAP affiliate company. All rights reserved. 3
12.1 Sample Use Case. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
12.2 Basic Metric Lookup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
12.3 Calculation Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
12.4 Out of Bounds Calculations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
12.5 Display Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
12.6 Automatic Rating Scale Population. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
12.7 Automatic Target and Rating Scale Population. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
12.8 Numeric vs. Text Target Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
12.9 Non-Linear Step Warning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
12.10 Detailed Miscellaneous Behaviors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
12.11 XML Example for Goals and Ratings with Achievement Lookup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
12.12 Auto-Create Target Entries for Metric (Achievement) Lookup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

13 Mass Upload for Assigning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

13.1 Requirements & User Story. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138
13.2 Accessing Mass Assign Button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
13.3 CSV Header Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
13.4 Running the Import Job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141
13.5 Mass Assign Assumptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

14 Mobile Goals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

14.1 Enabling Mobile in Provisioning and Admin Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
14.2 Installing SuccessFactors HCM Mobile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144
14.3 Accessing Goals on Mobile Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Implementing Goal Management

4 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Table of Contents
1 Change History
The following table provides a historical overview of the most important changes made to this document since its
initial publication.

Version Date Description

1.0 May 2014 Initial release

Implementing Goal Management

Change History © 2014 SAP AG or an SAP affiliate company. All rights reserved. 5
2 What is Goal Management?
SuccessFactors Goal Management enables employees and managers to align individual goals with company
business objectives.

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
● Managers can set cascading goals and see individual, team, or company-wide progress
● Compliance is improved by providing evidence of an objective review process. Plus, Legal Scan helps facilitate
compliance with Sarbanes-Oxley and other regulations

2.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

2.2 Integrating Performance Management

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

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

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

Implementing Goal Management

6 © 2014 SAP AG or an SAP affiliate company. All rights reserved. What is Goal Management?
3 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.

Resources for Configuration - DTD The DTD file is another good source of reference. If you have access to the
corporate intranet, you can download the latest DTD (document type definition) file which defines the structure
and syntax. It can be accessed from the Partner Portal or, from the company intranet at http://cvs/
viewcvs/V4/src/com/sf/dtd. The objective-template.DTD is used for TGM, IDP, Learning Activity and Career
Worksheet.

3.1 Recommended Goal Management Implementation

Sequence

To help you with your implementation, we recommend following this proven formula. This formula is based on PS
expertise. We strongly recommend you follow this sequence for the first few implementations and discuss any
variations with your team lead.

Step Num­ Name Description

ber

1 Set up Goal Management in Provi­ The initial configuration tasks to set up Goal Management.
sioning For more information see: Turning on Total Goal Manage­
ment in Provisioning

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

● Importing a Goal Plan Template

● Exporting a Goal Plan Template

Implementing Goal Management

Getting Started - Configuration Overview © 2014 SAP AG or an SAP affiliate company. All rights reserved. 7
Step Num­ Name Description
ber

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

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 Options [page 17]

5 Define Sub-tables: Targets, Tasks, Define the sub-tables for the goal field definitions. For more
Milestones, Comments information see: Defining Goal Plan Fields [page 34]

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

7 Define SMART Goal Wizard Enable the SMART Goal Wizard, if required. For more infor­
mation see: Goal Wizard Option [page 31]

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

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 120]

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

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

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 configure 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

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 Management form, if goals are pulled from the
goal plan into the PM form. For more information see: Defin­
ing Goal Plan Fields [page 34]

Implementing Goal Management

8 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Getting Started - Configuration Overview
3.2 Turning on Goal Management in Provisioning

When you turn on TGM for a customer, you are turning on TGM 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.

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

Note
This is for US English only, and does not apply to other languages.

3.3 Importing a Goal Plan Template

When you turn on TGM for a customer, you must also import a goal plan template for the company. Otherwise,
when a user tries to access TGM, an error will be displayed in the browser.

Currently, 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/re-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.

Implementing Goal Management

Getting Started - Configuration Overview © 2014 SAP AG or an SAP affiliate company. All rights reserved. 9
 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. More information is available
here .

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

1. Log in to Provisioning.
2. Select the company for which the goal plan template should be imported.
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 generally 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 (as shown in the
screenshot above) to specify which plan is rendered by default when you invoke TGM.

If more than one plan is active at a time, users will see a drop down list in TGM so that they can switch between
plans.

Implementing Goal Management

10 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Getting Started - Configuration Overview
3.4 Exporting a Goal Plan Template

You export a goal plan on the same page in Provisioning that you imported 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 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.

3.5 Copying and Exporting Goals

You can copy goals between goal plans as well as export the goals from a particular goal plan.

Copying Goals from Other Goal Plans

You can enable the wizard for copying goals between goal plans from Provisioning using the TGM/CDP Objective
Transfer Wizard setting.

Implementing Goal Management

Getting Started - Configuration Overview © 2014 SAP AG or an SAP affiliate company. All rights reserved. 11
Exporting Goals from Goal Plan (End User)

A user can export the goals from a particular goal plan page based on the permissions configuration.

In order to do this we 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>

3.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

To enable the goal filtering option, include the following XML in your TGM template: <summary-section
filter="true"/>

Implementing Goal Management

12 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Getting Started - Configuration Overview
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

a. 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.
b. 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.
c. 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

a. 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
b. 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:

Default Setting (date range filter enabled)- note that the goals displayed are within range:

Implementing Goal Management

Getting Started - Configuration Overview © 2014 SAP AG or an SAP affiliate company. All rights reserved. 13
Date Range Disabled - note that the goals outside the default date range are now displayed:

3.7 Email Notifications

There are three standard goal activity email notifications that are configurable for each goal plan.

1. Goal Creation Notification will be sent to a user when an goal was created for him/her.
2. Goal Delete Notification will be sent to the goal owner when the goal was deleted by another user from the
goal plan.
3. Goal Modification Notification messages are sent every 24 hours if changes were made to public goals on
the user's goal plan. The message includes created, modified, and deleted goals. Users are not notified of

Implementing Goal Management

14 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Getting Started - Configuration Overview
 changes they made themselves. Valid tokens for this message: [[LAST_EMAIL_DATE]] [[GOAL_OWNER]]
[[OBJ-PLAN-NAME]] [[OBJ_LIST]] [[SIGNATURE].

Implementing Goal Management

Getting Started - Configuration Overview © 2014 SAP AG or an SAP affiliate company. All rights reserved. 15
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.

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

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.

The first 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" "http://cvs/viewcvs/V4/scr/com/sf/dtd/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

Implementing Goal Management

16 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Goal Plan Templates
 This allows you to then 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 Template Options

The <obj-plan-template> tag is at the top of the goal plan template.

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”
>

There are various additional attributes that you can add into the <obj-plan-template>. To find these attributes
and put them in the correct order, refer to the DTD (objective-template_4_0.dtd - see topic “File Header”
for more information.)

In the DTD, the <!ELEMENT <obj-plan-template> area tells you the order the larger sections should be in, and
the <!ATTLIST obj-plan-template tells you all the possible attributes that can be in the <obj-plan-template>
section and in which order they have to be in.

Table 1: The obj-plan-template element is the root element of the objective template descriptor. It contains
the following sub-elements:
Sub-element Description Additional information

obj-plan-id The unique number that identifies Numbers are assigned as follows:
the goal plan
● 1 - 1000 for TGM
● 2001 - 3000 for IDP

Implementing Goal Management

Goal Plan Templates © 2014 SAP AG or an SAP affiliate company. All rights reserved. 17
Sub-element Description Additional information

● 4001 - 5000 for Learning Activ­

ity
● 5001 - 5099 for Career Work­
sheet

obj-plan-type Goal plan type This is used to differentiate between

the types of plans. Values for this
field are:

● Business goal plan

● DevelopmentCDP development
plan
● LearningActivitCDP learning ac­
tivities
● CareerWorksheetCDP career
worksheet

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

obj-plan-desc Goal plan description The dsecription does not appear in

the UI.

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

when the xml file is successfully up­
loaded into provisioning.

obj-plan-start Goal plan start date Format must be MM/DD/YYYY.

This establishes the default value
for the start date for each goal.

obj-plan-due Goal plan due date Format must be MM/DD/YYYY.

This establishes the default due
date for each goal.

obj-plan-numbering Option to automatically number For further information see Auto­

goals matic Goal Numbering [page 24]

add-wizard Option to use the Goal Wizard For further information see Goal
Wizard Option [page 31]

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

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

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

Implementing Goal Management

18 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Goal Plan Templates
 Sub-element Description Additional information

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

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

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

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

form-layout The goals that appear on a PM form For further information see Defining
layout Goal Display for PM Forms (v11 only)
[page 46]

pdf-layout Not used

details-layout Not used

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

Table 2: Global Setting Details (obj-plan attributes)

Option Valid Values Description Default

spellchk true a Spell Check button ap­ false - if option not speci­
pears next to the Save fied
Changes and Cancel but­
tons underneath each goal
being created

false disables spell checking for

all goals

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

false goals are created as pri­

vate goals

instructions-viewdefault on sets the View Options off - if option is not speci­

checkbox to automatically fied
display Instructions to new
users

off Instructions are not dis­

played until the user se­
lects the View Options
Instructions checkbo

alerts-viewdefault on sets the View Options on

checkbox to automatically
display show on plan
alerts to new users.

Implementing Goal Management

Goal Plan Templates © 2014 SAP AG or an SAP affiliate company. All rights reserved. 19
Option Valid Values Description Default

Note
The onscreen alert is a
yellow triangle icon that
appears next to a goal
plan to indicate one of
the following events oc­
curred:

● Goal is aligned to
another goal by an­
other user
● Goal is modified by
another user
● Aligned up goal is
modified by goal
owner
● Aligned up goal is
deleted by goal
owner
● Aligned up goal is
unaligned by an­
other 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 View Options
Alerts checkbox

cascade-parent-viewde­ on Current version of applica­ off

fault tion allows only off or disa­
off
ble, to meet accessibility
disable requirements

cascade-child-viewdefault on Current version of applica­ off

tion allows only off or disa­
off
ble, to meet accessibility
disable requirements

new-obj-share-status- true / false false

public

Implementing Goal Management

20 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Goal Plan Templates
 Option Valid Values Description Default

share-confirm true displays a Windows dialog false - if option not speci­

box prompting the user to fied
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 with­
out further confirmation

unshare-confirm true displays a Windows dialog false - if option not speci­

box prompting the user to fied
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 with­
out further confirmation

allow-group-goal true allows the goal administra­ false

tor to create and assign
group goals: this enables
goals for workgroups re­
porting to the same man­
ager

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

displayed 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- <number> Obsolete

parent

more-details-child-format orginal displays aligned down original - if option not

goals as a list, showing specified
only the full name, user­
name and goal name. See

Implementing Goal Management

Goal Plan Templates © 2014 SAP AG or an SAP affiliate company. All rights reserved. 21
Option Valid Values Description Default

example below for effect See Examples below for

of setting to original. screenshots showing the
goal-plan displays aligned down effect of different value
goals in a format similar to settings.
viewing goals in a plan.
See example below for ef­
fect of setting to goal plan.

display-alignment-format names displays the goal owner

goals displays the goal name

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

goal as public or private.
Additionally, goal can be
set as public or private
when goal is being cre­
ated.

false Icons are displayed to

show goal as public or pri­
vate.

Example
XML Example:

<?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>
</obj-plan-numbering>

Example
Text replacement:

</obj-plan-numbering>
<text-replacement for="Instructions">

Implementing Goal Management

22 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Goal Plan Templates
 <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">

Example
The following screenshots show the effect of the more-details-child-format option:

● more-details-child-format=original:

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

Example

Related Information

File Header [page 16]

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

Implementing Goal Management

Goal Plan Templates © 2014 SAP AG or an SAP affiliate company. All rights reserved. 23
4.3 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
Omit the obj-plan-numbering element entirely, if your customer does not want to have automatically
numbered goals in Goal Management.

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>
<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 are also able to left indent or right indent the goal by using the arrow buttons in the goal plan:

Implementing Goal Management

24 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Goal Plan Templates
4.4 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.)

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 16]

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

4.4.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>

Implementing Goal Management

Goal Plan Templates © 2014 SAP AG or an SAP affiliate company. All rights reserved. 25
 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.
● 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 26]

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

Min/Max per Category [page 27]

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

Min/Max per Objective [page 28]

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

4.4.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”.)

Implementing Goal Management

26 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Goal Plan Templates
 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">

Related Information

Objective Weight Rules and Objective Count Rules [page 25]

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

4.4.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>

Implementing Goal Management

Goal Plan Templates © 2014 SAP AG or an SAP affiliate company. All rights reserved. 27
Related Information

Defining Category and Default-Category [page 30]

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

4.4.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”.)

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 25]

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

4.4.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”.)

Implementing Goal Management

28 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Goal Plan Templates
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">

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.

Implementing Goal Management

Goal Plan Templates © 2014 SAP AG or an SAP affiliate company. All rights reserved. 29
Related Information

Defining Category and Default-Category [page 30]

The elements for category and default-category are used to determine sections of an objective plan to
which the objectives are allocated.
Objective Weight Rules and Objective Count Rules [page 25]
Attributes can be set to specify weight rules and count rules at various levels within the plan.

4.5 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. 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. If no category elements are defined, the objective plan is not divided into sections.

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.

Points to remember when defining category are:

● If no category element is defined, the objective plan is not divided into sections.
● 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
Do not 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 is not supported in category id: to display it in the goal category label on the plan, use "&".

For default-category remember:

● 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.

Table 3: Sub-elements
Attribute Description
id The id attribute defines the internal name used to store
and identify the category. This name should not be lo­
calized.

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

Implementing Goal Management

30 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Goal Plan Templates
 Attribute Description
lang The optional lang attribute for category-name defines
the locale 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">
<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.6 Goal Wizard Option

The optional add-wizard element provides a SMART goal wizard function in the goal plan.

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.
● You must enable the goal library with it.
● The Goal Wizard is not yet localized.

Implementing Goal Management

Goal Plan Templates © 2014 SAP AG or an SAP affiliate company. All rights reserved. 31
DTD Definition:

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

<!ATTLIST add-wizard
mode CDATA #REQUIRED

Sub-elements:

Table 4: 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>
</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">

Implementing Goal Management

32 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Goal Plan Templates
 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"/>

Implementing Goal Management

Goal Plan Templates © 2014 SAP AG or an SAP affiliate company. All rights reserved. 33
4.7 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 |

Implementing Goal Management

34 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Goal Plan Templates
 field15 | field16 |
field17 | field18 | field19 | field20) #IMPLIEDfield-show-coaching-advisor
(true | false) "false">

Table 5: 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

It is strongly recommended that you use the types as

illustrated 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).

field-label The field label that is displayed in the goal plan tem­
plate. 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.

Table 6: 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

Implementing Goal Management

Goal Plan Templates © 2014 SAP AG or an SAP affiliate company. All rights reserved. 35
Option Valid Values Description

viewdefault true Ignored (for 508 compliance). All

the fields in the first rows are dis­
false played by default.

showlabel true Field labels are not displayed by de­

fault when you view goals in the goal
false
plan but they are always displayed
when you create or edit a goal.

You may not need to display field la­

bels if the goal plan column head­
ings or tasks/targets/milestones
column headings are adequate in
representing the fields displayed.
Not showing field labels will help re­
duce 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), espe­
cially if the fields in the non-first
rows are not the table fields
(tasks/targets/milestones).

To show the field label, specify

showlabel="true" in the field defini­
tion tag. Otherwise, field labels are
not displayed by default if the attrib­
ute 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.

reportable true The "reportable" attribute deter­

mines which fields are available in
false
the Objective List report.

At most 20 fields across an entire

company may be reportable. If a
company has more than one objec­

Implementing Goal Management

36 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Goal Plan Templates
 Option Valid Values Description

tive template, all of the reporta­

ble="field1" fields must have the
same id and be of the same type
(text, date, enum, etc) across all ob­
jective plans.

Likewise for all of the reporta­

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

field-show-coaching-advisor true If true the link to the Coaching Advi­

sor will display above the field.
false
Only applies to fields of type tex­
tarea.

spellchk true ● If true, a Spell Check link is dis­

played above the field. Only ap­
false
plies to fields of type textarea.
● If false, this disables spell
checking for all goals
● Default is false if option is not
specified

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.

Implementing Goal Management

Goal Plan Templates © 2014 SAP AG or an SAP affiliate company. All rights reserved. 37
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:

Table 7: 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.

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

measured, in other words, success
criteria.

start date Goal start date - auto-populated

with the start date defined in the
<obj-plan-start> template tagfor­
mat 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

Implementing Goal Management

38 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Goal Plan Templates
 Field ID Type Typical Usage / Characteristics

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".

done percent Displayed as a whole number with a

graphical "progress" bar.

weight enum,(use text, textarea with care) The value in this field is used to
auto-populate the objective weight
when the goal is added to a PM
form. If configured as enum, the
value is used in the form not the la­
bel, e.g. <enum-value value="3">; if
configured as text, the text value en­
tered is used verbatim.

tasks table A table of individual tasks support­

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

targets table A table of individual targets towards

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

milestones table A table of individual milestones to­

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

metric text Defines a measurement for the goal,

for example percentage of comple­
tion.

comments comment Used to configure the layout and

permission for public comments.
The field is read-only and automati­
cally includes the name and date
stamp when the comments 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

Implementing Goal Management

Goal Plan Templates © 2014 SAP AG or an SAP affiliate company. All rights reserved. 39
Field ID Type Typical Usage / Characteristics

group-rating-comments rating Allows the group goal owner to en­

ter rating comments. See Group
Goals.

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”).

Table 8: Table field types

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 ID Must be of type Notes

Tasks desc textarea or text Max 2048 chars

Milestones start date

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, milestones and members. 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.

Implementing Goal Management

40 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Goal Plan Templates
Table 9: Table field elements
Description
table-row-label Displayed in the UI. The word "Add" is always pre­
pended to the label specified. For example "Task"
would display as "Add Task"-

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-de­

scription, type attribute defining its type; and optional
required and a default-value attributes similar to a
field-definition. Additional attributes available for the
table-column id element are:

● width: The width attribute specifies the width of the

column in characters. It should be specified for col­
umns of type "text" and "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 attribute, 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. An example is shown below.

column-label This is the label that identify the columns that appear in
a table. 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", 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", "per­
cent", or "number", the value is specified in a non-
localized format, and the lang attribute is not al­
lowed.
● For "enum" fields, the contents must be "value" at­
tribute 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).

Implementing Goal Management

Goal Plan Templates © 2014 SAP AG or an SAP affiliate company. All rights reserved. 41
 Description

In all cases, if the value is not required, an empty de­

fault-value tag specifies the initial value of the field is
empty.

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

Currently, 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

Enum Fields

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

Table 10: 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 colla­
tion order for sorting by the field.

● The "value" attribute defines the non-localized, in­

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

enum-label This is the text that displays in the drop down list.

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.

Implementing Goal Management

42 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Goal Plan Templates
 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.

Note
(HR: JIRA (TGM-4897) - is this still applicable?

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.

Table 11:
Attribute Description
reportable Determines which fields are available in the Objective
List report. At most, three 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 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 en­
tire application.

Custom fields can be added using the OneAdmin 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.

Implementing Goal Management

Goal Plan Templates © 2014 SAP AG or an SAP affiliate company. All rights reserved. 43
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.The field
becomes read-only after it is entered.

<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>

Implementing Goal Management

44 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Goal Plan Templates
 <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>
</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 101]

Permission tags give you the ability to control who can create, modify, or delete rows of a table within a goal
plan.

Table Column Permissions [page 102]

Table column permissions allow you to get more granular and define permissions for columns in the table.

Implementing Goal Management

Goal Plan Templates © 2014 SAP AG or an SAP affiliate company. All rights reserved. 45
4.8 Defining Goal Display for PM Forms (v11 only)

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

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

Example
The following XML defines a layout for displaying information in the PM form (V11):

<form-layout><![CDATA[<table width="100%" border="0">

<tbody>
<tr height="35">
<td width="20%" bgcolor="#DCDCDC" valign="top">#if($display.name) <b>$
{label.name} :</b>#end</td>
<td width="33%" valign="top">#if($display.name) ${field.name}#end</td>
<td width="8%" bgcolor="#DCDCDC" valign="top">#if($display.weight) <b>$
{label.weight} :</b>#end</td>
<td width="7%" valign="top">#if($display.weight) ${field.weight}#end</td>
<td width="8%" bgcolor="#DCDCDC" valign="top">#if($display.start) <b>$
{label.start} :</b>#end</td>
<td width="8%" valign="top">#if($display.start) ${field.start} #end</td>
<td width="8%" bgcolor="#DCDCDC" valign="top">#if($display.due) <b>$
{label.due} :</b>#end</td>
<td width="8%" valign="top">#if($display.due) ${field.due} #end</td>
</tr>
</tbody>
</table>

This shows how the PM form would appear:

4.9 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 (See ???? for additional supported functionality to display category and goal plan
level Score totals)
● Run Rate: Actual / (Current Date – Start Date)

Implementing Goal Management

46 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Goal Plan Templates
● Year End Forecast (based on current Run Rate): Run Rate x (Due Date – Start Date)
● Target Run Rate: Target / (Due Date – Start Date).
● 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>
<calculated-result calculator-id="posMed"/>

Implementing Goal Management

Goal Plan Templates © 2014 SAP AG or an SAP affiliate company. All rights reserved. 47
 </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>
<col id="description"><![CDATA[First Point - 2nd scale]]></col>
</row>

Implementing Goal Management

48 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Goal Plan Templates
 <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 50]

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

Custom Calculation DTD [page 51]

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

Calculations, Functions and Operators [page 54]

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

Special Case - Goal Plan and/or Category Score Total [page 58]
This feature is related to the calculated fields but is specific to displaying total scores.

Special Case - Sub-goal Calculated Rating [page 59]

Steps and XML to achieve a sub-goal calculated rating.

Implementing Goal Management

Goal Plan Templates © 2014 SAP AG or an SAP affiliate company. All rights reserved. 49
4.9.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.

CDO:/content/authoring/i041397146540509.image

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

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">

Implementing Goal Management

50 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Goal Plan Templates
 <rule><calculated-result calculator-id= "goalScore"/></rule>
</auto-population>

4.9.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”.

<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>

Implementing Goal Management

Goal Plan Templates © 2014 SAP AG or an SAP affiliate company. All rights reserved. 51
<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 but­

ton for the user to trigger the calcu­
lation and update of the field.

<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-condi­

tion, then populate the table (defined as the field in
<auto-population>) with values defined in this sec­
tion.

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 >

Implementing Goal Management

52 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Goal Plan Templates
 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).

<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 lo­

cale this value represents.

Implementing Goal Management

Goal Plan Templates © 2014 SAP AG or an SAP affiliate company. All rights reserved. 53
<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 54]

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

4.9.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
● 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))

Implementing Goal Management

54 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Goal Plan Templates
 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").

Table 12: Arithmetic Operators

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

Operator Description

+ Sum

- Difference

* Product

/ Quotient

Table 13: Arithmetic Grouping

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

Grouping Description

() Open and close parentheses to group expressions

Table 14: 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)

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)

Table 15: 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>

Implementing Goal Management

Goal Plan Templates © 2014 SAP AG or an SAP affiliate company. All rights reserved. 55
 <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>

Table 16: 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
(number) 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 columns (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)

multiple(column1, column2) For each row in a sub-goal table, multiply values from
two columns 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 column. 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
columns (column1/column2) into a third column. The
result is a column in a sub-goal row. For example,
FUNC.divide(task.actual, task.target)

Implementing Goal Management

56 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Goal Plan Templates
 Function Description

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)

Table 17: 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 pla­

ces, use this: round(1.234*100)/100=1.23. For 1
decimal 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, ceil(1.9)=1

Table 18: 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

Table 19: Comparision Operators

Can only be used in <rule-condition>.

Operator Description

== Equals

!= Does not equal

> Greater than

Implementing Goal Management

Goal Plan Templates © 2014 SAP AG or an SAP affiliate company. All rights reserved. 57
 Operator Description

= Greater than or equal to

< Less than

<= Less than or equal to

Table 20: Logical Operators

Can only be used in <rule-condition>.

Operator Description

&& And

|| Or

! Not

4.9.4 Special Case - Goal Plan and/or Category Score Total

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".
CDO:/content/authoring/i041398943225450.image
3. The same attribute can be applied to the <category> element show-total-goalscore="true".
CDO:/content/authoring/i041398943833367.image

Results

Formatting Total Score:

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

Implementing Goal Management

58 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Goal Plan Templates
4.9.5 Special Case - Sub-goal Calculated Rating

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”.

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

CDO:/content/authoring/i041398944339812.image

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>

Implementing Goal Management

Goal Plan Templates © 2014 SAP AG or an SAP affiliate company. All rights reserved. 59
 <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>

Related Information

Calculations, Functions and Operators [page 54]

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

Implementing Goal Management

60 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 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 the Admin Tools.

The goal import feature also supports:

● Import of the metric lookup table

● 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 though the import
● Enable goal plan permission association for customers with standard permissions

5.1 Enabling and Accessing Goal Import

Goal Import is turned on and off through Provisioning.

To turn on Goal Import go to Provisioning Edit Company Settings Goal Frameworks Goal Import .

The feature is accessed through Goal Management in the Administration Tools.

Implementing Goal Management

Goal Import © 2014 SAP AG or an SAP affiliate company. All rights reserved. 61
The link to the goal import feature is controlled using the administrative privileges permissions (meaning you
either get both or you get neither).

The first thing you need to do is generate CSV template for the goal import. Select the goal plan you want to
update and click Generate CSV Header. Save the CSV file to your machine.

Implementing Goal Management

62 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Goal Import
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).

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 OBJECTIVE

will be taken on. Valid options are:

Implementing Goal Management

Goal Import © 2014 SAP AG or an SAP affiliate company. All rights reserved. 63
Column Description Example

OBJECTIVE, TASK, MILESTONE,

TARGET, METRICLOOKUP, OB­
JCOMMENT. Values are case sensi­
tive.

ACTION The action to take on the item iden­ ADD

tified in TYPE. Valid options are:
ADD, UPDATE, DELETE. Values are
case sensitive.

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

only be created by the SuccessFac­
tors 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 specific goal. The
future goal export feature will auto­
matically retrieve each goals' ID
when a goal is exported.

GUID Required. This is a unique code that Imp123

the import creator added to the im­
port 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 employees
in both the engineering and sales
department. At a later date and
time, all these goals can be updated
by one import file line by specifying
an action and the GUID.

SUBGUID This is a unique code used to Subimp123

uniquely identify a row in a tablefield
(TASK, MILESTONE, TARGET, MET­
RICLOOKUP). 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 em­ msmith; cgrant

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

Implementing Goal Management

64 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Goal Import
 Column Description Example

FILTER_MGR_ID This field is not currently supported.

A placeholder for future functional­
ity.

FILTER_DEPT This field is filtered against the em­ sales

ployee DEPARTMENT field. Used to
determine which users to great the
goal for.

FILTER_DIV This field is filtered against the em­ EMEA

ployee DIVISION field. Used to de­
termine which users to great the
goal for.

FILTER_LOC This field is filtered against the em­ Paris

ployee LOCATION field. Used to de­
termine which users to great the
goal for.

FILTER_CUSTxx This field is filtered against the em­ Any text here
ployee CUSTOMXX field. NOTE:
only a max of three custom fields
can be used to filter goal actions.
Custom fields must be defined in
the data model under <custom-fil­
ters>. Used to determine which
users to great 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:

Column Description Example

OBJECTIVE_CATEGORY Category ID as defined in the goal Financial

plan XML

OBJECTIVE_PARENTID Used to manage goal alignment. 3364

This is the internal goal ID for the
goal to be aligned up to.

OBJECTIVE_PUBLIC Define if the goal will be public or Y

private. Accepted values are (Y / N)
or (1 / 0)

OBJECTIVE_name Maps to field-definition id="name". Increase Services Revenue per Ac­

count

OBJECTIVE_metric Maps to field-definition id="metric" Service Revenue per Account

Implementing Goal Management

Goal Import © 2014 SAP AG or an SAP affiliate company. All rights reserved. 65
Column Description Example

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".

Accepts the enum value.

OBJCOMMENT_comments Maps to field-definition id=" com­

ments". Goal comments are added
as a separate row in the CSV file
with a ^TYPE of OBJCOMMENT.

OBJECTIVE_actual-achievement Maps to field-definition id=" actual- 500

achievement". 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

table. Sub-goal tables require a sep­
arate row in the CSV file.

TARGET_target Target column of the Target sub-

goal table.

TARGET_actual Actual column of the Target sub-

goal table.

OBJECTIVE_NUMERIC_MET­ This column appears when a goal Y

RIC_LOOKUP_TABLE plan is configured with both ach­
ievement and achievement-text. Ac­
cepted values are Y / N or 1 / 0. A
positive value (Y, 1) represents the
goal uses the achievement column
and field.

OBJECTIVE_link Represents the URL field supported [[http://www.successfactors.com]

in a goal plan. Row value format is: [Click here]]
[[URL][Label]]

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

Implementing Goal Management

66 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Goal Import
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 TEMPLATE

row type. For template associations,
should always be "TEMPLATE".

Owner ID Key Any one of the available owner ID USER_ID

types: USER_ID, USER_NAME,
DEPT_NAME, DIVISION_NAME,
JOB_CODE, LOCATION_NAME,
CUSTOM01, CUSTOM02, or CUS­
TOM03. Note: USERID can be used
in place of USER_ID.

Owner ID Value The value corresponding to user1234

the key types specified in column 2.

Plan ID The goal plan template ID to asso­ 1

ciate with the user(s) described in
the owner ID key/value pair. Typi­
cally a number: 1, 2, 3, etc.

Action ADD (to establish the template as­ ADD

sociation for the user(s)) or RE­
MOVE (to remove 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.

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.

Implementing Goal Management

Goal Import © 2014 SAP AG or an SAP affiliate company. All rights reserved. 67
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. This is an optional field that is used
when the import file needs to update an objective or sub-objective 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.

● 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 say
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.

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). Example 3: An update action has
identified a GUID but no filters - All goals with the GUID will be updated. Example 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.

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.

Implementing Goal Management

68 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Goal Import
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.

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 and 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.

Implementing Goal Management

Goal Import © 2014 SAP AG or an SAP affiliate company. All rights reserved. 69
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 problem(s).

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

^TYPE ACTION ID GUID SUBGUID FILTER_USER­

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

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

Implementing Goal Management

70 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Goal Import
 METRICLOOKUP_achievement METRICLOOKUP_rating

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: 9

OBJ_PLAN_NAME: 1 Test Goal Plan

DATE: Mon Mar 02 11:04:13 MST 2009

MAX_ERROR

^TYPE ACTION ID GUID SUBGUID FILTER_USER­

NAME

OBJECTIVE ADD Goal301 cgrant

OBJCOMMENT ADD Goal301 cgrant

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.
The internal ID can be found under Reports > Classic Reporting > Goal Search. The column is Goal Id.

OBJ_PLAN_ID: 9

OBJ_PLAN_NAME: 1 Test Goal Plan

DATE: Mon Mar 02 11:04:13 MST 2009

Implementing Goal Management

Goal Import © 2014 SAP AG or an SAP affiliate company. All rights reserved. 71
MAX_ERROR

^TYPE ACTION ID GUID SUBGUID FILTER_USER­

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 (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.

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 sub-goal tables (Tasks, Targets, Milestones, Metric Lookup) you will need to goal's internal ID. When
defining the sub-goal rows, reference the internal goal ID of the goal the sub-goal rows should be added to.

Implementing Goal Management

72 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Goal Import
OBJ_PLAN_ID: 51

OBJ_PLAN_NAME: 2008 Goal Plan with everything

DATE: Thu Nov 06 17:25:41 PST 2008

MAX_ERROR

^TYPE ACTION ID GUID SUBGUID FILTER_USER­

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. Sub-
goal 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
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.

Implementing Goal Management

Goal Import © 2014 SAP AG or an SAP affiliate company. All rights reserved. 73
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 SuccessFactors Job Scheduler application.
5. The recommended maximum number of entries to update is 100,000. This could be 100,000 goals with no
sub-goals, or 10,000 goals each with 10 sub-goal entries (tasks, targets, milestones, metric lookup). This
could come in the form of one row in the CSV, or 100,000 rows in the CSV.
6. The new goal import does not support the filter option of job code
7. 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.
8. 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.
9. Custom fields to be used as filters must be defined in the data model under <custom-filters>.
10. 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.
11. 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.10 Limitations

1. The file size limit for beta goal import is 100,000 lines (as specified in the new goal import user guide)
2. MS.Excel 2007 has character limit of 255 per cell, so if you open a file in excel, ensure text based fields do not
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

Implementing Goal Management

74 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Goal Import
6 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.

6.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">
<field-label>Execution Actual</field-label>
<field-label lang="de_DE_SF">Tatsächlich</field-label>
<field-label lang="es_ES">Actual</field-label>

Implementing Goal Management

Enabling Goal Execution © 2014 SAP AG or an SAP affiliate company. All rights reserved. 75
 <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.

In a SMART goal, this should be the target value of the metric that is being measured. It can only be rolled-up to
the goal owner's plan as an AVERAGE, as their is no "sum" for Low, Med & High. (rollup-calc-type="avg")

Sample XML for Goal Plan Template (using a roll-up as a sum):

<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>

Implementing Goal Management

76 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Enabling Goal Execution
 <field-label lang="pt_BR">Situação</field-label>
<field-label lang="zh_CN"></field-label>

<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>

Configuration of this field is not supported in the Goal Execution product.

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>

Implementing Goal Management

Enabling Goal Execution © 2014 SAP AG or an SAP affiliate company. All rights reserved. 77
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 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>

Implementing Goal Management

78 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Enabling Goal Execution
6.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">

<field refid="bizx-target"/>

</column>

<column weight="1.0">

<field refid="bizx-pos"/>

</column>

<column weight="1.0">

<field refid="bizx-strategic"/>

</column>

6.3 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
both check boxes under this section.

Implementing Goal Management

Enabling Goal Execution © 2014 SAP AG or an SAP affiliate company. All rights reserved. 79
6.4 Admin Configuration

You need to make several changes in the Admin section to enable Goal Execution.

Permissions

Under Admin Company Settings Administrative Privileges you'll see a section called Manage Goal
Execution with four permissions.

● 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.

Implementing Goal Management

80 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 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 (re­
minder: 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 Re­
port. Recommendation is to use the start of the customer's fiscal year because we may
introduce enhancements 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
(days) is due. Status report due dates are calculated based on the Start Date and Interval val­
ues. 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
(days) due. Status report due dates are calculated based on the Start Date and Interval values.
You can set up to 1 reminder emails.

Implementing Goal Management

Enabling Goal Execution © 2014 SAP AG or an SAP affiliate company. All rights reserved. 81
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.

Implementing Goal Management

82 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Enabling Goal Execution
6.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.

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.

Implementing Goal Management

Enabling Goal Execution © 2014 SAP AG or an SAP affiliate company. All rights reserved. 83
6.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.
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.

Implementing Goal Management

84 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Enabling Goal Execution
7 Permissions
This chapter describes the permission settings in Goal Management and Execution.

7.1 Settings for SuccessFactors in the Home Menu

You can disable the display of the Goal Management entries in the Home menu.

There 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 permissioning, and can be done for all users by
default, or for specific users or groups of users.

7.1.1 Goal Management Module Permission (RBP)

How to control access to the Goal Management module with Role Based Permissions (RBP).

Prerequisites

You have role based permissions enabled in your instance:

Context

First carry out the following steps in Provisioning:

Procedure

1. Navigate to Edit Company Settings in Provisioning.

Implementing Goal Management

Permissions © 2014 SAP AG or an SAP affiliate company. All rights reserved. 85
2. At the bottom of the first section of configurations, click the check boxes for the applicable access
permissions: performance, goals, or both.

3. Click Save Feature at the top of the section to save the configurations. (This is all that needs to be done in
Provisioning.)
The next steps are performed in the Administration Tools:
4. In the Admin Tools, navigate to the Set User Permissions interface and click Manage Permission Roles.

Implementing Goal Management

86 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Permissions
5. Either create a new Permission Role by clicking Create New or navigate to the Role you want to edit by clicking
on the permission role link.

6. Under the User Permissions for Goals, make sure that none of the permissions are clicked. Save changes.

Implementing Goal Management

Permissions © 2014 SAP AG or an SAP affiliate company. All rights reserved. 87
7. Under the User Permissions for Performance, make sure that none of the permissions are checked. Save
changes.

Results

For a user in the Floor Workers group, which now has no permission to access Objectives (Goal Management) or
Performance, the Home menu now looks like this:

Implementing Goal Management

88 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Permissions
For a user who does have permission to access Objectives and Performance, the menu looks like this:

And the User Permissions interfaces look like this:

Implementing Goal Management

Permissions © 2014 SAP AG or an SAP affiliate company. All rights reserved. 89
And this:

Lastly, this permission can be set for all users in an instance by creating a new Permission Role that includes
everybody, and not assigning access permissions to that group. Creating a group that includes everyone looks like
this:

Implementing Goal Management

90 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Permissions
7.1.2 Goal Management Module Permission (Standard
Permissions)

How to control access to the Goal Management module (standard permission model).

Prerequisites

Role based permissions are not enabled in your instance:

Context

Carry out the following steps in Provisioning to enable Performance Management Access Permission and Goal
Management Access Permission:

Procedure

1. Navigate to the Edit company settings interface in Provisioning.

Implementing Goal Management

Permissions © 2014 SAP AG or an SAP affiliate company. All rights reserved. 91
2. At the bottom of the first section of configurations, click the check boxes for the applicable access
permissions: performance, goals, or both.
3. Click Save Feature at the top of the section to save the configurations. (This is all that needs to be done in
Provisioning.)
The next steps are performed in the Administration Tools for default user and admin user permissions.
4. If you want to set the default in the instance to have performance and/or goal management access disabled,
go to the "old" admin tools and select Default User Permissions.

Both Performance Management Access and Objective Management Access are disabled by default.

5. If you want to have the access disabled for a specific set of users (retroactively or proactively), you can
access an interface via the Manage Security group of tools.

Implementing Goal Management

92 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Permissions
6. Click Performance Management Access or Object Management Accessto go to the Admin Tools interface.

Implementing Goal Management

Permissions © 2014 SAP AG or an SAP affiliate company. All rights reserved. 93
7. Select group from the dropdown menus.
8. Choose either Grant Permission or Revoke Permission.

Results

Changes will take effect for applicable users immediately.

7.2 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.

Implementing Goal Management

94 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Permissions
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/denied permission to impact the goals of the employee, based upon the
configurations.

Table 21: 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 member'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

7.3 Action Permissions

The following table describes the action permissions that you can configure for Goal Management.

Table 22: 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.

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

Implementing Goal Management

Permissions © 2014 SAP AG or an SAP affiliate company. All rights reserved. 95
Action Description

will always allow the user who created the goal to de­
lete the goal for him or herself.

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 Se­
lected Public] and [Make Selected Private] buttons will
still appear when looking at goals in your own plan.
When you press the button, a Windows dialog box will
appear displaying a message that you do not have per­
mission to perform this operation.

Cascade Pull (cascade-pull) Define who has permission to cascade goals from an­
other user's goal plan into their own plan. Currently,
the only roles supported 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] but­
ton will not appear 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 with­
out matrix reports will not be able to select any
users, but they will still see the Cascade button.

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 individually but you would like to link
them for reporting purposes. If no roles are listed the
[Align To] button will not appear when you mouse un­
derneath 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 permis­
sion, 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 perform
this operation.

Implementing Goal Management

96 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Permissions
 Action Description

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 permis­
sion, 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 appear dis­
playing 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 include which table the permission ap­
plies 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 tables. To revoke cre­
ate row permission from all roles define the permission
with no roles listed. Roles not included in the permis­
sion definition will not have rights to create table rows.

Delete Row (delete-row) Define who has permission to delete rows in tables
(Tasks, Targets, Milestones, Achievement Lookup).
Definition must include which table the permission ap­
plies 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 tables. To revoke de­
lete row permission from all roles define the permis­
sion 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, Targets, Milestones, Achievement Lookup).
Definition must include which table the permission ap­
plies 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 permis­
sion with no roles listed. Roles not included in the per­
mission 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
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.

Implementing Goal Management

Permissions © 2014 SAP AG or an SAP affiliate company. All rights reserved. 97
 Note
A user with permission to add goals will automatically see a Save as New button on the goal edit page.

7.4 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/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:

Implementing Goal Management

98 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Permissions
Table 23: 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 withing 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 enclosed 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>

7.5 Cascader Role

You have the option to specify which goal details can become editable when an employee cascades a goal to
others.

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:

Implementing Goal Management

Permissions © 2014 SAP AG or an SAP affiliate company. All rights reserved. 99
 a. Field permissions (standard, custom, table) <field-permission>
b. Table column permissions <table-col>
c. Action permissions for tables <permission for=””>

a. Create (create-row)
b. Delete (delete-row)
c. 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.

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>
<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>

The following allows you to configure the following cascader settings:

1. Action permissions for tables <permission for=’’>

a. Create (create-row)
b. Delete (delete-row)
c. 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">
<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>

Implementing Goal Management

100 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Permissions
 <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>

7.6 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 some sample XML that can be added to your permissions section of a goal plan:

Example

<permission for="create-row">

Implementing Goal Management

Permissions © 2014 SAP AG or an SAP affiliate company. All rights reserved. 101
 <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>

7.7 Table Column Permissions

Table column permissions allow you to get more granular and define permissions for columns in the table.

Supported tables are: Tasks, Targets, Milestones, and Achievement Lookup. Listed below are some useful tips/
best practices to consider when using table column permissions.

1. If table column permissions are not defined, the columns will have the permission level of the table defined in
field permissions (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
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.

Implementing Goal Management

102 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Permissions
 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>

7.8 Requirements

1. All permissions are based on the premise, "WHO can take this action affecting the Employee's goals?" For
example:

○ 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. When comp
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.

The following matrix illustrates which roles can be assigned access to TGM features. Y = available N = not
available

Table 24: Role Permission Matrix

TGM *** E EM EMM EM+ ED EDD ED+ EMD EH F OP OC NO Sug­
Fea­ Role gest
ture ed
Role

View Y Y Y Y Y Y Y Y Y Y Y Y Y N E,
pri­ EM,
vate or
goals OP

Implementing Goal Management

Permissions © 2014 SAP AG or an SAP affiliate company. All rights reserved. 103
TGM *** E EM EMM EM+ ED EDD ED+ EMD EH F OP OC NO Sug­
Fea­ Role gest
ture ed
Role

Cre­ Y Y Y N N N N N N N Y N N N E,
ate EM,
Goal F
s

De­ Y Y Y Y Y Y Y Y Y N N Y N N E,
lete EM,
Goal or
s OP

Move N Y N N N N N N N N N N N Y E
Goal
s

Shar N Y Y Y Y Y Y Y Y Y N N N N E,
e/ EM
Un­
shar
e
Goal
s

Cas­ Y Y N N N N N N N N N N N Y ** or
cade OFF*
Pull

Cas­ Y Y Y Y Y Y Y Y Y N N N N Y ** or
cade OFF*
Push

Align Y Y Y Y Y Y Y Y Y Y N N N Y *, ED
To or ED
+

Un­ N Y N N N N N N N N N N N N E
align
Pa­
rent

Un­ N Y N N N N N N N N N N N N E
align
Child

Cre­ Y Y Y Y Y Y Y Y Y Y Y N N Y E,
ate EM
Row

De­ Y Y Y Y Y Y Y Y Y Y Y N N Y E,
lete EM
Row

Implementing Goal Management

104 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Permissions
 TGM *** E EM EMM EM+ ED EDD ED+ EMD EH F OP OC NO Sug­
Fea­ Role gest
ture ed
Role

Move Y Y Y Y Y Y Y Y Y Y Y N N Y E,
Row EM

The roles listed above are also used to set read and write permissions when accessing goals in an individual's goal
plan. The only exception is that even if OC is granted write permission, OC still cannot write to OP's goal (this
inconsistency has been filed as bug 1229).

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>
<role-name>E</role-name>
<role-name>EM</role-name></permission>
<permission for="cascade-pull">
<description Anyone may cascade a goal from anyone. </description>

Implementing Goal Management

Permissions © 2014 SAP AG or an SAP affiliate company. All rights reserved. 105
 <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.

7.9 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

Implementing Goal Management

106 © 2014 SAP AG or an SAP affiliate company. All rights reserved. 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>

7.10 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.

7.10.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 and the employee
could update only certain fields while the goal is Locked and update all fields / delete goals when it is in an
unlocked state.

Implementing Goal Management

Permissions © 2014 SAP AG or an SAP affiliate company. All rights reserved. 107
Configuration

All of this is configured in the Goal Plan itself as described below.

Note
Add the below configuration, after defining <field-definition> elements.

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">

Implementing Goal Management

108 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Permissions
 <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.
target-state: element specified inside "change-state" permission - 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>
\\

Note
Repeat the steps, if we need to configure the multiple objective plan states under </ obj-plan-states>
element.

7.10.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: This element is used to define the single goal plan state.

Implementing Goal Management

Permissions © 2014 SAP AG or an SAP affiliate company. All rights reserved. 109
● to-step: attribute 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.
● 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.

Implementing Goal Management

110 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Permissions
8 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.

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)”.

Context

This is how you set up the Admin Tools when RBP is disabled.

Procedure

1. Login as a super admin.

2. Go to 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.

Implementing Goal Management

Setting up the Goals Management Home Page Tile without RBP © 2014 SAP AG or an SAP affiliate company. All rights reserved. 111
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)”.

Context

This is how you set up the Admin Tools when RBP is enabled.

Procedure

1. Login as an admin who has permission to create a role.

2. 2.Go to the Admin Tools page.
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. Login as the user who has Manage Homepage permission - Go to Admin Tool Permission to Manage
Home Page .
8. Select a user to grant manage home page permission - Click Grant Permission.

Implementing Goal Management

112 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Setting up the Goals Management Home Page Tile without RBP
9 Accessing the Goal Management Tile
This section describes how to enable the goals tile on the home page.

1. Click the Admin Tools link.

2. Click Company Settings.Click the Manage v12 Home Page link.

3. Click Turn on Home Page.

4. Go back home page, then you will see revolution home page.
5. Click My Goal, you would see the active goal plan and the All Goals link.
6. Click on any goal plan name, and it would display all the goals for the selected goal plan.

You can also access all goals for all goal plans.

1. Click All Goals, it will display all goal for active goal plans.
2. The goals with alerts are displayed first and then goals without alert; they are ordered by ADDED alert,
MODIFIED alert, DELETED alert.
3. Click the goal with ADDED/MODIFIED alert, it will navigate to goal plan page, the alert will disappear; and the
goal will be automatically combined with other goals without alerts.
4. Click the delete icon in the goal with a DELETED alert, the goal and alert will disappear.

You can click the Tile Browser link on the new home page, the Tile Browser will pop up to allow users to add/
remove the GM tile.

Implementing Goal Management

Accessing the Goal Management Tile © 2014 SAP AG or an SAP affiliate company. All rights reserved. 113
 Note
The alerts on the goal homepage tile will be cleared when the goal plan is accessed from the tile, when the goal
plan is accessed via the top navigation menu, or when the goal details are viewed from the mobile goal product.

Implementing Goal Management

114 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Accessing the Goal Management Tile
10 Group Goals Overview
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).

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.
● No support of import for group goals - This is also not supported in group goals v1.
● 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

Implementing Goal Management

Group Goals Overview © 2014 SAP AG or an SAP affiliate company. All rights reserved. 115
Comparing the Different Versions of Group Goals

Feature Group Goal v1 Group Goal v2

Changes to fields by the owner can Yes Yes

be pushed down to members

Dynamic group goal membership Yes No

Group goal membership can be No Yes

modified 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 No Yes

group 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

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"

Implementing Goal Management

116 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Group Goals Overview
Admin

Once the provisioning switch is enabled for Group Goals 2.0, you will see a new set of permissions in the
application under Admin Manage Security Administrative Privileges Manage Goals . There are 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 the XML - you must allow group goals. Default is false, you need to make it true: allow-group-goal="true"

10.2 Using Group Goals

The following sections describe how an end user will use the new Group Goals 2.0 feature.

Create Group Goal

Creating a group goal still happens from the Create a New Goal button on a goal plan. The user will see an option
for Group Goal if they have permission to create a group goal.

Implementing Goal Management

Group Goals Overview © 2014 SAP AG or an SAP affiliate company. All rights reserved. 117
The creation of the group goal is a one step process (since assigning members to the group goal happens
separately). The group goal creation will only create the group goal with all the supported fields.

Assign Group Goal

Assigning a group goal is done using the button located in the row of buttons on a goal plan.

First you select which group goal or group goals (you can assign multiple group goals at once) you want to assign
by checking the checkboxes to the left of the goal name, then you click Assign Selected.... This opens up a window
very similar to the cascade window where you can choose who to assign this group goal to. A new supported
feature here though is step two of the assign wizard. The assigner will have an opportunity to change the group
goal before assigning it. The assigner will be able to edit any field that is not configured as a read-only field in the
group goal.

10.3 Configuring Editable Fields

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"

Implementing Goal Management

118 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Group Goals Overview
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".

Example
Weight should be editable by everyone 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>

Field Permissions

● When a field is set to "push-down", this field will be editable by group goal owners and read only to group goal
members 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.

Implementing Goal Management

Group Goals Overview © 2014 SAP AG or an SAP affiliate company. All rights reserved. 119
11 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
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
● 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 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">

Implementing Goal Management

120 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Mapping of Goal Library Content to Goal Plans
 <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">
…

11.1 Enhancing the Goal Library

You can enhance the goal library to support defaults for all goal and sub-goal fields.

The goal library has several important features:

● A UI in admin to allow an administrator to manage the goal library entries.

● Support of the import/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.

Importing the Goal Library

It is possible to include any fields that the customer requires in the Goal library.

Note
It should be possible to include multiple languages and multiple libraries in the same import file.

There are the standard goal plan template fields (though goal library is not limited to standard fields):

● name
● desc
● start
● due
● done
● metric
● target-baseline
● category
● weight
● state
● comments
● goto-url
● bizx-actual
● bizx-target
● bizx-pos
● bizx-strategic

The table column fields include:

Implementing Goal Management

Mapping of Goal Library Content to Goal Plans © 2014 SAP AG or an SAP affiliate company. All rights reserved. 121
● 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)

Modifying the Goal Library

When modifying an existing goal library, the user has the option of viewing the goals in the library in terms of any
of the existing goal plans in the company instance. For example, if the goal plan has 10 fields and the goal library
only has 2 fields populated, then selecting that template will show 2 populated fields and 8 blank fields.

Implementing Goal Management

122 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Mapping of Goal Library Content to Goal Plans
Adding Library Goal to Goal Plan

You can select multiple libraries to add to a goal plan.

Related Information

Default SF Goal Library

Sample Goal Library

Implementing Goal Management

Mapping of Goal Library Content to Goal Plans © 2014 SAP AG or an SAP affiliate company. All rights reserved. 123
12 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 show/quantify what a rating value actually means to the user in real world terms (meaning what does
it take to get a 5 out of 5).

12.1 Sample Use Case

Here is a sample use case for goals and rating with achievement lookup.

The employee is a sales rep and one of their goals is to generate $1 million dollars of revenue this year. If they
bring in $1m then they have met their goal and they get 3 out of 5 as a rating. If they bring in $1.25m they get a 4,
$1.5m a 5, $750K, 2, and $500K a 1.

The employee now knows the targets they need to achieve and where the different cut off points are. Let's say at
the end of the year the sales rep has generated $1.13m in revenue. Using the metric lookup table the system will
calculate 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. In this example the system will either calculate the goal rating to be 3
(step), or 3.52 (interpolate).

Features not yet included but which may be considered for future releases:

● Using calculated ratings in Group Goals

● Naming metric tables for re-use in multiple goals
● Option for the manager to "bump" the final rating up or down
● Supporting multiple actual results for a single goal through averaging, etc.
● Supporting both interpolation- & step-rated goals on the same goal plan.

Implementing Goal Management

124 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Creating Goals and Ratings with Achievement Lookup
12.2 Basic Metric Lookup

The basic metric lookup table and calculated goal rating consists of the following items:

1. Target Levels to achieve

2. Ratings associated to those Target Levels
3. A place to enter in the actual achieved value
4. The calculated rating that results from mapping the actual achievement in the metric lookup table.

Three types of fields are required to enable rating calculation:

● rating, type "number" - stores the rating calculated by comparing the actual-achievement with the target
achievement values.
● metric-lookup-table, type "table" – used to store the target achievement values
● actual-achievement (type number) or actual-achievement-text (type text), – used to store the achievement
value

Metric Lookup Table Display

The metric lookup table will always be in edit mode or display mode. To move back and forth between modes you
will need to click set scale or edit scale.

There are four columns that can be displayed with the calculated ratings table:

1. Column with ID achievement will always have a number data type and is optional
2. Column with ID achievement-text will always have a text data type and optional
3. Column with ID rating will always have a numberdata type and is mandatory.
4. Column with ID description will always have a textdata type and is optional.

A minimum of two columns are required but all four columns can be made available to employees. One column
must be the rating column and the second column is either the achievement or the achievement-text column.

Implementing Goal Management

Creating Goals and Ratings with Achievement Lookup © 2014 SAP AG or an SAP affiliate company. All rights reserved. 125
There are several additional configuration options that go above and beyond this. These configuration options are
described below. It is important to know that configuration for the metric lookup table (like all other goal
configuration today) applies at the goal plan level and not at the goal level. This does not mean every goal in a goal
plan needs to have a calculated rating, but it does mean that you can't have one goal calculate a rating using step
and another goal calculated using interpolation.

12.3 Calculation Types

The goal plan can be configured with one of two calculation types, Step or Interpolation.

This configuration is defined in the field-definition for metric lookup table. Accepted values are step or
interpolate.

<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">

Interpolation – When the rating is interpolated from the target values above and below the actual achievement.
(NOTE: Interpolation does not work with text achievement. If the calculated ratings feature is configured to use
interpolation and the employee enters character based values, a step based calculate will be performed.)

Example
Interpolated Rating Example

Table 25: Target Rating Table

Target Rating

20 1

30 2

40 3

50 4

70 5

Table 26: Actual Achievement Calculations

Target Rating

20 1

25 1.5

55 4.25

80 5

Implementing Goal Management

126 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Creating Goals and Ratings with Achievement Lookup
Interpolation

When the rating is interpolated from the target values above and below the actual achievement. (NOTE:
Interpolation does not work with text achievement. If the calculated ratings feature is configured to use
interpolation and the employee enters character based values, a step based calculate will be performed.)

Example
Interpolated Rating Example

Table 27: Target Rating Table

Target Rating

20 1

30 2

40 3

50 4

70 5

Table 28: Actual Achievement Calculations

Target Rating

20 1

25 1.5

55 4.25

80 5

Step

When the target achievement values are treated as thresholds and the amount by which the actual achievement
exceeds them does not matter.

Example
Step Rating Example

Table 29: Target Rating Table

Target Rating

20 1

30 2

40 3

50 4

Implementing Goal Management

Creating Goals and Ratings with Achievement Lookup © 2014 SAP AG or an SAP affiliate company. All rights reserved. 127
 Target Rating

70 5

Table 30: Actual Achievement Calculations

Target Rating

20 1

25 1

55 4

80 5

12.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:

Table 31: Target Rating Table

Target Rating

20 1

30 2

40 3

50 4

70 5

● Upper Bound: The system will always give the highest rating value when the actual achievement is above the
highest target level. An actual rating of 71 will give 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 above 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 above and actual achievement of 18 would result in a rating of 0.

Note
There's more complexity to this attribute than may first appear. 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 has to change to 0-5 (what's a 0 in a 1-5 rating?). Why is this important? This could cause
confusion for customers when it comes time to normalize ratings on a PM form. Let's say the customer has a

Implementing Goal Management

128 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Creating Goals and Ratings with Achievement Lookup
 goal plan and there are two goals on it. One goal has a rating of 1 with a scale of 1-5 and the other goal has a
rating of 0 with a scale of 0-5. If the PM form has a rating scale of 1-5, then both goals will be treated as a 1. If
the attribute is set to false, it is recommended that all rating scales also have a 0 entry.

12.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
(similar to how rating scales are configured under Admin in the application). 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:

● Numeric – Only shows the numeric value

● Text – Only the description is displayed
● Number - Text – Both numeric value and description are displayed

This configuration is controlled through the display attribute on the rating field definition. Accepted values are:
(number | number-text | text). Interpolation calculation type will always display numeric only regardless of the
configuration option. The calculated goal rating will display on a PM form however it was configured in the goal
plan. The rating will appear the same way it does on the goal plan as it does on the PM 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>

Implementing Goal Management

Creating Goals and Ratings with Achievement Lookup © 2014 SAP AG or an SAP affiliate company. All rights reserved. 129
Column Ordering

This 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 will
check and require 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 | both).

<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. This is because some achievements should result in a better rating as the achievement
decreases (think number of errors per 1000. Fewer defects is good and therefore should result in a better rating.)

12.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.

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.

Implementing Goal Management

130 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Creating Goals and Ratings with Achievement Lookup
 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.

12.7 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" default="true">

<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>
</mapping>
<mapping baseline-percent="110" rating="120">
<mapping-description>Good</mapping-description>
</mapping>

Implementing Goal Management

Creating Goals and Ratings with Achievement Lookup © 2014 SAP AG or an SAP affiliate company. All rights reserved. 131
 <mapping baseline-percent="120" rating="140">
<mapping-description>Best</mapping-description>
</mapping>
</metric-lookup-table-target-auto-population>

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.

12.8 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.

Implementing Goal Management

132 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Creating Goals and Ratings with Achievement Lookup
12.9 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 >

12.10 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.

Implementing Goal Management

Creating Goals and Ratings with Achievement Lookup © 2014 SAP AG or an SAP affiliate company. All rights reserved. 133
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, the calculated rating will be "0" if the value goes
below the minimum rating value. If the use-min-target-as-rating="true" then the minimum possible rating
value will always be the minimum rating. The example above shows use-min-target-as-rating="false". If use-
min-target-as-rating="true" then the actual achievement of 10 would show a calculated rating of 1.
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.

12.11 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 Example

<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>

Implementing Goal Management

134 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Creating Goals and Ratings with Achievement Lookup
12.12 Auto-Create Target Entries for Metric (Achievement)
Lookup

This feature enables the system to auto-calculate the different levels of target achievement based on the levels of
percent achievement that will be paid out for.

Goals can have a direct or inverse correlation of achievement to percent payout (thus supporting sales and
savings based goals).

Through appropriate configuration of the goal plan, a user can now select a merit guideline (a rule which defines
scores based on % achievement of target along with a textual descriptor) and then enter 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 Pays140% of Bonus BEST

Implementing Goal Management

Creating Goals and Ratings with Achievement Lookup © 2014 SAP AG or an SAP affiliate company. All rights reserved. 135
So when I create my goal, and set the Target Baseline and Merit Guideline, the system automatically generates
the Achievement Levels as follows: Target Baseline = $50,000 (entered)

Note
This feature supports multiple "Merit Guidelines" in both ascending and descending scale formats and appears
to support both interpolated and step achievement lookups. Any automatically calculated level or score can be
overridden using the "edit scale" option displayed directly under the "Rating Scale" drop-down. As of B1009
100 maximum rows (prior limit was 5 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):

Implementing Goal Management

136 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Creating Goals and Ratings with Achievement Lookup
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">
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>

Implementing Goal Management

Creating Goals and Ratings with Achievement Lookup © 2014 SAP AG or an SAP affiliate company. All rights reserved. 137
13 Mass Upload for Assigning
This feature enables mass upload functionality for the assigning process.

This is accomplished using an excel spreadsheet 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, meaning if you have the
admin privilege, role permissions will be ignored (EM, EMM, EX, and so on). The exception to this will be that the
import will not allow the assignment of goals to an employee plan in a “locked” plan permission state.

13.1 Requirements & User Story

As a user or admin, I want to be able to mass upload goal and target assignments using an excel spreadsheet.

Users

1. User (with Group Goal Assignment permission to access button from Goal Plan)
The Assigner gets admin privileges when they are given “Add Group Goal Assignment” permission granted
through Administrative Privileges. This is accomplished in the Manage Goals configuration. Any check box
selection from this section means that the user has some level of Manage Goals privileges. It should be noted
that based on label configurations, this section may look different to different companies.

2. Admin (with access to Goal Import)

Prerequisites

● Goal Import is enabled in provisioning

● User must have the Group Goal Assignment user permission given to them in the Admin interface

Basics Flow: Admin Access

1. Admin accesses Goal Import feature from Admin interface

Implementing Goal Management

138 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Mass Upload for Assigning
2. User (with appropriate access) clicks Mass Goal Assign from goal plan.

13.2 Accessing Mass Assign Button

This section describes how you can access the mass assign button.

Procedure

1. Admins can access feature from existing Goal Import functionality.

2. The Mass Assign button is located on the assigner goal plan.

Implementing Goal Management

Mass Upload for Assigning © 2014 SAP AG or an SAP affiliate company. All rights reserved. 139
3. The Mass Assign button is a push feature, meaning it will not require any additional configuration to activatein
addition to the Assign admin privileges mentioned above.
4. The label within the Mass Assign button is localized (translated into other languages).
5. Clicking Mass Assign causes the Mass Import button to appear.

13.3 CSV Header Template

The section describes how you can use the CSV header template.

Procedure

1. The CSV Header template is accessed by clicking on the download button in the Goal Plan.

Implementing Goal Management

140 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Mass Upload for Assigning
2. The CSV Header template button appears in addition to the Mass Assign button when the “Add Group
Objective Assignment” permission granted through Administrative Privileges.
3. We leveraged the existing Goal Import tool for this solution. The change we made is to add an additional
action option of assign. The headers are generated based on the plan template. The following is a sample of
what it looks like, with the assign action field populated.

4. 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.
5. You can have an individual row for each FILTER_USERNAME if needed
6. You can have an individual row each Target for each user if needed
7. Fields can be populated to be included in the assignment based on 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)
8. 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 will depend on the configuration of the form as to whether a field is a
push down field (that the assigner cannot modify) or a field that the assigner can modify (like the weight field).
If a field is populated for a push down field that the assigner does not have access to, then the system will
ignore that value (as opposed to showing up as an error in the job run e-mail).
9. The assignment of new group goals allows you to make assignments to inactive users.
10. The file does not have an explicit row limitation; however there is a 5 MB size limitation/recommendation for
the CSV file.

13.4 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).
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:

Implementing Goal Management

Mass Upload for Assigning © 2014 SAP AG or an SAP affiliate company. All rights reserved. 141
 ○ 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.

13.5 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).

Implementing Goal Management

142 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Mass Upload for Assigning
14 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

● View all personal goals description and details
● View and Update Status related fields (percentage complete, state/status, BizX target/actual)
● Manager Access

What is Not Currently Supported

● Add Goal
● Edit Goal
● Cascade/Align Goals
● Goal Tables (Target, Task, Milestone)
● Metric Look-up Tables •Group Goals (1.0 or 2.0)
● Goal Plan State/Workflow functionality (lock/unlock plans)
● Goal Execution

14.1 Enabling Mobile in Provisioning and Admin Tools

This section describes how to enable Mobile Goals.

Prerequisites in Provisioning

1. Check Enable Goal Management on Mobile and Enable Native Mobile Access.

2. Enable TGM modules:

○ Goal Management Suite

○ My Goals Tab - For V10 and Ultra — requires “Total Goal Management”

Implementing Goal Management

Mobile Goals © 2014 SAP AG or an SAP affiliate company. All rights reserved. 143
Admin Tools

When RBP is disabled go to Admin Tools Manage Security Permission to Access Mobile . Here you will
grant Mobile Goal/Objective permission for user/group.

When RBP is enabled go to Admin Tools Manage Security Manage Permission Roles General User
Permission . Here you will check Mobile Goal Access for a specific role or group.

14.2 Installing SuccessFactors HCM Mobile

This section describes how to install SuccessFactors HCM Mobile in iOS.

1. 1.Download from App store.

2. During the installation, select SuccessFactors in step 2, which will allow the code to be displayed in step 3.
3. Login to the web application Options Mobile , add a new device, type the code in last step and click
Save, to activate the user on the mobile device.
4. Go to the mobile device and tap Done, the mobile device is activated successfully.

Implementing Goal Management

144 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Mobile Goals
 Note
To install on an iPad follow the same steps with iOS above.

14.3 Accessing Goals on Mobile Devices

Goal Plan Template

You must add <mobile-field-list> in goal plan template, either in XML or via Manage Templates.

Implementing Goal Management

Mobile Goals © 2014 SAP AG or an SAP affiliate company. All rights reserved. 145
The mobile-field-list fields are the status related fields that appear in the following location in the Mobile UI.

The following table shows the supported status related fields that can be configured into the mobile-field-list.

Implementing Goal Management

146 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Mobile Goals
 Name Field ID Typical Usage/Characteristics

Goal State state Typically presented as a drop down

list of values with colors to report
the goal state or status. It is used in
dashboard reports. Limited to 128
characters and often labeled "Sta­
tus."

Percent Complete done Displayed as a whole number with a

graphical progress bar.

Bizx-Actual bizx-actual In a SMART goal, this should be the

actual value of the metric. It can be
rolled up to the goal owner's plan as
a SUM or AVERAGE (rollup-calc-
type="sum" or "average")

Bizx-Target bizx-target In a SMART goal, this should be the

target value of the metric. It can be
rolled up to the goal owner's plan as
a SUM or AVERAGE (rollup-calc-
type="sum" or "average")

Bizx-POS bizx-pos "Probability of Success" An indica­

tor for a goal that a user can use to
project whether or not they will be
successful in accomplishing the
goal.

Bizx-Effort-Spent bizx-effort-spent This field is currently used only in

status reports in Goal Execution,
but will be supported in Mobile
Goals. It represents the effort the
goal owner has put into success.

1. Go to provisioning to import goal plan template.

2. Login to the web application to add goals for the goal plan.
3. Go to the mobile device, tap the Goals/Objectives icon on the Home screen, you will see goal list page.

Implementing Goal Management

Mobile Goals © 2014 SAP AG or an SAP affiliate company. All rights reserved. 147
 Implementing Goal Management
148 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Mobile Goals
Implementing Goal Management
Mobile Goals © 2014 SAP AG or an SAP affiliate company. All rights reserved. 149
My Team View

The manager can view his or her direct reports' goal plans and goals by choosing the My Team tab.

Implementing Goal Management

150 © 2014 SAP AG or an SAP affiliate company. All rights reserved. Mobile Goals
Implementing Goal Management
Mobile Goals © 2014 SAP AG or an SAP affiliate company. All rights reserved. 151
www.sap.com/contactsap

© 2014 SAP AG 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 AG.
The information contained herein may be changed without prior
notice.
Some software products marketed by SAP AG and its distributors
contain proprietary software components of other software
vendors. National product specifications may vary.
These materials are provided by SAP AG and its affiliated
companies ("SAP Group") for informational purposes only, without
representation or warranty of any kind, and SAP Group shall not be
liable for errors or omissions with respect to the materials. The only
warranties for SAP Group 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 AG in Germany and other countries.
Please see http://www.sap.com/corporate-en/legal/copyright/
index.epx for additional trademark information and notices.