Skip to Content
0

JCO$ConversionException: (122) JCO_ERROR_CONVERSION

Apr 18, 2017 at 09:25 AM

33

avatar image

we have two scenarios , sync and async which is from CLM to ECC. Sync is a standard one and because of some problem we shifted solution to Async.

So here for request part we have not chnaged anything even in PI. For response we have changed to XI proxy.

so when we publish MA's (data) from CLM to ECC in Async case the message is processed to target (ECC) and it is struck in queue and here user assume that MA is published but it is failing in ECC where as when we do it in sync we are are facing the JCOerror and CLM (source system) they can see that MA is not getting published.

So even in async case my MA should fail in SAP PI. But here it is sent to ECC and getting failed there. So here Source is assuming that MA is published from there end.

I am facing the below issue when data is sent to RFC . Data is failing in PI with below error.

com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: could not convert request from XML to RFC:com.sap.mw.jco.JCO$ConversionException: (122) JCO_ERROR_CONVERSION: Number 240000 cannot be encoded as a BCD of length 5 with 0 decimal places at field

I can see in RFC the above field as type decimal and at source i am maintaning as string.

Note: This is a standard RFC.

Why async case is not behaving like in sync.?

Can anyone suggest what should be done.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

0 Answers