...
Release 5.4.1.0
Released on Nov 30, 2022
New Feature
Priority |
---|
SC-1209
Title | Release Note |
---|
SC-1214
Change date of the template entries to field type timestamp
With this feature, field CREATIONDATE has been changed to use field type "TIMESTAMP" for templates TEMPLATE_ SOLMAN_SMIN and TEMPLATE_ SOLMAN_SMIR. This configuration settings allows you to view the timestamps in a user friendly format.
Components | Reference | |
---|---|---|
New template in the TM Integration Framework for ServiceNow connection | With this feature, you can easily configure a Service Now system within the TM Integration Framework, without knowledge of the technical details.
For the ITSM configuration, 2 item types are available: GET → Query to read Service Now Incidents For the Workflow step configuration, the following actions are included:
For UPD item type/ Update SNOW Incident:
|
Configuration, Integration Framework, ServiceNow | SC- |
1209 | ||
OdataService: Return request TM workflow level and status for getting quality aspects | Add level and status information in OData to get collisions Ex.
|
OData Services | SC- |
Improvement of the change of the license key in the TM Controller
With this feature if a temporary key for the installation is used and if later this should be changed to a perpetual or subscription one, the change can be done in the TM Server on System/Groups using “Change license key”.
This change will also change the local license key in the development system.
SC-1110
Automatically update the whitelist entries for all ZRTC* RFC Connections
The transaction /RTC/SC_WHITELIST will be used to update whitelist information in TM/SYM RFC destinations.
The transaction should be called from TM/SYM server.
SC-1087
1198 | ||
Display of the date non-technically in the popup of the request assignment (GET action) | With this new feature, timestamp fields read from external ITSM systems are displayed in SAP user-friendly, during the assignment of a ticket to a transport request. |
Integration Framework | SC- |
Quality checks with a custom-specific Special Aspect
The new feature is used to add custom Special Aspects checks at the quality aspects check.
A new custom Special Aspect can be created in the template of the Special Aspects:
For the implementation please use new enhancement spot. /RTC/TM_IF_ES_CUSTOM_SA_CHECK. This is deliverd with example implementation /RTC/TM_IF_BIM_CUST_SA_CHECKEX.
1087 | ||||
ServiceNow update on creation | With this new feature, SNOW App - SmartChange tab is updated at transport request creation, if a SNOW incident has been assigned to the transport request. | Integration Framework, ServiceNow | SC-888 | |
ServiceNow configuration included in the standard TM Integration Framework | With this feature request, you can configure TM integration with a Service Now instance within the standard. | Integration Framework, ServiceNow | SC-887 | |
Change date of the template entries to field type timestamp | With this feature, field CREATIONDATE has been changed to use field type "TIMESTAMP" for templates TEMPLATE_ SOLMAN_SMIN and TEMPLATE_ SOLMAN_SMIR. This configuration settings allows you to view the timestamps in a user friendly format. | Configuration, Integration Framework | SC-1214 | |
ServiceNow update on import into a target system | With this new feature, SNOW App - SmartChange tab is updated at transport request import into a target system via TM, if a SNOW incident has been assigned to the transport request. |
Integration Framework, ServiceNow | SC- |
891 | ||
ServiceNow update on approval and revoke approval | With this new feature, SNOW App - SmartChange tab is updated at transport request approval or revoked approval, if a SNOW incident has been assigned to the transport request. |
Integration Framework, ServiceNow | SC- |
890 | ||
ServiceNow update on release | With this new feature, SNOW App - SmartChange tab is updated at transport request release, if a SNOW incident has been assigned to the transport request. |
Integration Framework, ServiceNow | SC- |
889 |
Priority | Title | Release Note | Components | Reference |
---|---|---|---|---|
Improvement of the change of the license key in the TM Controller | With this |
SC-887
ServiceNow configuration included in the standard TM Integration Framework
With this feature request, you can configure TM integration with a Service Now instance within the standard.
feature if a temporary key for the installation is used and if later this should be changed to a perpetual or subscription one, the change can be done in the TM Server on System/Groups using “Change license key”. This change will also change the local license key in the development system. | Configuration, TM Connectivity | SC-1131 | ||
Automatically update the whitelist entries for all ZRTC* RFC Connections | The transaction /RTC/SC_WHITELIST will be used to update whitelist information in TM/SYM RFC destinations. The transaction should be called from TM/SYM server. | Security, TM Connectivity | SC-1110 | |
Archive TM-History data | A new transaction /RTC/TM_ARCHIVE is used to archive TM history data. The archived transports can be displayed from the transaction /RTC/TM menu: | TM History | SC-877 | |
Quality checks with a custom-specific Special Aspect | The new feature is used to add custom Special Aspects checks at the quality aspects check. A new custom Special Aspect can be created in the template of the Special Aspects: For the implementation please use new enhancement spot. /RTC/TM_IF_ES_CUSTOM_SA_CHECK. This is deliverd with example implementation /RTC/TM_IF_BIM_CUST_SA_CHECKEX. | BAdI, Quality Assurance | SC-1083 | |
Limit import tracking into the same system | Import in a system defined as production, in users and groups, will be possible only for the users with authorization for authority object ZRTC_TM with ID '/RTC/TM_AC' = ‘IT’. (The users without authorization will not see PROD system and client in the search help for the target system for the personal queue ) If the source and target system and client are the same a popup message will be displayed for confirmation of the selection. | Roles/Authorizations, Security, Tools | SC-261 |
Fixed Bugs
Priority |
---|
Title |
---|
Release Note | Release Note Solution |
---|
SC-1208
Import Scanner terminates with short dump CALL_FUNCTION_CONFLICT_TYPE after upgrade to SC 5.4.0.0
Components | Reference | |
---|---|---|
Message text /RTC/TM_IF_MSG_CALL031 contains obsolete info | Message text of message /RTC/TM_ |
IF_MSG_CALL031 contain obsolete info. | The message text of message /RTC/TM_ |
IF_ |
MSG_CALL031 was updated whit the new transactions. | Integration Framework, UI | SC-1015 |
OData ImportSet As4date invalid format | The result of the call is the error ‘Property 'As4date' has invalid value ''’ . |
The program has been corrected. | OData Services | SC- |
Special Job is not created
The special JOB for transports in signature status is not created.
1207 |
Priority | Title | Release Note | Release Note Solution | Components | Reference |
---|---|---|---|---|---|
STMS Job scheduled triggers SyM analysis at import | Enhancement for standard STMS Job not to trigger event for objects analysis comparison in case SyM configuration at_import is disabled. | The program has been corrected. |
BAdI, Objects analysis | SC- |
Short dump RAISE_EXCEPTION in program /RTC/SAPLTM_QA when opening special aspects details tab
When openig special aspects details tab a short dump RAISE_EXCEPTION occured in program /RTC/SAPLTM_QA.
The dump occurs when special aspects is empty.
SC-1192
The "Other period" button in the Job Scheduler does nothing
In the Job-Scheduler if the periode 'other ' is selected, a small button 'Other period' is shown. By clicking on that button, the program is jumping out.
1202 | |||||
CDAT objects not able to synchronize | Sometimes the CDAT original transaction can not be added to the rollout transport | The program has been corrected. | Customizing, Objects analysis, Workbench | SC-1123 | |
Empty transport requests added to the Tasklist | All the transport request at release are added to the tasklist, even the empty ones. | The program was changed to prevent adding empty transport requests to the tasklist. | Customizing, Objects analysis, Tasklist, Workbench | SC-1117 |
Priority | Title | Release Note | Release Note Solution | Components | Reference |
---|---|---|---|---|---|
Short dump RAISE_EXCEPTION in Program /RTC/SAPLTM | Short dump at the call of function module /RTC/TM_MESSAGE_GET_TEXT when exception NO_T100_FOUND was raised. |
If the message is not found for the needed language, then an additional check will be done if the message exists in English and if is not found the exception NO_T100_FOUND will be raised. The program was modified to catch the exception. | UI | SC- |
1155 | |||
Blank Pop-up in Job Scheduler | By trying to save a scheduled job, an empty pop-up message is displayed. | The program has been corrected. |
Scheduler | SC- |
1150 | |||||
Saving the Special Aspects with SAP objects takes too long | Saving the Quality Assurance takes a very long time if SAP objects are selected and activated in the Special Aspects. | The reason for this was that the table index was not used. | Performance, Quality Assurance | SC-1149 | |
Indexes on systems with HANA DB are not effective | In systems with HANA DB the multi-column indexes are not effective, they should be deactivated. | The indexes are excluded for HDB. | NW/S4 platform specific issues, Performance | SC-709 | |
Import Scanner terminates with short dump CALL_FUNCTION_CONFLICT_TYPE after upgrade to SC |
5.4.0.0 | Program “/RTC/TM_IMPORT_SCANNER” is terminated with runtime error CALL_FUNCTION_CONFLICT_TYPE, exception CX_SY_DYN_CALL_ILLEAGAL_TYPE. The call to function module “/RTC/TM_JOB_SET_PERIO_FOR_PROG” is incorrect - “LV_TEXT has a field type different than the function module interface parameter EV_TEXT”. | The program “/RTC/TM_IMPORT_SCANNER” is obsolete, report “/RTC/TM_IMPORT_SCANNER_MAIN” has to be used instead, by scheduling it from TM > Global settings > Import scanner tab. However, to support smooth upgrades from older versions, if the report “/RTC/TM_IMPORT_SCANNER” was already scheduled, at the next run after the upgrade in background mode, the report will modify the job to call the correct program. The program has been corrected to correctly modify the import scanner job. | Tools | SC-1208 | |
Special Job is not created | The special JOB for transports in signature status is not created. | The program has been corrected. | Queues/Proposals | SC-1206 | |
Short dump RAISE_EXCEPTION in program /RTC/SAPLTM_QA when opening special aspects details tab | When openig special aspects details tab a short dump RAISE_EXCEPTION occured in program /RTC/SAPLTM_QA. | The program has been corrected. | Quality Assurance | SC-1193 | |
The "Other period" button in the Job Scheduler does nothing | In the Job-Scheduler if the periode 'other ' is selected, a small button 'Other period' is shown. By clicking on that button, the program is jumping out. | The program has been corrected. | Scheduler | SC-1192 | |
Empty message, when lock multiple systems in Systems & Groups | When locking multiple systems in Systems & Groups, if the lock button is clicked a second time, then an empty pop-up message is displayed. |
The program has been corrected. | Configuration | SC- |
1146 | ||
Import in 'SUBSET' mode returns code blank | Sometimes imports via SUBSET are logged into the TM with the return code blank and red color and marked as imported. The reimport cannot be performed via TM after this, only via STMS. Analyzing the logs from the target system, it seems that:
|
Import system queue using SUBSET has been enhanced to handle blank return code as error 9950 - Exception during tp call: could not specify return code. For further troubleshooting, additional logging points have been added in the SUBSET system queue to save the results of tp commands: add to buffer and import subset (tp_retcode, tp_subrc, tp_message). The logging points can be activated by running report /RTC/R_LIB_LOGGING_MANAGER in the target system, setting Configuration > Logging level 5. | Queues/Proposals | SC-1139 | |
Short dump after changing and saving something in Special Aspects | Shortdump after changing and saving something in Special Aspects |
SC-1123
CDAT objects not able to synchronize
Sometimes the CDAT original transaction can not be added to the rollout transport
In tables E071, E071k the field ACTIVITY is filled and is not considered by SYM.
SC-1117
Empty transport requests added to the Tasklist
All the transport request at release are added to the tasklist, even the empty ones.
SC-1015
Message text /RTC/TM_IF_MSG_CALL031 contains obsolete info
Message text of message /RTC/TM_IF_MSG_CALL031 contain obsolete info.
SC-709
Indexes on systems with HANA DB are not effective
Upgrade of the system to NW 7.40 with HANA DB.
The program has been corrected. | Quality Assurance | SC-1126 |