SAP Knowledge Base Article - Public

2277994 - How to Import Data for MDF Objects/MDF picklists in SuccessFactors?

Symptom

  • Importing data for MDF objects
  • MDF picklist related import process
  • Error "The number of results loaded in this batch exceeded the limit"
  • What is the limit of records one can Import into an MDF object at once?
  • The total file size exceeds the user size limit of 100,000 kilobytes

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

Environment

  • SAP SuccessFactors HCM Core
  • Metadata Framework (MDF)

Resolution

Importing data to an MDF instance is a two-step process and both processes need to be carefully followed.

  1. Download the correct template for the object (parent or child as per your requirement). The template contains the structure of the object as is has been set up in MDF object definitions.
  2. Enter the data you want to Import into the template file. Both these operations use the same process s below:

To import data:

  1. On the Admin Center → Employee Files → Import and Export Data
  2. On the Import and Export Data page, select Download Template as the action to perform
  3. Select a Generic Object
  4. If you want the package to be generated as a zip file of all CSV files corresponding to the parent object and related child objects, choose Yes in the Include dependencies dropdown. An Import_Sequence.csv file is also generated, containing information such as the name of the file and the sequence in which the CSV files are to be imported (Do not change anything in this file)
  5. Click Download

    1.png
  6. Open the CSV file that is downloaded and enter the data that you want to import for the object
  7. Save your data

    2277994_2.PNG
  8. On the Import and Export Data page, select Import Data as the action to perform
  9. Select one of the following options:
  • For importing the CSV File, the following Import Data form appears. To validate the data before importing it, click Validate; otherwise, click Import

2.png

  • For importing the ZIP file, the following Import Data form appears. Choose the required file and click Import

    3.png


3.png


3.png

  • For Importing the from the Success Store, the following Import Data form appears. Select the required packages and click Import

4.png

  • Once done, you can view the results clicking in the View Results button that is presented in the right-bottom corner. It will redirect you directly to the Scheduled Job Manager page;
  • If there were errors, the job monitor generates error reports with error messages indicating why a particular record was not imported;
  • In the import of MDF Picklist values, the error messages are not on a record level, so you need to analyze the whole file to identify the errors;
  • Due to performance concerns, when there is any error on the import, the whole file is not updated. The import of MDF data is processed on batches and unless the file is entirely correct, no records will be imported;
  • An e-mail mentioning the status is also sent to the user logged-on user.

''

Important Note:

1) Since 1911 version, in case you get the error  “The number of results loaded in this batch exceeded the limit. Please go to Import Config and reduce the batch size of object ({0}) by half, then try again." => You will need to reduce the batch size in configuration and do the import again.

=> Select Import Config in the action to perform and insert the batch size (number of different records that will be imported (considering external code + effective date))

6.png

=>Do the import again. The error should not appear anymore

2) In case you're facing an error "The total file size exceeds the user size limit of 100,000 kilobytes",  note that it does not denote the size of attachment file or whole zip file. It actually denotes the space limit for the user/uploader performing the action. In this case,

For example: checked batch size is 100 for position object. Export all existing records for one position and see 1007 timeslices for it. Timeslices means the records with different effectiveStartDate. While importing a new record for position, system is not just loading one record in import file. All existing records will be loaded. Then system will handle 1000+ records. If one batch has 100 unique positions, average timeslice is 1000, handled amount will be 100*1000=100000. If the amount is more than 50000,validation "The number of results loaded in this batch exceeded the limit. Please go to Import Config and reduce the batch size of object (Position) by half. Then try again." will appear to avoid unexpected import errors.

It's expected behavior.

choose another user which has not surpassed the space limitation to do the import. Then the import should go smooth.

See Also

2277155 - How to Export Data for MDF Objects in SuccessFactors?

2442249 - Importing of MDF object file with special characters (Non-UTF-8 characters) is failing.

2447216 - MDF Attachment file extensions

2236017 - Mass Deletion of MDF Data via Import

2257047 - Adding attachments on an MDF Object for attachment type field via Import.

2516461 -  “Cannot locate corresponding object” error when trying to delete record.

==> Product Support, please see Internal Memo

Keywords

success factors, PLT, Metadata Framework, MDF, Import, Export, Import and Export Data, Object, MDF-29740, number of results loaded in this batch exceeded the limit, size, batch size MDF Import, mass deletion, mdf attachments, UTF-8, custom MDF object




, KBA , export data , LOD-SF-MDF-IMP , Import and Export Issues , How To

Product

SAP SuccessFactors HCM Suite all versions