Release 5.2.0.0
Released on Feb 08, 2021
New Feature
| Priority | Key | Summary | Status |
|---|---|---|---|
|
SC-577 |
With this feature, you can filter Project and Destinations based on transport type, when releasing a Transport Request into TM or when manually adding it to TM. External transport requests are treated as a separate transport type. You can maintain allowed transport types for specific destinations in TM>Configuration>Destinations. If no transport type is maintained for a destination, then all transport types are allowed. |
Done |
|
|
SC-541 |
The authorization concept for SmartChange has been enhanced to fullfill following security finding concept: - "Missing AUTHORITY-CHECK in RFC-Enabled Functions" - "Missing AUTHORITY-CHECK in Reports" A new authorization object ZRTC_COM - REALTECH SmartChange Common has been created. The standard /RTC/ Roles have been enhanced as follows: 1. A new common single role has been created: /RTC/SC_COM_SECURITY - which encapsulates the ABAP Code Security Authorizations. 2. The single role /RTC/SC_COM_SECURITY has been included in the following composite roles: SyM: /RTC/SA_ADMIN SyncAssist Admin Role /RTC/SA_DEV Sync Assist Developer Role /RTC/SA_DEV_EXTENDED SyncAssist Developer Role: Extended /RTC/SA_VIEWER SyncAssist Viewer Role TM - Application Roles: /RTC/TM_DEVELOPER TM-Role for Developer /RTC/TM_APPROVER1 TM-Role for approver1 /RTC/TM_APPROVER2 TM-Role for approver2 /RTC/TM_SUPER_APPROVER1 TM-Role for super approver1 /RTC/TM_SUPER_APPROVER2 TM-Role for super approver2 /RTC/TM_PROJECT_MANAGER TM-Role for Project Manager 3. The following Single Roles have been enhanced to include the new ABAP Code Security Authorizations: SyM: /RTC/SA_CON SyncAssist Generic Role TM - Application Roles: /RTC/TM_RFC_LOCAL TM-Profile for user 'ZRTC4_TM_ADM' in work clients /RTC/TM_ALL TM: All in TM + Standard authorizations TM - Communican Roles: /RTC/TM_RFC_HIGH TM: Transport- und Jobuser TM-client /RTC/TM_RFC_MEDIUM TM: Transportuser TM-client /RTC/TM_RFC_LOW TM: User TM-client |
Done |
|
|
SC-510 |
With this new feature, you can easily integrate your third-party ITSM system with SmartChange Transport Manager. The main actions that you can achieve on the SAP side are the following: * Assign an ITSM ticket at Creation of the Transport Request * Trigger updates of the ITSM ticket from SAP at different moments: * At TR Creation/Deletion * At TR Release * At TR insertion into TM Workflow * At TR Approval in TM Monitor * After TR import in target system using TM Using the TM Integration Framework and the TM OData Services, you can enable end-to-end change management between SAP and non-SAP systems - like Jira, ServiceNow or Siemens Polarion. "SAP Transport Integration for Jira", available on the Atlassian Marketplace, is an out-of-the-box integration with preconfigured workflows and offers the user the functionality to control SAP transports directly and easily from Jira. For detailed information, please consult the SAPTIJira User Manual. |
Done |
|
SC-487 | With this feature, you can automatically copy SAP attributes into TM attributes when a transport request is released. For this, the table /RTC/TM_CONF_SAT must be filled with the corresponding attribute pairs. | Done |
|
|
SC-336 |
The TM standard role /RTC/TM_ADMINISTRATOR has been enhanced to allow the deletion of the personal queues for a different user (ex. obsolete users) via /RTC/TM_TOOLS -> Queue Management -> Right click -> Delete personal queue. ( ZRTC_TM authorization object - Activity 'DP' (Delete Personal Queue) ) By default, the role /RTC/TM_ALL also contains this authorization. |
Done |
|
|
SC-317 | With this feature, you can now use report /RTC/SA_RESET to clear also the Task List. | Done |
|
|
SC-292 | With this feature, you can now see the Project and Destination description in TM Monitor, having two separate columns for Name and Description and also in the Popup to Assign Project/Destination at Transport Request release. | Done |
|
|
SC-291 |
This feature allows you to define a system as SAP S/4 HANA when defining the systems in "Systems & Groups". The following system types are now available: - SAP S/4HANA - ABAP - Virtual - Non-ABAP |
Done |
|
|
SC-288 | This feature allows you to have a quick overview of all SAP HANA objects that are included in the transport request, from the TM Monitor. The object list is displayed in a new tab 'SAP HANA Objects' in the Detail view of a transport request. This tab is available only if the transport request contains SAP HANA objects. | Done |
|
|
SC-260 | With this feature, you can add a short text for Projects and Destination, in addition to the technical name. The short text is maintained for Projects in Project Management and for Destinations in the maintenance of Destinations. | Done |
|
|
SC-239 |
This feature allows you to delete the Personal Queue of obsolete users. The TM Admin can do this from /RTC/TM_TOOLS>Queue Management and right-click on a personal queue. For this, the 'DP'(Delete personal) permission included in the /RTC/TM_ADMINISTRATOR role is required (ZRTC_TM authorization object). |
Done |
|
|
SC-234 |
With this feature, you can easily identify if SAP HANA-specific objects are transported using Transport Manager. A new column 'SAP HANA' has been added to the TM Workflow monitor. The meaning of all icons displayed in TM Monitor can be checked in TM>TM Help>Color key. |
Done |
|
|
SC-142 |
With this feature, you are able to connect from external resources to SAP Smartchange>Transport manager. RESTful web services have been created with SAP OData API under the name ‘/RTC/TM_GW_SRV’. The following actions are possible: * Check TM license * Create Transport Request * Get Transport Request details: Standard SAP TR details, TM Workflow information, TM Approvals and TM Import information * Release Transport Request/ Add Transport Request to TM Workflow * Delete Transport Request from TM Workflow * Get/Create/Update Transport Request TM attributes * Get Transport Request collisions * Get Transport Request critical objects * Get Transport Request object list * Create/Delete Transport Request dependency relationship in TM Workflow * Approve Transport Request in TM Workflow For detailed information, please consult the TM OData Services user manual. |
Done |
|
|
SC-128 |
With this feature, Transport Manager has been confirmed to transport SAP HANA content in the following scenario: 1. SAP HANA content for ABAP for SAP HANA application Transport Scenario: * SAP HANA Transport for ABAP (HTA) or HANA Transport Container (HTC) Or ABAP Managed objects (CDS Views, ABAP Managed Stored procedure) * Uses the transport routes configured for the ABAP Systems Scenarios to be investigated next: 2. SAP HANA content for native SAP HANA applications or non-ABAP application that are based on SAP HANA, if CTS+ is in use Transport Scenario: * Extended Change and Transport System (CTS+) using specially configured transport routes 3. SAP HANA content for native SAP HANA applications, if CTS+ is not in use Transport Scenario: SAP HANA Application Lifecycle Management |
Done |
Bugs
| Priority | Key | Summary | Status |
|---|---|---|---|
|
|
SC-614 |
Issue: When accessing TM Help > System Info in S/4HANA 1909, the dump CX_SY_RANGE_OUT_OF_BOUNDS occurs. Root cause: The length of the field for service pack level was changed by SAP. Solution: The program has been adjusted. |
Done |
|
|
SC-611 |
Issue: After activating the RFC callback whitelist for SAP System, a dump CALLBACK_REJECTED_BY_WHITELIST occurs while running transaction /RTC/TM_UPDATE, when checking the transport files. Root cause: RFC Callback whitelist was activated for SAP System, but whitelist entries for Transport Manager Add-On are missing. Solution: The following whitelist entries are to be added in all RFC destinations of TM controller, where an import will be performed, as well as in the RFC destinations to the development systems. Whitelist entries are also to be added in the SAP Development systems to the RFC Destinations to TM controller. Called FM | Callback FM /RTC/TM_WIZ_CHECK_AND_PREP_TR | EPS_GET_FTP_SYSTEM_INFO /RTC/TM_WIZ_CHECK_AND_PREP_TR | EPS_OPEN_INPUT_FILE /RTC/TM_WIZ_CHECK_AND_PREP_TR | EPS_READ_BLOCK /RTC/TM_WIZ_CHECK_AND_PREP_TR | EPS_READ_TEXT_BLOCK /RTC/TM_WIZ_CHECK_AND_PREP_TR | EPS_CLOSE_FILE Transaction /RTC/TM_INI has also been enhanced to consider the whitelist entries when creating the needed TM RFC destinations. |
Done |
|
SC-608 |
Issue: When executing transaction /RTC/TM_INI with marked checkbox 'Create RFC destination', the error message "Fill in all required entry fields" is displayed. Root cause: Programming error. The flag for maintenance of the whitelist is set although the Whitelist maintenance is greyed out. The user is asked to fill in a field that is hidden. Solution: The program has been corrected. |
Done |
|
|
SC-604 |
Issue: Standard Function Module TR_DISPLAY_REQUEST requires additional permissions, starting with newer SAP NetWeaver versions (ex. 7.52) or S/4HANA systems. Therefore, the minimum set of standard authorizations needed for SM must be adjusted. Root cause: The standard SAP authorization concept for displaying the objects list of a transport request has been changed. The following Authorization Objects are now required: S_TCODE - TCD = SE80 S_DEVLEOP - ACTVT = 03 (Display) Solution: The Role /RTC/SA_CON (SyncAssist Generic Role) has been enhanced to include the following authorization: S_TCODE - TCD = SE80. |
Done |
|
|
SC-602 |
Issue: The button "List" in the TM Workflow Monitor>Request Header for displaying the List of Objects of a Transport Request does not do anything. This behavior can be reproduced for Development Systems with newer SAP NetWeaver versions (ex. 7.52) or S/4 HANA systems. Root cause: The standard SAP authorization concept for displaying the objects list of a transport request has been changed. The following Authorization Objects are now required: S_TCODE - TCD = SE80 S_DEVLEOP - ACTVT = 03 (Display) Solution: The following /RTC/ standard roles have been enhanced, with the two authorization objects described above: Communication Roles: /RTC/TM_RFC_LOW TM: User TM-client /RTC/TM_RFC_MEDIUM TM: Transportuser TM-client /RTC/TM_RFC_HIGH TM: Transport- und Jobuser TM-client Application Roles: /RTC/TM_USER_BASICS TM: Minimal authorization for TM user /RTC/TM_RFC_LOCAL TM-Profile for user 'ZRTC4_TM_ADM' in work clients /RTC/TM_ALL TM: All in TM + Standard authorizations |
Done |
|
|
SC-600 |
Issue: TM Monitor>TR Details>Attribute>Attribute Sets tab contains typos in the German translation. Root cause: Error. Solution: The translation has been corrected. |
Done |
|
|
SC-599 |
Issue: The names of the Realtech application roles /RTC/* are not displayed in German or not at all. Root cause: Translation in German is missing. Solution: The German translations have been added. |
Done |
|
|
SC-596 |
Issue: By calling the transaction /RTC/TMC, the program ends with the short dump 'CONNE_IMPORT_WRONG_COMP_LENG'. Root cause: Programming error. Solution: The program has been corrected. |
Done |
|
|
SC-574 |
Issue: If a system is in several destinations and the user tries to delete one job only from a specific queue, over the Job-Scheduler, the system doesn`t delete the correct job. Root cause: The internal table was not sorted correctly. Solution: The code was corrected. |
Done |
|
|
SC-457 |
Issue: Short dump at TR release with message: "Screen output without connection to user", when the release is done in a non-dialog mode, like JOB or ODATA call. Root cause: The screen is called in a non-dialog session. Solution: The program has been corrected. |
Done |
|
|
SC-448 |
Issue: Whitelists for RFC have been activated on the systems and authorization checks are failing using Synchronization Management. Root cause: Additional checks are done based on this parameter activation which are causing authorization checks to fail on Synchronization Management. Solution: It is necessary to maintain the RFC Callback Whitelist on Synchronization Management RFC's. Additional enhancements on Roles delivered have been done. |
Done |
|
|
SC-187 |
Issue: If a Proposal is created and the scheduled import time coincides with the start time of a periodic import job for the same system, the Proposal job is banned and breaks off after a minute. In this case, if the transport requests included in the Proposal were not imported, the Proposal job can be rescheduled only by resetting the Proposal status. Root cause: Product restriction - the proposal can only be scheduled once. Solution: New functionality was implemented. The user is now allowed to copy an old proposal. All the transport requests from the old proposal are copied to the new proposal. The new proposal can be scheduled, allowing a rerun of the import for the same set of transports. |
Done |