Release 5.3.3.0

Released on Aug 30, 2022

New Feature

Product

Transport Management

Title	Release Note	Components	Reference
TM_BADI enhancement: Check special aspects before release	With this feature, the TM Badi configuration is extended. In addition to checking for Critical Objects, it is now also possible to check and display Special Aspects before release. This feature causes issue SC-1070 Done (Dump CALLBACK_REJECTED_BY_WHITELIST at TR release) if you have the callback security mode set to '3' (secure). Please adjust the ZRTC* RFC whitelist according to the instructions in the related issue.	BAdI, Quality Assurance	SC-1060
Create a template for Solution Manager configuration	With this feature, you can easily configure a Solution Manager system within the TM Integration Framework, without knowledge of the technical details. For the configuration 2 templates are available: TEMPLATE_ SOLMAN_SMIN TEMPLATE_ SOLMAN_SMIR For the ITSM configuration, 2 item types are available: GET -> Query Solution Manager Tickets J2O -> Jump from TM Monitor to the Solution Manager Ticket For the Workflow step configuration, the following actions are included: TEMPLATE_ SOLMAN_SMIN GET AFTER_WF_A After workflow assignment before release is finalized TEMPLATE_ SOLMAN_SMIN GET CREATION Creation of a request TEMPLATE_ SOLMAN_SMIR GET CREATION Creation of a request	Configuration, Integration Framework	SC-1074
Update Jira Configuration Templates with Action STATUS_SW	The Jira TM IF configuration templates, TEMPLATE_ JIRA CLOUD and TEMPLATE_ JIRA SERVER, have been enhanced with the new action, STATUS_SW for Item type 'UPD', for activating the Jira Update on Status Switch.	Configuration, Integration Framework	SC-1100
Make action "Creation of a request" available for Solution Manager Integration	With this feature, you are now able to assign a Solution Manager Ticket to a transport request in SAP, at the creation time of the transport request. As prerequisite, you need to install and activate the OData service /RTC/SOLMAN_SRV on the Solution Manager system.	Integration Framework	SC-813
Extract TM Notes from one Server and Upload to a different one	This new feature gives the option to copy TM transport notes from one TM server to another TM server. The report /RTC/TM_COPY_TR_NOTE will be executed in TM server where notes should be updated. The source system from where the notes are copied will be from parameters R/3-System or RFC Destination.	Notifications/Mails, TM History, UI	SC-1056
Adapt TM WF-Monitor to higher resolutions 4k/8k	With this feature, the size of the TM WF-Monitor subscreen was increased to maximum size.	UI	SC-778

Fixed Bugs

Product

Transport Management

Title	Release Note	Components	Reference
Checking Critical Objects at TR Release does not work for sub-objects	Issue: Checking for critical objects at release time does not recognize an object as critical, if the Quality Assurance configuration contains not the object itself, but its development class, with ‘check sub-objects’ flag set. This seems to occur because the code to identify the development class of the analyzed object is executed on the TM Server (which can be a Solution Manager, not containing the objects) instead of the development system. Solution: The program has been corrected. The check is done in the development system.	BAdI, Quality Assurance	SC-1050
Error when jumping to ITSM Ticket from TM Monitor	Issue: If multiple ITSM systems are configured in the TM Integration Framework, jumping to the ITSM Ticket from TM Monitor by clicking on column 'Ticket ID' does not work. The following error message is displayed, even though the configuration is correctly done: 'Please define item type J2O for ITSM ID &. Transaction code /RTC/TM_IF_CONFIG'' Solution: The program has been corrected, the issue was caused by a programming error.	Integration Framework, UI	SC-1071
/RTC/TM_LD_15 reports running in parallel transfer transports multiple times from DEV to the TM system	Issue: When transports are released, an entry is created in the /rtc/tm_lo81 table with the project/destination route combination. The transports are transferred from development systems to the TM system with event-controlled jobs with /RTC/TM_LD_15. If the destination route combination is blocked on the TM, the entries remain in /rtc/tm_lo81, waiting for the next event or scheduled job. When the destination route combination is open on the TM, if the distribution job has a lot of accumulated transports for distribution, that may take a long time. If other transports are released in the meantime, the event-controlled LD_15 runs again and takes a large part of the LO81 entries, which are already 'in progress in the previous LD_15. In this situation, the same transports can be included multiple times in the TransportManager. Solution: The /RTC/TM_LD_15 was adjusted. When the LD_15 reads the transports entries from the /rtc/tm_lo81 table, these are also locked so that the LD_15 can run multiple times in parallel jobs, without processing the same transport requests.	Loaders/Switchers	SC-1064
Dump CALLBACK_REJECTED_BY_WHITELIST in dev system at transport request release	Issue: When the whitelist check is active in the development system (parameter rfc/callback_security_parameter = 3), the short dump CALLBACK_REJECTED_BY_WHITELIST occurs at transport request release. Root cause: New function modules are called with destination 'BACK', as a result of enhancing the TM_BADI with special aspects checks before release ( SC-1060 Done ). Solution: The default whitelist for the ZRTC* RFC destination was adjusted with the new function modules. In order to correct the whitelist, the customer should run /RTC/TM_INI transaction in client '000' in the development system with the option "Maintain whitelist" for the Sid of TM server. The whitelist will be adjusted with the new lines: Called Function Module \|Callback Function Module /RTC/TM_IF_QA_AT_RELEASE \| /RTC/TM_GET_TADIR /RTC/TM_IF_QA_AT_RELEASE \| /RTC/TM_GET_DD02L /RTC/TM_IF_QA_AT_RELEASE \| RFC_PING /RTC/TM_IF_QA_AT_RELEASE \| /RTC/TM_OBJECT_LIST /RTC/TM_IF_QA_AT_RELEASE \| /RTC/TM_DOCU_READ /RTC/TM_IF_QA_AT_RELEASE \| /RTC/TM_GET_REQUEST /RTC/TM_IF_QA_AT_RELEASE \| /RTC/TM_GET_DOCU_INFO /RTC/TM_IF_QA_AT_RELEASE \| /RTC/TM_CHECK_AUTHORITY	Security	SC-1070
When adding a note for transport the UI shows an option for deletion of multiple requests	Issue: When adding a note for a transport request, the popup for creating the note shows an option for enabling the deletion of multiple requests. Solution: This option has been hidden when entering the note creation screen with the function TM > Notes. It is only displayed when creating the note as part of the TR deletion process.	UI	SC-1059

Product

Synchronization Management

Priority

Title

Release Note

Release Note Solution

Components

Reference

High

Short dump CNTL_ERROR when running the SyM>Workbench analysis at Release

Issue:
Short dump CNTL_ERROR occurs in program CL_GUI_CUSTOM_CONTAINER=======CP, when running the analysis job for SyM Workbench analysis at transport request release. The DUMP is created on the DEV system.

Solution:
Report /RTC/SA_AFTER_EXPORT_ANALYSIS triggers the mentioned runtime error when analyzing objects of type ‘ENHS’ (Enhancement Spot) when running in background. The standard function module SVRS_COMPARE_OBJECTS cannot be executed in the background for ENHS object type.

The program was modified, and ENHS object types are now correctly analyzed via SyM in background jobs. The ENHS objects are no longer analyzed with function module SVRS_COMPARE_OBJECTS (this FM is mandatory for CDS views mostly).

Objects analysis, Workbench

SC-1062

Powered by Automated release notes for Jira

Browser not supported