These instructions are relevant if you use the direct interface of the add-on for SAP for ATLAS Export. For more information, please see: Changes to the add-on for SAP® for ATLAS Export 3.0: setup and implementation.
All basic changes to the direct ATLAS interface were introduced with the November 2022 build. Additional configuration-related enhancements are scheduled for release with the February 2023 build.
- Independently of the changes and suggested actions described here, check which customs-related changes relating to AES ATLAS Export 3.0 have been communicated by the customs authorities. AEB cannot guarantee that the following is a complete and up-to-date list of issues.
Header: Changes and suggested actions
Field Technical field name | Change with version 3.0 | Suggested action |
Type of declaration TypeOfDeclarationCode | New code list A0121 from German customs authorities. Code field length extended from 2 to 8 characters. The field 'qualifier' is no longer used in AES 3.0. |
In most cases, you can still input entries such as 'AM+a’ the same as before under ATLAS 2.4. ATLAS Engine then automatically converts these entries to the new entries if the data allows. The entry 'AM+a' would be converted to the new code '00000100', for example. You can also input the new 8-digit code in the BAdI. |
Loading place All new fields starting with “PlaceOfLoad__” |
New fields for loading place data:
|
The new fields for the UN/LOCODE and GNSS coordinates are optional, offered by the German customs authorities as an alternative to the address entry available under 2.4. If no country is entered in the interface under the address, ATLAS Engine assigns DE by default. Exception: If customs is managed centrally, the country must be input in the interface. If presentation takes place outside of the customs office, the loading place can come from an authorization even if no authorization is indicated in the export declaration. In such cases, the authorization number must be entered in the loading place. |
CCL authorization number AuthNumberCCL |
New field for CCL authorization number (centralized customs) | Relevant when customs is centralized. |
Means of transport at departure MeansOfTransport Departures |
AES 2.4 already included a means of transport at departure. AES 3.0 now makes it possible to input up to nine means of transport. Both the identification type and the identification are required fields under AES 3.0. |
If data is entered in the fields previously introduced under AES 2.0 (starting with MOTDEPARTURE), the appropriate entry for Means of transport at departure is automatically populated in ATLAS Export. Any additional means of transport relevant for the customs declaration that are known in SAP can be added in the interface using a BAdI. For more information, see:
|
Means of transport at the border / type MOTBORDERTYPE |
This field was already available under AES 2.4. The possible values changed with AES 3.0. |
Adjust the entry under the rule of the invoice collector or transport collector if necessary. For more information, see Means of transport at the border – Identification (German) |
Presentation office customsOfficeOfPresentation |
Presentation office | Technically optional data field. Needed where relevant to in-house customs processes as in the case of centralized customs. |
Security security |
New field for the “Identification for the integral declaration of the data for the exit summary declaration.” Values from code list C0217. New required field under AES 3.0. |
This field can be left empty in the interface and will then be populated by the ATLAS Engine with the value "2" (EXS). This means that you will not generally need to input a different security code in the BAdI. |
Non-preferential exporter contractualPartner |
New fields for non-preferential exporter data. |
Defined under AES 2.4 using a coded document (3LLK). Must be specified separately under AES 3.0 using the new fields. If relevant for your customs processes, input from SAP via BadI. |
Terms of delivery termsOfDelivery |
New fields for the terms of delivery:
Note: You must enter either the UN/LOCODE or the combination city/country. |
The terms of delivery country is a required field under AES 3.0 if the UN/LOCODE is not used for identification. Since it is not possible to detect the country automatically, you must either enter this field using a BAdI or have it auto-populated using a template. With the feature pack (build) February 2023 a rule ist available in the billing or transport collector. For more details about the new rule, see Configuring country of delivery term in the add-on for SAP. |
Carrier carrier |
New fields for carrier data | If relevant for your customs processes, input from SAP via BadI.For more information, see Information on carrier (German). |
Consignor consignor |
New fields for consignor data | Technically optional data field. If relevant for your customs processes, input from SAP via BadI. |
Supply chain actors supplyChainActors |
New fields for supply chain actors data | Technically optional data field. If relevant for your customs processes, input from SAP via BadI. |
Transport document transportDocuments |
New header-level fields for transport document data: Type and reference number. See code list I0941. |
Example: “N730 truck waybill”. Technically optional data field. If relevant for your customs processes, input from SAP via BadI. |
Previous documents previousDocuments |
New header-level fields for previous document data. For values, see code list I0931. |
Technically optional data field. If relevant for your customs processes, input from SAP via BadI. |
Documents documents |
Documents can also be input at header level with AES 3.0. For values, see code list I0921. |
Technically optional data field. If relevant for your customs processes, input from SAP via BadI. |
Additional references additionalReferences |
New fields for indicating the additional references. For values, see code list I0911. |
Technically optional data field. If relevant for your customs processes, input from SAP via BadI. |
Additional information additionalInformations |
Additional information at the header level. Replaces the special facts ('specialFacts'). For values, see code list I0901. |
Technically optional data field. If relevant for your customs processes, input from SAP via BadI. |
Constellation of concerned parties constConParties |
The logic behind the possible values has been changed. 1st character: Non-preferential exporter 2nd character: Exporter 3rd character: Representative 4th character: Subcontractor The characters for the exporter, representative, and subcontractor have been shifted one place to the right. The character for the non-preferential exporter has been added to the front. The character for the holder OPR has been removed. |
The changes must be implemented in SAP: One option is to manually update the constellation of concerned parties in the configuration rule, which can be found in the invoice collector or transport collector. For instructions, see the next row below. Another option is to update the constellation of concerned parties through a BAdI, which you can do by going to the method BEFORE_STD_FILLING and changing the parameter CH_CONST_OF_CONC_PART. |
Instructions for manually updating the configuration rule:
|
||
Container isInContainer |
Container data is entered under transport equipment. | If container data is input at the header level, ATLAS Export generates a corresponding entry under Transport equipment. |
Authorisation no. VA authNumberVA |
This field is no longer used in AES 3.0. | No ToDo: ATLAS Export ignores any data input in the interface. |
Item: Changes and suggested actions
Field Technical field name | Change with version 3.0 | Suggested action |
Country of export countryOfExport |
New item-level field for the country of export. |
It’s generally sufficient if you indicate the country of export at the header level if this applies to the entire export transaction.
|
Consignor Consignor |
New fields for consignor data | Technically optional data field. If relevant for your customs processes, input from SAP via BadI. |
Supply chain actors supplyChainActors |
New fields for supply chain actors data | Technically optional data field. If relevant for your customs processes, input from SAP via BadI. |
Previous documents previousDocuments |
New item-level fields for previous document data. For values, see code list I0932. |
Technically optional data field. If relevant for your customs processes, input from SAP via BadI. Note: A different code list is used for the previous document data at the item level than at the header level, and there are the additional fields 'goodsItemNumber', 'quantity', and 'measurementUnitAndQualifier'. |
Documents documents |
Newly added fields:
|
If documents are input here that are to be entered under transportDocuments or additionalReferences under AES 3.0, ATLAS Export moves the entries into the appropriate data groups. The content has changed for BAFA licenses, EMCS administrative documents. and BLE export licenses:
|
Outward processing outwardProcessing |
New fields for outward processing data | Technically optional data field. If relevant for your customs processes, input from SAP via BadI. |
Additional references additionalReferences |
New fields for indicating the additional references. For values, see code list I0912. | Technically optional data field. If relevant for your customs processes, input from SAP via BadI. |
Additional information additionalInformations |
Additional information at the header level. Replaces the special facts (“specialFacts”). For values, see code list I0902. |
Technically optional data field. If relevant for your customs processes, input from SAP via BadI. |
Type of declaration alternativeTypOfDeclaration |
Type of declaration based on code list A0121. | Technically optional data field. If relevant for your customs processes, input from SAP via BadI. |
CUS number cusCode |
New field for the CUS number. Values from code list C0016. | Technically optional data field. If relevant for your customs processes, input from SAP via BadI. |
UN dangerous goods number dangerousGoods |
New fields for hazardous goods data. Code list C0101 for the UN dangerous goods number (UNDG). |
ATLAS Engine takes the entry in the previous field 'undgNumber' and applies it to the new structure. To specify multiple entries for one item, you must use a BAdI. |
Inward processing termination |
New fields for inward processing data. 'simplyGrantedAuthorisation': Indicates whether the authorization has been requested and granted on the basis of a customs declaration. 'customsOfficeOfSupervision': Office code of the customs office with oversight over the inward processing. Code list D0141. |
Technically optional data field. If relevant for your customs processes, input from SAP via BadI. |
Country of origin ctryNonPrefOriginISO |
Non-preferential country of origin. This field already existed under AES 2.4 but is now required under AES 3.0. |
ATLAS Engine sets the non-preferential country of origin to "DE” by default if nothing is input in the interface and the region of origin is Germany. With the February 2023 build of the add-on, the value is read from the EIPO-HERKL field. If empty, the value is determined via the material master from the MARC-HERKL field. |
Comments
Please sign in to leave a comment.