Information to the next release change on 22.07.2025

The next IMP release change is planned for the 22.07.2025. The new version 12.5.0 / ISS mainly includes internal changes:

• Change of interal status model and status message. With this change we create the prerequisite to no longer carry out consolidations in case of landside deliveries.
• Preprations for the migration of transshipment processes from the presentation notification in ZAPP to the Port Order/EMP. The implementation will be carried out step by step, probably from the 4. August.
• Prepration for the introduction of ATLAS WKS (re-export control system). The date for the commissioning in ZAPP /EMP is not yet been determined, but planned in 2025.

Important: After the release change status messages additionally include a container status besides the SumA status. We already provided information about this status message changes in newsletter 06/2024.

The new versions oft he status messages are downward compatible. If you use manifests, presentation notifications or the IMP Status Request you don’t need to carry out amendments. Your software must be able to overread the additional field for the container status.

Changeover from ATB to MRN in IMP

The MRN was assigned as leading reference for the summary declaration with ATLAS release 10.1. The ATB no. will nevertheless continued to be created and can be used for the follow-up procedures, likewise the MRN, until further notice. 

IMP changes the processing step by step. Probably from September onwards both, MRN and ATB will be transmitted and displayed, so you can decide on your own when you change your systems from ATB to MRN. We already published information concerning the status messages in the newsletter 06/2024.

The description of the IMP StatusRequest for the declarant will probably be updated in the third quarter.

Division of the manifest interface IFTMCS

We have often been approached with the request to separate the contents between the messages import, export and feeder transfer in the implementation manual more clearly. With the new version 2.0.0 we are glad to fulfil this request and created separated manuals for the three use cases.

The manuals can be found on our homepage or directly at https://www.dakosy.de/support/dokumentation-fuer-entwickler/schnittstellen-seehafen#c12173.

An additional information: the version of the inferface will be continued in a standardised manner, only during the generation we create separate manuals. The introductions and change histories in all documents are therefore identical. 

WKS: Amendments in IFTMCS

For the introduction of ATLAS/WKS two additional requirements emerged in the meantime, which we would like to point out here:

Dangerous goods: the current description already includes one DGS segment which could be sent as optional information so far. In the future it must be specified if the container includes dangerous goods. The UN number will then be transmitted in the ASumA. The EMP Port Order does not require  further dangerous goods specifications for now.As dangerous goods messages are sent separately to the terminals for transshipments, the message can be limited to the DGS segment with UN number and dangerous goods class in IMP. The limitiation applies subject to possible changes in the future, to be decided within the ZAPP/EMP working group.

Transport document: in the future at least one transport document and the respective document type must also be specified in the ASumA from ATLAS/WKS, similar to the preliminary paper N355 from ICS2. In many use cases the document type from the export side unfortunately was not transmitted, e.g. if OESUMA is specified as preliminary paper in the import.

An FTX segment on GID level has been implemented in the export and import manifest, to be able to send the transport document in the export. Generally the Bill of Lading and the respective document type is specified here. Further, comma separated transport documents can also be entered. Each entry must be specified in the  format „<Transportdocumenttype>=<Transportdocumentname>“.

Example:

FTX+AAZ++I0943+N704=XYBL12345678,N714=YZBL87654321'

The code list I0943 for the document type is published on the customs homepage under: https://www.eas.internetzollanmeldung.de/iia/action/invoke.do?id=CODELISTEN

The segment must be specified for transshipments depending on the different use cases:

Feeder – Ocean Carrier: Export manifest

Ocean Carrier – Feeder: Import manifest

We advise you to generally transmit the segment both in the import and the export manifest to guarantee a smooth processing. The IMP recognizes whether it needs to be read out, so you avoid possible error sources and delays in the transshipment process. 

The segment structure has been taken over from the BIP in order to continue guaranteeing a most possible standardised use of the IFTMCS in BIP and IMP. Further optional information in the ASumA will not be included  in the IMP descriptions, unlike in BIP.

The changes are included in the implementation manuals import and export IFTMCS 2.0.0 to be downloaded from our homepage under the following URL https://www.dakosy.de/support/dokumentation-fuer-entwickler/schnittstellen-seehafen#c12173.