Customs Management plug-in for SAP: Types of interfaces

AEB provides two different connections for SAP systems:

1. The “legacy” or direct interface:
   Here, the SAP system communicates directly with the ATLAS Export application in the AEB data center. The data for an export declaration is collected and enriched in SAP. There are several customizing settings for this (including the two collectors (invoice and shipment)). The shipments for this are provided by AEB under the version name Customs Management 1.0. In a consistency check and in the AEB Cockpit in SAP, the name Customs Management would appear, but you would also see the two entries Customs Management Export Filing: ATLAS and Customs Management Export Filing: e-dec.
   This integration was implemented for new implementations until the end of 2019.
2. The Customs Management interface:
   Here, the SAP system no longer communicates directly with the ATLAS Export application, but via the integration service in AEB Customs Management. In the case of a German export declaration, the data is forwarded to the ATLAS Export e-customs system. The data in SAP is no longer determined via customizing settings, but predominantly from the transaction data, enriched via a so-called BAdI. However, most fields of an export declaration are filled via templates in the ATLAS Export engine. The shipments for this are provided by AEB under the version name Customs Management 1.1. In the AEB Cockpit and the consistency check, you will only find the name Customs Management.
   This is the new connection of AEB for customs clearance since 2020.

In which SAP systems are the interfaces used?

• The Customs Management 1.0 version of the AEB plug-in can handle both the first and the second variant and is only available in SAP ECC.
• The Customs Management 1.1 version of the AEB plug-in can only handle the second variant and is available under both SAP ECC and SAP S/4HANA.

How can you tell what type of interface you are using?

If you run the consistency check (transaction code /n/AEB/CONSISTENCY), you will get the following results and can deduce from them the interface version you are using:

Customs Management 1.0:

• If version 1.0 is displayed for Customs Management and you find current entries with the reporting procedure "ATLAS" in the Customs Management Monitor (transaction code /ATLAS/AESETMON), then you are also using the legacy or direct interface with ATLAS Export.
• If version 1.0 is displayed for Customs Management and you find current entries in the ATLAS Export Monitor (transaction code /n/AEB/AAMONITOR), then you are also using the legacy or direct interface with ATLAS Export.
• If version 1.0 is displayed for Customs Management and you find current entries with the reporting procedure "EXPORT_DE" in the Customs Management Monitor (transaction code /AEB/AESETMON), then you are using the new integration, the Customs Management interface.

Customs Management 1.1:

• If version 1.1 is displayed for Customs Management, you are using the new integration, the Customs Management interface.

Are you still using the legacy or direct connection in an SAP ECC system? A changeover to the current Customs Management 1.1 connection is being carried out as part of a project to set up the integration service in AEB Customs Management and adapt the customizing in both SAP and the ATLAS Export engine. At the latest, this changeover must be addressed when switching to S/4HANA.