‎2007 May 09 10:57 AM
Hi all ,
while doing upgrade from 4.6c to ecc 6.0 i am gettig this error
"I_COSS" cannot be converted to the line incompatible. The line type
must have the same structure layout as "I_COSS" regardless of the
length of a Unicode . Unicode character. Unicode character.
and this error is coming in this line of code
PERFORM accepted TABLES i_coss USING zcoss quantity hour.
PERFORM accepted TABLES i_cosp USING zcosp quantity hour.
FYI:
these two perform calling a single form
FORM accepted TABLES w_table STRUCTURE i_cosp USING char6 char3 typ.
also
DATA: i_coss TYPE coss OCCURS 0 WITH HEADER LINE.
DATA: i_cosp TYPE cosp OCCURS 0 WITH HEADER LINE.
please help me in resolving this issue
thanks in advance .
‎2007 May 09 11:02 AM
apparantly your form accepted uses a tabel type COSP and you pass type COSS, in the new version this is not accepted anymore. What is the difference between type COSS COSP?
‎2007 May 09 11:02 AM
apparantly your form accepted uses a tabel type COSP and you pass type COSS, in the new version this is not accepted anymore. What is the difference between type COSS COSP?
‎2007 May 09 11:08 AM
yes i know in 4.6 this structure incompatibility issue was not dere but in 6.0 it is not acceptable.
these coss and cosp are table
in 4.6c coss have 161 feilds
cosp have around 145
in 6.0 coss have 167 feilds
cosp have 151 fields
‎2007 May 09 11:12 AM
Hello Anit
Table COSP has 161 fields and table COSS 145 fields, most of which are common to both tables.
The TABLES parameter is of (line) type COSP. In order to get around the Unicode error you have to move the data from I_COSS to an itab having line type COSP:
DATA:
lt_cosp_tmp TYPE cosp OCCURS 0 WITH HEADER LINE.
LOOP AT i_coss INTO ls_coss.
clear: ls_cosp.
MOVE-CORRESPONDING ls_coss TO ls_cosp.
APPEND ls_cosp TO lt_cosp_tmp.
ENDLOOP.
" PERFORM accepted TABLES i_coss USING zcoss quantity hour. " Replace by:
PERFORM accepted TABLES lt_cosp_tmp USING zcosp quantity hour.
PERFORM accepted TABLES i_cosp USING zcosp quantity hour.However, it is up to you to find out whether this coding is semantically correct.
Regards
Uwe
‎2007 May 11 7:27 AM
hi uwe,
thanks 4 d reply
this code seems to b correct means it is nt giving error
i havnt checked its output bcoz i dnt hav test data rite nw
but i thnk this move corresponding will create some problem while activating
bcoz in coss and cosp there are two feilds which are totally different apart from that difference in no of feilds.
means
coss vbund cosp parob
pargb vspob
these field differs
so wen i ill use move corresponding i think it will create som data loss.
wat say??