REALTECH SmartChange SP5

Send Message using Firebase Cloud Messaging Service for Pending Approvals

Configuration prerequisites

1. Firebase certificate is installed in SAP, on the TM Server using STRUST transaction, under node SSL Client (Standard).
2. SC Approval App authorization key (the app is registered in Firebase) is configured in SAP (table /RTC/TM_APP_NOTI) and marked as active:
   
    
3. User setting: 'Push notification > on request for approval' is set, and devices are registered for the user

Functionality

When using the SmartChange Approval App, you can now receive a push notification whenever a transport request has been moved to the next status and is waiting for your approval.

Troubleshooting

Logs for calling the Firebase message service are saved in SAP in table /RTC/TM_NOTI_LOG. No message is returned to the online/background process which triggered the notification. If an error occurs, it is only logged. If prerequisites are not met, nothing is done.

Approval_App

SC-1368

Enhance personal settings to allow the activation of SC approval notifications

This release includes a new option in Settings -> User Dependent in order to activate or deactivate the push notification for approval applications. This option is also available in Settings -> Global -> Default User Settings

Approval_App, Configuration, UI

SC-1369

Report to Synchronize Transport Requests between SAP and ITSM

In this release a new Report named /RTC/TM_SYNC_SAP_ITSM was developed. The purpose of this is to synchronize requests between SAP and ITSM. This can be used to update the request to rebuild all requests. Especially after there are some new update features (e.g. history) the update of old requests that are already in history can be done. Furthermore, for new Jira security requirements, it is an advantage to be able to rebuild data in case they are lost.

The report can be run also in the background and have a selection screen where the user can filter the ITSM Type that he wants to synchronize. If the ITSM Type remains empty, then all the ITSM Types are taken into consideration. Also can decide what transports he wants to synchronize (Modifiable, Workflow or History).

To synchronize the requests between SAP and ITSM the user needs to set the action 'Synchronize TR data from SAP to ITSM' in the configuration (/rtc/tm_if_config transaction) for all the needed Server IDs.

Integration Framework

SC-975

Enhance OData Services to Return New QA Collision Type: Overwritters

Add Overwriten information at collisions at call:

/sap/opu/odata/RTC/TM_GW_SRV/QA_TM_TRSet?$filter=Trkorr eq 'MDQK900048' and Approve eq 'A' and Usrgroup eq 'Development'&$expand=NavToCollisions,NavToDependency,NavToCritObj,NavToSpecialAspects

Jira_App, OData Services

SC-1383

