Skip to main content

EDI Tutorial - Advanced Parameterization

Third Part of the EDI Tutorial: EDI Communication Parameterization Options, Automatic Document Import, and Possible EDI Message Extensions

Written by Petr Pech

Using advanced parameterization, it is possible to partially automate the import and export of EDI documents, which will occur every time a user logs into the company. Manual import is also available even when automatic mode is configured. Additionally, further EDI extensions can be activated via advanced parameterization. The XML file with the advanced parameter is imported into ABRA Flexi via the menu Tools > Import > Import XML.

If you are interested in any of the EDI parameterizations, please contact our technical support. Configuring advanced parameterization is subject to a standard service fee in accordance with the current price list.

The configured parameters can be verified at:

{Váš server}/c/{identifikátor firmy}/parametr.xml?limit=0

Below is an overview of the individual advanced parameters

The parameter names listed correspond to their representation in the XML installation:


paramLoginImportEDIDirectory

  • function description: used for automatic import of received orders (ORDERS message) upon user login to ABRA Flexi from a selected folder on the PC

  • usage example: <hodnota>c:\communicator\in\orders</hodnota>

Recommendation: we recommend organizing the c:\communicator folder into subfolders by message type (ORDERS, INVOIC, DESADV) to avoid conflicts during import/export.

You also have the option to install the EDI integrator communicator on multiple client PCs. For automatic import upon user login to ABRA Flexi, messages must be downloaded to a shared folder, such as OneDrive, Dropbox, etc. All users must have the shared folder accessible on their PCs at the same path, for example drive Z:\communicator\edi/... All users with access to the drive can then use the automatic import upon login.

  1. Prepare the folders or shared drive from which the EDI files will be imported.

  2. Next, create an XML file with the parameter settings and import it into ABRA Flexi.

  3. Download incoming EDI files using the communicator into the designated folders. The next time you log in to ABRA Flexi, their sequential import will start automatically, and then they will be moved to the folder for imported files as configured by the following parameter paramLoginImportEDIMoveTo.

paramLoginImportEDIMoveTo

  • function description: sets the directory to which EDI messages for received orders (ORDERS message) that have been imported into ABRA Flexi will be moved

  • usage example: <hodnota>c:\communicator\in\orders\imported</hodnota>

paramLoginImportEDIFapDirectory

  • function description: used for automatic import of received invoices (INVOIC message) upon user login to ABRA Flexi from a selected folder on the PC

  • usage example: <hodnota>c:\communicator\in\invoic</hodnota>

paramLoginImportEDIFapMoveTo

  • function description: sets the directory to which EDI messages for received invoices (INVOIC message) that have been imported into ABRA Flexi will be moved

  • usage example: <hodnota>c:\communicator\in\invoic\imported</hodnota>

paramLoginImportEDISklDirectory

  • function description: used for automatic import of goods receipts (DESADV message) upon user login to ABRA Flexi from a selected folder on the PC

  • usage example: <hodnota>c:\communicator\in\desadv</hodnota>

paramLoginImportEDISklMoveTo

  • function description: sets the directory to which EDI messages for goods receipts (DESADV message) that have been imported into ABRA Flexi will be moved

  • usage example: <hodnota>c:\communicator\in\desadv\imported</hodnota>

paramLoginImportEDISklad

  • function description: a required parameter for automatic import of orders upon login; sets the warehouse code to which the imported received orders should be assigned, i.e., from which they will subsequently be dispatched

  • usage example: <hodnota>SKLAD</hodnota>

To enable automatic import, it is not necessary to configure all parameters — only those relevant to the document types for which automatic import is required.

paramEDIEanObjednateleZMistaUrceni

  • function description: when set to the value "true", the GLN of the delivery location will be used as the buyer's GLN during EDI export; "false" for the standard behavior (GLN from the document/company header).

  • usage example: <hodnota>true</hodnota>

paramEDIExportPodleZaskrtavatek

  • function description: suitable for bulk export of EDI messages using checkboxes; determines whether the document selection should be respected during EDI export (value "true") or whether only the current record should be exported by default (value "false")

  • usage example: <hodnota>true</hodnota>

paramEDIExportDirectory

  • function description: used for semi-automatic export of documents to EDI; after clicking the "Export to EDI" button, it is not necessary to select a directory — the file is automatically saved to the configured folder.

  • usage example: <hodnota>c:\communicator\out</hodnota>

paramEDISaveOrderLinnr

  • function description: this parameter inserts into the exported delivery note (DESADV message) line numbers matching those on the stock issue in ABRA Flexi; enable by setting the value to "true".

  • usage example: <hodnota>true</hodnota>

paramEDIFAPSaveOrderNr

  • function description: this parameter enables saving the order number to the line item notes of a received invoice in ABRA Flexi when importing a received invoice (INVOIC message).

  • usage example: <hodnota>true</hodnota>

