REALTECH SmartChange SP5 HF03

When creating a new system, systems sharing a transport directory will be grouped together, while those with different transport directories will be assigned to separate groups.

This feature introduces automatic verification upon adding a new system to a group. If the selected group contains systems with a different transport directory from the new system, users will receive a warning. They'll have the option to select another group or even create a new group without exiting the wizard.

This feature introduces two new standard filter fields, namely ITSM-ID and TICKET-ID, added to both the TM selection screen and the Workflow Monitor filter. These filters offer users the ability to search for specific ITSM-ID and TICKET-ID entries. Notably, these fields will only be displayed if the integration framework is active.

This update introduces an automated process that saves ticket information directly into the /RTC/TM_TICKET table when corresponding TM attributes are saved. This functionality ensures seamless and automatic maintenance of ticket-related data within the specified table.

The /RTC/R_LIB_DW_CLEANUP report has been enhanced to not only provide the option to delete all ReturnCode Forecast (RCFC) data but also to remove data associated with transport requests already in the history. Typically, RCFC data is no longer necessary for transports existing in the history, allowing the scan on the development system to be deleted.

In this latest update, a new feature has been introduced in the Feature Tab of Global Settings. The functionality, named "Enable Transport of Copies Testing," enables users to enable or disable the testing of ToC (Transport of Copies).

When the "Enable Transport of Copies testing" feature is enabled in the TM Server's Global Settings, users will now encounter the Project/Destination assignment screen during creation of a transport request.

All authorization roles and filter criteria applied during TR release will also be considered for assignment during TR creation.

Restrictions:

• At the time of transport request creation, only Project/Destination assignments are permitted, disregarding the /RTC/TM_BADI configuration in the development system.

In the TM Workflow Monitor under Modifiable Requests, two new columns have been added:

• Project
• Destination

The destination functions within the "Destination" menu have been expanded to include a new button and column. The newly introduced button allows users to select and assign an existing destination as a Transport of Copies (TOC) destination for another destination. This selection is made via a dropdown menu displaying destinations suitable for TOC purposes (Type = space (all) or Type = T (one of the selected types)).

The newly added column displays the assigned TOC destination.

In the latest update, a new feature has been introduced within the Modifiable Request tab – the 'Project/Destination' button.

This feature allows users to manage the Project or Destination for a Modifiable request. Users can select multiple transport requests provided they share the same request type. Upon clicking the 'Project/Destination' button, a pop-up window appears, enabling the assignment of a new Project/Destination.

If new values are selected while the ToC process is already running, a warning message will prompt confirmation for the changes.

In the latest update, the Modifiable Request tab now features the 'Start ToC Distribution for Testing' button. This enhancement allows users to select multiple requests for Quality Assurance (QA) testing via ToC (Transport of Copies) requests instead of original transport requests.

To initiate the ToC testing process, the following requirements must be met:

• ToC is enabled in the Feature Configuration,
• all requests tasks are released,
• the same project/destination is assigned to all modifiable requests,
• ToC destination is assigned to the original destination.

In the latest update, a new functionality is introduces into the Modifiable Request tab: the 'Start ToC Distribution for Testing' button.

Activating this button initiates the creation of a new transport in the development system of modifiable requests, labeled 'SmartChange - generated transport request' with a ToC typ in the development system of modifiable requests. Subsequently, it releases the transport and adds it to TM Workflow Monitor to the ToC Destination of the request destination.

In cases where the project and destination are selected for the modifiable transport request, the selection pop-up for the project and destination will no longer appear during transport release. Instead, the already chosen project and destination will be utilized automatically.

During the creation of a transport request, the chosen project and destination will now be automatically transmitted to the ITSM plattforms.

With this feature, changing the TM Project/Destination assignment of a modifiable TR from TM Monitor triggers an update to the assigned ITSM Plattform issue to reflect the change in the Jira SmartChange Pannel.

Any errors encountered when updating the assigned ITSM plattform instance are logged and can be recalled manually or automatically.

Troubleshooting

If there are any errors during the update calls to the ITSM(s), they will be saved for later recall via the transaction /RTC/TM_IF_MONITOR. The update can be triggered either manually or automatically (job schedule).

The /RTC/TM_BADI transaction now displays the list of modifiable transports that couldn't initially appear as modifiable transport requests in TM Workflow Monitor due to RFC errors during the transport request creation process. A new "Distribute" button has been introduced, enabling users to retry sending the information to the TM server for resolution.

The /RTC/TM_TRACKING2FILE report now includes additional filtering criteria, allowing exclusion of Transfer of Copies (ToC) from Development (DEV) systems. DEV systems are configured within the global settings under Standard System(s).

With this latest hotfix, users now possess the capability to verify the accuracy of the transport directory. A newly added tab, positioned behind the "Protocol Transportdirectory," provides infos about the Status, SID and information messages for all checked systems.

The mobile approval app encounters difficulties in handling certain SAP user date formatting.

The program has been corrected.

With this feature, the new output field ‘Timestamp’, format ‘YYYYMMDDhhmmss’ has been added to OData Web Services /sap/opu/odata/RTC/TM_GW_SRV/Transport_RequestSet and /sap/opu/odata/RTC/TM_GW_SRV/TR_TO_TMSet.

An error occurred due to the limitation on the RFC SNC parameter, restricting character lengths to 60, impacting the report /RTC/SC_SNC_CHANGE. This issue particularly affected HANA systems.

The report /RTC/SC_SNC_CHANGE was adjusted specifically for SAP HANA systems to support SNC parameter longer than 60 characters (string type) within the determination of the SNC parameter.

In scenarios where the TM Integration Framework is activated for transport types "Workbench" and "Customizing," the report /RTC/TM_SYNC_SAP_ITSM fails to consider transports from TM History during processing. Consequently, an erroneous message stating 'There are no tickets to be synchronized' is displayed.

The program has been corrected.

Exceptions within the function module /RTC/TM_UI_MAKE_APPROVAL_NEW were not triggered in non-dialog mode.

The program has been corrected.

TM compatibility issues with some SAP Netweaver versions:

• Error during installation of transport RTCK900139 (SmartChange 2019 SP05)
• Dump SYNTAX_ERROR when entering TM Monitor

The program has been corrected.

The deleted custom function module was displayed as a standard SAP object in special aspects.

The program has been corrected.