Could not find code page for receiving system error

[Former Member]

Hi all,

my interface is IDOC to file , , i have done everything in IR and ID, and in WE20 partner profile the idoc i am using in the IDOC which is ORDERS05, but i am not able to see anything in message in monitor, when i check the IDOC status i am getting the error Could not find code page for receiving system

and can i trigger manually my IDOC for testing purpose, plase help me in this

Edited by: sridhar loganathan on Jan 14, 2009 7:28 AM

[dharamveer_gaur2]

Hi

Have you Created RFC Destination for this IDoc?

[dharamveer_gaur2]

Hi

Check your RFC Destination setting and also check Unicode is selected in RFC Destination.

look with similar thread.

[Former Member]

i have logged int o SM59, while checking test it is giving me some other error, casue the IODC was used for some other purpose for VB.DOT purpose , now i am using for XI purpose , i am not able to poroceed please help me

[former_member208856]

Hi,

You have given the entry in WE20 for Partner Profile as Outbound for this IDOC.

Check the RFC Destination in SM59, type "3" (ABAP Connection),

from ECC to XI System, if you have this RFC Destination, check the same or contact to BASIS Team to create the same for ECC to XI.

Now, check the settings in XI :

First, check the entry of Port in tcode - IDX1.

now import the IDOC matadata in tcode - IDX2 for this idoc in created Port.

Sandeep

[Former Member]

I didnt create any RFC , casue there was already a IDOC to FIle , so thought not needed , and one more thing , IDX2 for adding IDOC TYPE , what is that source port , what should i give ,

and for every new IDOC interface should i create a new RFC

Thnaking you

[Former Member]

Hi,

For each interface you don't need to create the RFC destination.

One thing I need to ask,

Your previous interfacae is using the same Sender R/3 system details only?

Then you can add the Idoc in the partner profie. Already port is added in your previous interface.

delete the metadata dn reload the metadata in IDX2.

Check the RFC destination by testing the Remote logon.

If it is ok then trigger the Idoc from WE19 and test it.

Let me know if any error you get.

Regards

Goli Sridhar

[Former Member]

yes i am suing the same R/3 details only, only the IDOC is different , in the IDX2 , already the IDOC which is running , should i delete , i am afraid that it will affect the previous interface which is running

[Former Member]

Hi Sridhar,

You can trigger the Idoc from the R/3 system by using the WE19 testing tool.

Then you can find the Idoc in the XI system by using the WE05 tr code.

you can monitor the message in SXMB_MONI tr code whether it is processed successfully or not.

Check the SM58 if you are getting any error information.

Regards

Goli Sridhar

[Former Member]

Hi thanks you , first of all , i have just added in WE20, just the IDOC name and not done anyoher chnages , dont know how to check the RFC connection for this IDOC , i thought it will be there already casue we where using one more interface which is rinning for another IDOC , is it we muct do any changes there aslo

please help me

Thnaking you

[former_member184619]

Hi Sridhar,

Just cross check your setting with this blog:

/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi

Sachin