关于crm:SAP-One-Order应用的跟踪工具CRMDTRACESET

41次阅读

共计 1175 个字符,预计需要花费 3 分钟才能阅读完成。

The object event history could record the event of the object involvement in business scenario such as adding an individual object to a business transaction.

The record is done via IOITF (Object integration framework). The detail functionality explanation and necessary could be found in SAP help.

There is a useful user parameter which is not clearly documented in SAP help:

My issue

After I finish all necessary customizing and add one object to service order, the event history assignment block is empty. I expect there is one entry which records the

I set the user parameter as X in SU3 and remove the object from service order and add it once again, it will stop everywhere the method CL_COM_IOITF_DEBUG~BREAKPOINT is called. So we can debug to investigate the handling logic of IOITF framework.

In order to find the root cause for my dedicated issue, I create a dynamic breakpoint on ABAP keyword MESSAGE, since I assume there must be some error message raised which blocks the event creation.

After I click F8 the debugger stops at the code where one error message is raised:

Go upper callstack and I know the framework complains the necessary settype COM_COMMERCIAL is not assigned to object category.

After I add this set type to object category,

After that once I add the object to service order, I could see the expected record in object Event History assignment block.

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

正文完
 0