[LIKELY JUNK]In reference with an earlier question of problems with extended notifications (HTTP error 403)

Dart, Jocelyn jocelyn.dart at sap.com
Tue Mar 24 00:38:02 EDT 2009


Hi Stefan,
That BSP application creates the layout of the extended notifications email messages for all the different formats (plain, html, sms).
So yes absolutely mandatory that this service has to be active.
Regards,
Jocelyn 

________________________________

From: sap-wug-bounces at mit.edu on behalf of Stefaan Vermeulen
Sent: Sat 21/03/2009 2:16 AM
To: SAP Workflow Users' Group
Subject: [LIKELY JUNK]In reference with an earlier question of problems with extended notifications (HTTP error 403)


Hi,
 
Previously I encountered via the possible logs & SWN test program just a message that no messages were sent.
Altough the config. was confirmed to be OK by some users of this group.
I had some more time to get to the bottom of it (debug SWN_SELSEN_TEST).
 
Last time I stranded at the error from call function SWN_CALL_BSP that gave an error.
Since I do not use BSP I didn't put to much attention to it.
 
I went a bit deeper into it and saw that the function is used to call up a service I presume to create a message content.
I found a OSSnote 603624  related to http client 403 forbidden error.
Since I'm on a new ECC6 in development it is possible that these services are not all set to active, what indeed is the case, I could check with  /nSICF.
 
/default_host/sap/bc/bsp/sap/swn_message1
 
My question is 3 way's; Can someone conform this that even without using BSP, this service has to be active?
What does this service exactly do  ?
Is it enough to activate only this service 
 
Kr,Stefaan.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 5172 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20090324/8a5fb674/attachment.bin


More information about the SAP-WUG mailing list