Skip to end of metadata
Go to start of metadata

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

Compare with Current View Version History

« Previous Version 4 Current »

Release 5.1.1.0

Released on Mar 05, 2020

New Feature

Priority Key Title Release Note
Medium SC-305 Pass TM server Value in User Exits BEFORE_IMPORT and AFTER_IMPORT Issue:
Currently, there is no way to determine the TM server from inside following User Exits:
• BEFORE_IMPORT
• BEFORE_EACH_IMPORT
• AFTER_EACH_IMPORT
• AFTER_IMPORT

Within a landscape, it is possible to determine which is the TM server that the current system is linked to, only from the Development system or from the TM server itself (but not from a Quality System, for example).

Solution:
The mentioned user exits definition has been enhanced to pass also the value for calling TM server.
The following parameter has been added to the user exits mentioned above:
Parameter name: 'TMS_SID'
Parameter Value: <TM server SID>
Medium SC-254 New column 'Full name' for Author in TM Monitor available Issue:
Display full name (first and last name) for the author of a transport request in the TM monitor.

Solution: A new column 'Full name' has been added, with the full name of the SAP user.
Medium SC-232 Enhance systems settings to define Import mode 'Import single/import all' at system level Issue:
Customer should be able to define import type (single or subset) for individual systems (e.g. BW systems). There are specific cases where it is necessary to have a different import type for specific TM landscapes, especially for BW systems.
Currently, the setting is global, per controller, which sets the import mode option for all landscapes.

Solution:
More flexibility to handle those scenarios is provided with a customizable option for individual systems.
The System Attributes have been enhanced with the new field: "Import Mode".
Possible Values:
- Default/Standard
- Single
- Subset
The "default" option means that the global setting will be used.
Medium SC-192 Make 'Display User Exits' functionality available in TM System and Groups Issue:
When the "User Exists" are in edit mode, they cannot be viewed by another user.

Solution:
The user can now display the "User Exits" even when these are open in edit mode by a different user:
1. System and groups -> right click on any SID -> Display User Exits
2. System and groups -> click on the glasses icon (from the menu) -> User Exits
Medium SC-82 Using Mass Transport Requests deletion in TM Monitor display one notice popup for all Transport Requests Issue:
If a user wants to delete more than one Transport Request simultaneously he has to fill individually the subject and text for each Transport Request.

Solution:
If the user checks the "Delete multiple requests" box from the pop-up window, all the selected transports will be deleted at once. The same email will be sent to all authors. This checkbox can be used also if the user wants to cancel the deletion for all the transports. He will also receive a single cancel pop-up window.

Bugs

Priority Key Title Release Note
Medium SC-299 Short dump ITAB_ILLEGAL_SORT_ORDER - /RTC/CL_TM_SECURITY_OPTIONS===CP in Quality Assurance Issue:
A short dump occurred in method /RTC/CL_TM_SECURITY_OPTIONS->READ_SPECIAL_ASPECTS_TEMPLATE when pressing quality assurance button.

Root cause:
Programming error.

Solution:
The program has been corrected.
Medium SC-280 Error message "No valid TM target found" at release of transport request Issue:
This error does not let the user to release into STMS if no TM destination is available. This also happens when the source client of transport request is not defined as a source client in any TM destinations.

Root cause:
Restriction from the product.

Solution:
The restriction has been replaced by a check if the user has authorization to release outside TM.
In case of no destination available a check is done if the user has authorization to release into STMS. If so, a popup will show up to ask user if it's sure to release outside of TM.
Medium SC-258 Wrong SAP version in SmartChange > TM-Help > System Info Issue:
The ServicePack for SAP Basis Component are displayed wrong in SmartChange > TM-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 were 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 a SAP S/4 Hana, these 2 lines (Hana Version/ServicePack) will be hidden.
High SC-237 Short dump APCRFC_OVERLAY_ERROR in User Group administration Issue:
Short dump occurred when entering in edit mode for User group administration. Shortdump occures at call of FM /RTC/TM_GET_SIGN_USER

Root cause:
Programming error.

Solution:
The program has been corrected.
High SC-233 Report /RTC/TM_RESET does not clean all tables Issue:
Executing report /RTC/TM_RESET does not clean transparent tables for the /RTC/TM* sub-packages.

Root cause:
Programming error.

Solution:
The report was changed and now clean also the transparent table from sup-packages of the /RTC/TM*.
Medium SC-217 Wrong transport order of the import in /RTC/TM_TOOLS > Import Tracking Issue:
When using the IMPORT SUBSET functionality, more transport requests will have the same timestamp of the import in the ALOG file. Therefore, the Import Tracking tool will fail in restoring the correct order when creating the personal queue.

Root cause:
For this particular case of using import subset, the import timestamp is not enough to establish the order of the import of transport requests into a system.
SAP uses the short timestamp for the log, which in this case is not unique per transport.

Solution:
A second sorting criteria has been added, which will make the difference for those transports with the same import timestamp.
Medium SC-208 Displayed message text in TM User Exit AFTER_WF_ASSIGNMENT is fragmented Issue:
The message text is separated at the 50th position. As result of this sometimes a word will be separated in two parts and the second part is displayed in the next line.

Root cause:
Programming error.

Solution:
Display the message separated by existing spaces not by 50th position.
Medium SC-186 Incorrect text for the Return Code field in the "Import tracking: Single system" selection screen Issue:
In the "Import tracking: Single system" selection screen the text for the Return Code field is incorrect.

Root cause:
The description of the parameter on the selection screen changed by mistake.

Solution:
The description was corrected.
Low SC-185 Mass Approval stopped with error 'Approval table of TR1 and TR2 are not unique' Issue:
The error occurs with mass approvals using different user groups. If the selected TR's for approval are from different user groups the approval is stopped with error :
"Approval table of TR1 and TR2 are not unique"

Root cause:
Product restriction: All selected transport requests [TR's] must have the same user groups.

Solution:
The program has been modified and product restriction has been moved. If the user is authorized to approve the transports individually, he can approve them together as well.
Medium SC-66 Using ‘Import into systems’ option in Report /RTC/TM_STATUS_SWITCHER does not work Issue:
'Import into systems' parameter is available on the selection screen of the switcher in Report /RTC/TM_STATUS_SWITCHER. Selecting the 'Into all systems' option, the transport request is wrongly switched, although transport requests was not imported into all target systems , but at least in one target system.

Root cause:
Program error.

Solution:
The program has been corrected.
With the /RTC/TM_STATUS_SWITCHER is now possible to switch transport requests which have been imported into all target systems or into at least one target system, based on selection parameter.

Powered by Automated release notes for Jira
  • No labels