Unicode & ABAP

Hi All,
Q1. I have to determine whether my system is Unicode enabled or not? For that I have checked System>status>Unicode system = NO. But whenever I create new program Unicode checks active is by default mark as tick. So how can I determine whether system is Unicode enabled or not?
Q2. We have existing ABAPs which we need to be convert to Unicode compliant. How can we determine what changes required? What is the procedure to change the ABAP? Please provide details.
Thanks
Yogesh

Hi All,
I have to change existing ABAP to enable unicode. For that, I heard that transaction UCCHECK need to be check and after entering ABAP name , i got few errors in it.
But the method i am following to make ABAP unicode compatibale i.e. open the same ABAP in editor.By doing right click>display>attribute, I am changing "Unicode Checks active" as tickmark. After that when i do syntax check , i am getting error only for one statement i.e.
OPEN DATASET wm_datasetname FOR OUTPUT IN TEXT MODE
which i am changing as
OPEN DATASET wm_datasetname FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
After this I am not getting any error. I can activate and run also the programe.
So, could you please let me know do i need to take care of other errors which i am getting in UCCHECK transaction as i mentioned above.
Thanks
Yogesh

Similar Messages

Unicode ABAP programs

Hi ,
I want to know the steps to be followed AFTER syntax errors are removed from UCCHECK programs with error status.
Shall I test the programs for runtime errors before enabling Unicode flag?
or
first I should activate Unicode flag in UCHHECK for all programs and then do testing to check runtime errors and correctness of data.
Please clarify.
Thanks,
Yogita

There is a system parameter BASIS can set that makes the unicode flag mandatory in programs - once this is set, programs without the flag will short dump. This can be done in non-unicode system as a preliminary step before eventual move to unicode.
Setting this means the unicode flag will not be missed on any used programs - testing will soon show the missing flag.
It also means that leaving the flag not set on obsolete programs prevents their accidental execution and highlights if they are really obsolete or not.
following this strategy means that you do not want to set the flag globally - only in programs you know are required.
Once the paramenter is set, the first syntax error in any program will be unicode flag not set, and this needs to be fixed before further errors can be found/fixed.
Extended check (SLIN) and source code inspector both have options to highlight unicode issues in programs. Not all need to be fixed - eg use of TYPE instead of LIKE only needs fixing in ABAP Objects, not report programs. Good practice would be to fix all, but resource / time limits mean you fix the importants ones instead.
Andrew

ABAP development in a non-unicode system

Does anyone have a "list of abap development considerations" when developing ABAP in a 4.6C system to also be sensitive to an upcoming UNICODE conversion project, that is, What do I need to be sensitive to concerning unicode when developing in a non-unicode 4.6C system to make the upgrade to unicode of these programs easier .

You can check the documents available at market place.
service.sap.com/unicode under section
Sap netweaver-> Sap Netweaver in Detail -> Application Platform -> Unicode -> ABAP and Unicode Library.
There is one document which is specifically related to 4.6c (Vorbereitung von ABAP Programmen für Unicode in 4.6C/D) but its in German.
You can go through the other documents and see whichever is applicable for 4.6c
Regards,
Abhishek

Java Add-in for AS ABAP ERP ECC 6.0 non-unicode

Hi all,
I have a AS ABAP ECC 6.0 NON-UNICODE system and i need to install Java add-in to the system without doing unicode conversion. The problem is that when i go to SAPinst:
Start SAPinst [page 90].
2. On the Welcome screen, choose <SAP system> Additional Software Life-Cycle Tasks Java Add-In for
ABAP <database> <system variant>
I have to use UC-Kernel even though my system is Non-unicode.
Is it mandatory to convert to unicode to be able to install Java add-in. I am doing this installation so i can configure Adobe Interactive Forms in the system.
All help will be apprieciated!!

The J2EE instance will always be unicode. The installation process should create an addiitional subdirectory, 'uc', under the existing kernel path to store the unicode kernel. We have been through this process and OSS note 669902 describes additional settings that are needed for a non-Unicode ABAP instance being combined with Unicode J2EE add-on. You will need to maintain both kernel versions going forward.

Unicode conversion of reports in abap

Hi all,
how to convert non-unicode abap report into unicode report. We are planning to upgrade from 4.7 to ecc 5.0. please guide how to convert a report to unicode system.
Thanks.

