Inbox messages sent by WF-BATCH with no Expiry Date.

Mon Sep 26 10:37:44 EDT 2005

Bruno,

Thanks for the reply. 

We asked SAP for a fix to get "all" messages stamped with Expiry Date.

This was not working for WF-BATCH. I just got a reply back from them
Friday
but have not had time to review. 

With the list of notes below, the normal reorg programs will clean up 
any new messages beyond this Expiry Date "if read". 

We have also implemented and modified Note 862985. This will help us 
clean up all those old messages that have no Expiry Date set and 
clean up those users who never read the messages. 
We can now delete un-read messages past Create Date + (var). 

Our policy from the beginning was that SAP Inbox was to be used for
messages 
only, not used for e-mail type functionality, and no long term storage
of system / app messages. 

Notes:
567975 Reorganization of send operations
870566 Method SOFM.Send sets no expiry date
646332 SOFM: Expiry date is not transferred (SOFM->Compose)
881594 Default Expiry Date set for office documents of workflow

I will let keep you posted.

Rick Sample

>>> Bruno.Magnani at Equistarchem.com 9/26/2005 5:33:29 >>>
Rick,

SAP just came back to me on this issue and published OSS note 881594
and
related. 

I did not have time to check in detail yet, but basically this would
allow you to specify an expiration date for workflow related messages
and subsequent deletion through a new version of RSSODFRE.

Although not the last word in safe, automatic cleanup of all obsolete
messages, it should help quite a bit, because the workflow messages
probably are a major contributor to the ever-increasing Office tables.

I do not want to resort to deletion of messages based on creation
date;
so more work to follow in other application areas. 

I'll keep you posted.  

Bruno Magnani  

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
Behalf
Of Rick Sample
Sent: Tuesday, July 12, 2005 8:10 PM
To: Magnani, Bruno G.; sap-wug at mit.edu 
Subject: RE: Inbox messages sent by WF-BATCH with no Expiry Date.

Bruno,

We will be requesting SAP to fix the Expiry Date issue(s) for WF-BATCH

if we cannot do some of the maintenance we want automatically or by
batch. 

That is, after I do a little more digging. The more I dig, the more
questions 

I come up with. ;-} I will let you know what we get back if you want. 

RSSODFRE:

We know about RSSODFRE. 

>From my understanding, this kills some WF-BATCH "folders". 

RSSODLWF: 

I just started reviewing. This looks like it deletes only Dark
"files".
Yes? 
I assume these are all safe to remove since no one can see these
messages anyway? 

RSSOEXDA:

I also noticed that nothing happens to the users inbox until they log
in
and 

then it appears to start the delete process. Which is why we started
this 

review due to the wonderful Hourglass and delay in launching SWBP. 

This does not help us for those who never login or don't login
regularly. 

The title of this program mentions only the Outbox. 

Are you saying that applying the note will do more that just the
Outbox?

I will review these notes. Any other tips or info you have is very
much
appreciated.

Our goal is to get Expiry Date issue working the way we assumed (and
was
told) it was to work. 

If it worked the way we thought it was to work we wouldn't be in this
predicament.

Thanks!

Rick Sample
SAP Workflow Analyst/Developer
Graybar, Inc.
11885 Lackland Rd.
63146-4208
314.573.5822
Rick.Sample at GBE.com 

>>> Bruno.Magnani at Equistarchem.com 7/12/2005 10:41 >>>

Rick,

You're not alone. I'm currently in discussion with SAP to get this
issue
addressed as well. Messages without expiration date are generated
throughout the system, which makes maintenance of SAP office a big
problem. For the moment you can use program RSSODLWF to clean up the
so-called dark folder, which contains the messages send by ao
WF-BATCH.
The program only works by year and does not consider the expiration
date
at all. See OSS note 131031 for some more info.

For users in general the expiration of messages only kicks in when the
office folder is accessed through SAP; not too many batch users visit
their outbox :-) and some/most online users do not feel that urge. You
can use program RSSOEXDA (see OSS note 431801) to address this issue.
The program has a 'workaround' for the missing expiration date; in
case
the expiration date is missing the create/change date is used instead
to
select/delete obsolete messages.

Etc, etc etc........   

Bruno Magnani  

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
Behalf
Of Rick Sample
Sent: Tuesday, July 12, 2005 7:38 AM
To: sap-wug at mit.edu 
Subject: re: Inbox messages sent by WF-BATCH with no Expiry Date.

I just got an answer back from SAP. We appear to be the only 

customer that uses this functionality. I was wondering why I never 

got any replies!

So, if no other customers use this functionality, I guess the next
question 

would be how do customers manage these SAP Inbox messages? 

Do they just let users manages their own inbox messages, or are
messages

sent to something other than SAP Inbox like MS Outlook, ?. 

At this point, I am just looking for some info so I can pass on to
management.

Thanks!

Rick Sample
SAP Workflow Analyst/Developer
Graybar, Inc.
11885 Lackland Rd.
63146-4208
314.573.5822
Rick.Sample at GBE.com 

=============================================

I applied SAP Note 591430 to get the Expiry Date added to all 

messages sent in the system. 

If a dialog user creates a message it stamps Expiry with correct date.

Problem:

Any messages from WF-BATCH are not being set with any Expiry Date so 

we have no way of auto-deleting these messages. ?

(Growing by the day and system performance issues!)

If anyone that can shed some light on this it would be greatly
appreciated.

4..6c