Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Release 5.2.4.0

Released on Jun 25, 2021

New Feature

Priority Key Summary Status
High SC-753 With this new feature, you are now able to trace configuration changes done for the TM Integration Framework (transaction code /RTC/TM_IF_CONFIG), used to connect ITSM systems to SmartChange.

For the following configuration tables, the "Log data changes" setting has been enabled, allowing you to display the logs using transaction SCU3 - Table History:

Table name | Description
/RTC/TM_IF_CONFIG | TM IF: Global settings
/RTC/TM_IF_STAT | TM IF: Workflow configuration per action/level
/RTC/TM_IF_ITSM | TM IF: ITSM definition
/RTC/TM_IF_ITEM | TM IF: Web resource/Item definition
/RTC/TM_IF_FIELD | TM IF: Fields definition for Web Resource/Item
/RTC/TM_IF_DEV | TM IF: Development systems for ITSM
/RTC/TM_IF_OPT | TM IF: Optional settings at ITSM level
/RTC/TM_IF_POC | TM IF: POC user list

Note!
Logging only takes place if the parameter "rec/client" in the system profile is set correctly. 		Done
Medium SC-752 With this feature, a new column was added to TM Workflow Monitor to display the package description. Done
High SC-748 With this new feature, the parameters 'ExternalAtribute' and 'ExternalId' of the OData call for creating a transport request (sap/opu/odata/RTC/TM_GW_SRV/Transport_RequestSet) are now linked to the TM Integration Framework configuration.

As default:
- 'ExternalAttribute' represents the value of the ITSM id. The default SAP attribute name where the value will be saved is the value from TM IF configuration>Global Activation Settings>ITSM Attribute.
If no value is configured, the default SAP attribute delivered with the TM Integration Framework will be used (ZRTC_TM_ITSM_ID).

- 'ExternalId' represents the value of ticket/issue id. The default SAP attribute name to be used is the configured value in the TM IF >ITSM system configuration.
If no value is configured or the ITSM system is not found, the default SAP attribute delivered with the TM Integration Framework will be used (ZRTC_TM_TICKET_ID).

BAdI /RTC/TM_BD_GET_CONF can be used for implementing your own logic to associate the two OData parameters to different SAP attributes. Otherwise, the default implementation /RTC/TM_BIM_GET_CONF~GET_CONF will be called. 		Done
Medium SC-741 With this feature, in TM>Package administration, the drop-down menu for the field Package displays the technical number and the description. This way, you can now easily select the right package.
Also, the TM>Package administration view has been improved to display the package header information in a more user-friendly manner. 		Done
High SC-740 With this new feature, you can now use Jira Automation rules with the TM Integration framework. This allows you to trigger transitions of Jira Issues at a specific event in SAP (ex. Move issue to "In review" at TR release in SAP).

The TM Integration Framework configuration cockpit (transaction /RTC/TM_IF_CONFIG) has been enhanced as follows:

1. ITSM Systems configuration:
- At the ITSM system level, you can maintain the automation server and the RFC destination for it.
- For each ITSM system, with the new "Automation" view, you can maintain the webhooks used for triggering the Jira Automation rules.

2. TM Workflow step configuration:
The webhooks defined at the previous can now be assigned to the following TM actions:
* Creation of a request
* Release and export request
* Approval of a request
* Import of a request.

Note1:
For Jira Server instances, the automation server is the same hostname as the Jira server instance. Therefore the same RFC destination to the Jira Instance can be used also as the Automation Server RFC.
For Jira Cloud instances, the automation server is different. Therefore, you need to set up a new RFC destination for the automation server and upload the corresponding SSL certificate in transaction STRUST.

Note2:
On the Jira side, you are required to use the Jira Automation.
The Jira Automation rules must be defined as triggered by incoming webhooks. 		Done
High SC-711 To test the integration for a specific system before everyone will see the pop-up, a POC user list is required. This configuration is possible via t-code /N/RTC/TM_IF_CONFIG in the menu 'ITSM system configuration' under the node 'Dev systems'.

If the table is maintained for the current DEV system, then the current user for the current DEV system must be in the table. If the POC user list is empty, the integration is active for all users. 		Done
High SC-695 With this new feature, the OData service for the Creation of TR can be used without passing a target system.
Parameter 'Tarsystem' is an output parameter only.
The consolidation target is automatically determined by the system. If no consolidation target is configured or set as default, the request will be created as local transport request. 		Done
Medium SC-373 With this feature, the TM administrator can delete more System Queues at the same time. The functionality for TM>Import Scheduler>"Delete all jobs" has been enhanced, so the administrator can choose to either delete one of the selected queues or all the queues that have been previously selected in the tab "Select System Queues".
In addition, the drop-down for selecting a single System Queue to be deleted considers the previous selection and proposes only the pre-filtered queues. 		Done

Bugs

Priority Key Summary Status
Medium SC-765 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. 		Done
Critical SC-756 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. 		Done
Medium SC-755 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. 		Done
Medium SC-751 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'. 		Done
Medium SC-749 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. 		Done
Medium SC-746 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. 		Done
Medium SC-745 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. 		Done
Medium SC-738 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. 		Done
Medium SC-737 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. 		Done
Medium SC-736 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. 		Done
Medium SC-734 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 		Done
Medium SC-732 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. 		Done
Critical SC-728 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. 		Done
Medium SC-715 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. 		Done
High SC-706 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. 		Done
Medium SC-700 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. 		Done

Powered by Automated release notes for Jira
  • No labels