Release Notes 22.09.XX (R2/2022)

Situation:

When working with the Report DT Pos, conversions for foreign currencies were calculated in the individual company and deducted from the profit and loss statement.

Solution:

Since there can be no conversion rates for foreign currencies within a individual company, the corresponding column is no longer filled. Moreover, the translations will no longer have any effect on the values of the profit and loss statement.

Situation:

If an export based on an Own Report is executed several times, the report is only calculated once for each company. The same result is then used for subsequent calls of the export.

As a result, any validation value is not re-evaluated.

Solution:

The report is recalculated for each export.

Situation:

In the master data area, users can be assigned rights for the company "---".
In this case, the user does not see any data records under Master data / Companies.

Solution:

In the master data area, the assignment of the company "---" is evaluated in the authorisations as "all companies".

Situation:

Custom reports that pull data from a standard report are not being created properly in Excel.

Solution:

The own reports should be displayed correctly in Excel.

Situation:

A mapping with the balance sheet type "Questionnaire " cannot be assigned to the company.

Solution:

The mapping is saved correctly so that the subsequent import can be carried out.

Situation:

If the language is changed in the Income Taxes module within the "My Data" dialogue, the Income Taxes dialogues and reports are still displayed in the language that was previously set.

Solution:

After changes in the portal dialogue "My data", the Income Taxes-side cache is updated, which causes the Income Taxes dialogues and reports to be executed in the currently selected language.

Situation:

If "Netting (types of taxes without maturity)" is selected for "Netting of deferred taxes" in an company, the "Summary" dialogue ignores the values for tax credits and other LCF segments in the calculation of totals. Only corporate tax and local tax are taken into account.

Solution:

The "Summary" dialogue contains additional rows for the other LCF segments (besides corporate and local tax). The additional rows are taken into account in the calculation of totals.

Situation:

More than one mapping can be stored for an interface structure for enhanced import ("mapping engine") for a specific period. The import, however, will only take one of these mappings into account.

Solution:

For a specific period and interface structure only one mapping can be stored. The user is shown a corresponding notification.

Situation:

From GTC Version 21.07.13 or 22.09.03 onwards it may happen that an error that occurs during an SAP import is written to the log file, but not shown on the GUI.

Solution:

Each error that occurs during an SAP import ist written to the log file and shown on the GUI.

Situation:

Under certain conditions it may occur that the import of the "(Sub-) Group" area has an error which in the GUI is diplayed as an endlessly looping progress bar. This can happen, if in the interface structure the field "Local GAAP correction to tax balance sheet values" is empty, checkboxes "open milestones" and "close milestones" are activated, checkbox "reset milestones" is deactivated and the milestone "Current taxes" of an imported unit is closed.

Solution:

The error is properly handled and shown in the GUI.

Situation:

As soon as a data export is executed for different companies, it can happen that the memory of the system overflows, which can lead to failures when generating the export.

Solution:

During a data export, the data that is no longer needed is removed from the memory, thus reducing failures due to lack of memory.

Interfaces

Situation:

The values of the detailed presentation of the OCI facts in the result sheet are calculated and not saved in an item. Thus, they cannot be imported or exported.

Solution:

These values now have their own positions in the GTC and can thus be imported and exported via reports, REST services as well as in the Tax Questionnaire.

Situation:

A bulk import is to be executed for a period and a part of the companies.

With ticket #130874, the import in the (sub-)group was changed in such a way that an import was only possible if no other user was active in the period. This procedure turned out to be impracticable.

Solution:

A conflict among users only exists if they process companies within the same subgroup. Triggering an import in the (sub-)group area is possible at any time, in case of conflict via the button "Import anyway". 

If an import has been triggered, the dialogues of all subgroup companies are locked for the duration of the import. Here, too, it is possible to bypass the lock via the "Edit anyway" button.
In this case, the users themselves must ensure that the manual entries do not overwrite the imported data and vice versa.

Interfaces

Situation:

If a direct import with a number format was created and then executed, the specified number format was not taken into account during the import. Values with a trailing minus sign were not correctly interpreted.

Solution:

When creating a direct import, the specified number format is taken into account during import. Values with a trailing minus sign are correctly interpreted.

Situation:

With flag SHOW_OBD = 1 the dialogue "OBD" and the report "Tax Investment Book Value" are visible.

If values in foreign currency (e.g. USD) are entered in this dialogue for a foreign company and the report is executed in group currency (e.g. EUR) for the group parent, incorrect values are shown: The exchange rate conversion is done twice.

Solution:

The report contains correct values: The exchange rate conversion is done only once.

Situation:

