This page explains how to read the error log when the import of mobilities fails, how to correct the import file following the instructions of the error log and the most common error log messages. When importing a file, the system first checks if the file type is right, then it checks if the field format and content are correct and finally it checks against the business rules.

<div class="page-break-ruler"></div>

Example of business rules that must be respected:

• it is not allowed to have multiple organisations (different Organisation ID) with the same PIC
• the sending and receiving organisations cannot be the same
• the sending and receiving countries cannot be the same (depending on key action)
• the number of interruption or zero grant days cannot be greater than the duration
• the number of travel days must be 0, 1 or 2 (if applicable for the key action)
• the start date cannot be greater than the end date
• the start date cannot be before the project start date
• the end date cannot be after the project end date
• the duration of Student mobilities cannot be greater than 360 days
• the duration of Staff mobilities cannot be less than 2 days and more than 60 days
• the adjusted budget cannot be greater than the calculated budget 

In the following scenario, the import will fail 3 times.

<div class="page-break-ruler"></div>

Import fails due to incorrect file type

In the case where an incorrect file type (other than CSV or XLS) is selected to import, an error message will appear.

<div class="page-break-ruler"></div>

Import fails due to validation rule for cell format and content

The import will fail due to validation rules for cell format and content, such as:

1. Not using the allowed codes in place of field terms, as specified in the MT+ data dictionary. 
2. Mandatory fields are being left blank.
3. Not respecting the accepted decimal separator or date format.

<div class="page-break-ruler"></div>

Related Articles