AEB provides two different connections for SAP systems:
- The connection with direct interface to Export Filing: ATLAS (also called "ATLAS Export Engine"). This integration was implemented for new installations until around the end of 2019. The following documentation refers exclusively to this integration.
- Connection via the Integration Service of Customs Management. For this type of integration, you will receive separate documentation for the conversion to ATLAS Export 3.0 at a later date
How can you tell what type of connection is being used?
Start the consistency check (transaction code /n/AEB/CONSISTENCY). If version 1.1 is displayed there for Customs Management, use the new integration. Then, the following information does not concern you.
In the following cases, the instructions are relevant for you:
- If the consistency check for Customs Management shows version 1.0 and you find current entries in the ATLAS Export Monitor (transaction code /n/AEB/AAMONITOR), then use the direct interface with ATLAS Export.
- 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 /AEB/AESETMON), also use the direct interface with ATLAS Export.
Options for testing: If you have a test system for Export Filing: ATLAS, you will be able to use this from the beginning of 2023. If you do not have a separate test system yet, AEB will provide you with a test system. In this case, contact AEB support.
Proceed as follows:
The following procedure is recommended for converting ATLAS Export to release 3.0 with the add-on for SAP®:
- Import the current status of build transports from AEB into the SAP systems for development and testing. For more information, see Current transports for the add-on for SAP®.
- Switch to version 3.0 of AES ATLAS Export in the SAP system for development and testing. The exact procedure is described in Activate conversion to version 3.0 in SAP.
- Evaluate the technical changes for relevance to your customs processes using the instructions in this document.
- Create SAP documents that cover your different business transactions and transfer them to the ATLAS Export test system.
- Check the transferred test data in ATLAS Export for completeness and correctness. If necessary, adjust the available settings accordingly.
- Are additional changes needed in the interface? If so, plan a corresponding adaptation (via BAdI) for your SAP development.
- After successful completion of the tests, transport all changes to the SAP production system.
Please note: This may be done no earlier than February 27, 2023.
Current transports for the add-on for SAP®
All essential changes to the direct ATLAS interface were made available with the November 2022 build. Further enhancements in the area of configuration are planned for delivery with the February 2023 build.
On the website Documentation & Downloads in the Download Center you will find after logging in the current transports for the Base system, Customs Management and other product-specific transports. Download and import them into the SAP system. For a detailed description of the procedure search in the Documentation Center.
Activate conversion to version 3.0 in SAP
To activate the transfer of data with version 3.0, proceed as follows:
- Start the transaction /n/AEB/AA_V_ATLVER.
- Select New entries.
- Select the desired target client in ATLAS Export for the changeover.
- Select the desired time for the changeover (date and time).
- Save the entries in a transport request.
- When the transport request is imported into the subsequent systems, the interface is set to version 3.0 according to the date and time set.
Other notes:
- Use templates to specify constant values: You can also maintain certain constant values via a template in ATLAS Export. The unique identifier of the template can be stored in the invoice / transport collector. Alternatively, the identifier of the template to be used can also be determined in the BAdI.
- ATLAS code lists: In ATLAS Export, you can access and search the customs code lists under Master data – ATLAS code lists. This overview can be helpful during testing to determine the values allowed under AES 3.0.