The "Tax groups" dialogue is called up for a foreign tax group parent.

A large number of NullPointer messages are then written in the log file. As a result, the log file fills up very quickly and becomes confusing.

Solution:

The error handling has been improved at this point so that the log files are not filled up with unnecessary messages.

Situation:

During bulk import with activated robotics automation, it is possible to specify via the interface structure that the tax rates in the "Loss carry forward" dialogue are to be taken over directly.
However, this does not work if the extended mapping is used.

Solution:

Even if the extended mapping is used, the tax rates are taken over successfully, if this has been activated in the robotics.

Interfaces

Situation:

If an invalid PATH_FILESERVER is configured, the (Sub-) Group import will not be carried out. However, no error message is displayed at the GUI.

Solution:

If the (Sub-) Group import cannot be carried out due to an error, the error message is shown at the GUI.

Situation:

The time at which the GTC terminates the connection is set in the code.
As a result, the GTC cannot establish a connection with the external system in some configurations and data cannot be imported.

Solution:

In the ApplicationConfig.properties there is now a new value "REST_TIMEOUT", which can be used to set the time until timeout. The default value is 60 seconds.
If the time is to be changed, a numerical value must be entered. This is specified in milliseconds.

Situation:

After a period copy including transaction data and milestones it may occur that the milestone "Current taxes" of the tax payer of a group cannot be closed.
This happens, if the milestone "Current taxes" in the source period is closed for the tax payer and members of a group and after the period copy the milestone of the tax payer in the new period is reset.

Solution:

A period copy including transaction data and milestone status copies all data which are relevant for milestones (especially the timestamps for the tax group member and the tax group payer).
In a period copy including transaction data without milestone status the milestones are reset and all data which are relevant for milestones are removed (especially the timestamps for the tax group member and the tax group payer).

Situation:

The execution of "Own Reports" may require a lot of main memory. If more than one user calls up "Own Reports" at the same time, these reports are therefore not processed in parallel, but always one after the other.

If "Own reports" are used in the "Data export" dialogue, however, the calls are made in parallel. This can lead to too much memory being used and the execution of the reports and thus the data exports being aborted.

Solution:

A queue is also used in the "Data export" dialogue.
If several users initiate an export at the same time, these exports (and the "Own Reports" behind them) are not executed simultaneously but one after the other.

Security

Situation:

For the library "commons-beanutils", which is integrated via the Struts framework, a security vulnerability is known for the version used so far.

Solution:

GTC includes the most current version 1.9.4 of commons-beanutils which does not have any security issues.

Reports

Situation:

Reports can be marked as favourites in the overview table. Sorting by favourite reports is not possible.

Solution:

In the table header, a sorting option is also offered for the Favourites column.

Interfaces

Import

Situation:

Via the "Import" dialogue in the "(Sub-)Group" area, it is also allowed to import into the "Data Transfer" dialogue if the milestones for current and deferred taxes are already closed. This is generally allowed because this dialogue is not included in calculations within the GTC application.

If several companies ("bulk import") import into the same position, the position values are summed up across all companies on an ongoing basis. This leads to incorrect imported values for the companies.

Solution:

In each company, only values that are assigned to it according the UNITID are stored.

Situation:

If JNDI is set up as database connection, the log file always shows HSQLDB as database type.

Solution:

The actual database type used is displayed.

Situation:

An ATC proxy is configured that does not require user authentication.

When maintaining a connection configuration without user name and password, an error message is displayed.

Solution:

Username and password are now passed to the proxy even if they are empty. The connection can be established successfully.

Situation:

Library commons-net has a security issue in version 3.6 which is included in GTC.

Solution:

GTC includes the most current version 3.9.0 of commons-net which does not have any security issues.

Situation:

When "All log files" have to be downloaded via the corresponding button, the generated zip file cannot be opened or all files are not included.

Solution:

Generating the zip file with all GTC log files works properly again.

Situation:

Dialogue "Validation" (optional add-on function) is part of the tax calculation, but it is not included in a period export.

Solution:

The values of dialogue "Validation" are included in a period export and are part of the import.

Situation:

The current version 6.2.6 of library woodstox-core has a vulnerability of category "High". The library is loaded via the library axis2 version 1.8.0.

Solution:

The application now contains axis2 in its most current version 1.8.2 and woodstox-core in its most current version 6.4.0. Thereby the vulnerability no longer exists.

Situation:

At least one milestone of the current company is set to "finished" or "checked".
A parent unit can be added. An error message appears, but the unit is added anyway.
It is not possible to delete the added unit afterwards.

Solution:

