Problems with FreeWheel import
Surrounding the FreeWheel import, multiple problems can be encountered:
- wrong financial values;
- a placement / package seems to exist twice;
- etc.
This article elaborates on the main cause of such issues and proposes a workflow in case of an error message.
The causes of the various symptoms can of course vary. However, the main reason for such problems is frequently related to the fact that it is often different people who create a placement in FreeWheel on the one hand, and ultimately settle it in MYDAS on the other. It is generally the case that a placement in the FreeWheel file corresponds to a package in MYDAS.
When the FreeWheel file is imported, an import log is generated in MYDAS. It should be checked whether there is an entry here that indicates an error or a nonexistent master data record in MYDAS.
If everything is OK according to the protocol, it should be compared with the original import file from the FreeWheel-SFTP-Server. In this file, the existence of corresponding packages with their values can be checked.

To find the cause of an error message, the corresponding data record from the FreeWheel file must thus be compared with the values of the MYDAS package. In MYDAS, the Placement-ID in the FreeWheel file (column 29 / Excel column AC) corresponds to the 'ExternalID' at package level.