wait up to 48 hrs

Tue Aug 14 06:03:43 EDT 2007

Hi Stanley, 

Not ideal use of the wait statement.

A running program is swapped out, for X seconds then swapped back in.

If anything happens to the running program, or Work process, or system,
then this step will be left orphaned.

Eg if system is brought down, then this wait never finished, therefore
the current wf step needs restart.

I suggest you consider temporary error and retries.

Or Consider a loop in the workflow to check to see if the payroll area
is locked with a delayed start time. WI creation + x hrs.

With of course some exit condition to avoid permanent loops.

I can not recommend the ABAP wait statement for all but the briefest
periods inside Workflow.

Even then error handling after the wait period is still required. 

Phil Soady 
Solution Architect 
Netweaver Consulting 
SAP Australia 
M  +61 412 213 079 
F  +61 2 9957 7263 
mailto:phil.soady at sap.com 

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Stanley Nemavhola - BCX - CDE
Sent: Tuesday, 14 August 2007 6:02 PM
To: sap-wug at mit.edu
Subject: wait up to 48 hrs

Hi,

I have got a wait step which wait for 48 hrs when the payroll area is
locked, some of the workflows do not continue after 48hrs, they remain
on wait.

Is there an explanation for this kind of error?  Please check below.

------------------------------------------------------------------------
------------------------------------------------------------------------
-----------------------------------------------------------------

Kind Regards,

Stanley Nemavhola
SAP Consultant
CDE
As service provider for: Sasol

  Office:

  +27 (0)11 266 5022

  Mobile:

  +27 (0)82 322 2848

  Fax:

  +27 (0)11 266 5107

  Email:

  Stanley.Nemavhola at bcx.co.za <mailto:Stanley.Nemavhola at bcx.co.za> 

  Web Site: 

  www.bcx.co.za <http://www.bcx.co.za> 

NOTICES:
1. This message and any attachments are confidential and intended solely
for the addressee. If you have received this message in error, please
notify the sender immediately, contact details as above. Any
unauthorised use, alteration or dissemination is prohibited.
2. Although the sender has sent this message using the Sasol email
system and a Sasol email address, he/she is, at all times, a Business
Connexion employee, acting on behalf of Business Connexion (Pty) Ltd. 
3. Business Connexion (Pty) Ltd accepts no liability whatsoever for any
loss whether it be direct, indirect or consequential, arising from
information made available and actions resulting there from.
4. Please note that Business Connexion only binds itself by way of
signed agreements. 'Signed' refers to a hand-written signature,
excluding any signature appended by 'electronic communication' as
defined in the Electronic Communications and Transactions Act, no. 25 of
2002.
5. Directors: L.I. Mophatlane, P.A. Watt, L.B. Mophatlane, A.C. Farthing
(British), M.W. Schoeman.
6. Business Connexion (Pty) Ltd Company Registration Number:
1993/003683/07

Important Notice:

This e-mail and its contents are subject to the Business Connexion (Pty)
Ltd.

E-mail legal notice available at:

http://www.bcx.co.za/disclaimer.htm

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20070814/d3061b9f/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 8799 bytes
Desc: image001.jpg
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20070814/d3061b9f/attachment.jpg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 71810 bytes
Desc: image002.jpg
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20070814/d3061b9f/attachment-0001.jpg