REALTECH SmartChange SP7 HF04
Release 5.7.4.0
Released on Jan 28, 2026
New Feature
Product Transport Management
Priority | Title | Release Note | Components | Reference |
|---|---|---|---|---|
PoC BAdI for Additional Checks | A new BAdI /RTC/TM_IF_BD_POC_CHECK has been introduced to allow additional custom checks beyond the standard Proof of Concept (PoC) check. This enhancement enables customers to implement project-specific validation logic and extend the existing PoC checking process with their own requirements. | BAdI | SC-2297 | |
Remote Function Module to Assign ITSM Tickets to Transport Requests | A new remote function module /RTC/TM_IF_GET_ITEMS_RFC has been introduced to retrieve the list of ITSM tickets for a modifiable Transport Request. Additionally, the remote function module /RTC/TM_IF_SET_ITSM2TR_ATTR has been enhanced to assign an ITSM ticket to SAP attributes by calling /RTC/TM_SAP_REPLACE_ATTR, and to Transport Management attributes by calling /RTC/TM_SET_MOD_ATTR. Synchronization with the ITSM system (ServiceNow) is performed via the function modules /RTC/TM_IF_AFTER_REASSIGN or /RTC/TM_IF_LINK_TO_EX. | Eclipse_Plugin | SC-2279 | |
ServiceNow Filter Supports USER ID Placeholder | ServiceNow filters now support the user-specific placeholder * {USER_ID} *, allowing change requests to be filtered and displayed only for the currently logged-in user. This enables more personalized and relevant views when working with ServiceNow-integrated change requests. | Integration Framework, ServiceNow | SC-2313 | |
Status Switcher – Enable Variant Sequence Definition | The Status Switcher has been enhanced to allow changing the order of variants within a level. This enables users to define the sequence in which variants are evaluated, providing greater control over status determination and improving flexibility for process-specific requirements. | Loaders/Switchers | SC-2265 |
Product SmartChange
Priority | Title | Release Note | Components | Reference |
|---|---|---|---|---|
Automatic Population of Node ID and Routes When Maintaining a New Node | When maintaining a new node in SAP Business Technology Platform, the system now automatically populates the Node ID and Routes fields. This eliminates the need for manual input, reduces configuration errors, and improves the overall user experience during node setup. | cTMS | SC-2145 |
Fixed Bugs
Product Synchronization Management
Priority | Title | Release Note | Release Note Solution | Components | Reference |
|---|---|---|---|---|---|
Unused Select Query in Application Code | The application contained an unused SELECT query that was not referenced or executed anywhere in the system. This redundant code increased unnecessary complexity within the codebase and could negatively impact maintainability and readability during future development and maintenance activities. | The program has been corrected by removing the unused select query from the codebase. | BAdI, UI | SC-2291 | |
Password Truncated in ZRTC_SA_ADM Setup for RFC Destination | During system setup using transaction ZRTC_SA_ADM, passwords exceeding 20 characters were incorrectly truncated when generating the Remote Function Call (RFC) destination. As a result, the stored credentials did not match the originally entered password, causing remote logon attempts to fail. Users were forced to manually shorten their passwords as a workaround to establish a successful connection. | The program has been corrected to properly handle passwords of any supported length when generating RFC destinations during system setup. | Configuration, UI | SC-2316 | |
Lock Override Confirmation Dialog Not Displayed for Locked Objects in Special User Group Scenario | When multiple users from the same user group attempted to manually adjust a locked object, a special use case could occur after restarting the process where the lock override confirmation dialog was not displayed. Instead of prompting the user to confirm the lock override, the system proceeded directly to the object adjustment completion dialog. This behavior occurred because the object lock had already been transferred to the current user, leading to an unclear lock status and preventing users from properly managing the intended lock override workflow. | The program has been corrected to properly display the lock override dialog in all scenarios when restarting a manual adjustment process, ensuring users receive the appropriate prompts regardless of the current lock status. | Synchronization | SC-343 | |
Tasklist Shows Wrong User When Running Mass Update Report | In previous versions, when executing the mass update report /RTC/SA_TASKLIST_INIT for task lists, the system displayed the technical user instead of the current user performing the action. This behavior also affected the user information recorded in the corresponding log entries. | The program has been corrected. | Tasklist, UI | SC-2253 |
Product SmartChange
Priority | Title | Release Note | Release Note Solution | Components | Reference |
|---|---|---|---|---|---|
Missing Message When Revoking Approval Without Existing Approval | When attempting to revoke an approval for SAP Business Technology Platform Transport Requests where no approval exists, the system did not return any message to the user. As a result, users received no feedback indicating that there was no approval available to revoke, leading to unclear system behavior. | The program has been corrected. | cTMS | SC-2231 | |
Transport Request Type Dropdown Value Not Stored in Variant | In the SmartChange selection screen, the value selected in the Transport Request Type dropdown was not stored when saving a variant. As a result, users had to reselect the value each time the variant was used. | The program has been corrected. | cTMS | SC-2234 | |
SmartChange Shows Popup and Blocks Process When Incorrect API Token Is Configured | When an incorrect API token was configured in cTMS, SmartChange displayed a popup error message and prevented the process from continuing. As a result, the selection screen was blocked and could not be displayed. | The program has been corrected. | cTMS | SC-2312 | |
Routes Are Not Updated When Node Name or Description Does Not Match | In report /RTC/TM_BTP_NODE_MAINTENANCE, routes were not updated when the manually maintained node name or description in the cTMS configuration did not match the corresponding data in cTMS. This mismatch prevented the route update process from being executed as expected. | Program was corrected | cTMS | SC-2317 |
Product Transport Management
Priority | Title | Release Note | Release Note Solution | Components | Reference |
|---|---|---|---|---|---|
Import Job Log Not Displayed | Users were unable to view the import job log after job execution. As a result, execution details and error information were not displayed, making it difficult to analyze import results and troubleshoot issues. | The program has been corrected. | job, Log | SC-2315 | |
Release Assignment via OData Service Is Canceled When Ticket Contains Transport Requests in Status Current | In previous releases, mass assignment of a release to a ticket via the OData service using a ticket ID was canceled if the ticket contained at least one transport request or Transport of Copies (TOC) in status Current. As a result, the release was not assigned to any transport requests, even if other requests on the ticket were in Queue or Signature status.With this correction, the release assignment proceeds for all transport requests in Queue or Signature status. Transport requests that are in status Current or already in History are skipped and do not block the assignment process. | The program has been corrected. | OData Services, Release Management | SC-2287 | |
Short Dump “You Are Not Authorized to Logon to the Target System” When Creating or Releasing Transport Requests via OData Service | When creating or releasing Transport Requests via the OData service, users encountered a short dump with the message “You are not authorized to logon to the target system”. The issue occurred because the transport request client was not determined correctly, leading to an incorrect authorization context during processing. | The program has been corrected. | OData Services | SC-2290 | |
Personal Queue Counter Remains at 0 After Manual Transport in Single Mode | When Transport Requests were manually imported individually in single mode, the summary header counter in the Personal Queue was not updated to reflect the successful imports. Although the Transport Requests were processed correctly and showed the appropriate status indicators in the list view, the imported counter in the header remained at 0. This led to a discrepancy between the actual import status and the displayed counter, causing confusion about the result of the import operation. | The program has been corrected. | Personal Queue | SC-2302 | |
System Queue Not Locked After RC8 | The system queue was not locked correctly when the “After RC” value differed from 0004, 0008, or 0012. In such cases, the system previously defaulted to the value 0012 regardless of the configured input. This led to incorrect queue locking behavior after RC8. |
| Queues/Proposals | SC-2295 | |
Authority Check Error for Project and Destination Determination | An authority check error occurred during project and destination determination because the authorization was not consistently evaluated for the current user. This led to incorrect authorization behavior and could prevent users from determining valid projects or destinations despite having the required permissions. | The program has been corrected. | Roles/Authorizations | SC-2303 | |
Attributes Icon Not Displayed in Workflow Monitor Overview After Package Creation | When creating a new package and configuring the attributes during the package creation process, the attributes icon did not appear immediately in the Workflow Monitor overview. The icon was only displayed after users manually opened the attribute settings, switched to change mode, and saved the configuration. | The program has been corrected. | TM Attribute, UI, Workflow Monitor | SC-2324 | |
Package Tab Not Displayed During Project and Destination Selection in Transport Request Creation | When creating a transport request and the popup for project and destination selection was displayed, the additional Package tab was missing. As a result, users could not select or review package information during the transport request creation process, limiting the available selection options in the dialog. | The program has been corrected. | TM Attribute, Workflow Monitor | SC-2325 | |
ToC Request Tab Disappears After Release of Transport Request | When a Modifiable Request was released, the ToC Request tab disappeared from the details view. As a result, users could no longer access the associated ToC information after the release, even though this information could still be required for reference or compliance purposes. | The program has been corrected to ensure that the ToC Request tab remains visible in the details area even after a Transport Request has been released, providing continued access to this information. | ToC, Workflow Monitor | SC-2043 | |
Upload cofile/data file path limited to 58 characters | When uploading cofile and data files, the file path length was restricted to 58 characters. This limitation prevented uploads when longer directory paths were used. | The program has been corrected. | UI, Workflow Monitor | SC-2320 | |
Quick Filters Not Cleared When Deleting Filter Selection in TM Workflow Monitor | When users deleted all filters in the TM Workflow Monitor, only the legacy filters were removed. The Quick Filters section retained previously selected values instead of being cleared together with the other filters, leading to inconsistent filter states. | The program has been corrected. | Workflow Monitor | SC-1327 | |
Deleting Transport Requests from Transport Monitor Does Not Remove Entries from Tracking Table | When users attempted to unassign a destination from a project in the project administration interface, an error message indicated that the project–destination combination was still in use. This occurred even after Transport Requests were deleted from the modifiable requests state. The issue was caused by remaining entries in table /RTC/TM_MOD_REQ, which were not removed when the Transport Requests were deleted. As a result, the unassignment operation could not be completed, blocking project configuration changes and workflow adjustments. | The program has been corrected to handle deleted Transport Requests in the modifiable state properly. Deleted Transport Requests no longer block the unassignment of project destinations. | Workflow Monitor | SC-1739 |
Powered by Automated release notes & reports for Jira