Release 5.4.1 news

Table of contents

• 1 General notes
• 1.1 Advice for this release
• 1.2 Error during connection to the IDL Konsis-database
• 1.3 Connection to the database with Microsoft SQL-Server 2000 (NT-authentication)
• 1.4 Dismiss the connect to an IDL database if the user-id is unknown in the IDL Konsis application
• 1.5 Microsoft SQL Server 2005
• 2 Export function (To KONSIS)
• 2.1 Direct import
• 3 data collecting form - KVM100
• 3.1 conversion factor
• 3.2 IDL Connector-reference also in actual period
• 3.3 GESUBR table of IDL Konsis
• 3.4 Additional details - HBI/II
• 3.5 Additional details - PERIODE
• 3.6 Additional details - UKV / UKV-X
• 3.7 Additional details - GB-X / UKV-X

The IDL Connector is a part of release IDL KONSIS 5.4.1 (analogue IDL Winkons 3.1 and PPconsis 4.2). This is an interim maintenance and therefore can be left out in the release sequence. Prerequisite for this release is the last main maintenance (IDL KONSIS 5.4.0 or IDL Winkons 3.0 or PP consis 4.01) of the Sept. 15th 9th 2005. The supplements and corrections to the main maintenance are contained in the current interim maintenance.

Concerned application:

IDL Connector-Server

Error:

Concerning Microsoft Excel97 the IDL Connector wasn't able to establish an connection to the IDL Konsis-Database.

Concerned application:

IDL Connector in conjunction with Microsoft SQL Server 2000

Error:

The IDL Connector used an incorrect user-id for the connection to the Microsoft SQL-Server 2000 with NT-authentication. The IDL Connector was able to connect the user to the database with the incorrect user-id but the user got no datas back from the database.

Concerned application:

Database access

Enhancement:

The IDL Connector accepts so far if the user-id for the connection was known in the relative database management system but unknown in the user-table of the IDL Konsis application, in this case the IDL Connector established an connection to the database. The user wasn't able to get any datas back from the database.

Change:

The IDL Connector will matched to IDL Konsis, i. e. if the user-id is unknown in the user-table or got no company startup data the login will be denied with an error message.

Concerned application:

Database access

Enhancement:

The IDL Connector version 5.4.1 supports now the Microsoft SQL Server 2005

Enhancement:

The IDL Connector version 5.4.1 supports the direct import into the IDL Konsis database. The IDL Connector starts IDL Konsis in the backround and transfers the import data online into the application. After starting the export the user will be asked every time if the datas should be saved into the database (Button 'save' analogue TXT... in IDL Konsis), if existing datas in the database should be deleted and afterwards saved in the database (button 'delete/save' analogue TXL... in IDL Konsis), or if the IDL Connector should create a text file (button 'save to file').

Enhancement:

The IDL Connector version 5.4.1 supports now an conversion factor. Example: In IDL Konsis an company has got the local currency EUR, the balance of an account in the previous period is 5.000,-EUR and the user types a factor of 1000 in cell D2 in the data collection form in all values of the previous period will be devide by the factor of 1000. The user which fill out the collecting form read only the value 5 EUR in the previous period of this account, he has to fill in the values in the same form. That means if the account balance is 10.000,-EUR he has to fill in only 10 EUR in the cell of the actual period. When the export of the collecting form runs all values of the actual periode will be multiply with the factor 1000 of cell D2. The value of this account in the IDL Konsis database should be 10.000,-EUR after import.

Enhancement:

The IDL Connector supports now a new option 'create master on act period', this option enabled the user to get also IDL Connector-references in the actual period of the sheet 'account balances'. This enhancement is necessary if the account balances are transferred by an interface from your finance-system into IDL Konsis but the transactions are not delivered from your system. In this case the user gots an collecting form which still contains the account balances of the actual and the previous period. The user has only to fill in the needed transactions.

Enhancement:

the IDL Konsis version 5.4.1 supports structure table "GESUBR" of company and business unit. The permitted combinations must be defined in this new structure table. The IDL Connector considers this combinations when the collecting form will be created if the user choose the addional details GB or GB-X.

Attention:

Until now the function 'create master' don't work for this kind of collecting forms, that means if there are different combinations of company and business units the user has to insert for each combination an report and create collection forms for each combination afterwards. The function to adjust the combinations automatically couldn't be finished because of time constraints. IDL will deliver this function in the future IDL Connector version addition.

Enhancement:

The IDL Connector supports now to create the collection form HBI/II. This collection form enabled the user to fill in the acount balances according to the financial accounting. Afterwards the collection form affords another column to fill in some postings. The sum of account balances +/- postings will be used for the particular transactions. At the export of the collection form the cumulative account balances (account balance +/-postings) and the transactions will be exported.

Enhancement:

The IDL Connector offers now to create the collection form PERIODE. This collection form enabled the user to fill in the datas for multiple periods in only one collection form. The IDL Connector read the report header and used all period between the actual and the previous period for the collection form but if one or more periods are not inserted in the application 'Closing date actual periods' (ABR) the IDL Connector ignores this periods. Example: In the table ABR are the periods 12.2005, 03.2006, 06.2006, 09.2006 and 12.2006 inserted. The actual period of the report header is 12.2006 and the previous period is 12.2005. At the creation of the collection form PERIODE the IDL Connector used all periods between 12.2006 and 12.2005, according to this there are four columns available for entry.

Enhancement:

The user is able to decide which controlling objects should be available für the collection form. This selection must be defined BEFORE the collection form will be created. IDL supports now until 30 controlling objects für the collection form. The user has to click on the button on the right side of the field 'Additional details' for this selection but this button is only enabled if an addional detail e. g. UKV would be selected.

Error:

If a value would be filled in the column actual period but the user filled no value in the columns for business units or controlling objects, then the collection form don't dye the cell red although there is a difference. This error was fixed with this version.