REALTECH SmartChange SP3 HF01

SC-993

OData Service: Get transport request and return 'Dependencies' of Quality Checks

1. The Odata Service to read transport requests has been extended with the possibility to read Dependencies.
GET /sap/opu/odata/RTC/TM_GW_SRV/Transport_RequestSet

The following URL parameters are supported:
- filter | example: filter=Trkorr eq 'NDQK900011'
- expand | example: expand=TR_Dependency

2. The new Odata Service is created to read Dependencies of a transport request
GET /sap/opu/odata/RTC/TM_GW_SRV/TR_DependencySet

The following URL parameters are supported:
- filter | example:filter=Trkorr eq 'NDQK900011'

The type of dependency is encoded in output field 'Type', meaning:
S -> Successor
P -> Predecessor
C -> Companion
CS -> Companion: Successor
CP -> Companion: Predecessor

SC-992

OData Service: Get transport request and return 'Special Aspects' of Quality Checks

1. The Odata Service to read transport requests has been extended with the possibility to read Special Aspects.
GET /sap/opu/odata/RTC/TM_GW_SRV/Transport_RequestSet

The following URL parameters are supported:
- filter | example: filter=Trkorr eq 'NDQK900011'
- expand | example: expand=TR_Special_Aspects

2. The new Odata Service is created to read Special Aspects of a transport request
GET /sap/opu/odata/RTC/TM_GW_SRV/TR_Special_AspectsSet

The following URL parameters are supported:
- filter | example:filter=Trkorr eq 'NDQK900011'

SC-991

OData Service: Approve transport request with reason for ignoring collisions

This Odata Service approve transport requests with reason for ignoring collisions. The reason is also saved in the action log.
PUT /sap/opu/odata/RTC/TM_GW_SRV/TR_ApproveSet(Trkorr='<transport request>')

The following body parameters are supported
- UserName, Approve, ApprovalType, ProdLevel, TestLevel, ExternalUser, CollisionReason

Body example :
{
"UserName": "REALTECH",
 "Approve": "A",
 "ApprovalType": "T",
 "ProdLevel": "",
 "TestLevel": "",
 "ExternalUser": "USER",
 "CollisionReason":"Odata test"
 }

SC-988

OData Service: Simulate Approval extended with returning of authorization result for accepting approval quality checks

This Odata Service to Simulate Approval was extended to return if user has the authorization to accect quality checks result of the approval.
GET /sap/opu/odata/RTC/TM_GW_SRV/QA_TM_TRSet

The following URL parameters are supported:
- filter | example: filter=Trkorr eq ‘NDQK900011'
- expand | example: expand=NavToCollisions,NavToCritObj,NavToDependency,NavToSpecialAspects

The authorization result is to find in the field ACTION, when TRKORR = SPACE

SC-972

Odata Service: Simulate Approval with Quality Checks as result

This Odata Service returns the results of the quality checks for a specific transport request.
GET /sap/opu/odata/RTC/TM_GW_SRV/QA_TM_TRSet

The following URL parameters are supported:
- filter | example: filter=Trkorr eq ‘NDQK900011' and Approve eq 'A’
- expand | example: expand=NavToCollisions,NavToCritObj,NavToDependency,NavToSpecialAspects

SC-970

Report to rework Returncode Forecast scan

With this new feature, a new report /RTC/R_LIB_RF_SCAN_START was created to scan transports already released. The report takes into consideration only TR's created in the current system.
The selection can be done :
- for specified transport requests
- all the transport from the date of the last scan until today
- all the transports from a specified starting date until today

SC-961

Allow locking and unlocking of multiple projects and destination

With this feature, the user has the possibility to lock or unlock multiple projects and destinations in the Project Administration.

SC-950

Allow locking and unlocking of multiple SAP systems in Systems and Groups

With this feature, the user has the possibility to lock or unlock multiple SIDs or groups of systems simultaneously in 'System and groups' .

SC-945

OData Service: Read of all transport requests and packages waiting for approval by level name and approval type

This Odata Service returns all transport requests and packages in a specific level or for all levels for the specified approval type.
GET /sap/opu/odata/RTC/TM_GW_SRV/Transport_RequestSet

The following URL parameters are supported:
- filter | example: filter=LevelName eq '*' and ApprovalType eq '*' and AuthorityCheck eq true
- expand | example: expand=TR_Workflow

SC-935

OData Service: Count of all transport requests waiting for approval by level name and approval type

This Odata Service determines and returns the number of transport requests and packages in a specific level or for all levels for the specified approval type.
GET /sap/opu/odata/RTC/TM_GW_SRV/TM_Count_TRSet

The following URL parameters are supported:
- filter | example: filter=LevelName eq 'TEST' and ApprovalType eq '*'

SC-927

OData Service: Approval of packages

The Odata service for approvals has been extended so that, in addition to transport requests, packages can also be approved.
PUT /sap/opu/odata/RTC/TM_GW_SRV/TR_ApproveSet(Trkorr='<Package_No>')

