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.

Extension of CSV interface for import operation instructions (CSV upload)

The CSV interface for import operation instructions was extended by a mail address and five status.

The new fields are shown in bold in the following example:

You can still use the previous fields for the email notification. The new data fields provide more flexibility: up to five status codes per email address are freely selectable.

New version 1.5.6 of XML status message

The IMP status message status was extended in case of the messages 930 (early ATB) and 934 (ATB confirmed) on item level by the MRN of an possibly available summary declaration. This information can be used later, e.g. within the ZAPP declaration (declaration type MIT), in which both the ATB number as well as the MRN are mandatory information.

The new version will become operational in February 2021. The precise date will be provided in one of the following newsletters.

The message implementation guide can be found directly via:

Status Message (message description XML)

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).

New: Check for validity of EORI numbers

Occasionally, invalid or incorrect EORI numbers are transmitted. This leads to the fact that an ATB will not be confirmed or the summary exit declaration concerning the S-number will not be generated. 

In order to provide early warnings in the registration process, from now on the EORI numbers in the manifest data will be checked for validity by means of an EU web service. The check only applies for EORI numbers relevant for the processes in IMP:

• Shipper: NAC+CZ
• Consignee: NAD+CN
• Person authorized to dispose the import operation manifest: NAD+AG (only in import manifest)

If the web service is not available, the respective EORI will be accepted and processed as before.

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 11.11.2020.

New status code 776 = cancellation due to annulation

In case of an annulation/cancellation the ASUMA after the transfer, the S-number will also be cancelled and the new status "776 = cancellation due to annulation" will be sent.

Reporting back of BGM reference in case of ATLAS error messages

From now on the APERAK concerning error messages from ATLAS also includes the BGM reference.

The first message reference of the BL will always used.

This applies for the following message elements:

RFF+ANK

RFF+ACW

RFF+AGO