<br><font size=2 face="sans-serif">Hi,</font>
<br>
<br><font size=2 face="sans-serif">I have tried to launch WD application
from extended notification but its not working.</font>
<br><font size=2 face="sans-serif">I have maintained only SWFVISU.</font>
<br>
<br><font size=2 face="sans-serif">Can anybody suggest what needs to be
maintain in </font><tt><font size=2>WD_HOST</font></tt><font size=2 face="sans-serif">
( </font><tt><font size=2>SWNCONFIG</font></tt><font size=2 face="sans-serif">
) ?</font>
<br><font size=2 face="sans-serif"><br>
Sanjay Pal<br>
Asst System Engineer<br>
Tata Consultancy Services<br>
Mailto: sanjay9.p@tcs.com<br>
Website: </font><a href=http://www.tcs.com/><font size=2 face="sans-serif">http://www.tcs.com</font></a><font size=2 face="sans-serif"><br>
____________________________________________<br>
Experience certainty. IT Services<br>
Business Solutions<br>
Outsourcing<br>
____________________________________________</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">From:</font>
<td><font size=1 face="sans-serif">Ramki Maley <rmaley@erpworkflow.com></font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">To:</font>
<td><font size=1 face="sans-serif">"SAP Workflow Users' Group"
<sap-wug@mit.edu></font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Date:</font>
<td><font size=1 face="sans-serif">03/10/2011 07:27 PM</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Subject:</font>
<td><font size=1 face="sans-serif">Re: Launching WDA items from Extended
Notifications</font>
<tr valign=top>
<td><font size=1 color=#5f5f5f face="sans-serif">Sent by:</font>
<td><font size=1 face="sans-serif">sap-wug-bounces@mit.edu</font></table>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2>Thanks Jocelyn. I wasn't sure if SWFVISU would still
work in a non UWL <br>
environment.<br>
<br>
Regards,<br>
Ramki.<br>
<br>
On 3/9/11 11:12 PM, Dart, Jocelyn wrote:<br>
> Ramki,<br>
> 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.<br>
><br>
> This works even if you aren't using the UWL and doesn't need any coding.<br>
><br>
> Regards,<br>
> Jocelyn<br>
><br>
><br>
> -----Original Message-----<br>
> From: sap-wug-bounces@mit.edu [</font></tt><a href="mailto:sap-wug-bounces@mit.edu"><tt><font size=2>mailto:sap-wug-bounces@mit.edu</font></tt></a><tt><font size=2>]
On Behalf Of Ramki Maley<br>
> Sent: Saturday, February 26, 2011 3:47 AM<br>
> To: SAP Workflow Users' Group<br>
> Subject: Re: Launching WDA items from Extended Notifications<br>
><br>
> Mike, apologies for the drifting and thanks again for separating the<br>
> issue and your valuable suggestions.<br>
><br>
> Best Regards,<br>
> Ramki.<br>
><br>
> On 2/25/11 11:40 AM, Mike Pokraka wrote:<br>
>> Hi Ramki,<br>
>><br>
>> We've drifted way off topic into specific problems so I changed
the<br>
>> title...<br>
>><br>
>> Had a quick look, can use SAP_WAPI_GET_METHODS to derive whether
it's a<br>
>> webby item and SAP_WAPI_LAUNCH_URL_GET is self-explanatory.<br>
>><br>
>> That's the easy bit, the extended notification part can get a
tricky.<br>
>> Haven't worked with it for a while but from memory I think you
may need to<br>
>> do an enhancement. CL_SWN_NOTIF_WORKFLOW is a good starting point.<br>
>><br>
>> Cheers,<br>
>> Mike<br>
>><br>
>> On Fri, February 25, 2011 4:12 pm, Ramki Maley wrote:<br>
>>> Mike, great ideas. I will look into them. I am under severe
time<br>
>>> constraints and was thinking in the lines of your first suggestion.<br>
>>><br>
>>> Many Thanks,<br>
>>> Ramki.<br>
>>><br>
>>> On 2/25/11 11:06 AM, Mike Pokraka wrote:<br>
>>>> Hi Ramki,<br>
>>>><br>
>>>> The main issue is that your're launching a web app which
drops down into<br>
>>>> GUI mode to launch a new web app. Very roundabout and
spawns an extra<br>
>>>> unnecessary session.<br>
>>>><br>
>>>> There are a few ways to work around this, mostly involving
customizing<br>
>>>> Extended Notifications to some degree. You can look at
the work item and<br>
>>>> if it's web-based then pull out the URL the work item
is trying to<br>
>>>> launch<br>
>>>> (there's a WAPI for it), and put that into the mail instead
of the link<br>
>>>> to<br>
>>>> SWNWIEX.<br>
>>>><br>
>>>> Another solution I've built is to redirect everything
to a filter app<br>
>>>> which looks at where it was launched from, what the work
item does and<br>
>>>> then decides what to do. Useful if you have multiple entry
points and<br>
>>>> execution mode. (e.g. if single approval in user's inbox,
launch yes/no<br>
>>>> window, if multiple approvals in inbox then launch an
overview app).<br>
>>>><br>
>>>> Cheers,<br>
>>>> Mike<br>
>>>><br>
>>>> On Fri, February 25, 2011 3:13 pm, Ramki Maley wrote:<br>
>>>>> Mikko, thanks for a great reply. I fully agree with
you. I too have<br>
>>>>> been<br>
>>>>> using ABAP-OO to create new objects, new methods for
existing BOR etc.<br>
>>>>><br>
>>>>> I am in a situation where the users want WebDynpro
and don't want<br>
>>>>> anything to do with SAPGUI. The client does not have
EP. We have built<br>
>>>>> a<br>
>>>>> simple WDA application and used WF_EXTSRV to generate
a task for it.<br>
>>>>> This works fine when executed from the SBWP. The issue
is when an email<br>
>>>>> with Execute Workitem link is sent to Outlook using
Extended<br>
>>>>> Notifictions. Since the link executes Txn. SWNWIEX,
the 'Close Window'<br>
>>>>> screen is opened first in SAPGUI/browser and then
the WDA is launched.<br>
>>>>><br>
>>>>> Is there any way to launch the WebDynpro from the
email other than<br>
>>>>> actually putting the URL in the workitem description?<br>
>>>>><br>
>>>>> Thanks,<br>
>>>>> Ramki.<br>
>>>>><br>
>>>>><br>
>>>>><br>
>>>>> On 2/25/11 2:24 AM, Mikko Mäki-Rahkola wrote:<br>
>>>>>> Hi all,<br>
>>>>>><br>
>>>>>> interesting to hear other workflowers' experiences
on ABAP OO and WDA<br>
>>>>>> usage! I hope you (especially Sue, Mike and Ramki)
however don't mind<br>
>>>>>> me as a late joiner combining the two topics of
ABAP OO for WF and WDA<br>
>>>>>> for WF when sharing my experiences, since I've
been accustomed to<br>
>>>>>> using both of them simultaneously and I strongly
believe that 1 + 1 =<br>
>>>>>> 3 in this case :)<br>
>>>>>><br>
>>>>>> ABAP OO for WF experiences:<br>
>>>>>> We've now been using ABAP OO for WF in ~10-15
projects since 2007 and<br>
>>>>>> I can pretty much agree on the use cases and comments
already stated.<br>
>>>>>> Our rule of thumb is similar to others', we are
using ABAP OO for WF<br>
>>>>>> in cases where new functionality is required.
Such cases have included<br>
>>>>>> e.g. request objects in need of object specific
functionality (like<br>
>>>>>> material requests, where the usage of ISR notification
objects is not<br>
>>>>>> sufficient), but also completely new objects which
SAP doesn't support<br>
>>>>>> at all in BOR (e.g. SAP HCM Enterprise Compensation
Management). Cases<br>
>>>>>> where not to go with ABAP OO and resort to existing
BOR objects have<br>
>>>>>> included e.g. event handling, simple workflows
(like IDoc handling)<br>
>>>>>> where the standard objects are sufficient and
customer driven cases<br>
>>>>>> where the usage of BOR objects have been a must.<br>
>>>>>><br>
>>>>>> In general, we are using BOR objects nowadays
only where it's<br>
>>>>>> necessary like event handling or where the ABAP
OO<br>
>>>>>> replacing/complementing functionality would require
too big an effort<br>
>>>>>> when compared to a standard BOR object. The main
benefits we have<br>
>>>>>> perceived of going ABAP OO instead of BOR come
from a developer<br>
>>>>>> perspective. People using ABAP OO in other development
(see my<br>
>>>>>> comments below) are quickly accustomed to using
the WF class<br>
>>>>>> interface, the class editor is familiar to them
and there is no need<br>
>>>>>> for a separate editor, there are less restrictions
(anyone had a<br>
>>>>>> requirement for more than one delegation/subclass?)
and in general<br>
>>>>>> there's a single development environment which
can be utilised for<br>
>>>>>> other development as well.<br>
>>>>>><br>
>>>>>> WDA for WF experiences:<br>
>>>>>> WDA has been around in our projects since 2007-2008
after customers<br>
>>>>>> started upgrading their systems to SAP ERP 6.0
(gladly no more WDJ<br>
>>>>>> since then!) and most of the WDA solutions we've
done have been<br>
>>>>>> integrated to WF in one way or the other. Some
have just started off a<br>
>>>>>> workflow either through a custom or a standard
event, some have been<br>
>>>>>> been developed for work item processing (= approval
views) and some<br>
>>>>>> have been done for work item reporting. Since
both WDA and WF work on<br>
>>>>>> the ABAP runtime, they work beautifully together.
Firing events with<br>
>>>>>> ABAP OO for WF, processing work items and reporting
on them are as<br>
>>>>>> straightforward with WDA as with plain ABAP.<br>
>>>>>><br>
>>>>>> Currently our nr 1 choice for a new customer specific
web user<br>
>>>>>> interface sitting on top of any SAP Business Suite
(ok CRM and SRM may<br>
>>>>>> be different) is WDA as per SAP's Best Built Application
guidelines.<br>
>>>>>> As Mike P stated before, it has lots of benefits
when compared to the<br>
>>>>>> other alternatives (WDJ, BSP, VC) available. So
our outlook on it is<br>
>>>>>> very positive, it works well together with WF
implementations and also<br>
>>>>>> has UI-wise very powerful features like POWL and
FPM delivered with<br>
>>>>>> the framework.<br>
>>>>>><br>
>>>>>> WDA + ABAP OO for WF experiences:<br>
>>>>>> Yes, the 1 + 1 = 3 section :)<br>
>>>>>><br>
>>>>>> Having gone through multiple projects using the
two, the main benefits<br>
>>>>>> arising from the usage of ABAP OO together with
Workflow and WDA are<br>
>>>>>> reuse and encapsulation in my experience. What
this basically means is<br>
>>>>>> that when building a web enabled workflow solution
having WDA as the<br>
>>>>>> UI, we are first structuring the solution into
architecturally<br>
>>>>>> different layers. Most common layers in a typical
scenario include the<br>
>>>>>> UI layer (incl WDA), process integration layer
(WF) and the business<br>
>>>>>> logic layer (ABAP OO). Each of the scenario specific
layers then have<br>
>>>>>> several components like multiple WDA components,
multiple workflow<br>
>>>>>> definitions and multiple classes.<br>
>>>>>><br>
>>>>>> As an example, let's take a typical parked invoice
approval scenario<br>
>>>>>> where you need to have a web UI for casual invoice
approvers, a<br>
>>>>>> workflow to coordinate the process and a class
to take care of invoice<br>
>>>>>> actions and information provisioning. For the
invoice object realized<br>
>>>>>> as an ABAP OO class, the typical implementation
should then include<br>
>>>>>> not only WF interface methods, but also getters
and setters (called as<br>
>>>>>> functional methods from WF, and by WDA as instance
methods), invoice<br>
>>>>>> action methods (status changes triggered by WF
and/or WDA) and static<br>
>>>>>> methods used for invoice work item reporting etc.
Having implemented<br>
>>>>>> everything in one class, you can use e.g. the
same object and its<br>
>>>>>> methods efficiently and effectively by both the
WDA and by the WF<br>
>>>>>> definitions.<br>
>>>>>><br>
>>>>>> My experience in summary currently is that I would
go no other way<br>
>>>>>> than using ABAP OO in WF related projects. Switching
back to BOR not<br>
>>>>>> only would make my life miserable because of all
the macros, outdated<br>
>>>>>> editors and other features of BOR, but more importantly
because its<br>
>>>>>> integration to WDA would be so much more difficult
when compared to<br>
>>>>>> ABAP classes. There is of course the learning
curve you need to<br>
>>>>>> conquer as discussed in previous posts, but I
definitely think it's<br>
>>>>>> worth the leap.<br>
>>>>>><br>
>>>>>> Kind regards,<br>
>>>>>> Mikko<br>
>>>>>><br>
>>>>>> Mikko Mäki-Rahkola<br>
>>>>>> Managing Director<br>
>>>>>> Nobultec Ltd<br>
>>>>>> Tekniikantie 12<br>
>>>>>> 02150 Espoo<br>
>>>>>> Finland<br>
>>>>>> +358 50 558 7834<br>
>>>>>> mikko.maki-rahkola@nobultec.com<br>
>>>>>> </font></tt><a href=www.nobultec.com><tt><font size=2>www.nobultec.com</font></tt></a><tt><font size=2>
- Work redistributed<br>
>>>>>> fi.linkedin.com/in/mikkomakirahkola - Follow me
on LinkedIn<br>
>>>>>> twitter.com/mikkomr - Follow me on Twitter<br>
>>>>>> twitter.com/nobultec - Follow Nobultec on Twitter<br>
>>>>>><br>
>>>>>> _______________________________________________<br>
>>>>>> SAP-WUG mailing list<br>
>>>>>> SAP-WUG@mit.edu<br>
>>>>>> </font></tt><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><font size=2>http://mailman.mit.edu/mailman/listinfo/sap-wug</font></tt></a><tt><font size=2><br>
>>>>> _______________________________________________<br>
>>>>> SAP-WUG mailing list<br>
>>>>> SAP-WUG@mit.edu<br>
>>>>> </font></tt><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><font size=2>http://mailman.mit.edu/mailman/listinfo/sap-wug</font></tt></a><tt><font size=2><br>
>>>>><br>
>>>> _______________________________________________<br>
>>>> SAP-WUG mailing list<br>
>>>> SAP-WUG@mit.edu<br>
>>>> </font></tt><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><font size=2>http://mailman.mit.edu/mailman/listinfo/sap-wug</font></tt></a><tt><font size=2><br>
>>> _______________________________________________<br>
>>> SAP-WUG mailing list<br>
>>> SAP-WUG@mit.edu<br>
>>> </font></tt><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><font size=2>http://mailman.mit.edu/mailman/listinfo/sap-wug</font></tt></a><tt><font size=2><br>
>>><br>
>> _______________________________________________<br>
>> SAP-WUG mailing list<br>
>> SAP-WUG@mit.edu<br>
>> </font></tt><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><font size=2>http://mailman.mit.edu/mailman/listinfo/sap-wug</font></tt></a><tt><font size=2><br>
> _______________________________________________<br>
> SAP-WUG mailing list<br>
> SAP-WUG@mit.edu<br>
> </font></tt><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><font size=2>http://mailman.mit.edu/mailman/listinfo/sap-wug</font></tt></a><tt><font size=2><br>
><br>
> _______________________________________________<br>
> SAP-WUG mailing list<br>
> SAP-WUG@mit.edu<br>
> </font></tt><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><font size=2>http://mailman.mit.edu/mailman/listinfo/sap-wug</font></tt></a><tt><font size=2><br>
_______________________________________________<br>
SAP-WUG mailing list<br>
SAP-WUG@mit.edu<br>
</font></tt><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug"><tt><font size=2>http://mailman.mit.edu/mailman/listinfo/sap-wug</font></tt></a><tt><font size=2><br>
</font></tt>
<br>
<br><pre style="white-space:normal">=====-----=====-----=====<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><br></pre>