Skip to Content
author's profile photo Former Member
Former Member

Workflow Log Strange Behaviour

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.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Posted on Jul 12, 2011 at 09:05 AM

    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

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Rick Bakker

      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..

  • author's profile photo Former Member
    Former Member
    Posted on Aug 21, 2011 at 06:50 AM

    Thanks Karri and Rick for your help..

    -Anwar

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.