Page Comparison

Adding Sync (original) from a Released Rollout, but not imported, to a new Rollout deletes it from the previous Rollout

When adding a Sync request (original) from a Released Rollout, but still not imported, to a new Rollout - SyncReq is deleted without warning from the Released Rollout and assigned to the new one.

If an original transport request is added to a rollout request, after releasing the rollout request it is possible to add the same original transport request to another rollout request and the original transport will be displayed also in previous rollout requests.

If in released rollout requests are SYNC or original request which are not synchronized the status will be changed to IGNORED.

Customizing, Synchronization, UI, Workbench

SC-816

Import during synchronization fails due to corrupted transport files

While doing synchronization of big customizing transport requests, the data files have been considered corrupted and could not be used for import in the target system.
The import log contains the following error: 'Unexpected EOF after 1048435 bytes'.
As a workaround, the transport files had to be copied manually to the other system.

To ensure consistency of the transport request files, the copy process has been enhanced with additional checks.

At synchronization time, the size of the data file on the project (target) system is compared with the size of the data file from the maintenance (source) system. If they are different, the user is asked to consent to the overwrite, proceeding to repeat the copy process.

Manual steps:

The callback positive list for the ZRTC_SA* RFC destinations must be enhanced with the following entry (relevant if the parameter rfc/callback_security_method = 3: secure)

Called Function Module | Callback Function Module
/RTC/SA_COPY_TR_FILES | EPS_CLOSE_FILE

This is done by running transaction /RTC/SC_WHITELIST on the SM console, with the option to activate the whitelist for the SmartChange module SYM.

Customizing, Synchronization

SC-836

Errors at running /RTC/SAPLSA_TAB_CMP (SC2019 SP04) on S/4HANA 2022

SyM customizing comparison compatibility issues with S/4 HANA 2022:

• Error during installation of transport RTCK900076 (SmartChange 2019 SP04)
• Dump SYNATX_ERROR during Customizing analysis in SM (initial analysis)
• Dump SYNTAX ERROR during Customizing analysis in SM (at Transport Request Release)

“Program /RTC/SAPLSA_TAB_CMP, Include LSCT1F2A: Syntax error in line 000033
Field 'GT_RECEIVER' is unknown.”

Customizing, NW/S4 platform specific issues, Objects analysis

SC-1221

Requests Task List popup contains a double scroll bar

On the SyM RequestsTask list pop-up window, the scroll bars are doubled when working in full-screen mode.

The program has been corrected.

Tasklist, UI

SC-1259

Assignment to Jira issue wrongly allowed, although status has been changed in the meantime

When a user creates a transport request and calls F4 help to assign an external ITSM Ticket ID, the following can occur:

• user does not immediately assign a Ticket and lets the popup open for some time, confirming later the selection
• user closes the F4 help, but not the assignment screen; calling again the F4 help sometime later

If in the meantime, the displayed/selected ticket is closed or assigned another status not allowed for the TR creation process, it is wrongly allowed to assign the ticket to the transport.

The program has been corrected. Buffering is no longer used whenever using F4 or manually entering and checking a Ticket ID.
As an additional precautionary measure, a final check is made against the ITSM when confirming the popup.

Integration Framework, Jira_App

SC-605

Dump CALL_FUNCTION_NOT_FOUND occured when calling F4 Help for Work Item Field

Dump CALL_FUNCTION_NOT_FOUND occurs when calling the F4 Help for Work Item Field in the Integration Framework Configuration > ITSM System > Work Item > Fields.

“Function ZRTC_SH_FIELD_NAME_EXIT does not exist.”

The program has been corrected. The search help for columns Field name/ Field description / Field alias is now available for ITSM type Service Now.

As a prerequisite, the Sub-Item path value must be filled in the corresponding Work Item:
/api/now/table/sys_dictionary?sysparm_query=name=task&sysparm_fields=column_label,element

Integration Framework

SC-687

Wrong notification behavior when using user groups and the feature 'Send all workflow emails' is active

When switching down a transport request from the status Queue to Signature, notifications are sent to the wrong list of users. Not all of the recipients can approve in TM Monitor because not all of them belong to the assigned User Group.

The scenario can be reproduced when the feature TM > Global Settings > Feature > Send all emails is active.

The program has been corrected.

The standard behavior is as follows:

• Send all emails = space:
  • If the current user is authorized for the next approval and belongs to the assigned user group, no emails are sent
  • If the current user is not authorized for the next approval OR does not belong to the assigned user group emails are sent to the authorized users in the assigned user group
• Send all emails = 'X':
  • If the current user is authorized for the next approval and belongs to the assigned user group, emails are sent to the authorized users in the assigned user group, current user included
  • If the current user is not authorized for the next approval OR does not belong to the assigned user group emails are sent to the authorized users in the assigned user group (same behavior)

Users in SUPER group never receive notification emails, even though they can approve in TM Monitor.

Notifications/Mails

SC-1243

TM destination not shown in Popup to assign Project/Destination at TR release for TOCs

When the TM server is not in the DEV system, the destination's transport type is incorrect at the transport request release. This causes TM destinations restricted to transport type ‘Transport of copies’ not to be visible in the popup to assign Project/Destination at the transport of copies release.

The program has been corrected.

Project Administration, UI

SC-1261

Issue with filtering for TM Attributes in TM Workflow Monitor

The following issues have been identified in working with TM Attributes filters in TM Monitor:

• When filtering for a TM attribute and confirming the popup, the counter in the Transport levels tree already adapts, but the transport requests are not yet filtered in TM Monitor. The counter should adjust only after pressing the 'Filter' button.
• When trying to delete the filter, clicking the ‘Delete’ button in the Filter screen or the ‘Refresh’ button in the TM Monitor application bar does not clear the TM attribute filter.

The issues have been corrected.

TM Attribute, Workflow Monitor

SC-1248

Table /RTC/TM_HLOG not cleared with TM Reset

Table /RTC/TM_HLOG is not cleared with the report TM Reset.

Table /RTC/TM_HLOG was added to the /RTC/TM_RESET report.

TM Reset

SC-1140

Wrong German Translation in System Queue

Wrong German Translation in System Queue for the title of the popup to enter a reason for locking the queue.

The program has been corrected - new translation text ‘Grund für Systemqueuesperre’.

UI

SC-1234

New feature Modifiable Transport Requests does not have text description when you login in JA

There are missing Japanese translations for the new TM feature, Modifiable Transport requests.

The program has been corrected.

UI

SC-1266

Obsolete function modules detected by the Panaya tool

SmartChange code contains calls to standard SAP function modules which are marked as obsolete.

The following function modules have been replaced in the Smartchange code according to SAP suggestions:

• POPUP_TO_GET_VALUE
• GUID_CREATE
• GET_FIELDTAB
• DOWNLOAD

The rest have been marked for further review.

Security

SC-1218