parameter_conversion_error during RFC

[Former Member]

Hello Experts,

I get a 'PARAMETER_CONVERSION_ERROR' dump with the following short text 'An error occurred during the receipt/conversion of a complex parameter'. The dump file is also attached.

The called function module has no 'tables' parameters. Also the associated 'exporting' parameter is of type string.

The OSS note 414429 has already been referred to. I DO NOT get the 'CALL_FUNCTION_SEND_ERROR' dump and there is no mismatch of the

parameters or types used.

Somewhere in the attached dump file, you will notice that there are some corrupted entries like '䄀###䄀###䄀.....'.

(The managed ERP system is based in Asia, making me wonder if this is a Unicode related issue..but again, im not ure about this)

Any suggestions what the issue could be here? Could this be the RFC middleware engine that converts data from ABAP<-> XML causing this problem or could it be a ABAP language(kernel)issue?

Thanks in advance.

Best,

Dev

[venkateswaran_k]

Can you please tell me what are your /import and export paramters and their type?

Regards,

Venkat

[Former Member]

Hi Venkat,

Thanks.

Please find attached the parameters that are being used in the function.

Best,

Dev

[former_member196490]

Check the below link if it helps

http://www.saptechies.com/abap-runtime-error-parameterconversionerror/

[RaymondGiuseppi]

If one system is Unicode and not the other then conversion will occur (check tab "MDMP and Unicode" in RFC definition) > First check definition of RFC destination related to Unicode and Conversion.

Parameter type character will be converted in the RFC call, but not deep/complex ones, so that can be the cause of the problem ?

Some references : Code Pages (help.sap.com) , Note 1790232 - FAQ: Unicode - Technical FAQs (question 25), Note 991572 - Code page settings for external RFC programs and Note 547444 - RFC Enhancement for Unicode ./. non-Unicode Connections.

Regards,

Raymond

[Former Member]

HI Mahadevan,

It looks like an unicode conversion issue. If that is it, then you need to convert the attached value by using the below class method.

  TRY.

      CALL METHOD cl_abap_conv_in_ce=>create

        EXPORTING

          encoding = '1100'

          input    = ls_xstring

        RECEIVING

          conv     = l_convin.

      CALL METHOD l_convin->read

        IMPORTING

          data = p_string.

    CATCH cx_root.

      EXIT.

  ENDTRY.

Put it in a loop if more than one record and then append into one more table.

Hope that helps.

Regards,

Adithi

[former_member215981]

Hello,

please check RFC destination SM_OBICLNT132_READ, under Unicode tab, ensure target is maintained

correctly. you can use unicode test to know what the target sytem is.

Best Regars,

Yong Luo

[Former Member]

Thanks Yong,

RFC destination SM_OBICLNT132_READ in SM59 has the following status.

The client system itself has Unicode status = 'YES' under system->status.

So if this is the issue, should not the ABAP system/RFC engine take care of such conversion issues?

Cheers

Dev

[former_member215981]

Hello Dev

please click "Unicoe test" button on the menu. if it is non-unicode, please go to Logon& Security to check

what language is maintained here, you need to specify correct one.

if the target is unicode then you need to change to unicoe under this tab.

after this, to see this help or not.

Best Regards,

Yong Luo

[Former Member]

Hi,

could you set communication type to unicode and try again? Or copy the RFC destination to a unicode connection? If yes, what's the result then?

Regards,

Klaus

[Former Member]

Hi Yong,

Unicode test results

Screenshot below doesn't say much

'please go to Logon& Security to check what language is maintained here'

No language is maintained here. I don't think I can change this as this is automatically generated from SolMan

if the target is Unicode

No, target system is not Unicode. Source system is.

Best,

Dev