Hi Jaya,
Report - --- Goto --Attributes ---check the Unicode checks active.
1. Open dataset
*Open the input file for in read mode.
OPEN DATASET p_phyfil FOR INPUT IN TEXT MODE ENCODING DEFAULT.
2. For the Describe
Need to add the character or Byte mode
3. check the structure of internal table while passing to another internal table.
Regards,
Bharani

Making ABAP sources Unicode compliant ... after Unicode conversion

Hi,
I was asked by a customer if there is any problem with the following scenario :
A system must be converted to unicode. Unfortunately, not all the ABAP source codes will be unicode enabled on-time for the conversion.
The development team wanted to know if they can assign priorities to ABAPs and focus their manpower on these ABAPs only.
The rest of the ABAPs will be made unicode compliant AFTER the conversion of the system.
I am well aware that if ABAPs don't have the Unicode flag checked, the system won't allow their execution but will it still be possible to edit the source code of those non unicode ABAPs and enable them afterwards ? From a technical point of view, I can't find any reason why it shouldn't be possible but who knows ...
Thanks for your answers,

Hi,
Yes during upgade the unicode check comes into picture..
The first unicode version is 4.7,so from 4.7 to higher versions unicode is thre...below 4.7 say 4.c is non unicode .
one example is u can dclare a variable of type X in non-unicode system(4.6c) but not possible in unicode system(ECC6.0).
Check the below links for understanding of unicode.
[UCCHECK downporting;
[UCCHECK;
[http://www.sap.com/korea/Company/Events/techday05/img/data_01.pdf]
[http://www.sap-press.de/download/dateien/1240/sappress_unicode_in_sap_systems.pdf]
[Re: ECC 6.0 Upgrade & changes required in programs;

Can we make ABAP programs Unicode enable after SAP sys is converted to uni

Hello Experts,
Can we convert the Non Unicode ABAP programs to Unicode after upgrading non unicode SAP system to Unicode?
Is there any serious problem?
If Non Unicode SAP is upgraded to Unicode without converting all non unicode ABAP programs to Unicode.
Thanks in advance.
Hari

Hi
There is no need of correcting the programs from Non unicode to Unicode
After migrating the system from non Unicode to Unicode you have to run certain Notes (which will be done by Basis) to take care of this.
Reward points for useful Answers
Regards
Anji

R3ldctl error for - ABAP Database Content Export -

Hello !!!
While running sapinst to perform the export phase, I see the next error message at console:
Error: 2007-03-05 11:57:40 [iaxxbrunas.cpp:269]
CIaRunAsUser::run_impl()
MOS-01012 PROBLEM: '/sapmnt/BWD/exe/R3ldctl -l ./R3ldctlExport.log -p /instal/export/DATA/ ' returned with '2' which is not a defined as a success code.
Detailed info about system & procedure for export:
O.S. Linux RedHat 2.4.21-37.ELsmp
Machine type: i686
Component Version: Business Information Warehouse 3.10
Kernel Release: 620
Software component: SAP_BW 3.10, Patch level: 0026
DB: Oracle 9.2.0.5.0
I try to create a Database EXPORT using R3load Based procedure.
I use for that: Installation_Master_6.20_6.40_09_06, from the tree control, I choose:
SAP Patch Collection Installation Master,
>SAP NetWeaver 04 SR1
>System Copy
 >Source System
 >ABAP System
 >Oracle
 >Unicode
 >ABAP Database Content Export
In phase of Database export:
In sapinst.log file is put the error message:
ERROR 2007-03-05 11:57:40
MOS-01012 PROBLEM: '/sapmnt/BWD/exe/R3ldctl -l ./R3ldctlExport.log -p /instal/export/DATA/ ' returned with '127' which is not a defined as a success code.
In R3ldctl.log file is put the error message:
/sapmnt/BWD/exe/R3ldctl: error while loading shared libraries: libsapu16.so: cannot open shared object file: No such file or directory
Has anyone experienced this error? If so, how did you resolve it ?
thanks in advance for any suggestion and help,
Augustin EDVES,
[email protected]
Electrica Transilvania Nord - Romania

Hallo,
I choose Non Unicode way, but still error:
ERROR 2007-03-06 15:00:11
MOS-01012 PROBLEM: '/sapmnt/BWD/exe/R3ldctl -l ./R3ldctlExport.log -p /instal/export/DATA/ ' returned with '2' which is not a defined as a success code.
persist.
In log file R3ldctl.log is not write any messages,... consider that is a good sign.
In log file R3ldctlExport.log is write error message:
DbSl Trace: OCI-call 'OCIInitialize' failed: rc = -1
DbSl Trace: OCI-call 'OCIErrorGet' failed: rc = -2
ERROR: DbSlConnect rc= 99
DbSl Trace: OCI-call 'OCIInitialize' failed: rc = -1
DbSl Trace: OCI-call 'OCIErrorGet' failed: rc = -2"
Log file R3ldctlExport.log is created under user/group = bwdadm/sapsys.
I execute sapinst under user/group = root/root.
Curiously is: under user/group = bwdadm/sapsys from console, command
/sapmnt/BWD/exe/R3ldctl -l ./R3ldctlExport.log -p /instal/export/DATA/
is executed with success.
But .. in logfile R3ldctlExport.log is a set of warning messages, like that, for all tables founded:
"WARNING: no technical settings for table "BTCJSTAT" in SAP data dictionary - defaults used"
In export directory /instal/export/DATA/ is created files like:
49173 -rw-rr 1 bwdadm sapsys 4929 Mar 6 15:16 DDLORA.TPL
49171 -rw-rr 1 bwdadm sapsys 1048 Mar 6 15:16 SAP0000.STR
Thanks for any suggestion or help
Augustin EDVES

"jco.server.unicode" is gone in JCO 3.0.5??!!

Recently we have migrated from   JCO 2.1.8 to 3.0.5.   Currently we are witnessing some problems with communications from non-Unicode Sap systems.
In the previous version (JCO 2.1.8) JCoIDoc.Server had a property "jco.server.unicode" in the latter one the property is gone.
AS far as I understand, JCo3 Server based on the data sent form a client recognizes encoding and applies proper conversion. However when we try to establish a non-Unicode connection ( from a Unicode enabled system), through setting In the SM59 transaction (tab MDMP & Unicode) u201ECommunication Type with Target Systemu201D to Non-Unicode, we are getting the following error :
com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "??????????????????
????????å å" with extension "     SAPCFL CF5CL          ???" is unavailable.
        at com.sap.conn.idoc.rt.DefaultIDocDocument.(JCoIDocDocument.java:92)
        at com.sap.conn.idoc.jco.rt.JCoIDocDocument.createIDocDocument(JCoIDocDocument.java:170)
        at com.sap.conn.idoc.jco.rt.JCoIDocRuntime.createIDocDocumentList(JCoIDocRuntime.java:80)
        at com.sap.conn.idoc.jco.JCoIDoc$DefaultJCoIDocRuntime.createIDocDocumentList(JCoIDoc.java:144)
        at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:107)
        at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:153)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3300)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2780)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2598)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2489)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2310)
        at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:277)
        at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:337)
        at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:238)
        at java.lang.Thread.run(Thread.java:619)