paramEDIExportVydejkaDatumDodaniPosunDny

  • function description: this parameter sets the number of working days to be added to the issue date of the stock issue and used as the expected delivery date when exporting a stock issue/delivery note (DESADV message) to EDI. Applicable for EDI communication with Alza a.s.

  • usage example: <hodnota>7</hodnota>

paramEDIImportHDRNeomezenePosledniPole

  • function description: when the parameter is set to "true", all text in the header of imported received orders (ORDERS message) from position 123 onwards is transferred to the order description; for imported goods receipts (DESADV message), all text in the header from position 182 onwards is transferred to the document note. The value "false" activates the default behavior, where only the Free text field (70 characters) from the EDI message is written.

  • usage example: <hodnota>true</hodnota>

paramEDIImportLINNeomezenePosledniPole

  • function description: when the parameter is set to "true", all text on the line of imported received orders (ORDERS message) from position 86 onwards is transferred to the order item name; for imported goods receipts (DESADV message), all text on the line from position 176 onwards is transferred to the item name; for imported received invoices (INVOIC message), all text on the line from position 357 onwards is transferred to the item name. The value "false" activates the default behavior, where only the Free text field (45 characters) from the EDI message is written.

  • usage example: <hodnota>true</hodnota>

paramEDIImportLINEanNepovinny

  • function description: this parameter allows importing issued invoices (INVOIC message) without GTIN (EAN) item codes.

  • usage example: <hodnota>true</hodnota>

desadvOcekavaniDodavkyObpTermin

  • function description: this parameter activates the transfer of the Due Date field from the linked received order when exporting a delivery note/stock issue (DESADV message) to the Expected Delivery Date field. Applicable for EDI communication with Albert ČR.

  • usage example: <hodnota>true</hodnota>

invoiceCisloDodacihoListuZVydejky

  • function description: this parameter activates the transfer of the Internal Number field from the linked stock issue when exporting an issued invoice (INVOIC message) to the Delivery Note Number field. Applicable for EDI communication with Albert ČR.

  • usage example: <hodnota>true</hodnota>

ediInvoicLinEanZboziPovinny

  • function description: this parameter enables the option to export an invoice (INVOIC message) without EAN codes for individual line items. Applicable for EDI communication with Škoda AUTO.

  • usage example: <hodnota>false</hodnota>

ediFavLinCisloObjednavkyZakaznikaUvadet

  • function description: this parameter enables the export of order numbers to invoice line items when exporting an invoice (INVOIC message). When the parameter is active (true), the incoming number is filled in for the items; if not filled in, the order code is used instead. Applicable for EDI communication with Škoda AUTO.

  • usage example: <hodnota>true</hodnota>

ediFavLinCisloDodacihoListuUvadet

  • function description: this parameter enables the export of delivery note numbers to invoice line items when exporting an invoice (INVOIC message). When the parameter is active (true), the delivery note number is filled in for the items; if not filled in, the stock issue code is used instead. Applicable for EDI communication with Škoda AUTO.

  • usage example: <hodnota>true</hodnota>

ediFavLinCisloDodacihoListuVychozi

  • function description: if the previous parameter is activated but no delivery note number is available, the default value configured here will be used. Applicable for EDI communication with Škoda AUTO.

  • usage example: <hodnota>DOD123</hodnota>

ediFavLinCastkaDphUvadet

  • function description: this parameter activates the addition of the mandatory VAT amount on the invoice line to 2 decimal places when exporting an invoice (INVOIC message). Without this parameter, the field is not populated. Applicable for EDI communication with Škoda AUTO.

  • usage example: <hodnota>true</hodnota>

paramEDIImportBaleniPodleMmozMjVBal

  • function description: when set to true, this parameter enables searching for a matching packaging unit based on the quantity per package. The search is based on the Number of consumer units (EDI LIN 19), not the unit of measure name.

  • usage example: <hodnota>true</hodnota>

paramEDIExportBaleni

  • function description: the export of document line items (delivery notes, invoices, orders) reports in the Quantity field, in the case of a price list item with a defined packaging unit, the number of packages

  • the value of Number of consumer units in the ordered unit is written to the EDI line items

  • by setting this advanced parameter to false, it is possible to revert to the previous behavior

  • usage example: <hodnota>false</hodnota>

paramEDIImportIgnorujMnozstviVBaleni

  • function description: when set to true, the Number of consumer units… field, which affects the loaded quantity of a given item, can be ignored when loading an EDI message.

  • usage example: <hodnota>false</hodnota>

EDI Tutorial

Need help?
If you have any questions about the application, contact us at podporaflexi@abra.eu or via the chat window in the bottom right corner.

Did this answer your question?