DatevLodasIU
|
Class name |
com.ebd.hub.datawizard.iu.DatevLodasIU |
This Integration Unit can be used to generate a DATEV LODAS interface file from the target structure.
The detailed structure of LODAS files can be found in the corresponding interface manual of DATEV.
Parameters
The following parameters are used to indicate which nodes in the target structure contain the data for the various LODAS sections.
The Satzbeschreibung section is mandatory in LODAS and is automatically generated by the Integration Unit. It contains the structure description of the individual tables in the form of record types. For this purpose, the nodes Bewegungsdaten, Stammdaten and Entfernen must each contain subnodes table_<table name>. See example below.
|
Parameter name |
Default value |
Description |
|
Data section node |
Bewegungsdaten |
Use the default value. The node Bewegungsdaten in the target structure has to contain the data for the LODAS file section Bewegungsdaten . Note: This section is optional in LODAS. One of the sections Stammdaten or Bewegungsdaten must be used. |
|
General section node |
Allgemein |
Use the default value. The node Allgemein in the target structure has to contain the data for the LODAS file section Allgemein . Note : This section is mandatory in LODAS. |
|
Master data section node |
Stammdaten |
Use the default value. The node Stammdaten in the target structure has to contain the data for the LODAS file section Stammdaten . Note : This section is optional in LODAS. One of the sections Stammdaten or Bewegungsdaten must be used. |
|
Removal section node |
Entfernen |
Use the default value. The node Entfernen in the target structure has to contain the data for the LODAS file section Entfernen . Note : This section is optional in LODAS. |
|
Text section node |
Hinweistext |
Use the default value. The node Hinweistext in the target structure has to contain the data for the LODAS file section Hinweistext . Note : This section is optional in LODAS. |
Example
Let's assume the following target structure.
The Integration Unit then creates a file like the following.
[Allgemein]Version_SST=1.0Version_DB=11.10BeraterNr=455148MandantenNr=5Feldtrennzeichen=;Stringbegrenzer='Zahlenkomma=Kommentarkennzeichen=StammdatenGueltigAb=BetrieblichePNrVerwenden=[Satzbeschreibung]1;u_lod_bwd_buchung_standard;abrechnung_zeitraum#bwd;bs_nr#bwd;bs_wert_butab#bwd;la_eigene#bwd;pnr#bwd;[Bewegungsdaten]1;01.12.2020;1;0,07;14;17;1;01.12.2020;1;5,57;14;45;1;01.12.2020;1;0,47;14;68;1;01.12.2020;1;0,47;14;75;1;01.12.2020;1;3,75;14;79;1;01.12.2020;1;0,02;14;89;1;01.12.2020;1;1,10;14;102;1;01.12.2020;1;1,58;14;103;1;01.12.2020;1;0,25;14;119;1;01.12.2020;1;0,50;14;131;1;01.12.2020;1;0,83;14;134;[Hinweisdaten]My text...In the data line in section "Satzbeschreibung" you can see the first value 1. This is the record type that is also referenced in section "Bewegungsdaten". It is automatically generated from the first table_ node. Another table_ node would create record type 2.
The second value in the line is the table name, see (1) in the screenshot.
The remaining values are the field names, see (2) in the screenshot.