Release Notes 22.XX.00

The Java version on which the software is based was raised from 8 to 17.

Situation:

If the function "Copy settings" is used within the toolbox and then "... Copy to period" is selected, the data from the period to be copied is not taken over.

Solution:

The copy can be executed.

Situation:

A large number of error messages are displayed in the log files. These error messages are not "real" failures.

Solution:

No error messages are displayed in the log file if they are already intercepted and processed by the GTC.

Situation:

When creating a new company, data can be copied from another company. It is not possible to select from which period the company data should be loaded.

The performance for loading the create dialogue is very slow depending on the number of companies and periods in the GTC.

Solution:

The copy function has been adapted. The source period is now selected first and then the company to be copied.

Only active companies are displayed in the list of companies. The corresponding master data authorisations are taken into account.

As the list of information to be loaded is now significantly shorter, the performance of the create dialogue has also improved.

Situation:

In the sections "Withholding Taxes", "Tax Questionnaire", "Risk Management" and "Compliance", the button "My Profile" is displayed.

Solution:

The button is split into "My Data" and "My Settings" in the portal context. This now also applies to the aforementioned areas.

Situation:

In the milestone workflow of tax groups, it was possible to create a state in which the milestone 'Actual taxes' of a company could no longer be continued, although all conditions were apparently fulfilled.
In this specific case, it was not possible to set the milestone of an (intermediate) tax group parent from 'completed' to 'checked'.

Solution:

It is now no longer possible to create such a state. If the system is already in the state, the milestone 'Actual Taxes' of the affected (intermediate) tax group parent must be reset to "in progress".

Situation:

In the configuration of the Toolbox, the selection of the country cannot be changed. The behaviour occurs in versions 21.07.12, 22.00.02, 22.05.00 and 22.06.00.

Workaround:

Switch to the dialogue Master Data / Home and select a company there that is assigned to the country that is to be configured in the Toolbox. Then carry out the configuration in the Toolbox.

Solution:

The selection of the country can again be changed directly in the dialogue Toolbox.

Situation: 

Under some circumstances the log files are not displayed under Master Data /Administration.

In addition, since the changeover to Log4j2, it is no longer possible to change the log level within the GTC application at runtime.

Solution:

The log files are displayed in the dialogue Master data / Administration / Log files, no matter where the path to the log files is maintained.

The log levels can be changed again in the dialogue Master data / Administration via the button "Change log level".

Situation:

A security vulnerability has been reported for the library xalan-2-7-2.jar. 

Solution:

The library is now provided directly by the underlying JDK. As of JDK version 1.8.0.342.b07, CVE-2022-34169 has been fixed.

Please update the Java version used by the Tomcat server if necessary.

Situation:

Since the dialogue "Report DT (LCF)" in "(Sub-) Group" was redesigned, some values are incorrectly shown as zero.

Solution:

The dialogue "Report DT (LCF)" in "(Sub-) Group" correctly calculates all values.

Situation:

The dialogue cannot be opened if one of the tax group members is not existing in the true-up period.

Solution:

The dialogue can still be displayed.

Situation:

The Deferred Tax milestone cannot be set to checked for a consolidation unit.

Solution:

The milestone worklfow can also be run through to the last status checked for consolidation units.

Situation:

Uploading XML files is a security risk because links can be hidden in XML files that enable attacks (e.g. SSRF). 

Solution:

The XML upload options in the Master Data/Countries, Master Data/Companies (in the IMPORT period) and Company/Import dialogues have been removed.

Situation:

Dialogue "Own Reports" allows GTC customers to directly access database tables and use them for a variety of further evaluations and data processing.

Because of security reasons the access to table TUSER and associated tables was forbidden. This restriction was regarded as too far-reaching by several customers.

Solution:

Own reports may again access every database table. There is one exception, namely table TUSER. The view VUSER must be used instead.

Only relevant if the setting SHOW_OCI_AT_SUMMARY=1 is active:

Situation:

When entering a value in the "Others" dialogue in the block "Other, Prior year adjustments - OCI", the calculated value is doubled in the "Summary" dialogue.

Solution:

The value is displayed at the correct amount.

Situation:

Users with auditor rights must not be able to create or view comments. This restriction is not completely implemented in all dialogues.

Solution:

