Release Notes 23.2 IDL Konsis, Forecast, Xlslink
Contents
- 1 General Notes
- 2 IDL Konsis
- 3 IDL Forecast
- 4 IDL Xlslink
1 General Notes
1.1 About this Release
This documentation describes the changes in IDL Konsis, IDL Forecast, and IDL Xlslink compared to Release 23.1. The minimum requirement for installing this version is the installation of Release 23.1.
The previously released fixpacks are included.
1.2 Data Backup
Before installation, please make a backup of your database(s) and check it to protect against data loss.
1.3 Migration
After installation, the release migration for IDL Konsis / IDL Forecast must always be performed first. After logging in, start the release migration via <Start migration now> in the message window. A restart is not necessary, all applications are available afterwards.
You can find the protocol of the migration under the short word KONVERT (right-click on the corresponding migration).
If the migration is not started in this manner, e.g., because the logged-in user lacks authorization, the call of other applications is blocked. The only exceptions are the applications for maintaining the authorization data if the logged-in user does not have authorization to execute the migration due to the use of individual authorization groups. After manual execution of the migration, IDL Konsis / IDL Forecast must be restarted.
1.4 Documentation
In the subdirectory Doku\Release you will find the following documentations:
- Technical Installation Instructions
- Operational Installation Instructions
- Release Notes
For the currently valid "Hard- and Software Requirements", please refer to the Customer Portal
https://help.insightsoftware.com/s/article/IDL-Hard-and-Software-Requirements (login required).
1.5 Security
TLS 1.3 is used as the communication protocol between the client and the application server. Perfect Forward Secrecy makes it even much more difficult to decrypt the connection at a later date.
1.6 Technical Information Web Client / Desktop Clients / Java
To enable "Web Client (Streaming)" please start configure.exe on your IDL Application Server and go to the Common Configuration Section. After services have been restarted you could access IDL Konsis with your Browser at your individual URL followed by https://myIDLKonsisAppServer/webswing-server/konsis/.
The IDL Desktop Client and the IDL Launcher deliver the used JRE (Java Runtime Environment) in the installation directory, so that a separate installation of a JRE is not necessary.
Java 17 has been used since release 22.1.
After extensive internal renewal work IDL Konsis since release 23.2 is delivered as a fully Java based application to you. No functional differences belong to this. Older DLLs will be removed within the upcoming releases.
Note: The runtime environment included in this release is limited until 01.03.2026 and must be renewed from this date at the latest.
1.7 Other Notes
1.7.1 Insightsoftware Platform
Authentication and licensing have been extended to allow operation within the insightsoftware Platform. The platform has multifactor authentication (MFA) to increase IT security. The insightsoftware Platform also guarantees a single sign-on (SSO) to other insightsoftware brands.
1.7.2 User Interface
Further adjustments were made towards a uniform UI for all products of insightsoftware.
1.7.3 External Libraries
External libraries were updated to eliminate potential vulnerabilities.
2 IDL Konsis
2.1 Menu Authorizations
The following menu items have been deactivated with this release because they have already been replaced by other applications in previous releases. The menu items will be deleted in a subsequent release. Until then, please remove all individual uses (authorizations, menu structures) of these menu items:
- This release does not contain any disabled menu items.
2.2 Master Data
2.2.1 Extension of the Chart of Accounts Definition Application (KTODEF)
The chart of accounts definition application has been extended in such a way that all the functions existing in the previous accounts application (KTO) are now mapped. For this purpose, the following functions have been added.
In the account table of the KTODEF application, the function "Create pos acc allocations for company account" can now be called in the context menu. After calling this function, a dialog opens in which the desired chart of positions must still be entered.
The new table "Group/Aggregation Account View" has been added as an additional tab next to the account table. In this table, aggregation account allocation and group account allocation are displayed together in a tree structure. Accounts can be edited in this view using the wizard, provided they are included in an open chart of accounts. Direct editing in the table cells or assignment via drag & drop is not possible in this view.
The new context menu item "Show assigned group account" has been added to the account table of the KTODEF application. When it is called, the system switches to the above-mentioned "Group/Aggregation account view" table and positions it on the selected group account.
2.3 Company Financial Statements
2.3.1 Automated Vouchers and Postings (BUCHDEF)
The balances and transactions available in IDL Konsis on one fact (FAC) can be verifiably changed on the next fact using vouchers (BEL) and postings (BUCH).
As of this release, in addition to manually created vouchers and postings, rule-based vouchers and postings can be generated with the new BUCHDEF application, thus automating essential steps.
The creation of rules for vouchers and postings is conveniently supported with wizards and guides you through the process.
On the first page of the voucher rules, as usual, an ID, description, and validities must be specified:
Voucher No., text, and data type as well as other details are defined from page 2 of the wizard:
On page 4, the affected period(s) and the inclusion of business units can be defined:
In the case of posting rules, a guided setup is also carried out via a wizard.
Note: The creation of a posting rule is optional. If there is only a voucher rule, without posting rules, this voucher rule creates "empty" vouchers. Vouchers that are not needed can later be deleted or made inactive in order to clean up yellow status displays in the company financial statement monitor.
In general, carry-forward posting keys are not available for transactional development accounts, as it does not make sense from a business point of view in normal cases to post directly to the carry-forward of an account within company related financial statements.
The origin and target are defined in the posting rule. The account (possibly with posting key, business unit, and controlling information) must be specified as the origin, on which the balance to be posted or the development transaction to be posted can be found:
Controlling objects, etc. can also be taken into account in the further steps:
Subsequently, the rule-based postings and vouchers can be generated in the company financial statement monitor:
In a voucher, both manual postings (including carry-forward postings) and rule-based postings can exist side by side. When the vouchers are generated, it is checked whether the attributes of the existing vouchers match the information in the voucher rule.
Within the BUCH application, rule-based postings can be identified in a new column that shows the voucher rule number. For non-rule-based postings (e.g., manually entered postings or carry-forward postings), this column remains blank.
Period carry-forward
In the case of period carry-forwards, a distinction must be made between carry-forwards during the year and carry-forwards at the turn of the year. If the origin period is an annual period (indicator = J), it is a carry-forward with the turn of the year, otherwise it is a carry-forward during the year.
In the case of period carryforwards at the turn of the year, rule-based postings are carried forward in the same way as manually entered postings. They do not bear a mark of origin in the target period, as they were not generated from rules, but from the carry-forward.
During the year, all transactional movements and manually recorded bookings are copied from the origin period to the target period. However, the rule-based postings are left out, as the generation of rule-based postings has to be restarted in the target period, as the amounts to be posted may also have changed.
When (re)generating the rule-based vouchers and postings, if necessary, existing rule-based postings are deleted.
Special case amount 0.00
If the amount to be posted is 0.00, the respective posting rule is executed, and corresponding postings are generated with an amount of 0.00 each. This is done in order to ensure completeness and clarity in the case of a sequential sequence of several voucher rules.
2.4 Reporting
2.4.1 Options for Columns in Reports
New report column options are provided for the result-related representation of the change. These start with # and end in DB, e.g., #ALTDB, #BUCDB, #NEUDB, #SUMDB, #KONDB, #KTKDB.
3 IDL Forecast
3.1 General
No significant changes to IDL Forecast functions are included in this release.
4 IDL Xlslink
4.1 General
In addition to the new features described below, a number of bug fixes and performance improvements have again been incorporated into IDL Xlslink in this release.
The UI of IDL Xlslink was adapted to the further development of the user interface of the insightsoftware platform and IDL Konsis to ensure a uniform appearance.
4.2 Read Functions
4.2.1 Read IC-account Balances
In the read function for group IC-account balances, you can now also select by consolidation voucher number and thus by state of consolidation. Please note: The voucher companies 1 or 2 can be sometimes GES, sometimes IC-GES.
4.2.2 Controlling Balances can be Selected by State of Consolidation
In the controlling balances, it is now also possible to select according to the attributes of the consolidation voucher.
4.2.3 D/C flag new in EAICKTOSAL, KAKTOSAL, and EAGESGES
In the reading functions for individual financial statements - IC account balances, group - IC account balances, and shareholding transactions, there is now also a field for the debit/credit flag.
4.2.4 Origin report number removed from item balances from reports.
When creating item balances with different report IDs, the existing item balances are always overwritten by the last report created, so each position exists only once. Therefore, the entry of the origin report is redundant or leads to zero values if it was overwritten by another report. We have therefore removed the superfluous origin report number field from the read function.
4.3 Export Functions
4.3.1 New fields for font and background colour in export function Report lines
We have added two new fields for the export function Report Lines in order to be able to specify the font colour and background colour during export. Colour values can be specified in RGB format.
4.3.2 Presets in IDL Konsis are now affecting exporting functions as well
The preset default values for IDL Konsis are now also used as default values for the export functions.