Please note that the maintenance works/ release update, planned on 14.10.2020, have been postponed.

The changes and new functionalities announced in the newsletter 08/20 will be activated during the next maintenance works/ release update during the night to 11.11.2020.

Technical maintenance works on 18.10.2020

Due to technical maintenance works on 18.10.2020 during 6:00 p.m. until 8:00 p.m. no message interchange with ATLAS will take place in the realm of SumA. Incoming messages will be parked and automatically processed after the completion of the maintenance works.

The HHLA terminals are not affected. Likewise there are no affects on Transshipment declarations to ZAPP.  The announcement applies for the terminals:

• Eurogate
• Unikai
• Rhenus Midgard
• Wallmann

New terminal code FKZ

Due to organisational reasons IMP transforms the terminal code OSW at Unikai to the new terminal code FKZ (Frucht- und Kühlzentrum / fruit and refrigeration center), if the manifest was sent by one of the carriers Maersk (MAE2), Hamburg Süd (HSA) or MSC (BER). Status messages regarding each container will also be transmitted with the code FKZ.

Implementation of ATLAS error messages / new error code 901

At the moment there are some error messages around the SumA declarations which are reported back without any detailed error text, but with "unspecified error". These errors will be replaced step-by-step by understandable error texts.
In the first step this concerns the changes of the EORI or branch no. of the person lodging the presentation notification, which is not allowed in case of an existing ATB (error 901).

Update: Process description of the Transshipment in IMP

The description of the Transshipment process is now available in the current version 2.2. Substantial change is the elimination of the rule R6 which, under certain conditions, resulted in the fact that the ZAPP declaration could not be created. The problem was caused by routes with port of loading and country of destination in the EU and an intermediate stop outside the EU, e.g.:

• Poland             - loading port within the EU
• Marocco           - next port of discharge, there repositioning of the goods
• Spain               - country of destination within the EU

While attempting to create a B-number in the Transshipment process this combination triggered the error message „KENNZ SUMA EINGANG – BEFREIUNGSGRUND“. Since no MRN from an ICS declaration is available a S-number has to be created in such case. The rule R6 was eliminated in consultation with the customs (AG30), so as of now also the case described above can be declared automatically.

The process description can be reached at www.imp-hamburg.en under „Documentation / Documentation for end-user“ or directly via the Link.

MRN check in import manifest

In addition to the previous MRN check of an ICS declaration (Import Control System) the MRN number of positions, the first customs office of entry, the ETA of the first customs office of entry and the IMO no. will also be checked from now on. The preconditions for this is that the MRN was created via the product ZODIAK-ICS operated by DAKOSY. Only than the IMP can compare the data. If the MRN was not created via this applciation, the formal checks are carried out as usual. 

Following error codes must be used:

• 391: The specified customs office of entry does not match with the MRN
• 392: The specified ETA of the customs office of entry does not match with the MRN
• 393: The specified IMO no. does not match with the MRN
• 394: The MRN does not have as many positions as stated

The check service which was temporarily suspended has now been acitvated again to provide early information in case of error situations. At present such errors are only reported back with the confirmation of the ATB no. from ATLAS, while, in the future, they will already be checked during the incoming of the manifest in order to gain more time for the troubleshooting.

Due to organisational reasons this check will only be activated in the course of the 15.10.2020.