The following body parameters are supported
- UserName, Approve, ApprovalType, ProdLevel, TestLevel, ExternalUser, CollisionReason

SC-879

Auto delete Semaphore

The new global feature "Hours until auto delete semaphore" is added to TM SmartChange > Global Settings > Feature Tab.
This field controls the auto deletion of the semaphore if no tp process is running. It allows the specification in hours.

If the TP process is not running in the target system and the last semaphore was set more than the defined hours ago, the system queue will delete the semaphore and the import will set a new semaphore with the current date and time.
If value equals '0', the auto deletion is off.

SC-857

Display reason why system queue was locked by administrator

With this new feature when the lock is set for a system queue, a reason for the lock should be maintained. This reason can be displayed if is pressed the additional button next to the lock message.

SC-723

Upload transport files when add a new transport request to the TM Workflow Monitor

This new feature allows to upload transport request files from the presentation server into transport files folder from application server, when a new transport request is added to the TM Worflow Monitor.
When selecting the menu 'Request' > 'Add', a new icon 'Upload Transport (F2)' is available to upload the files.

SC-652

Translation of transaction /RTC/TM_IF_CONFIG into German

Transaction /RTC/TM_IF_CONFIG was translated into German.

SC-543

Extension of the display of the system queue locking information with user and date

With this feature, when a queue is locked or unlocked, it is also displayed by whom and when this was done. This affects the following areas:
- Workflow monitor > Display system queue
- Tools > Queue Management >Display Queue
- The email that is sent automatically was extended. The subject of the email additionally contains the user and the content contains additional information about the user, date and time who locked or unlocked the queue.

SC-1018

OData Service: The error message ‘Action only possible by group members' is displayed incorrectly

Issue:
When approving a transport request using Odata Service, the service returns the message ‘Action only possible by group members', even though the transport request has been successfully approved for the user group the user belongs to.

Solution:
The program has been corrected.

SC-1005

When using filter on existing Synchronisation-Request it dumps

Issue:
When trying to filter on an existing SyncRequest, if a Transport Request is not added on filtering, the Pop-up window dumps.

Solution:
The program has been corrected.

SC-999

Error displayed in Systems & Groups RFC check

Issue:
Error '/RTC/TM_INI on system '<SID>' is executed with wrong parameters.’ appears at RFC connection check, in System & Groups.

Solution:
Program was changed.

SC-998

Error during distribution to multiple TM servers with loader /RTC/TM_LD_15

Issue:
After the upgrade to v5.2.3.0, report /RTC/TM_LD_15 can no longer be used to distribute transport requests to multiple TM Servers.
The report is scheduled with variant TM-system = <Central TMS> and the job is finished without any error, but the TRs are only distributed to the Central TMS.

Solution:
The program has been corrected to handle distribution to multiple TM servers at the release of a transport request.
The following configuration must be done for this scenario:
* Table /RTC/LO8 must be configured in the development system
* Report /RTC/TM_LD_15 must be scheduled as periodic job on the development system:
    - triggered by the event (configured in /RTC/TM_BADI);
    - variant: TM-system = <Central TMS>
* all the secondary TM Servers must be defined in TM Central > System and groups.

SC-997

The reason of overwriting collisions to the action log is not written for all transport requests

Issue:
The Actionlog, for the reason to overwriting collisions, is written only for the first transport request.

Solution:
The program has been corrected.

SC-995

'Object * COMMENT could not be attached to RollOut Request!' displayed in the log after synchronisation

Issue:
If transport contains lines with ProgramId equal '*' , the error 'Object * COMMENT could not be attached to RollOut Request!' is displayed in the log, because the program ID equal '*' is not considered.

Solution:
The program was changed

SC-985

Umode is only partially assigned to client level after destination copy

Issue:
Create a new destination by copying the already existing destination with Umode, the Umodes are not assigned to the first client for the new destination.

Solution:
The program has been corrected.

SC-981

Wrong overtakers are displayed when simulating collisions for manually added transport requests

Issue:
When adding transport requests manually into TM Monitor, the reference date and time can be different from the export time and date, depending on the settings (/RTC/TM_SPECS table).
In this case, when pressing 'Simulate collisions', the overtakers are wrongly calculated.

Solution:
The program has been corrected.

SC-979

Collisions popup not displayed for content approval with multiple groups

Issue:
For content approval with 2 user groups, the Quality Assurance popup is not displayed for either group. When this situation occurs, the popup is always displayed at the revoke of the 2nd group approval and the 'Simulate collisions' functionality wrongly displays all collisions as overtakers.
For technical approval, the popup always works (both for approval and revoke).
The behaviour was reproduced when the 1st content approval was already given for the colliding transports.

Solution:
The program has been corrected.
As default functionality, the QA popup is always displayed when the last content approval is given. For technical approval, the QA popup is displayed for all user groups.

SC-976

Customizing Synchronization-Request can only be assigned to one Rollout-Request

