您好, 欢迎来到 !    登录 | 注册 | | 设为首页 | 收藏本站

SAP CRM Service order 的distribution lock和status profile

2022/1/2 13:00:24 架构 字数 7762 阅读 616 来源 https://www.iteye.com/blogs/category/architecture

SAP CRM Service order 的distribution lock和status profile I would like to share an investigation done today regarding distribution lock in Service Order. My colleague observed that if there is no status profile maintained for Service Order transaction type ... SAPSAP云平台SAP Cloud PlatformSAP成都研究院CRM? JerryWang_SAP

I would like to share an investigation done today regarding distribution lock in Service Order.

My colleague observed that if there is no status profile maintained for Service Order transaction type,

 

 

once the service order is created and saved, you can not edit it any more. When Edit button is clicked, the error message “Document/transaction is being distributed; changes are not possible” is displayed:

 

 

However, when a status profile is maintained to the transaction type, the edit works. Why?

In below chapter I can transaction type without status profile as scenario A and type with status profile as scenario B.

(1) figure out why error message is raised in scenario A.

The message is raised in line 216 due to flag lv_status_transferring is set. However in scenario B, lv_status_transferring is initial.

 

 

(2) population logic of flag lv_status_transferring It is filled by this function module:

 

 

This function module reads order status and check whether system status I1054 “To be distributed” exists. If found, lv_status_transferring is set to true. And I debug to find the status for scenario A:

 

 

System for scenario B:

 

 

So the next task: figure out why I1054 is created for scenario A but not for scenario B

(3) status transition debug I notice that in both scenario, the function module below will be called to set business transaction “TOR3” to order.

 

 

“TOR3” means “To be distributed”.

 

 

For scenario A, this function module is executed successfully, however in scenario B, it fails with sy-subrc = 4.

 

 

Then I debug into this function module and found it is the status profile which is assigned to transaction type prevent this status transition. The transition will NOT be performed due to the error message raised in line 448. See line 435, WHEN 3.

 

 

Here the program found that for status profile ZCRMACT, business transaction type TOR3, there is an user status set as flag 3 – Forbidden.

 

 

Where does it come from? Go to status profile, double click “OPEN”,

 

 

Here it is:

 

 

It is this user status which prevents the status transition of order in scenario B to “Transferring”, thus edit still works for scenario B.

要获取更多Jerry的原创文章,请关注公众号"汪子熙":


如果您也喜欢它,动动您的小指点个赞吧

除非注明,文章均由 laddyq.com 整理发布,欢迎转载。

转载请注明:
链接:http://laddyq.com
来源:laddyq.com
著作权归作者所有。商业转载请联系作者获得授权,非商业转载请注明出处。


联系我
置顶