11:15:20,062 ERROR Sap server details
Class: com.syncron.bpe.engine.extinterface.sap.idoc.SapIDocServer
Program id: GIM
Thread name: JCoServerThread-1
Registered (at gateway) connection count: 5
Max thread count: 1
Exception occured
com.sap.conn.jco.JCoException: (104) RFC_ERROR_SYSTEM_FAILURE: IDocException occurred (raised by system karbie-nc6400|a_rfc)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc.generateJCoException(MiddlewareJavaRfc.java:639)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2395)
        at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:277)
        at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:337)
        at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:238)
        at java.lang.Thread.run(Thread.java:619)
Caused by: RfcException: karbie-nc6400
    message: IDocException occurred
    Return code: RFC_FAILURE(1)
    error group: 104
    key: RFC_ERROR_SYSTEM_FAILURE
Exception raised by karbie-nc6400|a_rfc
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2785)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2598)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2489)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2310)
        ... 4 more
Caused by: RfcException: karbie-nc6400
    message: IDocException occurred
    Return code: RFC_FAILURE(1)
    error group: 104
    key: RFC_ERROR_SYSTEM_FAILURE
Exception raised by karbie-nc6400|a_rfc
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3329)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2780)
        ... 7 more
Caused by: com.sap.conn.idoc.IDocRuntimeException: IDocException occurred
        at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:151)
        at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:153)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3300)
        ... 8 more
