Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Help req with the code

Former Member
0 Likes
1,305

Hi all

we are a MDMP code page system and we upgraded to ECC 6.0.

-

This is the error iam getting IN UCCHECK for unicode

The system could not perform a static convertibility check on the current

statement, because of untyped or generic operands. It can only carry out this

. runtime.

Whta exactly static convertibility check.

Can anyone suggest what i have to do regarding this

The error is pointing this piece of code

----


  • FORM bdc_dynpro *

----


  • ........ *

----


  • --> PROGRAM *

  • --> DYNPRO *

----


form bdc_dynpro using program dynpro.

clear i_bdcdata.

i_bdcdata-program = program.

i_bdcdata-dynpro = dynpro.

i_bdcdata-dynbegin = 'X'.

append i_bdcdata.

endform.

----


  • FORM bdc_field *

----


  • ........ *

----


  • --> FNAM *

  • --> FVAL *

----


form bdc_field using fnam fval.

clear i_bdcdata.

i_bdcdata-fnam = fnam.

i_bdcdata-fval = fval.

append i_bdcdata.

endform.

This is from the standard include bdcrecx1

----


  • Start new screen *

----


FORM BDC_DYNPRO USING PROGRAM DYNPRO.

CLEAR BDCDATA.

BDCDATA-PROGRAM = PROGRAM.

BDCDATA-DYNPRO = DYNPRO.

BDCDATA-DYNBEGIN = 'X'.

APPEND BDCDATA.

ENDFORM.

----


  • Insert field *

----


FORM BDC_FIELD USING FNAM FVAL.

IF FVAL <> NODATA.

CLEAR BDCDATA.

BDCDATA-FNAM = FNAM.

BDCDATA-FVAL = FVAL.

APPEND BDCDATA.

ENDIF.

ENDFORM.

It looks the same way i wrote the code right.

Thanks

Suchitra

14 REPLIES 14
Read only

Former Member
0 Likes
1,275

Hi,

Any suggestions would be appreciated

Thanks

Read only

Former Member
0 Likes
1,275

try my guess!!!!!!!!

form bdc_dynpro using program <b>type bdcdata-repid</b>

dynpro <b>type bdcdata-dynnr.</b>

clear i_bdcdata.

i_bdcdata-program = program.

i_bdcdata-dynpro = dynpro.

i_bdcdata-dynbegin = 'X'.

append i_bdcdata.

endform.

----


  • FORM bdc_field *

----


  • ........ *

----


  • --> FNAM *

  • --> FVAL *

----


form bdc_field using fnam <b>type bdcdata-fnam</b>

fval <b>type bdcdata-fval</b>.

clear i_bdcdata.

i_bdcdata-fnam = fnam.

i_bdcdata-fval = fval.

append i_bdcdata.

endform.

Read only

0 Likes
1,275

Hi,

I tried

1)form bdc_dynpro using program dynpro.

either of this worked

form bdc_dynpro using program type bdcdata-PROGRAM

dynpro type bdcdata-dynpro.

or

form bdc_dynpro using program TYPE BDC_PROG dynpro TYPE BDC_DYNR.

2) But for this it gaave me an other error

form bdc_field using fnam fval. "commented

form bdc_field using fnam type bdcdata-fnam

fval type bdcdata-fval. " added

or even i tried this as well

*form bdc_field using fnam TYPE FNAM_____4 fval TYPE BDC_FVAL. " added

this gave me an error in the code saying

In PERFORM or CALL FUNCTION "BDC_FIELD", the actual parameter

"T_UPLOADEMPTY-ERDAT" is incompatible with the formal parameter "FVAL".

the error is pointing towards

perform bdc_field using 'ZXXX-ERDAT(01)'

T_UPLOADEMPTY-erdat.

LET ME KNOW

Thanks

Read only

0 Likes
1,275

Hi ,

can anyone throw some light on this issue

thanks

Read only

Former Member
0 Likes
1,275

