Page Properties |
---|
|
Version | 5.1.3.0 | Date | Jul 24, 2020 | Description | SmartChange 2019 SP1 HF03 | Features | 3 | Bugs | 7 |
|
Release 5.1.3.0
Released on Jul 24, 2020
New Feature
Priority | Key Product
Transport Management
Priority | Title | Release Note | Components | Reference |
---|
Image Modified |
SC-435 | Enhancement of TM>User Settings to change default width of navigation tree for TM Monitor | Issue: Optimize Left-Side Tree in the TM Workflow-Monitor. The minimum width of the tree cannot be set less than 300 in the SmartChange>Settings>User Setting>Width navigation tree. Optimize the columns width of the tree according to column content. Solution: The minimum width allowed for User Settings>"Width navigation tree" can now be set in transaction /RTC/TM_OPT, field TREE_WIDTH. If this value is not configured, then the default minimum value is 300. The width of the tree columns is dynamically optimized according to column content. | Configuration, UI | SC-435 |
Image Modified |
SC-401 New function to export collisions in TM Monitor>Simulate collisions | Issue: Add possibility to export collision entries to an excel file. Solution: A new button "Export collisions" added to TM Workflow-Monitor>"Simulate collisions" window. Using that function all collisions will be exported to an excel file. | Quality Assurance, UI | SC-369 |
Image Added | Enhance functionality of TM Monitor>Simulate collisions to allow multiple selection | Issue: To have a better overview for Release Manager, the check of collisions function is enhanced to use for multiple transport requests. Further the button name was changed from "Show collision objects" to "Simulate collisions". Solution: The program was changed to allow multiple line selection. |
Image Removed 369 New function to export collisions in TM Monitor>Simulate collisions | Issue: Add possibility to export collision entries to an excel file. Solution: A new button "Export collisions" added to TM Workflow-Monitor>"Simulate collisions" window. Using that function all collisions will be exported to an excel file. Bugs
Priority | Key | Title | Release Note |
---|
Image Removed | SC-439 | In the "TM Monitor>Simulate collisions" function the other tabs are not hidden | Issue: The button "Simulate collisions" in TM Workflow-Monitor checks only collisions, but displays beside the collision tab also tabs for Special Aspects, Special Objects and Dependencies. Root cause: Programming error Solution: The program was corrected Image Removed | SC-410 Fixed Bugs
Product
Transport Management
Priority | Title | Release Note | Release Note Solution | Components | Reference |
---|
Image Added | Job fields values are cleared, if wrong batch user entered | Issue: When creating a job in TM>Global settings for 'Reorganisation of import queues' or 'Import scanner', popup fields are cleared in the following situation, if wrong batch user was entered: - changing job period
- error message for validation of the batch user
- canceling the next message
Root cause: Validating the batch user name at the job creation. Clearing of the fields on init of the screen. Solution: Validating the username before job creation without clearing the fields. | | Configuration, UI | SC-367 |
Image Added | Loader /RTC/TM_LD_10 does not respect export order | Issue: Loader LD_10 does not respect the export order when distributing transport requests to configured TM servers. This is an issue when the loader is configured to add the TRs in status "Current" and the System Queues scheduled on the target TM server started, while the loader is still running. In this situation, the already loaded transport requests will be picked up by the system queue. Therefore, there will be two subblocks of transports, each sorted according to the export timestamp; overall, however, the import order can be wrong. Root cause: Programming error Solution: The program has been corrected. The transports will be distributed according to the export timestamp. |
Image Removed 404 "Page not available" error, when selecting TM help>create message 410 |
Image Added | In the "TM Monitor>Simulate collisions" function the other tabs are not hidden | Issue:
|
Selecting TM help>"create message" leads to an error "Page not available" The button "Simulate collisions" in TM Workflow-Monitor checks only collisions, but displays beside the collision tab also tabs for Special Aspects, Special Objects and Dependencies. Root cause:
|
The URL to create message was changed. Programming error Solution: The |
URL . Image Removed 367 Job fields values are cleared, if wrong batch user entered 439 |
Image Added | Import information not updated in /RTC/TM_SCPT table | Issue:
|
When creating a job in TM>Global settings for 'Reorganisation of import queues' or 'Import scanner', popup fields are cleared in the following situation, if wrong batch user was entered: - changing job period - error message for validation of the batch user - canceling the next message Root cause: Validating the batch user name at the job creation. Clearing of the fields on init of the screen. Solution: Validating the username before job creation without clearing the fields. Image Removed | SC-327 | Synchronization doesn't update the objects counters on customizing | Issue: The view in Customizing IMG tree is faulty after objects being synchronized. Counters were not being updated correctly as the entries were still being displayed on the column 'only in Maint' instead of "Equal Records" or "Different Records" columns. Root cause: Job that updates these information wasn't being triggered correctly after the import. Solution: The program has been adjusted. Image Removed | SC-326 While several System Queues are running in parallel, sometimes feedback regarding return code and import flag is missing in /RTC/TM_SCPT, even though the transports have been imported. This causes the next System Queue import job to reconsider the transports for import. Root cause: Programming error. Solution: The program has been corrected. System queue generation and preparation for import for System A should not lock/change entries already considered for import in other system queues. If a stop mark entry exists in /RTC/TM_SCPT for system B, it means that System Queue for system B is currently running and the entries before the Stopmark should not be locked/modified by System A. | | Queues/Proposals | SC-189 |
Image Added | "Page not available" error, when selecting TM help>create message | Issue: Selecting TM help>"create message" leads to an error "Page not available". Root cause: The URL to create message was changed. Solution: The URL was corrected. | | UI | SC-404 |
Product
Synchronization Management
Priority | Title | Release Note | Release Note Solution | Components | Reference |
---|
Image Added | Dump SYNTAX_ERROR in program /RTC/SAPLSA_TAB_CMP on S/4HANA 1909 | Issue: |
- - Error during installation of transport SR0K900040 (SmartChange 2019
SP00)
|
- - Dump SYNATX_ERROR during Customizing analysis in SM (initial analysis)
|
- - Dump SYNTAX ERROR when trying to display the "Details" tab for an object in the Customizing analysis view in SM
"Syntax error in program /RTC/SAPLSA_TAB_CMP. The data object "GS_DYN310" does not have a component called "SCU0 _TEST". Root cause: Incompatibility with S/4HANA 1909. Solution: The program has been adjusted. |
Image Removed | | Customizing, NW/S4 platform specific issues | SC- |
189 Import information not updated in /RTC/TM_SCPT table 326 |
Image Added | Synchronization doesn't update the objects counters on customizing | Issue:
|
While several System Queues are running in parallel, sometimes feedback regarding return code and import flag is missing in /RTC/TM_SCPT, even though the transports have been imported. This causes the next System Queue import job to reconsider the transports for import. Root cause: Programming error The view in Customizing IMG tree is faulty after objects being synchronized. Counters were not being updated correctly as the entries were still being displayed on the column 'only in Maint' instead of "Equal Records" or "Different Records" columns. Root cause: Job that updates these information wasn't being triggered correctly after the import. Solution: The program has been |
corrected System queue generation and preparation for import for System A should not lock/change entries already considered for import in other system queues. If a stop mark entry exists in /RTC/TM_SCPT for system B, it means that System Queue for system B is currently running and the entries before the Stopmark should not be locked/modified by System A. | | Customizing, Synchronization | SC-327 |