Problem with function module SO_NEW_DOCUMENT_SEND_API1

[Former Member]

Hello All,

I have a program that sends an email using the function module SO_NEW_DOCUMENT_SEND_API1. It works well in the DEV system however when it was moved to QA system, I am no longer able to send out an email. I tried debugging my program and it works fine. I also tried testing the standard function module in SE37. I was able to send an email from this test in the DEV system both on a distribution list and a single internet email address. I replicated the same testing for the standard function module SO_NEW_DOCUMENT_SEND_API1 in the QA system and I didn't receive again any emails.

Can someone give light to this problem? I'd appreciate it very much. Thanks!

Regards,

Kristine

[Former Member]

Check if the messages are actually there using transaction SCOT. If you look through the options there, you can figure out what status they are in.

Usually all external mails and other output messages such as faxes are sent out in batch scheduled as a background job using program RSCONN01. If this is not scheduled, then you need to manually run this program to send your messages.

Hope this helps,

Srinivas

[Former Member]

Hi Srinivas,

Thanks, the transaction SCOT helped. It seems like all the internet emails are in the 'Waiting' column in transaction SCOT. What does this mean? I tried running the program that you mentioned, RSCONN01, and it actually reduced the value under the 'Waiting' column however, when I checked on my internet mails I still haven't received anything.

Regards,

Kristine

[andreas_mann3]

Hi Kristine,

i think mail-service is'nt customized on your QA-system

-> look this web logs:

1) /people/thomas.jung3/blog/2004/09/08/sending-e-mail-from-abap--version-610-and-higher--bcs-interface

2)/people/thomas.jung3/blog/2004/09/07/sending-e-mail-from-abap--version-46d-and-lower--api-interface

regards Andreas

[Former Member]

Hi Kristine,

try also transaction SOST for monitoring the emails sent out. There you should be able to track down the successfully sent and erroneous messages. You can get there also from SCOT (can't exactly remember where from..).

-Mikko

[MariaJooRocha]

Hi,

If there are no errors on the log (SOST), maybe you can put a commit work?

This works for me with a similar situation, but with FM

SO_OBJECT_SEND.

Regards,

Maria João Rocha

[Former Member]

Christine,

Is the user in your QAC environment setup correctly? The e-mail address of the user that is running the program and sending the e-mail must have their e-mail address set up. This can be done in transaction SU01.

Bruce

[Former Member]

Hi Maria João Rocha! I rewarded you some points.

Actually, 4.7 version requires adding the parameter COMMIT_WORK when using the function module SO_NEW_DOCUMENT_SEND_API1 to ensure that the mail is sent. I just got this from a colleague.

Thanks!