Process Observer Discussion

[JChristophNolte]

This thread is dedicated to questions and discussions around the Process Observer component that is part of Business Suite.

Process Observer is used in different scenarios, including and prominently with Operational Process Intelligence.

For details on what Process observer is see here.

[qurm]

Hi all,

I have recently started running a POB process in production after some months of prototyping.  While the core process works correctly, in monitoring the activity I am seeing a large number of Unassigned Tasks in POC_TASK and would like some feedback on what is reasonable.

The process is based on Service Noti as a base object, BOR BUS2080, with Type ID 118 and a few events/tasks.  Subsequent events/tasks are configured on Type 468, Maintenance Order, and Type 114, Sales Order.  We have many types of Service Noti, lets say A, B, C, of which only A are required for this process.

In the POB Process Definition I have configured a BRFplus rule on the Binding of Noti Create Activity to the Task Create Noti (21,118).  The purpose of this is to allow only Noti type A to trigger the Process Start, by setting  the value POC_BRF_ACT_BIND_DETERMINED to ‘X’ (true).

I am seeing various classes of Unassigned Tasks in POC_TASK:

1. Tasks that are in the Process definition, but where the Process Start event for that instance was in the past, so the task/event cannot be correlated to a Start task/event.  This is expected behaviour as the process lifecycle is about 60 days, and after that time most new task/event will be correlated.
2. Tasks that are in the Process definition, but should be excluded by the BRFPlus rule on the Start Task Create Noti (21,118).  For example Noti type B should not trigger the Start (as POC_BRF_ACT_BIND_DETERMINED is set to false)..  Should these tasks still appear in POC_TASK?  I expected these would be ignored by POB.
3. Tasks for objects like Maintenance Order, Sales Order.  These objects are in the table POC_C_BOR_EVT, but I do not expect that tasks will be created unless they are related to a process instance.  Should these tasks still appear in POC_TASK as Unassigned?  I expected these would be ignored by POB.
4. Tasks for a Maintenance Noti BUS2038, which is similar to the Service Noti BUS2080 – this is in the table POC_C_BOR_EVT, but not Active, yet still raises events/tasks.

Any feedback on the above 4 classes of Unassigned Tasks will be helpful.  I assume that POC_MASS_DELETE should be scheduled regularly to delete these unwanted tasks.

Note that the Process logging is set to "Standard Logging"

Thanks,  Andy

[bernd_schmitt]

Hi Andy,

we have a BAdI implementation available that suppresses the logging of all the unassigned tasks of any kind. You find it described at the bottom of this article: or in note 2018078. By activating the BAdI implementation you can suppress the orphaned tasks in your productive systems.

Logging the orphaned tasks makes mainly for checking the logging during the design and testing phase.

Regards,

Bernd

P.S. for our internal statistics and references it would be nice, if you could send  me some info about your use case to my email. Thank you!