一个好用的SAP ABAP工作进程跟踪工具-阿里云开发者社区

开发者社区> jerrywangsap> 正文

一个好用的SAP ABAP工作进程跟踪工具

简介: 一个好用的SAP ABAP工作进程跟踪工具
+关注继续查看

As an ABAPer we have SAT, ST05 ( or sometimes ST12 ) for trace in our toolbox, and recently I find this report which could also do the trace job.


Although the trace information it generates is quite technical and perhaps more useful for those guys who are interested with the ABAP kernel.


How to use this report

(1) SE38, execute report RSTRC000, mark the checkbox “Keep Work process”, so that a free work process will be owned exclusively by you unless you release it via this report again. And change the trace Level to 2: Full trace. Select the component which you would like to trace, for example Database.


image.png


Click save button and you can see the work process 23 is locked.


image.png


you could observe that the work process 23 has status “halt” in tcode SM50.


image.png


(2) Now it is ready to run the program which you would like to trace ( just the similar process as SAT or ST05 ). Use /nse38 to go to ABAP editor starting from the current screen of report RSTRC000, and run your program. For me, I just run a report which will query material data from database table COMM_PRODUCT. Once the program finishes, run report RSTRC000 again.


click button “Default val.” so that trace Level is changed to 1 automatically,


image.png


then click save button and you could observe the previously locked work process 23 is released.


image.png


Now you could click “Display” button to review trace log:


image.png


You could export the trace locally to review it. For me I prefer to use my favourite text editor “sublime text” to review text file.

Here below I just list the trace review of several trace component which I have already tried myself.


Database log

from the log, I could find which database tables are involved in the report execution and which ABAP program triggers such access. Some C language call could be observed but due to security or authority reasons maybe, we could not review the source file like ablink.c in folder /bas/*.


image.png


We could also find the detail OPEN SQL statement from the log, however I could not find the value of query parameter as shown below – they are displayed as ? in the trace.


image.png


ABAP proc.

It just lists all the ABAP class which are involved in the report execution but without method name of those class. In my case from the trace I can just know there are totally 40 different ABAP class with prefix CL_CRM_PROD* ( which are responsible by me) involved in the execution.


image.png


Database (DBSL)

Since we are currently use HANA as our database, I could have a very draft understanding about how the OPEN SQL like SELECT XXX FROM table statement is executed in HANA.


image.png


Lock Management

This time I would like to trace the lock behavior in tcode COMMPR01. I switch to edit mode which triggers a lock request to enqueue server to lock the product and then I make changes on its description field.



image.png

in the trace this enqueue request is perfectly recorded:


the enqueue object

the database table on which the enqueue object is working

the guid of the product instance being locked

the tcode name COMMPR01

the user which triggers the enqueue request


image.png


From my point of view this option is a good substitute for the enqueue trace in ST05.

image.png



Background

I run my report ZHANA_OBJECT_SEARCH in the background and



image.png

and I could see from the job log that it is successfully executed.



image.png

and this information is also available in RSTRC000 trace:


image.png


I didn’t try all the other trace options and maybe they are useful under some extreme use cases. If you are interested, you can start now try it yourself


版权声明:本文内容由阿里云实名注册用户自发贡献,版权归原作者所有,阿里云开发者社区不拥有其著作权,亦不承担相应法律责任。具体规则请查看《阿里云开发者社区用户服务协议》和《阿里云开发者社区知识产权保护指引》。如果您发现本社区中有涉嫌抄袭的内容,填写侵权投诉表单进行举报,一经查实,本社区将立刻删除涉嫌侵权内容。

相关文章
用C#写一个多进程监控自动关机工具
因为据说某server开着就很贵,所以我们跑完测试的job后就要赶紧关机才行,但是测试的job要跑很久,过程中又不需要干什么,所以就得有个守家的,有时候会走很晚。如果有一个自动化关机的工具就好了,当指定的进程结束了以后系统就会自动关机。
793 0
多进程监控自动关机工具升级远程关闭多台server——C# works with PowerShell
之前给单位做过一个多进程监控的自动关机工具,详见那篇blog。 这次领导又加了需求,说要等进程监控结束后,不止需要关闭主控端server,还需要关闭其他servers。于是就用到了我上篇文章所介绍的知识——通过PowerShell来远程管理计算机。
966 0
Linux网络进程监控工具nethogs
  Linux网络监控工具nethogs 标签: 监控工具linux 2015-12-17 22:06 448人阅读 评论(0) 收藏 举报  分类: linux(40)  版权声明:本文为博主原创文章,未经博主允许不得转载。
963 0
Wndows 主进程(Rundll32)已停止工作
打开电脑,出现"windows 主进程(Rundll32)已停止工作",百度了一下,是文件损坏了。     下载一个新的文件,替换即可,若遇到权限问题,使用魔方工具中的设置大师,即可设置右键添加管理获取权限的功能。
934 0
SAP CRM HANA report里 默认filter 的工作机制分析
SAP CRM HANA report里 默认filter 的工作机制分析
11 0
使用OpenApi弹性释放和设置云服务器ECS释放
云服务器ECS的一个重要特性就是按需创建资源。您可以在业务高峰期按需弹性的自定义规则进行资源创建,在完成业务计算的时候释放资源。本篇将提供几个Tips帮助您更加容易和自动化的完成云服务器的释放和弹性设置。
11935 0
SAP 电商云 Accelerator 和 Spartacus UI 的工作机制差异
SAP 电商云 Accelerator 和 Spartacus UI 的工作机制差异
5 0
软件自动化测试工具的历史进程
软件测试最早可以追溯到1958年的美国第一个载人航天计划-水星计划,当时在该计划中首次诞生了软件测试团队。当然,在此之前也肯定是有软件测试存在的,但远没有这次有了自己的江湖地位。但这也仅仅是软件测试的萌芽,远没有到开宗立派的地步。
930 0
+关注
2628
文章
0
问答
来源圈子
更多
+ 订阅
文章排行榜
最热
最新
相关电子书
更多
《2021云上架构与运维峰会演讲合集》
立即下载
《零基础CSS入门教程》
立即下载
《零基础HTML入门教程》
立即下载