Page Comparison

Situation:

When importing with the Mapping Engine and automatic creation of comments, "Import (EXT)" is written into the "comments" field. This text is not configurable.

Solution:

The content of the "comments" field can be controlled by the import. For example, '"Import (EXT): " += $5' additionally writes the value of the fifth import column into the "comments" field.

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.

The GTC is operated as the "Income Taxes" module in the GTC Suite environment:

The URLs for registering with the portal will henceforth be governed by the Tomcat startup parameters:

Always necessary:
-Dincometaxes.url.base=<URL of the module>
-Dincometaxes.url.portal=<URL of the portal>

Optional to specify a different API address:
-Dincometaxes.url.api=<URL of the API of the module>

Optional for static registration required:
-Dincometaxes.clientId=<string from the portal - ClientId>
-Dincometaxes.clientSecret=<string from the portal - ClientSecret>

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.

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:

Using the bulk import, it is possible to import values for several companies hanging under the selected company at once. However, only the consolidated companies are taken into account.

Solution:

In the definition of the interface for bulk import, the import behaviour can now be controlled.
For this purpose, the user is provided with a new checkbox "Include non-consolidated companies in import".

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:

The import robot of the (sub-) group import dialogue supports the mostly automatic processing of transaction data of companies. Currently, tax rates for LCF, for example, can be transferred.

Solution:

Further values are to be set automatically:
- LCF: "Gross amount long term usable" from "Gross amount"
- Others "Adjustments related to other periods": proposed values for "deferred taxes (balancesheet)", "Unrecognised deferred tax asset (without loss carry forward) P&L" and "Unrecognised deferred tax asset (loss carry forward)"
- Current taxes inland and abroad: proposed values für equity

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:

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.

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:

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.

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:

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.

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

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:

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.

Interfaces

-

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:

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).

Design / GUI

Situation:

The Report Repository window was too small, so it was necessary to scroll in the window to use buttons.

Solution:

The contents of the window were rearranged so that all functions and information are directly visible.

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.

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.

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.

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:

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:

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:

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:

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:

In the "Fast entry" dialogue and when deleting flags, an input of "<delete>" indicates a deletion process. In GTC, however, critical special characters (such as less/greater) should be avoided whenever possible.

Solution:

In the "Fast entry" dialogue and when deleting flags, an input of "delete" indicates a deletion process.

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:

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:

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:

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.

Design / GUI

Situation:

The sequence of the menu items under "Master data" does not correspond to the usual processing sequence.

Solution:

The dialogues under the menu item "Master data" are sorted in the order in which a user usually works on them.

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:

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:

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:

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:

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:

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:

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

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.

Interfaces

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.

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:

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:

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:

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:

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:

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 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:

Web Services via HTTPS do not work.

Solution:

Web Services can be accessed via HTTPS.

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.

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

The xstream library has been updated.

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.

Situation:

The GTC can be configured to automatically update the database when the Tomcat is started (flyway).

Even if not all database updates have been executed successfully, users can log in to the GTC and work with it without being made aware of the fact. Certain functions that should have been changed by the updates may then not work correctly: this can have small or large damaging consequences.

Solution:

Users can only log into the GTC if the database updates were all successfully executed on server start-up. If this is not the case, the user receives a suitable error message and cannot log in.

Users with superuser rights are an exception: They can log in, but after logging in they are directed to the page "Master data - Home" and also see the error message there.

Situation:

When a partnership is newly created, the milestone ‚Current Taxes' is set to "Plausible" after assigning a parent company.

Solution:

The milestone status does not change when new companies are created, the milestone remains in the status 'not started'.

Situation:

By default, the connection details to the database are stored in a repository file of the deployment. For this purpose the war file must be unpacked, modified and packed again.

Solution:

The installation process is simplified. By default, the repository file of the deployment contains a JNDI designation. The connection details for this name are maintained in the file context.xml of the Tomcat installation (and by that independent of the deployment).

An interface with four end points was created to read out master data. These endpoints can be used to export periods, companies (in varying degrees of detail) and superior units for a company.
The interface uses REST technology and is only available in the context of the GTC Suite.

The contents can only be accessed if the calling other party has the necessary permissions:
* RestExportPeriods (periods)
* RestExportUnits (companies in low level of detail)
* RestExportUnitDetails (companies with a high level of detail and higher-level units)

The interface is used by the Tax Balance module.

Situation:

The calculation of line 23a is not correct.

Entries in line 39b are not saved.
The effect from line 39a is included with the tax rate of the group parent in line 40.5.

Solution:

The calculation of line 23a no longer includes line 23d.
The names of lines 39a and 39b have been adjusted. Entries in line 39b are saved. The tax bases (e.g. 39a and 39b) multiplied by the tax rate of the company are included in the calculation of line 40.5.

Situation:

In the print view of the balance sheet comparison (in one of the tabs where differences can be entered), not the values but the item IDs of the respective balance sheet item is output for the input fields of the differences.

Solution:

The print view of input fields shows the entries and not the item ID.

Deferred Taxes

Situation:

Constellations exist in the loss carry-forwards, especially in connection with the utilisation/addition (development VV), tax rate changes and valuation allowances, which are not correctly reported in the TRR.

Solution:

The effects from the loss carry-forwards are shown in the TRR in the correct lines.

Situation:

It may happen that the own milestones are not displayed when selecting "Group structure" in the dialogue "(Sub-) Group / Status". In addition, it may occur that the selected company is not included in the table with the milestones of all depending companies.

Solution:

The own milestones are always displayed in the dialogue "(Sub-) Group / Status". The selected company is always included in the table with the milestones of all depending companies.

In the table with the milestones of all depending companies the sub-group milestones of the current company are included if it is the top sub-group.

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:

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.