SAP Knowledge Base Article - Public

2072251 - Manage Templates - Table fields, Subgoals, Notes, Milestones, Targets - Goal Management


  • Can I add a table to my goal plan fields?
  • What are the formats available for table fields?
  • Can I add/remove columns?
  • Can I permission who can control tables?


  • Goal Management


Table fields

  • Special fields of type "table" are supported in goal plans. The table fields that are supported are: Tasks, Milestones, Targets, and Achievement Lookup.


What is a Table Field?

A table field as a collection of fields that can be repeated for each goal. For example each goal may have several Tasks or Milestones associated with it.

  • Table can be renamed. For example, you can relabel the "tasks" 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 n which the fields will display in the UI.
  • Columns can be arranged in any order.
  • You can remove columns from the table structure if you do not want all the task attributes that you see listed.
  • The column types must match those in the table above.
  • Text columns have a character limit of 2048 characters.
  • The date and percentage columns cannot be transformed to text fields.
  • You can change the values in the label or description tags but you must not change the ids that are referenced as these ids are recognized by the application.

table-row-label Displayed in the UI. The word "Add" is always prepended 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-description, type attribute defining its type; and optional required and a default-value attributes similar to a field-definition. These additional attributes are also supported for the table-column id element:

width The width attribute specifies the width of the column in characters. It should be specified for columns of type "text" and "textarea" to provide enough space anticipated user input. For all other column types, width is ignored.
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", "percent", or "number", the value is specified in a non-localized format, and the lang attribute is not allowed.
  • For "enum" fields, the contents must be "value" attribute of one of the enum-value elements.
  • For "date" attributes, the format is MM/DD/YYYY.
  • For "percent" the value is an unformatted number (no "%" sign).


In all cases, if the value is not required, an empty default-value tag specifies the initial value of the field is empty.
field-format The field-format defines the format of a field or column. Currently, it is only implemented for the number type as follows:
#.00 number with 2 decimals

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


Goal Plan Table Field Permissions

 A couple of new permission tags have been added to enhance the ability to control who can create, modify, or delete rows of a table within a goal plan.   Here is some sample XML that can be added you your permissions section of a goal plan:

<permission for="create-row">
      <description><![CDATA[ Anyone can create row.]]></description>
            <field refid="targets"/>
            <field refid="tasks"/>
            <field refid="milestones"/>
            <field refid="metric-lookup-table"/>
   <permission for="delete-row">
      <description><![CDATA[Anyone can delete row.]]></description>
            <field refid="targets"/>
            <field refid="tasks"/>
            <field refid="milestones"/>
            <field refid="metric-lookup-table"/>
   <permission for="move-row">
      <description><![CDATA[Anyone can move row.]]></description>
            <field refid="targets"/>
            <field refid="tasks"/>
            <field refid="milestones"/>
            <field refid="metric-lookup-table"/>


Goal Achievement Table

  • You now have the option to let your employees automatically populate the Goal Achievement table with the correct target increments. To do so, contact SuccessFactors Customer Success to have your Goal Plan template updated. Once the tables are set, new Goal Plans will see an Autopopulate Achievement Lookup button. (TGM-2150)
  • For more information on lookup tables please refer to   - Metric Lookup Tables Custom Calculations for Goal Score and   - Metric Lookup Tables

The SuccessFactors Application does support custom calculations for sub-goals (tasks and milestones) such as:
•Calculated sub-goal rating
•Calculate sub-goal score (rating x weight)
•Roll up sub-goal scores to the goal level rating


KBA , LOD-SF-GM-TMP , GM Template Management , How To


SAP SuccessFactors HCM Core all versions