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

Released on Mar 05, 2021

New Feature

Priority Key Summary Status
High SC-625 With this feature, you are now able to jump into the SM Task List from TM Monitor, if the TM/SM Integration is configured. This offers you the option to mark the transport request(s) as "Sync finished" in the SM tasklist, within the same session.

The TM Monitor toolbar button "SyM" has been enhanced. The following menu buttons are available:
"Analysis results" - which jumps to SM Object Comparison, as before
"Task List" - which jumps to the SM task list, prefiltered with the Transport Request(s) selected in TM Monitor

Authorization needed for the "SyM" button (authorization object ZRTC_TM):
* FV: Foreign requests: Analysis of Requests
* V: Own requests: Analysis of Requests 		Done
High SC-610 With this feature, you can manually add multiple external transport requests into the TM Workflow, via TM Monitor>Add request.
Previously, this was only possible for transport requests already imported into the SAP system (existing in table E070) via the F4 search help in the popup "Selection of new requests".
Now, the "Multiple selection" button with the option to add any transport has been added.
Please note that the transport files for the transport requests to be added must be available in the transport directory of the TM Server. 		Done
High SC-575 With this feature, you can now set up TM/SM Integration to automatically mark transports as "Synchronized" in the TM Monitor, after being synchronized in SM (marked as "Finished" in the SM Task List).
You can activate this feature via the TM Menu: Smartchange>Settings>Global>Synchronization Management tab, by checking the new checkbox "Automatic synchronization".

When saving the configuration, the following actions happen in the background:
* the event Z_TM_SA_UPD_SYNCH is created and the job Z_TM_SA_UPD_SYNCH is scheduled to run periodically on the TM Server, triggered by the event.
* the information regarding the TM/SM integration is saved in every DEV SyM system, in table /RTC/SA_TM_CONTR
* trusted RFC destination is created in SyM DEV, to allow access to TM Server.