No changes can be made to the parent units if at least one milestone is already closed.

Situation:

When REST services of the portal are called from the IncomeTaxes module via SSL/TLS, they require a certificate that was issued by a trusted certificate authority. They do not support self-signed certificates.

Solution:

REST services of the portal can be called from the IncomeTaxes module via SSL/TLS, even when they are based on a self-signed certificate.

Situation:

The detailed protocol of a (Sub-) Group import does not contaion the unit id, which makes it difficult for the user to assign the log lines to the import lines.

Solution:

The detailed protocol contains the unit id in every line.

Situation:

There is a "Critical" level vulnerability in the current version of the snakeyaml library.

Solution:

By updating the swagger library to version 2.2.7, the vulnerability was closed. In the latest snakeyaml version 1.33, which depends on this, a "High" level vulnerability is still present.
This doesn't represent a security risk in production environments, as the swagger documentation, which includes the snakeyaml library, is used exclusively during development at AMANA.

Situation:

If the function "Copy settings" is used within the toolbox and then "... Export to file" is selected, the landing settings are dragged from the last selected company.

Solution:

The data export takes the landing settings from the country selected in the dropdown.

Situation:

Some reports (eg: "Mass Export GTC-IDs, all") end up in a system failure when no SAP interfaces are used by the customer. The direct import with stored procedure does not work either.

Solution:

Customers who do not use SAP interfaces will not extend the Tomcat installation with the SAP JCo library. The deployment was modified such that no SAP specific code is executed for these customers. Reports and direct import can be executed successfully.

Situation:

If scope "Group structure"is selected for report "Dialogue Current taxes - detailled (non German)", no values are shown for the other units. If different positions are activated for different countries, the report does not contain all these different positions.

Solution:

Values are shown for all units in a comprehensive layout. The report contains all the different positions of all countries.

Situation: 

Selecting the dropdown fields for Reporting Dimensions have no effect on the settings selected for the report. 

Solution: 

The selection of the drop-down fields for reporting dimensions determine the companies selected for the report as usual.

Situation:

1. The interface structure can be used to define that values are to be imported into the differences columns in the MVBS dialogue.

Values can also be imported into difference columns for positions that are not relevant for deferred taxes, although these rows cannot be edited in the dialogue itself. Values imported there cannot be reset afterwards.

2. After the import, all positions in the tree structure are recalculated. The calculated values are only written to the database after an additional save. As a result, the display and the database may differ.

Solution:

• Differences can only be imported if they are also editable in the dialogue itself.
• The function "Reset columns" also affects closed rows.
• The calculated values of the sum positions are written to the database when they are saved for the first time.

Situation:

A security vulnerability has been reported for the batik library for the previously used version 1.14.

Solution:

The library Apache FOP has been updated from version 2.7 to the latest version 2.8. Thereby batik is updated from version 1.14 to 1.16, in which the vulnerability is fixed.

Situation:

The "Deferred Taxes (Balance Sheet Comparison)" line from the "Other" dialog is no longer linked into the TRR due to calculation base 1301031.

Solution:

The "Deferred Taxes (Balance Sheet Comparison)" line from the "Other Dialog" is linked back into the TRR line "Out-of-period Deferred Taxes".

Situation:

For Oracle the database connection cannot be configured via JNDI.

Solution:

Also for Oracle the database connection in the configuration file repository.xml can be set to JNDI. The details of the database connection are defined in the Tomcat file context.xml.

Situation:

Creating comments via the context menu when right-clicking was no longer available.

Solution:

The right-click context menu has been restored. Creating comments via the context menu works as expected.

Situation:

If an error occurs in dialogue "Data export" during the execution of a flexible RFC export, its details are written to the log and a success message is displayed in the browser.

Solution:

The information that an error occurred is also displayed in the browser. The error cause and details are written to the log.

Situation:
The iText library used is outdated and has potential security risks.

Certain old export versions use this library to generate PDF booking vouchers.

Solution:
The library has been removed. PDF exports have been disabled in export versions that are no longer supported. If the export is still configured and a user triggers the export, a corresponding error message is displayed.

Situation:

When an import in the "(sub-) group" area is executed, it can happen that the subsequently displayed protocol is very extensive. Its rendering in the browser might take a very long time or not work at al, which can lead to data inconsistencies.

In addition, this dialogue is typically used for data import for many companies, and, if necessary, the tax calculation executed. However, the companies are not locked for other users. This means they can be processed in parallel.

Solution:

The import in the "(Sub-) Group" area is implemented analogously to the period transfer. While the import is being carried out, the complete period is locked for other users. The user may log out during the import. After the import is completed, the short protocol is displayed in the dialogue. The detailed protocol is available for download.

