Problems creating mail attachment in codepage ISO-8859-1

Hi,
i'm sending emails from PI tom our customers. Some of them cannot read the attachements that are created in codepage utf-8.
Can anyone tell me how to create an attachment in codepage ISO-8859-1.
Thanky
BR
Ralf

Hi Ralf,
I create plain text files.
also
actually i´m using an own local ejb to create a nice looking html-email.
Can u please specify whether the attachment is going as a simple txt file or as HTML....
if it is a text file.. then the things are very simple.
From inbound XML,use the MessageTransformationBean,and specify the FCC(File content conversion)how u want the text file.
If it is a HTML or XML u can create the payload from the Mapping itself and send it to adapter.
But make sure that the attachment name is having .htm or .html and content_type is text/html
Babu

Similar Messages

How to set codepage iso-8859-1 in output XML?

Dear experts,
I want to create an XML file with codepage "iso-8859-1" from PI 7.11.
I have already tried to put the filetype to TEXT and ISO-8859-1 in the File Encoding field of my receiving CC (using the FTP adapter), but I still get an xml in codepage UTF-8.
It should also be possible to realise this via an XSL mapping, but where do I have to do this? Or is there any other way to use codepage ISO-8859-1?
Thanks in advance,
William

Hi
You can do this change at Visual Administrator level. There are some parameters you need to edit and add IS0-8859, so that Integration engine will set for that encode.
So, you can ask the Basis guys to perform this.
This would certainly works out for you.
Regards
Pothana

How to determine codepage ISO-8859-1 for my output XML?

Dear experts,
I want to create an XML file with codepage "iso-8859-1" from PI 7.11.
I have already tried to put the filetype to TEXT and ISO-8859-1 in the File Encoding field of my receiving CC (using the FTP adapter), but I still get an xml in codepage UTF-8.
It should also be possible to realise this via an XSL mapping, but where do I have to do this? Or is there any other way to use codepage ISO-8859-1?
Thanks in advance,
William

Hi William,
Write a simple XSLT mapping to change the value of the attribute "encoding" to "ISO-8859-1" in the output XML of message mapping . Include this XSLT map as the second mapping step in your interface mapping.
First step in your interface mapping will be your already existing message mapping.
Here is the XSL code !
<?xml version='1.0'?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method='xml' encoding='ISO-8859-1' />
<xsl:template match="/">
<xsl:copy-of select="*" />
</xsl:template>
</xsl:stylesheet>
Hope you can solve now ...if not pls let us know !
cheers,
Ram.

Codepage Conversionerror UTF-8 from System-Codepage to Codepage iso-8859-1

Hello,
we have on SAP PI 7.1 the problem that we can't process a IDOC to Plain HTTP.
The channel throws "Codepage Conversionerror UTF-8 from System-Codepage to Codepage iso-8859-1".
The IDOC is 25 MB. Does anybody have a idea how we can find out what is wrong with the IDOC?
Thanks in advance.

In java strings are always unicode i.e. utf16. Its the byte arrays that are encoded. So use the following codeString iso,utf,temp = "�� ";
byte b8859[] = temp.getBytes("ISO-8859-1");
byte butf8= temp.getBytes("utf8");
try{
iso = new String(b8859,"ISO-8859-1");
utf = new String(butf8,"UTF-8");
System.out.println("ISO-8859-1:"+iso);
System.out.println("UTF-8:"+utf);
System.out.println("UTF to ISO-8859-1:"+new String(utf.getBytes("iso8859_1"),"ISO-8859-1"));
System.out.println(utf);
System.out.println(iso);
}catch(Exception e){ }Also keep in mind that DOS window doesnot support international characters so write it to a file

Mail receiving attachments in ISO-8859-1 format

I have this weird issue on my brand new Macbook Air. I have google apps and some of the emails attachments I receive seems to be in a ISO-8859-1 format and the extension is changed on mail.
In gmail webmail, the attachments is in the correct format.
Example : Éte_2010.docx become ISO-8891-1?Q?te...docx?=
See the dropbox link for more examples :
https://www.dropbox.com/s/cjnr3gbm4cr06u1/encoding.png
It seems to do this only on attachment with special characters and from certains users (not all my incoming emails do this). The first attachment is always in the good format, if there is more than one attachments, the others seems to change format.
I switched from a 2010 MacBook Pro and mail wasn't doing this.
Thanks!