Try this.

Unicodes checks active is this checked for your in the program, check for the attribues.

Read only

0 Likes
1,275

Hi,

ITS CHECKED . tHATS WHAT WE ARE DOING WE ARE FIXING UNICODE ERRORS

Thanks

Read only

Former Member
0 Likes
1,275

I think the issue is in this FORM with the IF statement. Here NODATA is of CHAR type with a value of '/' whereas FVAL is not determined statically during syntax check. Its value can be numeric or char. So instead of this IF statement, you should define another local variable of type C, move FVAL to it and check that variable <> NODATA instead of FVAL.

But again, since this is standard SAP include, you cannot do much about it. You may have to copy the FORM into your program, name it different and then make these changes.


FORM BDC_FIELD USING FNAM FVAL.
  DATA: L_FVAL LIKE BDCDATA-FVAL.
  L_FVAL = FVAL.
  IF L_FVAL <> NODATA.
    CLEAR BDCDATA.
    BDCDATA-FNAM = FNAM.
    BDCDATA-FVAL = FVAL.
    APPEND BDCDATA.
  ENDIF.
ENDFORM.

Read only

Former Member
0 Likes
1,275

Hi Srinivas,

This is my actual code

Here iam not comparing FVAL with NODATA

As its being done in SAP Standard code

----


  • FORM bdc_dynpro *

----


  • ........ *

----


  • --> PROGRAM *

  • --> DYNPRO *

----


form bdc_dynpro using program dynpro.

clear i_bdcdata.

i_bdcdata-program = program.

i_bdcdata-dynpro = dynpro.

i_bdcdata-dynbegin = 'X'.

append i_bdcdata.

endform.

----


  • FORM bdc_field *

----


  • ........ *

----


  • --> FNAM *

  • --> FVAL *

----


form bdc_field using fnam fval.

clear i_bdcdata.

i_bdcdata-fnam = fnam.

i_bdcdata-fval = fval.

append i_bdcdata.

endform.

I haven't used the satndard inclue bdcrecx1

which has the code as you mentioned

let me know

Read only

0 Likes
1,275

So are you getting this unicode check issue in your code? Which line exactly is it pointing to?

Read only

0 Likes
1,275

Suchitra,

To correct the syntax error we can give as TYPE ANY.

Like <b>form bdc_field using fnam TYPE any fval TYPE any.</b>

If you give fval type BDC_FVAL(Char 132) & if you pass the date(DATS8). The data type is not compaitable since one is CHAR & other is DATS.

Generic solution is TYPE any. It will accept any data type & wont throw any syntax error.

But still you will get error in UCCHECK anyway u can ignore it.

Regards,

Sail

Read only

0 Likes
1,275

Hi,

Srinivas ,

Its pointing towards

i_bdcdata-fnam = fnam.

i_bdcdata-fval = fval.

I guess i have to ignore the warnings.Let me know if anyone of you came across such type of warnings

Thanks

Read only

0 Likes
1,275

It is true that this comes up as warning and you can always ignore it. Typing these parameters is one way to avoid but then all your calls should be compatible. You can also use TYPE ANY which should also eliminate this problem.

Read only

0 Likes
1,275

Hi Srinivas,

I tried Like form bdc_field using fnam TYPE any fval TYPE any.

But even then it shows me the same warnings iN UCCHECK

Let me know

Thanks

Read only

0 Likes
1,275

Hi Suchitra,

I am working on a similar Unicode upgrade. At the moment I'm also stuck with the same issue regarding defining a data type for the FNAM and FVAL fields in my own customer include for BDC (not SAP standard include, without the NODATA check!!).

I have tried TYPE ANY, but the error is still displayed by UCCHECK.

Have you been able to resolve this error. Please reply at the earliest as i need to work this out on an urgent basis. Thanx a ton in advance!!!

Can you or someone else who's faced this issue please revert to me.

Thanks so much,

Priya