REALTECH SmartChange SP6 HF01

A new configuration option has been introduced in the Global Settings to display only projects and destinations for transport requests containing exclusively Allowlist objects.

The terms "Fast Track" and "Uncritical Objects" have now been unified under "Allowlist" and "Allowlist Objects."

In the latest update, quality checks have also been implemented for all objects included in the new Transport of Copies (ToC) requests.

Before the ToC process starts, the BaDI settings of development systems will check for critical objects and special aspects. If any critical objects or special aspects are found, they will be displayed to the user. The user must then accept these critical objects and special aspects before the ToC requests will be created.

This new feature ensures that users are aware of any potential issues or considerations related to the objects being included in the ToC requests, allowing for informed decision-making and improved quality control.

The Quality Assurance Collision Configuration interface has been redesigned to enhance user experience and accessibility. In the past, users needed to double-click on red or green icons to modify collision check options, which could be confusing. The updated interface replaces these icons with checkboxes, making it clearer and more straightforward for users to adjust settings.

The F4 was added for the attributes added in the quick filter if the attributes have the Value Help set . As default maximum 14 attributes are expected to be displayed in quick filter.If more attributes are added then the transaction /RTC/TM_GEN_QFILTER should be executed one time to generate the F4 event for the desired number of attributes.

This release introduces TM attributes specifically designed for modifiable transport requests. This enhancement involves the creation of a new table for storing TM attributes of modifiable requests and ensures these attributes are correctly transferred and preserved during transport request releases. Only attributes of type ‘TEXT’ or 'LINK' can be used.

The Transport of Copies (ToC) functionality has been enhanced to support selection at the system level. The ToC process has been optimized to handle multiple transport requests. When multiple requests are selected for ToC, the system will split the ToC on the following criteria:

• Transport Requests with different System IDs and Clients will have a separate ToC generated for each unique combination of System ID and Client.
• Transport Requests with different project or destination assignments will continue to be handled as per the existing implementation.

With these enhancements, the ToC button will now be available at all tree levels, including the system level, providing greater flexibility and convenience for users.

In this new version, the upload and download of transport files has been refactored to use the class /rtc/sc_cl_trans_files in the /RTC/ namespace.

The OData service for the Transport_RequestSet endpoint has been enhanced with the addition of a flag to indicate the existence of TM attributes for a transport request. This new feature allows users to identify whether specific TM attributes are assigned to the transport request directly through the OData call.

Example Usage

• OData Entity: Transport_RequestSet
• HTTP Method: GET
• Request URI: /sap/opu/odata/RTC/TM_GW_SRV/Transport_RequestSet?$filter=Trkorr eq 'MT3K901200' &$expand=TR_Workflow,TR_Approve,TR_ImportSet

The transport is not added to TM at the release of TR when POC users are used.The reason is the check of the user in POC list or because of the RFC ping error.

The program has been corrected.

After updating to SP05 HF6, LD_15 stopped bringing transports into the workflow. The error was caused when using the POC list in TM BADI. There was a POC user check in the BADI after export.

The program has been corrected to ensure that LD_15 correctly brings transports into the workflow. The POC check was removed because the user is the user who scheduled the job RDDFDBCK.

In the previous version, an icon appeared for modifiable requests in the Transport Management Workflow Monitor. When users clicked on this icon, it unexpectedly triggered a short dump, leading to an "OBJECTS_OBJREF_NOT_ASSIGNED" error. The short text for this error is "Access using a 'ZERO' object reference is not possible." The issue occurred in the ABAP program /RTC/SAPLTM_WF and the exception CX_SY_REF_IS_INITIAL.

The program has been corrected.

In this new version, after a transport request is added to the TM Monitor, the attributes flag is displayed only if the transport request contains TM Attributes. Additionally, the “Attributes” tab of a transport request’s detail view is visible if the transport request has either TM or SAP attributes.

The program has been corrected.

In the latest service pack, the F4 Help button for opening the file explorer was missing in the TM Attributes interface. Using F4 on the keyboard remained functional, this issue has been fixed in the most recent version.

The program has been corrected.

Transaction /RTC/SC_TR_FILES did not upload or download files when the parameter REJECT_EMPTY_PATH was set to ‘ON’ in newer SAP releases.

The program has been corrected.

In the previous version, the SmartChange banner was not fully extended across the GUI.

The program has been corrected.

In previous versions, users who set and saved a default variant with ascending reference time sorting found that these preferences were always lost upon re-entering TM Workflow Monitor.

This issue was traced to the setting at Settings -> User dependent -> 'Sort request in the workflow monitoring ascending'. If this checkbox was not set, the system defaulted to descending sorting, which overrode user-specific layout settings.

With the latest version, once a default layout is set, the system will no longer overwrite the user-specific time sorting preference, ensuring consistency and enhancing user experience.

The program has been corrected.

In the previous version, ToC feature buttons “Project/Destination” and “Start TOC” were displayed for modifiable transports in the TM Workflow Monitor even when the feature “Enable Transport of Copies Testing” was disabled in Global Settings.

The program has been corrected.

In previous versions, deleting a maintenance system from the system management screen also removed development system details, preventing the development system from being deleted.

The program has been corrected.

The check of the locked objects is not done at the moment when they are added to the rollout request.

The program has been corrected.

In earlier versions, accessing the Object Analysis view from the Tasklist did not display older versions of transport requests in the Detail Section. However, if the object was accessed directly from the initial screen, the Detail Section showed all transports containing the object. This limitation hindered the ability to view a complete history of transport requests for objects,, potentially affecting decision-making and analysis processes. In the latest version, this limitation has been eliminated.

In the previous version, the overtaken error message did not include information about the transport request. This information has been added in the latest version.

The program has been corrected.

Users experienced short dumps in transaction /RTC/SA when the RFC destination was using fast serialization.

Dump Info:

• Runtime Errors: APCRFC_TRANSFORMATION_ERROR
• ABAP Program: /RTC/SAPLSA
• Short Text: When calling the RFC with new serialization, incorrect parameters were submitted.

The program has been corrected.