Issue with Chinese characters while sending IDOCs from PI to SAP system

Hi,
We are working on File to IDOC scenario where in some of the fields are having Chinese characters. In SAP system, we noticed that the Chinese characters are getting replaced with # where as in PI output payload we are able to see the correct Chinese characters. The systems involved are PI 7.4 and SAP ECC -6.0.

Like in dual stack where we have an option to choose unicode/ non-unicode, i don't see any option in single stack.
However not sure if it works but you can give a try..
I assume you have created the RFC destination in NWA.
Go to RFC destination ->Specific Data -> Advanced Settings - here we have an option to mention the code page.
You might want to mention the code page for chinese char and see if it helps..
Before doing this, do checkMark's suggestion.

Similar Messages

How to send IDocs from a non-SAP system to a SAP system

Hi everyone i am new to SAP R/3 System.
Currently i am required to send IDocs from a non-SAP system to a SAP R/3 System.
There is a guide on Cost-Effective and Quick Communication between SAP and 3rd Party Systems using IDOC HTTP XML Interface. But its from a SAP system to a non-SAP system and i am able to do that.
Is there any step by step guide where they teaches you how to send IDocs from a non-SAP system to SAP system via similar method?
Thank You!

Hi,
I hope this link may help you......
http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r1/index.jsp?topic=/com.ibm.swg.im.iis.ds.entpak.sapr3.use.doc/topics/c_pack_r3_Introduction.html

Problem with chinese characters while sending mail with .CSV attachment

Hi,
i am sendin .CSV file as an attachment with mail using "SO_DOCUMENT_SEND_API1" FM,
whle opening the mail attachment the chinese characters are not displaying properly.
currently i am using ECC 5.0
can any body help in this regard.
Thanks,
Rahim

Hi Kang Ring,
please convert the content of the attachement into the binary format and then add it as a mail attachment.
LOOP AT i_data ASSIGNING <wa_data>.
if s_output is INITIAL.
CONCATENATE <wa_data> cl_abap_char_utilities=>cr_lf into s_output.
else.
CONCATENATE s_output <wa_data> INTO s_output SEPARATED BY cl_abap_char_utilities=>cr_lf.
endif.
ENDLOOP.
CALL FUNCTION 'SCMS_STRING_TO_XSTRING'
EXPORTING
text = s_output
IMPORTING
buffer = x_output.
CALL FUNCTION 'SCMS_XSTRING_TO_BINARY'
EXPORTING
buffer = x_output
TABLES
binary_tab = imail_att.
     OR
please use ABAP-Object classes like CL_BCS , CL_document_BCS.....
please findthe below sample code.
cl_bcs_convert=>string_to_solix(
          EXPORTING
            iv_string   = s_output
            iv_codepage = '4103'          "suitable for MS Excel, leave empty
            iv_add_bom = 'X'               "for other doc types
          IMPORTING
            et_solix = s_output_binary "(of type solix_tab)
            ev_size   = size ).
attachment->add_attachment(                       "attachment of type ref to cl_document_bcs
          i_attachment_type    = 'xls'
          i_attachment_subject = l_subject
          i_attachment_size    = size
          i_att_content_hex    = s_output_binary ).
you need to write the code for adding the receipents, subject and adding this "attachment " as an attachment to the mail.
Hope this will helps to you....,
thanks,
Rahim.

GUI Download Issue with Chinese characters

Hello,
Currently we are upgrading from 4.7 to ECC. I'm using GUI_DOWNLOAD
function module to download the data from SAP to desktop. I do have an
issue with Chinese characters while downloading the file from SAP to ECC.
In 4.7 the Chinese characters are being downloaded (I haven't used any
code page) perfectly, but where as in ECC the downloaded file has junk
characters instead of Chinese.
Is there any change in the GUI_UPLOAD FM.
For your reference below is the code present in the program
CALL METHOD CL_GUI_FRONTEND_SERVICES=>GUI_DOWNLOAD
    EXPORTING
      FILENAME             = Z_FILENAME
*****DCDK900543 - Begin of fixing for Unicode conversion ****
     FILETYPE             = 'WK1'
      FILETYPE             = 'ASC'
      WRITE_FIELD_SEPARATOR = ABAP_TRUE
