RSWUWFML2 in ECC 6.0

[Dart, Jocelyn]

Hi Zsolt, 
 
You should NOT be using RSWUWFML2 in ECC 6.0 but should move to the new Extended Notifications instead (transaction SWNCONFIG / batch program SWN_SELSEN).
 
Extended Notifications will send executable attachments also if you wish - you just need to create a subscription and set the subscription parameters appropriately. 
You should also make sure you adjust the General Settings area for the appropriate host/port information. 
Extended Notifications also provides many extension options by creating handler classes to control data/links selected and BSP application to control layout.
You do NOT need to change any workflows. 
 
While RSWUWFML2 may continue to work if you are lucky it is now deprecated and should not be used. 
 
You should also check your SCOT settings to make sure the relevant attachment types are permitted for INT type mails.
 
P.s. In future PLEASE make sure you put a subject on your emails ... otherwise they are likely to be marked as SPAM - I almost missed this one.
 
Hope that helps. 
Regards,
Jocelyn
 
 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Márton Zsolt
Sent: Thursday, 12 February 2009 7:35 AM
To: SAP Workflow Users' Group
Subject: [LIKELY JUNK]



Hi all,

I'm in a middle of an 4.6c->ECC60 upgrade.  

There are two customer developed workflows (PR approval and invoice approval) which works with an executable attachment (R3F) in Outlook. The proper task use BO FORM-PROCESS BO and method. The attachment is created by using SAP forms and the workitem was sent by a copy of RSWUWFML2. 

After approval or rejection in the outlook the User has to confirm that the Outlook may send an e-mail automatically on his behalf.

 

After the DEV upgrade we realized that the workitem notification is sent properly but the attachment is not in an executable format. (via RSWUWFML2)

I've  customized the Extended Notification, the email notification is  sent, but I can not attach the form. (the form can be shown in the workflow log, but can not be executed (shown) in the outgoing message created in SCOT). 

 

What could be the problem?

Is there any solution to use the regular old process, or do I have to change the hole workflow?  If I can not use the specified form anymore, is there any solution to replace without rewriting the hole process?

Can an executable attachment added to the workitem using the extended notification (not the sap gui links)?

 

Unfortunately the problem is very urgent and important. :-( 

Thanks in advance

Regards

zsolt

 

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20090212/81a96a73/attachment.htm