Users with auditor rights can neither create nor view any comments.

Furthermore, the report "Comments" is hidden and cannot be called.

Situation:

If the import of a csv file is based on a flexible interface structure and the position id is missing in some row, the import is aborted and a corresponding error message shown.

Solution:

The import ignores lines with a missing position id and continues with the remaining lines.

Situation:

If module Income Taxes is integrated into the Portal Suite, roles and role allocations are maintained in the portal. Nevertheless, dialogue "User" of Income Taxes still presents all role assignments. Instead of role names, however, only their internal IDs are shown.

Solution:

Data should generally be shown where they are created and maintained. A second (redundant) presentation only invokes synchronisation problems. Role assignments are therefore no longer shown in dialogue "User" of module Income Taxes.

In dialogue "My profile" of Income Taxes, however, the user's own roles will be shown, as long as this function is not available within the portal.

Situation:

Some features that are now standard features are enabled via customizing flags.

Solution:

If the necessary flags were not yet activated in the GTC, this is now done automatically with the GTC update. The following features belong to this:

• Under Master data / CoA Group, the function "Maintain columns" is always available.
• Under Master data / CoA Group / Maintain columns, the parameters "Permanent differences" and "affecting P&L / affecting OCI" can always be selected.
• For maintenance reasons, very old dialogues such as "Payment Status", "Tax management" and "Tax Tracing" are hidden in the "Reports" area. These dialogues are no longer maintained and have meanwhile been replaced by newer functions / modules.
• Under Master Data / Countries, the simple import for currency conversion rates is always available.
• In the area "Company" the dialogue "Deferred taxes / Report DT Pos" is available.
• In the dialogue B/S comparison (tab Local GAAP - Tax Balance), the button "Calculate Local GAAP" is displayed.
• The period export is always available.
• The table "Change in deferred taxes" is always displayed in the dialogue Summary
• A changelog is always written in the master data area.
• When generating your own reports, the report repository is always used.
• It is always possible to create true-up periods (master data / periods).

Situation:

If the user associates an SAP Remote Function Call (RFC) directly in the "Allocation of the connection information" of a company's master data, an error message appears, as soon as the user saves RFC data after an import (based on a MSSQL database).
For an Oracle database the error occurs, when the user enters the "Import" dialogue.

Solution:

The RFC can be directly associated with a company in its master data dialogue. However, it is recommended, to define a flexible interface structure with the RFC instead. If needed the interface structure can be associated with selected companies in the "Interfaces" section of their master data. But it can as well be defined as a default interface structure such that it may be used in the import of every company.

Situation:

If no balance sheet items have been created for a period yet, a system error message occurs each time when saving the balance sheet comparison and when copying the transaction data.

Solution:

Issue error messages describing the problem. Intercept the system error message.

Situation:

With every import with transaction data, the language entries are completely emptied (regardless of the period) and then rewritten. In addition, the language entries in the period transfer belong to the transaction data.

If an export is now only carried out with master data, but the selection "Overwrite period" is made on the import page, the language entries are completely deleted during the import, but not rewritten, as they are not available in the export file. Thus, all descriptions that the GTC user can maintain multilingually in the master data are no longer available (e.g. descriptions of balance sheet items and countries).

Solution:

The language entries are never deleted during the import. By using selection fields, the user has the option to update the language entries contained there based on the export file to be imported or to add language entries that do not yet exist.

In addition, the language entries are always exported because they belong to the master data.

Situation:

Even when not all autorun jobs (database migrations) could be executed successfully, users may log in to GTC without being pointed to the situation. Functionalities which should have been changed by the jobs may not work correctly. This might have minor or major consequences.

Solution:

New autorun jobs (database migrations) work as follows: User can only log in to GTC when all jobs were executed successfully. Otherwise they cannot log in and get a corresponding error message. The only exception are users with superuser permissions: They can log in, but are directed to page "Master data - Home" and are shown the same error message.

Situation:

The proposed value in line 27, corporate tax column is incorrect.

Solution:

The effect from the local tax column is no longer shown in the proposed value of line 27, corporate tax column.

Situation:

The implementation of a user's unit-dependent permissions may check permissions of the same unit multiple times.

This can lead to the user having difficulty working with the GTC, as the loading times of the dialogues increase (performance).

Solution:

