List of Special Characters in SAP

Hello All,
Can anyone help me with a list of special characters that can be accepted by SAP ?
Issue: Ariba(An Interface) has various special characters and they send files to GIF(An Interface). GIF takes those special characters and then generates idocs.. but when sending data to sap.. sap is not able to recognise some characters ..
Appreciate your help.. Thanks.
Regards,
Pranay

SAP reads "!" as space since R2 days.

Similar Messages

  • How to print Special Characters in Sap-Scripts

    How to print Special Characters in Sap-Scripts
    Thanks,
    Ravi

    Hi
    if u want print special characters we can use hot codes i.e '  '  (single inverted commas). in between these hot codes insert u r special characters.
    write    '    !@#$%^&*( )  '.
    for the above write statement output is
    output is   !@#$%^&*( )

  • Need to add special characters in sap scripts

    Hi All,
       I need to add special characters in sap script.
    I have used them as it is my script,but in the print preview i am able to see '#' instead of those special characters.Can anybody please tell me the way in which we can add special characters in the scripts.
    eg. 'Shlesha' i.e. name in inverted colons.
    Thanks

    Hi
    If # is coming means, that is the problem with the printer. I think u might have used your local printer to see the print preview.
    Don't use LOCL or LP01. Our local printer won't recognize those characters.
    Just change the printer name to client printer name. It will work.

  • Issue with special characters in SAP CRM ICSS application.

    Hi ,
    I have issue with the special character in CRM web application.
    1. In CRM IC Webclient application(5.0) . i am copying and pasting some special characters in the description of the service request document. then this is saving the character as it is.
    But when i am opening the same service request in SAP CRM  ICSS(Internet Customer Self-Service) application, then the special characters are converting to different characters.
    I am not sure whether this is the right forum for this or not.
    Can anyone please suggest how can i correct this. Or is there any standard solution to handle the special characters in ICSS.
    Thanks
    Sudhansu

    misunderstood =/
    Original (Coming - output):  "<PAY_TXT>PAYκ Contact your bank or financial institution to make this payment from your cheque, savings, debit or transaction account.</PAY_TXT>"
    it's in output but what is data in database ?
    sorry but without knowing about source data for forming the xml i haven't ideas about your problem
    in db it's "TM " or "™" or ... ?
    Original (Coming - output):  "<PAY_TXT>PAYκ Contact your bank or financial institution to make this payment from your cheque, savings, debit or transaction account.</PAY_TXT>"
    Something like XAE or "K" after PAY Value in the xml tag and continued the text value.  (Tag value is not getting copied exactly here - i am sorry for that )
    that's ok. i need to see the problem not the data as is
    Expected (output):  "Here it needs to produce the "PAY TM" (Here "TM" should be super scripted to "PAY" Value in tag).
    as super scripted in xml?
    as idea - you can have <PAY_TXT>PAY TM</PAY_TXT> and in publisher set TM as super
    Designing XSL Subtemplates - 11g Release 1 (11.1.1)

  • Special Characters in SAP R/3 System

    Hi All,
    I need some help to handle the below situation.
    I need some help in XI. Below is the message from SXMB_MONI
    This is FILE to BAPI UPLOAD Scenario. The bolded characters above have special characters (First letter of the Bolded part).
    The values are getting uploaded in BAPI but when I check in R/3 system, I can see the values as Guss-Achsbr####, Bremsbelag-Verschlei########
    Edited by: Srinivasa Babu Mutyala on Aug 14, 2008 11:06 AM

    Hi,
    please have a look at this thread:
    special character
    Regards
    Patrick

  • Unable to print special characters in SAP script.

    Hi,
      There is an address which needs to be hardcoded in a SAP Script form.
    It looks like:
    Česká republika s.r.o
    Karla Engliu0161e 3219/4
    Česká republika
    IČO:  25635972
    The letters which has got a tilde and sign above them are appearing as a hash '#' in print. I have tried uploading it as an image and as standard text. But still not working. Can someone help please?
    Thanks in advance,
    Anita

    Hi Anita,
    Please search in SDN,, similar issues were answered before many times...
    Regards,
    Aditya

  • How doI find a special character not listed in 'Special Characters?'

    Hi There
    I am trying to type the letter a with both a macron and an acute. I can find the o equivalent, but that's not helping me to write laudatis correctly!!
    Thank you
    Eve
    P.S.  I have tried going into system settings and looking for international (as I saw something somewhere else!) - I can't see international either!

    Esme The Rat wrote:
    I had the UK one switched on as well.. it appears that needs to be switched off
    You just need to select the right keyboard in the "flag" menu.
    Here is a picture to show you the box to check for Show Input Menu in Menu Bar, plus a picture of the "flag" menu where you select which keyboard you want to use.

  • SSRS and data from SharePoint lists - special characters in HTML

    Hi All,
    This may not actually fit into this forum, but here goes anyway...
    We're using SSRS to report on data stored in Project Server workspaces (so SharePoint lists). Prior to upgrading to 2013, we could pull this data in and set the "Placeholder properties" of the text box to interpret HTML tags as styles and it would
    format everything as it appeared in the SharePoint list. Now that we have upgraded to 2013, this works with a few notable exceptions - some special characters are rendered as their escaped/encoded (whatever the term is) - so a colon which is within the text
    field in SharePoint, rather than appearing in the SSRS report as ":" appears as "&#58;".
    These are multiline, rich text formatted columns in the SharePoint list. Using =Replace(Fields!Description.Value,"&#58;",":") in the report makes the appropriate replacement, but given that this occurs with a handful of other special
    characters as well, this solution becomes very unruley very quickly. Has anyone else encountered this, or does anyone have any other suggestions for a work around?
    If not now, when?

    Facing same issue but having no solution, please suggest..

  • Write Special Characters in PDF file from SAP Script

    Hi there,
    Need a quick help...
    We are converting SAP Script to PDF using the function module CONVERT_OTF
    and saving the file on presentation server using GUI_DOWNLOAD...
    But in certain cases where the item text is maintained with some special
    characters like @#$% u03B1 u03B2 u03B3 u03B4 ®... then, some of these characters are seen
    as junk/garbage characters...
    how do we handle this??
    P.S. Our Forms are already using Korean Font...
    Any help is highly appreciated
    Kind Regards,
    Tanuja

    Hi,
    Use the FM  CONVERT_OTF to get the Binary data and  down load it as PDF .
    sample
    */ Convert the OTF data into PDF.
        call function 'CONVERT_OTF'
         exporting
           format                      = 'PDF'
         importing
           bin_filesize                = lv_bin_filesize
            bin_file                   = lv_xstring
          tables
            otf                        = lt_otf_data-otfdata[]
            lines                      = lt_pdf_data
         exceptions
           err_max_linewidth           = 1
           err_format                  = 2
           err_conv_not_possible       = 3
           err_bad_otf                 = 4
           others                      = 5  .
    */ Convert the Xstring data into PDF
        call method cl_document_bcs=>xstring_to_solix
          exporting
            ip_xstring = lv_xstring
          receiving
            rt_solix   = lt_mess_att .
    Then down load the table lt_mess_att  with extension PDF.
    Edited by: UmaMaheswaraRao Surapaneni on Apr 1, 2009 5:44 PM

  • Sending special characters to non-unicode non-sap system: user exit

    Hello All,
    We are sending data from a SAP unicode system to a non-sap non-unicode system via IDOC. The idoc is standard idoc GLMAST which contains gl account information.
    Some text fields contained in this idoc can contain special Polish characters. If they are sent unchanged to the non-unicode system, they give problems in the destination system.
    What we would like to do is to build a user exit to convert these special characters, for example : 'é' becomes 'e', ....
    We used enhancement object ALE00001, function EXIT_SAPLBD11_001 and implemented it, but it seems this exit is not called. Can this user exit be used for this functionality?
    We also tried to change in SM59 the type of system of the destination to non-unicode, so that SAP replaces those special characters by #. But, than the error 02. Codepage not found is given in the idoc. Note: the link to the external system is not set up yet, so no actual connection is possible. Is this why we receive this error, and will this functionality work in the end with a non-sap system?
    Thanks for helping.
    Kind Regards,
    Bart Pelsmaekers

    I faced this problem in many project i implement below logic.
      DATA: c_splchar(2) VALUE '90',
            c_defaultchar(1) type c VALUE '#'.
    You have to move one by one character to this function module
              CALL FUNCTION 'URL_ASCII_CODE_GET'
                   EXPORTING
                        trans_char = spl_char
                   IMPORTING
                        char_code  = spl_code.
    All non unicode(Better you check) are always greater than 90.
             if spl_code is gt c_splchar.
                move c_defaultchar to c_splchar.
             endif.       
    "Reward points if usefull"
    Thanks,
    Narayan

  • ELM -  Special characters in List Management

    I have the following two questions which are very important for business, can anyone let us know the simplest way we can workaround the following issues:
    1.     Special charaters to take care using UTF-8 format csv or txt files
    2.     Everytime correction to the file is done it cannot be uploaded or corrected to the server file for existing Lists, a   new one needs to be created instead.
    Details are below:
    Point 1:
    When we try liading special characters like in the word München it is replaced with M#nchen in the application after loading.
    I think we can solve this by selecting the UTF-8 type of the csv file, has anyone done this/tried this, pls provide details.
    Point 2:
    In this case when a list is created & loaded and errors are encountered due to data we would like to correct the file and re-load without having to create a new list again.
    Is there a possibility to correct the file and re-load it or upload it once more so that the corrected data is then available for the List to be loaded.
    Please let us know the simplesrt workaround. Or let us know if we are not doing this right.
    Thanks
    Regads
    Rahul

    Hi Priyanka,
    Thanks for the answer, I will test point 1 but for point 2 I tried the steps for example I created a new List & selected
    Read data
    Map data
    The rest I left unchecked, I started th eload, it gave an error in step 2 i.e Map data.
    Now I should be able to correct the file locally & re-load it and repeat the step, but I cannot select th eupdated/corrected file again, nor can I check the flag for Map data?
    Is this standard functionality or needs to be customized.
    I would expect I should be able to select the corrected file & load it to the server to re-run th eList load, isnt this what you described in point2?
    Thanks
    Regards
    Rahul

  • Can I change the Password Policy Special Characters list?

    I would like to add the UK Pound sign ‘£’ to the list of characters IDM uses for ‘special characters’ in its password policy checks.
    Is this possible?
    Regards,
    Gavin

    It should be possible but it might be be possible from the GUI. I did a quick search in my IDM development environment and found two objects that might be of use to you.
    First was the UserUIConfig Configuration object. I have a feeling that is a hold-over from IDM 7.1 so it might not be applicable but within it is this:
        <PolicySpecialChars>
          <String>~!@#$%^&*()_+=-`{}[]|\:";'<>,.?/</String>
        </PolicySpecialChars>
    {code}
    The second thing I found was the "Alpha Numeric Rules" rule library, also a Configuration object.  It has a rule called "SpecialCharacters" and "hasSpecial" that might be of use to you.
    I haven't tried changing either of those objects myself.  Let us know how it goes!                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • Dir listing with umlauts / special characters

    I've got a directory tree, where several files have umlauts or french accented characters in their names.
    When I do 'ls' in such a directory, I can see the umlauts fine in Terminal, e.g.:
    Die rote Wüste - Michelangelo Antonioni.avi
    Nazarin - Luis Buñuel (span, eng sub, 1959).avi
    I've got the environment variable LC_CTYPE=UTF-8.
    However, when I do this: 'ls > /tmp/f.txt'
    and then open the text file in TextEditor, I get this:
    Die rote WuÃàste - Michelangelo Antonioni.avi
    Nazarin - Luis BunÃÉuel (span, eng sub, 1959).avi
    Does anyone have an idea, how to fix this?
    (BTW: I've got a similar problem when I rsync these files ...)
    Thanks a lot in advance.
    Best regards,
    Gabriel.

    Well, I've been using /Applications/TextEdit for these files, because I was assuming that it handles UTF-8 automatically.
    I opened the files now with Vim (my favorite editor), and, lo and behold, all special characters are fine!
    I think, that solves my problem, because I can even copy-and-paste the text from Vim into my notes.
    Best regards,
    Gabriel.

  • Printing Turkish Characters in SAP Script Form

    Hi I want to print a Form where I need to Print Turkish characters from Database. Its Print Preview is coming absolutely right but there is some problem while printing. I shows # symbol in places of Turkish Characters. I have checked the printer and drivers and they are absolutely fine. Printer is printing other documents in Turkish Language but not the form. System has Turkish fonts installed. Kindly help. Thanks in advance.

    Hi
    See this OSS note for your problem
    OSS Note: 776507
    Symptom
    Documents printed via SAPscript or SmartForms do not print with correct special characters, e.g. ### prints instead of Japanese or Russian characters. What to do?
    Other terms
    SAPscript, SmartForms, printing, device types, OTF
    Reason and Prerequisites
    Help required to choose proper fonts in a SAPscript or SmartForm
    Solution
    When using SAPscript or SmartForms to print (or email or fax) a form from a business application, many factors influence the outcome of the actual text within the form. All these factors must be checked in order to ensure a correct printout:
    1) The language version of the form used to produce the printout.
    Example: If you want to print a French invoice, you need to have a FR version of your SAPscript or SmartForms invoice form RVINVOICE01. And the application program must specify the corresponding language key (FR) when calling the SAPscript or SmartForms API.
    2) The font selections specified in the form (possibly also in a SAPscript style or SmartStyle used in a form).
    Example: In a SAPscript form or a SmartStyle you need to specify HELVE if you want to print German text in Helvetica (or similar) font. If you want to print Japanese text, HELVE is not a valid choice but you need to specify a Japanese font like JPMINCHO in your Japanese form.
    3) The output character set of the device type
    Every printer in transaction SPAD has a "device type" assigned. Device types used by the spooler for printing support only one single specific output character set. All text from the form has to be converted (using SAP's built-in character conversion mechanism) to this output character set.
    A character set can typically support either a single language (e.g. Shift-JIS which supports only Japanese) or a set of languages (e.g. ISO 8859-1, which supports Western-European languages). It is possible that a given language (such as German) can be supported by several output character sets, e.g. you may use either ISO 8895-1 (Latin-1) or ISO 8859-2 (Latin-2) to represent German text. This is so because both character sets contain the special characters used in German.
    Example: HPLJ4000 is a HP LaserJet device type supporting the ISO 8859-1 (Latin-1) character set. ISO 8859-1 can be used to represent e.g. Dutch, English, French, German, Spanish, Swedish but NOT Russian or Japanese.
    As a consequence, it is ok to use HPLJ4000 to print English, German French etc. but not for Japanese or Russian.
    4) The set of available printer fonts for a given device type
    When formatting a document, SAPscript and SmartForms perform an automatic mapping of the font definitions in the form (e.g. "HELVE 14 point bold") and the available printer fonts of the device type. A replacement printer font is chosen, should the specified font selection not be available in the device type. Now this replacement can be problematic if a language-specific font, such as Chinese CNSONG, is specified in a form and it gets replaced by a font which does not support this language, e.g. COURIER.
    To solve this problem, font families in SE73 have language attribute assigned, e.g. some fonts are characterized as being suitable only for certain languages. And when a replacement has to be chosen because the original font from the form is not available in the device type, a replacement font is chosen which has the same language attributes.
    If no fonts for the language in question exist in the device type, the resulting font will not be able to print the special characters and you will see "wrong" output characters in the printout.
    Note on SAPscript/SmartForms Print Preview:
    The OTF Print Preview available in Windows GUI (e.g. from transaction SP01) will sometimes not show the "wrong" characters which appear on the final printout. Here is the reason: since the Print Preview runs in Windows environment, it will use Windows fonts to represent the actual printer fonts. A Windows font typically has more available characters (i.e. covers more character sets) than are actually available in a printer's resident font.
    A typical example where the Print Preview will differ from the printout is here: if you have a Chinese PCL5 printer such as CNHPLJ4 and use the Western Latin font COURIER in your document, the print preview will show you Chinese characters if you (by accident) tried to format Chinese characters in COURIER font. This is because Windows will automatically choose a font that can output Chinese characters (which is actually not Courier). But when you print the job on an actual PCL5 printer with resident Western and Chinese fonts, the Courier font will not print any Chinese characters but Western special characters instead, because the printer's resident Courier font does not include Chinese characters.
    Rule of thumb: all Asian device types (e.g. CNHPLJ4, JPHPLJ4, JPPOST, KPHPLJ4) support not only Asian fonts but also COURIER, HELVE and TIMES fonts. But these Latin fonts can only be used to print English text, not Chinese/Japanese/Korean characters.
    Which fonts are suitable for a given language?
    Language(s):            Font family to use in a form:
    Latin-1 (Western Europe/Americas) *******
    DE,EN,FR,ES,NL,SV       COURIER, HELVE, TIMES
                            (LETGOTH, LNPRINT)
    Latin-2 (Central Europe) ****************
    PL, CZ                  COURIER, HELVE, TIMES
    ISO 8859-4 (Baltic) *********************
    ET, LT, LV              COURIER, HELVE, TIMES
    ISO 8859-5 (Cyrillic) *******************
    BG, RU, SR, UK          COURCYR, HELVCYR, TIMECYR
    ISO 8859-7 (Greek) **********************
    EL                      COUR_I7, HELV_I7, TIME_I7
    ISO 8859-8 (Hebrew) *********************
    HE                      COURIER, HELVE, TIMES
    ISO 8859-9 (Turkish) ********************
    TR                      COURIER, HELVE, TIMES
    Simplified Chinese **********************
    ZH                      CNHEI, CNKAI, CNSONG
    Japanese ********************************
    JA                      JPMINCHO, DBMINCHO, DBGOTHIC
    Korean **********************************
    KP                      KPBATANG, KPDODUM, KPGULIM
                            KPGUNGSE, KPSAMMUL
    Traditional Chinese *********************
    ZF                      TWDPHEI, TWMING, TWSONG
    Thai ************************************
    TH                      THANGSAN, THDRAFT, THVIJIT
    Arabic (Unicode systems only) ***********
    AR                      ANDALE_J
    Verify your output by examining the OTF data
    When analysing printing problems of this type, be sure to check the OTF data which gets produced by SAPscript or SmartForms. OTF or "Output Text Format" is the intermediate page-description format generated from SAPscript or SmartForms. OTF will contain the final printer font names and character set/language identifiers which help to solve the problem. OTF will even name the form and the language of the form used to create the output.
    The easiest way to do this is to create a spool request from your application, run transaction SP01, use menu
    Goto->Display Requests->Settings
    and choose
    Display Mode: Raw
    Now display your spool request. If this is a SAPscript or SmartForms spool request, you will see OTF data. Each line represents one OTF command, every command starts with a 2-character cmd identifier and possibly some cmd parameters follow.
    Here is an excerpt from a sample OTF file where we highlight the most interesting commands:
    //XHPLJ8000    0700 00000000001
    IN04EALEXTEST_ZEBRA
    IN05%PAGE1
    OPDINA4  P 144  240 1683811906000010000100001
    IN06%WINDOW2
    MT0024401289
    CP11000000E
    FCHELVE  120  00109XSF100SF101110000067E X
    UL +0000000000000
    SW00067
    CT00000000
    ST0453037Dieses SF hat Stil ALEXTEST_ZEBRA mit
    The 1st line with the // (Control) command reveals the device type usedto print: HPLJ8000
    //XHPLJ8000    0700 00000000001
    The 2nd line (IN = Info command) shows the name and (internal 1-char)language key of the form:
    IN04EALEXTEST_ZEBRA
    In this case it is the English (E = EN) SmartForm ALEXTEST_ZEBRA
    The OP-line (OP = Open Page) gives the page format used in the form, it is DINA4 Portrait orientation:
    OPDINA4  P 144  240 1683811906000010000100001
    The CP (CodePage) cmd shows the SAP system codepage used to code the text and the active language. In our case it is codepage 1100 and language E = EN = English.
    CP11000000E
    Finally, the FC-cmd (Font Call) lists a printer font selected within SmartForms. Please note that every SmartForm has a designated default SmartStyle under "Form Attributes->Output Options". In addition, every text node can have a SmartStyle attached (which will override the definitions from the default style for the text). In our case the resulting printer font that was selected is HELVE 12.0 pt bold-off, italic-off.
    FCHELVE   120  00109XSF100SF101110000067E X
    Header Data
    Release Status: Released for Customer
    Released on: 22.08.2005  09:57:20
    Priority: Recommendations/additional info
    Category: Customizing
    Primary Component: BC-CCM-PRN Print and Output Management
    Secondary Components: BC-SRV-SCR SAPscript
    BC-SRV-SSF Smart Forms
    <b>
    Reward points for useful Answers</b>
    Regards
    Anji

  • Special characters in XI

    Hi,
    Does anybody have the list of characters not supported by XI? I am using XI 7.0
    I am specifically looking for Special Characters which come in the payload and are seen in SXMB_MONI.
    Thanks
    Mateen.

    Hi,
    XI supports Unicode compatibility also so I don't think there will be any list but go through below link to deal with some special characters in PI 7.0
    Refer
    How To…Work with Character Encodings in Process Integration
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42
    Thanks
    Swarup
    Edited by: Swarup Sawant on Feb 29, 2008 12:51 PM

Maybe you are looking for