2007 Feb 28 3:32 AM
Hi Abapers,
If i am using 4.7 where Unicode Checks were there , how it is different from previous versions , if i am upgrading code from previous version
, what are the precautions should i need to take care , in which part of the statements should i need change ......
With Regards
Bhaskar Rao.M
2007 Feb 28 7:33 AM
Hi!
Most problems occur with move (also by perform / call function), when an un-structured variable should be equal a structured variable.
data: begin of ls_struc,
field1(10) type c, "has 20 bytes
field2(10) type n, "has 10 bytes
end of ls_struc,
field3(20) type c. "has 40 bytes
move field3 to ls_struc. "error in unicode
In a non-unicode system the move would work, because field3 has 20 bytes just as ls_struc.
Regards,
Christian
Hi Abapers,
If i am using 4.7 where Unicode Checks were there , how it is different from previous versions , if i am upgrading code from previous version
, what are the precautions should i need to take care , in which part of the statements should i need change ......
With Regards
Bhaskar Rao.M
2007 Feb 28 7:33 AM
Hi!
Most problems occur with move (also by perform / call function), when an un-structured variable should be equal a structured variable.
data: begin of ls_struc,
field1(10) type c, "has 20 bytes
field2(10) type n, "has 10 bytes
end of ls_struc,
field3(20) type c. "has 40 bytes
move field3 to ls_struc. "error in unicode
In a non-unicode system the move would work, because field3 has 20 bytes just as ls_struc.
Regards,
Christian
2007 Feb 28 1:27 PM
Hi,
This switch to Unicode affects all statements where an explicit or implicit assumption is made about the internal length of a character. If you use these statements in a program that is designed to exploit the Unicode capabilities of the runtime environment, they must be checked and changed if necessary. Once a Unicode-enabled program has been changed accordingly, it behaves in the same way in both Unicode and non-Unicode systems. You can develop programs in a non-Unicode system (NUS) and then import them into a Unicode system (US).
Restrictions in Unicode Programs
The adjustments you have to make and the restrictions that apply in the Unicode context have been limited to the essentials on the ABAP development side to keep the conversion effort for ABAP users to a minimum. In some cases, however, this has led to the emergence of more complex rules, for example, with regard to assignments and comparisons between incompatible structures.
Character-Type and Numeric-Type Operands
Access Using Offset and Length Specifications
Assignments
Comparisons
Processing Strings
Type Checks and Type Compatibility
Changes to Database Operations
Determining the Length and Distance
Regards,
Sruthi
2007 Mar 01 6:20 AM
2007 Feb 28 3:13 PM
Hallo Bhaskar,
the transaction /nABAPHELP contains in Release 7.10 an according chapter.
Regards,
Klaus
2007 Mar 01 9:44 AM
hi,
many problem you will face is in OPEN dataset statements and in the SPLIT,CONCATENATE,OVERLAT,TRANSLATE, in non unicode versions these stmnt can perform operations on non character type also, but in the unicode versions these opn are possible only using character data type(c,n,d,t).
2007 Mar 07 12:37 PM
IF u are using open data set for input/output/appending you must and should use encoding default other wise it will give error
2007 Mar 09 5:56 AM
Hi...
In versions enabled with unicode checks, problems arise when you try to assign data to a variable which is not large enough to hold it..... Versions prior to 4.7 would not throw an error as truncation occurs... but with versions with unicode checks enabled an error is reported....
You will have to replace certain obsolete function modules like ws_upload and ws_download with suitable function modules like gui_upload and gui_download....
Please reward points if found useful
2007 Mar 10 11:37 AM
Hi,
Thanks for ur answer...
With Regards
Bhaskar Rao.M
| User | Count |
|---|---|
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |