‎2007 Aug 31 2:39 PM
HI all,
When I do the sci for my program , it is giving the error " Greater than/less than comparisons with character type operands may not be portable".
how can i rectify this.
wil get reward points.
regards,
Ajay
‎2007 Aug 31 2:43 PM
Hi
acording to that
your comparing the charcet vales with lessthan or greater than
if you avoid this that won't get
so make that field as integer field
reward if usefull
‎2007 Aug 31 2:43 PM
Hi
acording to that
your comparing the charcet vales with lessthan or greater than
if you avoid this that won't get
so make that field as integer field
reward if usefull
‎2007 Aug 31 2:50 PM
Hi Naresh,
I could n't make it 'INT'. it should be Char only. Then what is the solution .
regards,
Ajay
‎2007 Aug 31 2:52 PM
‎2007 Aug 31 3:02 PM
Hi sndeep,
I am wrting like this.
data : LW_CHAR(50)
IF NOT LW_CHAR BETWEEN LW_LOW AND LW_HIGH.
will get full reward points if solved .
regards,
Ajay
‎2007 Aug 31 3:15 PM
hi,
Which release u are working on ( is it 4.7 or above)?
Also , data type of lw_low and high?
‎2007 Aug 31 3:19 PM
‎2007 Aug 31 3:23 PM
Hi,
I tried this in ECC6.0 and it works fine for me.
No SCI errors .
DATA : lw_char(50),
lw_low TYPE char50,
lw_high TYPE char50.
*IF NOT lw_char BETWEEN lw_low AND lw_high.
IF lw_char GE lw_low AND lw_char LE lw_high.
ENDIF.
‎2007 Aug 31 3:29 PM
Hi sandeep,
When i do the same changes what you suggested in 4.7 i amgetting the SCI errors here.
regards,
Ajayreddy
‎2007 Aug 31 3:37 PM
Ajay,
Normally if you use Charcters field ,then should not compare like gt,lt,ge,le..
even you want to keep operation then create one range ..
DATA : lw_char(50),
lw_low TYPE char50,
lw_high TYPE char50.
ranges r_value for lw_char.
r_value-low = lw_low.
r_value-high = lw_high.
r_value-option = 'BT'.
r_value-sign = 'I'.
append r_value.
if not LW_CHAR in r_value.
endif.
Thanks
Seshu
‎2007 Aug 31 2:59 PM
hi
Tools for Performance Analysis
Run time analysis transaction SE30
SQL Trace transaction ST05
Extended Program Check (SLIN)
Code Inspector ( SCI)
Code Inspector (SCI)
You can call the Code Inspector from the ABAP Editor (SE38), the Function Builder (SE37), the Class Builder (SE24), or as a separate transaction (SCI).
The Code Inspector indicates possible problems. However, note that, especially with performance issues: There is no rule without exception. If a program passes an inspection, it does not necessarily mean that this program will have no performance problems.
<b>click on that error it will explain what you have to do</b>
reward if useful