Skip Navigation LinksHome / Support / FAQ

You can now freely use the web site for the evaluation period. If you need additional time to evaluate the product, please send a request to support@b-data.com.

The best way to understand how it works is to run the supplied demo transactions. Those transactions were carefully chosen to demonstrate mapping and translations for most popular types of files and standards.

It is recommended to review the definitions and options as they appear in Business Partners|Options and review the Help. For example, if you are located in the United State you have to check the US Date Format option or switch the Language to English (US). In general, it is highly recommended to have a good understanding of all settings and options before starting to use the application.

This is part of your setup and all you have to do is to make sure that the folder to which you want to move your source files after processing is defined in the Processed files folder field (Business Partners|General). There is already a predefined folder \Ediprc which you can use for this purpose.

You can use wild cards in the name of the source file. For example, \Ediinp\*.*, will cause the processing of all files in the ediinp folder.

You can use the command AUTO in the destination file field and EDIx will automatically assign a file name to each destination file according to a predefined pattern that you can setup in Business Partners|Options.

EDIx has all you need to execute scheduled processes for both scenarios and communications. Please use the Services Controller,

You can setup automatic e-mail notifications by using the error notifications options as defined in Business Partners|Error Control.

Translated codes can be associated with a certain partner by entering the partners code in the ePartner column in Translation Tables. The ePartner code itself is defined in Business Partners|Options and as such allowing the execution of the same transaction for different partners depending on the scenarion ini file (the ini file contains the ePartner code).

You can use the Business Rules and Routines options and record your code. This code can be then re-used by copying into maps or filters.

You can practically define any mathematical or logical expression by using the function EVAL. It is recommended to test functions by using the Function Evaluator program.

You can check conditions (business rules) and generate errors during the mapping process. See example bellow. For details look up the Business Rules chapter. IF@EVAL(((KEEP10 in '34') and (KEEP11 in 'SY')) or ((KEEP10 in '24') and (KEEP11 in 'EI')))=True:ERROR50- REF01 cannot be 24,34 when NM108 is EI,SY

All you have to do is to check the No error check on destination file check box in Business Partners|Error Control.

You can check conditions (IF@) before writing to file and use the command SKIP to indicate that a certain segment should not be generated.

Use the switches KC and KM in the Commit column of the filter. Segments kept in memory can be also indexed by using the command SETID and retrieved according to a certain key by using the command GETID.

Codes like A2, I2..3, etc… can be used in the Pattern column of a map to indicate that data elements should match such patterns. For example A2 will check that the data element is alphanumeric and of fixed length 2 – if the condition is not met an error message will be automatically generated.

A KEEP variable can be used in the Formula column to store the value of the data element that holds the pattern and then reused in the Pattern column of the data element that is supposed to have this particular pattern.

To indicate different patterns for different loops use the syntax Pattern|Loop/Pattern|Loop/Pattern, etc… For example A2..4|2000/D6|2100/X will indicate that the default pattern is A2..4 but if this particular segment appears in loop 2000 then pattern is D6 and if it appears in loop 2100 it is not used (X).

If the segment has a unique identifier then use this value in the Level/Anchor column of the map. If there is no unique identifier then use the indicator @ in the Level/Anchor column to cause the program to continue to search in the map after the first appearance of the segment.

Back to Top