topic Re: SO_NEW_DOCUMENT_ATT_SEND_API1 - problem after Unicode in Application Development and Automation Discussions

SO_NEW_DOCUMENT_ATT_SEND_API1 - problem after Unicode

Former Member — Thu, 16 Jun 2011 04:03:44 GMT

Hi experts, I'm using SO_NEW_DOCUMENT_ATT_SEND_API1 to create an email with an attached report. Prior to Unicode upgrade, I had no problems with the attachment. Now each line of the contents_bin atttachment wraps after 127 characters and the wrapped part is in Chinese! Each line is 242 characters long so it shouldn't wrap. Can somebody suggest what I can do to prevent both the wrapping and the change from English to Chinese from char 127 onwards.? Thanks.

Re: SO_NEW_DOCUMENT_ATT_SEND_API1 - problem after Unicode

Former Member — Thu, 16 Jun 2011 06:00:13 GMT

Hi Brigitte,

I don't know the excat reason for this issue, but why couldn't you try OO concept for sending the mail ?

I think that will be more stable.

[CL_CRM_EMAIL_DATA |http://wiki.sdn.sap.com/wiki/display/Snippets/Abap-SendingemailwithclassCL_CRM_EMAIL_DATA]

[Sending mails|http://wiki.sdn.sap.com/wiki/display/ABAP/SendingMails-HomePage#SendingMails-HomePage-Howtobuildlinesofmorethan255characters%3F]

Regards

Re: SO_NEW_DOCUMENT_ATT_SEND_API1 - problem after Unicode

Rushikesh_Yeole — Thu, 16 Jun 2011 06:42:54 GMT

it is problem due to unicode.

select the proper unicode value to support your characters ahile uploading or downloading file by mail.

use transaction SCP , you will get detailed idea about unicode selection

Re: SO_NEW_DOCUMENT_ATT_SEND_API1 - problem after Unicode

Former Member — Fri, 17 Jun 2011 00:16:36 GMT

Thanks for your responses.

Hareesh, CL_CRM_EMAIL_DATA doesn't exist on my system. Nor do many others I tried after reading other posts.

Rushikesh, I looked at SCP but am none the wiser. How do I know which to use and where do I specify it?

Re: SO_NEW_DOCUMENT_ATT_SEND_API1 - problem after Unicode

Former Member — Fri, 17 Jun 2011 03:38:55 GMT

Hi Brigitte,

As this issue happened after upgrade, try to check for SAP notes. Check and see if the below notes are valid for your release

Note 787418 - Sent documents are not readable after upgrade

Note 1430123 - Document size is not calculated correctly

Regards

Rajvansh

Re: SO_NEW_DOCUMENT_ATT_SEND_API1 - problem after Unicode

Former Member — Fri, 24 Jun 2011 04:56:13 GMT

Thanks Rajvansh, I had already looked at those notes but neither applied to my problem. I suspect that the problem is either that I should use objhex instead of objbin or that there is some setting on Unicode that is beyond my abilities (basis perhaps). I've given up and written each record over 2 lines of < 127 characters each because my user doesn't mind anyway, and its the cheaper option that spending the time to find the cause of the fault.

Re: SO_NEW_DOCUMENT_ATT_SEND_API1 - problem after Unicode

Former Member — Fri, 24 Jun 2011 06:52:53 GMT

Hi Brigitte ,

Please refer note : 190669.

As I have faced the similar issue.

The problem is with the upgradation.

And due to upgradation, the internal logic of SO_NEW_DOCUMENT_ATT_SEND_API1 has been changed.

So after referring the note : 190669.

We have referred Program : BCS_EXAMPLE_# (# indicates 1-8) and updated my program with this example.

I have referred BCS_EXAMPLE_5 to send the email notification with the attachment.

Now sending email is easier comparing with the SO_NEW_DOCUMENT_ATT_SEND_API1.

As we DONT need to use PACKING LIST in this FM and

its easy to use this example as we just need to pass required parameters like

email body, subject line, receivers,attachment body,attachment name,etc., .

Regards,

Amit Linge.

Edited by: Amit Ashok Linge on Jun 24, 2011 8:53 AM

Edited by: Amit Ashok Linge on Jun 24, 2011 8:57 AM

Re: SO_NEW_DOCUMENT_ATT_SEND_API1 - problem after Unicode

Former Member — Tue, 28 Jun 2011 04:46:25 GMT

Thanks Amit. I was hoping I wouldn't have to do so much coding but your suggestion works. Regards, Brigitte