Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Release 5.1.2.0

Released on May 08, 2020

New Feature

Priority Key Title Release Note
Medium SC-307 Logging improved for the distribution by Loader /RTC/TM_LD_10 Issue:
Program /RTC/TM_LD_10 distributes transport requests to a number of transport manager systems. If one of these systems hangs, the distribution program also hangs. It takes quite a long time until the RFC timeout terminates the connection. Meanwhile, the other functioning systems are not supplied. The log of program /RTC/TM_LD_10 does not show which system is currently being supplied or is hanging.

Solution:
The program has been enhanced. If the RFC PING to a remote destination fails, the distribution to this system is aborted and the processing moves on to the next system. The return messages from the ping are recorded in table /RTC/TM_LO3.
Medium SC-190 Mass approval for packages Issue:
As a user a want to have the possibility to approve multiple packages at the same time, if the packages have the same approval table structure.
Currently, the approval functionality was designed for only one package at a time.

Solution:
The program has been enhanced.
Medium SC-181 Batch user maintainable for import jobs Issue:
When creating the jobs for the import scanner and the job reorganization in the global settings, a field is required in which the batch user for the job can be given.
At the moment, after the job has been created from TM, the user has to edit it manually in SM37 in order to change the batch user in the step of the job (currently always the logged-in user).

Solution:
When creating a job from the TM settings, a new field is shown in the popup for job creation: "batch user". The user can enter an SAP user name, that will be used as the author for the step of the job.

Bugs

Priority Key Summary Release Note
Medium SC-353 Wrong authority check for critical objects Issue:
The authority check for critical objects doesn't work properly at TR release

Root cause:
The authority check is done in TM server not in development system

Solution:
Program was corrected
Medium SC-339 /RTC/TM_STATUS_SWITCHER is not switching with virtual systems Issue:
Standard switcher /RTC/TM_STATUS_SWITCHER is not moving transport requests to the next level when virtual systems are involved.
For example, if there is only one system in the current level, and the system is a virtual one, no import flag will be set, as no system queue can run for a virtual system. Therefore, the switcher will never move the transports to the next level.

Root cause:
Programming error.

Solution:
The program has been corrected.
Program /RTC/TM_STATUS_SWITCHER offers now a selection parameter that allows activating the checks that were previously done for the virtual systems if needed. By default, the program will run with the new functionality - virtual systems are ignored by the switcher.
Medium SC-338 Wrong SAP version displayed in System info Issue:
The ServicePack for SAP Basis Component is displayed wrong in SmartChange > Sync Management-Help > System
Info for NW versions greater than 7.31.

Root cause:
The name for SAP Basis Packages for NetWeaver Versions greater than 7.31 was changed by SAP.

Solution:
The program has been corrected. Additionally, now are displayed also the Version/ServicePack for SAP S/4 Hana Systems. If the system is not an SAP S/4 Hana, these 2 lines (Hana Version/ServicePack) will be
hidden.
Medium SC-335 Wrong message "No authorization to access the Task List" displayed in the task list Issue:
When the Task List is empty for a system pair, trying to access it triggers the misleading message "No authorization to access the Task List".

Root cause:
This was due to a program error.

Solution:
The program has been corrected:
- The message "No authorization to access the Task List" means there are entries in the Task List that the user is not authorized to access.
- The message "No data found" means there are no entries to be displayed in the Task List.
Medium SC-334 Dump GETWA_NOT_ASSIGNED when deleting user from user group Issue:
If an SAP user is deleted from the system, a dump GETWA_NOT_ASSIGNED occurs when trying to delete this user from the Synchronization Management user group it belonges to.

Root cause:
Programming error.

Solution:
The program has been corrected.
Medium SC-325 Wrong name or name missing in column "Author full name" of TM Workflow Monitor Issue:
The new column "Author full name" introduced with HF01 is not described properly.
Also, when the transport requests in the TM Monitor originate from different clients, the full name of the owner cannot be identified.

Root cause:
Programming error.

Solution:
The program has been corrected.
The owner's name is read from the source client of the transport request.
The names and translations of the columns "Author" and "Author full name" have been adjusted.
High SC-318 Title is showing old name "SyncAssist" Issue:
Synchronization Management (SyM) is still being shown as SyncAssist (or SA) in several places.

Solution:
The texts for SyM were corrected:
- 'SA' was replaced with 'SM';
- 'SynchAssist' was replaced with 'Synchronization Management'.
Medium SC-314 Wrong Synchronization Management version displayed in System info Issue:
In Synchronization Manager > Sync Management > Help > System info, the wrong SmartChange version is shown after the import of SR0K900051 SmartChange (Service Pack v5.1.0.0).

Root cause:
Packaging error during the rollout process of SRK900051

Solution:
The rollout procedure has been corrected. Starting with SmartChange (Service Pack v5.1.2.0), the correct Smarchange version is shown again.
Medium SC-306 Slow performance due to faulty /RTC/TM_TR_DISTRIBUTOR step in @@ Job Issue:
The system queue import job collects a lot of transports that are not discarded in step /RTC/TM_TR_DISTRIBUTOR. Because of this, the performance of the job/TM is affected.

Root cause:
Programming error - The transport requests are distributed back to the original system as well.

Solution:
The program has been corrected.
High SC-302 Syntax error "Field CMP_EXCEPT-EXPTREASON unknown." using SAP Hana 1909 or higher Issue:
Report /RTC/SA_RSCMPEXP has syntax error "Field CMP_EXCEPT-EXPTREASON unknown."
The error occurs during the installation of transport SR0K900040 SmartChange (Repository v5.0.0.0) on S/4HANA 1909.

Root cause:
Standard SAP table CMP_EXCEPT has been deleted in S/4HANA 1909.

Solution:
The program has been corrected.
High SC-301 Double entries in the task list for transport requests and its tasks Issue:
The tasklist shows both the transport request and its tasks for customizing transports.
The error always occurs when the Synchronization Manager configuration or connection is carried out [again] (e.g. after a maintenance system has been rebuilt) for a system pair.

Root cause:
Program error in the initial analysis job for customizing transport requests.

Solution:
The program has been corrected.
Medium SC-264 Responsible User not updated Issue:
Responsible User is not updated when the manual adjustment process is done.

Root cause:
Programming error.

Solution:
The program has been corrected (new validations on status, user group and lock user when the synchronization status is changed in: "In Progress", "For Update", "Adjusted")
Medium SC-257 Transport could not be add to workflow with message "No request corresponds to the selection." Issue:
If you delete a transport request from TM monitor/remove it from the workflow, and then you want to add it again in the monitor manually, using the search help, you receive the message: 'No request corresponds to the selection'.
This error does not let the user select a request which has been deleted using the F4 search help.

Root cause:
Restriction from the product.

Solution:
The restriction has been removed.
Medium SC-256 Wrong message: "Transport was not scanned on Export" Issue:
In case Return Code ForeCast (FCFC) is active on the system and you release an empty transport, the RCFC popup message 'Transport xxx was not scanned on export' is misleading. In the case of empty transport, the message should be: 'Transport xxx does not contain any objects.'

Root cause:
Programming error.

Solution:
The program has been corrected.

Powered by Automated release notes for Jira
  • No labels