Task with AFTER method question

[Sample, Rick]

Let me break this down a little better for I know others could benefit
from this thread.
 
First:
I have issues with the buffers not refreshing after code change 
on and Secondary, BEFORE, and AFTER methods. Annoying! 
 
I tried a few things that were suggested by Mark Pyc like backing "ALL"
the way out of SWO1, PFTC_CHG, etc. 
Then re-sync buffs, etc. Some times it works, sometimes not. 
(Sometimes even shutting down SAP, bringing it back up and refreshing
buffers don't work! )
For now, best I can do when I need to change a method is to flip to
foreground, set  break-point, "see" if latest 
version is indeed there. Then remove the breaks, set back to background
and continue. 
+++++++++++++++++++++++++++
 
Second:  (not necessarily an issue I don't think?)
I understand the use of Secondary methods after reviewing you book 
"Practical Workflow for SAP" (plug on book intended and looking for ver
2 ) 
and playing around with them. 
My use for secondary is limited at best. Pop-ups or msg displays of some
sort, etc.
Got that! And, I will review the User Decision Extra function later. 
+++++++++++++++++++++++++++
 
Third:
I hope you are not saying that the use of BEFORE / AFTER methods are
limited? 
I have a few methods that I would like to include in a few task(s)
verses multiple background tasks. 
Some steps in the flow will need the same BEFORE or AFTER or both. 
Much easier if I could just move this logic to a before / after on task
vs making a bunch of BG tasks 
before and after the main FG task. Very cool! And finally have a need
for them. 
+++++++++++++++++++++++++++
 
Forth: (And big one!)
How do I get the Exceptions from any BEFORE / AFTER methods to prorogate
back 
to the main Task's method so I can use this in the Outcomes?
 
Oh, and one more thing while I have your attention, in ECC6 my basis
folks 
are telling me that WF-BATCH will now be the user for deadline
monitoring. 
We have DDIC as the user of these batch progs in prod on 4.6c. 
For some reason, which I am still trying to ascertain from BASIS, these
user types changed. 
 
WF-BATCH is now SYSTEM (not communication type) and 
DDIC is now a  (Dialog type) verse SYSTEM. 
 
I read your posts a few years ago stating that WF-BATCH _should_ be type
COMMUNICATIONS type 
and to use DDIC (SYSTEM) for these deadline batch programs. 
True? See any real issues with our BASIS changes?
 
Rick
 
 
 
 
 


________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Dart, Jocelyn
Sent: Wednesday, August 22, 2007 8:55 PM
To: SAP Workflow Users' Group
Subject: RE: Task with AFTER method question


Hey Rick
 
The intent of secondary methods is to do non-important stuff like
display things.  
If you are using it for updates you might want to think again. 
 
An alternative if you are using UWL is just to create an extra action
(button) for your item type that calls your secondary app directly
rather than through an object method. 
You still need to make sure the workflow is able to respond to any
changes made by the secondary app as needed. 
However it's quite a handy approach for e.g. User Decision + Extra
function
 

Regards, 
Jocelyn Dart 
  Senior Consultant 
SAP Australia Pty Ltd. 
Level 1/168 Walker St. 
North Sydney 
NSW, 2060 
Australia 
T   +61 412 390 267 
M   + 61 412 390 267 
E   jocelyn.dart at sap.com 
http://www.sap.com <http://www.sap.com/>  

The information contained in or attached to this electronic transmission
is confidential and may be legally privileged. It is intended only for
the person or entity to which it is addressed. If you are not the
intended recipient, you are hereby notified that any distribution,
copying, review, retransmission, dissemination or other use of this
electronic transmission or the information contained in it is strictly
prohibited. If you have received this electronic transmission in error,
please immediately contact the sender to arrange for the return of the
original documents. 

Electronic transmission cannot be guaranteed to be secure and
accordingly, the sender does not accept liability for any such data
corruption, interception, unauthorized amendment, viruses, delays or the
consequences thereof.

Any views expressed in this electronic transmission are those of the
individual sender, except where the message states otherwise and the
sender is authorized to state them to be the views of SAP AG or any of
its subsidiaries. SAP AG, its subsidiaries, and their directors,
officers and employees make no representation nor accept any liability
for the accuracy or completeness of the views or information contained
herein. Please be aware that the furnishing of any pricing information/
business proposal herein is indicative only, is subject to change and
shall not be construed as an offer or as constituting a binding
agreement on the part of SAP AG or any of its subsidiaries to enter into
any relationship, unless otherwise expressly stated. 

 


________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Sample, Rick
Sent: Saturday, 18 August 2007 12:04 AM
To: SAP Workflow Users' Group
Subject: Task with AFTER method question


I have a task with a bor-method as a secondary method. 
After MUCH fuss with the buffers I almost got what I want. 
 
In a the task when you use an object-method that has Exceptions 
you can see these exceptions in the Outcomes and take 
action. i.e. not a before / after method.
 
I removed the method from the main task, put in a void BG method,
(testing)
then moved that same method to a secondary method. 
I do not get these exceptions added to the Outcomes when 
in a secondary method. 
 
Any ideas how to handle exceptions from a secondary method?
 
Rick Sample
SAP Business Workflow Developer
Graybar, Inc.


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