Need to send extended notifications from different names: yes? no?

[Mike Pokraka]

Hi Alan,

 

Good to hear from you again. The cunning way you referred to below works as
follows:

 

You will need to different schedules interleaved at different times. For the
purposes of this example we will use one-hour intervals:

Schedule ReactQuick is set up for 0:55 at two-hour intervals.

Schedule DoYourColleagueAFavour is set up for 01:55 at two-hour intervals.

Delivery will be at 1:00, hourly intervals.

 

The cunning part in this whole plan is in the way that the SWN_SELSEN job
shall be scheduled:

One shall run under a userID ReactQuick at 01:05 every two hours.

Another one shall run under a userid DoYourColleagueAFavour at 02:05 every
two hours.

 

The basic premise of this technique is to isolate the schedule, delivery and
sending processes from each other by timing them in the right sequence in
order to be able to have one userid sending jobs for one schedule. Once they
are isolated, it's a simple matter of putting the required tasks into the
appropriate schedules.

 

Cheers,

Mike

 

 

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Rickayzen, Alan
Sent: 19 August 2008 23:02
To: SAP Workflow Users' Group
Subject: Re: Need to send extended notifications from different names: yes?
no?

 

Hi Shai,

Thanks very much for your feedback (and Ramki).

 

I don't want to raise false expectations because I'm not investigating this
for the standard SAP Business Workflow capability (but I'll pass your
feedback on to my colleagues) - it's only the integration with Lotus  Notes
that I can influence.

 

It sounds as if 

a) "disguising" the sender address or configuring it is useful and

b) it would be handy to have different names for different tasks but this is
something that is not a must-have and

c) that there may be a possible work-around to enable the above option by by
scheduling the batch jobs in a cunning way.

 

Many thanks for your feedback,

Alan

SAP AG

 

  _____  

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Shai Eyal
Sent: Tuesday 19 August 2008 20:44
To: sap-wug at mit.edu
Subject: [LIKELY JUNK]Re: Need to send extended notifications from different
names: yes? no?

Alan,

 

I accomplished that by scheduling the RSWUWFML2 under different name and I
assume doing the same for SWN_SELSEN suppose to work the same. The thing is
that I'll need several jobs (one for each sender...).

As for your comment, I think the sender should be task dependant.

As for e-mail sent from WF-BATCH - this resolved within subtype.

 

Off-course it'd be great to this functionality within standard SAP.

 

BTW, if we're already discussing Extended Notification, one major missing
functionality: In case you use extended notification to send collective
message (which is unique for extended notification) the subject will always
be the same, like "you have workitems in you inbox". This is very limiting -
the subject should have been the scenario description. Example: I send
collective mails for Notification processing and another for requisition
release.

I've expected to have the mail subject accordingly. Off-course I developed
this functionality using enhancement implementation however I think it
should have been in the standard system.

 

Thanks.

 

Regards,
Shai Eyal

SAP Logistics senior consultant
SAP Workflow specialist
Mobile: 972-52-5816633

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20080820/34193a1c/attachment.htm