REALTECH SmartChange SP3 HF02

SC-994

Hide 'Application Context' details tab if SmartChange Controller is not configured

With this feature, if the SmartChange Controller is not used and configured, the 'Application Context' tab is hidden in the detail view of the transport request.

SC-1055

Error in Systems and Groups at system RFC creation

Issue:
When adding the current system (TM server) in TM>Systems and Groups, an error is displayed stating that the RFC destination already exists.

Solution:
The program was corrected; the RFC destination ZRTC4_TM_<SID> is correctly created.

SC-1051

Special Aspects > SAP objects are not correctly identified during Quality Assurance checks

Issue:
When Transport Management server is not in development system, the check for Special Aspects > SAP objects is not working correctly.

Solution:
The program was corrected

SC-1036

Errors 'Whitelist should be maintained for RFC destination NONE'

Issue:
In the configuration of 'System and Groups', the error 'Whitelist should be maintained for RFC Destination NONE' is displayed when checking the RFC Destination.

Solution:
The program has been corrected.

SC-1035

System Queue terminates with short dump DATAREF_NOT_ASSIGNED

Issue:
Auto delete semaphore is set on 2 hours but, this is not deleted and remains blocked. The table /RTC/TM_ACTS contains an entry and no TP process is still running on the affected system.

Solution:
The /rtc/tm_group table was read from the target system, not from the TM Server. The program has been corrected.

SC-1031

Transport Request has status 'Signature' when added to TM Workflow, even if in TM_BADI the status is set to 'Current'

Issue:
If the 'IGNORE_LOCKED' is activated in the /RTC/TM_OPT table and the TM_BADI is configured to insert the transport request into TM Workflow Monitor with the status 'Current', the technical approval is automatically granted for virtual and locked systems only if the TM Server is locked.

Solution:
The program has been corrected.

SC-1030

RFC Destination NONE wrongly changed to Type 3

Issue:
If /RTC/TM_INI is executed after the installation of SP03 HF02, then the RFC destination 'NONE' is wrongly changed from Type I to Type 3.

Solution:
The program has been corrected.

SC-1028

'QA Approval' line is incorrectly displayed in the TM

Issue:
The import protocol of TM Workflow Monitor displays 'QA Approval' line as 'Unknown step'.

Solution:
The information of displayed lines is taken from the cofiles and it will be translates into a message. 'QA Approval' is missing in the translation.
The program has been corrected.

SC-1027

Ignored option is missing in the Color Key

Issue:
The Ignored option is missing on the Color key.

Solution:
The program has been corrected.

SC-1022

Odata Service 'Get TR' does not return icons for Quality Checks

Issue:
With the Odata Service 'GET TR', the icons for Quality Checks are wrongly not returned in the response.

Solution:
The program has been corrected.

SC-1010

Customizing tab incorrectly shows workbench selection options

Issue:
If in the SyM initial screen the Customizing tab is selected, then display the tasklist and select a Transport to jump to WB overview then go back to the tasklist and close it. The Customizing tab is selected but the subscreen shown is for the Workbench options.

Solution:
The program has been corrected.

SC-1009

Special aspects are not displayed for packages

Issue:
Special aspects for packages are not displayed in TM package monitor

Solution:
The program has been corrected.

SC-1008

Wrong color for overtaker using approval with multiple groups

Issue:
Collision pop-up does not show the correct color for overtaker for content approval with multiple groups.

Solution:
The program has been corrected.

SC-1003

Typing errors in the 'Notes' tab in the history

Issue:
In the TM Workflow Monitor History is a type error in the notes tab.

Solution:
The program has been corrected.

SC-1002

Dump GETWA_NOT_ASSIGNED in report /RTC/SAPLTM_CONFIG

Issue:
When adding an object to the 'Critical Objects' via copy and paste, the program dumps.

Solution:
The program has been corrected.

SC-943

Merging Transports in SAP not deleting transport in Jira

Issue: When two transport requests are merged the deleted transport (first transport) from SAP is not deleted from ITSM ticket

Solution:
A new enhancement with the custom BAdi /RTC/TM_IF_BD_MERGE_REQUEST has been created to delete the request (first request) from the ITSM ticket when two transport requests are merged.
Furthermore, the TM integration attributes from the first request are also not transferred to the target transport request.