[LIKELY JUNK]Extended Notifications runtime
Karl Nietz
knietz at csc.com.au
Mon Feb 16 22:21:17 EST 2009
Thanks Joceyn
I checked again and could only find 1105696 and 1098805. If anyone else is
aware of others please let me know. I opened an OSS note and received
corroborating feedback to your own, (ie. too much data). The program is
attempting a sequential read of SWWLOGHIST which contains a whopping
24million records. Understandable on the first run but not on subsequent
runs using delta as the timestamps were all set to the last couple of days
so no need to read the older records.
Karl Nietz
"Dart, Jocelyn" <jocelyn.dart at sap.com>
Sent by: sap-wug-bounces at mit.edu
17/02/2009 01:13 PM
Please respond to
"SAP Workflow Users' Group" <sap-wug at mit.edu>
To
"SAP Workflow Users' Group" <sap-wug at mit.edu>
cc
Subject
RE: [LIKELY JUNK]Extended Notifications runtime
Hi Karl,
There is definitely more than one SAP Note to apply - please make sure you
look for all notes relating to the performance of SWN_SELSEN or
SWNCONFIG.
Regards,
Jocelyn
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Karl Nietz
Sent: Friday, 13 February 2009 6:20 PM
To: SAP Workflow Users' Group
Subject: [LIKELY JUNK]Extended Notifications runtime
Hi Jocelyn,
I've been investigating a number of your suggestions. I am attempting to
create notifications for leave approvals in the dev system (a backup of
prod) and when running swn_selsen/swn_selsen_test it runs forever. Last
night for 6 hours until the system went down, which is indeed long. I
have established that there are 870 leave approvals in 'Ready' status (and
1000's of 'completed' as archiving is not done in this site). Is this
number (780) likely to be deleterious? The SM50 txn seems to show the
program performing a sequential read of table SWWLOGHIST which contains
24,000,000 records(!). This makes me nervous and I asked an ABAPer to
check note 1105696. This note is applicable to SAPKB70015 but we are
running SAPKB70017 and an initial check indicated we had the changes. Is
there another note that I have overlooked? It's worth mentioning that
the program runs acceptably for a different schedule referencing a
workflow I execute via SWUI_VERIFY - for this workflow there are almost no
prior instances. Trying to manually complete 870 leave approval instances
is not going to be easy so if you have any other ideas based on this info
i would appreciate it. Thanks.
Karl Nietz
Senior Consultant
CSC Australia
Ph: 61 3 8695 1157
Mob: 61 434 181303
Please consider the environment before printing this e-mail.
CSC - This is a private message. If you are not the intended recipient,
please delete without copying and kindly advise us by e-mail of the
mistake in delivery. Note: Regardless of content, this e-mail shall not
operate to bind CSC to any order or other contract unless pursuant to
explicit written agreement or government initiative expressly permitting
the use of e-mail for such purpose - CSC Australia Pty Limited; Registered
Office: 5B/26 Talavera Road, Macquarie Park NSW 2113 Australia;
Incorporated in Australia. ACN: 008 476 944
"Dart, Jocelyn" <jocelyn.dart at sap.com>
Sent by: sap-wug-bounces at mit.edu
12/02/2009 05:42 PM
Please respond to
"SAP Workflow Users' Group" <sap-wug at mit.edu>
To
"SAP Workflow Users' Group" <sap-wug at mit.edu>
cc
Subject
RE: [LIKELY JUNK]RE: [LIKELY JUNK]]Extended Notifications SDN blog
Try SWN_SELSEN_TEST to play around with the timestamp. And apply the SAP
Notes around performance.... important!
Jocleyn
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Karl Nietz
Sent: Thursday, 12 February 2009 5:26 PM
To: SAP Workflow Users' Group
Subject: [LIKELY JUNK]RE: [LIKELY JUNK]]Extended Notifications SDN blog
Thanks, I was wondering whether that was the case. Does the program read
every record in 'Ready' status and then apply the task filter? - if so
then it will be a long slog. Is there a way to initialise the
date/timestamp so that the program starts from the current date? Otherwise
i see a similar situation when moving to prod. Thanks.
Karl Nietz
Senior Consultant
CSC Australia
Ph: 61 3 8695 1157
Mob: 61 434 181303
Please consider the environment before printing this e-mail.
CSC - This is a private message. If you are not the intended recipient,
please delete without copying and kindly advise us by e-mail of the
mistake in delivery. Note: Regardless of content, this e-mail shall not
operate to bind CSC to any order or other contract unless pursuant to
explicit written agreement or government initiative expressly permitting
the use of e-mail for such purpose - CSC Australia Pty Limited; Registered
Office: 5B/26 Talavera Road, Macquarie Park NSW 2113 Australia;
Incorporated in Australia. ACN: 008 476 944
"Dart, Jocelyn" <jocelyn.dart at sap.com>
Sent by: sap-wug-bounces at mit.edu
12/02/2009 04:46 PM
Please respond to
"SAP Workflow Users' Group" <sap-wug at mit.edu>
To
"SAP Workflow Users' Group" <sap-wug at mit.edu>
cc
Subject
RE: [LIKELY JUNK]]Extended Notifications SDN blog
Hi Karl,
If you have a lot of work items in READY status hanging around then the
first run of the program can be very long. It's even worse if most of
your users don't have email addresses yet while the system exhausts all
options trying to find an email address. Both typical scenarios in a DEV
System.
So if you can do a bit of cleansing of dead work items first.
You should also look for and apply performance notes - search
service.sap.com/notes using the term SWN_SELSEN or SWNCONFIG. Depending
on your release/support pack it's definitely worth applying some of these
as well.
Regards,
Jocelyn
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Karl Nietz
Sent: Thursday, 12 February 2009 4:36 PM
To: SAP Workflow Users' Group
Subject: [LIKELY JUNK]]Extended Notifications SDN blog
Thanks Jocelyn. This reaffirmed things well. I have query about the
Delta setting, which I presume relates to entering for items new or
changed since last run, rather than all items. Whe I config this and run
SWN_SELSEN_TEST with schedule id of xxxxxx_delta and a test case of 10 the
program runs interminably. Doesn't seem to end so I cancel it. Is this a
config error or is it because it is reading through all data in the
system? I there a way to address this?
Karl Nietz
Please consider the environment before printing this e-mail.
CSC - This is a private message. If you are not the intended recipient,
please delete without copying and kindly advise us by e-mail of the
mistake in delivery. Note: Regardless of content, this e-mail shall not
operate to bind CSC to any order or other contract unless pursuant to
explicit written agreement or government initiative expressly permitting
the use of e-mail for such purpose - CSC Australia Pty Limited; Registered
Office: 5B/26 Talavera Road, Macquarie Park NSW 2113 Australia;
Incorporated in Australia. ACN: 008 476 944
"Dart, Jocelyn" <jocelyn.dart at sap.com>
Sent by: sap-wug-bounces at mit.edu
12/02/2009 11:49 AM
Please respond to
"SAP Workflow Users' Group" <sap-wug at mit.edu>
To
"SAP Workflow Users' Group" <sap-wug at mit.edu>
cc
Subject
RE: [LIKELY JUNK]Extended Notifications SDN blog
Hi Karl ... it's not under my name...
The blog search is playing up for me today.. sigh...
Basically there are 5 steps:
1. Create a delivery schedule
2. In scenario WORKFLOW category STANDARD, create a subscription and set
up your subscription parameters.
Set the Granularity to the multiple option, set the recipient to * using
the CL_SWN_SUBSCRIPTION handler - this identifies all agents who have an
email address maintained
3. Set up schedule selection for DELTA
4. Adjust your general settings - particularly the email address
determination priorities (number them 1 to 4) - URL fragments for links
and adjust texts - texts starting NA are SE91 T100 messages, texts
starting DT are SE61 dialog texts.
5. Schedule a job for program SWN_SELSEN with WF-BATCH as the executing
user and of course matching your delivery schedule/schedule selection
time.
I usually start with a Monday to Friday - hourly during business hours
approach and keep both schedules the same until you know what you are
doing.
Hope that helps.
Regards,
Jocelyn
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Karl Nietz
Sent: Thursday, 12 February 2009 11:33 AM
To: SAP Workflow Users' Group
Subject: [LIKELY JUNK]Extended Notifications SDN blog
Hi Jocelyn,
Must admit I couldn't find your blog on SDN (I'm assuming you are the
author). I had a good look but no success. Can you please send along the
link when you get a moment. Thanks.
Karl Nietz
Senior Consultant
CSC Australia
Ph: 61 3 8695 1157
Mob: 61 434 181303
Please consider the environment before printing this e-mail.
CSC - This is a private message. If you are not the intended recipient,
please delete without copying and kindly advise us by e-mail of the
mistake in delivery. Note: Regardless of content, this e-mail shall not
operate to bind CSC to any order or other contract unless pursuant to
explicit written agreement or government initiative expressly permitting
the use of e-mail for such purpose - CSC Australia Pty Limited; Registered
Office: 5B/26 Talavera Road, Macquarie Park NSW 2113 Australia;
Incorporated in Australia. ACN: 008 476 944
"Dart, Jocelyn" <jocelyn.dart at sap.com>
Sent by: sap-wug-bounces at mit.edu
12/02/2009 09:51 AM
Please respond to
"SAP Workflow Users' Group" <sap-wug at mit.edu>
To
"SAP Workflow Users' Group" <sap-wug at mit.edu>
cc
Subject
RE: [LIKELY JUNK]Extended Notifications
Jerry - there's a blog on SDN which gives you the basics. Don't have the
link on me but you should be able to find it easily enough.
Regards,Jocelyn
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Miller, Jerry
Sent: Thursday, 12 February 2009 4:06 AM
To: sap-wug at mit.edu
Subject: [LIKELY JUNK]Extended Notifications
We are moving to ECC6 6.0 so this is my 1st attempt using Extended
Notifications.
I have it working for 1 "filter" but what do I need to do to add more
filters?
Can I add more filters for the same Subscription?
tks, Jerry_______________________________________________
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/20090217/cf3dc27e/attachment.htm
More information about the SAP-WUG
mailing list