Note:
If TM Global Settings>Synchronization Management> Checkbox "Synchronization must be confirmed" is flagged and you have the proper authorization (detailed below), you can also manually mark a transport request as synchronized in TM. Nevertheless, please consider that this manual "Sync" action in TM Monitor has no background check on the transport request status in the SM task list.
Authorization needed for the manual "Sync" button display in TM Monitor ((authorization object ZRTC_TM):
- FP: Foreign requests: Confirm Sync for Requests
- P: Own requests: Confirm Sync for Requests 		Done

Bugs

Priority Key Summary Status
Medium SC-666 Issue:
Dump CONVT_OVERFLOW occurs during TM_TOOLS>Adjustment of import database (TM-System) when table /RTC/TM_HLOG contains more than 255 entries.

Root cause:
Programming error.

Solution:
The program has been adjusted. The variable data type has been increased from INT1 (max 255) to INT2 (max 32767) 		Done
Medium SC-664 Issue:
Once the TM/SM integration is activated, you can jump from the TM Monitor into the SM Object analysis for specific transport request(s), by selecting the transport request(s) in the TM Monitor and pressing "SyM">"Analysis results".
If the SM configuration contains several system pairs for the same 2 systems (ex. 100-100, 200-200, 300-300), a popup appears allowing you to select which system pair to use for the SM analysis.

This "Synchronization analysis" popup is not displaying the correct system pairs to choose from, even though the analysis is executed for the correct pair.

Root cause:
Programming error.

Solution:
The program has been adjusted. The filtering of the SM pairs displayed in the popup is based on the source client of the analyzed transport requests. 		Done
High SC-650 Issue:
The report /RTC/TM_REORG_IMP_QUEUES for the reorganization of Personal Queues/ System Queues has a wrong log output.
The log for cleaning up import queues shows all deleted transports for the previous queues, under the current queue information. This makes the log unreadable and difficult to identify the transports belonging to each queue.

Root cause:
Programming error.

Solution:
The program has been corrected. 		Done
High SC-649 Issue:
The "Import" button for Personal Queue from /RTC/TM_TOOLS>Queue Management is not shown after pressing "Start-Check".

Root cause:
Programming error.

Solution:
The program has been corrected. 		Done
High SC-647 Issue:
When trying to approve an external transport request, possible collisions with other requests are displayed.
If you try to expand some of the subtrees to see more details, you get the error message: 'Error retrieving data. Please recalculate the collisions'.

Root cause:
When the collisions for a transport request are calculated based on the Cofile and Data file (meaning the transport is external and has not yet been imported into any TM connected systems), the TM Monitor signals the collisions with a specific Collision Icon.
This means that there are some technical limitations in determining the collisions - The Object Keys cannot be read for external transports from the transport files. This information is decrypted only during import.

Solution:
The handling of Object types 'TABU'/'VDAT'/'CDAT' for external transports (no key information) has been reviewed and improved.
For external TR containing TABU entries, collisions can be detected with other VDAT/CDAT entries already existing in TM Monitor and can be expanded at the object level.

Note:
Not all collisions can be detected for external transports, due to the limitation of not having the object key information at this step:
- External TR contains VDAT - Collisions can only be detected with other Internal/External VDAT entries already existing in TM Monitor
- External TR contains CDAT - Collisions can only be detected with other Internal/External CDAT entries already existing in TM Monitor
- External TR contains TABU - Collisions can only be detected with other Internal VDAT/CDAT entries already existing in TM Monitor 		Done
High SC-646 Issue:
In the SM>Task list screen it is not possible to export the content of the task list.

Root cause:
Not implemented.

Solution:
The "Export" button has been added to the ALV toolbar. 		Done
Medium SC-644 Issue:
Wrong text is displayed for message information 'Please maintain in global TM settings the work clients'. This message is output when entering the /RTC/TM transaction for the first time.

Root cause:
Typing error for the message information.

Solution:
The text error was corrected. 		Done
Critical SC-643 Issue:
In SM>Customizing Object Comparison, when double-clicking on table contents, no relevant table contents are output. The message 'No entries available!' is displayed.
In the MAINT system, the following dumps are generated:
* CALL_FUNCTION_REMOTE_ERROR in object /RTC/SA_CL_CLUSTER_OP ========= CP
* XML_FORMAT_ERROR in object /RTC/SAPLCOM_GENERATE

Root cause:
Programming error.

Solution:
The program has been corrected. 		Done
High SC-628 Issue:
Once TM/SM integration is activated and there is a change on the TM Global Settings if the "Synchronization must be confirmed" field is active, the field is deactivated. This means in TM Workflow monitor the column "Synchronized" and button "Synchronize" from TM/SM integration are not displayed.

Root cause:
Programming error.

Solution:
The program has been corrected. 		Done
High SC-619 Issue:
By pressing the "Cancel" button for the "Repeat check" functionality in the TM Monitor>Personal Queue, the system will still perform the check.

Root cause:
Programming error.

Solution:
The program has been corrected. 		Done
High SC-618 Issue:
Report /RTC/TM_STATUS_SWITCHER does not ignore locked systems. If the switcher is run with the option "All systems" (switch TRs if import has happened into all target systems in the current transport-level) and one of the target systems is locked, the TRs will not be moved into the next transport level.

Root cause:
Works as designed. The locked systems were not handled differently.

Solution:
The switcher has been enhanced. In the selection screen a new checkbox has been added, allowing you to ignore the locked systems.
The default behavior for already scheduled switchers remains as it was.
In order to use the new feature, the switcher job must be rescheduled, modifying the program variant accordingly. 		Done
High SC-606 Issue:
In SM>Task List, the release time is not updated properly sometimes, '00:00:00' being displayed instead.
How to reproduce the error:
Task List is updated via the SM - Object Analysis Initialization Job (SM>Sytems>MAINT>Object analysis job)

Root cause:
Programming error

Solution:
The program has been corrected. 		Done
Medium SC-598 Issue:
The total number of transport requests in History, displayed on the initial screen of TM, does not correspond with the total number of transports actually displayed in the TM History tree.

Root cause:
A program error in the status switcher report /RTC/TM_STATUS_SWITCHER, when moving transports into History.

Solution:
The program has been corrected.
The implemented solution ensures that the transports switched to History from this moment on are counted correctly. 		Done
High SC-589 Issue:
In the TM Monitor, with TM/SM integration configured, if SM has more than a system pair configured, external TRs analysis must jump to the correct SM pair.
This is important especially if TRs contain objects which are client-dependent.

Root cause:
Programming error.

Solution:
Once the SID of TR is not found as pair, display all system pairs available on the screen to choose the pair to be analyzed, filtering by the source client of the transport.
Note!
TR from an external system is released and it is added to TM. SyM analysis will only be executed once TR is imported into the SM MAINT system. → TM/SM integration for SyM overview is displayed empty until import occurs. Additionally, all pairs are displayed in the integration due to unawareness of in which client is going to be imported. 		Done
High SC-547 Issue:
Program /RTC/SA_TASKLIST_INIT, used for massive initialization of SM Task List, has the following shortcomings:
- while updating the task list to status "Finished", the transports remain with an empty status
- missing "delete from task list" functionality
- missing authorization check for running the report

Root cause:
Program error

Solution:
The program has been modified.
A new option on the selection screen has been implemented to allow deletion of task list content.
For running the report, authorization to reset is needed (authorization object ZRTC_SA):
R - Reset Activities 		Done

  • No labels