Workflow Log Strange Behaviour

[Former Member]

Hi,

We have a Travel Management Workflow.

Once the Workflow is approved at all levels(From R/3 using the managers inbox), there are some background tasks that updates Infotypes 2002 and 0015 and changes the trip status to approved, settles the trip etc.

This is as usual done by the WF-BATCH(Workflow Processor). And thereby, when i see in the Workflow Log, it shows correctly that these background steps have been created by the Workflow Processor under the CREATED BY Column.

But, When the trip is approved in MSS using the Manager's Credentials(Eg: Sameer Khan)After the Trip is approved at all levels, the same background tasks are executed without any problem, but under the WF Log in CREATED BY column, the system is showing the name of the last approver ie., Sameer Khan where it should ideally be WF-BATCH (Workflow Processor).

Is anyone aware of this why this behaviour when the trip is approved from MSS.

If the trip is approved from R/3 backend, the Background tasks are shown to be created by Workflo Processor.

Note : This does not impact the completion of Workflow in anyway, But the Workflow Log seems to be confusing and it seems that the last approver will be accountable as it shows He has performed thoses Backgorund Tasks.

Regards,

Mohammed Anwar.

[Former Member]

Thanks Karri and Rick for your help..

-Anwar

[former_member185167]

Hello,

This can happen - that a process is run under the name of the last user. To avoid it, you can just insert a background activity step that does nothing, to switch the context back to WF-BATCH.

regards

Rick Bakker

hanabi technology

[Former Member]

I have added a background step with a dummy method which does nothing.

But Still the same problem...

-Anwar

Edited by: Sameer Anwar on Aug 17, 2011 2:57 PM

[former_member185167]

Hello,

Impossible (almost). Where could that step be getting the name of the person? Is it passed in via the bindings?

It's a background step, right? And you added a dummy background step just before it?

Otherwise, check the code of the method that gets called. I have seen some that actually go and update tables to replace WF-BATCH with a different username.

regards

Rick Bakker

hanabi technology

[Former Member]

Hi Rick,

This works fine when users make approvals from the backend ECC.The Background jobs are shown as being run by WF-BATCH.

BUT, The problem comes only when the user approves from the Portal,.

After the last user approves the travel request, there are background jobs to update ceratin infotypes.When we see the Log . It shows the background jobs under the last user's name instaed of WF-BATCH.

-

Anwar..

[Former Member]

When you look the updated infotypes, who was the last user to change them - WF-BATCH or the approver? I am just trying to find out that is there something wrong with the log or does the system really execute the steps with the approver user. If the case is the latter one, maybe it has something to do with the portal session handling or whatever. I have a feeling that I've seen something similar but I just didn't care since what the log showed didn't have any importance in my case.

Regards,

Karri

[Former Member]

Karri,

I too understand that it does not impact the workflow execution in any way..Even it is of not much importance.

But, in future it may lead to Audit issue i believe..

-Anwar

[former_member185167]

Hello,

"After the last user approves the travel request, there are background jobs to update ceratin infotypes.When we see the Log . It shows the background jobs under the last user's name instaed of WF-BATCH."

Sure, it can do that for the first background job, but not for any after that. Not that I've ever seen.

I can't imagine auditors would care about background jobs being run under usernames - what ends up in the data tables is more important.

regards

Rick Bakker

hanabi technology

[Former Member]

Rick,

Thanks for your response.

Its always good to see your erudite comments.

Yeah the problem is that the username is shown for all the rest of the background jobs after the last user approves it. But, Pls allow me to repeat again that this happens only if the approvals are from portal and if the approvals are from backend ECC, it works fine.

Regarding the auditors comment, I think your point makes sense.But still let me try to raise it up with SAP.Probably this may be a Bug ...

-Anwar..