Program RSWUWFML2 (Running for hours)

[Former Member]

Hi all, Can anybody suggest on the following issue i am facing with program RSWUWFML2.

I created a job with prog RSWUWFML2 and ran it (background mode). Its sending the mails to my ouotlook but each time i ran the job its taking way too much time (around 3 - 4 hrs) to complete. Seems may be i have not been using the correct parameters for prog RSWUWFML2. The parameter values i have been using are as follows:

Job Suffix - 2

New Work Items Only - X

One Message per Work Item - X

Work Item Execution - X

Message Class for Subject - SWU_NOTIF

Message Number for Subject - 2

Before Work Item Description - SWU_NOTIF_PROLOG1

After Work Item Description - SWU_NOTIF_EPILOG2

Errors Only – X

I would appreciate any hints on this.

thanks,

ashok

[Former Member]

this sometimes happens. We deleted the job and rescheduled it again. I dont remember what was the issue but rescheduling it solved the issue

Message was edited by:

Arghadip Kar

[Former Member]

AK, This note has nothing to do with workflow or this program. I guess you have sent this note by mistake.

thanks,

ashok

[Former Member]

Job Suffix - 2

New Work Items Only - X

One Message per Work Item - X

<b>Workflow Entry - X</b>

Message Class for Subject - SWU_NOTIF

Message Number for Subject - 2

Before Work Item Description - SWU_NOTIF_PROLOG1

After Work Item Description - SWU_NOTIF_EPILOG2

Errors Only – X

Change what is in bold. This thing works for me:))))

<b>Please reward points if useful</b>

[Former Member]

Check in Tcode SCOTand select double click on SMTP and here you can select a Time line here.

<b>Please reward points if useful</b>

Thanks

Arghadip

[Former Member]

Hi Guys, Thanks for your reply.

SCOT has been working fine but the background job i am running with program RSWUWFML2, is taking 3 to 4 hrs. So i wonder may be i am missing some of the parameters in the variant with which i am running the job.

Please let me know if you have any idea on this OR Could you let me know the parameter values that you are using for running this program in background job.

thanks,

ashok

[martin_nooteboom]

Hi Ashok,

Kathryn asked you how often the job is running, you didn't answer it. This could be part of the problem Several jobs running simultaneous and locking tables for each other.

Regards,

Martin

[Former Member]

How often did you set the background job to run? Also after RSWUWFML2 is run, all the items are just sitting there waiting for SCOT to send it. You could see the list in SOST. So you can setup a second step on the same background job, and set the time interval as you desire.

Cheers,

Kathryn

[Former Member]

Hi Kathryn, This job is running every 30 mins and now te job takes few seconds to complete. We thought this issue has been solved after we used date parameter (current date - 1) on the selection screen. But everytime the job runs its sending all the workitems (The new ones + the work items sent in the previous job runs).

The parameter values we have been using are as follows:

Job Suffix - 2

New Work Items Only - X

One Message per Work Item - X

Work Item Execution - X

Message Class for Subject - SWU_NOTIF

Message Number for Subject - 2

Before Work Item Description - SWU_NOTIF_PROLOG1

After Work Item Description - SWU_NOTIF_EPILOG2

Errors Only – X

Please let me know if you know anything on this.

thanks,

ashok

[KKilhavn]

That's odd. Your observations indicate that the table holding timestamp per job suffix is not being updated. I think that is caused by your date parameter. Alternatively, your DB table statistics for SWWIHEAD are not correct, so SAP doesn't pick the right index when it should be using the creation date and time index.

It is this timestamp table that prevents duplicate messages, and also (normally) ensures fairly quick execution. Have a look in the table, or execute the program in debug mode once to check if the timestamp table is being updated.

What's odd is that I wouldn't expect long run time except perhaps for the first execution, when no existing timestamp is found for a job suffix.

You should be able to run RSWUWFML2 quite frequently, e.g. every 12 minutes (use the same frequency as for sending mails from SAP to INT, but starting a minute or two before), without any problems.

[Former Member]

Thanks Kjetil,

The hints that you gave were helpful in solving this issue. I debugged th' RSWUWFML2 and realised the time stamp has been stored in table SWU_WLSCAN which doesn't get updated when you use a specific date or specific time or user on the selection screen.

I took out the above 3 parameters and reran the job and it started working the way we wanted.

thanks,

ashok