<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40"><head><meta name=Generator content="Microsoft Word 12 (filtered medium)"><!--[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]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-AU link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi Sanjay, <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>You need to enter the absolute URL for running your webdynpro <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Quickest way is to go to transaction SE80, bring up a webdynpro app, and test it from there. That should bring up a browser session given you the complete URL to that webdynpro. So what you want in WD_HOST is most of that URL … i.e. everything up to and including …./webdynpro/<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Regards,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Jocelyn<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] <b>On Behalf Of </b>Sanjay9 P<br><b>Sent:</b> Thursday, 17 March 2011 12:19 AM<br><b>To:</b> SAP Workflow Users' Group<br><b>Cc:</b> SAP Workflow Users' Group; sap-wug-bounces@mit.edu<br><b>Subject:</b> Re: Launching WDA items from Extended Notifications<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Hi,</span> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>I have tried to launch WD application from extended notification but its not working.</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>I have maintained only SWFVISU.</span> <br><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Can anybody suggest what needs to be maintain in </span><tt><span style='font-size:10.0pt'>WD_HOST</span></tt><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> ( </span><tt><span style='font-size:10.0pt'>SWNCONFIG</span></tt><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> ) ?</span> <br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>Sanjay Pal<br>Asst System Engineer<br>Tata Consultancy Services<br>Mailto: sanjay9.p@tcs.com<br>Website: </span><a href="http://www.tcs.com/"><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>http://www.tcs.com</span></a><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'><br>____________________________________________<br>Experience certainty. IT Services<br> Business Solutions<br> Outsourcing<br>____________________________________________</span> <br><br><o:p></o:p></p><table class=MsoNormalTable border=0 cellpadding=0 width="100%" style='width:100.0%'><tr><td valign=top style='padding:.75pt .75pt .75pt .75pt'><p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F'>From:</span> <o:p></o:p></p></td><td valign=top style='padding:.75pt .75pt .75pt .75pt'><p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Ramki Maley <rmaley@erpworkflow.com></span> <o:p></o:p></p></td></tr><tr><td valign=top style='padding:.75pt .75pt .75pt .75pt'><p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F'>To:</span> <o:p></o:p></p></td><td valign=top style='padding:.75pt .75pt .75pt .75pt'><p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>"SAP Workflow Users' Group" <sap-wug@mit.edu></span> <o:p></o:p></p></td></tr><tr><td valign=top style='padding:.75pt .75pt .75pt .75pt'><p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F'>Date:</span> <o:p></o:p></p></td><td valign=top style='padding:.75pt .75pt .75pt .75pt'><p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>03/10/2011 07:27 PM</span> <o:p></o:p></p></td></tr><tr><td valign=top style='padding:.75pt .75pt .75pt .75pt'><p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F'>Subject:</span> <o:p></o:p></p></td><td valign=top style='padding:.75pt .75pt .75pt .75pt'><p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>Re: Launching WDA items from Extended Notifications</span> <o:p></o:p></p></td></tr><tr><td valign=top style='padding:.75pt .75pt .75pt .75pt'><p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif";color:#5F5F5F'>Sent by:</span> <o:p></o:p></p></td><td valign=top style='padding:.75pt .75pt .75pt .75pt'><p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif"'>sap-wug-bounces@mit.edu</span><o:p></o:p></p></td></tr></table><p class=MsoNormal><o:p> </o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="100%" noshade style='color:#A0A0A0' align=center></div><p class=MsoNormal style='margin-bottom:12.0pt'><br><br><br><tt><span style='font-size:10.0pt'>Thanks Jocelyn. I wasn't sure if SWFVISU would still work in a non UWL </span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>environment.</tt><br><br><tt>Regards,</tt><br><tt>Ramki.</tt><br><br><tt>On 3/9/11 11:12 PM, Dart, Jocelyn wrote:</tt><br><tt>> Ramki,</tt><br><tt>> If you enter the WebDynpro application for the task in transaction SWFVISU Task Visualization and in transaction SWNCONFIG General Settings set up the field WD_HOST, then Extended Notifications will generate the work item execution links for you, provided you have selected the work item execution link in your subscription parameters of SWNCONFIG.</tt><br><tt>></tt><br><tt>> This works even if you aren't using the UWL and doesn't need any coding.</tt><br><tt>></tt><br><tt>> Regards,</tt><br><tt>> Jocelyn</tt><br><tt>></tt><br><tt>></tt><br><tt>> -----Original Message-----</tt><br><tt>> From: sap-wug-bounces@mit.edu [</tt></span><a href="mailto:sap-wug-bounces@mit.edu"><tt><span style='font-size:10.0pt'>mailto:sap-wug-bounces@mit.edu</span></tt></a><tt><span style='font-size:10.0pt'>] On Behalf Of Ramki Maley</span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> Sent: Saturday, February 26, 2011 3:47 AM</tt><br><tt>> To: SAP Workflow Users' Group</tt><br><tt>> Subject: Re: Launching WDA items from Extended Notifications</tt><br><tt>></tt><br><tt>> Mike, apologies for the drifting and thanks again for separating the</tt><br><tt>> issue and your valuable suggestions.</tt><br><tt>></tt><br><tt>> Best Regards,</tt><br><tt>> Ramki.</tt><br><tt>></tt><br><tt>> On 2/25/11 11:40 AM, Mike Pokraka wrote:</tt><br><tt>>> Hi Ramki,</tt><br><tt>>></tt><br><tt>>> We've drifted way off topic into specific problems so I changed the</tt><br><tt>>> title...</tt><br><tt>>></tt><br><tt>>> Had a quick look, can use SAP_WAPI_GET_METHODS to derive whether it's a</tt><br><tt>>> webby item and SAP_WAPI_LAUNCH_URL_GET is self-explanatory.</tt><br><tt>>></tt><br><tt>>> That's the easy bit, the extended notification part can get a tricky.</tt><br><tt>>> Haven't worked with it for a while but from memory I think you may need to</tt><br><tt>>> do an enhancement. CL_SWN_NOTIF_WORKFLOW is a good starting point.</tt><br><tt>>></tt><br><tt>>> Cheers,</tt><br><tt>>> Mike</tt><br><tt>>></tt><br><tt>>> On Fri, February 25, 2011 4:12 pm, Ramki Maley wrote:</tt><br><tt>>>> Mike, great ideas. I will look into them. I am under severe time</tt><br><tt>>>> constraints and was thinking in the lines of your first suggestion.</tt><br><tt>>>></tt><br><tt>>>> Many Thanks,</tt><br><tt>>>> Ramki.</tt><br><tt>>>></tt><br><tt>>>> On 2/25/11 11:06 AM, Mike Pokraka wrote:</tt><br><tt>>>>> Hi Ramki,</tt><br><tt>>>>></tt><br><tt>>>>> The main issue is that your're launching a web app which drops down into</tt><br><tt>>>>> GUI mode to launch a new web app. Very roundabout and spawns an extra</tt><br><tt>>>>> unnecessary session.</tt><br><tt>>>>></tt><br><tt>>>>> There are a few ways to work around this, mostly involving customizing</tt><br><tt>>>>> Extended Notifications to some degree. You can look at the work item and</tt><br><tt>>>>> if it's web-based then pull out the URL the work item is trying to</tt><br><tt>>>>> launch</tt><br><tt>>>>> (there's a WAPI for it), and put that into the mail instead of the link</tt><br><tt>>>>> to</tt><br><tt>>>>> SWNWIEX.</tt><br><tt>>>>></tt><br><tt>>>>> Another solution I've built is to redirect everything to a filter app</tt><br><tt>>>>> which looks at where it was launched from, what the work item does and</tt><br><tt>>>>> then decides what to do. Useful if you have multiple entry points and</tt><br><tt>>>>> execution mode. (e.g. if single approval in user's inbox, launch yes/no</tt><br><tt>>>>> window, if multiple approvals in inbox then launch an overview app).</tt><br><tt>>>>></tt><br><tt>>>>> Cheers,</tt><br><tt>>>>> Mike</tt><br><tt>>>>></tt><br><tt>>>>> On Fri, February 25, 2011 3:13 pm, Ramki Maley wrote:</tt><br><tt>>>>>> Mikko, thanks for a great reply. I fully agree with you. I too have</tt><br><tt>>>>>> been</tt><br><tt>>>>>> using ABAP-OO to create new objects, new methods for existing BOR etc.</tt><br><tt>>>>>></tt><br><tt>>>>>> I am in a situation where the users want WebDynpro and don't want</tt><br><tt>>>>>> anything to do with SAPGUI. The client does not have EP. We have built</tt><br><tt>>>>>> a</tt><br><tt>>>>>> simple WDA application and used WF_EXTSRV to generate a task for it.</tt><br><tt>>>>>> This works fine when executed from the SBWP. The issue is when an email</tt><br><tt>>>>>> with Execute Workitem link is sent to Outlook using Extended</tt><br><tt>>>>>> Notifictions. Since the link executes Txn. SWNWIEX, the 'Close Window'</tt><br><tt>>>>>> screen is opened first in SAPGUI/browser and then the WDA is launched.</tt><br><tt>>>>>></tt><br><tt>>>>>> Is there any way to launch the WebDynpro from the email other than</tt><br><tt>>>>>> actually putting the URL in the workitem description?</tt><br><tt>>>>>></tt><br><tt>>>>>> Thanks,</tt><br><tt>>>>>> Ramki.</tt><br><tt>>>>>></tt><br><tt>>>>>></tt><br><tt>>>>>></tt><br><tt>>>>>> On 2/25/11 2:24 AM, Mikko Mäki-Rahkola wrote:</tt><br><tt>>>>>>> Hi all,</tt><br><tt>>>>>>></tt><br><tt>>>>>>> interesting to hear other workflowers' experiences on ABAP OO and WDA</tt><br><tt>>>>>>> usage! I hope you (especially Sue, Mike and Ramki) however don't mind</tt><br><tt>>>>>>> me as a late joiner combining the two topics of ABAP OO for WF and WDA</tt><br><tt>>>>>>> for WF when sharing my experiences, since I've been accustomed to</tt><br><tt>>>>>>> using both of them simultaneously and I strongly believe that 1 + 1 =</tt><br><tt>>>>>>> 3 in this case :)</tt><br><tt>>>>>>></tt><br><tt>>>>>>> ABAP OO for WF experiences:</tt><br><tt>>>>>>> We've now been using ABAP OO for WF in ~10-15 projects since 2007 and</tt><br><tt>>>>>>> I can pretty much agree on the use cases and comments already stated.</tt><br><tt>>>>>>> Our rule of thumb is similar to others', we are using ABAP OO for WF</tt><br><tt>>>>>>> in cases where new functionality is required. Such cases have included</tt><br><tt>>>>>>> e.g. request objects in need of object specific functionality (like</tt><br><tt>>>>>>> material requests, where the usage of ISR notification objects is not</tt><br><tt>>>>>>> sufficient), but also completely new objects which SAP doesn't support</tt><br><tt>>>>>>> at all in BOR (e.g. SAP HCM Enterprise Compensation Management). Cases</tt><br><tt>>>>>>> where not to go with ABAP OO and resort to existing BOR objects have</tt><br><tt>>>>>>> included e.g. event handling, simple workflows (like IDoc handling)</tt><br><tt>>>>>>> where the standard objects are sufficient and customer driven cases</tt><br><tt>>>>>>> where the usage of BOR objects have been a must.</tt><br><tt>>>>>>></tt><br><tt>>>>>>> In general, we are using BOR objects nowadays only where it's</tt><br><tt>>>>>>> necessary like event handling or where the ABAP OO</tt><br><tt>>>>>>> replacing/complementing functionality would require too big an effort</tt><br><tt>>>>>>> when compared to a standard BOR object. The main benefits we have</tt><br><tt>>>>>>> perceived of going ABAP OO instead of BOR come from a developer</tt><br><tt>>>>>>> perspective. People using ABAP OO in other development (see my</tt><br><tt>>>>>>> comments below) are quickly accustomed to using the WF class</tt><br><tt>>>>>>> interface, the class editor is familiar to them and there is no need</tt><br><tt>>>>>>> for a separate editor, there are less restrictions (anyone had a</tt><br><tt>>>>>>> requirement for more than one delegation/subclass?) and in general</tt><br><tt>>>>>>> there's a single development environment which can be utilised for</tt><br><tt>>>>>>> other development as well.</tt><br><tt>>>>>>></tt><br><tt>>>>>>> WDA for WF experiences:</tt><br><tt>>>>>>> WDA has been around in our projects since 2007-2008 after customers</tt><br><tt>>>>>>> started upgrading their systems to SAP ERP 6.0 (gladly no more WDJ</tt><br><tt>>>>>>> since then!) and most of the WDA solutions we've done have been</tt><br><tt>>>>>>> integrated to WF in one way or the other. Some have just started off a</tt><br><tt>>>>>>> workflow either through a custom or a standard event, some have been</tt><br><tt>>>>>>> been developed for work item processing (= approval views) and some</tt><br><tt>>>>>>> have been done for work item reporting. Since both WDA and WF work on</tt><br><tt>>>>>>> the ABAP runtime, they work beautifully together. Firing events with</tt><br><tt>>>>>>> ABAP OO for WF, processing work items and reporting on them are as</tt><br><tt>>>>>>> straightforward with WDA as with plain ABAP.</tt><br><tt>>>>>>></tt><br><tt>>>>>>> Currently our nr 1 choice for a new customer specific web user</tt><br><tt>>>>>>> interface sitting on top of any SAP Business Suite (ok CRM and SRM may</tt><br><tt>>>>>>> be different) is WDA as per SAP's Best Built Application guidelines.</tt><br><tt>>>>>>> As Mike P stated before, it has lots of benefits when compared to the</tt><br><tt>>>>>>> other alternatives (WDJ, BSP, VC) available. So our outlook on it is</tt><br><tt>>>>>>> very positive, it works well together with WF implementations and also</tt><br><tt>>>>>>> has UI-wise very powerful features like POWL and FPM delivered with</tt><br><tt>>>>>>> the framework.</tt><br><tt>>>>>>></tt><br><tt>>>>>>> WDA + ABAP OO for WF experiences:</tt><br><tt>>>>>>> Yes, the 1 + 1 = 3 section :)</tt><br><tt>>>>>>></tt><br><tt>>>>>>> Having gone through multiple projects using the two, the main benefits</tt><br><tt>>>>>>> arising from the usage of ABAP OO together with Workflow and WDA are</tt><br><tt>>>>>>> reuse and encapsulation in my experience. What this basically means is</tt><br><tt>>>>>>> that when building a web enabled workflow solution having WDA as the</tt><br><tt>>>>>>> UI, we are first structuring the solution into architecturally</tt><br><tt>>>>>>> different layers. Most common layers in a typical scenario include the</tt><br><tt>>>>>>> UI layer (incl WDA), process integration layer (WF) and the business</tt><br><tt>>>>>>> logic layer (ABAP OO). Each of the scenario specific layers then have</tt><br><tt>>>>>>> several components like multiple WDA components, multiple workflow</tt><br><tt>>>>>>> definitions and multiple classes.</tt><br><tt>>>>>>></tt><br><tt>>>>>>> As an example, let's take a typical parked invoice approval scenario</tt><br><tt>>>>>>> where you need to have a web UI for casual invoice approvers, a</tt><br><tt>>>>>>> workflow to coordinate the process and a class to take care of invoice</tt><br><tt>>>>>>> actions and information provisioning. For the invoice object realized</tt><br><tt>>>>>>> as an ABAP OO class, the typical implementation should then include</tt><br><tt>>>>>>> not only WF interface methods, but also getters and setters (called as</tt><br><tt>>>>>>> functional methods from WF, and by WDA as instance methods), invoice</tt><br><tt>>>>>>> action methods (status changes triggered by WF and/or WDA) and static</tt><br><tt>>>>>>> methods used for invoice work item reporting etc. Having implemented</tt><br><tt>>>>>>> everything in one class, you can use e.g. the same object and its</tt><br><tt>>>>>>> methods efficiently and effectively by both the WDA and by the WF</tt><br><tt>>>>>>> definitions.</tt><br><tt>>>>>>></tt><br><tt>>>>>>> My experience in summary currently is that I would go no other way</tt><br><tt>>>>>>> than using ABAP OO in WF related projects. Switching back to BOR not</tt><br><tt>>>>>>> only would make my life miserable because of all the macros, outdated</tt><br><tt>>>>>>> editors and other features of BOR, but more importantly because its</tt><br><tt>>>>>>> integration to WDA would be so much more difficult when compared to</tt><br><tt>>>>>>> ABAP classes. There is of course the learning curve you need to</tt><br><tt>>>>>>> conquer as discussed in previous posts, but I definitely think it's</tt><br><tt>>>>>>> worth the leap.</tt><br><tt>>>>>>></tt><br><tt>>>>>>> Kind regards,</tt><br><tt>>>>>>> Mikko</tt><br><tt>>>>>>></tt><br><tt>>>>>>> Mikko Mäki-Rahkola</tt><br><tt>>>>>>> Managing Director</tt><br><tt>>>>>>> Nobultec Ltd</tt><br><tt>>>>>>> Tekniikantie 12</tt><br><tt>>>>>>> 02150 Espoo</tt><br><tt>>>>>>> Finland</tt><br><tt>>>>>>> +358 50 558 7834</tt><br><tt>>>>>>> mikko.maki-rahkola@nobultec.com</tt><br><tt>>>>>>> </tt></span><a href="www.nobultec.com"><tt><span style='font-size:10.0pt'>www.nobultec.com</span></tt></a><tt><span style='font-size:10.0pt'> - Work redistributed</span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>>>>>>> fi.linkedin.com/in/mikkomakirahkola - Follow me on LinkedIn</tt><br><tt>>>>>>> twitter.com/mikkomr - Follow me on Twitter</tt><br><tt>>>>>>> twitter.com/nobultec - Follow Nobultec on Twitter</tt><br><tt>>>>>>></tt><br><tt>>>>>>> _______________________________________________</tt><br><tt>>>>>>> SAP-WUG mailing list</tt><br><tt>>>>>>> SAP-WUG@mit.edu</tt><br><tt>>>>>>> </tt></span><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><span style='font-size:10.0pt'>http://mailman.mit.edu/mailman/listinfo/sap-wug</span></tt></a><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>>>>>> _______________________________________________</tt><br><tt>>>>>> SAP-WUG mailing list</tt><br><tt>>>>>> SAP-WUG@mit.edu</tt><br><tt>>>>>> </tt></span><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><span style='font-size:10.0pt'>http://mailman.mit.edu/mailman/listinfo/sap-wug</span></tt></a><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>>>>>></tt><br><tt>>>>> _______________________________________________</tt><br><tt>>>>> SAP-WUG mailing list</tt><br><tt>>>>> SAP-WUG@mit.edu</tt><br><tt>>>>> </tt></span><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><span style='font-size:10.0pt'>http://mailman.mit.edu/mailman/listinfo/sap-wug</span></tt></a><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>>>> _______________________________________________</tt><br><tt>>>> SAP-WUG mailing list</tt><br><tt>>>> SAP-WUG@mit.edu</tt><br><tt>>>> </tt></span><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><span style='font-size:10.0pt'>http://mailman.mit.edu/mailman/listinfo/sap-wug</span></tt></a><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>>>></tt><br><tt>>> _______________________________________________</tt><br><tt>>> SAP-WUG mailing list</tt><br><tt>>> SAP-WUG@mit.edu</tt><br><tt>>> </tt></span><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><span style='font-size:10.0pt'>http://mailman.mit.edu/mailman/listinfo/sap-wug</span></tt></a><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>> _______________________________________________</tt><br><tt>> SAP-WUG mailing list</tt><br><tt>> SAP-WUG@mit.edu</tt><br><tt>> </tt></span><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><span style='font-size:10.0pt'>http://mailman.mit.edu/mailman/listinfo/sap-wug</span></tt></a><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>></tt><br><tt>> _______________________________________________</tt><br><tt>> SAP-WUG mailing list</tt><br><tt>> SAP-WUG@mit.edu</tt><br><tt>> </tt></span><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><span style='font-size:10.0pt'>http://mailman.mit.edu/mailman/listinfo/sap-wug</span></tt></a><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>_______________________________________________</tt><br><tt>SAP-WUG mailing list</tt><br><tt>SAP-WUG@mit.edu</tt><br></span><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><span style='font-size:10.0pt'>http://mailman.mit.edu/mailman/listinfo/sap-wug</span></tt></a><span style='font-size:10.0pt;font-family:"Courier New"'><br><br></span><o:p></o:p></p><pre style='margin-bottom:12.0pt'>=====-----=====-----=====<br>Notice: The information contained in this e-mail<br>message and/or attachments to it may contain <br>confidential or privileged information. If you are <br>not the intended recipient, any dissemination, use, <br>review, distribution, printing or copying of the <br>information contained in this e-mail message <br>and/or attachments to it are strictly prohibited. If <br>you have received this communication in error, <br>please notify us by reply e-mail or telephone and <br>immediately and permanently delete the message <br>and any attachments. Thank you<br><br><o:p></o:p></pre></div></body></html>