Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Background job to monitor email in wait status -

Former Member
0 Kudos

Transaction SOST or program RSSOSOSTSTAT display status of external email.

I have a print program that will email to customer when the billing document is created. However we do not send email immediately, I set up to send at 10am on the next business day from the billing creation date. For example if we bill on Friday, it will be sent at 10am on on Monday. If Monday is a holiday, it will be sent on Wednesday instead.

The reason is that if something is wrong, we will retrieve the email in the queue so that it will not send to customers.

And sometimes we send the email to multiple recipients.

The user wants me to write a report to monitor the email in wait status with information such as document title, recipient email address, emai l subject.

The program RSSOSTAT can provide that but it is not a batch program and the user does not have authorization for SOST.

Is there a batch program running in background similar to RSSOSTAT? From SOOD I can get the specific email subject which is the invoice number to be sent and SOSC is the table show entries to be connected to SAP communication and SAP Connect.

Thanks,

4 REPLIES 4

Former Member
0 Kudos

Hi

You can send Email immediately by executing the Tcode SCOT. Else you can define time in your program after that email is automatically sent.

Regards

Ajit

0 Kudos

My question is that is there any report to monitor email in the queue? Normally in production environment, we do not have permission for SOST but I want to write report of emails sitting in the queue.

We set up email to send invoice to customers with future date and time and user wants to know the email list in case something wrong, they will be able to retrieve the email before sending to customers.

0 Kudos

Akinosora,

You could create a transaction variant for transaction SOST, deactivating all the different screen actions that you do not want the user to perform. Then you could create a variant transaction that calls SOST using the transaction variant you created previously. Then you would have to give the user access to this new variant transaction.

Look at:

http://wiki.sdn.sap.com/wiki/display/Snippets/TransactionVariant-AStepbyStepGuidefor+Creation

Bruce

Edited by: Bruce Tjosvold on Dec 12, 2011 5:18 PM

0 Kudos

Bruce,

Thanks, I will try that.