Situation:

The import is made via the flexible RfC interface.
The interface always resets all values during the import, even if these were not configured in the definition of the interface.

For example, if local GAAP values are to be imported into the Local GAAP column via the flexible RfC interface, the IFRS balance sheet is reset during the import. However, no parameter for the IFRS value was specified in the interface structure and "Reset IFRS" was not activated either.

Solution:

Only the balance sheet is reset that was also activated accordingly in the interface structure.

Situation:

Creating comments via the context menu when right-clicking was no longer available.

Solution:

The right-click context menu has been restored. Creating comments via the context menu works as expected.

Situation:

The local balance is deactivated for the company in the company master data.

When importing, the imported values are displayed with 0.00 in the log.

Solution:

If the local balance is deactivated, the import log shows the imported values correctly.

Situation:

Under certain circumstances, the drop-down lists that control the contents of the reports are displayed in a very verbose manner, making it almost impossible to use the dialogue.

Solution:

The drop-down lists are displayed in a much more space-saving way.

Situation:

In the extended mapping, a condition is stored in the column "Import value" or in the column "Condition" whether the imported value is greater or less than zero.

A csv file is imported via the extended mapping. If an import value with decimal places is specified in the csv file, the conditions are not interpreted.

Solution:

With the csv import via the extended mapping, the condition is applied to the imported value.

For security reasons, FTP imports have been deactivated in the GTC.

Situation:
A security vulnerability has been reported for the Apache Commons Text library for the previously used version 1.6.

Solution:
The library has been updated to the latest version 1.10.0, in which the vulnerability is fixed.

Situation:

Web Services via HTTPS do not work.

Solution:

Web Services can be accessed via HTTPS.

Situation:

If in the dialogue "Validation" no GTC values are available for a validation position, then validation status will not be calculated for this position.

If, on the other hand, no values are available for external data, the calculation of the validation status can be controlled via flags (e.g.: treat NULL as 0.00).

Solution:

If the new flag "VALIDATION_GTC_NULL_VALUE_AS_ZERO" is activated, NULL values from the GTC are treated as 0.00 during validation.

https://docs.amana.de/x/zgzzBg

Situation:

A company cannot open the "Status" dialogue. The error message "The selected entry does not exist: "null" appears.

As a workaround, the status page can be called up in the subgroup area. There, milestones that were not initialised correctly for unknown reasons are automatically repaired when the page is called up. Afterwards, the company can also be displayed again in the single company area.

Solution:

The initialisation of the milestones is also checked in the single company area. This means that the company can be displayed in any case and milestones that have not been initialised are automatically repaired. The workflow of the milestones remains unaffected.

Situation:

The reports of the dialogue "Dialogue current taxes (non German)" always show the current values. Values from snapshots are not displayed.

Solution:

In the "Reporting / Tax Reports" dialogue, the reports of the "Dialogue current taxes (non Germa)" dialogue can now also display values from snapshots.

In addition, all reports that can display snapshot values show in the header whether they are the current values or the values of the selected snapshot.

The xstream library has been updated.

Situation:

If the reclassification column is displayed in the TRR, the line "Effective income taxes (original + deferred taxes)" is not calculated in this column. If the reclassifications / corrections should lead to an effect on the effective income taxes, this was not taken into account in the IFRS column.

Solution:

Starting with the 2017 financial year, the line "Effective income taxes (original + deferred taxes)" is also calculated for the reclassification column in the TRR. The calculated effect is then taken into account accordingly in the IFRS column.

Situation:

When saving the data coming from the STB import, the actions to be performed during a save were performed as defined in the first interface structure. This includes, among others, the checkboxes for resetting, opening and closing the milestones.

Solution:

The interface structure dropdown is ignored when saving the STB import.

Portal / GTC Suite

Situation:

In the portal name-related information are stored under the columns LOGIN, FIRSTNAME and LASTNAME of the database table TUSER. Their maximum permissible length is not compatible with the lengths in the GTC table, which can lead to problems during data synchronization.

Solution:

The name-related table columns in the portal and in GTC have the same maximum permissible length.

Situation:

Reports always show current values. Snapshot values cannot be included in reports.

Solution:

Two new selection fields have been added to the "Reporting / Tax Reports" dialogue. The first selection field lists for the currently selected company all snapshots of the period, the second all snapshots of the comparison period. This can be used to select which data the report should use.

In the table of all reports, a new column "Snapshot" with an activated checkbox shows which reports support the snapshot feature.

The existing reports will be extended with the new feature step by step.