sap系统中的batch_SAP UI5里Batch操作和Read操作的区别

最新推荐文章于 2024-03-13 15:26:37 发布

宅货

最新推荐文章于 2024-03-13 15:26:37 发布

阅读量155

点赞数

文章标签： sap系统中的batch

本文链接：https://blog.csdn.net/weixin_32236693/article/details/112041166

版权

博客讲述了作者在处理一个客户问题时，发现系统在更新预约后产生了不必要的三次读取操作。通过深入调试，作者发现这个问题源于标准代码的一个最新变更未在客户系统中生效，导致了刷新标志设置不一致。最终，作者找到了问题根源并提供了一个已知问题的论坛链接，节省了后续的调试时间。

摘要由CSDN通过智能技术生成

I would like to share with you my story today about fighting with one customer incident. We can make changes on Appointment and click save button:

There is a batch operation observed in Chrome network tab to update appointment as expected. However, why every time there are three subsequent appointment read roundtrips?

The callstack clearly shows that the three roundtrips are NOT issued by customer extension, or else the customer js file could be observed in the callstack.

Set a breakpoint on the top most callstack, h function. Check the content of e.target.data:

This is actually the batch request payload which could be observed in Chrome network tab:

This finding gives me more confidence that these roundtrips are issued by framework, not standard or customer application code. So I just continue debugging until I reach this suspicious stack:

in line 1957, this.bRefreshAfterChange = true.

However, in our internal system ( where everything works fine, there is no duplicate read operations ), this.bRefreshAfterChange = false, which has suppressed the refresh operation. This is the reason why the read operation could not be found in my internal system, since they are not executed at all. But in customer system, _isRefreshNeeded returns true, which leads to the execution of all subsequent read operations.

So why is this difference between two systems? In Chrome development tool, search the boolean variable name and we found one function setRefreshAfterChange defined for ODataModel. Just set a breakpoint in this method and re-launch the application in my internal system from beginning:

Breakpoint is triggered:

However, this line in customer system is missing, which is the root cause – our latest standard code didn’t reach customer system. After I found the root cause, I search in SCN to check whether there are other poor guy which had encountered the same issue with me, and actually I found one:http://scn.sap.com/thread/3724174

If I read this thread several months earlier, I would save my hours’ debugging today.