...
The content of the file DSN/ENIM export is based using the Annual Summary code maintenance configuration. Similar to how the Danish Statistics export is implemented.
This gives us a flexibility in setting up the export . Most as most of the information needed is available in payroll fields and can be added to the correct transaction fields and DSN export codes.
The following modifications are made in APM, one expanding the number of fields available in the entry code, annual reference tab. In the Annual Definition, there is an a sorting number to identify in what sequence the DSN "annual" codes need to be exported.
Example of a DSN annual codes:
S10.G00.00.001 | Name of software used | Nom du logiciel utilse |
S20.G00.07.003 | Contact mail address | Addresse mel du contact |
The relevant codes are added as annual summary codes like this:
The AS Code is an abbreviation of the block/topic id. However, the AS Code is max limited by 10 char, for the AS code . when adding the block and topic is we skip the 'G00' which is standard for all block ids. The tag field XML Tag field contains the complete block id which is used in the export file.
The block/Topic Ids are grouped as follows;Main main structure of the export file:
...
Header information
Exist out of static information like software used to produce the file, version numbers and Siren, NIC Number and address of the transmitter.
Employee information
The employee information
...
exists out of payroll related information that can be subtracted from the payroll transactions and information that are not directly related to payroll transactions. Like contract start and end date etc.
Footer Information
This is the summary of the number of persons reported in the export file.
To collect the none payroll related information we are captured on person level using addition entry codes specially used for the DSN export. These entry codes are a company created, meaning only once per payroll calculation period.
The various fields like DIM, Text and input fields are set using payroll scripts.
Based on the information received from SUPPORT-PILOTE-DSN <support-pilote-dsn@enim.eu> we have filtered out the block and topic id's required for ENIM.
This need to be confirmed with the customer. (PONANT)See excel spreadsheet: Eng-DSN - ENIM Monthly Export block and topic ids.xlsx
These codes are added when installing the DSN Plugin.
A full description of the block/topic ids you find in the chapter 8 of this document: https://adonisas.sharepoint.com/:w:/s/sp/development/EUc3SWCzFFVAvNmLiuFDSIgBSlkj88-5bXv3he4nViaU0g?e=nbOp3iFrench version: https://adonisas.sharepoint.com/:b:/s/sp/development/EQ2NuJZUP5pDriIcQxbjmIABBdQ6oXQ6DfcBdpUGCjrypA?e=4dC0Ki Eng - DSN Specification DSN-CT-2021.1 Chapter 1 to 8 .pdf
Original French document: DSN Specification DSN-CT-2021.1.pdf
What is next:
Setup the Annual Code References
- Upload the block/topic id
...
- into the Annual Maintenance (Install DSN Plugin and APM 2020.50.5 Patch 4)
...
- The DSN plugin contains the routine to upload the DSN Block and topic id's the APM patch is needed to
...
- include the database modification needed.
- Identify those fields/Information that is missing and can not be set during the payroll calculation. (for details check chapter 8 see above)
- Check with the customer if all block- and topic-id's are covered
...
- . Identify missing id's and id's that are redundant and can be removed.
Finish the plug-in to produce the file and user interface to check and upload the file.
The plug implementation covers the functionality to produce and upload the file. Besides some exception of some header information, the plugin does not contain any functionality populating the topic id. This s need to be covered as much as possible in the annual code setup.
Check the other export types and workflow sending corrections,
...
cancelling an export etc.
Other variations of the export.