*****DCDK900543 - End of fixing for Unicode conversion ****
    CHANGING
      DATA_TAB             = I_TAB_TMP
    EXCEPTIONS
      FILE_WRITE_ERROR     = 1
      NO_BATCH             = 2
      INVALID_TYPE         = 3
      UNKNOWN_ERROR        = 4
      OTHERS               = 5.
Regards,
Bharath.

Hi bharat,
please check whether you ecc 6.0 is uni coded or not (as you upgraded).
If it is not uni coded then you will not be able to print the Chinese characters.
You can see whether it is uni coded or not by the following
in your app toolbar under system click on status.
There you can see whether your ecc6.0 is uni coded or not.
Regards,
koolspy.

Issue in sending IDOC from BODS to SAP

I am getting issue while sending IDOC from BODS to SAP.
Job is getting failed with error : "No authorization to send Idoc with message type CREMAS"
I have checked last authorization in SU53 and it is Successful !!
What would be reason because of which job is getting failed with Authorization error?

Go to sm58-->Select IDOC_INBOUND_ASYNCHRONOUS this function module, in menu mar select edit--> execute LUW.
or take help from sap basis team, can you please check user in the source system have authorizations profile. 'S_BI-WX_RFC' for this u can refer sap note :150315.
if you need more information refer this document:
How to check a BW - SAP source system connection - SAP NetWeaver Business Warehouse - SCN Wiki

How to send IDOC from nonSAP to SAP

Hi ;
I need to send IDOC from nonSAP to SAP. I have experience it with XI and BC..but now I need sending IDOC to SAP directl without these tools..
Can you explain it via sample? (I know already how to create port , define LP from we20,we21 ).
Firstly Do I need to create a RFC destination ? and I want to send IDOC as XML by HTML post method..Which port must I send?
Must this port point to this RFC?
Thanks.

Hi,
Here you have to generate an IDOC and convert into XML format and put at required server
third party will accept the IDOC XML not the IDOC.
Just check with ur third party in which format the data is accepted.
if its IDOC XML then u can use the file receiver adapter and place the IDOC XML file on 3rd party folder.
You use the IDoc adapter to have IDocs (intermediate documents) processed by the Integration Engine. IDocs from SAP systems Release 3.1x or higher are supported. You can also use the IDoc adapter to connect non-SAP systems to the Integration Engine.
The IDoc adapter converts the IDocs to IDoc XML format so that they can be processed by the Integration Server pipeline.
You can also transfer XML in IDoc format received from the Integration Server to connected systems. The Integration Server pipeline must convert the received XML to IDoc XML, and then transfer this IDoc XML to the IDoc adapter. The IDoc adapter converts the IDoc XML to native IDoc format and sends the IDoc to the identified receiver system using the standard IDoc interface.
Regards,
Shamma

Error while sending data from XI to BI System

Hello Friends,
I m facing an error while sending data from XI to BI. XI is successfully recived data from FTP.
Given error i faced out in communication channel monitoring:-
Receiver channel 'POSDMLog_Receiver' for party '', service 'Busys_POSDM'
Error can not instantiate RfcPool caused by:
com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=10.1.45.35 SYSNR=01 GWHOST=10.1.45.35 GWSERV=sapgw01 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner '10.1.45.35:sapgw01' not reached
TIME Fri Apr 16 08:15:18 2010
RELEASE 700
COMPONENT NI (network interface)
VERSION 38
RC -10
MODULE nixxi.cpp
LINE 2823
DETAIL NiPConnect2
SYSTEM CALL connect
ERRNO 10061
ERRNO TEXT WSAECONNREFUSED: Connection refused
COUNTER 2
Error displaying in message monitoring:-
Exception caught by adapter framework: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=10.1.45.35 SYSNR=01 GWHOST=10.1.45.35 GWSERV=sapgw01 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.1.45.35:sapgw01' not reached TIME Fri Apr 16 08:15:18 2010 RELEASE 70
Delivery of the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=10.1.45.35 SYSNR=01 GWHOST=10.1.45.35 GWSERV=sapgw01 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.1.45.35:sapgw01' not reached TIME.
Kindly suggest me & provide details of error.
Regards,
Narendra