New Authorization Check (Auth. Obj. ZRTC_TM, Auth. Field '/RTC/TM_AC' = ‘IT') for Limiting Import into Production in TM Tools > Import Tracking

The standard role, /RTC/TM_ADMINISTRATOR, now has the authorization value 'IT' which allows limited imports into Production in TM Tools> Import Tracking.

Roles/Authorizations

SC-1217

Update SNOW on Deletion of Modifiable Transport Requests and Enhance TM IF Configuration Template

With this feature, deleting a modifiable TR from SAP triggers an update to the assigned Service Now Incident to reflect the change in the SNOW Plugin.

To ensure its proper functioning, certain prerequisites must be met, such as configuring TM IF. Additionally, any errors encountered when updating the Service Now instance are logged and can be recalled manually or automatically.

Successful implementation of this feature requires certain prerequisites to be met:

TM IF configuration
The following actions must be configured for the current assigned ITSM system.

1. UPD/DELETE_TR (Deletion of a modifiable TR from the SAP system)

The template entry TEMPLATE_ SNOW_INC can be copied and used as a reference.

If there are any errors during the update calls to the ITSM(s), they will be saved for later recall via the transaction /RTC/TM_IF_MONITOR. The update can be triggered either manually or automatically (job schedule).

ServiceNow

SC-1400

TM Tools: Create TM Backup

With /RTC/TM_BACKUP report, the user can perform a TM backup via RFC connection.

Tools

SC-1294

TM Tools: Lock/Unlock Systems and TM T-Code

The report /RTC/TM_LOCK_UNLOCK_SYSTEMS allowing users to lock and unlock the systems queue in the same way as it is available in the “Systems and Groups”.

Tools

SC-1295

TM Tools: Get TR List

This report /RTC/TM_TRACKING2FILE allows you to filter tracking data for transports in two systems.

It has the option to filter specific WF status and to display in ALV. Additionally, saving files onto Presentation or Application server is possible.

Icons in ALV are represented by characters

• 'X' where is a notification
• 'X' for WF status ‘In workflow monitor’
• 'E' for WF status ‘external’
• 'H' for WF status ‘in wf history’
• 'D' for WF status ‘in wf history-deleted’

When 'Save to file' is used, specify the full path and file name. The default field separator is space (horizontal tab) but can be changed.
If the report will be executed in the background then the application server should be used and the display option should be deactivated.

Transport requests can be excluded using the table /RTC/TM_NOTRK_TR.

Tools

SC-1296

TM Tools: Load Personal Queue with TR List

The report /RTC/TM_ADD2PQUEUE allows users to load transport requests from a file into their personal queues.

The selection screen requires specifying the target system SID and Client, as well as the owner of the personal queue.
The file can be loaded from either the Presentation or Application servers. The file must include an initial line with field names.

Example:

Tools

SC-1297

TM Tools: Get Tracking Info

The report /RTC/TM_TRACKING2FILE allows users to filter transport tracking data for transports in one system:

It has the option to filter specific WF status and to display in ALV. Additionally, saving files onto Presentation or Application server is possible.

Icons in ALV are represented by characters

• 'X' where is a notification
• 'X' for WF status ‘In workflow monitor’
• 'E' for WF status ‘external’
• 'H' for WF status ‘in wf history’
• 'D' for WF status ‘in wf history-deleted’

When 'Save to file' is used, specify the full path and file name. The default field separator is space (horizontal tab) but can be changed.
If the report will be executed in the background then the application server should be used and the display option should be deactivated.

Transport requests can be excluded using the table /RTC/TM_NOTRK_TR.

Tools

SC-1298

TM Tools: Set/Reset System Message

The new feature allows users to create system messages across multiple systems via an RFC connection and /RTC/TM_SET_RESET_SYS_MSG report.

• To use this feature, users must enhance the '/RTC/TM_RFC_HIGH' authorization:
  Transaction PFCG, Select Role '/RTC/TM_RFC_HIGH
  Edit>Authorizations>Change Authorization Data>+ Manually>Add authorization object 'S_ADMI_FCD' and check the authorization field 'SM02'.
• ensure 'S_ADMI_FCD' and 'S_RFC' authorization objects with the 'SM02' authorization field are set.
• Deleting system messages must be done locally as the RFC connection does not support this function.

Tools

SC-1300

Adjust all /RTC/SA* Roles to Include New Deletion Functionalities

Adjustment of all /RTC/SA* Roles to include new /RTC/SA_09 Field name and its values for new deletion activities

Activity “QUE” for deletion of Transport Requests in the Failed analysis queue

• /RTC/SA_ADMIN_ role should have “QUE” option flagged
• In all other roles should be used value “NON” (if no other deletion value is flagged)

This option will allow the button “deletion“ to be visible in the referred screen.

Activity “TSK” for deletion of Transport Requests in Tasklist

• /RTC/SA_ADMIN_ role should have “TSK” option flagged
• In all other roles should be used value “NON” (if no other deletion value is flagged)

This option will allow the button “deletion“ to be visible in the report /RTC/SA_INIT_TASKLIST which allows maintaining tasklist.

Objects analysis, Roles/Authorizations

SC-1302

Short Dump RFC_NO_AUTHORITY during the Analysis on the Customizing Job

Analysis on the Customizing job was leading to short Dump when the analysis is being executed for 2 clients in the same system.

Role /RTC/SA_CON has been enhanced to include a missing authorization for the user ZRTC_SA_ADM.

Customizing, Objects analysis, Roles/Authorizations

SC-1237

Incorrect Status Displayed for ENHS Objects

The status for ENHS object was displayed ‘NON-COMPARABLE’ when the object is missing in DEV system.

The object versionability check has been extended to include checks in both the "versobj" and "versobj_alias" tables. With this enhancement, the active version in the development system is taken into account.

Objects analysis, Workbench

SC-1103

Reset Report Displays Wrong Message

The reset report previously displayed an incorrect message when executed in test mode. Instead of showing the number of the selected Customizing object, it incorrectly stated "No Authorization to reset data".

The program has been corrected.

SM Reset, UI

SC-1389

Import Log Menu not Available for SynRequests of Released Rollouts

This release solved an issue by the import logs menu for Released Rollout SyncRequest. At selecting a Release Rollout Request on the synchronization tree, the user could not access the menu for import logs because this was disabled (grayed out).

The program has been corrected.

Synchronization, UI

SC-1384

Short Dump GETWA_NOT_ASSIGNED in Synchronization Tree When Starting Sync

The short dump GETWA_NOT_ASSIGNED has been observer when overwriting modifications in DEV system.

The program has been corrected.

Synchronization, UI, Workbench

SC-1399

Rollout Request Deletion Fails After Prior SE10 Deletion

In the previous version, users encountered a problem when trying to delete a Rollout Request from the tree that previously was deleted from SE10. The Rollout Request remained in the tree and could not be deleted from there. An error message was displayed: "Only empty RollOut Requests can be deleted." By double-clicking on it, a pop-up was displayed with the message "Task/request xxx does not exist in system xxx."

With the release of this version, we have resolved the issue of Rollout Requests persisting in the tree even after being deleted from SE10.

UI

SC-878

Incorrect Display of Rollout Request in the Workbench View

This release resolves issues with the Rollout Request icons that previously resulted in Synchronization Management displaying discrepancies. This includes instances when Rollouts were visible in the tree, but an object list was missing, or when the Rollout was empty but the released icon was still present.

The program has been corrected.

UI, Workbench

SC-1358

Missing Result of ITSM Update as Status Message after Deletion of the Transport Request

This release resolves an issue where the ITSM update status message was not being displayed after deletion of the request from Workflow Monitor.

This issue was fixed, and an ITSM status message will be displayed if the deletion was executed successfully or with an error.

Integration Framework

SC-1379

Indexes on Systems with HANA DB are not Effective

In systems with HANA DB the multi-column indexes are not effective, they should be deactivated.
Upgrade of the system to NW 7.40 with HANA DB.

The indexes are excluded for HDB.

NW/S4 platform specific issues, Performance

SC-1225

No Authorization to Access /RTC/TM for Users with /RTC/TM_USER_BASISCS after Upgrade to SP04

Users with role /RTC/TM_USER_BASICS which includes S_TCODE authorization for /RTC/TM can no longer access Transport Management.
As a workaround, the profile could be regenerated manually.

The program has been corrected.

Roles/Authorizations

SC-1197

SU53 Shows Access Error for Iser ZRTC4_TM_ADM after Imports

After successful imports of transport requests with SmartChange, SU53 shows access errors for user ZRTC4_TM_ADM, when having assigned the standard role /RTC/TM_RFC_LOCAL.

It has no impact on the import itself, or the notification emails, but it might create confusion when troubleshooting authorization errors.

In older versions of SAP, the authorization object S_RFC could have only the value FUGR (function group) for the field RFC_TYPE. Now, it is also possible to assign the value FUNC (Function Module).

Authorization role /RTC/TM_RFC_LOCAL has been updated with:

• S_RFC
  • RFC_TYPE: FUNC
  • RFC_NAME: SO_EXPRESS_FLAG_SET

Roles/Authorizations

SC-1333

Transport Request Approval from External ITSM Occurs Short dump CX_SY_DYN_CALL_ILLEGAL_TYPE

When trying to approve a transport request from an external ITSM, the process ends with the short dump CALL_FUNCTION_CONFLICT_LENG, exception CX_SY_DYN_CALL_ILLEGAL_TYPE (ABAP Program /RTC/SAPLTM_CMI, function call ‘/RTC/TM_API_APPROVAL’).

The program has been corrected.

TM/SM Integration

SC-1406