Waiting condition step - any better ideas?

Thu Aug 30 05:47:53 EDT 2007

Hi Flavio,

I should have thought about it before replying to you.

The event is published from Infotype 0001 for a reason - it would be much 
harder to try to publish the event from when Infotype 0002 is saved. Not 
sure how familiar you are with HR.

I thought about having a wait step that waits for event PERSDATA.CREATED - 
might be ok to do it that way.

Thanks anyway,

Cristiana
_________________________________
Cristiana d'Agosto
IBM Global Business Services
Mobile:  +61 417 927 224
cristiana.dagosto at au1.ibm.com

Cristiana D'Agosto/Australia/IBM at IBMAU 
Sent by: sap-wug-bounces at mit.edu
30/08/2007 04:31 PM
Please respond to
"SAP Workflow Users' Group" <sap-wug at mit.edu>

To
"SAP Workflow Users' Group" <sap-wug at mit.edu>
cc

Subject
RE: Waiting condition step - any better ideas?

Hi Flavio, 

yes, that's another good idea - thanks! 

Obrigada, 

Cristiana
_________________________________
Cristiana d'Agosto
IBM Global Business Services
Mobile:  +61 417 927 224
cristiana.dagosto at au1.ibm.com 

Flavio Oliveira <oliveiraflavio at hotmail.com> 
Sent by: sap-wug-bounces at mit.edu 
30/08/2007 03:16 AM 

Please respond to
"SAP Workflow Users' Group" <sap-wug at mit.edu>

To
"SAP Workflow Users' Group" <sap-wug at mit.edu> 
cc

Subject
RE: Waiting condition step - any better ideas?

Is it not possible to generate the event only when the 0002 infotype is 
saved?

Regards,
Flávio.

To: sap-wug at mit.edu
Subject: RE: Waiting condition step - any better ideas?
From: cristiana.dagosto at au1.ibm.com
Date: Thu, 30 Aug 2007 01:44:36 +1000

Thanks Sue, 

yes, it is possible to change the order of the Infotypes in the system, 
however the client has defined that IT0001 comes first... 

In theory you are right - if  I use the event queue there is a good chance 
that the Name would have been saved, but we never know how fast / slow the 
users are when they are entering data in the system... 

I guess I will have to keep my waiting step! 

Cheers

Cristiana
_________________________________
Cristiana d'Agosto
IBM Global Business Services
Mobile:  +61 417 927 224
cristiana.dagosto at au1.ibm.com 

"Sue Doughty" <Sue.Doughty at odfl.com> 
Sent by: sap-wug-bounces at mit.edu 30/08/2007 01:25 AM 

Please respond to
"SAP Workflow Users' Group" <sap-wug at mit.edu>

To
"SAP Workflow Users' Group" <sap-wug at mit.edu> 
cc

Subject
RE: Waiting condition step - any better ideas?

Cristiana, 

I walked through a new Hire in our system.  We're currently on 4.7 but 
testing in ECC 6.0.  Infotype 0002 is stored before Infotype 0001 in our 
system, so the Personal data is there when the event is triggered and the 
text in the workflows descriptions contain all the information.  Is there 
a way to specify in SAP the order in which the Infotypes would be stored 
for a New Hire? 

We also send most of our events through the Event Queue (SWEQADM).  The 
job that delivers the events runs every five minutes, so 9 times out of 10 
all of the info types would be stored by the time the event is delivered. 
There would be occasions, though, where the event would hit the queue 
right before the job would execute and all of the data would not be 
stored. 

Sue Doughty 

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf 
Of Cristiana D'Agosto
Sent: Wednesday, August 29, 2007 4:50 AM
To: SAP Workflow Users' Group
Subject: Waiting condition step - any better ideas?

Hi all, 

we are in ECC 6.0 

We have a workflow that gets triggered when a new employee is hired. The 
triggering of the even actually happens when Infotype 0001 is saved. 

The work item that is sent upon hire has the Name of the employee as part 
of its text. The email that is sent to the Distribution List when an 
employee is hired, contains the Name of the employee as part of its text. 

The Infotype 0002 gets saved after Infotype 0001.... 

So, the work item and the email text do not have the Name of the employee 
when the workflow gets triggered. 

To 'solve' the problem, I have created a Wait step in the workflow with a 
Wait for Condition (is Employee Name NE blank?). 

Report RSWWCOND has been set up and everything is working absolutely fine. 

I am only wondering if there is a better way of doing what I did? 

Cheers,

Cristiana
_________________________________
Cristiana d'Agosto
IBM Global Business Services
Mobile:  +61 417 927 224
cristiana.dagosto at au1.ibm.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 

Invite your mail contacts to join your friends list with Windows Live 
Spaces. It's easy! Try it!_______________________________________________
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20070830/4ec52114/attachment.htm