JCO_ERROR_CONVERSION:

Hi,
I am pulling data from a DB2 table using JDBC adapter and inserting into sap R3 using RFC adapter. The DB2 table has a field pay_ref with integer 4 value. In design / RFC I have tried all combinations of data types but it gives me the following error message -
Exception caught by adapter framework: 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: Integer '167080' has to many digits at field.
This integer 167080 is pay_ref at DB2.
Could anybody help as to how I can map it ??
Thanks.

Preeti,
What type u have in RFC? If ur using some numeric types then try using FormatNumber builtin function in the map for this value.Sometimes it helps.
SourceField->FormatNumber->TargetRFCField.
regards
rajeev

Similar Messages

RFC Adapter : JCO_ERROR_CONVERSION : Unparseable date

Hi all,
We are working with RFC Adapter .
We are getting the following error in RWB -->
Component Monitoring --> Adapter Engine --> RFC
Adapter
" JCO_ERROR_CONVERSION: Date '01.12.2005' has a wrong format at field VALIDITYBEGIN: Unparseable date: "01.12.2005" "
- Error: 2006-02-03 11:17:13 IST: Message processed for interface BAPI_BANKDETAIL_CREATE: com.sap.aii.af.rfc.afcommunication.RfcAFWException: 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)
Can anyone please suggest how to resolve it .
Regards,
Shikha

Hi,
In which format the date is passed from XI?
If, it is of type Java Date there will be No conversion issue else if the it of Type String then the date should be in the format YYYYMMDD.
Hope this helps you.

Error as :JCO_ERROR_CONVERSION: Integer '33701138    S1' has to many digits

Hi Experts,
   I am doing the scenario flat File to RFC [BW System]. Sender side file is picking fine and processing fine but in the receiver side i am facing problem. According to RFC channel logs the below error i am getting.
Error in processing caused by: 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: Integer '33701138    S1' has to many digits at field /BIC/ZSAL_ONO.
I am facing problem in field /BIC/ZSAL_ONO.
In some records i am getting data as 55704438S1 and this is processing successfully. But with gap i am getting as above error.
I can see in RFC the above field as type string and also in souce i am maintaning as string.
Note: I have imported standard RFC.
Can anyone sugget what should be done.
Thanks,
Bahskar

Hi Sameej,
   The type is NUMC and length is 10. But i am getting in source field as 14 in length with gap. So i need to fill that gap and send as
10 length.
suppose if am getting in source field as 33007718    S1 then i need send to target as 33007718S1.
Can any one suggest how to write UDF for this. Can any one send with code pls.
Thanks,
Bhaskar

JCO_ERROR_CONVERSION -- Number 33,4 cannot be encoded

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

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

Error in soap to rfc scenario

while checking the result in altovaxmlspy i m getting the following error "(122) JCO_ERROR_CONVERSION: Date '12/20/2002' has a wrong format at field FLIGHTDATE: Unparseable date: "12/20/2002"" . The BAPI being used is SXIDEMO_AIRL_FLIGHT_CHECKAVAIL.
The date format visible in fldate field of SFLIGHT table is MM/DD/YYYY and while mapping in IR the source date format is dd/mm/yyyy and target format taken is mm/dd/yyyy.
pl help how to rectify the error in order to see the proper result

Hi Prateek
Date conversion while mapping has been done using std function " Date Trans" only.
" But the target date u mentioned is mm/dd/yyyy. Make sure that the RFC accepts the date in this format."
The crux of the matter is that i m unable to make sure the above quoted point . Pl help how to ensure whether the RFC accepts the date in this format .
Rgds
Edited by: shazia seemin on Jan 22, 2008 7:44 AM

How to Handle RFC delivery exception (rfcClientException) in XI?

I have a following scenario.
I have an outbound soap interface (sender) and inbound RFC(receiver). When the soap message is posted it goes to receiver where it has to execute the RFC. It tries to convert the XML to RFC and throws the following exception.
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: Date 'xxxx-xx-xx' has a wrong format at field CREAT_DATE: Unparseable date: "xxxx-xx-xx
I defined the fault message and attached it to the Inbound Interface. I also defined the mapping of receiver exception message to fault message. I am expecting a fault message back to sender which is not happening.
When I go to moni and try to look for the error in the response message I see the following.
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="PARSING">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>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: Date 'xxxx-xx-xx' has a wrong format at field CREAT_DATE: Unparseable date: "xxxx-xx-xx"</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I am suspecting that since the fault message does not contain this structure it's not able to build it.
How do I handle such runtime exception and transfer it to sender system. Any help would be greatly apperciated.

I have the same problem. The error is as follows:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="PARSING">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>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: Date '2006/04/09' has a wrong format at field INVALIDITYBEGIN: Unparseable date: "2006/04/09"</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Anyone have any idea, how should I resolve the data format issue?
Thanks

File RFC sync scenario error: MsgId alredy exists in the system

Hi,
I am working on File RFC sysnc scenario.
The first message that I tried to processed gave a error
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: Date ' ' has a wrong format at field REQ_DATE_H: Unparseable date: " "
When I retried correcting the data, it started giving strange error
Message ID 62D07CA0D3EE11DCCD36DA01C52F0606 for pipeline CENTRAL, version already exists in system.
How to rectify this?
XI version is PI 7.0 SP10

