REALTECH SmartChange SP4 HF08

Enhance the 'Simulate collisions' function

This release introduces an enhanced 'Simulate Collisions' function for transport requests, providing customers with additional options for determining collisions. A sub-menu is accessed via right-clicking on a transport to provide the customer with a choice of behaviours when simulating collisions for approval or revocation of approval.

Right-clicking on a transport

Button “Simulation collisions”

Approval

SC-1313

Optimization of TM Selection Screen

This release includes an optimization of the TM selection screen, allowing new fields to fit within the screen without the need of scrolling.

The Quick-Filter selection will only be displayed if filters are defined and the user can configure the setting to have the Quick-Filter selection visible when initiating the SmartChange transaction in the SmartChange Settings.

This can be configured in SmartChange > Settings > User dependent -> 'Show quick filter for TM attributes'.

UI

SC-1309

Add job analysis feedback for each scheduled job

With this feature, a new column has been added in the Analysis Job ALV to include also the feedback from job analysis, so that not only the last feedback of how many objects have been analyzed is displayed. Because in the case several jobs are running in parallel that info is lost from the jobs which finish first.

Configuration, Objects analysis, UI

SC-479

Update Jira on deletion of TR from TM

This release adds a new feature to TM Workflow Monitor that allows users to trigger an update to the ITSM/Ticket ID assigned to a transport request when it is deleted from TM Monitor, either manually or via switcher at the end of the request lifecycle. To ensure its proper functioning, certain prerequisites must be met, such as configuring TM IF. Additionally, any errors encountered when updating the ITSM services are logged and can be recalled manually or automatically.

Prerequisites

A 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 (Delete transport request from TM Workflow Monitor)

The template entries can be copied and used as references.

Troubleshooting

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 also be triggered either manually or automatically (job schedule or subsequent update calls triggered by working with the specific transport request in TM Workflow Monitor: such as approval, import, or switch status).

Integration Framework, Jira_App

SC-509

Update SNOW on deletion of TR from TM

This release adds a new feature to TM Workflow Monitor that allows users to trigger an update to the ITSM/Ticket ID assigned to a transport request when it is deleted from TM Monitor, either manually or via switcher at the end of the request lifecycle. To ensure its proper functioning, certain prerequisites must be met, such as configuring TM IF. Additionally, any errors encountered when updating the ITSM services are logged and can be recalled manually or automatically.

Prerequisites

A 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 (Delete transport request from TM Workflow Monitor)

The template entries can be copied and used as references.

Troubleshooting

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 also be triggered either manually or automatically (job schedule or subsequent update calls triggered by working with the specific transport request in TM Workflow Monitor: such as approval, import, or switch status).

Integration Framework, ServiceNow

SC-1370

Enhance TM Integration Framework Jira Template for action 'Delete TR from TM Monitor'

The Jira TM Integration Framework configuration templates have been enhanced with action DELETE (Delete Transport Request from TM Monitor) for Item type ‘UPD’. This action will allow users to view a deleted transport request from TM in the Jira SmartChange panel with the corresponding status.

The following templates are affected by this update:

Jira templates: TEMPLATE_ JIRA CLOUD, TEMPLATE_ JIRA SERVER

UPD/ DELETE - Delete transport request from TM WF Monitor

Integration Framework, Jira_App

SC-1371

Enhance TM Integration Framework SNOW Template for action 'Delete TR from TM Monitor'

The ServiceNow TM Integration Framework configuration templates have been enhanced with action DELETE (Delete Transport Request from TM Monitor) for Item type ‘UPD’. This action will allow users to view a deleted transport request from TM in the ServiceNow SmartChange tab with the corresponding status.

The following templates are affected by this update:

SNOW template: TEMPLATE_ SNOW_INC

UPD/ DELETE - Delete transport request from TM WF Monitor

Integration Framework, ServiceNow

SC-1372

New function "Reassign" as Odata Service

With this new feature, a new OData service is available for triggering the reassign of a transport request to another ITSM/ Ticket Id from outside SAP.

OData definition:

OData service name: /RTC/TM_GW
New EntitySet: TR_ReassignSet
HTTP Method: PUT

Entity properties:

Example of OData call:

URL: /sap/opu/odata/RTC/TM_GW_SRV/TR_ReassignSet('MDQK900133')
Method: PUT
Body:

{
"ItsmIdOld": "RT-DEV MASTER",
"TicketIdOld": "MDX-1",
"ItsmIdNew": "RT-DEV MASTER",
"TicketIdNew": "MDX-2"
}

Use cases:

1. If the transport request is already released and inserted into the TM Workflow, the corresponding* TM attributes are changed. User needs the authorization to maintain TM attributes (TA).
2. If the transport request is modifiable, the corresponding* SAP attributes are changed. For this use case, a trusted RFC must exist from the TM server to the source system and source client of the transport (name of RFC destination ZRTC4_TM_<DEV_SID>_<DEV_CLIENT>_TRUST), the same prerequisite as for the OData to Create Transport Request.
3. If the transport request is released outside TM, nothing will be done. TM attributes do not exist and SAP attributes for already released TR cannot be changed.

*Corresponding TR attributes are determined by the default BAdI implementation /RTC/TM_BIM_GET_CONF of Badi /RTC/TM_BD_GET_CONF (same used for OData to Create Transport Request.
If TM Integration Framework is active and configured, the TM attributes are retrieved from TM IF. Otherwise, the following default attributes are used for mapping:

• ItsmIdOld/ ItsmIdNew → ZRTC_TM_ITSM_ID
• TicketIdOld/ TicketIdNew → ZRTC_TM_TICKET_ID
  -TicketGuidOld/ TicketGuidNew → ZRTC_TM_TICKET_GUID

Logging and troubleshooting

All OData calls for service /RTC/TM_GW_SRV are logged in table /RTC/TM_CON_LOG, with the corresponding success or error message.

All changes to a TM attribute are logged in the TM Monitor > Transport Request details > Action log.

If TM Integration Framework is also configured, after changing the TM attribute values on the SAP side, the corresponding ITSM update calls are also triggered to delete the previous assignment of TR to Old Ticket Id and create the new assignment to the New Ticket Id. All ITSM update calls are logged in transaction /RTC/TM_IF_LOG. If any of these calls fail, they are saved for further reprocessing via transaction code /RTC/TM_IF_MONITOR.

Jira_App, OData Services

SC-920

Too many ITSM system are displayed during reassign for external transports

For TM Integration Feature ‘Reassign [ITSM]/Ticket ID’, if several ITSMs are configured and enabled for ‘Reassign’, they are displayed multiple times in the popup to assign Ticket Id.

If multiple ITSMs are enabled for reassignment, they are now shown once in the assignment popup.
The program has been corrected.

Integration Framework, UI

SC-1355

Bug when displaying ITSM and Ticket number in mails

The program has been updated to ensure that the ITSM System is displayed in the emails when TM Integration Framework is active regardless of the golbal settings for TR_TYPE 'A' = All, ' ' = Customizing and Workbench

The program has been corrected.

Integration Framework, Notifications/Mails

SC-1359