topic Re: Unicode Conversion Error in Application Development and Automation Discussions

Unicode Conversion Error

Former Member — Wed, 06 Apr 2011 04:51:10 GMT

Hi Friends,

I have a class method where I came across the following statement


DATA nw TYPE bapi_te_network.
DATA: BEGIN OF ext,
             val1 TYPE valuepart,
             val2 TYPE valuepart,
             val3 TYPE valuepart,
             val4 TYPE valuepart,
            END OF ext.
MOVE nw TO ext.

The class has the "Unicode checks active" flag enabled.

The last "MOVE" statement works fine in a Unicode system.

However, the same statement throws an error message in a non-Unicode system - ""EXT" and "NW" are not mutually convertible. In Unicode programs, "EXT" must have the same structure layout as "NW", independent of the length of a Unicode character."

Since the Unicode checks are enabled, shouldn't the "MOVE" statement throw an error, no matter what system (Unicode/non-Unicode) it is executed on?

Regards,

Anil Madhavan

Re: Unicode Conversion Error

Former Member — Wed, 06 Apr 2011 05:04:12 GMT

Hi,

structure BAPI_TE_NETWORK contains the include structure CI_AUFK.

It may be depending on the definition of CI_AUFK (data types of the fields, ...) if there occurs a unicode error or not!

Regards,

Klaus

Re: Unicode Conversion Error

Former Member — Wed, 06 Apr 2011 05:08:58 GMT

Hi Klaus,

Thanks for your quick response.

Could you please tell me, what field types would cause this error?

In the previous code snippet, the structural layouts of 'EXT' and 'NW' are different, irrespective of the definition of CI_AUFK. But still, it works in a Unicode system, but fails in a non-Unicode system. Could you please tell me why this is so?

Regards,

Anil Madhavan

Re: Unicode Conversion Error

Former Member — Wed, 06 Apr 2011 05:36:23 GMT

Hi Anil,

I think all types of character fields should work fine.

CHAR and NUMC should be no problem.

Please post all fields of CI_AUFK from you non-unicode system with the unicode error, which are not of CHAR and NUMC type!

There should be the issue.

Regards,

Klaus

Re: Unicode Conversion Error

Former Member — Wed, 06 Apr 2011 06:58:57 GMT

Hi Klaus,

There are 20 CURR fields of length 15, and 1 CUKY field of length 5. Could this be the reason for this error?

Additionally, the error mentions something about structure layout. Does that mean that, for an equality assignment to work (not MOVE-CORRESPONDING), both the sturctures should be exactly the same?

Regards,

Anil Madhavan

Re: Unicode Conversion Error

nils_buerckel — Wed, 06 Apr 2011 13:40:18 GMT

Hi Anil,

please have a closer look at

http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b02d3594-ae48-2a10-83a7-89d369b708e5

Chapter 4 (and specifically 4.3).

Best regards,

Nils Buerckel

SAP AG

Re: Unicode Conversion Error

Former Member — Thu, 07 Apr 2011 04:31:01 GMT

Hi Nils,

Excellent Article!!

Thank you!!

Regards,

Anil Madhavan