Caused by: com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "???????
???????????????????å å" with extension "     SAPCFL CF5CL          ???" is unavailable.
        at com.sap.conn.idoc.rt.DefaultIDocDocument.(JCoIDocDocument.java:92)
        at com.sap.conn.idoc.jco.rt.JCoIDocDocument.createIDocDocument(JCoIDocDocument.java:170)
        at com.sap.conn.idoc.jco.rt.JCoIDocRuntime.createIDocDocumentList(JCoIDocRuntime.java:80)
        at com.sap.conn.idoc.jco.JCoIDoc$DefaultJCoIDocRuntime.createIDocDocumentList(JCoIDoc.java:144)
        at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:107)
        ... 10 more
With JCO 2.1.8 we used to solve it through setting the mentioned "jco.server.unicode"   to 1, in the current one it seems that there is not much to configure regarding encoding.
Please advice.

In unicode ABAP backend systems you always have to set the destination in SM59 to "Unicode" if the communication partner is JCo. There is no choice for setting the Non-Unicode option. It won't work.
JCo3 does not require a manual setting of the "jco.server.unicode" property any longer. Therefore the property has been deleted. In JCo3 you don't have to take care for this anymore.

What is the functionality of unicode in 4.7

hi gurus
can anyone
inform me
what is the functionality of unicode in 4.7
thank u
regards
kals.

Before release 6.10, SAP supported different codes for representing characters of different fonts, for example ASCII, EBCDIC as single-byte code pages or double-bytecode pages:
ASCII (American Standard Code for Information Interchange) encodes every character with one byte. This means that a maximum of 256 characters can be displayed (strictly speaking, standard ASCII only encodes one character using 7 bit and can therefore only represent 128 characters. The extension to 8 bit is introduced with ISO-8859). Examples of common code pages are ISO-8859-1 for Western European, or ISO-8859-5 for Cyrillic fonts.
EBCDIC (Extended Binary Coded Decimal Interchange) also encodes each character using one byte, and can therefore also represent 256 characters. For example,EBCDIC 0697/0500 is an IBM format that has been used on the AS400 platform for Western European fonts.
Double byte code pages require between 1 and 2 bytes per character. This enables the representation of 65,536 characters, of which only 10,000 to 15,000 characters are normally used. For example, the code page SJIS is used for Japanese and BIG5 for traditional Chinese fonts.
Using these character sets, all languages can be handled individually in one ABAP-based SAP system. Difficulties arise if texts from different incompatible character sets are mixed in one central system. The exchange of data between systems with incompatible character sets can also lead to problems.
The solution to this problem is the use of a character set that includes all characters at once. This is realized by Unicode Unicode (ISO/IEC 10646) . A variety of Unicode character representations is possible for the Unicode character set, for example UTF, in which a character can occupy between one and four bytes.
From release 6.10, the SAP NetWeaver Application Server supports both Unicode and non-Unicode systems. Non-Unicode systems are conventional ABAP systems, in which one character is usually represented by one byte. Unicode systems are ABAP systems that are based on a Unicode character set and which have a corresponding underlying operating system, including a database.
Before release 6.10, many ABAP programming methods were based on the fact that one character corresponds to one byte. Before a system is converted to Unicode, ABAP programs must therefore be modified at all points where an explicit or implicit assumption is made about the internal length of a character.
ABAP supports this conversion using new syntax rules and new language constructs, whereby emphasis was placed on retaining as much of the existing source code as possible. As a preparation for the conversion to Unicode - but also independently of whether a system will actually be converted to Unicode - the checkbox Unicode checks active can be selected in the program properties. The transaction UCCHECK supports the activation of this check for existing programs. If this property is set, the program is identified as a Unicode program. In a Unicode program, an additional stricter syntax check is performed than in non-Unicode programs. In some cases, statements must also be enhanced by using new additions. A syntactically correct Unicode program will normally run with the same semantics and the same results in Unicode and non-Unicode systems. (Exceptions to this rule are low-level programs that query and evaluate the number of bytes per character). Programs that are required to run in both systems should therefore also be tested on both platforms.
In a Unicode system, only Unicode programs can be executed. Before converting to a Unicode system, the profile parameter abap/unicode_check should be set to "ON" so that only the execution of Unicode programs is permitted. Non-Unicode programs can only be executed in non-Unicode systems. All language constructs that have been introduced for Unicode programs can, however, also be used in non-Unicode programs.
It has been established that existing programs that have been programmed with no errors mostly fulfill the new Unicode rules and therefore require very little modification. Conversely, most programs that require significant changes are due to an error-prone and therefore questionable programming style. Even if you are not planning a conversion to a Unicode system, Unicode programs are preferable because they are more easily maintained and less prone to errors. Just as outdated and dangerous language constructs are declared obsolete and are no longer permitted for use in ABAP Objects, the rules for Unicode programs also offer increased security when programming, for example when working with character fields and mixed structures. This applies particularly for the storage of external data (for example using the file interface), which has been completely reviewed for use in Unicode programs. When creating a new program, SAP therefore recommends that you always identify the program as a Unicode program, and older programs can be converted to Unicode in stages.

