UC_OBJECTS_NOT_CHARLIKE dump while upgrading crm 6.0 to 7.0

[Former Member]

Hi,

While upgrading the system we were asked to replace the occurrences of "OPEN DATASET lv_physpath FOR OUTPUT IN BINARY MODEu201D by u201COPEN DATASET lv_physpath FOR OUTPUT IN TEXT MODE ENCODING DEFAULT".

When i did this change it resulted in dump UC_OBJECTS_NOT_CHARLIKE near the statement TRANSFER l_xml_data TO lv_physpath.

The data type of l_xml_data is xstring.

Here my question is can we open a .xml file using text mode? And Why is it resulting in dump near TRANSFER statement.

[Former Member]

you need to convert xstring to string and then process.

search for a FM which converts xstring to string in your system landscape.

[Former Member]

Hi,

if i change the data type to string will it affect the functionality anywhere else?

Why was it given as xstring. I am eager to know the justication for your answer.....Please...

[Former Member]

Hello,

Am not sure if its any different in a CRM system compared to a R3 system. But i doubt replacing Binary mode to Text mode is a wrong suggestion. You may trying giving a LEGACY BINARY MODE mode to make it behave as in the older version.

Vikranth

[Former Member]

It worked when I changed to string. Thanks