Enqueue Errors - ECC 6.0

[Mike Pokraka]

Hmmm, my first thougt was that this is complete nonsense from OSS.
Then I notice that they talk about a decision task. So, now I think we're
missing a piece of info here - is this a decision or a PA40?

A possible workaround may be to put the PA40's into a subWF. It may only
lock the subworkflow. On the other hand it may also be a case of rejecting
SAP's response - depending on this mystery decision task that is PA40.

Cheers,
Mike


On Mon, October 22, 2007 1:26 pm, Sue Doughty wrote:
> We are in the process of upgrading from 4.7 to ECC 6.0.
>
>
>
> We have a New Hire workflow that has a fork with three branches.  Each
> branch goes to a different department and they all have a work item that
> executes PA40 where they execute a specific action for the employee.
>
>
>
> In 4.7, if two departments happened to hit the same employee at the same
> time, the second department trying to execute the work item would get an
> error in PA40 - Employee is being processed by ######.  They would
> cancel out and come back later.  The work item would remain in their
> in-box.
>
>
>
>
> In ECC 6.0, the workflow gets an ENQUEUE error - Error when loading
> component: Work item 000000638111 locked (action FIND_FLOWITEM) and then
> Work item 000000638111 locked by user E050889 (enqueue error) (action
> FIND_BY_WIID_BY_WFM)
>
>
> The error is referencing the Workflow INSTANCE, not the work item being
> executed.  The work item for the second user is then set to Complete -
> it never takes them to PA40.  They have no way of going back in later
> and executing the action.
>
>
>
> I opened a note with SAP and was told that it is working as designed.
> See SAP's response below:
>
>
>
> Here the lock did not occur during work item execution, but after
> execution during
> the so-called "callback", because the corresponding workflow (father
> work item) was locked. In such a case the work item (user decision)
> is COMPLETED and the workflow is suspended. Especially the so-called
> "synchronous process chain" (advance with dialog) is interrupted
> unless SWWERRE puts the subsequent work item (PA40) into the inbox
> of the user concerned.
>
> According to our development manager this works as designed.
>
>
>
>
>
> I am at a loss as to how to fix this problem.  I don't want to take out
> the fork and have the departments execute the PA40 action one after the
> other.  This would lengthen the time the workflow takes to get someone
> hired and I don't know which department I would do first....they all do
> things in their own time.
>
>
>
> Has anyone else encountered this problem?  Does anyone have any
> suggestions?
>
>
>
> Any help would be greatly appreciated.
>
>
>
> Regards,
>
> Sue T. Doughty
> SAP Workflow Specialist
>
> OLD DOMINION FREIGHT LINE, INC.
>
> 500 Old Dominion Way, Thomasville, NC 27360
>
> Toll Free :(800)432-6335, ext.5189
> Phone :(336)822-5189 Fax :(336)822-5149
> sue.doughty at odfl.com
>
>
>
>
>
> ****************************
> CONFIDENTIALITY NOTICE: The information contained in this message may be
> confidential, privileged, proprietary, or otherwise legally exempt from
> disclosure. If the reader of this message is not the intended recipient,
> or an employee or agent responsible for delivering this message to the
> intended recipient, you are hereby notified that you are not authorized to
> read, print, retain, copy or disseminate this message, any part of it, or
> any attachments. If you have received this message in error, please delete
> this message and any attachments from your system without reading the
> content and notify the sender immediately of the inadvertent transmission.
> Thank you for your cooperation.
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>


-- 
Mike Pokraka
Senior Consultant
Workflow Connections
Mobile: +44(0)7786 910855