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.

[woutdejong]

Hi Christoph and Bernd,

Question on the timestamps of PObs Activities (execution) and timestamps recorded in the log of the application itself (in our case FS Claims Management).

We noticed in our sandbox system that theses timestamps are not equal, the timestamps in the (change) logs of the application are 1-2 seconds earlier than those in the PObs (in db tables).

This concerns us a bit in general, even though the business impact for this particular case is low.

Is this normal behavior? Can the timestamps be aligned, or is it very much BOR Event dependent?

Cheers, Wout

[JChristophNolte]

Hi Wout,

right. POB is using the time stamp of the BOR event that is used to bring the change document information to POB from the change document creation exit. It should really be using the information from the time stamp to not add in the processing time in the exit (and maybe some of the change document processing, not sure where that time stamp is created). I had to put a break-point into the event creation routine to see the effect, but obviously this can happen, depending on overall system load, type of change document (little/a lot of processing required) etc.

So: I will fix that. If you need the fix, I'd prefer that you raise a ticket (that may also expedite the process).

In practice it should not have much effect. Times will be off by a couple of seconds. KPIs should not depend on a couple of seconds (and I think more than two or three seconds should be very, very rare), but again: You need to judge.

But anyway, this should be fixed.

Best,

Christoph

[woutdejong]

Christoph, ok, you are referring to the Change Document way of raising events, I guess.

But for standard BOR Events it uses the timestamp as seen in SWEL. So unless the Event itself does contains a Timestamp parameter with the actual time the event happened in the application, one has to use the SWEL timestamp.

Indeed, I agree, a few seconds off usually does not have a big impact.

[JChristophNolte]

Hi Wout,

right (again).

Just to confirm this: The SWEL time stamp will not be considered for change document based BOR events only! Regular events will not be touched here at all! (There is no "local" time stamp that I could use anyway). - I'm using the BOR event POCGENERIC.Event_Raised to move the change document information into the BOR connector. What I will do now technically is only for event POCGENERIC.Event_Raised to use the value from (new) parameter TIMESTAMP rather than the "SWEL timestamp" if available. So POCGENERIC.Event_Raised provides the option to pass the value. And I will use that for the change documents. No existing code will be affected by that either (unless you already fill that parameter, which is unlikely, since it doesn't exist).

Regards,

Christoph