Hi Narendra,
Message is clearly showing that your system is not reachable
102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=10.1.45.35 SYSNR=01 GWHOST=10.1.45.35 GWSERV=sapgw01 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.1.45.35:sapgw01' not reached
Please check to ping the BI server IP 10.1.45.35 from your XI server , in case its working you can check telnet to SAP standard port like 3201/3601/3301/3901 etc.
It seems to be connectivity issue only.
Make sure your both the systems are up and running.
Revert back after checking above stuff.
Regards,
Gagan Deep Kaushal

Send IDOC from XMII to SAP

Hi All,
I want to send an IDOC from xMII to SAP. Can anyone suggest me the steps and how to configure in SAP and xMII.
thanks
Manoja

Hi,
What ever Dipankar Saha said is correct.
SAP xMII is used for the purpose of connecting ERP and shop floor.
Usually from R/3 system, you can get info in the form of idoc.(through other forms also you can get data. I hope that you have got the data through idoc)
From shop floor, you get data in the form of B2MML.
If you want some data back to ERP, you can use JCO interface present in the
business logic editor. Use this, to find correct BAPI which can push some data into ERP.
Link the data from B2MML field to BAPI field.
Save this transaction and call this where you want.
Hope this may help you...
Regards,
P.S.Kishore kumar

Is it possible to receive IDOCs from a non-SAP system?

Hi,
I'm facing a problem where I have to configure SAP MII (12.0) to receive IDOCs from a non-SAP client. Is it possible? I'm dealing with a system named Hydra (developed by MPDV) and I'd like to know what I should configure in Hydra systems in fields like: PROGID, GWHOST, GWSERV, SYSNR, CLIENT etc.
Anyone can help me?
Thanks a lot in advance

Unless Hydra emulates ECC sending IDOCS, then you just might want to use the WSMessageListener (http://help.sap.com/saphelp_xmii120/helpdata/en/45/6a86ac88130dece10000000a11466f/frameset.htm) and configure your message processing rules accordingly.

Issues with Chinese characters via HTTPRequest

We have the below scenario:
http --> PI --> IDOC
Before the message arrives to PI we do the conection with the below code:
String urlString = WDConfiguration.getConfiguration("local/AIB_PAD").getStringEntry("HTTPURL");
     java.net.URL url = new java.net.URL(urlString);
     HttpURLConnection connection = (HttpURLConnection)url.openConnection();
     connection.setDoInput(true);
     connection.setDoOutput(true);
     connection.setUseCaches(true);
     connection.setRequestMethod("POST");
     connection.connect(); //(http connection is made)
this conection transform all chinese characters to "?"
Does anybody knows what is missing to receive the chinese characters to PI correctly?
Thanks.
Edited by: Israel Toledo on Sep 29, 2011 1:27 AM

Hi Mark,
Thanks for your answer.
We are sure that both systems support chinese characters, because when we see the outbound XML generated on the source system(JAVA SAP Portal) it looks good. Also, when we send an XML to PI via HTTP client using Java script, it works good.
The issue is when we make the connection to PI. I thing some parameter is missing. could be the text code (UTF, unicode), but we are not sure how to change that in the Java code.

Discoverer Desktop 10g : Issue with Chinese Characters

Hi ,
Discoverer Desktop 10g client is having issue in displaying Chinese data. My report has chinese characters in it and the same does not get displayed properly when run from Discoverer desktop. However, when I export the report in html format and opened it in browser, it is displaying the chinese characters properly. Browser was set to Unicode(UTF-8) character set.
I tried changing to different fonts in Discoverer Desktop, but couldn't get the chinese character issue resolved in Desktop.
Could someone , please tell me how to fix this issue ?
Please mail directly to [email protected]
Thanks
Venkatesh

I am facing the same issue too. I think it is a problem with the fonts. Get back to you later if I find any solutions.

Issue with Czech characters in PDFs generated from RSTXPDFT4

Hi,
We have a requirement to generate PDF documents from the spool of the Billing document outputs in our project.
For this we are using the standard program RSTXPDFT4, which converts the SAP script OTF to PDF format.
But the Czech characters in the billing document output are not getting displayed in the PDF generated out of it.
We are already using a device type I2HP4 when creating the print request , which supports Latin-2 Character set ( ISO 8859-2 ), to which the special characters
of East European languages belong.
Even then , the czech characters are not getting displayed in the PDF generated.
We have raised a message to SAP for this, and SAP informed us that currently the only solution to this is to use Latin 2 soft fonts,
and to upload these soft fonts into R/3 System using report RSTXPDF2 as they contain the Eastern European special characters plus all the other characters in ISO 8859-2.
But, since character font definitions (font files) are protected by copyrights, SAP informed us that they cannot provide these font files and we have to acquire
these latin-2 font files by searching in search engines in the internet.
If anyone has the information where we can get these "Adobe type 1 Latin-2" font files with '.PFB' extension, for the proper display of Czech characters, please let me know.

Hi,
Did you or anyone manage to find a reasonable solution for this issue?
I'm currently facing something similar but with Polish characters instead.
I tried using RSTXPDF2 to upload .PFB and .TTF files but to no avail.

Label printing issue with chinese characters (SAP script)

Hi ,
I have a requirement to print chinese characters on label print out.
Here are the steps already tried:
1) Created a new device type which is copy if ASCIIPRI and character set 8400
2) Font ANDALE_S, CNHEI, CNSONG are assigned to device type, same fonts called in SAP script.
3) During the print, it is picking ANDALE_S font(observed in spool RAW data), but preview is good.
4) I put ZPL codes CW1,B:MSUNG.FNTFS in beginning of script and also ^A@N,50,50,B:MSUNG.FNT while prining actual chinese text in SAP script.
5) also tried other device types assigned to printer LZEBU2, LB_ZEB2 etc.,
6) already checked at printer DIMM level, SIMSUN, ANDALE_S fonts are already installed
7) Character set on printer is same as in SAP
So far no option worked, it default to Courier fonts while printing and it results garbage characters.
If anyone has ideas, please advice.
thank you,
Anil

