Enqueue Errors - ECC 6.0

Tue Oct 23 07:49:57 EDT 2007

Hello all,

I have a requirwement in DMS with workflow ...

Where we developed the application in development system usng DRAW object type CHANGED method.
Transported the same to Quality system ,
Now the required fucntionality is not getting triggered in Quality Sytem .

Please provide me the your valuable suggestions on the same .

Regards,
Shishupal

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Sue Doughty
Sent: Tuesday, 23. October 2007 5:07 PM
To: SAP Workflow Users' Group
Subject: RE: Enqueue Errors - ECC 6.0

Hi Mike,

Thanks for your response.

It is a standard call to PA40.

Hi Mike,

Thank you for your response.

It is a standard call to PA40.

I agree...a task should NOT lock the TOP level workflow.

I did what you said and got the PA40 up and then tried to execute
another branch doing something different.  It still locks the workflow
at the top level.

I will try moving the decisions out into the sub workflow and see if
that changes things.

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
-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Mike Pokraka
Sent: Tuesday, October 23, 2007 4:46 AM
To: SAP Workflow Users' Group
Subject: RE: Enqueue Errors - ECC 6.0

Hi Sue,

OK, so that changes the picture a little. Regarding subWF, you should
try
putting the entire user dialog chain into the subwf - i.e. the decision
and the PA40.

I've had similar probs where a lock would cause a similar error and the
error monitoring job would pick it up - as per the OSS response. However
I
am also not convinced this is right. Is this s standard "Call
transaction
PA40" type of method or does the code do something strange?

A task should NOT lock the top level workflow. That defeats the whole
point of parallel execution. Yes there can problems if you and up with
two
branches joining at the same time and racing for the next step but a WF
should definitively be able to execute two steps in parallel otherwise
we
can all go home. Here's another test: when one user locks PA40, try to
execute something else in the other branch after the decision - or a
PA40
on a different employee - in other words something that works. If that
also fails then I say it's rubbish design that needs to be fixed.

Cheers,
Mike

On Mon, October 22, 2007 9:10 pm, Sue Doughty wrote:
> Hi Mike,
>
> I changed the PA40s to subworkflows.
>
> I executed the workflow again and tried to execute the decision tasks
> (which call the PA40 subworkflow).
>
> It is still giving me an enqueue error on the Decision step at the
> INSTANCE level if more than one fork is executed at a time.  It seems
> like it is telling me that only one path of the fork can be executed
at
> a time.  If two people try to execute two different paths, it will get
a
> locking error.  It is two difference paths of a fork and two separate
> decision steps.
>
> This can't be the way it is supposed to work!
>
> 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
>
> -----Original Message-----
> From: Sue Doughty
> Sent: Monday, October 22, 2007 11:28 AM
> To: 'SAP Workflow Users' Group'
> Subject: RE: Enqueue Errors - ECC 6.0
>
> Hi Mike,
>
> Thanks for responding.
>
> There is a decision task.  They can click to print forms or if they
want
> to do the action in PA40, they click "Execute Payroll (or whatever)
> followup action".  The task that gets executed is a call to PA40.
>
>
> 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
>
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
Behalf
> Of Mike Pokraka
> Sent: Monday, October 22, 2007 9:39 AM
> To: SAP Workflow Users' Group
> Subject: Re: Enqueue Errors - ECC 6.0
>
> 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
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
> ****************************
> 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

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

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