Question Re: CHAR 1 CONVERSION in Technology Q&A

CHAR 1 CONVERSION

bjorn-henrik_zink — Tue, 30 Aug 2005 08:39:25 GMT

Hi,

I have a "state" field type CHAR 1 in a R/3 table that I want to display via Web Dynpro. The problem is that the CHAR 1 data type is automatically converted into BOOLEAN when I create the model. How can I avoid that the field is converted into a boolean - I want a string?

Thanks in advance.

Elvez

Re: CHAR 1 CONVERSION

Former Member — Tue, 30 Aug 2005 09:20:38 GMT

Elvez,

Sadly, this is done automatically by Adaptive RFC import wizard. No way to alter this behavior.

But: if I understand, "state" assumes some enumeration of valid states. Just a guess, if you add enumeration you will get String type. Thoughts?

Valery Silaev

EPAM Systems

http://www.netweaverteam.com/

Re: CHAR 1 CONVERSION

Former Member — Fri, 08 Aug 2008 02:11:36 GMT

Hi Elvez,

I'm facing the same problem. How did you solved this?

Thanks in advance.

Alan

Re: CHAR 1 CONVERSION

venkatakalyan_karanam — Fri, 08 Aug 2008 11:33:28 GMT

There is no option for this. But you can change the data element in R/3 for this field. or otherwise

Take a string variable and assign it as per the back end results through coding in webdynpro.

Regards

Kalyan

Re: CHAR 1 CONVERSION

Former Member — Fri, 08 Aug 2008 11:47:40 GMT

Hello,

i think there is also an other way, you are able to create the model classes with the SAP Enterprise Connector after the creation you can edit these classes and convert inside these classes the backend CHAR1 return value which is interpreted as boolean back to String!

The only difference is now you have to call the backendsystem manually via JCO.

kind regards

Fabian

Re: CHAR 1 CONVERSION

Former Member — Sun, 10 Aug 2008 09:18:56 GMT

Hello dear,

The data element you used in R/3 is domain fixed values "X" and " ". Thats why it is taking it in to boolean.

Avoid to give domain fixed value. Then at Java side it came as string.

regards,

Sumit Malhotra

Re: CHAR 1 CONVERSION

anand7297 — Mon, 24 Nov 2025 10:50:44 GMT

Does anyone find a solution for this issue ?