Want to lock user

Soady, Phil phil.soady at sap.com
Fri Jan 14 03:06:37 EST 2005


Also consider configuring a temporary exception.
There is job (configured thru swu3) that can be scheduled to retry all
temporary errors.

Locks are common and expected temporary error.  
Programmed Loops  generally isnt the best way forward.

regards



Phil Soady
Senior Consultant
Business Technologies
SAP Australia 
M  +61 (0) 412 213 079
E  phil.soady at sap.com


-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Jeffrey A. Rappaport
Sent: Friday,14 January 2005 7:44 AM
To: SAP Workflow Users' Group
Subject: Re: Want to lock user

Eric,

   I just ran a quick test on the Enqueue & Dequeue Methods in the
Bus. Object the WF uses (EMPLOYEET), and they worked when I either
had the Person open in another session or tried to open them for
changing. Try it that way to see if they're working.

   Here's a quesiton for the Gurus, which would be better:

1) Use the WF in question here with the constant checking, adding to
counter and reopening/closing of processes w/WF-BATCH; or

2) Have a loop in one Task that does the checking & adding to counter
until the Person is open for changing; and this way use one open
process, but have it open the whole time until free???

Thanx,

Jeffrey A. Rappaport
Business Workflow, LLC
Voice:(732)355-0123
Fax:  (509)757-4144
Email:Jeff at Business-Workflow.com
Web:  www.Business-Workflow.com


Quoting Tedde Taege <ttaege at nebraska.edu>:

> You might be able to achieve a broader locking through creation of
> your own
> enqueue & dequeue task using business object BUS1065.  I can't
> speak to the
> effectiveness of the enqueue/dequeue on EMPLOYEET but if it is not
> doing
> what you want, then try the functionality on BUS1065.
>
>
------------------------------------------------------------------------
-------------
>
> Tedde Taege
> UNCSN - SAP Development
> 402 472-7544
>
>
>
>              "Caillet, Eric"
>              <Eric.Caillet at log
>              icacmg.com>
>     To
>              Sent by:                  "'SAP Workflow Users' Group
> '"
>              sap-wug-bounces at m         <sap-wug at mit.edu>
>              it.edu
>     cc
>
>
> Subject
>              01/12/2005 09:13          Want to lock user
>              AM
>
>
>              Please respond to
>                "SAP Workflow
>                Users' Group"
>              <sap-wug at mit.edu>
>
>
>
>
>
>
> Hi all,
>
> i'm creating new workflow with specific Business Object Type. This
> workflow
> is used for approval/reject leave request.
>
> When a manager accept a request, i want to lock the matricule
> (PERNR),
> create infotype 2001 and unlock the matricule.
>
> So i wanted to use the SAP standard workflow WS01200003 who allows
> that but
> this workflow don't lock the matricule, i don't see the trace in
> transaction
> SM12.
>
> Do you have a idea for this problem ?
>
> Thanks so much
>
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>

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



More information about the SAP-WUG mailing list