Page Properties | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
Release 5.3.0.0
Released on Apr 01, 2022
New Feature
Priority |
---|
SC-788
Replacing obsolete function modules
PANAYA tool detected obsolete function modules.
Root cause:
SmartChange code contains calls to standard SAP function modules which are marked as obsolete.
Solution:
The list of obsolete function modules was analyzed. Most of them have been replaced according to SAP suggestions, and the rest have been marked for further review.
SC-679
Title | Release Note |
---|
SC-880
Column name changed form "Transport request" to "Request"
Due to length reasons, the column name "Transport request" was changed to "Request".
SC-873
Enhance TMC with approval list
With this feature, all waiting approvals for selected TM servers can be displayed in the TMC.
A new button is available to switch between the approval list and the alert list. Depending on the monitor setting, the approval list will contain only selected approval types.
SC-856
Permit customer adding of User-Exits
Allow customers to add CUSTOMER EXIT TYPES beside the standard Realtech types. The restriction: Custom added CUSTOMER EXIT TYPE name should start with 'ZZ'.
SC-849
Exclude transports in history when adding transports to TM manually
When adding transports to TM manually, in the list of transport also transports that are in history will be shown, the list can become very large and finding the transports that you want will be very painful. Therefore a check-box to enable or disable the selection from history was added in the selection screen.
SC-826
Customizing enhanced to consider exception objects when creating a Synchronizing Request
The user has the possibility to define Exception objects in the SyM Customizing. These objects are excluded from the analysis.
With this new feature, the status of the object (ex. "Excluded") is shown in the screen 'Create Customizing sync request', as displayed in the Customizing Object Comparison screen. The user has now the option to filter by excluded objects or to delete excluded objects.
SC-804
Update Jira after transport request was switched automatically to the next level
This function performs an update in the Jira SmartChange Panel after the transport request has been automatically moved to the next level. In case of an automatic content approval, the approval data is also updated.
SC-803
Update Jira after release transport request w/o add to TM Workflow
This function performs an update in the Jira SmartChange Panel at release of transport request also when is not added to the Transport Management.
Components | Reference | |
---|---|---|
Allow Transport of Copies to be assigned to an External ITSM issue ID | With this new feature, Transport of Copies (ToC) can now also be assigned to an external ITSM issue (ex. Jira), same as Workbench or Customizing transport requests. |
BAdI, Integration Framework, NW/S4 platform specific issues | SC- |
Deploy application roles to development systems via TM Update assistant
With this feature, the TM Update assistant will apply the application roles transport to all the development systems.
The queue generation is based on the tm_upd.txt file. The new code, SDEV, determines the import in all development systems configured in TM > Global settings > Standard systems, for all active clients with the role 'Development' or space.
679 | ||||
Update Jira after release transport request w/o add to TM Workflow | This function performs an update in the Jira SmartChange Panel at release of transport request also when is not added to the Transport Management. | Integration Framework | SC-803 | |
Update Jira after transport request was switched automatically to the next level | This function performs an update in the Jira SmartChange Panel after the transport request has been automatically moved to the next level. In case of an automatic content approval, the approval data is also updated. | Integration Framework | SC-804 | |
Enhance TMC approval and alert list with custom attributes | Possibility to display TM attributes as columns in the alert and approval list of TMC. |
|
|
|
| TMC, UI | SC-597 |
Enhance TMC with approval list |
SC-370
Synchronisation of Translation Object
This feature allows the synchronization of translation objects via Transport Requests.
With this feature, all waiting approvals for selected TM servers can be displayed in the TMC. | TMC, UI | SC-873 | ||
Column name changed form "Transport request" to "Request" | Due to length reasons, the column name "Transport request" was changed to "Request". | TMC, UI | SC-880 | |
Deploy application roles to development systems via TM Update assistant | With this feature, the TM Update assistant will apply the application roles transport to all the development systems. | TM Update Assistant | SC-658 | |
Filter in the TM Monitor to select all TRs with intersection of 2 attribute-values | With this feature, the user can filter in the TM for Transport Requests with more than one attribute. The TM Attribute filter can be set by using the “TM Attribute” button in the filter area. Using the “TM Attribute” Button a pop-up is displayed to add TM attributes entries to a list. The TM-Attribute name is mandatory. The value field is not mandatory, if this is empty or ' |
' then all the Transport that have the inserted TM-Attribute name will be selected. The value field is key-sensitive and does not work with value + ' |
' like 'REALT*'. |
Bugs
UI | SC-69 | |||
Exclude transports in history when adding transports to TM manually | When adding transports to TM manually, in the list of transport also transports that are in history will be shown, the list can become very large and finding the transports that you want will be very painful. Therefore a check-box to enable or disable the selection from history was added in the selection screen. | UI | SC-849 | |
Permit customer adding of User-Exits | Allow customers to add CUSTOMER EXIT TYPES beside the standard Realtech types. The restriction: Custom added CUSTOMER EXIT TYPE name should start with 'ZZ'. | User Exits | SC-856 |
SC-861
System Locked even when Lock is not active
If a system is locked and a new client is added, this client will be added as locked. After the system is unlocked, the client will remain locked and the system acts like a locked system.
Root cause:
Programming error.
Solution:
The program has been corrected.
SC-848
Project/Destination short text is not displayed all the time
Project/Destination short text is not displayed all the time
Priority | Title | Release Note | Components | Reference |
---|---|---|---|---|
Customizing enhanced to consider exception objects when creating a Synchronizing Request | The user has the possibility to define Exception objects in the SyM Customizing. These objects are excluded from the analysis. | Customizing, Synchronization | SC-826 | |
Synchronisation of Translation Object |
SC-949
TM: Dump trying to delete dependencies
Short Dump CALL_FUNCTION_PARM_UNKNOWN in ABAP program /RTC/SAPLTM_SERIAL happens when trying to delete a dependency between two transport requests in TM Monitor.
Root cause:
Programming error.
Solution:
The program has been corrected.
SC-948
TM: German translation missing for dependencies description
In TM Monitor, the German translation is missing for the description of the dependencies types.
Root cause:
Programming error.
Solution:
The program has been corrected.
This feature allows the synchronization of translation objects via Transport Requests. | Synchronization, UI, Workbench | SC-370 |
Priority | Title | Release Note | Components | Reference |
---|---|---|---|---|
Extend the Jira templates in the TM Integration Framework by the work item J2O | As a prerequisite configuration step for using the column 'Ticket ID' from the TM Monitor to jump directly to the assigned Ticket ID in the default web browser, you must configure work item J2O in the TM Integration Framework cockpit (/RTC/TM_IF_CONFIG>ITSM systems configuration). J2O work item has been included in the template configurations: TEMPLATE _JIRA CLOUD, TEMPLATE _JIRA SERVER. For the hyperlink to work correctly, make sure you also have defined the server path in the corresponding ITSM definition (ex. https://server-path.atlassian.net). | Integration Framework | SC-978 | |
Replacing obsolete function modules | Issue: Root cause: Solution: | NW/S4 platform specific issues | SC-788 |
Fixed Bugs
Priority | Title | Release Note | Release Note Solution | Components | Reference |
---|---|---|---|---|---|
Authorization failed due to missing authorization role during SyM Customizing analysis | Issue: Root cause: Solution:
| Customizing, Objects analysis, Roles/Authorizations | SC-677 | ||
Customizing objects wrongly not displayed in the tree with filtering options | Issue: Root cause: Solution: | Customizing, Objects analysis, UI | SC-789 | ||
Short Dump MESSAGE_TYPE_X when filtering Rollout | Issue: Root cause: Solution: |
Synchronization, UI, Workbench | SC- |
815 |
Priority | Title | Release Note | Release Note Solution | Components | Reference |
---|---|---|---|---|---|
Empty Transports freezes System Queue | Issue: Root cause: Solution: |
Performance, Queues/Proposals, UI | SC- |
847 | ||
TM: Dump trying to delete dependencies | Issue: |
When adding a filter to Rollout Request by owner, it creates the DUMP MESSAGE_TYPE_X in program CL_GUI_CFW====================CP on the DEV
CALL_FUNCTION_PARM_UNKNOWN in ABAP program /RTC/SAPLTM_SERIAL happens when trying to delete a dependency between two transport requests in TM Monitor. Root cause: Solution: | Quality Assurance | SC-949 | |
System Locked even when Lock is not active | Issue: Root cause: Solution: |
Queues/Proposals | SC- |
Customizing objects wrongly not displayed in the tree with filtering options
When filtering in the initial customizing selection screen, if all selected customizing objects have not been analyzed, nothing is displayed
861 | ||
Project/Destination short text is not displayed all the time | Issue: Root cause: |
Programming error. Solution: |
SC-677
Authorization failed due to missing authorization role during SyM Customizing analysis
Sometimes, SyM Customizing analysis fails due to missing authorization for the user.
Depending on objects being analyzed, different failed authorization checks are registered, for example when creating the CUST initial job
has been corrected. | UI | SC-848 | |
TM: German translation missing for dependencies description | Issue: Root cause: |
Programming error. Solution: |
Authorization role /RTC/SA_CON updated with:
* S_RFC - RFC_name : FUNCTION_EXISTS, SCCR*
* S_TABU_NAM - Activity: 02, 03
* S_TABU_CLI
| UI | SC-948 |
Priority | Title | Release Note | Release Note Solution | Components | Reference |
---|---|---|---|---|---|
An /RTC/ authorization role is missing to allow creation of Smart Connection | Issue: Root cause: Solution: | Roles/Authorizations | SC-670 |