A country-specific update to implement the ELMA5 file format of the EU sales list declaration for Germany is available in Microsoft Dynamics AX

To increase security, the German authorities made some changes to the law. From January 1, 2013, the EU sales list declaration must be submitted with an authentication. To comply with this change, an update that introduces the ELMA5 file format of the EU sales list declaration for Germany is available.

This update contains the following interface changes in the export dialog box:

• Remove the following existing fields:
  • Participant Number
  • Auditor
  • xml file
• Add the following new fields:
  • EU Sales List ID
  • Notification
    Note The following three notification types are involved: None, Notice and Revocation.
  • Text file
    Note The Create export file check box and the File name path field are included.

Naming conventions of the ELMA5 file

During the ELMA5 export process, the naming conventions of the file is an important part.
A successful upload only can be done by using a correct file name.
Therefore, you must follow the following rules to create a correct file name for the ELMA5 file.

File name formation for the transmitted files

The files that are transmitted by the sender must apply to the following naming convention:Notes

• The m5 means the ELMA5 file name.
• The zm means the ZM product description.
• The <sssssssssss> placeholder represents the source identifier (Senderkennung). This string is alphabetical and contains 11 digits.
  Note This string is from the BZSt number value that is assigned by ZIVIT during the initial registration.
• The <ppp> placeholder represents the transmission process ID (Übertragungsprozess ID). This string is alphanumeric and contains three digits.
  Note This string is defined by the sender. Both letters and numbers can be used.
• The <xxx> placeholder represents the supplier ID (Lieferanten ID). This string is alphanumeric and contains three digits.
  Note This string is defined by the sender. Both letters and numbers can be used.
• The v<xx> placeholder represents the data format version. Currently, the value is v01.
• * The z<yyyymmdd> placeholder represents the start of the reporting time period. For example, 20060401 means that the reporting time period start from the second quarter in 2006.
  Note The annual statements must be marked with z<yyyy1231>.
• * The j<yyddd> placeholder represents the desired processing sequence (Verarbeitungssequenz).
  Processing sequence = (reporting period) + Julian calendar (indication of the day of the year)
  
  • The "m" means the monthly processing reporting period.
  • The "j" means the annual processing reporting period.
  • The "q" means the quarterly processing reporting period.
  Note The Julian calendar displays the year with two digits, and displays the day in the year without the month.
• The <c> means IBM-850. The <e> means EBCDIC 273 or EBCDIC 1141.
• * The <x> placeholder represents the processing type. From a to k, the value represents the order of daily data supply for the delivery of several files that have the same date.
  For examples, "a" means the first submission, "b" means the second submission of the same file in the same day, and "c" means the third submission of the same file on the same day.
• The "." is the separation of prefix and suffix.
• The <f> placeholder represents the function type.
  "e" means the individual file transmission (Einzeldatei-Übertragung) type.
  "m" means the combined transmission (Massenübertragung) type.
  "sig" means the signature file.
• The <v> placeholder represents the processing type.
  "g" means the total stock (Gesamtbestand) type.
• * The <l> placeholder represents the processing run type.
  "t" means the test run type.
  "p" means the production run type.

The variables that are marked with "*" are a subject to change, as they show the reporting period that can change from monthly to quarterly. All other variables will not affect single ERP users.

Examples for the file name formation of transmitted files

Example 1

In this example,

• The bz123456789 string comes from the BZSt number value in the initial registration.
• The transmission process ID (Übertragungsprozess ID) is created as b01 for back-end 1.
• The supplier ID (Lieferanten ID) is I01.
• The reporting time period for the ZM starts from October 1, 2012, the first day of the fourth quarter.
• The processing is implemented from the January 5, 2013, the fifth day of the current year.
• This is the transmission for the first file.
• ".egt" means that this is a single file transmission for a test run.

Example 2

In this example,

• The source identification, BZ000056789, comes from the BZSt number value in the initial registration, and the activation for the ZM procedure was processed.
• The transmission process ID (Übertragungsprozess ID) is created as b01 for back-end 1.
• The supplier ID (Lieferanten ID) is I01.
• The reporting time period for the ZM starts from January 1, 2013, as a monthly reporting.
• The processing sequence should be implemented from March 25, 2013.
• This is the second file that is transmitted on the respective day.
• Data from different companies is transmitted in one joint file.
• This is a production run.

After the data follows the plausibility check, the data will be taken over into the operative systems of the BZSt.

Hotfix information

A supported hotfix is available from Microsoft. There is a "Hotfix download available" section at the top of this Knowledge Base article. If you are encountering an issue downloading, installing this hotfix, or have other technical support questions, contact your partner or, if enrolled in a support plan directly with Microsoft, you can contact technical support for Microsoft Dynamics and create a new support request. To do this, visit the following Microsoft website:

https://mbs.microsoft.com/support/newstart.aspx

You can also contact technical support for Microsoft Dynamics by phone using these links for country specific phone numbers. To do this, visit one of the following Microsoft websites:

Partners

https://mbs.microsoft.com/partnersource/support/

Customers

https://mbs.microsoft.com/customersource/support/information/SupportInformation/global_support_contacts_eng.htm

In special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to any additional support questions and issues that do not qualify for the specific update in question.