Language Conversion Issue in PI

Hi Experts,
The scenario is from IDoc to PI to File System. There is one particular field in the source IDoc which needs language conversion to Spanish.
Can you please guide me when the IDoc XML comes into PI how can I convert that particular field in Spanish Language and also how can I convert the whole IDoc XML content to Spanish language?
Thanks,
Arkesh

Hi Arkesh,
I think you can achive using a work around.
1. Find/write  a function module/ BAPI in SAP which can be used for language converison.
2. You can pass the text in english to the function module using RFC lookup function, which in turn will return the converted text in spanish.
I am not an ABAPer but you can ask your abaper to check and developed fxn module based on following fxn modules
SXMI_MESSAGE_TRANSLATE_INT
TERM_TRANSLATE_TEXT
HR_RU_TRANSLATE_XML
Regards,
Deepak.
Edited by: Deepak  Shah on Feb 11, 2011 12:21 PM

Similar Messages

  • Language conversion issue in PI7.1

    Hi,
    My sceanrio is file to Idoc. Am facing language conversion issues.
    For example one of the field in the source file is having the value "Différence sur net". And in the IDOC field the value is appearing as "Différence sur net".
    With the same data I have done file to file scenario with and without content conversion and the output is coming correctly as "Différence sur net".
    I have enabled Unicode check box in RFC destination also in XI server. But still its coming "Différence sur net" . Please advice how can I get the target field value same as that of the source field vale.
    Can anyone help me to sort out this issue?
    Thanks.
    Dinesh

    Hi,
    In Channel try with using the File type: text and encoding : UTF-8.
    I think this will solve your issue.
    Thank you,
    Siva

  • Language Conversion issue of HWC SUP APP

    Hello Experts
    Can any one have idea for conversion the hwc sup App from English to other language(French) which was built in SUP2.1.3?
    Thanks in advanced for your suggestion.
    Thanks
    Anil

    Have you restarted the application or device after you changed the device language to French?  The HWC will pick up the current language when it is started.  If you change the device language when the application is already launched, it is not going to pick it up until the next time it is restarted.
    The current device language is passed into your application on the query string with the lang parameter.  You can display the value of this parameter in an alert to double check the app has the language that you think should be displayed. 
    URL Parameters
    Then make sure your localized application has a Locale Properties file that matches what the device is showing for lang.
    Localizing a Hybrid App Package
    Thanks,
    Andrew.

  • Language conversion issue.

    Hi Experts,
            My scenerio is File 2 PI to R/3 . From file in one of the fields, I am sending a field with a text in KOREAN. This value is passing successfully through PI [ I can see in SXMB_MONI and IDX5] and once it reaches R/3, it simply converts KOREAN language into "####', however it is keeping the English part of teh text Intact. I see this in WE02 in the field of the segment.
        I would wish to know whats setting in R/3 do i need to do so as to keep this KOREAN text intact and NOT #####. I am sure som setting realted to language KEY will resolve this,, just dont know, where in R/3 it can be done.
    Rgards,
    Arnab.

    In the RFC destination that has been defined to transfer IDOCS to ECC,
    SM59 --> Special Options --> Charater Width in Target system as "Unicode",
    For more help refer to...
    http://help.sap.com/saphelp_nw70/helpdata/EN/65/9fb5d80f7c2e4fbc6258b66e131285/content.htm
    -SM

  • Conversion issue in encoding in PI

    Hi,
      I am having a problem in conversion issue for encoding. Let's have a detailed look into the scenario first.
    Scenario: SNC->PI (through Proxy)->MQ (through Receiver JMS adapter)->SeeBeyond (It's a middleware system).
                   Here from SNC, data are coming into PI as in UTF-8 encoding, whereas all the systems shown in the above flow are of ISO 8859_1 format. Hence UTF-8 needs to be converted into ISO 8859_1. PI does this conversion in Receiver JMS adapter. CCSID has been set to 00819 which is for ISO 8859_1 encoding. But the beginning of the xml, it remains still UTF-8, like below:-
      <?xml version="1.0" encoding="utf-8" ?>
    Whereas the content of the xml has already been converted into ISO 8859_1 by Receiver JMS adapter. Now let's see the problem now.
    Problem: After the data been passed in SeeBeyond, the mapping fails in SeeBeyond, since SeeBeyond tries to look at the XML tag from the beginning and it found it's in UTF-8 as per he tag above. Then it tries to map it in UTF-8 format whereas the content is in ISO 8859_1, so mapping fails in SeeBeyond. Please note, here allthe systems except SeeBeyond are just bypassing the data, no mapping been introduced in anywhere in the systems except SeeBeyond.
    Workaround: Is there any other chance where we can change the tag header from UTF-8 to ISO 8859_1 in Receiver JMS adapter itself in PI like this:-
    <?xml version="1.0" encoding="iso 8859_1" ?>
    This might resolve our problem I think. Any suggestions would be appreciated.
    Thanks and Regards
    Soumya

    Hi Stefan,
                Thanks for your reply. I have gone through the link you have specified. Ya, that's the other way to resolve that issue in that case. But here we have asked the receiver system (SeeBeyond) to change the encoding part in their mapping. Because changing the coding part in SeeBeyond is less time consuming than adding a new Bean in JMS adapter. Our problem got resolved by changing the mapping in Receiver end. Thanks anyway for your valuable reply.
    Thanks
    Soumya

  • Umlaut Conversion issue in Sender communication channel SAP PI

    Hi Gurus,
    We are facing issue while conversion.
    umlaut Conversion issue in Sender communication channel that is reason channel not able to pic the file from the path.
    Sender CC error:
    Value of incoming field is too large. Segment:'IMD', Field:'7008', MaxLength:'35', value:'Plssvvkbecher Lübzer 0,4 (1280Stk p' DESCRIPTION: The length of the field value is too big !
    Actually field contains 35 Chars only the value is  : 'Plssvvkbecher Lübzer 0,4 (1280Stk p'
    We tried with “ISO-8859-1” if the field value is less than 35 characters it is able to converting.
    Please help me out from this issue.
    Thank you.
    Regards,
    Jittu.

    Hi Jittu,
    Have you tried using the codepageconversion bean in the modules under the sender?  It would be like:
    AF_Modules/TextCodepageConversionBean with a parameter of Conversion.charset and a value of utf-8.
    Regards,
    Ryan Crosby

  • Description of key figure for multi language support issue.

    Hi Experts,
    Have a good day ahead!!
    Custom key figure description multi for the language support issue
    The key figure is created in English  language and description also in English.
    When I have logged in to English language and checked the report in Bex ,description of key figure is available.
    But when I log in to other language(German, Spanish Portuguese and etc) environment the description in Bex rport of key figure is showing blank
    In rsa1 in both English and other(German, Spanish Portuguese and etc)  environments key figure description is okay and correctly displaying.
    Please post me your inputs on the same.
    Thanks in advance!!
    Regards
    Priya.

    Hi Prasanth,
    This are the key figures XPRECIO: Transactional Price and XPRECLIST: Price list, its maintained in RSA1 tcode at info object level .
    These two KF descriptions are maintained in English, its working fine when I login into SAP Bex analyzer with English language and its not showing the description for the languages (German, Spanish, Portuguese and etc).
    Its need to be displayed in when login into SAP Bex analyzer with language German, Spanish, Portuguese and etc.
    Regards
    Priya

  • Problem in Chinese Language conversion

    HI ,
    I have some probelm in chinese language conversion.
    Scenario:
    1.I am trying to send the saleorder details as a mail, from the output types of sale order.
    2.The details of the related cutomer in sales order is maintained in chinese in (XD01)
    3.When I login in chinese language the mail generated is having chinesse texts as expected..But when i login in english language, the mail generates some JUNK values in place of chinese texts in SOST.
    Note: If i generate a mail by loging in English, i need the chinese text as such maintained in XD01.Please give a solution for this problem.

    Why is this a problem?  It is just a way of letting Chinese users know about a new set of discussion forums in their language.

  • Language conversion of text on buttons in application toll bar of report -

    Hello,
       Can you please let us know,
      How to convert the language(EN -> FR)  the text  for buttons in application tool bar of a report . I have tried  with SE63.  If SE63, pl let me know the navigation path ?
    Regards
    Badari

    Hi,
    This would happen in much the same way as text-elements and would be a straightforward language conversion.
    For your [reference|http://www.sapdev.co.uk/country/Lang_Conv_Issues.htm].
    May it helps you.
    Regards,
    DS.

  • Language conversion or translation is available for oracle istore

    Hello Gurus,
    I am dealing with multiple language in iStore.There all the messages that which are displaying in iStore site are the FND MESSAGES. For one language itself I am nearly using 100 FND MESSAGES like that I am going to use 5 more languages for the same site. Its really painful thing to create FND MESSAGES for each and every language. Here whats my question is
    "Any Language conversion or translation is available for oracle istore to do this?". Could anyone please help me on this.
    Please suggest me to cross this difficulty. Its really high priority.
    Thanks,
    Vinoth

    873376 wrote:
    Hello Gurus,
    I am dealing with multiple language in iStore.There all the messages that which are displaying in iStore site are the FND MESSAGES. For one language itself I am nearly using 100 FND MESSAGES like that I am going to use 5 more languages for the same site. Its really painful thing to create FND MESSAGES for each and every language. Here whats my question is
    "Any Language conversion or translation is available for oracle istore to do this?". Could anyone please help me on this.
    Please suggest me to cross this difficulty. Its really high priority.
    Thanks,
    VinothYou need to do it manually.
    Re: Internalization
    Re: translate extensions
    Thanks,
    Hussein

  • Language conversion in BI

    Hello Forum,
    The data from the data source is in Chinese format, When loading it into BI i need to convert into English and load it into BI.
    Is there any standard SAP methods or steps that we can follow for performing a language conversion.
    Thanks and  Regards,
    KK

    What do you actually want to translate?
    The text in the datasource?

  • Question on Language Conversion exit

    Does anybody know whether Language Conversion exit gets executed when sourcing data from SAP systems (R/3, CRM)?
    I am sourcing data from CRM, SPRAS(2 digit) is mapped to 0LANG(1 digit) in the transfer structure. Spanish(ES) and English(EN) for some reason is interpreted as English(E) instead of E and S.
    In T002 table I see both the entries for english (E) and spanish (S) and if the conversion exit would have applied, these two digit language code from the datasource should be converted to the corresponding one digit code.
    Can I assume that these conversion routines are executed only when sourcing data from non-sap systems.
    Please let me know your ideas.
    thanks
    George

    Conversion routine ISOLA converts the two-digit ISO language abbreviation INPUT into its SAP internal OUTPUT presentation. These are assigned using the LAISO and SPRAS fields in table T002. An INPUT that cannot be
    converted (because it is not defined as T002-LAISO) produces an error message and triggers the UNKNOWN_LANGUAGE exception.
    Because they are compatible, single-digit entries are supported in that they are transferred to OUTPUT unchanged. They are not checked against table T002.
    The difference between upper and lower case letters is irrelevant with two-digit entries however with single-digit entries, upper and lower case letters stand for different languages.
    Now I have no system availabilty...try to search in SE37 with ISOLA and then F4...
    Did you debug your transfer rules ?
    Bye,
    Roberto

  • Urgent ,Where the Smart Form once the change the language conversion??

    Hi Experts,
    I had done the language conversion (smatform thru SE63)from English to French. Once I had done the target smartform. I am trying to save and activate the same, its not asking any request number, Its just simly saved. How can we track this and  How could we know it transports the successfull

    Hi,
    Go to SE03 and choose Object Directories entries.There use the form and click f8.You will find the transport and can change the package accordinglu.
    Reward if useful.
    Thanks,
    Dishant

  • Currency conversion issue in SPM. We are getting incorrect results with SPM conversion function from one of the document currency to USD.

    Currently we are using SPM 2.0 version and we have been facing currency conversion issues.
    Please help me in following aspects.
    1) Where actually currency conversion happens in SPM. Is it the global program which does the conversion or other way.
    2) We have conversion issue for one of the currency where conversion function is giving incorrect results when converting from one of the document currency to USD. here The respective document currency is considering the 1:1 ratio with Dollar which is actually incorrect.
    3) We have verified in both BI side(currency tables) and even ECC side.
    Please help me in understanding this issue and let me know if you need more information on this.
    Its an production issue and appreciated your immediate inputs.
    Thanks
    Kiran

    Hi Arun,
    The following information may be helpful to you.The SSA_HELPER_PROGRAM has options regarding currency settings.
    EXCH_RATE_TYPE: This flag governs the exchange rate type which will be used for currency conversion in data management. For example if RSXAADMIN contains an entry EXCH_RATE_TYPE = „ZSPM‟ then the conversion type used for currency conversion is ZSPM. The default value for the exchange rate type is „M‟. More details can be found in the note 1278988.
    CURRENCYCONVERSION: By default data management converts all the measures in transaction currency to reporting currency and copies over to the corresponding measure in reporting currency. If the measure in reporting currency is already available in source it might be desirable to disable the currency conversion. To disable the conversion you can make an entry CURRENCYCONVERSION = „ „ in the table RSXAADMIN. This can also be achieved by running the program SSA_HELPER_PROGRAM with the option DEACTIVATE_CURRENCYCONVERSION. The conversion can be reactivated by running the same program with option ACTIVATE_CURRENCYCONVERSION.
    UNITCONVERSION: Similar to above. To deactivate unit conversion you can use the program with option and DEACTIVATE_UNITCONVERSION and to reactivate ACTIVATE_UNITCONVERSION. By default both the conversions are switched on
    EXTERNAL_CURRENCIES: Normally most of the international currencies are stored with two decimal places however certain currencies do have 0 and 1 decimal place too. For example JPY has 0 decimal places. SAP internal format stores even these currencies with 2 decimal places and at the time of display it changes the value to right decimal places. In case a file from external source is loaded to SPM it might have the format with 0 decimal places in the file. To convert it to SAP standard format post processing needs to be done on this value. If that is the case you can set the flat EXTERNAL_CURRENCIES = „X‟ in the table which will enable the post processing for these values. This flag can also be set and reset using the helper program using the option TURNON_EXT_CURRENCY_FORMAT and TURNOFF_EXT_CURRENCY_FORMAT.
    Kind Regards,
    John Harris
    Senior Support Engineer, SAP Active Global Support

  • Non English characters conversion issue in LSMW BAPI Inbound IDOCs

    Hi Experts,
    We have some fields in customer master LSMW data load program which can
    contain non-English characters. We are facing issues in LSMW BAPI
    method with non-English characters Conversion. LMSW steps read and
    conversion are showing the non-English characters properly with out any
    issue. While creating inbound IDOCs most of the non-English characters
    replaced with '#' and its causing issues in creating customer master data in
    system. In our scenario customer data with non-English characters in
    the first name, last name and address details. Any specific setting
    needs to be done from our side? Please suggest me to resolve this issue.
    Thanks
    Rajesh Yadla

    If your language is a unicode tehn you need to change the options  like IN SAP you need to change it to unicode  in the initial screen Customize local layout(ALT F12) options 118  --> Encoding ....

Maybe you are looking for