Release 5.6.9.0
Released on May 05, 2025
New Feature
Product Transport Management
| Priority | Title | Release Note | Components | Reference |
|---|---|---|---|---|
|
Integration Framework UPD action with no ticket assignment | In this updated version, the Integration Framework has been enhanced to skip UPD actions when no ticket assignment exists, across all ITSM types. | Integration Framework | SC-1968 |
|
|
Error while releasing a transport via the SmartChange Panel in SmartITSM | In this new version, when the 'Check Critical Objects' or 'Check Special Aspects' flags are set in transaction /rtc/tm_badi, attempting to release a transport request from ITSM containing these flagged objects does not trigger an error message anymore. If the release is performed directly in SAP, the QA Check screen appears as usual, without error. | OData Services | SC-1952 |
|
Very often TM and necessary tasks are blocked, because of locks by other TM-Users | SC-1542 | ||
|
|
Enhance Odata service with External User for TR_AssignRelease | In this enhancement, authorization checks for /sap/opu/odata/RTC/TM_GW_SRV/TR_AssignReleaseSet have been refined to validate permissions against an external user. | SC-1964 |
Fixed Bugs
Product Transport Management
| Priority | Title | Release Note | Release Note Solution | Components | Reference |
|---|---|---|---|---|---|
|
|
Short Dump at TR release related to critical objects | At release of the Release request a shortdump is generated at critical objects check. | Customizing, Quality Assurance | SC-1970 | |
|
|
TOC Log Double Entries | In previous versions, the ToC log contained duplicate entries. | The program has been corrected. | Log, ToC | SC-1932 |
|
|
Odata Service TR_Attribute is not working for modifiable requests when Trkorr is used in the filter | In previous versions, the OData Service TR_AttributeSet could not process modifiable requests via the GET method when the transport request was passed in the filter instead of being used as a key. | The program has been corrected. | OData Services | SC-1956 |
|
|
Desti and Project have the name fields iregular. | In the latest version, the short text field in the Project Management and Destination tabs has been extended to 60 characters. | UI | SC-1945 | |
|
|
Wrong user assigned at TR creation with project/destination assignment using technical user | Bug: When a Transport Request (TR) is created and both a project and destination are assigned during creation, the user recorded for the project/destination assignment is incorrect.Solution: Now, the user associated with project/destination assignment will match the user logged in the creation log, not the technical system user. | The program has been corrected. | SC-1961 | |
|
|
Odata Service to retrieve CTS projects return an error, if SC2015 systems are connected to the latest version of SmartChange Controller | If one of the RFC destinations is not working THE Odata throws an error, The Odata is changed not to display an error and to show the CTS projects for all DEV systems that can be reached. | The program has been corrected. | SC-1977 | |
|
|
ToC returnes wrongly the error, that request has a different ticket ID, after ticket reassigning | Users experienced an issue while reassigning Transport Requests to a different ticket within the workflow management system. Although the reassignment appeared successful — with the updated ticket ID correctly reflected in the workflow monitor and attributes — an error occurred while creating a TOC. The system incorrectly reported that the Transport Request was still linked to the previous ticket ID. | The program has been corrected. | SC-1979 |
Product SmartChange
| Priority | Title | Release Note | Release Note Solution | Components | Reference |
|---|---|---|---|---|---|
|
|
Ticket GUID is displayed instead of Ticket ID for ServiceNow in the Integration Framework Log | Issue: The Integration Framework Log displayed the Ticket GUID instead of the Ticket ID for ServiceNow tickets. This is not the optimal way to visualize the ticket information.Solution: The log has been updated to display the Ticket ID, as it is already done for other ITSM systems. | The program has been corrected. | Integration Framework, Log | SC-1942 |
|
|
F4 Search Help fails to show more than 1000 results | While creating a transport request in SAP, following short dump appears when using the F4 search help to look up the Jira Issue Number. The problem occurs when there are more than 1800 Jira issues available. For creating dynamic tables , SAP has a limitation of 36 subroutine pool generation limit in create_dynamic_table method | The program has been corrected. | Integration Framework | SC-1954 |
Product Synchronization Management
| Priority | Title | Release Note | Release Note Solution | Components | Reference |
|---|---|---|---|---|---|
|
|
SYM: Maintenance view status not changed after import |
Bug: Even after refreshing the screen, the object status TOBJ remained unchanged, leading to confusion about the actual import state.Fix: The maintenance view now properly reflects the updated status post-import without requiring manual intervention. |
The program has been corrected. | Objects analysis, Synchronization, UI, Workbench | SC-1824 |
|
|
TM/SYM: Mark as SYNC in TM when TR is not available in SyM Maint | Allow a transport to be marked as synchronised in TM only if there exists only one pair and the transport is marked as Finished in the tasklist in Synchronization Management | Synchronization, UI | SC-1948 |
Powered by Automated release notes & reports for Jira