Page Comparison

Short Text for Project/Destination is missing in TM BAdI popup screen

Issue:
The short text for destination does not appear in the BAdI-Popup screen to assign Project/Destination at transport request release.

Root cause:
Programming error.

Solution:
The code was corrected.

BAdI

SC-765

Short dump CALLBACK_REJECTED_BY_WHITELIST when releasing TR containing critical objects

Issue:
If the RFC Whitelist is active (and /rfc/callback_security_method > 1), when releasing a transport containing critical objects marked as "Error" in TM>QA, the short dump CALLBACK_REJECTED_BY_WHITELIST is generated.

Root cause:
The Whitelist table did not contain the necessary Function Modules

Solution:
The RFC Callback Whitelist table (/RTC/SC_WHITELIS) was enhanced with the following two entries:
Called Function Module | Callback Function Module
/RTC/TM_IF_CRIT_OBJ | /RTC/TM_CHECK_AUTHORITY
/RTC/TM_IF_CRIT_OBJ | RFC_PING

Configuration, Security

SC-734

TM IF - 'SWITCH_OFF' parameter not configured in /RTC/TM_IF_CONFIG results in SAP attributes not copied to TM Attributes

Issue:
In the TM Integration Framework Configuration, /RTC/TM_IF_CONFIG > Global activation settings, if the parameter SWITCH_OFF is not configured, there is inconsistency in triggering the TM IF functionality.
The default implementation for TM User Exit AFTER_ADD2_WF considers the TM IF as inactive, while the other User Exits trigger the TM IF specific functionality.
As a result, an external ITSM issue is assigned to the TR at request creation, but the values of the SAP attributes are not copied to the TM attributes when releasing the TR/ insertion in the TM workflow.

Root cause:
Programming error.

Solution:
The program has been corrected.
TM Integration is to be considered switched off if the parameter SWITCH_OFF is explicitly maintained with 'X'. If it is blank or not set at all, all active TM IF User Exits will be triggered.
Also, as the 'SWITCH_ON' parameter was obsolete, it has been removed.

Integration Framework

SC-755

Switcher '/RTC/TM_SW_12' has performance issues when processing a large number of transports

Issue:
When switching a large number of transport requests into status 'Current', using report /RTC/TM_SW_12, there are performance issues during the processing of the transport files.

Root cause:
A programming error in the transport files checks for determining if the copy to the target system is necessary.

Solution:
The program was corrected.

Loaders/Switchers, Performance

SC-706

Switching Up a Package from Queue to Current, with option "Repeat import" does nothing

Issue:
In TM Monitor, when manually switching a Package up, from status "Queue" to status "Current" of the previous level, a pop-up appears to choose the options for changing the package status:

• "Only change status"
• "Repeat Import".
  Option "Repeat import" does nothing. It should change the status and also mark the transports from the package for re-import.

Root cause:
Programming error.

Solution:
The code was corrected.

Loaders/Switchers

SC-715

Reports /RTC/TM_LD_10 and /RTC/TM_LD_15 end with short dump UNCAUGHT_EXCEPTION when RFC is missing

Issue:
Reports /RTC/TM_LD_10 and /RTC/TM_LD_15 end in a short dump, UNCAUGHT_EXPCEPTION, when the RFC destination for the originating system of the transport request is missing.

Root cause:
Programming error. The exception is not caught.

Solution:
The program has been corrected.

Loaders/Switchers

SC-738

OData Service: Create TR returns HTTP Error 400 with message 'Ping failed: IV_RFC_MESSAGE1IV_RFC_MESSAGE2IV_RFC_MESSAGE3'

Issue:
When creating a Transport Request in SAP via OData call, the call returns HTTP response 400 Bad Request and Message 'Ping failed: IV_RFC_MESSAGE1IV_RFC_MESSAGE2IV_RFC_MESSAGE3'.
As a prerequisite for using the CREATE TR OData call, a trusted RFC destination must be set from the TM server to the DEV client where the transport must be created.

Root cause:
A programming error in handling the exception.

Solution:
The program has been corrected.

OData Services

SC-746

Personal Queue not working, when application server is in passive mode

Issue:
When some of the application servers are in passive mode the personal queue is not working.

Root cause:
The check of available sessions is not taking into consideration if the application server is active or passive.

