Application Development and Automation 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: 
Read only

Mail error - SO_OBJECT_MIME_GET exception 3

Former Member
0 Likes
700

Hi there,

We've been looking at this problem for a while now, so far not able to figure out what it is that is going wrong. Now trying my luck in the community, perhaps somewhere out there is someone who has seen this before

When we send 1 mail to a single address, it works fine.

When we send 1 mail to multiple addresses, it works fine.

When we mail multiple mails to a single address, it work fine.

So now you can guess which one gives us trouble Multiple mails to multiple addresses. The technique on its own isn't that complicated, rather old-fashioned even, but we can't get it to work. Here's what happens:

The proxy receives a flat file with data for more than 1 document, let's say just 2. For both of those documents, a mail has to be sent to 3 e-mail addresses. From the proxy, for every document a function module is being called which converts all the data into the appropriate format for sending.

The first time everything works as intended. The three mail items (for the three separate addresses) are created and put into the queue.

The second time however, the mails get status 672. We can see them in trx SOST, but they're not being sent.

When we manually put those mails into the queue, the first one is being sent correctly (status 73 afterwards). The rest receive status 829, with the following error:

"Internal error: SO_OBJECT_MIME_GET Exception: 3"

So far we've not been able to find any differences in the first or second call, all parameters are the same. Debugging is a pain, since the entire process is being called from the proxy. Simply adding a breakpoint doesn't work, we need to put and endless loop in the coding to access it through trx SM50. Since SO_OBJECT_MIME_GET is standard SAP, we can't stop the process there unfortunately.

Browsing through the online documentation and threads, people only encounter exceptions 0 and 2... have we just discovered a new species of exception for this object?

Any help is very much appreciated!

Edited by: Egbert Venema on Mar 20, 2008 1:51 PM

Hi there,

We've been looking at this problem for a while now, so far not able to figure out what it is that is going wrong. Now trying my luck in the community, perhaps somewhere out there is someone who has seen this before

When we send 1 mail to a single address, it works fine.

When we send 1 mail to multiple addresses, it works fine.

When we mail multiple mails to a single address, it work fine.

So now you can guess which one gives us trouble Multiple mails to multiple addresses. The technique on its own isn't that complicated, rather old-fashioned even, but we can't get it to work. Here's what happens:

The proxy receives a flat file with data for more than 1 document, let's say just 2. For both of those documents, a mail has to be sent to 3 e-mail addresses. From the proxy, for every document a function module is being called which converts all the data into the appropriate format for sending.

The first time everything works as intended. The three mail items (for the three separate addresses) are created and put into the queue.

The second time however, the mails get status 672. We can see them in trx SOST, but they're not being sent.

When we manually put those mails into the queue, the first one is being sent correctly (status 73 afterwards). The rest receive status 829, with the following error:

"Internal error: SO_OBJECT_MIME_GET Exception: 3"

So far we've not been able to find any differences in the first or second call, all parameters are the same. Debugging is a pain, since the entire process is being called from the proxy. Simply adding a breakpoint doesn't work, we need to put and endless loop in the coding to access it through trx SM50. Since SO_OBJECT_MIME_GET is standard SAP, we can't stop the process there unfortunately.

Browsing through the online documentation and threads, people only encounter exceptions 0 and 2... have we just discovered a new species of exception for this object?

Any help is very much appreciated!

Edited by: Egbert Venema on Mar 20, 2008 1:51 PM

3 REPLIES 3
Read only

Former Member
0 Likes
622

Hello,

I got the same problem this week.

Did you ever got this solved by any chance?

Thank you

Helena Borges

Read only

Former Member
0 Likes
622

Hello Egbert,

I had the same error in the following scenario

We run a Z program that generate a log, this log is sent to a distribution list.

For the mail functionality in the program, We use the FM SO_NEW_DOCUMENT_ATT_SEND_API1, and pass the parameters for the attachment as an u2018XLSu2019, the mail body content and then the receiver list.

We have a shared distribution list u2018CRM_LABOURu2019 for which we assign the users mail ids in tcode u2018SBWPu2019 and pass to the FM as the receiver list.

The outbound email gets error 829 in SOST after you try to re-send it (Mail error - SO_OBJECT_MIME_GET exception 3)

A pointer to solve this problem that was given to us by SAP is:

As you are using SO_NEW_DOCUMENT_ATT_SEND_API1 you should change to

SO_DOCUMENT_SEND_API1 or the BCS interface. Since release 6.10 the

FM SO_NEW_DOCUMENT_ATT_SEND_API1 should not be used.

The interface is the same. Please take a look on note 190669.

Hope it helps

Helena

Read only

Former Member
0 Likes
622

Hi Egbert,

To send notification emails from CRM program execution, we use CL_BCS (Business Communication Services) class methods to send email with attachment. I have provided the entire source code on how to do that here -

http://www.divulgesap.com/blog.php?p=NTA=

Please have a look at the above article.

Let me know if you have any issues.

Regards,

Ravikiran