Perform migration

The first step is to configure the new version 1.1 and do the necessary programming in your development or test system. Since this is a new interface, the programming of the interface must be checked and adjusted. If necessary, convert the existing integration in the document flow to the new integration (see section Display in the document flow). In addition, it is necessary to adjust the configuration, because in some cases old configuration settings have been replaced by new ones and there is no automatic migration of the configuration. Therefore, match the configuration in your production system with the configurations now available in version 1.1. The following steps are required for the conversion of the production system:

AEB recommends that you run through this scenario once in the test system if possible.

• Before importing the transport for version 1.1, pause the job for synchronization execution (/AEB/AES_ET_SYNC or /AEB/AA_ET_SYNC reports).
• Run the /AEB/AES_ET_AR and /AEB/AA_ET_AR reports once.
• Check if there were any errors during the execution (/AEB/AALOGENTRIES or /AEB/AESLOGENTRIES transactions).
• Run the /AEB/AES_ET_CLE and /AEB/AA_ET_CLEARING reports once.
• Check if there were any errors during the execution (/AEB/AALOGENTRIES or /AEB/AESLOGENTRIES transactions).
• Deactivate all created jobs for the reports /AEB/AA_ET_CLEARING and /AEB/AA_ET_AR.
• Import version 1.1 and additionally the configuration and the necessary adjustments.
• Make sure the following reports are (re)scheduled:
• /AEB/AES_ET_SYNC
• /AEB/AES_ET_AR
• /AEB/AES_ET_CLE

The reports starting with "/AEB/AA" are no longer needed.

Customs declarations that were created via the old interface are no longer synchronized to the host system. For these, printing or archiving must be carried out manually.

The migration is then completed.

Customs declarations can generally still be transferred during the migration.