Special character in File to IDoc

Hi,
am working on file to Idoc scenario.
The data is populated as expected in to the segments but when i see the idoc in the receiving system the special characters are replaced by #
For ex
how LII u201Cexceeds industry benchmarks and defeats stereotypesu201D
is cming as LII #exceeds industry benchmarks and defeats stereotypes#
Any suggestions to display the special characters.

In your File Sender channel you can set the File Encoding Scheme of your choice. We had a similar case where special characters were seen as # . Once we changed the Encoding scheme to ISO-8859-1 it worked fine.
Refer to the below link
http://help.sap.com/saphelp_nw04/helpdata/EN/e3/94007075cae04f930cc4c034e411e1/content.htm
-Mala

Similar Messages

  • Remove Special Character "/" from file name

    I'm trying to upload a PDF located on my desktop to a server that won't accept special characters, and the mac path is by default ~/desktop/file ... all those forward slashes read as "special characters" and the file is rejected. I moved the file as high as I could, out of the user folder and onto the HD, but it still contains a "/" as the initial character even there.
    How do I get rid of the "/" at the beginning of the file name? Thanks...

    You can't; every location where a file can be placed on a disk available to Mac OS X contains a / in the path. Contact the server's operators or move the file to a computer running another OS.
    (42358)

  • External Table, Handling Delimited and Special Character in file

    Hi ,
    I have created one external table with these option
    ( TYPE ORACLE_LOADER
    DEFAULT DIRECTORY ***************************************
    ACCESS PARAMETERS
    ( RECORDS DELIMITED BY NEWLINE
    SKIP 0
    FIELDS TERMINATED BY '|'
    OPTIONALLY ENCLOSED BY '"'
    MISSING FIELD VALUES ARE NULL                                          
    LOCATION
    ( 'test_feed.csv'
    Now problem is these are coming as valid.
    anupam|anupam2
    anupam"test|anupam"test2
    "anupam|test3"|test3
    anupam""""test5|test5
    anupam"|test7
    but these are not coming as valid
    "anupam"test4"|test4    --> Case when we have quotes in the filed but still have quotes in it. I guess in this case we can send the filed expect closing double quotes.
    "anupam|test6   --> In case field is starting with double quotes then it's failing
    "anupam"test8|test8"|test8 --> In case one filed contains both pipe ( |) and double quotes then we are sending it enclosed in double quotes. But thats failing the job.
    Can you suggest what is the best way to handle such scenario? ( One restriction though. The file is used by other system - Netezza as well, which can't take more than one character long delimited :'( )

    One approach is to define the external table a ONE column table (with single field on the file). This way each line will come in as a row in the external table. Of course you have to build "parsing logic" on top of that.
    DROP TABLE xtern_table;
    CREATE TABLE xtern_table
        c1 VARCHAR2(4000)
      organization external
        type ORACLE_LOADER DEFAULT directory xtern_data_dir
        ACCESS PARAMETERS (
            RECORDS DELIMITED BY NEWLINE
            FIELDS TERMINATED BY '~'   ---- <<<<<<<< Use a field terminator as a character that is not found in the file
            MISSING FIELD VALUES ARE NULL
            ( c1 CHAR(4000)
         ) location ('mycsv.csv')
    > desc xtern_table
    desc xtern_table
    Name Null Type          
    C1        VARCHAR2(4000)
    > column c1 format A40
    > select * from xtern_table
    C1                                    
    anupam|anupam2                          
    anupam"test|anupam"test2                
    "anupam|test3"|test3                    
    anupam""""test5|test5                   
    anupam"|test7                           
    "anupam"test4"|test4                    
    "anupam|test6                           
    "anupam"test8|test8"|test8              
    8 rows selected
    Ideally, it will be good t have an incoming source file with predictable format.
    Hope this helps.

  • Special letter in file name in search results

    I have follow this quid
    http://charliedigital.com/2011/12/16/force-file-name-in-sharepoint-2010-search-results/ to change XSL to display file name in search results instead of title. It works very well. I'm happy. But I find a small thing. the special character in file name (e.g.
    Ö, Ü ...) cannot be displayed correctly. But before changing those special letter can be displayed in title correctly. How can I do to solve this problem? I put following XSL:
    <xsl:otherwise>
        <a id="{concat($currentId,'_Title')}">
            <xsl:attribute
    name="href">
    <xsl:value-of  select="$url"/>
            </xsl:attribute>
            <xsl:attribute
    name="title">
    <xsl:value-of select="title"/>
            </xsl:attribute>
            <xsl:if
    test="$isdocument">
    <xsl:value-of select="filename"/>
            </xsl:if>
            <xsl:if
    test="not($isdocument)">
    <xsl:choose>
    <xsl:when test="hithighlightedproperties/HHTitle[. != '']">
    <xsl:call-template name="HitHighlighting">
    <xsl:with-param name="hh"
    select="hithighlightedproperties/HHTitle"
    />
    </xsl:call-template>
    </xsl:when>
    <xsl:otherwise>
    <xsl:value-of select="title"/>
    </xsl:otherwise>
    </xsl:choose>
            </xsl:if>
        </a>
    </xsl:otherwise>

    Hi
    I think
    that special characters are not related to
    the change in the XML file
    on your personalized results page.
    With the original XML
    special characters display correctly?
    You can use
    <?xml version="1.0" encoding="UTF-8"?>
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
    <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>
    <xsl:template match="/">
    <xmp><xsl:copy-of select="*"/></xmp>
    </xsl:template>
    </xsl:stylesheet>
    to see results with another encoding
    Miguel de Hortaleza

  • File Adapter - special character in Filename

    Hi,
    i have a question concerning file adapter.
    Scenario: we are polling files via file sender adapter (FTP).
    Problem: if the filename contains a special character, an error is thrown with 'The System cannot find the file specified'
    Scope: Special character in filename (not in payload)
    Installed: XI 3.0 SP 19 on Linux
    Questions:
    - what FTP implementation does XI use?
    - What do i have to check/upgrade to unicode?
    - is it an OS problem or an Java problem or a XI problem?
    - or is it not possible copiing files with special characters in filename?
    Thank you very much in advance.
    Michael

    Hi Michael,
    The file/FTP adapter supports both passive and active FTP data connection. You can select the data connection while configuring the adapter.
    The file/FTP adapter follows specification RFC 959. The specification can be found on the Internet under  www.ietf.org/rfc/rfc0959.txt.
    For FAQs about the file/FTP adapter, see SAP Note 821267. Please note that you'll need an account to log in on service.sap.com.
    Question: How are you specifiying the file name? i.e. Are you using placeholders, like ?, *, *.txt, etc ?
    If there's a problem with the filenames, then it should be a problem in the JAVA implementation of the adapter I assume. So you could for instance build your own adapter extension to by-pass that problem.
    Just for your information; I haven't encounter a problem with filenames in other projects.
    Good luck!

  • Need to prevent special character in generated XML file

    Hello,
    I am using E-business Suite 12.1.3 and XML version 5.6.3.
    My XML file is ending up with a special character (a Latin capital letter U with circumflex) at the end, after the final closing tag.
    Due to this the concurrent program that needs to output the XML is ending with warning.
    My XML file is produced using a PL/SQL procedure, as follows (I've simplified it):
    FND_FILE.PUT_LINE(FND_FILE.OUTPUT,'<?xml version="1.0" encoding="UTF-8" ?>');
    FND_FILE.PUT_LINE(FND_FILE.OUTPUT,'<DOCS>');
    FND_FILE.PUT_LINE(FND_FILE.OUTPUT,'<LETTER>');
    FND_FILE.PUT_LINE(FND_FILE.OUTPUT,'<EMP_NAME>Michaela Hart</EMP_NAME>');
    FND_FILE.PUT_LINE(FND_FILE.OUTPUT,'</LETTER>');
    FND_FILE.PUT_LINE(FND_FILE.OUTPUT,'</DOCS>');
    But when I run the concurrent request that creates the output then try to view the output in Internet Explorer I get the following error:
    Invalid at the top level of the document. Error processing resource 'http://servername.domain...
    </DOCS>
    If I view the source of the page in Internet Explorer it shows a square after </DOCS> indicating the special character that has been added.
    I checked this by looking at the output file in unix (cat -v o7766582.req) and it showed up the Latin U character.
    I realise it could be to do with the character set I am using. I checked what we had on the server:
    > echo $NLS_LANG
    American_America.UTF8
    I would have thought that corresponded with the XML declaration character set but I'm not sure.
    Does anyone have any other ideas about why I have this special character, and how it could be removed?
    Thanks in advance,
    Hazel

    Hi AlexAnd,
    thanks very much for your reply.
    I'm now unable to recreate the problem since dbms_xmlgen worked. If I switch back to my previous method it works fine!
    I'm not sure your suggestion would help, as there were no special characters in the data, the special character was added after the last tag I output. I hard coded the data (as in my example) for testing purposes so there was no SQL in use and the special character was still added at the end of the XML output. But I will definitely give it a try if I get the problem again.
    I had the idea that maybe I should have been using FND_FILE.PUT rather than FND_FILE.PUT_LINE but now the error is gone I can't tell if that would have solved the problem either.
    I appreciate your input.
    Regards
    Hazel

  • How to deal with special character in source file

    Hi experts,
                      i am doing a file to file scenario in which my source file contains many special characters when i am puting this file into moni its going with the special character .My source file is a fixed length file so in content conversion i have specified the file length but due to these special charcters these field lenght is also varing.So please guide me how to deal with these special characters in sender adapter
    regards,
    Saurabh

    you could try using a Java Mapping to change the encoding manually. For that, set the encoding of the OutputFormat of the XML you'll serialize. Try the following code piece for the mapping (inside a try/catch declaration):
    DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
    DocumentBuilder documentBuilder = factory.newDocumentBuilder();
    Document input = documentBuilder.parse(in);
    OutputFormat format = new OutputFormat(XML, "ISO-8859-1", false);
    XMLSerializer serializer = new XMLSerializer(out, format);
    For more details check this guide:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42

  • How to insert special character in sgm file and interprete it without isoents while opening in FM9.0

    I have an sgm file which contains special characters in different languages.
    <!DOCTYPE MANUAL PUBLIC "-//SWE-XXX//DTD XXX MANUAL-DTD 2.0//EN">
    <MANUAL LANG="CS">
    <TITEL>
    Polish characters: &oacute;&ecirc;&iquest;&ntilde;&aelig;&Ntilde;&AElig;&Ecirc;&yen;&Oacute;&pound;
    Czech characters: &eacute;&igrave;&oacute;&iuml;&aacute;&oslash;&egrave;&iacute;&ugrave;&ograve;&uacute;&Og rave;&Igrave;&Eacute;&Oacute;&Uacute;&Ugrave;&Egrave;&Oslash;&Iacute;&Aacute;&Iuml; aacute: &aacute;</TITEL>
    </MANUAL>
    Is there any way to insert special character directly in sgm file, so that it won't have to be interpreted by isoents mapping rules?
    isoent.rwr interpretes oacute as:
    entity "oacute" is fm char 0x00F3;
    But I would like to use 0x00F3 directly in fm file, so that if any additional character is needed - I won't have to update isoent files
    I've tested already:
    &#x00F3;
    &x00F3;
    &0x00F3;
    but with no luck
    Is there anyone who could help me with it?
    I will really appreciate your help
    /Joanna

    Hi Michael. Thank you for your reply.
    There is no declaration within sgm file itself - but while opening the file I use sgml application definition with the following settings:
    Default API client:  FmTranslator
    SGML character encoding:  ISO Latin1
    XML character encoding:  UTF-8
    Namespace: Enable
    CSS2 Preferences:
    Generate CSS2: Disable
    Add Fm CSS Attribute To XML: Disable
    Retain Stylesheet Information: Disable
    Entity locations
    Entity search paths
    C:\Program Files\Adobe\FrameMaker9\Structure\sgml\isoents
    So as you can see, character encoding is set to ISO Latin1 (there is no way to use UTF-8 encoding in sgml files)
    Typing ź or ć in sgm document and opening it with framemaker sgml application - I receive: ¿æ and message: "Non-SGML character found; should have been character reference"
    Everything works fine when I type f.ex.: &x016B; and insert appropriate reference lines into isolat1.rw and isolat1.ent files
    But what I would like to avoid is editing those isoent files each time new character is be needed.

  • Problem with special character in Unix file

    Hi All,
    Need a help here. We have unicoded our system recently.
    It's regarding a special character (umlaut) that comes through a 3rd party system to an Unix file. This gets displayed in AL11 file as # instead of ö.
    As our program picks the file from Unix, it also has the # but we want ö.
    We could have done some fixes in our code to fix if AL11 file at least had ö and we got # in our program.
    But it's the other way round. So, how can we get rid of this issue? Please suggest.
    Regards,
    Sanj.

    How Al11 is reading file ? Look for
    OPEN DATASET "yourfilename" IN TEXT MODE ENCODING DEFAULT FOR INPUT
                                  IGNORING CONVERSION ERRORS.
    If the above code is there .. you might need to play with different 'OPEN DATASET " options .
    Also look for Note 1174468 - Non-7bit-ASCII characters used in ABAP Workbench
                       Note 1227961 - Names of text fields with non-7-bit ASCII characters
    Good Luck !
    ^Saquib

  • Unprintable special character in RDP file

    We're having strange issue. We use RDP files generated in RDP client, we then sign those using rdpsign.exe.
    Recently after upgrading our infrastructure from W8/2012 to W8.1/2012R2 we noticed that every RDP file generated in RDC 8.1 client contains a special character on first position that is not visible in normal text editor and is only visible in hex editor.
    This character wasn't there in W8/2012. When I create the RDP file manually (typing (copy/pasting) all the options in a text file), it doesn't contain any special character, but when I later sign that file file rdpsign, it adds that character again.
    How do we get rid of it? It's preventing our provisioning system from substituting username.

    Hello MarkosP,
    Thanks for contacting Microsoft.
    These bytes are regular UTF-16 byte order marks. See here:
    http://en.wikipedia.org/wiki/Byte_order_mark#UTF-16
    If the tool you use on the RDP file does not support UTF-16, you can try to convert the file to ASCII. This will probably work for most RDP files, except if some
    string uses some unicode character not present in the ASCII character set. Here is some info (see the powershell section in the first post/question):
    http://stackoverflow.com/questions/64860/best-way-to-convert-text-files-between-character-sets​
    Best regards,
    Sophia Sun
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Special character in title property of file in KM

    Hi Friends,
    In KM, I have uploaded some german,spanish files. When I set title with special character It shows square characters. If I write unicode, I displays unicode as it is..
    So Can anybody help me in this case?

    Hi 
    Refer this link
    http://social.technet.microsoft.com/Forums/office/en-US/6e7a7eae-26fc-467f-bfdc-7c5d5ff49a95/discussion-forum-storing-special-character-in-title-differently?forum=sharepointdevelopmentlegacy
    It seems that SharePoint will allow the Title of the discussion board to remain with the special characters, but the actual URL will not be allowed and will strip them from the final URL.  SharePoint Manager easily shows this, btw.
    So, there are probably many different ways to get what you are looking for, but one way could be to have a Linq query look for all Discussion Boards on a given site and then return the Title and the DefaultViewUrl, which the latter could then be prefixed by
    the SPWeb.Url to give you something like "Testing? , /" for the title and http://mysite/Lists/Testing/AllItems.aspx (assuming
    that is the actual default view) which you could then use as the final URL for your hyperlink in your web part.
    In the code snippet below you can see the Linq query (which I assumed from your post that you need to query to find the Discussion Boards) and a simple DataTable that you could then use to populate a repeater or you just omit the DataTable and
    enumerate the results from the query yourself:
    var linqResults
    = from list in oSPWeb.Lists.Cast<SPList>() where list.BaseTemplate
    == SPListTemplateType.DiscussionBoardselect list;
    DataTable oDataTable
    = new DataTable();
    DataColumn oDataColumn_Title
    = new DataColumn("Title", typeof(string));
    oDataTable.Columns.Add(oDataColumn_Title);
    DataColumn oDataColumn_URL
    = new DataColumn("URL", typeof(string));
    oDataTable.Columns.Add(oDataColumn_URL);
    foreach (SPList oSPList in linqResults)
    DataRow oDataRow
    = oDataTable.NewRow();
    oDataRow[
    "Title"]
    = oSPList.Title.ToString();
    oDataRow[
    "URL"]
    = oSPWeb.Url + oSPList.DefaultViewUrl.ToString();
    oDataTable.Rows.Add(oDataRow);
    oDataTable.AcceptChanges();
    Please remember to click 'Mark as Answer' on the answer if it helps you

  • Special character in XML causing the file to hit worng folder.

    I am facing program, while sending a data to a repository using SOAP XML. The file path which is needed has a special character and this is not getting identified at the target.
    here is the brief descriptio.
    1) We generate the PDF using the XML report in ERP.
    2) Using the same data, we generate SOAP XML file and send to a respoitory.
    3) Here using this SOAP XML, the PDF is generated and stored in a location which is sent in the file.
    we are sending the target path as "PO's from Customer" as below:
    '&lt;target_folder_path&gt;'||'/Documents/'||TO_CHAR(SYSDATE,'YYYY')||'/PO's from Customer'||'&lt;/target_folder_path&gt;';
    The path needed is '/Documents/2012/PO's from Customer' , but due the apostrophe, the file is hit /adadmin path.
    I have tried replcaing the special character by &apos; , but still no luck. If i remove the special characters, then the file is hitting correct path.
    But the requirement is to have '/Documents/2012/PO's from Customer' .
    Is there is a way this can be achived. Please advice.

    Is it as simple as using two single quotes between PO and s?
    '/PO''s from Customer'I can't tell from what you wrote how you are generating the value in the first place so if not correct provide more details related to whatever builds the path.

  • Uploading file with special character like ( # , $ or any other special ch)

    Hi All,
    This perform statements then uploads the file from UNIX. Because of the special character in the file this  program fails.
    Please let me resulation as soon as possible .
    Thanks,
    Madhav

    Hi
    Good
    Check the below sdn post on special character.
    https://forums.sdn.sap.com/profile.jspa?userID=3649609
    Thanks
    mrutyun^

  • Special Character error in IDOC

    All,
    I am trying to upload PO data using IDOC type "PORDCR1" from LSMW. All is well till I convert data. We have some speical characters in short text field at item level and even when I convert the data and display it from LSMW it looks fine, but when I processing idoc it's erroring out meaning if I have special character "Á" in IDOC during processing it's getting converted to "Á#" and it's screwing up the positions.
    What I am not able to understand is when I am displaying the converted data in segment mode in LSMW it's getting displayed perfectly without extra "#", but when I am checking errored idoc from WE05 it has this new #. Did anyone come across this issue?
    Your help will be greatly appreciated. Thanks for your time.

    Ok, the issue was with LSMW port (which was not marked as UNICODE) and because of which it's not translating special characters....

  • When  I am uploading  file with special character it gives error

    Hi All,
      I am uplloading one file with special character then it gives error. Please let me know solutions on this is soon as possible.
    Thanks,
    Madhav

    hi are you looking for the file to be transferred with the special character then declare it wil the char field...and send it..
    or the special charactera are coming unnecessary use the command ............replace all occurances  to avoid this..

Maybe you are looking for