‎2009 May 01 1:44 PM
hello,
I thought if unicode in attributes is checkd ( ecc6.0) we are not allowed to declare a table with header line but strangely its working fine with occurs 0.plz advise..am I missing something here?
Thanks
‎2009 May 01 1:51 PM
Do an extended syntax check on your program & you will get to the dark side of the occurs statement.
~Suresh
‎2009 May 01 2:01 PM
Thanks for ur reply but when its working fine why I wanted to go for extended check? In the previous threads and all the documents I have gone through each one of them said declaring internal table with header line is not allowed in ecc6.0 with unicode checked ..does it mean what everybody going on about is false when you can run the program with internal tables declared with header line?
‎2009 May 01 2:06 PM
I've never seen this statement about unicode. Can you show where you've seen it?
I think it relates to OOPS.
Rob
‎2009 May 01 2:07 PM
Hello,
Declaring an internal table with header line is "OBSOLETE" in ECC6.0 & just to let you know it has got nothing to do with unicode.
You can declare an internal table with header line, but you run the risk that in the subsequent SAP releases this declaration will not be supported.
Hope i am clear.
@Rob:
You are absolutely correct. If you do a SLIN for the code in which you declare an internal table you get this error:
Messages for Obsolete Statements(Error)
Program: ZTEST01335 Row: 10
The current ABAP command is obsolete and problematic, especially so in ABAP
Objects
Tables with headers are no longer supported in the OO context.
(The message can be hidden with "#EC *)
BR,
Suhas
‎2009 May 01 2:13 PM
right, so theres nothing to do unicode and declaring internal table with headerline in ecc6.0, so unicode is not that important in r/3 upgrade?
‎2009 May 01 2:24 PM
No Sir,
I have worked on 2-3 Unicode upgrade projects and there are many other aspects to unicode. I dont think i will be able to encapsulate all the things here, may be some other post will give a better idea.
BR,
Suhas
‎2009 May 01 2:38 PM
‎2009 May 01 2:53 PM
Check if your development objects (report) has a "Unicode compatible" switch "ON".