Field help (SIMSIMFLG) 

Specify whether the migration must be launched in simulation mode (no recording is made) or not.

The simulation can be used for controls before performing the real update. As soon as there are no more blocking errors, the real migration can be launched.

If multiple tables are selected for the simulation, they may be interdependent and blocking error messages may occur.
For example, to migrate the "Customers" table in simulation, the "Payment terms" table must be migrated in real mode beforehand.

SEEINFO For these reasons, it is preferable to process each table in simulation one after the other. If no error are found, the real processing may be launched, before the simulation of the next table, etc.

SEEWARNING If the import is restarted, the transcoding must be redone and the setup revised. 

SEEWARNING Be careful regarding the dependencies with other tables which have been migrated. These manipulations must be carried out sparingly. Depending on the reimported items, the transcoding and potentially the setup must be revised.

SEEWARNING Be careful regarding the dependencies with other tables which have been migrated. These manipulations must be carried out sparingly. Depending on the reimported items, the transcoding and potentially the setup must be revised.

SEEINFO This is normal insofar as the Sage X3 entry counter used is not updated for real. The entry numbers assigned after migration can be read and retained only after a processing launched in real mode.

When the processing is performed for real, it is necessary to restore the folder before migration in the event of severe errors that would require modifying the data input.