Data Loader

In a Nutshell

The heart of the Master Data Management module is the Data Loader. With it, you can download master data templates for specific data objects and upload when completed, update or overwrite existing data, or download object data resources saved to the cloud. The Data Loader feature validates for errors, such as missing required fields and format inconsistencies.

When complete, this data will be used in all SAP Field Service Management applications, from Knowledge Management, to Workforce Management, to the mobile application used by employees and technicians.

As an example, let’s take an Activity.

In order to create a Activity, you would use the following information:

1 A Business Partner (customer) who recevies the service.
2 An Address where the service takes place.
3 A Person to whom to assign the service call.
4 A Contact with which the technician (person) can coordinate a service call.
5 Equipment to be repaired.

All of this information can be uploaded using the Data Loader and managed using the Master Data Management app.

Note: Data Object templates are available in CSV, XLS, and XLSX format. Data must be encoded in UTF-8.


Identifiers are the key, unique value for each data object record. They are used to form connections between various data object records.

For example, a Business Partner, Contact, Equipment record, and Activity could all be connected through the businessPartnerID with the the Business Partner. The businessPartnerID can be represented by the code or the name of the Business Partner.

The following is a example of how equipmentId and businessPartnerId connect business partners, projects, equipment, and activities:

ID Logic

Import Logic

When uploading data, the id column of your data will be stored as the externalid in the database. The application assigns its own, internal ID to the records.

Attention: When an externalId is uploaded, it may only be comprised of alphanumeric characters, underscores or hyphens.

Export Logic

When exporting the data, the externalID is displayed as the id and the internal ID of the record is not exported.

Update vs Create New Logic

Please note the following differences between the identification logic used to determine a record match when updating a record, and how IDs are assigned when creating a new record:

Update Existing Record Create New Record
When updating an existing record, the cloudID, code, and externalId are checked by the application to determine if a match exists. When creating a new record, the ID from the uploaded file template will become the externalId value in the cloud.

User-defined Fields

You can expand on data object templates by adding user-defined columns to the file. Upon successful upload and validation, these values will be available for the selected data object type.

UDF column names will use the following pattern:


With the user-defined field column name preceded by udf and a period (.) and followed by the data type in square brackets.

Valid Delimiters

Please note that _ (underscore) can be used to delimit UDF fields (example: example_udf_field).

However, dashes - are not supported and cannot be validated (example: example-udf-field).

CSV Format

CSV stands for “comma-separated values”, and is a flat format commonly used to exchange tabular data between programs, as most programs support CSV format for data import and export. CSV-formatted data is commonly used to transfer information from database programs that stores data in a proprietary format to a spreadsheets that use another format.

The following is an example of CSV-formatted tabular data:

Columns without data are still reprsented with a comma-dileneated break, as seen in the missing dateOfBirth field in the last entry in the above image.

Rules for formatting data in CSV

  • Column order can differ from that contained in the template, but record data must remain consistent.
  • Column names must align with those present in the templates.
  • Rows with missing column data must use a comma-delimited break.
  • The Data Loader currently only supports column separation using comma.

Using these rules, we could then represent CSV-formatted data as follows:

This would then be processed the same as the data contained in the first image.

Data Loader Templates

The Data Loader Templates are used to upload data managed in other systems to the SAP FSM Cloud for use in the Field Service Management applications. The fields contained in the template references correspond to the column names used in the SAP FSM Cloud Data Model.

The id columns may refer to:

  • the externalId property supported in version 4 of the Data API
  • the code property (generally specific to ERPs)
  • or to name property, or even to userName/emailAddress.

This column is used to connect data objects to one another. For example, a Contact record could specify the id of a Business Partner, which would then connect the Contact to the Business Partner.

Importing Data

Data can be imported using the Data Loader by navigating to Master Data Management > Settings > Data Loader.

For detailed information on importing data using the Data Loader: