Ticket | Category | Dialog | Release Information | Patch |
---|
126674 | Interfaces | Import | 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. | - | 126608 | Portal / GTC Suite | Users | 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. | - | 126198126596Interfaces | Usability / Performance | ImportOthers | 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. | - | 125772 | Company | B/S Comparison | 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 messageSome 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).
| - | 126198 | Interfaces | Import | 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. | - | 125772 | Company | B/S Comparison | 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. | - | 104772 | Interfaces | Period transfer | 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. | - | 93752 | Usability | --- | 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. | - |
|