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

Version 1 Next »

Release 5.2.6.0

Released on Oct 08, 2021

New Feature

Priority Key Title Release Note
High SC-841 Display ITSM ticket number as hyperlink in TM Workflow Monitor With this feature, the column 'Ticket ID' from the TM Monitor has been defined as a hyperlink. You can now jump directly from the TM monitor to the assigned Ticket ID in the default web browser.

As a prerequisite for this feature, you must perform the following configuration in the transaction /RTC/TM_IF_CONFIG>ITSM Systems configuration:
* ITSM System: Define the Server path for the ITSM (ex. https://server-path.atlassian.net)
* ITSM System>Work ITEM: Define a new Work Item type for Issue Display as bellow:
Item Type: J2O
Item Description: Jump to Issue
Item path: /browse/
Medium SC-828 Central configuration and usage of import UMODE information via TM TOOLS>Import Tracking With this feature, you have now a central access point to maintain and configure the usage of UMODE import information, via TM>Global Settings>Feature as follows:

- option 'External Umodes' (flag EXT_UMODES):
Impacts now only the TM>Destination configuration process, enabling you to add different clients of the same system to different transport levels within the same TM destination.
Note!
You are no longer required to maintain the table /RTC/TM_OPT, field EXT_UMODES in each system of the TM landscape.
As default, part of the standard process, the UMODE used for import is ALWAYS stored in the log table of the import (/RTC/TM_HLOG), for all the systems.

- new option 'Imp. Tracking UMODES' (flag TRACK_UMODES):
Impacts the TM_TOOLS>Import tracking process, enabling you to use the original UMODE information of the import when adding the transport requests to the personal queue for reimport.
High SC-824 OData Service Create_TR should trigger the TM IF Badi for Updating Jira Issue With this new feature, the TM Integration Framework functionality has been integrated into the OData service for creating a transport request.
If the TM Integration Framework is configured to trigger an ITSM update after the Transport Creation in SAP, via transaction SE10/SE09, the same functionality will be triggered after creating a Transport Request in SAP via the OData service call (sap/opu/odata/RTC/TM_GW_SRV/Transport_RequestSet).
Medium SC-821 Mandatory reason for overwriting collisions With this feature, a new check box field 'Mandatory reason to ignore collisions' has been added in the collision configuration, TM>Quality Assurance>Collisions.
If the flag is set, then a popup window to enter a reason will be displayed at approval, after the collisions are confirmed. The text field for reason is mandatory.

The reason is saved in the TM Actionlog.
Line 1: “<date> <time> <user>(<TM>), Collisions in level <level> for <approval type> are confirmed.”
Line 2: “<date> <time> <reason>”
High SC-812 Create and prepare ITSM Type "SOLMAN" in TM Integration Framework With this feature, the TM Integration Framework configuration has been enhanced with a new ITSM type: SOLMAN.
Medium SC-785 Display content of a SYNCXXXXX request when double-clicking on it in the SyM Synchronization Tree With this feature, you can see the content of an SYNCxxxxx request in a pop-up window, by double-clicking on it in the SyM synchronization tree.
The popup displays information like sync request, object name, object type and description.
Medium SC-779 Add "Import Timestamp" information to the web call for updating a Jira Issue With this feature, the timestamp of the import is transferred to the Jira App, converted to UTC.
This is a prerequisite for the app "SAP Transport Integration for Jira", for enabling the validator "SAP transport imported", allowing you to perform a check on the import status of the assigned transport requests during the transition of a Jira issue.
Medium SC-771 TM/SyM integration - add SyM rollout request to TM action log With this feature, the TM/SyM Integration has been enhanced. You can now see the SyM Rollout Request used for synchronizing a Transport Request in the Transport Action log in TM.
If the Synchronization has been done using the original transport, the message 'Transport was synchronized with Rollout Request &4' is added to the action log.

Note!
In order to enable this feature, the automatic synchronization between SyM and TM must be enabled:
/RTC/TM > Global Settings > Synchronization management tab → TM/SyM Synchronization is configured with 'Automatic Synchronization' checked.
High SC-712 Display ITSM ID and ITSM ticket number in TM Workflow Monitor With this feature, two new columns have been added to the TM Workflow Monitor: ITSM ID and Ticket ID:
* ITSM ID - displays the value of the TM attribute defined in the TM Integration Framework configuration globally (ITSM_ATTR)
* Ticket ID - displays the value(s) of the TM attribute defined in the TM Integration Framework configuration at ITSM level.
High SC-656 Add Workflow Collision Tab to TM-Reporting (Request Lifecycle) With this new feature, you can now display the information about collisions in the Request Lifecycle in TM-Reporting.

Bugs

Priority Key Title Release Note
Medium SC-846 Return code 8 at TR import SR1K900050 (SC v5.2.0.0) when installing SmartChange version v5.2.5.0 Issue:
When installing SmartChange 2019 by importing all transport requests corresponding to SP02 + HF00->HF05 in subset mode, transport request SR1K900050 (v.5.2.0) returns code 8.
Errors from the import protocol:
Program /RTC/CL_TM_CORE_IMPORT_SINGLE=CP, Include /RTC/CL_TM_CORE_IMPORT_SINGLE=CM001: Syntax error line 000012
"The method 'EXECUTE_EACH_IMPORT' has no parameters."
Program /RTC/CL_TM_CORE_IMPORT_UE_AI==CP, Include /RTC/CL_TM_CORE_IMPORT_UE_AI==CM001: Syntax error line 000018
"Field 'IO_IMPORT_REQUEST' unknown."
Program /RTC/CL_TM_CORE_IMPORT_UE_BI==CP, Include /RTC/CL_TM_CORE_IMPORT_UE_BI==CM001: Syntax error line 000020
"Field 'IO_IMPORT_REQUEST' unknown."

Root cause:
Programming error.

Solution:
The program has been corrected.
Medium SC-840 The lock on TM>Global Settings is not released at 'BACK' user command Issue:
The table locks which are set when entering TM > Global Settings in edit mode are not released when pressing 'BACK' button.

Root cause:
Programing error.

Solution:
The program has been corrected.
Medium SC-837 TM Tools > Import Tracking shows wrong Umode values Issue:
TM Tools > Import Tracking shows wrong Umode values, doubling the values in some cases (ex. '22' or '2222').

Root cause:
Programming error in handling scenario CTC = 0.

Solution:
The program has been corrected.
Medium SC-835 TM Tools > right click on System Queue displays option "Delete Queue" Issue:
By trying to delete the system queue from TM-Tools -> Queue Management -> right click on the system queue -> Delete queue, a wrong message is displayed: "Do you want to delete personal queue for user?"

Root cause:
Programming error. The option to delete a queue should be available only for the Personal Queue.

Solution:
The program has been corrected. The option to delete the System Queue by right-clicking on it was removed.
High SC-832 Transport Manager ALV display not correct for approvers when filtering for approver Issue:
By filtering the requests with a specific approver, all transports, which match the approver, are correctly shown, but if in one of these transports an approval field is filled with another value (technical and business approval not done by the same person), the value not equal to the selected value is not shown.

Root cause:
The database contains two entries for each approval (technical/content). If the approvers are different, only the corresponding entry is read.

Solution:
The code has been corrected.
High SC-830 Short dump CNTL_ERROR when running the initial job for SyM>Workbench analysis Issue:
Short dump CNTL_ERROR occurs in program CL_GUI_CUSTOM_CONTAINER=======CP, when running the initial job for SyM Workbench analysis.

Root cause:
Report /RTC/SA_AUTO_SYNC stops with the mentioned runtime error when analyzing objects of type ‘ENHO’ (Enhancement Implementation) only when running in background.
The standard function module SVRS_COMPARE_OBJECTS cannot be executed in the background for ENHO object type.

Solution:
The program was modified, ENHO object types are now correctly analyzed via SyM in background jobs. The ENHO objects are no longer analyzed with function module SVRS_COMPARE_OBJECTS (this FM is mandatory for CDS views mostly).
Medium SC-829 TM Tools > Display of System Group name is limited to 12 characters Issue:
When transports are added to the personal queue (TM Tools > Import tracking: Single system > Add to personal queue > Client search help), the system group name is cut off after 12 characters.

Root cause:
The displayed text for the system group name is limited to 12 characters.

Solution:
The displayed text was increased to 30 characters.
High SC-827 TM Tools>Import tracking - transport is missing after adding a list of transports to the personal queue Issue:
In TM Tools>Import tracking (single system), when adding a list of transports to the Personal Queue, each transport request is added only once to the list.
This is not correct, because if the transport has been imported multiple times, and other transport requests have been imported in the meantime, the correct sequence is not respected.

Root cause:
Programming error. Only the first import of the same transport request is taken into consideration when adding to the personal queue.

Solution:
The program has been corrected.
The consecutive occurrences of the same transport are added to the personal queue as a single entry, with the last import date. The UMode is calculated by cumulating all the UModes, if /RTC/TM_OPT-EXT_UMODES is set, otherwise, it will be empty.
The transport request is added multiple times to the personal queue if there are other transports between the imports.
High SC-791 TM>Destinations>'Delete' destination shows no warning Issue:
In TM>Destinations, when pressing the 'Delete' button for a destination, there is no warning message. The destination is directly deleted.
This happens if the destination is not used in any TM Project. Otherwise, you receive the blocking message:
'Deletion not possible. Destination '&1' is still used in project '&2'!

Root cause:
Programming error.

Solution:
The program has been corrected. A pop-up message to confirm the deletion has been implemented.
High SC-787 TM Status Switcher does not ignore import checks for irrelevant systems Issue:
TM Status Switcher (report /RTC/TM_STATUS_SWITCHER_NEW) does not ignore the irrelevant systems when checking the import Return Code.
If Check import>'Into the following systems' is maintained, the return code is still checked for all the target systems. As a result, the transport request is not switched, if there is one system that does not meet the criteria.

Root cause:
Program error.

Solution:
The program has been corrected. Import related checks have been split into two categories:
- General checks: time since the last change
- System-dependent checks: Return code, Virtual system, Locked systems

The following scenarios can be configured:
* If Check import>'Into all systems' is maintained, the system-dependent checks will apply to all the systems.
* If Check import>'Into one system' is maintained, at least one system must meet the system-dependent criteria in order for the transport request to be switched to the next level.
* If Check import>'Into the following systems' is maintained, all maintained systems must meet the system-dependent criteria.
Medium SC-754 SyM Reset report, /RTC/SA_RESET, deletes all task list entries when having multiple client pairs Issue:
When doing reset on SyM (report /RTC/SA_RESET) and having multiple clients pairs, all task lists for all pairs are deleted.

Root cause:
The task list is not taking into consideration the client-dependent pairs.

Solution:
A new parameter was added on the initial screen to include MAINT client (not mandatory) with default '*'.
The deletion works as following:
- if MAINT client is filled → task list is deleted only for pair (DEV client / MAINT client) defined as a parameter.
- if MAINT client is NOT filled → task list is deleted for all pairs where the DEV client is defined as a parameter regardless of the MAINT client.

Powered by Automated release notes for Jira
  • No labels