REALTECH SmartChange SP6 HF10

Release 5.6.10.0

Released on May 28, 2025

New Feature

Product SmartChange

Title	Release Note	Components	Reference
cTMS Integration Setup and Core Functionality for Transport Management	The cTMS integration introduces initial setup and core functionality, enabling seamless connection between SmartChange and cTMS. This feature allows users to configure integration parameters and begin utilizing cTMS services within SmartChange. The integration affects transport management processes and provides a foundation for future enhancements. New configuration options are available in the system settings to manage cTMS connectivity and operational parameters.	cTMS	SC-2000
Display System and Groups for cTMS	In this new version, BTP nodes can now be visible in the TM Systems and the Groups tab. The BTP configuration and the nodes can be maintained in views /RTC/TM_BTP_V_CO and /RTC/TM_BTP_V_ND respectively:	cTMS	SC-2003
Support for Sequential Execution of Multiple Active TM Workflow Step Configurations per Action	The automation now supports processing multiple active TM Workflow step configuration entries for the same action. When several automation steps are configured and set as active, all steps will be executed sequentially. Previously, only the first active step was performed, and subsequent steps were ignored. This enhancement allows for more flexible and comprehensive workflow automation by ensuring that all relevant configured steps are executed. No additional configuration is required to enable this functionality.	Integration Framework	SC-802
Enhance Integration Framework Templates to Assign External Transport Requests to ITSM Issues	In this version, the integration framework templates have been modified to incorporate the GET action ADD2TM. With this action, you can assign transport requests to an ITSM issue while adding them to the TM Monitor using the ‘+' button. The templates for the following ITSMs were updated: Jira Cloud Jira Server ServiceNow Changes ServiceNow Incidents DOT4	Integration Framework	SC-1846
Technical Update of Class /RTC/CL_TM_IF_GET_JIRA	A correction has been implemented in class /RTC/CL_TM_IF_GET_JIRA to address the absence of a required method in the MT3 system. This update ensures proper functionality in MT3, while no changes are necessary for other clients or systems.	Integration Framework, Jira_App	SC-2001

Product Transport Management

Title	Release Note	Components	Reference
OAuth 2.0 Authentication Support for OData Services	OAuth 2.0 authentication support has been added for OData services, allowing users to securely access OData endpoints using industry-standard authorization protocols. This enhancement affects all areas where OData services are consumed and provides improved security and flexibility for integration scenarios. Administrators can now configure OAuth 2.0 credentials in the service settings to enable this functionality.	Integration Framework, Security	SC-1992
External User Integration Support in TR_RELEASE OData Service	The TR_RELEASE OData service now supports integration with External User information, enabling systems to pass and process external user details during transport request releases. This enhancement improves interoperability with external identity providers and allows for more flexible user management in transport workflows. No additional configuration is required for existing integrations, but systems utilizing external user data can now leverage this functionality for more comprehensive audit and tracking capabilities.	OData Services	SC-1963
Increased Maximum Entries Supported for Table /RTC/TM_PTRAN in Personal Queue	In previous versions, the program would terminate with a dump if the Personal Queue contained more than 10,000 entries. This issue has been resolved in the latest release.	Personal Queue	SC-1974

Product Synchronization Management

Priority	Title	Release Note	Components	Reference
	Error Message Displayed When Table Contents Exceed 512 Bytes or Contain String Fields in Customizing View	In this new version, when opening the “Details” tab on customizing view, an error message will be shown when the table contents cannot be displayed. The contents will not be displayed in the following situations: The key of the table or view exceeds 512 bytes The table contains strings E.g.	UI	SC-349

Fixed Bugs

Product Transport Management