Solution:
The function module /RTC/TM_GET_INST_STATE was changed to check only active application servers. The personal queue should run if there are enough batch processes available.

Queues/Proposals

SC-700

Maintaining dependencies in TM Monitor throws error 'Entry is too long for the field' for textbox 'Reason'

Issue:
When maintaining dependencies, the 'Reason' field is mandatory. However, if the entire textbox is filled, an error message occurs "Entry is too long for the field".

Root cause:
The textbox displayed on the screen is longer than the maximum technical field length.

Solution:
The textbox was restricted to the maximum field length, which is 60 characters.

UI

SC-736

TM-Attribute defined as Link shows no error message when the URL is wrong

Issue:
When a TM-Attribute is created as a Link and the URL is wrong, the user doesn't get any feedback when clicking on it.

Root cause:
This situation was not covered in the code. Normally the user should receive a Windows error which indicates that the link cannot be opened.

Solution:
An error message that the link can no be opened, is now shown also in the status bar.

UI

SC-745

Destination Short Text is too short and is not displayed when selecting the destination route at transport request release

Issue:
In TM>Destinations maintenance screen, the field length for 'Destination Short Text' is too short.
Also, the Destination Short Text is not displayed in the popup to assign 'Project/Destination' at the transport request release.

Root cause:
Programming error.

Solution:
The length of the Short Text for both Project and Destination has been increased to 60 characters. Also, the popup to assign TM Project/Destination has been adjusted to show the Destination short text.

UI

SC-749

Wrong translation for text 'Transport Types' in German, in TM>Destinations

Issue:
In TM>Destinations configuration screen, there is a translation error in German for text 'Transport types'.

Root cause:
Error at the translation for transport types.

Solution:
The translation has been corrected to 'Auftragstypen'.

UI

SC-751

Return code 8 at TR import SR1K900050 (SC v5.2.0.0) on S/4HANA 2020

Issue:
Errors during installation of transport SR1K900050 (SmartChange 2019 SP02) - Return Code 8.

• "Syntax error in program /RTC/SAPLSA_TAB_CMP,Include LSCT1F2A: Syntax error in line 000052.
  Field 'GV_USER_SEL' is unknown."
• "Program /RTC/SAPLSA_TAB_CMP, Include LSCT1O0A: Syntax error in line 000046
  The data object 'GS_DYN300' does not have a component called 'P_ALV'."
• "Program /RTC/SAPLSA_TAB_CMP, Include LSCT1F30: Syntax error in lines 000223,000224,000226
  The data object 'GS_DYN300' does not have a component called 'P_ALV'."

Root cause:
Incompatibility with S/4HANA 2020.

Solution:
The program has been adjusted.

Customizing, NW/S4 platform specific issues

SC-737

SyM>Sync Management-Help>System Info causes dump CX_SY_RANGE_OUT_OF_BOUNDS in S/4 HANA 1909

Issue:
When accessing SyM>Sync Management-Help>System Info causes a dump in S/4HANA 1909, the dump CX_SY_RANGE_OUT_IF_BOUNDS occurs in program /RTC/SAPLSA_SERVICE.

Root cause:
The length of the data element for the service pack level was changed by SAP.

Solution:
The code was corrected.

NW/S4 platform specific issues

SC-732

CDS views (DDLS-Objects) are displayed as 'Not Modified on DEV' after being synchronized _Part 2

Issue:
When synchronizing CDS Views (Object type DDLS), the objects appear as different in SM>Object Comparison, even after the synchronization. The displayed status is 'NOT MODIFIED ON DEV', instead of 'EQUAL', even though the log displays entry "Status changed to 'EQUAL'". After synchronization Creation Date/Time are empty

Root cause:
The highest version is taken into consideration in dev system.
The active version wasn't found.

Solution:
The program has been corrected, if the active version in DEV is 00000 then the version is set to 99999.
The program was changed to find the active version release date and time.

Objects analysis, Workbench

SC-756

Modification Assistant is disabled for some /RTC/ objects

Issue:
In a customer system (/RTC/ namespace set as 'Consumer'), some objects in the /RTC/ namespace cannot be modified using the Modification Assistant. The Modification Assistant appears as "Switched off" and cannot be switched on.

Root cause:
Standard objects modification error.

Solution:
The Modification Assistant has been switched on for the affected /RTC/ objects.

Security

SC-728