Is it required to do Unicode conversion before applying NW70EhP1?

Hi,
I am going to apply NW70EhP1 in our BI system.
My BI system details is:
1. NW70 SP16
2. ABAP+JAVA Web AS
3. Non Unicode.
Is it mandatory to do Unicode conversion before applying NW70EhP1SP6 in our NW70SP16 non-unicode ABAP+JAVA BI system?
Thanks
Manoj
+91-9231524195

Hi Yu,
Thank you for your answer.
But in the market place in the below two locations Non-Unocoe kernel are not available. As my system is NW70 ABAP+JAVA and having BI Java component as well as Portal component I am worring that will these components work properly in non-unicode kernel or it is required to convert the system to unicode?
Support Packages and Patches --> Entry by Application Group --> SAP NetWeaver --> SAP NETWEAVER --> SAP EHP1 FOR SAP NETWEAVER 7.0 --> PORTAL ADD-ON SAP NW 7.0 EHP1 --> Required Product Versions --> SAP EHP1 FOR SAP NETWEAVER 7.0 - Enterprise Portal
Support Packages and Patches --> Entry by Application Group --> SAP NetWeaver --> SAP NETWEAVER --> SAP EHP1 FOR SAP NETWEAVER 7.0 --> Entry by Component --> BI Java
Thanks again..
Manoj

Unicode conversion on 32 bit OS

Dear All,
I am planning to do unicode conversion for my non-unicode system.
Could you please let me know what are the steps to be taken to perform this activity?
Is the unicode conversion possible in 32 bit OS?
I would be obligued if anybody can give suggestions on this.
Thanks and Regards
Purna

Dear Purna,
depending on your system configuration (single code page or MDMP) you will need the attachments of the following SAP notes:
- Unicode Conversion without upgrade: See SAP Note 551344
- Single Code Page without Upgrade: See SAP Note 1051576
This is the technical step by step description how to do the conversion.
In addition I would recommend to have a look at the following SAP notes:
1322715 Unicode FAQs
1319517 Unicode Collection Note
The following link gives you an overview on the topic:
SAP Unicode Conversion Topics:
http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000380759&_OBJECT=011000358700002020842008E
If you need more details, then please have a look at:
Unicode Workshop slides
http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000380759&_OBJECT=011000358700004426552004E
For the ABAP enabling, you will definitely need the following document:
Internationalization > Unicode > ABAP and Unicode Requirements > ABAP Programming in Unicode Systems: Requirements
You will find further info in:
http://service.sap.com/unicode
and
Internationalization > Unicode
Last but not least, there is also a Unicode book available:
http://www.sap-press.com/product.cfm?account=&product=H1984
Best regards,
Nils Buerckel
Solution Management
Globalization Services

Dual Stack Unicode & Non-uniocde

Is it possible in nw04s, to have a non-unicode abap and j2ee unicode?
Is it supported by sap in 32 bit and for how long?
Would the kernel upgrade be "unicode" or "non-unicode"
Tami

Hi,
I have never come across a system with a ABAP with UNICODE and JAVa with non-unicode. AS far I have seen they must be the same. since the Portal connect to the backend (ABAP stack) and they should both be on the same unicode version.
Thanks
Adil

Java - Prerequisite Unicode ?

Hi,
we are on SAP MySAP ERP 2004 (ECC 5.0 - NW2004 ) , with only ABAP stack activated, no JAVA stack yet. No UNICODE active , code page Latin 1; DIMP active
If we want e.g. use the Employee Self Services , we have to activate the Java Stack.
I heard from another customer that UNICODE is pre-requisite for JAVA ; Is this correct ? Where can I find documentation on this ?
We looked into OSS, PAM, Java SAP Installation Guide, but don't find prerequisites in that direction. Only some notes about MDMP, but that we don't use.
kind regards
Jan Baeteman

