General configurations
Here you will find an overview of optional and required database field configurations of the ZF2INVHT table that use the ZUGFeRD mappings.
Status and Profile
The following database fields must be filled in for outgoing data records to be processed:
field name | content | function |
|---|---|---|
HTDIRECT | *OUT | Differentiation between incoming and outgoing data records. |
HTNAPPREF | extended_2.2.0 | Profile and version of ZUGFeRD. “basic", "comfort" and "extended" can be specified as the profile. The profile and version number must be separated by an underscore. |
HTSTATE | Displays the current status of the data record: empty = to be processed 1 = successfully processed 2 = incorrect processing |
PDF template and existing PDF files
It is possible to create a PDF, which is combined with the generated XML during mapping, using a template or to use an existing PDF file for the ZUGFeRD PDF. Which method is chosen depends on the content of the HTTEMPLDIR and HTPDF database fields:
field name | content | function |
|---|---|---|
HTTEMPLDIR | extended | The folder name of the template with which a PDF is to be created. The folder must be located under /home/ieffect/zugferd/templates. If the field is empty, a generic extended template is automatically used. |
HTPDF | /home/ieffect/pdf/zugferd.pdf zugferd.pdf | The path to an existing PDF file or the name of the PDF to be created. If a complete path (with a leading / ) is specified, no PDF is created, but an attempt is made to use the specified PDF for combining XML and PDF. If only a file name (including file extension) is specified, the PDF is generated using a template and is given the specified name. The file is created in the output directory specified in the RUNMAP command. |
If a complete path to a PDF file is entered in HTPDF, the content of HTTEMPLDIR is ignored as no PDF needs to be created.
If a PDF is created but no name is stored in HTPDF, a file name is generated. This file name consists of a prefix, which specifies the profile, and the invoice number. In this case, the output directory is also the output path specified in RUNMAP.