天天看点

SAP One Order应用的跟踪工具CRMD_TRACE_SET

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:

SAP One Order应用的跟踪工具CRMD_TRACE_SET

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

SAP One Order应用的跟踪工具CRMD_TRACE_SET

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.

SAP One Order应用的跟踪工具CRMD_TRACE_SET

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.

SAP One Order应用的跟踪工具CRMD_TRACE_SET

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

SAP One Order应用的跟踪工具CRMD_TRACE_SET

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

SAP One Order应用的跟踪工具CRMD_TRACE_SET

After I add this set type to object category,

SAP One Order应用的跟踪工具CRMD_TRACE_SET

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

SAP One Order应用的跟踪工具CRMD_TRACE_SET