分配给531和261运动类型的工作流程吗?
Bapi_goodsmvt_create在并行模式下导致“材料XXX的植物数据已锁定”错误。
正如我在上面的问题中所写的那样 - 我目前通过使用并行性将一项作业分为多个工作来改进程序,这正在减少整个工作时间。
问题
当我进行移动261张贴时,它的工作时间很高,这将减少了一半的工作时间。
REAL 问题是,它在移动531张贴方面不起作用,这会导致标准锁误差 - 材料 a 用户被用户材料锁定,对我来说似乎很奇怪(我认为正确的物质A被用户用户名锁定)。
问题
每当我发布这些文档时,是否有531个发布的工作流程?例如,更改Mardh,MCHB,AUFM表,可以调查,以便我可以找到锁定错误的根本原因。
当前,每当我尝试并行作业时 - 我必须多次进行多次处理(幸运的是,这只是锁定错误,所以我重试了此过程,它不会影响数据的持续性),这是因为我是因为我必须一直监视此CBO程序。
Follow-up question of BAPI_GOODSMVT_CREATE in parallel mode causes "plant data of the material XXX is locked" error.
As I wrote in above question - I'm currently improving program by using parallelism to split one job to multiple job, which are reducing whole work time.
Problem
It works great when I do Movement 261 posting, which are reduced working time by half.
The real problem is, It's not working for Movement 531 posting, which cause standard lock error - Material A is locked by user Material A, which are seems to be odd to me(I think correct one would be Material A is locked by user USERNAME).
Question
Is there a workflow of 531 posting, whenever i post these documents? like, changing MARDH, MCHB, AUFM tables, which can be investigated so i can find root cause of locked error.
Currently, whenever I try parallel job - I have to do multiple times because locked entry does not processed(fortunately it's just locked error, so how many times i retry this process, it doesn't affect data consistancy), which are annyoing because i have to monitor this CBO program whole time.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
您可以使用tcode
swels
跟踪工作流程事件:步骤1。执行事务swels
步骤2。通过BAPI或Migo
运行531个移动
步骤3。执行事务swel
在Swel Report中,您将看到所有触发的工作流程和事件
update :不要忘记检查跟踪
i.sstatic.net/5gcys.png“ rel =“ nofollow noreferrer”>
You can use tcode
SWELS
to trace workflow events:Step 1. Execute transaction SWELS
Step 2. Run posting of 531 movement via BAPI or in MIGO
Step 3. Execute transaction SWEL
in SWEL report you will see all workflow processes and events that were triggered
UPDATE: do not forget to check the restrictions for trace
it may be set a filter by object type that prevents from showing all the events