Issue:
For customizing transport requests, the same original transport from maintenance can't be assigned to more than one rollout request

Solution:
The program was changed to allow the same original transport from the maintenance system to be added to a new rollout transport if the previous rollout was released.

SC-973

Non-ABAP Transports are not filtered by TM attributes

Issue:
Non-ABAP Transports are not filtered by attributes. They are ignored in the code for attributes filtering.

Solution:
The code was changed.

SC-959

Filter lost after refresh of TMC Approval List

Issue:
After the refresh, the filter is deleted if data is filtered.

Solution:
Program was changed.

SC-958

Same customer attribute values are displayed multiple time in TMC

Issue:
The attribute values are displayed multiple times

Solution:
Program was fixed.

SC-956

Short dump OBJECTS_OBJREF_NOT_ASSIGNED in program /RTC/TM_UI_STATUS_SWITCHER

Issue:
Switching to the edit mode in transaction /RTC/TM_SW and press again the edit button a short dump occurs

Solution:
The program has been corrected.

SC-942

Short dump TSV_TNEW_PAGE_ALLOC_FAILED when executing the report /RTC/R_LIB_RF_JOB_EXPORT_SCAN

Issue:
When releasing a Transport Request in development system, having Return Code Forecast active in the TM Server, the job /RTC/R_LIB_RF_EXPORT_SCAN sometimes ends with the short dump TSV_TNEW_PAGE_ALLOC_FAILED. This is because in S/4HANA 2020, more object types have become versionable.
Entries like MSAD/MSAG are not handled correctly by RCFC analysis at export. The report runs into a recursive infinite loop.

Solution:
The program has been corrected.
In order to identify if an object is versionable, both table VEROBJ and VERSOBJ_ALIAS are checked.
Complex versionable entries (like MSAD in S/4HANA 2020) - a category that did not exist before - are now successfully handled.

SC-932

RC Final is not coloured red in System Queue when import is running

Issue:
RC Final column is not red-coloured in the system queue screen when the import is running

Solution:
The program has been corrected.

SC-911

Destination short text is wrongly truncated after 30 character

Issue:
When creating a new destination the short text will be truncated after 30 characters although the limit is 60.

Root cause:
Programming error.

Solution:
The program has been corrected.

SC-910

Destination wrongly deleted after short name changed

Issue:
If a destination is being created and the short text is changed before saving, the destination disappears from the configuration and can no longer be saved.

Solution:
The program has been corrected.

SC-881

Reporting does not show packages in history

Issue:
When running the Request LifeCycle and filtering for type 'Package', only the packages that are in the Workflow Monitor are displayed. The packages that are in the history cannot be found in the reporting while transport requests can be found.

Solution:
In the selection area two checkboxes were added: 1. 'Include Workflow Monitor', 2. 'Include Workflow History'. With this new option, the user can decide if the Request LifeCycle includes Packages/Requests from Workflow Monitor/History or both.

SC-875

Bad Performance in Transport Management History

Issue:
Opening the transport management history takes a long time if there is a large number of transport requests in the history. Even the use of a filter, displaying the details also takes a long time.

Solution:
Performance changes implemented

SC-683

Import of /RTC/TM_BACKUP transport request ends with RC=8

Issue:
With /RTC/TM_BACKUP Report the user can create a transport request to transfer the TM content from one system to another. When this transport is imported into the system, an importing error (RC=8) are generated.

Root cause:
This error occurs when the backup transport was not imported into the 000 client. Because, no matter where the /RTC/TM_BACKUP report was started, the transport is created in the 000 client.

Solution:
If the backup transport is imported in a different client than the one in which it was created, then this should be imported with the following import options:
- Overwrite Originals
- Ignore Non-Permitted Table Class
- Ignore Invalid Component Version

The /RTC/TM_BACKUP Report was also enhanced with a new field for the client, to be able to choose where the transport will be created.

SC-549

Transaction names are incorrect in SAP Easy Access > Favorites

Issue:
Some descriptions for the /RTC/* transactions are out of date.

Solution:
The descriptions have been updated.

SC-366

Display owners full name doesn't working in distributed landscape

Issue:
The solution implemented for displaying the full name of the owner of a transport request in the TM monitor does not work for distributed landscapes (TM server not on DEV).

Solution:
The /RTC/TM_REQ table was enhanced with a new field for 'Author's full name' which is populated when the entry Transport Request is inserted in the TM Monitors.
The transport request that already exists in TM, don't have the full name filled in the /rtc/tm_req table, therefore a new report was developed for this case. With the /RTC/TM_FILL_FULL_NAME report, the user can fill the owner full name field in the /rtc/tm_req. The Report bring the owner full name from the development system. If the TM Server doesn't have an RFC connection to the development system or this is not reachable, the name will be read from the TM server. The owner full name can be filled for all transport, only where is missing or for specific users/transports. The Report have also a test mode, where can be observed the "old name" and the "new name" which will be filled in the "Full_name" field for /rtc/tm_req table.