07-06-2008 11:32 AM
hi
wht is the importance of this check box
and why we r going for unicode in upgradations..
please give me perfect solution
07-06-2008 11:35 AM
hi..
Before release 6.10, SAP software used character sets based on codes such as ASCII and EBCDIC. In these codes, every character is displayed by one byte; therefore character sets like these are also called single-byte codepages. Since they are only one byte, a maximum of only 256 characters was possible. Due to this, each language had its own character set or this character set was suitable for only some languages. There are also other languages such as Japanese ,Chinese etc which required 2 byte since one byte is not sufficient for displaying all the character set of an East Asian languages, so double-byte codepages are used in which every character consists of one or two bytes.
u2022 ASCII (American Standard Code for Information Interchange) encodes each character using 1 byte = 8 bit. This makes it possible to represent a maximum of 28 = 256 characters to which the combinations 00000000, 11111111 are assigned.
u2022 EBCDI (Extended Binary Coded Decimal Interchange) also uses 1 byte to encode each character, which again makes it possible to represent 256 characters.
u2022 Double-byte code pages require 1 or 2 bytes for each character. This allows you to form 216 = 65536 combinations where usually only 10,000 - 15,000 characters are used.
Using these character sets, you can account for each language relevant to the SAP System. However, problems occur if you want to merge texts from different incompatible character sets in a central system. Equally, exchanging data between systems with incompatible character sets can result in unprecedented situations.
Unicode is a universal encoded character set that allows you to store information from any language using a single character set.
Unicode provides a unique code for every character, independent platform, program or language.
If your reports are not Unicode-enabled (i.e. checkbox marked and no Unicode-errors => transaction UCCHECK) they will not run on a Unicode SAP system.
For more details please refer to: ABAP and Unicode
thanks and regards
sindhu_gullapalli
07-06-2008 11:35 AM
hi..
Before release 6.10, SAP software used character sets based on codes such as ASCII and EBCDIC. In these codes, every character is displayed by one byte; therefore character sets like these are also called single-byte codepages. Since they are only one byte, a maximum of only 256 characters was possible. Due to this, each language had its own character set or this character set was suitable for only some languages. There are also other languages such as Japanese ,Chinese etc which required 2 byte since one byte is not sufficient for displaying all the character set of an East Asian languages, so double-byte codepages are used in which every character consists of one or two bytes.
u2022 ASCII (American Standard Code for Information Interchange) encodes each character using 1 byte = 8 bit. This makes it possible to represent a maximum of 28 = 256 characters to which the combinations 00000000, 11111111 are assigned.
u2022 EBCDI (Extended Binary Coded Decimal Interchange) also uses 1 byte to encode each character, which again makes it possible to represent 256 characters.
u2022 Double-byte code pages require 1 or 2 bytes for each character. This allows you to form 216 = 65536 combinations where usually only 10,000 - 15,000 characters are used.
Using these character sets, you can account for each language relevant to the SAP System. However, problems occur if you want to merge texts from different incompatible character sets in a central system. Equally, exchanging data between systems with incompatible character sets can result in unprecedented situations.
Unicode is a universal encoded character set that allows you to store information from any language using a single character set.
Unicode provides a unique code for every character, independent platform, program or language.
If your reports are not Unicode-enabled (i.e. checkbox marked and no Unicode-errors => transaction UCCHECK) they will not run on a Unicode SAP system.
For more details please refer to: ABAP and Unicode
thanks and regards
sindhu_gullapalli
09-23-2008 6:13 PM
Do not cross-post multiple questions and cross-post multiple answers....
Read [the rules|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/rulesofEngagement] next time.