Nisar,
Which program to re-run? Are you talking about activating the channel again? If so, then I have done it many times changing the file name.
I got below error in Communication Channel Monitoring:
2008-02-06 02:27:39 Error Received XI System Error. ErrorCode: MSGGUID_EXISTING ErrorText: ErrorStack: Message ID 83F8B0B0D48311DCA544DA01C52F0606 for pipeline CENTRAL, version already exists in system
2008-02-06 02:27:39 Error Returning synchronous error notification to calling application: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:MSGGUID_EXISTING:.
2008-02-06 02:27:39 Error Transmitting the message using connection http://xibox:8000/sap/xi/engine?type=entry failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:MSGGUID_EXISTING:.
2008-02-06 02:27:39 Error The message status set to FAIL.
2008-02-06 02:27:39 Error Returning to application. Exception: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:MSGGUID_EXISTING:
2008-02-06 02:27:39 Error Attempt to process file failed with com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:MSGGUID_EXISTING:
2008-02-06 02:27:39 Error Attempt to process file failed with com.sap.aii.af.service.util.transaction.api.TxManagerException: Unable to roll back transaction: com.sap.engine.services.ts.exceptions.BaseIllegalStateException

Call Adapter Error

Hello everybody,
I have a synchronous scenario ABAP Proxy->XI->RFC, the reason why we used XI it's beacuse by company politics any systems integration needs to go by SAP XI, and the reason why we used RFC in the receiver system it's because by company politics too we can't generate proxies in that system, so we decided to go by RFC, now the interface is working really fine, the abap proxy in the sender system is called by a Z program, so this program gives a report of every record, and the problem that I'm facing is that I need to give back to the sender systems errors like this:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>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: Date '9999-12-32' has a wrong format at field VALIDA: Unparseable date: "9999-12-32"</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
this error it's beacuse of the day 32 of the month december, we know that, but this error is only treated as exception CX_AI_SYSTEM_FAULT in the Proxy, and I need to pass the SAPAdditionalText of the error above to the sender system, is there a way to give back to the proxy this text so it will be more explicit in the error and not just a SYSTEM_FAULT???????, thanks in advance.
Regards,
Julio Cesar

Hello VJ,
Thanks for your answer, about the solution your are kindly giving me, it's not really clear to me in this point:
" When ever you get such exceptions, you need to catch them
in your RFC and fill your own exception object and throw it."
the exception I'm getting is a default by SAP, not one I could raise, maybe I'm not understanding right your proposal could you explain me more this part, do you mean that if I declare an exception in my RFC even if I'm not doing the RAISE is going to catch the exception I'm getting?, thanks a lot for your answer.
Regards,
Julio Cesar

File to RFC Error

Hi,
I done File->RFC scenario. It was showing WAITING in
Message Monitoring. But in CC Monitoring showing error
like No suitable sender agrement found. Y it is
showing like this? even I done Sender Agrement?
thx and regards,
Ansar.

Hi,
Now I gone through this link
Re: Unable to find the processed message
Here they mentioned to check in http://<host>:<port>/mdt
I checked it. Then I found the error in Audit Log
as Delivery of the message to the application using
connection AFW failed, due to: 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: Date '25.09.2006' has a wrong
format at field DELIV_DATE: Unparseable
date: "25.09.2006".
Now how to give the date format?
thx.

Error message com.sap.aii.af.ra.ms.api.DeliveryException: error while proce

hello experts
I am sending a message WS2RFC and recieve an error message that return from the RFC.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: error while processing the request to rfc-client: com.sap.aii.af.rfc.afcommunication.RfcAFWException: 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: Date '03042008' has a wrong format at field DATUM: Unparseable date: "03042008"</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
any ideas what it is and how to solve it?

Hi,
Looks like you have passed data in wrong format to RFC input parameter.
Your format: DDMMYYYY (03042008)
Expected: YYYYMMDD
I would use a graphical mapping function "DataTrans" to convert date format from DDMMYYYY to YYYYMMDD.
Regards,
Jakub

Repricing in CRM deletes manual price

When a manual price condition is entered in a CRM document, and pricing is refreshed, the manual price is deleted. In R/3, in price procedure configuration, there is a setting for 'pricing type' which allows control of manual prices. This feature does not exist on the CRM price procedure configuration, and I do not see it in Item category pricing choices.
Does anyone know how to hold manual prices, but redetermine others?

Hi Bill,
There are 2 steps to follow by which you can set a condition type to be manually processed
1. Set the value for 'Manual entries' for Condition type to 'Manual entry has priority'
2. Mark the 'Manual' flag for the relevant condition type in the pricing procedure.
If, after doing these customizing settings, the manual conditions get deleted, please check your SM53 log for the application component com->sap->conn->jco and rfc. If you get an error, as follows, then you may need to request your basis team to update your VMC kernel patch level to the latest version.
'com.sap.conn.jco.ConversionException: (122) JCO_ERROR_CONVERSION: Cannot convert field CALC_TYPE of type CHAR to char'
Hope this helps.
Regards,
Pavithra
**PS : Please reward points if this helps

Error while using Adaptive RFC model

I am using adaptive RFC model to consume a function module from BI system. The function module expects a Boolean input. While executing the function module we need to give u2018Xu2019 for that input. When I consumed the function module in the webynpro java project , used it and give the input as u2018trueu2019 on runnig the application it gives the following error: u201Ccom.sap.conn.jco.ConversionException: (122) JCO_ERROR_CONVERSION: Cannot convert a value from type java.lang.Object to CHAR at field I_READ_ATTRu201D
There is corresponding dictionary type created called u2018BOOLE_Du2019 but I could not access the dictionary type in the controller java file.
Is there a way to rectify the same or any workaround condition?
With regards,
Sougato.

Hi saurabh,
I need to give the value from webdynpro. Hers is the sample code.
rssem_Cha_Values_Get_Input.setI_Read_Attr();
// It expects a boolean value but if i pass a value to the method the obove error is show.
Where as there is a simple type "Boole_d" generated when i consumed the RFC in the webdynpro.
but i couldn't access this simple type in the code.
With regards,
Sougato.

JCO_ERROR_CONVERSION:

Similar Messages

Maybe you are looking for