Data Exchange Enhancements AE098

General Description #

This extension allows to set up merging of 2 text fields when importing bank statements through the definition of data exchanges. It also allows importing any file format. There is also an option to export the payment journal in the .121 format and to import bank statements in MT940 and CSV.

Data Exchange Definition has been extended with option to select line endings using Record Separator field and miscellaneous field Convert UTF-16 To MSDos, which may help if "'.', hexadecimal value 0x00, is an invalid character" error occurs during import.

Settings #

To import any file, on the Data Exchange Definition tab, select ext data handling codeunit data processing 79151 (reading a data exchange file). To set the rule for merging 2 text boxes, we enter the merge formula in the Merge Rule field in the field mapping row in the data exchange definition. It is allowed to merge the fields with the help of %x where X indicates the line number. Therefore %2 - %1 creates if line 1 contains "123" and line 2 "789", 789 - 123.

To import bank statement in MT940 format via data exchange, the Reading/Writing Codeunit in Data Exchange Definition must be set to 79150 and Ext. Data Handling Codeunit must be set to 1240. Additionally, in Field Mapping the Mapping Codeunit must be set to import codeunit specific for given bank, for example you must use codeunit 79187 for importing Deutsche Bank statement. Currently the extension does not allow users to specify which fields should be imported.

To import bank statement in CSV format from Bank Account Reconciliations or Payment Reconciliation Journals pages, the following must be set: In Data Exchange Definition the Reading/Writing XMLport must be set to 79010 and Ext. Data Handling Codeunit must be set to 1240 while in Field Mapping the Table ID must be set to 274, Mapping Codeunit to 1248 and Post-Mapping Codeunit to 79189. With this setting the users can use Column Definitions and Field Mapping to select which data should be imported. To ensure that only the statements of given bank account are imported, the column containing the bank account must be mapped to Related-Party Name.

To import bank statement in CSV format from Payment Journal page, the following must be set: In Data Exchange Definition the Reading/Writing XMLport must be set to 79010 and Ext. Data Handling Codeunit must be set to 1240 while in Field Mapping the Table ID must be set to 81, Mapping Codeunit to 1247 and Post-Mapping Codeunit to 79192. With this setting the users can use Column Definitions and Field Mapping to select which data should be imported. To ensure that only the statements of given bank account are imported, the column containing the bank account number must be mapped to Imported Account No. and the column containing IBAN must be mapped to Imported IBAN.