/
REALTECH SmartChange SP6 HF06
REALTECH SmartChange SP6 HF06
Release 5.6.6.0
Released on Jan 30, 2025
New Feature
Product Transport Management
Priority | Title | Release Note | Components | Reference |
---|---|---|---|---|
![]() |
Enhancements to Report /RTC/TM_TR_ADJUST_DB01 |
The Transport Request Adjustment report /RTC/TM_TR_ADJUST_DB01 has been enhanced with two key improvements:
|
Configuration | SC-1850 |
![]() |
Updating ITSM Issue: Handover of Locked Status for Systems in ITSM Import Information | This feature enhances the ITSM issue handling process by ensuring that the locked status of a system is accurately handed over during the import process. | DOT4, Integration Framework, OData Services, ServiceNow | SC-1832 |
![]() |
Screen Timer Added to Collisions Pop-up |
The Screen Timer now activates whenever the Quality Assurance pop-up is displayed, such as when TM is locked during actions like Make Approval or Revoke Approval.
Once the reminder time configured in the global settings has elapsed, an additional pop-up will appear to notify the user:
|
Quality Assurance, UI, Workflow Monitor | SC-1857 |
![]() |
Ability to Save Quick Filter Values in User-Defined Variants | Users can now save the attributes defined in the "Free TM Attributes Selection" and "Quick Filter" sections of the Transport Manager start screen as user-defined variants. These variants can be reused to apply consistent filtering criteria efficiently. | Quick filter, TM Attribute | SC-1827 |
![]() |
Option to Deactivate Project/Destination Pop-up During ToC Transport Creation |
Users can now choose to deactivate the project/destination assignment pop-up that appears when creating a transport request for TOC. This can be configured globally for all development systems or for specific systems maintained by the user.
To enable this functionality:
|
ToC, UI | SC-1874 |
![]() |
Custom Columns Available in Modifiable Transport Request View | The system now supports displaying custom columns in the modifiable Transport Request view, enhancing the flexibility previously available in the Transport Management Workflow Monitor and History views. This feature allows users to define and display custom column values tailored to their requirements when managing modifiable Transport Requests.The user exit WORKFLOW_01 has been extended to populate custom column values for modifiable Transport Requests, with the context parameter set to the value 'D' for this purpose. Additionally, the template implementation of function module /RTC/TM_TMPL_WORKFLOW_01 has been updated to demonstrate how TM attributes (e.g., attribute "test1" in column "TEXT_2") should be displayed. | UI, Workflow Monitor | SC-1828 |
![]() |
Screen Timer Configuration Added to Global Settings > Feature Tab |
A new Screen Timer section has been introduced under Global Settings > Feature tab. This section includes:
|
UI | SC-1856 |
Product Synchronization Management
Priority | Title | Release Note | Components | Reference |
---|---|---|---|---|
![]() |
New Object Filter Added to SyncRequests/Rollouts |
A new filter by Object has been introduced in the customizing view of Synchronization Management. This filter allows users to display only requests that include the selected objects in the request tree. Additionally, the filter can be saved as a variant for future use.
New UI included:
|
Customizing, Synchronization, UI | SC-1356 |
Product SmartChange
Priority | Title | Release Note | Components | Reference | ||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
![]() |
Freshservice: Automatic Note Creation During Ticket Assignment on Transport Request Release | A new note is automatically created in Freshservice during ticket assignment when a transport request is released (action AFTER_WF_A). This enhancement ensures proper documentation and tracking of actions taken during the transport request workflow. | Freshservice, Integration Framework | SC-1843 | ||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
Freshservice: Exclude Solved or Closed Tickets from F4 Help in the GET action | The F4 help ticket list in Freshservice now excludes tickets with the status "Solved" or "Closed" using filter functionality. This ensures users only see relevant, active tickets in the selection list. | Freshservice, Integration Framework | SC-1847 | ||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
Freshservice: Include Approver Details and Approval Type in Ticket Notes During Approval Process | During the approval process in Freshservice, ticket notes now automatically include information about the approver and the type of approval. This enhancement improves visibility and ensures clear documentation throughout the approval workflow. | Freshservice, Integration Framework | SC-1848 | ||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
Freshservice: Centralized Placeholder Handling for ITSM API Calls |
A new class has been introduced to centralize the retrieval of placeholder data for ITSM-related API calls in Freshservice. This class ensures consistent and efficient handling of placeholders across various actions within the ITSM process.The following placeholders are now available:
Placeholder Availability Matrix:
|
Freshservice, Integration Framework | SC-1853 | ||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
Freshservice: Template Update with New Action and Enhanced Placeholders | The Freshservice template has been updated to include a new action, AFTER_WF_A, along with additional placeholders to enhance the APPROVAL note | Freshservice, Integration Framework | SC-1876 |
Fixed Bugs
Product Transport Management
Priority | Title | Release Note | Release Note Solution | Components | Reference |
---|---|---|---|---|---|
![]() |
Misleading Error Message Flags All Systems as "Yellow" When Virtual System is Present in Transport Directory Check | Users encountered a misleading error message when checking the trans-directory in the "Systems and Groups" section.During the transport environment check, the first system in the group is used as the reference SID. If the first system is a virtual system, the program assumes that no transport directory can be determined for any system in the group. Consequently, if there is a virtual system in the list, all subsequent systems are incorrectly flagged as "yellow."This inaccurate error message could confuse users attempting to validate their system configurations. | The program has been corrected. The error message logic has been adjusted to accurately reflect the transport directory status for systems in the group, regardless of virtual system presence. | Configuration | SC-1852 |
![]() |
Free TM Attribute Selection Values Deleted When Adding New Lines | Users experienced a data loss issue in the Free TM Attribute Selection feature. When adding or deleting new rows to the selection, previously entered data would be erased if the inputs were not explicitly saved before making changes. | The program has been corrected. | TM Attribute, Workflow Monitor | SC-1833 |
![]() |
TM Attributes Not Displayed for Modifiable Transports Lacking SAP Attributes and Limited to Five Displayed Attributes | When the modifiable transport does not have SAP attributes, the TM attributes are not displayed. Additionally, if there are more than five TM attributes for a modifiable transport, only five are displayed. | The program has been corrected. TM attributes are now displayed correctly for modifiable transports without SAP attributes, and all TM attributes are shown regardless of quantity." | TM Attribute, UI | SC-1867 |
![]() |
Incorrect Transport Level Display in the Import Information | Users experienced inconsistencies in the display of Transport Levels within the Import Information. The Transport Level is now retrieved from table /RTC/TM_REQ instead of the last import level information. | The program has been corrected. | TM Import | SC-1855 |
![]() |
Incorrect Transport Request Displayed in System Info After SP06 Installation |
The changes in the /RTC/TM_UPDATE transaction are not displayed in the TM information. This issue occurs after the installation of SP06, where the System Info incorrectly displays the outdated transport request RTCK900221.Environment:
|
The program has been corrected. The Update Assistant now accurately displays correct transport request RTCK900237 in the System Info section following SP06 installation. | TM Update Assistant | SC-1851 |
![]() |
Inconsistent Import Time Display Leading to Misleading Duration Information | Users have reported an inconsistency in the system's import times display. The import time shown is shorter than the actual time taken to complete the import process. This discrepancy can lead to misunderstandings about the duration of import operations and potentially affect user workflow planning. | The program has been corrected. The import time display has been aligned with the actual import duration to prevent misunderstandings. | UI, Workflow Monitor | SC-1854 |
![]() |
Date Format Incorrect in System Configuration for License Validity | Users encountered an unexpected date format when viewing license validity information in the system configuration. Instead of displaying the date in a standard format, the system showed an unconventional arrangement of numbers. This issue occurred when the user's date format preferences were set to a particular configuration. While the license validity status appeared correct, the unusual date presentation could lead to confusion and misinterpretation of the expiration date. | The program has been corrected. The date format display for license validity information has been standardized to align with user preferences. | UI | SC-1859 |
![]() |
TM Logo Not Displayed Correctly Due to Christmas Logo Type Configuration Issue | The TM logo was not displayed correctly due to an issue with the Christmas logo type not being updated. | The program has been corrected. | UI | SC-1868 |
![]() |
Incorrect German Translation of SPAU and SPAU_ENH Objects after S/4HANA 2023 FPS1 Upgrade | In the latest version, certain SPAU and SPAU_ENH objects were incorrectly translated into German, causing confusion during the upgrade process. This issue affected the consistency of language in the system and could potentially lead to misinterpretation of the objects' purposes. | The program has been corrected. | Upgrade | SC-1650 |
![]() |
Short Dump CALL_FUNCTION_OPEN_ERROR After SP6 HF5 Update Due to Hanging Semaphores in RFC Calls | A short dump "CALL_FUNCTION_OPEN_ERROR" occurred due to an uncaught exception during an RFC call after updating to SP6 HF5. The issue was caused by hanging semaphores that disrupted the RFC communication process. | The program has been corrected. The handling of RFC calls has been improved to prevent unhandled exceptions. | Upgrade | SC-1865 |
![]() |
Import Information Not Sorted Correctly in TM Workflow Monitor and Integration | The import information was not sorted correctly in the TM Workflow Monitor and during integration. This issue caused confusion and inefficiencies when tracking import levels. | The program has been corrected. Sorting functionality in the TM Workflow Monitor and integration processes has been improved to ensure accurate tracking of import levels. | Workflow Monitor | SC-1781 |
![]() |
Project and Destination Fields Not Persisting After Transport Request Assignment in TM Workflow Monitor | The Project and Destination fields were not correctly saved after assigning them to a Transport Request in the TM Workflow Monitor. This issue caused the assigned Project and Destination to disappear from the list upon refresh. | The program has been corrected. | Workflow Monitor | SC-1878 |
Product SmartChange
Priority | Title | Release Note | Release Note Solution | Components | Reference |
---|---|---|---|---|---|
![]() |
ITSM System Fails to Update After Importing Multiple Transport Requests with Subsets | The ITSM system was not being updated when multiple transport requests were imported simultaneously. This occurred due to missing transactional consistency after processing the imports. | The program has been corrected. To ensure proper updates, a COMMIT statement has been added after the Function Module /RTC/TM_IF_UE_AFTER_IMPORT call. | Integration Framework, Jira_App, TM Import | SC-1837 |
Product Synchronization Management
Priority | Title | Release Note | Release Note Solution | Components | Reference |
---|---|---|---|---|---|
![]() |
Incomplete Translations in Sync Status Feature for Japanese Language Users | Users working with the Japanese language version of the software encountered incomplete or missing translations for various interface elements, particularly in the Sync Status feature. This localization gap affected multiple areas of the application, including function groups, dynamic programs, and transaction codes. As a result, Japanese users experienced difficulties in understanding and navigating certain parts of the software, potentially impacting their productivity and user experience. | The program has been corrected. Missing translations in the Japanese language version have been addressed, particularly in the Sync Status feature and related interface elements. | Synchronization, UI | SC-1447 |
Powered by Automated release notes & reports for Jira
, multiple selections available,