REALTECH SmartChange SP5 HF02

We're excited to present a new report that simplifies the process of updating Secure Network Communication (SNC) settings within Transport Management (TM) and Synchronization (SyM) RFC connections. This report can be accessed using the /RTC/SC_SNC_CHANGE transaction.
The information about the SNC string is taken from the profile parameter 'snc/identity/as' of the destination system.

• Password Requirement: To enhance security, this update requires RFC connection passwords to be entered.
• Expanded Landscape Search: The report will search the entire TM or SYM landscape, unless limited by the 'Only in current system' option.
• Filtered RFC Destinations: If you specify RFC Destination filters, only those designated RFC destinations will undergo the updates

In this release, we've expanded the SmartChange Menu to seamlessly integrate the Integration Framework. This enhancement streamlines your access to Integration Framework Configuration, Monitoring and Logs.

The report /RTC/TM_MIGRATE_TICKET_ID has been designed to copy Ticket information from TM attributes and store them in the new /RTC/TM_TICKET table. Please note that the report comes with a limitation: it expects a transport request to be assigned to a single ticket. Data migration is performed only for transport requests from the TM monitor (from the /RTC/TM_REQ table).

With SmartChange Transport Management, you now have the flexibility to postpone the import of specific transport requests based on attribute-defined time and date criteria. This feature can be particularly useful for scenarios where you wish to prevent certain transports from being imported during regular working hours. To take advantage of this function, please refer to the step-by-step guide outlined in the How-to article:

https://rtcom.atlassian.net/wiki/spaces/CONNECT/pages/868155395/How+to+use+attribute-based+import+time+delay

In this release, it was observed that the RFCDOC table for the RFC destinations of TM Integration Framework was filled incorrectly.

The program has been corrected to resolve this issue, ensuring the RFCDOC table is accurately filled in the backup report.

In previous versions, clicking the "Job" button in the Job/Proposal area ab had no effect; nothing happened.

The program has been corrected. Now, clicking the "Job" button will correctly display the job details in this release.

In this release, the German language translation and function code were missing within the 'Adjustment of import database (Target System)' tab.

The program has been corrected to include the missing German translation and function code.

In this release, we address the issue of the Rollout Request being erroneously displayed in the SA transport log.

The program has been corrected to resolve this error in the synchronization log, ensuring that the Rollout Request is displayed accurately.