Hi Jean-Philippe,
Yes, please check my first post, if you use same settings, and create message as mine, it should work, the TestFile is created as an attachment.
Include this line in the module configuration with transform key:
Transform.ContentType: multipart/mixed; boundary=--AaZz;
If you still have issues, please give me a description of the error.
Regards,
Ivan.

Problems with reading XML files with ISO-8859-1 encoding

Hi!
I try to read a RSS file. The script below works with XML files with UTF-8 encoding but not ISO-8859-1. How to fix so it work with booth?
Here's the code:
import java.io.File;
import javax.xml.parsers.*;
import org.w3c.dom.*;
import java.net.*;
* @author gustav
public class RSSDocument {
    /** Creates a new instance of RSSDocument */
    public RSSDocument(String inurl) {
        String url = new String(inurl);
        try{
            DocumentBuilder builder = DocumentBuilderFactory.newInstance().newDocumentBuilder();
            Document doc = builder.parse(url);
            NodeList nodes = doc.getElementsByTagName("item");
            for (int i = 0; i < nodes.getLength(); i++) {
                Element element = (Element) nodes.item(i);
                NodeList title = element.getElementsByTagName("title");
                Element line = (Element) title.item(0);
                System.out.println("Title: " + getCharacterDataFromElement(line));
                NodeList des = element.getElementsByTagName("description");
                line = (Element) des.item(0);
                System.out.println("Des: " + getCharacterDataFromElement(line));
        } catch (Exception e) {
            e.printStackTrace();
    public String getCharacterDataFromElement(Element e) {
        Node child = e.getFirstChild();
        if (child instanceof CharacterData) {
            CharacterData cd = (CharacterData) child;
            return cd.getData();
        return "?";
}And here's the error message:
org.xml.sax.SAXParseException: Teckenkonverteringsfel: "Malformed UTF-8 char -- is an XML encoding declaration missing?" (radnumret kan vara f�r l�gt).
    at org.apache.crimson.parser.InputEntity.fatal(InputEntity.java:1100)
    at org.apache.crimson.parser.InputEntity.fillbuf(InputEntity.java:1072)
    at org.apache.crimson.parser.InputEntity.isXmlDeclOrTextDeclPrefix(InputEntity.java:914)
    at org.apache.crimson.parser.Parser2.maybeXmlDecl(Parser2.java:1183)
    at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:653)
    at org.apache.crimson.parser.Parser2.parse(Parser2.java:337)
    at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448)
    at org.apache.crimson.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:185)
    at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:124)
    at getrss.RSSDocument.<init>(RSSDocument.java:25)
    at getrss.Main.main(Main.java:25)

I read files from the web, but there is a XML tag
with the encoding attribute in the RSS file.If you are quite sure that you have an encoding attribute set to ISO-8859-1 then I expect that your RSS file has non-ISO-8859-1 character though I thought all bytes -128 to 127 were valid ISO-8859-1 characters!
Many years ago I had a problem with an XML file with invalid characters. I wrote a simple filter (using FilterInputStream) that made sure that all the byes it processed were ASCII. My problem turned out to be characters with value zero which the Microsoft XML parser failed to process. It put the parser in an infinite loop!
In the filter, as each byte is read you could write out the Hex value. That way you should be able to find the offending character(s).

New Line Character problem in mail attachment

Hi all,
my xi-box is in patch level 16. i need to send the mapped xml as a pipe delimited file(a lineitem per line) attachment to a mail id. so i use MTB to content convert the payload and attach the content as an attachment using a custom module and send the mail. Since the naming convention of the attachment (as per my requirement) says the file should be a .txt file, i 've used text/plain as the content-type.
if i open the attachment in textpad or wordpad i can see one lineitem per line; but if i open it with notepad its not the case.lineitems do not appear in separate lines but appear continuously. i 'm seeing a box character as a separator between the lineitems. i'm not able to figure it out why.
i used MTB in file adapter and content converted the payload and opened the file in notepad;it was fine.
But i'm not able to figure out why its happening with the mail attachment. If you have come across such a problem please suggest me to solve this.
Regards,
Sundararamaprasad

Is there any way you can send the file in an ASCII format instead of BINARY format. In many of my resolved cases I just change from binary to ascii and it works for eg., while doing FTP.
thansk,
rakesh

Problem about mail attachment

Hi all:
    I use FM 'SO_NEW_DOCUMENT_ATT_SEND_API1' to create a html attachment,it contains some Chinese words.
    The issue is after I export the attachment from Business Workplace ,I found the Chinese words is disordered. I mean the exported file do not contain any Chinese words.
    Is there anybody can help me to sole the problem?
    Regards

Thanks for your reply,I think I don't explain it clearlly.
In SAP GUI,the attachment shows the Chinese word correctlly,but in PC-UI ,it has the problem.
I suppose the problem is about the codepage,but I've no idea how to solve it.

Problem creating mailing list with Server Console

Hi,
when I create a new mailing list, I do the following:
1. Right click on groups folder in Console
2. Choose New->Group
3. Entering all data and checking "Mail Account" under Account
The documentation sais, that a Mail-tab should now appear. But this is not the case for me!?
I can only create the group like this and have to add the attribute "mail" - to enter an email address - manually..
Is this normal? Am I doing something wrong or missing something? Also disallowing posting on this group can only be set manually. Shouldnt all this be done using a nice GUI dialog?
I'm using Directory Server 5.2 Patch 2. Also tried 5.2 Patch 4. Both same problem.
Thanks in advance
david

got the instructions from the "Sun Java System Messaging Server 6 2005Q4 Administration Guide", chapter "Managing Mail Users and Mailing Lists with the Console Interface"-"Managing Mailing Lists":
http://docs.sun.com/app/docs/doc/819-2650/6n4u4du0e?q=messaging+server&s=t&a=view
Step 6 sais: "Click the Mail Account box. -> The Mail tab becomes visible in the Create Group window."
Thanks,
--David

Problem in Mail Attachment

Hi,
I am developing one program there i have to send the report output as mail in XLS format.Everything working fine but the output all lines i am getting in only one line. Here i am using SO_DOCUMENT_SEND_API1 - FM
please, give your inputs .
Points will be awarded for valid inputs
Regards,
Nandha.

http://www.sapdevelopment.co.uk/reporting/rep_spooltopdf.htm

Problem with Mail attachement

Hi ,
Currently landscape is updated to Unicode,
i'm getting blankspace after each character in the attachemnt.
i have tested the same program on diffrent servers which is working properly.
is this the unicode issue or help me out how to resolve the problem.

Hi Avinash,
Check entry of File type in table TSOTD.
Blank spaces after each character may be because of file type missing in table.
Refer a sample code to update file type table TSOTD .
After updating the file type try agaiin. Hope it solves ur issue.
SELECTION-SCREEN BEGIN OF BLOCK b WITH FRAME TITLE text-001.
PARAMETERS : p_file   TYPE so_obj_tp OBLIGATORY,
             p_desc   TYPE so_tp_des.
SELECTION-SCREEN END OF BLOCK b.
START-OF-SELECTION.
DATA: wa_tsotd TYPE tsotd,
        wa_tsott TYPE tsott.
*-- File Type
wa_tsotd-objtp = p_file.
wa_tsotd-deflt = 'X'.
*-- File Type Description
wa_tsott-langu = 'E'.
wa_tsott-objtp = p_file.
wa_tsott-tpdes = p_desc.
*-- Update File type and Description
MODIFY tsott FROM wa_tsott.
COMMIT WORK.
MODIFY tsotd FROM wa_tsotd.
COMMIT WORK.
CLEAR: wa_tsotd,wa_tsott.
Reward points if this helps.
Manish

Mail Receiver - Send file in ISO-8859-1 encoding

Hi,
I'm sending mail with an attachment using mail adapter, but instead of specified ISO-8859-1 it is converted to UTF-8 no BOM,. Because of that, some characters (ñ,ç, etc) are not transferred properly.
Settings:
Message protocol: XIPAYLOAD
No mail package.
Transform.ContentType: multipart/mixed; boundary=--AaZz; charset=ISO-8859-1
Payload:
multipart/mixed; boundary=AaZz; charset=ISO-8859-1</Content_Type><Content>--AaZz
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
File attachment
AaZz
Content-Type: text/plain; charset= ISO-8859-1
Content-Disposition: attachment; filename=TestFile
iso-8859 characters ñ ç ñ ñ
AaZz--
</Content></ns:Mail>
I need advice in how to force the file to be created with ISO-8859-1 enconding.
Thanks in advance.
Regards,
Iván.

Hi Jean-Philippe,
Yes, please check my first post, if you use same settings, and create message as mine, it should work, the TestFile is created as an attachment.
Include this line in the module configuration with transform key:
Transform.ContentType: multipart/mixed; boundary=--AaZz;
If you still have issues, please give me a description of the error.
Regards,
Ivan.

Nerving Problem with UTF-8 and ISO-8859-1

Hi,
I´m looking for a solution to serve this problem for many hours now, maybe someone can help me:
1.) We need to send our Mails with the ISO-8859-1-Charset because otherwise Windows-Users get the text in the message twice: once as plain, and after a question mark formated. So I changed the NSPreferredMailCharset in the com.apple.mail.plist to ISO-8859-1:
defaults write com.apple.mail NSPreferredMailCharset "ISO-8859-1"
2.) So far so good. It works until I add an attachment to a message. Adding an attachment forces the sending of the mail again as Unicode (UTF-8). I could change the encoding manual, but thats not the way we can work in our company.
My question is: is there any way to force mail to encode as ISO-8859-1? It can´t be that we have to change the encoding for every message.
Thanks a lot
florian
PS: I´m not sure if this is important: we use the osx in German.