Title	Release Note	Release Note Solution	Components	Reference
SYM BAdI Not Triggered After SmartChange ToC Release, Causing Missing ToC in SYM Tasklist	When creating a Transport of Copies (ToC) from SmartChange, the SYM BAdI was not being called after release. As a result, the SmartChange ToC did not appear in the SYM Tasklist as expected. This issue affected the integration between SmartChange and SYM, causing inconsistencies in task tracking for ToCs created via SmartChange.	The program has been corrected.	BAdI	SC-1953
"Jump to the Incident" Functionality Not Working for TEMPLATE_SNOW_INC Item Types J2O and J2S Due to Incorrect Configuration	In previous versions, the configuration for the TEMPLATE_SNOW_INC item types J2O and J2S was incorrect, resulting in the "Jump to the incident" functionality not working as expected. The configuration has now been corrected to ensure proper functionality.	The program has been corrected.	Integration Framework, ServiceNow	SC-1984
Irregular Display of Destination and Project Name Fields Due to Inconsistent Field Length Handling	The name fields for Destination and Project were displaying irregularly, causing confusion for users. This issue occurred due to inconsistent handling of field lengths, leading to misalignment and truncation of names.	The program has been corrected. Field length handling has been standardized.	Project Administration	SC-2017
File Path Not Recognized in /RTC/TM_UPDATE When Entered Manually or Selected from History	If the file path in transaction /RTC/TM_UPDATE was entered manually or selected from the history instead of using the search help, the file path was not recognized or considered by the program. This caused the update process to fail or ignore the intended file, leading to incomplete or unsuccessful updates.	The program has been corrected.	TM Update Assistant	SC-1895
TOC_StartSet Fails to Process Transport Requests from Different Systems or Clients	The OData service TOC_StartSet was not functioning correctly when handling Transport Requests from different systems and clients. This issue occurred due to missing compatibility checks, resulting in failed or incomplete processing of TRs that did not originate from the expected system or client. The update resolves this by ensuring that TOC_StartSet can now process Transport Requests across various systems and clients without errors.	The program has been corrected. Compatibility checks for Transport Requests from different systems and clients have been implemented in TOC_StartSet.	ToC	SC-1958
Roles Not Generated in Target System When Transported via TM ToC	When role changes were transported using TM ToC, the roles were not generated in the target system. This issue occurred because the generation step was not triggered during the import process, resulting in missing or incomplete roles after transport.	The program has been corrected. The role generation step is now triggered during TM ToC import to ensure roles are properly created in the target system.	ToC	SC-1989
Unable to Add Deletion Transport Requests in TM	Previously, it was not possible to add deletion transport requests (where E070-TRFUNCTION = 'L') in the TM. This issue prevented users from managing deletion transports within the TM interface. The functionality has been corrected to allow deletion transport requests to be added as expected.	The program has been corrected.	UI, Workflow Monitor	SC-1991
Incorrect Error Message Displayed When Releasing Transport Request with Unreleased Tasks in Jira	In earlier versions, an incorrect error message was displayed when attempting to release a transport request from Jira while the associated task was still unreleased. The system previously indicated that the project and destination could not be assigned, which did not accurately reflect the underlying issue. The message has now been updated to align with SAP’s standard messaging, providing clearer guidance when a release is attempted with unreleased tasks.	The program has been corrected. Error messaging now accurately reflects unreleased tasks when releasing transport requests from Jira.	UI	SC-2012

Product SmartChange

Priority	Title	Release Note	Release Note Solution	Components	Reference
	ServiceNow Tickets Displayed with GUID Instead of Ticket ID in Integration Framework Monitor	In the Integration Framework Monitor, ServiceNow tickets were displayed using the GUID instead of the more user-friendly Ticket ID. This issue made it difficult for users to quickly identify and reference tickets. The display logic has been corrected so that the Ticket ID is now shown for ServiceNow tickets in the Integration Framework Monitor.	The program has been corrected.	Integration Framework, Log	SC-1985
	Webcalls Not Triggered for REVOKE_APP, ADD2REL, and ADD2WF Actions in TM IF Monitor	In previous versions, the TM IF Monitor did not execute the webcall when performing the following actions: revoking approval of a transport request (REVOKE_APP), adding a transport request to a release (ADD2REL), or adding a transport request to the TM workflow (ADD2WF). As a result, the expected integration actions were not triggered for these operations, leading to incomplete processing and potential inconsistencies in external systems. This issue has been resolved to ensure that webcalls are correctly triggered for all relevant actions in the TM IF Monitor.	The program has been corrected. Webcalls are now correctly triggered for REVOKE_APP, ADD2REL, and ADD2WF actions in the TM IF Monitor to ensure proper integration processing.	Integration Framework	SC-1986

Product Synchronization Management

Title	Release Note	Release Note Solution	Components	Reference
Exception Icon Displayed Incorrectly for Tables in Object Analysis List of /RTC/SA_RSCMPEXP	Users encountered an inconsistency in the Object Analysis list for Customizing objects in report /RTC/SA_RSCMPEXP. The exception icon symbol was displayed for certain tables regardless of whether exceptions were activated or deactivated. This discrepancy caused confusion and potentially misled users about the actual status of exceptions for specific objects. The program has been corrected to accurately reflect the exception status in the Object Analysis list.	The program has been corrected.	Objects analysis	SC-312
Transport Request Owner Incorrectly Assigned During Rollout Synchronization	When Original Transport Requests (TRs) were added to a Rollout in both the Workbench and Customizing views, the system incorrectly assigned the owner of these TRs to the user performing the synchronization, rather than retaining the actual owner of each TR. This issue caused confusion regarding TR ownership and impacted tracking and responsibility assignment. The bug has been fixed to ensure that the original owner of each TR is correctly retained during the synchronization process.	The program has been corrected.	Synchronization	SC-1993
Incorrect Transport Requests Displayed for Selected Object in Workbench View	In previous versions of SyM, within the workbench view, double-clicking an object such as a LANG object would sometimes display transport requests that did not include the selected object.	The program has been corrected.	Workbench	SC-1898

Powered by Automated release notes & reports for Jira