2266866 - Importing Development Goals (Development Objectives)

• This KB article explains how to import Development Goals
• What should I fill for each column in the Import File?
• Is the Development Goal import the same as a Goal import?

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

SAP SuccessFactors Career Development Plan

• This KB article provides a general understanding of the Development Goals Import and provide step-by-step instructions on performing such.
• Refer to the attached CSV Import File to easily review how to fill each field in the Development Goals Import.
• Development Goals can be imported with the Import Development Objective option under Admin Center > Development > Import Development Goals

Performing a Development Goals Import

1. First, you should obtain the Development Goals Import template for the Development Plan Template to which you would like to import Development Goals. You can find the Development Goals Import Template by going to “Admin Tools” > “Development” > “Import Development Goals”.
2. Then, you should select the desired Development Goals Template in the templates list dropdown, click “Generate CSV Header” and follow your browser’s instructions to download the template:

Fill the CSV Import File

See below a quick reference on how to fill each column of the CSV Import File:

• ^TYPE – you should fill this column with “OBJECTIVE”;
• ACTION – supported actions are “ADD”, “UPDATE”, “DELETE”;
• ID – fill with Development Goal ID. You should either use ID or GUID field. In case ID is provided, GUID will be ignored. Please note that you should only fill the ID if you are updating an existing goal. If you're creating new goals, you should leave the field blank and the system will automatically assign a new value.
• SUBID – Not applicable;
• GUID – fill it with GUID external identifier of choice. This is a unique code that the import creator added to the import file to update or delete goals at a later date and time. The code will group one or more goals into one action. Example, an import file is used to push a goal to all 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. The field accepts alphanumerical values. This Value has to be Unique in the system.

Note: if you are updating a manually added goal, for example with a Learning Activity, you can use the 'Development ID' instead of the GUID as manually added goals do not have a GUID.

• SUBGUID – Not applicable;
• FILTER_USERNAME – username for whom you would like to add the Development Goal.
• FILTER_MGR_ID - UserID of the manager of the employees for whom you would like to add the Development Goal.
• FILTER_DEPT - Department of the employees for whom you would like to add the Development Goal.
• FILTER_DIV - Division of the employees for whom you would like to add the Development Goal.
• FILTER_JOBCODE - Job Code of the employees for whom you would like to add the Development Goal.
• FILTER_LOC - Location of the employees for whom you would like to add the Development Goal.

Note: The “FILTER_...” fields may differ depending on your instance configurations and can be used to mass assign Development Goals according to the filter options specified. By default, you should have FILTER_USERNAME, FILTER_MGR_ID, FILTER_DEPT, FILTER_DIV, FILTER_JOBCODE and FILTER_LOC. But you may have additional custom fields as filter options, which can be configured in the Succession Data Model, in the section "custom-filters" within "default" module. For more information on how to configure custom filters, refer to KB article 2632183.

• OBJECTIVE_CATEGORY – Use " Goals " or if you have default categories then use those IDs
• OBJECTIVE_PARENTID – it should be left blank.
• OBJECTIVE_PUBLIC – “1” or “Y” if you would like the Development Goal to be public. “0” or “N” if you would like the Development Goal to be private.
• OBJECTIVE_name – should be filled with the desired Development Goal name.
• OBJECTIVE_... – other fields depend on the Development Plan Template. Please see below special considerations while completing information on the fields depending on their type:
• Text/Textarea – can be filled with any text.
• Enum – should be filled with the option values (field values) available in the dropdown options of the Development Plan Template (please note that the option values may differ from the option labels, depending on how the template was configured).
• Date – should be filled with a date with the format MM/DD/YYYY.
• Competency – you can fill it with multiple competency GUIDs and split the values by comma, for example, “7,8”, for the competencies to be associated with the objective. When updating or adding the development goal, you can leave the column as blank and the original association will not be updated or you can fill it with “NULL” to reset the association.
• Percent – should be filled with a percentage value (##.##).
• Number – should be filled with a number (supports Integer or Float values).
• Link – use the following format When importing URL values in that field: [[URL][Label]] - Note you need to use brackets [[]] like this and then replace the words "URL" or "Label" with what you want displayed.

Notes:

• Any fields that are required in the template need to be filled in.
• Enum fields (dropdown menus) configured with a space instead of alphanumerical will cause the import to fail.
• Importing links will only work with development goals. Importing to learning activities will display text and not a link.

Note on Importing Competencies: When importing Competencies to a Development Objective/ Goal, you should include the GUID of the Competency in the OBJECTIVE_competency column - on the same row as the Objective. If importing multiple competencies, then just separate them with a comma like this:

Import Developments Goals CSV File

1. Go to Admin Center > Development > Import Development Goals
2. In the Import Development Goals page, you should browser for the CSV file you would like to import and click “Import”
   Note: The limit for the total number of goals in a CSV file is up to 30,000. Please don't upload a CSV file containing more than 30,000 goals.
3. You will receive an e-mail upon completion informing the results of the Import Job.  

Example Import File

For more details on importing Development Goals, access the section "Importing Development Goals" of the Career Development Planning Implementation and Administration Guide.

Note: The Development Goal Import also supports importing Milestones and Tasks, if the Development Plan has been configured with those types of table fields. To import those field types, the TYPE column needs to be "TASK" or "MILESTONE".

In Provisioning, the Job name for all goal imports is called "TGM Data Import". It is the same job for GM and CDP goal imports

KB article 2632183 - Adding fields to the custom filters section of the Data Model

sf, success factors, CDP, SCM, Development Goal Import, Milestones, Tasks, Import Template, importing, objective , KBA , LOD-SF-CDP-DAT , Data Imports & Exports , How To