JCO_ERROR_CONVERSION -- Number 33,4 cannot be encoded

[Former Member]

Hi

We are getting the following problem at the RFC adapter level when an XML gets converted into RFC Structure at SAP.

The number can be accomidate into targer structure still then it is giving problem.

com.sap.aii.af.ra.ms.api.DeliveryException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not convert request from XML to RFC:com.sap.mw.jco.JCO$ConversionException: (122) JCO_ERROR_CONVERSION: Number 33,4 cannot be encoded as a BCD of length 5 with 2 decimal places at field XXX

Kindly please try to help.

Thanks

Ramesh

[Former Member]

Hi Ramesh,

Go to XI Server Tcode : SM59

Expand TCP/IP Connections, test the AI_RUNTIME_JCOSERVER connection working fine or not.

If connection failed then only you will get this kind of JCO errors. To resolve this error in this RFC Destination you will main tain the Program Id , this Program ID has to check in Visual Administrator JCO RFC Provider then connection perfectly or not..otherwise delete and re-create.

Regards,

Venu.

[Former Member]

Hi,

This error is occuring from Adapter level. Mapping program is successfully exceuting without any transformation error. And we have imported 3 or 4 times to SAP-XI from SAP R/3 system. Is there any refresh at Adapter level ? Does it require refresh for our problem ?

If we are sending a data of 33.4(dot instead of comma) and 3,4 (reduced one digit), We are able to invoke the RFC and get the response.

But if we are sending an data of 33,4, it is throwing the same error.

Please find the error message:

com.sap.aii.af.ra.ms.api.DeliveryException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not convert request from XML to RFC:com.sap.mw.jco.JCO$ConversionException: (122) JCO_ERROR_CONVERSION: Number 55,5 cannot be encoded as a BCD of length 5 with 2 decimal places at field ZZGO_PZ1

Please provide the precious inputs in resolving this issue.

Thanks,

Ramesh

[Former Member]

Hi Ramesh,

I guess it is something to do with incompatible data between the RFC structure and the data you are passing or receiving.

Try to debug with decimal data type (as in your error stack), if the RFC structure can handle the data you are sending.

For RFC reponse you can see in "Details" part of the RFC response.

Regards,

Venu