Hi,,
If the ZPL commands are correct for switching to the printer's internal CHinese font and character set, it may work to add the fonts via SE73 -> Printer Fonts -> ASCIIPRI . In here you need to add the commands in the print control SFxxx for your created font.
Another possibility is to print via windows and device type CNSAPWIN. Here it should not be necessary to add any font.
Regards,
Aidan

UNICODE Issue With Chinese Characters

Dear Experts,
I have chinese characters in my data. I want to downlaod this data on front end as ANSI file type and the chinese data should be convertable.
Am able to download using 4120 unicode in gui-downalod. but am not getting fiel format of ANSI if I have chinese characters in my file.
Please hep me.
Thanks in Advance.
Kiran.

Hi
You can get the code page of a language using function module NLS_GET_FRONTEND_CP.
Import parameters               Value
LANGU                          CH
FETYPE                          MS
Export parameters               Value
FRONTEND_CODEPAGE               1160
Then pass the code to you program and try.
Shiva

Sending IDoc from TIBCO to SAP

Hi,
request is to send IDoc type PURCONTRACT_CREATE01 from TIBCO to SAP.
After sending the data from Tibco there is nothing received in SAP although TIBCO adapter says successfully created.
But no entry in BD87 (IDoc monitor), no entry in SM48 (tRFC queue) on SAP side.
How can I recognize what went wrong - on TIBCO or SAP side?
Shouldn't there be an entry in IDoc monitor at least although content of sender or receiver data or IDoc would be wrong that was sent by TIBCO?
Has the TIBCO adapter to do a kind of commit ?
Help is highly appreciated.
thx.
Achim

Hi,
Configure the appropriate message type for the partner in the outbound parameter of the partner profile (WE20) . Afterwards reprocess your failed idoc using the program RBDAGAIN
Try Posting the Idoc with the help of WE19 instead of using your report
Status 29 indicates that the Partner Profile is not configured correctly.
As you know the target logical system is nothing but the partner, select that and click on Outbound Parameters and add the message type.
Status 30 indicates that the Idoc has been generated successfully.
Status 03 indicates that the Idoc has been reached Middleware.
Try running the standard program RSEOUT00.
All the Idocs in 30 statuses will change to 03.
To get all the IDOC's in status '03'
after MASTER_IDOC_DISTRIBUTE
Call FM "EDI_DOCUMENT_DEQUEUE_LATER"
Regards,
Shamma

Issue with Chinese characters while sending IDOCs from PI to SAP system

Similar Messages

Maybe you are looking for