[LIKELY JUNK]Re: [LIKELY JUNK]Re: [LIKELY JUNK]Re: Delivery selection & Schedule selection in Extended Notif. Config.

Fri Feb 27 03:18:42 EST 2009

Jocelyn, Ramki,

We're talking about different things I think.
I'm just trying to set up a this in a standard environment : ECC6 / SAP GUI
/ Outlook & that's it.

I don't understand why I'm blocked with this error related to BSP (which we
don't use).

kind regards,
Stefaan.

2009/2/27 Dart, Jocelyn <jocelyn.dart at sap.com>

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