The procedure for checking unit-dependent permissions is optimized in so far, as each unit is only checked once.

Situation:

The status page in the single company area cannot be accessed in a summary period.

The buttons (e.g. Show activities) are not displayed if the milestone " Current taxes" is in the status " finished" or "checked".

Solution:

The status page can also be opened in summary periods and the buttons are always displayed.

Deferred Taxes

Situation:

The proposed values are displayed as 0.00 in the read view of the Rollforward LCF dialog.

Solution:

During the editing of the dialog Rollforward LCF (period/milestones opened), the proposed values are saved in order to display them later in the read view (period/milestones closed).
No calculation is performed in the read view.

The json-smart libraries have been updated.

MVB - IFRS

Only relevant when using the MVB function:

Situation:

An import interface has been configured in the MVB dialogue. In this interface, the checkbox for resetting the differences columns in the MVB dialogue is activated.

In this case, when the import is performed, all differences in the "Other deferred taxes" tab are reset to 0.00 in all periods and all companies, no matter for which company and which period the import is performed.

Solution:

Only the differences of the currently selected company are reset to 0.00 in the currently selected period.

Situation:

During import of a balancesheet structure an error occurs, if languages besides "german" and "english" are configured in the interface structue, but the Excel file does not contain values. The log file contains no hint with regard to the column responsible for the error.

Solution:

Lanuage-dependent values may be empty in Excel. The log file specifies the column responsible for an error.

Situation:

Output location (CATALINA_HOME/logs) and format of the logging are not freely configurable.

Solution:

The output location as well as the output format of the logging can be configured via startup parameters of the Tomcat. If no settings are made here, logging takes place in the previous format by default.

The default output directory has been changed from CATALINA_HOME/logs to CATALINA_BASE/logs.

Further information on configuration can be found in the user guide.

Situation:

The URLs for calling the GTC interfaces have so far started with "<root>/portalapi/...". This does not correspond to the usual convention.

Solution:

The URL has been changed to "<root>/api/...".

This may result in the portal module no longer being able to connect to the Income Taxes module (GTC). Therefore, please check under "Portal/Administration/Module/Income Taxes/Edit" whether the entry "Api URL" already contains the new URL. If this is not the case, please contact your system administrator for further configuration.

Portal / GTC Suite

Situation:

Some user-related data (e.g.: email and phone number) are not transferred from the portal to GTC. As a consequence they cannot be used in error messages with regard to a concurrent page access.

Solution:

User-related data which are needed in GTC and which are available in the portal are transferred from there to GTC.

Situation:

Dialogue "(Sub-) Group Status" allows to download the displayed data as Excel, PDF or print view, whenever "Group strucure" or "Tax group structure" are selected in the "Display" dropdown.
If the entry "List" is selected, the export does not work.

Solution:

Data can also be downloaded as Excel, PDF or print view, when "List" is selected in the dropdown.

Situation:

A user who has the rights "User - Read" and "User - Edit" still cannot edit the users. An error message is displayed. Editing is only possible if the user also has the "Roles - Read" right.

Solution:

Editing users also works without the "Roles - Read" right, only with the "User - Read" and "User - Edit" rights.

Situation:
If processing has not yet been started for a company, it can only be started by clicking on one of the workflow milestones (Actual Taxes, Deferred Taxes, ...). This is not intuitive.

Solution:
To open a company, an alternative is to click on the button 'Start processing'. As long as the company has not been started, the single company dialogues are hidden in the menu tree.

Situation:

Even if the user uses the GTC in the English language, the German user guide is still opened as a direct link from the GTC.

Solution:

If the user selects a language that is not "German", the English user manual is displayed.
The same behaviour applies to the Release Notes.
Both links can be called up at the top right of the header via the "User" icon.

The Axis2 libraries have been updated.

The RestEasy libraries have been updated.

Situation:

Authentication and authorization of REST services is not yet homogeneously implemented.

Solution:

REST services can only be called from authenticated and authorized users. Whithin the GTC Suite users are authenticated via access tokens, otherwise Basic Authentication (username/password) is used.

For data access the user authorizations are checked. Outside of the GTC Suite the user needs the "RestInterfaces (RestUseAPI)" permission in order to call a REST service.

If you are already using REST interfaces, you may need to adjust permissions in the GTC.