<div>Jocelyn, Ramki,</div>
<div> </div>
<div>We're talking about different things I think.</div>
<div>I'm just trying to set up a this in a standard environment : ECC6 / SAP GUI / Outlook & that's it.</div>
<div> </div>
<div>I don't understand why I'm blocked with this error related to BSP (which we don't use).</div>
<div> </div>
<div>kind regards,</div>
<div>Stefaan.</div>
<div> </div>
<div><br><br> </div>
<div class="gmail_quote">2009/2/27 Dart, Jocelyn <span dir="ltr"><<a href="mailto:jocelyn.dart@sap.com">jocelyn.dart@sap.com</a>></span><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div dir="ltr" align="left"><span><font face="Arial" color="#0000ff" size="2">Folks, there is a BSP application used for the Message Template - you can see the name in that section of SWNCONFIG. </font></span></div>
<div dir="ltr" align="left"><span><font face="Arial" color="#0000ff" size="2">It's used to build the layout of the reminder. </font></span></div>
<div dir="ltr" align="left"><span><font face="Arial" color="#0000ff" size="2">Regards,</font></span></div>
<div dir="ltr" align="left"><span><font face="Arial" color="#0000ff" size="2">Jocelyn </font></span></div><br>
<div lang="en-us" dir="ltr" align="left">
<hr>
<font face="Tahoma" size="2">
<div class="im"><b>From:</b> <a href="mailto:sap-wug-bounces@mit.edu" target="_blank">sap-wug-bounces@mit.edu</a> [mailto:<a href="mailto:sap-wug-bounces@mit.edu" target="_blank">sap-wug-bounces@mit.edu</a>] <b>On Behalf Of </b>Stefaan Vermeulen<br>
</div><b>Sent:</b> Thursday, 26 February 2009 10:13 PM
<div class="im"><br><b>To:</b> SAP Workflow Users' Group<br></div><b>Subject:</b> [LIKELY JUNK]Re: [LIKELY JUNK]Re: [LIKELY JUNK]Re: Delivery selection & Schedule selection in Extended Notif. Config.<br></font><br>
</div>
<div>
<div></div>
<div class="h5">
<div></div>
<div>Rick,</div>
<div> </div>
<div>Not really, I presume it's not about e-mail addresses or phone numbers, but because of not having a BSP template or active protal, more in that region.</div>
<div> </div>
<div>kr,S;<br><br></div>
<div class="gmail_quote">2009/2/26 Rick Bakker <span dir="ltr"><<a href="mailto:rbakker@gmail.com" target="_blank">rbakker@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hello,<br><br>Did you look what's happening within fm SWN_CALL_BSP during debug<br>to see why it's "Unable to determine" e-mail addresses and telephone numbers?<br>
<div><br>regards<br>Rick Bakker<br>Hanabi Technology<br><br></div>
<div>
<div></div>
<div>On 2/25/09, Griffiths, Mark <<a href="mailto:mark.griffiths@sap.com" target="_blank">mark.griffiths@sap.com</a>> wrote:<br>><br>> That error message sometimes results from some of the SWN* BSP applications<br>
> not being activated in transaction SICF.<br>><br>> Hope this helps,<br>><br>><br>> Mark<br>><br>> SAP UK<br>><br>><br>> ________________________________<br>><br>> From: <a href="mailto:sap-wug-bounces@mit.edu" target="_blank">sap-wug-bounces@mit.edu</a><br>
> [mailto:<a href="mailto:sap-wug-bounces@mit.edu" target="_blank">sap-wug-bounces@mit.edu</a>] On Behalf Of Stefaan<br>> Vermeulen<br>> Sent: 25 February 2009 15:57<br>> To: SAP Workflow Users' Group<br>> Subject: [LIKELY JUNK]Re: [LIKELY JUNK]Re: Delivery selection & Schedule<br>
> selection in Extended Notif. Config.<br>><br>><br>> Thanks Rick and Jocelyn for the extra info,<br>><br>> I narrowed my problem down to the sending part of SWN_SELSEN.<br>> Message SWN 032 seems to be the killer here.<br>
> By debugging it seems a call function that uses a template related to BSP<br>> produces the error.<br>> message SWN 032.<br>><br>> I thought solving this by creating another delivery type not related to the<br>
> template, but it seems this field( BSP-URL) has to be filled up.<br>><br>> What am I still missing ?<br>><br>> kind regards,<br>> Stefaan.<br>> In attachment related prints<br>><br>><br>><br>
><br>><br>><br>> 2009/2/24 Rick Bakker <<a href="mailto:rbakker@gmail.com" target="_blank">rbakker@gmail.com</a>><br>> > Stefaan,<br>> ><br>> > Stefaan,<br>> ><br>> > How many entries do you have in table SWN_NOTIF? That's<br>
> > the table filled by the Selection process and read by<br>> > the Delivery process.<br>> ><br>> > Because you haven't been able to send any, maybe they're<br>> > piling up. And maybe when you first ran it you didn't<br>
> > have a very restrictive filter in place? This could explain<br>> > why it's showing 56K notifications selected.<br>> ><br>> > I tried removing the telephone number from a user, the notification<br>
> > still made it to SOST.<br>> ><br>> ><br>> > regards<br>> > Rick Bakker<br>> > Hanabi Technology<br>> ><br>> ><br>> ><br>> ><br>> > On 2/23/09, Rick Bakker <<a href="mailto:rbakker@gmail.com" target="_blank">rbakker@gmail.com</a>> wrote:<br>
> > > Stefaan,<br>> > ><br>> > > 'Unable to send 000000 messages due to errors'<br>> > > That's good news.<br>> > ><br>> > > "It seems that also the users telephone number has to be filled in to<br>
> > > avoid an error"<br>> > > I find that very unlikely. I'll have to try that. I suspect all my users<br>> > > have telephone numbers.<br>> > ><br>> > > "The subscription part is that Ok(attachment)? in your opinion "<br>
> > > Yes. Well, it's the same as mine.<br>> > ><br>> > > I'm not sure why it's picking up 50K messages, SLG1 is<br>> > > a good idea. Or do some debugging - a good way to learn<br>
> > > about the internals.<br>> > ><br>> > > regards<br>> > > Rick Bakker<br>> > > Hanabi Technology<br>> > ><br>> > ><br>> > > On 2/23/09, Dart, Jocelyn <<a href="mailto:jocelyn.dart@sap.com" target="_blank">jocelyn.dart@sap.com</a>> wrote:<br>
> > > ><br>> > > > Stefan,<br>> > > ><br>> > > > Try using transaction SLG1 when you get errors ... you will find logs<br>> giving<br>> > > > more details.<br>
> > > > Regards,<br>> > > > Jocelyn<br>> > > > ________________________________<br>> > > > From: <a href="mailto:sap-wug-bounces@mit.edu" target="_blank">sap-wug-bounces@mit.edu</a><br>
> > > > [mailto:<a href="mailto:sap-wug-bounces@mit.edu" target="_blank">sap-wug-bounces@mit.edu</a>] On Behalf Of Stefaan<br>> > > > Vermeulen<br>> > > > Sent: Monday, 23 February 2009 9:44 PM<br>
> > > > To: SAP Workflow Users' Group<br>> > > > Subject: [LIKELY JUNK]Re: Delivery selection & Schedule selection in<br>> > > > Extended Notif. Config.<br>> > > ><br>
> > > ><br>> > > > Rick,<br>> > > ><br>> > > > Thanks for the answer.<br>> > > > Like you said, combination of bad naming of parameters and more<br>> > > > posibilities.<br>
> > > ><br>> > > > The previous screen-shot was indeed related to a initial date for a<br>> delta.<br>> > > > After that I executed it again and got a number of selected<br>> notifications.<br>
> > > > But in the end I got the very helpfull message.<br>> > > > 'Unable to sent 000000 messages due to errors'.<br>> > > ><br>> > > > I'm still wrestling to get a message in /nSCOT.<br>
> > > > It seems that also the users telephone number has to be filled in to<br>> avoid<br>> > > > an error ?<br>> > > ><br>> > > > The subscription part is that Ok(attachment)? in you're opinion ? for<br>
> a<br>> > > > plain SAPGui on ECC6 with a outlook mail server ?<br>> > > ><br>> > > > I used also used swn_selsen_test to cast some light to the problem,<br>> without<br>> > > > much succes.<br>
> > > > Even my filter of one specific task gives about 50000 items selected.<br>> > > ><br>> > > > I'm afraid that debugging will be necessary<br>> > > ><br>> > > > Txs,<br>
> > > > S.<br>> > > ><br>> > > > 2009/2/20 Rick Bakker <<a href="mailto:rbakker@gmail.com" target="_blank">rbakker@gmail.com</a>><br>> > > > > Hello,<br>> > > > ><br>
> > > > > I haven't encountered that warning in your attachment:<br>> > > > ><br>> > > > > Filter YTIB_DELTA does not have a time stamp<br>> > > > ><br>> > > > > but I guess it means that it's try to apply a delta<br>
> > > > > while it doesn't have a baseline time. It could be<br>> > > > > that it'll only give that warning the first time.<br>> > > > ><br>> > > > > regards<br>
> > > > ><br>> > > > > Rick Bakker<br>> > > > > Hanabi Technology<br>> > > > ><br>> > > > > On 2/20/09, Stefaan Vermeulen <<a href="mailto:stefaan.vermeulen@gmail.com" target="_blank">stefaan.vermeulen@gmail.com</a>> wrote:<br>
> > > > ><br>> > > > ><br>> > > > ><br>> > > > > > Hi all,<br>> > > > > ><br>> > > > > > I took the time to search trough the sap-help, group archives and<br>
> sdn<br>> > > > blogs,<br>> > > > > > without specific answers to this question.<br>> > > > > ><br>> > > > > > Although I'm quite familiar with the SAP-logic it stuns me from<br>
> time to<br>> > > > > > time how one can create something complicated for simple things<br>> like<br>> > > > > > scheduling.<br>> > > > > > I'm used to the scheduling with rswuwfml2( I don't see regarding<br>
> > > > scheduling<br>> > > > > > what was wrong with these parameters)<br>> > > > > ><br>> > > > > > Can someone explain me in a simple way how to use these 3<br>
> parameters in<br>> > > > > > combination and how they influence each other ?<br>> > > > > > -Schedule selection.<br>> > > > > > -Delivery schedule<br>> > > > > > -The scheduling of the program SWN_SELSEN<br>
> > > > > ><br>> > > > > > I kept it simple regarding these config and selected every day of<br>> the<br>> > > > week<br>> > > > > > from 06:00 to 17:00.<br>
> > > > > ><br>> > > > > > The only thing I want to do is ; send a few new created work-items<br>> to<br>> > > > > > outlook.<br>> > > > > > I'm fumbling around with SWN_SELSEN_TEST with a DELTA filter but<br>
> (first)<br>> > > > > > without restrictions on TASK in filter.<br>> > > > > > I don't get a clear view of the problem in<br>> SWN_SELSEN_TEST.(attachment)<br>> > > > > ><br>
> > > > > > Thanks,<br>> > > > > > Stefaan.<br>> > > > > ><br>> > > > > ><br>> > > > > ><br>> > > > ><br>> > > > ><br>
> > > > ><br>> > > > > > _______________________________________________<br>> > > > > > SAP-WUG mailing list<br>> > > > > > <a href="mailto:SAP-WUG@mit.edu" target="_blank">SAP-WUG@mit.edu</a><br>
> > > > > > <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>> > > > > ><br>> > > > > ><br>
> > > > > ><br>> > > > > _______________________________________________<br>> > > > > SAP-WUG mailing list<br>> > > > > <a href="mailto:SAP-WUG@mit.edu" target="_blank">SAP-WUG@mit.edu</a><br>
> > > > > <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>> > > > ><br>> > > ><br>> > > ><br>
> > > > _______________________________________________<br>> > > > SAP-WUG mailing list<br>> > > > <a href="mailto:SAP-WUG@mit.edu" target="_blank">SAP-WUG@mit.edu</a><br>> > > > <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
> > > ><br>> > > ><br>> > ><br>> > _______________________________________________<br>> > SAP-WUG mailing list<br>> > <a href="mailto:SAP-WUG@mit.edu" target="_blank">SAP-WUG@mit.edu</a><br>
> > <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>> ><br>><br>><br>> _______________________________________________<br>
> SAP-WUG mailing list<br>> <a href="mailto:SAP-WUG@mit.edu" target="_blank">SAP-WUG@mit.edu</a><br>> <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
><br>><br>_______________________________________________<br>SAP-WUG mailing list<br><a href="mailto:SAP-WUG@mit.edu" target="_blank">SAP-WUG@mit.edu</a><br><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
</div></div></blockquote></div><br></div></div></div><br>_______________________________________________<br>SAP-WUG mailing list<br><a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
<br></blockquote></div><br>