I was thinking that since he is from Austria & references a company, there is a very strong possibility that the character "€" (the Euro currency symbol, Unicode 20AC, UTF-8 E2 82 AC) would frequently appear in messages.
Even if he sets a preference for ISO-8859-1 as the default with Terminal, or manually changes messages to ISO-8859-1, it would not be possible to include this symbol in such messages, since there is no "€" in ISO-8859-1.
Similar problems would occur with other symbols sometimes used in business (for example "™"), in engineering ("Ω"), in mathematics ("∑"), or even with some general punctuation marks such as the dagger ("†").
Other possible problems are the use of other currency symbols the Euro replaced (the franc's "₣" or the lira's "₤") or others still in use (the Israeli new sheqel's "₪ or rupee's "₨"). Ligatures in an international environment would really complicate things as well, as this Wikipedia article about the Œthel illustrates.
Note that in none of these cases would the presence or absence of an attachment matter -- ISO-8859-1 simply isn't up to the task.
I suspect that in some cases, if it is possible, setting the default to Windows-1252 (Windows Latin 1 in Mail's list?) would help, since it does include at least the Euro & dagger. I haven't played around with this much, but I do note that in a new message window containing "€" in the body, if I set the text encoding to Windows Latin 1, Automatic, or UTF-8, Mail doesn't complain, but if I set it to ISO Latin 1, I get an error saying the message can't be saved & an "Invalid Text Encoding" alert if I try to send it.
As for how messages are received at the other end, Windows apps (not just Outlook) are notorious for continuing to use non-Unicode API's even after the OS itself has long since moved to Unicode as its internal standard. Some of them employ bass-ackwards fixes like deciding ISO-8859-1 declarations are supposed to be Windows-1252 ones. Worse, Windows itself sometimes seems to interpret a few Windows-1252 code positions as their ISO-8859-1 control equivalents!
All this makes life that much more complicated for people trying to avoid problems like the above.

Mail attachement content trnsfer encoding 8bit , 7bit

Good morning to everybody.
I have a problem reading mail attachement.
When the attachement is 8bit encoded the exadecimal char "3D" is write in a file as "0D". This is wrong
When the attachement is 7bit encoded the exadecimal char "3D" is write in a file as "3D" . Thi is right
Is there anyone who knows why of this beaviour?
Many thanks

I'm using the msgshow.java that is the example included in the java mail library.
Attachement downloaded with JavaMail (the bad one):
�� 3D ==> 0D (CR)
2007-05-15;18.11.26;978;000469,00;380;Italy
;LUISA SPAGNOLI NAPOLI IT;34009575;8036527 ;5651;00;
Attachement downloaded with outlook (the good one):
�� 3D not translated
2007-05-15;18.11.26;978;000469,00;380;Italy =
;LUISA SPAGNOLI NAPOLI IT;34009575;8036527 ;5651;00;
Here the properties of the mail message:
Microsoft Mail Internet Headers Version 2.0
Received: from EXSMTP-IN2.sede.corp.sanpaoloimi.com ([10.244.7.21]) by EVS01.sede.corp.sanpaoloimi.com with Microsoft SMTPSVC(6.0.3790.2499);
     Mon, 28 May 2007 08:09:14 +0200
Received: from secgw-b-e02.intesabci.it ([172.19.0.27]) by EXSMTP-IN2.sede.corp.sanpaoloimi.com with Microsoft SMTPSVC(6.0.3790.2499);
     Mon, 28 May 2007 08:09:13 +0200
Received: MHUBINT
Received: FW
Received: from mail1.ssb.it ([192.106.129.13])
     by mailbox.intesabci.it with SMTP id l4S696n5006757
     for <[email protected]>; Mon, 28 May 2007 08:09:09 +0200
Received: (qmail 11377 invoked by uid 509); 28 May 2007 06:02:04 -0000
Received: from 127.0.0.1 by Imhotep (envelope-from <[email protected]>, uid 501) with qmail-scanner-2.01
(spamassassin: 3.1.3.
Clear:RC:1(127.0.0.1):.
Processed in 0.078893 secs); 28 May 2007 06:02:04 -0000
     Mon, 28 May 2007 08:02:03 +0200 (CEST)
     (Postfix) with SMTP id 6798F34257;Mon, 28 May 2007 08:02:03 +0200 (CEST)
to: <[email protected]>,
from: <[email protected]>
subject: 28 May 2007 08:00 PS12 FROD-ATM1
MIME-Version: 1.0
Content-Type: multipart/mixed;
     boundary="P=_NextPart_000_01BD3BAF.A762FD80"
Date: Mon, 28 May 07 08:00:27 B
Message-Id: <[email protected]>
Return-Path: [email protected]
X-OriginalArrivalTime: 28 May 2007 06:09:13.0674 (UTC) FILETIME=[B707A2A0:01C7A0EE]
--P=_NextPart_000_01BD3BAF.A762FD80
CONTENT-TYPE: TEXT/PLAIN; CHARSET="US-ASCII"
Content-Transfer-Encoding: 8bit
--P=_NextPart_000_01BD3BAF.A762FD80
Content-Type: text/plain; charset=us-ascii; name="SPIMI.TXT"
Content-Disposition: attachment
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mailbox.intesabci.it id l4S696n5006757
--P=_NextPart_000_01BD3BAF.A762FD80
CONTENT-TYPE: TEXT/PLAIN; CHARSET="US-ASCII"
Content-Transfer-Encoding: 8bit �� I think the problem is here
P=_NextPart_000_01BD3BAF.A762FD80

Mail adapter module UTF-8 to ISO-8859-1 conversion

Hi!
I've a problem with a mail attachment which is generated by an adapter module for the mail adapter. The content type is set to "Application/EDIFACT; charset=iso-8859-1" when I add the attachment, but the mail adapter ignores the charset-setting.
Therefore german "umlauts" like ü are displayed in a wrong way: Ã¼
When I set the content, I transform it in ISO-8859-1 : attachment.setContent(edifactString.getBytes("ISO-8859-1"),"ISO-8859-1");
When I test the result of edifactString.getBytes("ISO-8859-1"), I get the String in the right character encoding, but the mail adapter seems to "fix" the encoding
I also tried to use the messageTransformBean, but it doesn't worked.
Anyone knows how to solve this issue?
Best regards,
Daniel

Hi all!
I found a solution for this problem: First I used the TextPayload-Object for the Attachment which should be added. It seems that the TextPayload-Object has some bugs handling different encodings (handels only Unicode and deletes the charset=... setting from the ContentType).
When using the Payload object for the attachment (which handles binary data), there is no conversion to Unicode, so I get my attachment as desired (but still without the charset-setting).
Best regards,
Daniel

Problems creating mail attachment in codepage ISO-8859-1

Similar Messages

Maybe you are looking for