Hi Jan
The Java stack is always unicode, but still it is possible to add the java (unicode) add-in to a non-unicode ABAP stack.
Anyway, keep in mind that full integration between ABAP and JAVA components can be achieved only with Unicode Systems, as JAVA is based on Unicode. In non-Unicode systems there is always danger of data loss during text data transfer from the J2EE part to the ABAP part.
Regards,
Désiré

Can i know some thing about unicode errors

can i know some thing about unicode errors

Hi,
UCCCHECK is to check if all your programs are UNICODE compatiable.
Now UNICODE means
Unicode - Overview
Before release 6.10, SAP supported different codes for representing characters of different fonts, for example ASCII, EBCDIC as single-byte code pages or double-bytecode pages:
ASCII (American Standard Code for Information Interchange) encodes every character with one byte. This means that a maximum of 256 characters can be displayed (strictly speaking, standard ASCII only encodes one character using 7 bit and can therefore only represent 128 characters. The extension to 8 bit is introduced with ISO-8859). Examples of common code pages are ISO-8859-1 for Western European, or ISO-8859-5 for Cyrillic fonts.
EBCDIC (Extended Binary Coded Decimal Interchange) also encodes each character using one byte, and can therefore also represent 256 characters. For example,EBCDIC 0697/0500 is an IBM format that has been used on the AS400 platform for Western European fonts.
Double byte code pages require between 1 and 2 bytes per character. This enables the representation of 65,536 characters, of which only 10,000 to 15,000 characters are normally used. For example, the code page SJIS is used for Japanese and BIG5 for traditional Chinese fonts.
Using these character sets, all languages can be handled individually in one ABAP-based SAP system. Difficulties arise if texts from different incompatible character sets are mixed in one central system. The exchange of data between systems with incompatible character sets can also lead to problems.
The solution to this problem is the use of a character set that includes all characters at once. This is realized by Unicode Unicode (ISO/IEC 10646) . A variety of Unicode character representations is possible for the Unicode character set, for example UTF, in which a character can occupy between one and four bytes.
From release 6.10, the SAP NetWeaver Application Server supports both Unicode and non-Unicode systems. Non-Unicode systems are conventional ABAP systems, in which one character is usually represented by one byte. Unicode systems are ABAP systems that are based on a Unicode character set and which have a corresponding underlying operating system, including a database.
Before release 6.10, many ABAP programming methods were based on the fact that one character corresponds to one byte. Before a system is converted to Unicode, ABAP programs must therefore be modified at all points where an explicit or implicit assumption is made about the internal length of a character.
ABAP supports this conversion using new syntax rules and new language constructs, whereby emphasis was placed on retaining as much of the existing source code as possible. As a preparation for the conversion to Unicode - but also independently of whether a system will actually be converted to Unicode - the checkbox Unicode checks active can be selected in the program properties. The transaction UCCHECK supports the activation of this check for existing programs. If this property is set, the program is identified as a Unicode program. In a Unicode program, an additional stricter syntax check is performed than in non-Unicode programs. In some cases, statements must also be enhanced by using new additions. A syntactically correct Unicode program will normally run with the same semantics and the same results in Unicode and non-Unicode systems. (Exceptions to this rule are low-level programs that query and evaluate the number of bytes per character). Programs that are required to run in both systems should therefore also be tested on both platforms.
In a Unicode system, only Unicode programs can be executed. Before converting to a Unicode system, the profile parameter abap/unicode_check should be set to "ON" so that only the execution of Unicode programs is permitted. Non-Unicode programs can only be executed in non-Unicode systems. All language constructs that have been introduced for Unicode programs can, however, also be used in non-Unicode programs.
It has been established that existing programs that have been programmed with no errors mostly fulfill the new Unicode rules and therefore require very little modification. Conversely, most programs that require significant changes are due to an error-prone and therefore questionable programming style. Even if you are not planning a conversion to a Unicode system, Unicode programs are preferable because they are more easily maintained and less prone to errors. Just as outdated and dangerous language constructs are declared obsolete and are no longer permitted for use in ABAP Objects, the rules for Unicode programs also offer increased security when programming, for example when working with character fields and mixed structures. This applies particularly for the storage of external data (for example using the file interface), which has been completely reviewed for use in Unicode programs. When creating a new program, SAP therefore recommends that you always identify the program as a Unicode program, and older programs can be converted to Unicode in stages.
Regards,
Shakir

Unicode & ABAP

Similar Messages

Maybe you are looking for