File to IDOC : Code page error

[Former Member]

Hi

I am working on Scenario File to IDOC.

T90CLNT90 is the rfcdest for SAP R3 System from XI.

The file sender succesfully sends thefile to the XI Engine.From XI to R3 the adapter fails to send the idoc.

What could be the reason for code page error?

I am getting following eror.

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Call Adapter

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">

<SAP:Category>XIAdapter</SAP:Category>

<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>

<SAP:P1>DB Tab RFCDES: Could not determine code page with T90CLNT90</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Error: DB Tab RFCDES: Could not determine code page with T90CLNT90</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

Regards,

Prashanta

[former_member206604 · Accepted solution]

Hi,

Check if T90CLNT90 exists in SM59 transcation I think it should be T90CLNT090.

Also check this link

http://help.sap.com/saphelp_nw04/helpdata/en/3b/beb13b00ae793be10000000a11402f/content.htm

Thanks,

Prakash

[Former Member · Accepted solution]

Hi All,

Prakash were correct. The code page error was comming as I had setup RFC Destination as T90CLNT090 and had incorrect entry(T90CLNT90 with 0 missing) in Configurator for Receiver Channel to SAP.

So this error occured due to incorrect RFC destination name in communication channel.

That was a great observation.I could post the idoc into SAP.

Thanks,

Prashanta

[Former Member]

Hi,

Do you use a Unicode system?

You can check that in SM59.

Always in SM59, don't forget to fill the corresponding box "unicode / non-unicode".

Else you have this OSS note "784381 - IDoc: Status 02, code page cannot be determined"

Mickael

[bhavesh_kantilal]

Hi,

This is an Authorization Issue.Take a look at this note : <b>837595</b> and make sure the authorizations available in this note are available to the User ID used in the RFC destination.

Regards,

Bhavesh