<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:st1 =
"urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3020" name=GENERATOR><!--[if !mso]>
<STYLE>v\:* {
BEHAVIOR: url(#default#VML)
}
o\:* {
BEHAVIOR: url(#default#VML)
}
w\:* {
BEHAVIOR: url(#default#VML)
}
.shape {
BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]--><o:SmartTagType name="PersonName"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><!--[if !mso]>
<STYLE>st1\:* {
BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
font-family: Wingdings;
}
@font-face {
font-family: Tahoma;
}
@font-face {
font-family: Verdana;
}
@font-face {
font-family: Webdings;
}
@font-face {
font-family: Rage Italic;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: blue; TEXT-DECORATION: underline
}
P {
FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.EmailStyle20 {
COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=blue link=blue>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>Let me break this down a little better for I know
others could benefit from this thread.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>First:</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>I have issues with the buffers not refreshing after
code change </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>on and Secondary, BEFORE, and AFTER methods.
Annoying! </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>I tried a few things that were suggested by Mark Pyc
like backing "ALL" the way out of SWO1, PFTC_CHG, etc. </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>Then re-sync buffs, etc. Some times it works, sometimes
not. </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>(Sometimes even shutting down SAP, bringing it back up
and refreshing buffers don't work! )</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>For now, </SPAN></FONT><FONT face=Arial
color=#0000ff><SPAN class=822402513-24082007>best I can do when I need to change
a method is to flip to foreground, set break-point, "see" if latest
</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>version is indeed there. Then remove the breaks, set
back to background and </SPAN></FONT><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>continue. </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>+++++++++++++++++++++++++++</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>Second: (not necessarily an issue I don't
think?)</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>I understand the </SPAN></FONT><FONT face=Arial
color=#0000ff><SPAN class=822402513-24082007>use of Secondary methods after
reviewing you book </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>"Practical Workflow for SAP" (plug on book
intended and looking for ver 2 ) </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>and playing around with them. </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>My use for secondary is limited at best.
Pop-ups or msg </SPAN></FONT><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>displays of some sort, etc.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>Got that! </SPAN></FONT><FONT face=Arial
color=#0000ff><SPAN class=822402513-24082007>And, </SPAN></FONT><FONT face=Arial
color=#0000ff><SPAN class=822402513-24082007>I will review the User Decision
Extra function later. </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>+++++++++++++++++++++++++++</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>Third:</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>I hope you are not saying that the use of BEFORE /
AFTER methods </SPAN></FONT><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>are limited? </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007></SPAN></FONT><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>I have a few methods that I would like to include
in a few task(s) verses </SPAN></FONT><FONT face=Arial
color=#0000ff><SPAN class=822402513-24082007>multiple background tasks.
</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>Some steps in the flow will need the same BEFORE or
AFTER or </SPAN></FONT><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>both. </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>Much easier if I could just move this logic to a before
/ after on task vs making a bunch of BG tasks </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>before and after the main FG task. Very cool! And
finally have a need for them. </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>+++++++++++++++++++++++++++</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>Forth: (And big one!)</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>How do I get the Exceptions from any BEFORE / AFTER
methods to prorogate back </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>to the main Task's method so </SPAN></FONT><FONT
face=Arial color=#0000ff><SPAN class=822402513-24082007>I can use this in the
Outcomes?</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007></SPAN></FONT><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>Oh, and one more thing while I have your attention, in
ECC6 my basis folks </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>are telling me that WF-BATCH will now be the user for
deadline monitoring. </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>We have DDIC as the user of these batch progs in prod
on 4.6c. </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>For some reason, which I am still trying to ascertain
from BASIS, these user types </SPAN></FONT><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>changed. </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>WF-BATCH is now SYSTEM (not communication type) and
</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>DDIC is now a (Dialog type) verse SYSTEM.
</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>I read your posts a few years ago stating that WF-BATCH
_should_ be type COMMUNICATIONS type </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>and to use DDIC (SYSTEM) for these deadline batch
programs. </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>True? See any real issues with our BASIS
changes?</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007>Rick</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff><SPAN
class=822402513-24082007></SPAN></FONT> </DIV><FONT face=Arial
color=#0000ff></FONT><FONT face=Arial color=#0000ff></FONT><FONT face=Arial
color=#0000ff></FONT><FONT face=Arial color=#0000ff></FONT><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of </B>Dart,
Jocelyn<BR><B>Sent:</B> Wednesday, August 22, 2007 8:55 PM<BR><B>To:</B> SAP
Workflow Users' Group<BR><B>Subject:</B> RE: Task with AFTER method
question<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=460255201-23082007>Hey Rick</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=460255201-23082007></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=460255201-23082007>The intent of secondary methods is to do non-important
stuff like display things. </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=460255201-23082007>If you are using it for updates you might want to think
again. </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=460255201-23082007></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=460255201-23082007>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</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=460255201-23082007>rather than through an object method.
</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=460255201-23082007>You still need to make sure the workflow is able to
respond to any changes made by the secondary app as needed. </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=460255201-23082007>However it's quite a handy approach for e.g. User
Decision + Extra function</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV><!-- Converted from text/rtf format -->
<P><SPAN lang=en-us><FONT face=Arial size=1>Regards,</FONT></SPAN> <BR><SPAN
lang=en-us><B><FONT face=Arial color=#000080 size=1>Jocelyn
Dart</FONT></B></SPAN> <BR><SPAN lang=en-us><FONT color=#808080
size=1><FONT face=Arial><SPAN class=822402513-24082007><FONT color=#0000ff
size=3> </FONT></SPAN>Senior Consultant</FONT></FONT></SPAN>
<BR><SPAN lang=en-us><B><FONT face=Arial color=#808080 size=1>SAP Australia Pty
Ltd.</FONT></B></SPAN> <BR><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>Level 1/168 Walker St.</FONT></SPAN> <BR><SPAN lang=en-us><FONT
face=Arial color=#808080 size=1>North Sydney </FONT></SPAN><BR><SPAN
lang=en-us><FONT face=Arial color=#808080 size=1>NSW, 2060</FONT></SPAN>
<BR><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>Australia</FONT></SPAN> <BR><SPAN lang=en-us><FONT face=Arial
color=#808080 size=1>T +61 412 390 267</FONT></SPAN> <BR><SPAN
lang=en-us><FONT face=Arial color=#808080 size=1>M + 61 412 390
267</FONT></SPAN> <BR><SPAN lang=en-us><FONT face=Arial color=#808080
size=1>E jocelyn.dart@sap.com</FONT></SPAN> <BR><SPAN
lang=en-us><FONT face=Arial color=#808080 size=1><A
href="http://www.sap.com/">http://www.sap.com</A></FONT></SPAN> </P>
<P><SPAN lang=en-au><FONT face="Times New Roman" color=#ff0000 size=1>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. </FONT></SPAN></P>
<P><SPAN lang=en-au><FONT face="Times New Roman" color=#ff0000 size=1>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.</FONT></SPAN></P>
<P><SPAN lang=en-au><FONT face="Times New Roman" color=#ff0000 size=1>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. </FONT></SPAN></P>
<DIV><FONT face=Arial color=#0000ff></FONT> </DIV><FONT color=#ff0000
size=1></FONT><FONT color=#ff0000 size=1></FONT><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of </B>Sample,
Rick<BR><B>Sent:</B> Saturday, 18 August 2007 12:04 AM<BR><B>To:</B> SAP
Workflow Users' Group<BR><B>Subject:</B> Task with AFTER method
question<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><SPAN class=017283513-17082007><FONT face=Arial color=#0000ff>I have a task
with a bor-method as a secondary method. </FONT></SPAN></DIV>
<DIV><SPAN class=017283513-17082007><FONT face=Arial color=#0000ff>After MUCH
fuss with the buffers I almost got what I want. </FONT></SPAN></DIV>
<DIV><SPAN class=017283513-17082007><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV><SPAN class=017283513-17082007><FONT face=Arial color=#0000ff>In a the task
when you use an object-method that has Exceptions </FONT></SPAN></DIV>
<DIV><SPAN class=017283513-17082007><FONT face=Arial color=#0000ff>you can see
these exceptions in the Outcomes and take </FONT></SPAN></DIV>
<DIV><SPAN class=017283513-17082007><FONT face=Arial color=#0000ff>action. i.e.
not a before / after method.</FONT></SPAN></DIV>
<DIV><SPAN class=017283513-17082007><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV><SPAN class=017283513-17082007><FONT face=Arial color=#0000ff>I removed the
method from the main task, put in a void BG method,
(testing)</FONT></SPAN></DIV>
<DIV><SPAN class=017283513-17082007><FONT face=Arial color=#0000ff>then moved
that same method to a secondary method. </FONT></SPAN></DIV>
<DIV><SPAN class=017283513-17082007><FONT face=Arial color=#0000ff>I do not get
these exceptions added to the Outcomes when </FONT></SPAN></DIV>
<DIV><SPAN class=017283513-17082007><FONT face=Arial color=#0000ff>in a
secondary method.</FONT></SPAN><SPAN class=017283513-17082007><FONT face=Arial
color=#0000ff> </FONT></SPAN></DIV>
<DIV><SPAN class=017283513-17082007><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV><SPAN class=017283513-17082007><FONT face=Arial color=#0000ff>Any ideas how
to handle exceptions from a secondary method?</FONT></SPAN></DIV>
<DIV><SPAN class=017283513-17082007><FONT face=Arial
color=#0000ff></FONT></SPAN> </DIV>
<DIV><SPAN class=017283513-17082007><FONT face=Arial color=#0000ff><!-- Converted from text/plain format -->
<P><FONT size=2>Rick Sample<BR>SAP Business Workflow Developer<BR>Graybar,
Inc.<BR></FONT></P></FONT></SPAN></DIV></BODY></HTML>