How to perform an error analysis on SAP side?
Maybe something is not working as expected. In this case you want to perform some basic error analysis activities. This analysis might help you to detect and fix an issue by your own. Even if you cannot fix it, the analysis result might help us to help you.
- 1 Analyze issues
- 2 Fix issues
- 2.1 Recalculation of final transports: Report /XALM/CC5_HELP_REACTIVATE_TR
- 2.2 Remove a transport request from CC5 table: Report /XALM/CC5_HELP_DELETE_TR and /XALM/CC5_HELP_DELETE_TR_MULTI
- 2.3 Refreshing Transport Header and Tracking details: Report /XALM/CC5_HELP_REFRESH_TR
- 2.4 Refreshing ChaRM Transport Header and Tracking details: Report /XALM/CC5_SM_TL_REFRESH_TR
Analyze issues
Short Dumps: Transaction ST22
Especially if the Jira app is alerting a http 500 error, you should search for a short dump in your “endpoint system” which is the SAP Solution Manager system (deployment option 1) or domain controller system (deployment option 2).
It might be helpful to search for short dumps in your managed systems too: If access to a managed system failed due to missing authorities, there might be some short dumps created in your managed system.
SAP Gateway Error Log and Trace: /IWFND/ERROR_LOG + /IWFND/TRACES
If you are facing any issue receiving/processing an odata call, you should have a look into the SAP Gateway Error log of your endpoint system. If this is not helping, you should activate a trace for your technical user used by the Jira app.
Please note that you have to call these transaction codes with /n/IWFND/ERROR_LOG and /n/IWFND/TRACES in SAP GUI.
TMS Alert Viewer: STMS
If you might face an error related to some CTS functionalities, maybe caused by technical or authority issues, you should perform an analysis of the TMS Alert viewer.
Please goto STMS → Monitor → TMS Alerts → TMS Alert Viewer.
Please perform this check in your endpoint system and in your managed system.
Application Log: SLG1
Since ABAP version 2.6.0 our solution is storing logging information to the application log accessible via transaction code SLG1 or SLGD. However, some used SAP standard functionalities might do it as well. Therefore it is not a bad idea to check SLG1 too. In your endpoint system and your managed system.
Additionally to CC5, SAP CTS or SAP Solution Manager are also performing some logging in SLG1. Maybe these logging features need to be activated. For instances: If you are facing an error message “System <SYSTEMNAME> is currently not available. Action cannot be executed.“ using CC5 with SAP Solution Manager, it might be helpful to logon to SAP Solution Manager, call transaction DNO_CUST04, set parameter CM_TROUBLE_SHOOT_LOG to X and check SLG1 log after the failed call.
RFC Destinations: SM59
The endpoint system is receiving requests from the Jira app. It is converting the request in a sequence of CTS function calls. These calls are triggering activities in your managed systems. As prerequisite a lot of RFC destinations need to be existing and working. THese RFC destinations where either be generated by managed system configuration of SOLMAN_SETUP of your SAP Solution Manager system or by TMS configuration of SAP Transport Management System of your domain controller system.
If you are facing connectivity issues inside your landscape, you should check your RFC destinations in transaction SM59 (connection check + authority check). Maybe a host or port got changed? Maybe a technical user is locked? Maybe some authorities are missing?
Landscape, Deployment, Import details: Report /XALM/CC5_HELP_GET_LANDSCAPE
Sometimes the landscape definition is not read or not evaluated correctly. To understand what is going wrong, this report can be used. If this report is raising any exceptions or returning no valid data, please check TMS Alert Viewer additionally, in your endpoint system and in your managed system.
The report is reading the landscape definition of a given source system.
It is reading the deployment details for a given transport request.
It is reading the import details of this transport request for a given import system.
You can call the report using transaction call SE38 or SA38 in your SAP GUI. This report is available from CC5 version 2.2.0.
Fix issues
Recalculation of final transports: Report /XALM/CC5_HELP_REACTIVATE_TR
For performance reasons, transport request data are not read/updated anymore if STATUS is P and NEXT_SYSTEM is empty. If moving to this status was caused by a bug or misconfigured landscape setup, you might want to trigger/force a recalculation. For this purpose, you can use this report. It will change the status to "?" which will trigger a reread/update on next fetch/read by the Jira app.
You should restrict this call to a dedicated set of transport requests. Only in a few cercumstances it is a good idea to trigger the recalculation for all final transport requests. You can use the asterisks * to trigger a complete recalculation. However, there is no risk to execute the report for all transport requests as long as the system landscape and the transport requests are still existing and the landscape and deployment details can still be read and evaluated. This also means that you should never trigger a recaclulation for a landscape which go decommissioned or for transport requests which got removed from the tms transport directory.
You can call the report using transaction call SE38 or SA38 in your SAP GUI. This report is available from CC5 version 2.2.0.
Remove a transport request from CC5 table: Report /XALM/CC5_HELP_DELETE_TR and /XALM/CC5_HELP_DELETE_TR_MULTI
Let’s assume a Jira issue got converted or deleted. Then the TR is still assigned to the not existing jira issue and cannot be reassigned to annother issue till it is getting deassigned using this report.
Let’s assume your are decommissioning an external system or an ABAP system but the CC5 table /XALM/D_CC5_REQ is still containing a lot of useless transport details for these systems. Then a clean-up activity could be helpful for improving performance or reducing data volume.
You can call the report using transaction call SE38 or SA38 in your SAP GUI. This report is available from CC5 version 2.2.0.
Refreshing Transport Header and Tracking details: Report /XALM/CC5_HELP_REFRESH_TR
You might face the issue that the transport details stored in CC5 table /XALM/D_CC5_REQ is not up to date. When using the Jira app you will not face any issue because the date are always getting updated when opening a Jira ticket. But if you want to perform a reporting based on table /XALM/D_CC5_REQ you might need data which are up to date. You can use this report to achieve it.
You can call the report using transaction call SE38 or SA38 in your SAP GUI. You can schedule it as regular job. This report is available from CC5 version 2.2.0.
Refreshing ChaRM Transport Header and Tracking details: Report /XALM/CC5_SM_TL_REFRESH_TR
Let’s assume you are using the task list integration by selecting a cts project id which is assigned to a task list. Now you want to perform a mass import using the task list import option. You are facing the issue, that some transport requests are not in scope of the import in some circumstances. You are detecting the root cause, that some entries in table /TMWFLOW/TRORD_N are not up to date: Some transport requests are flagging as modifiable even if they are already released.
There is no ChaRM configured in your landscape, therefore the ChaRM feedback mechanism, which is updating this table automatically, is not working. Also report /TMWFLOW/CMSSYSCOL2 might not be working for some reasons, which is usually updating this table once a day.
In case you the table is not getting updated or not getting updated at the right time you can use this report to trigger an refresh on ChaRM tables like /TMWFLOW/TRORD_N and /TMWFLOW/TRACK_N.
You can call the report using transaction call SE38 or SA38 in your SAP GUI. You can schedule it as regular job. This report is available from CC5 version 2.2.0.