Non-unicode to Unicode conversion in ECC 6.0

hello friends,
WE have ECC 6.0 at our location , it was upgraded from 4.7 to Ecc 6.0, but it is in non-unicode format , just we have to convert that thing to unicode , for that we have seen that we can export the data from current non-unicode system by SAPINST and import that data to another ECC 6.0 unicode system by using SAPINST .
i bit confuised that which oprn from SAPINST i have to select to export the data and which option to be select from SAPINST to import the data so pls can anybody help me regarding the same.
Regards
Anil

> Go for the exact document which u need. Code page
> 4100 is common for Unicode conversion....
4100? No - 4102 or 4103 are the correct ones - depending on processor and operating system (endianess). See
Note 552464 - What is Big Endian / Little Endian? What Endian do I have?
Markus

Similar Messages

Regarding non-unicode to unicode conversion in mapping

In our project we have Pi system which is installed as unicode system.
But the SAP systems at the sender side is unicode and most of them are non-unicode systems.
We have a doubt regarding the challenges that we need to face in PI mapping with reference to unicode and non unicode conversion.
Is it possible for us to Map the RFCs of non-unicode SAP system at sender side with the help of graphical mapping?
Any conversion we need to do?
Thanks & Regards,
sasi
Edited by: sasitharan on Jan 6, 2009 4:25 PM

Thanks a lot for your replys.
In our customer lanscape they have following SAP R/3 vsesions 4.0B,4.5B.4.6B,4.6C,ECC 5.0,ECC 6.0
so how this unicode , non unicode settings varies with respect to versions?
Is it resembles same with respect to all the version?
Thanks & Regards,
Sasi

Unicode Non Unicode

Hi Experts
I have installaed a ECC 6.0 ABAP+ JAVA unicode system. Now for soem reason my management wants to move to a Non-Unicode version.
Is there any way we can make unicode to Non-Unicode conversion or I have to go for a fresh install and start all work fron scratch.

Hello Raj,
As you can see above there is no method to move your system to a Non Unicode System from a Unicode system.
In addition to this, i would point out that even with a non unicode system your java stack will always have to
be unicode even your your abap stack is not.
Kind Regards,
David

What's the best solution Unicode Conversion and Upgrade on AS 400

Hi Guys,
We have a R/3 4.6C system on AS400 server. Within this year, we' like to change hardware and DB vendor (Oracle), in the meantime we also need to perform the UC and upgrade to ECC6.0.
What 's the best scenario? we have below suggestions.
1
Step1 - Heterogeneous migration and perform UC to new server and DB in one migration (export / import)
Step2 - Upgrade ECC6.0 Unicode
(not sure about this solution, is Unicode conversion to 4.6C without upgrade possible?????)
2
Step1 - Heterogeneous migration to new server and DB
Step2 - UC&UP
3
Step 1 - Heterogeneous migration to new server and DB
Step 2 - Upgrade to ECC non-unicode
Step3 - Unicode conversion to ECC unicode
????? which is better? 2 big question
- is Unicode conversion to 4.6C without upgrade possible?????)
- what's the difference between UC&UP and upgrade first and perform UC later, which is better?
Thanks very much
Lin
Edited by: ye zhulin on Mar 8, 2010 9:53 AM

Hi Lin,
I assume you have an EBCDIC database at the moment.
Point 1 is not possible, since 4.6C is not supported with Unicode.
The difference between CU&UC and a separate Upgrade and a later Unicode conversion is that CU&UC is done in one downtime. However you need to evaluate whether this is possible with your downtime requirements.
My recommendation would be to do the Migration and after that the CU&UC approach (if this is possible in a feasible downtime window - this is highly dependent on your system size / downtime requs / hardware capabilities).
Best regards,
Nils Buerckel
SAP AG
Edited by: Nils Buerckel on Mar 8, 2010 10:34 AM

U00C9 becomes u00C3 after unicode conversion

Hi all,
After the unicode conversion in ECC 6.0 server, when we download a file from SAP to unix, the character É becomes Ã in the file,
1 When cat the file, it shows as
1. cat testzzz
TRÃSOR
2. When more the same file, it displays a different character # more testzzz
TRM-CM-^ISOR
3. When we download the same file to our PC and open it in the notepad it looks ok.
TRÉSOR
4. In the SAP also this displays correctly as below
TRÉSOR
So when I was checking the locale parameter at unix level, I could see that its "C".
1. locale
LANG=
LC_CTYPE="C"
LC_COLLATE="C"
LC_MONETARY="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_MESSAGES="C"
LC_ALL=
From my understanding "C" doesn't support unicode, so we tried "univ.utf8" & fi_FI.utf8 for LC_CTYPE but no luck.
Did anyone faced this problem earlier.
Our OS HPUX 11.31 - IA64
Thanks & Regards
Senthil

Hi Senthil,
what terminal software are you using. I use putty and when I switch my terminal window translation settings to UTF-8, I get the correct text. Therefore I assume that your problem is your terminal emulation.
Regards
Ralph

Importing from an Oracle database converted from non-unicode to unicode - SSIS 2012

Hi,
I've some SSIS 2012 pkgs that read from a non-unicode Oracle database to a non-unicode SQL Server database.
Few days later, the Oracle database will be converted to unicode one and so I need to update the SQL database and the SSIS pkgs. Obiously no data conversion transformations are present in the pkgs. I'd like to avoid to add more of these data conversions.
As a first step, I'm trying to convert a SQL table to unicode format, but it isn't possible to convert non-unicode and unicode string data types.
I did not expect to have an error about the conversion from to non-unicode Oracle database (not yet converted) to unicode SQL Server database: a such conversion doesn't lost any information content. For me, it is right to have an error by from unicode to
non-unicode conversion.
Any suggests to solve this issue with a minimum development effort? Many thanks

Nope once you change datatypes to unicode you've to refresh metadata settings within SSIS packages for it to work fine. SSIS doesnt have the ability to do metadata changes at runtime. So someone has to update package metadata information to make them unicode
to make sure it works correctly after the changes.
What you can do is create test dbs in oracle and sql in uncode and create some modified packages based on it. Once you make changes to production dbs you need to move these modified copies also to production after making necessary config value changes like
servername,dbname,folder paths etc and then they will continue to work normally without causing any further downtimes to the customer.
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Migration Key for Unicode conversion

Hi,
I want to do a unicode conversion off ECC 6.0. The system was upgraded few days back from R/3 4.7 to ECC 6.0. Now it is required to convert the system to unicode. So to do the activity do we require Migration Key or any other approval from SAP for them to support us?
Thanks,
Suman

If you don't change the platform no migration key is required and no intervention or migration consultant necessary.
Depending on the number of languages/codepages it would probably make sense to get a Basis consultant (maybe remotely will be sufficient) to assist.
Markus

SAP R/3 4.6 C to ECC 6.0 Upgrade using CU &UC method- Unicode conversion

Basis Gurus
   I am working on upgrade from R/3 4.6C to ECC 6.0.
ECC 6.0 upgrade completed( still in non Unicode). Now I am in the process of Unicode conversion.
I have used following methods for the upgrade.
1. Combined Upgrade & Unicode conversion(CU & UC)
2. Resource minimized( as I am doing it in Sandbox).
As I understand I need to perform the DB export and Import now for the unicode conversion.
According to the Upgrade document, First I need to run Export using R3load in ECC6.0(Non unicode)
and then install Unicode system and import the same data file.
My understanding was, when I choose, Resource minimized, I need to run Export and import
in the same system.
Can you please help me , whether I need another Unicode system for import ??
Graham

Hi,
Dont get confused with upg strategy and unicode conversion.
In general Upgrade strategy (either downtime-minimized/resource minimized)
In unicode conversion you have export/import(exp/imp) of data concept
In CU&UC approach you have to do in a streach to complete migrate from old release to new realease ECC 6.00.
Using database independent (sapinst only) or Using database dependent (migration monitor or Distribution monitor)
It can be done in 2 ways.
If you dont have addtional server for unicode conversion
       1)you can either do exp on same hardware and take bakup and do import using the exp dump.
       2)Do exp on one server and prepare your target empty database on another server and complete imp of data.
Hope this is clear.
Regards,
Vamshi.

Regarding Conversion Of ABAP program from non unicode to uni code

Hi Can you please let me know the procedure for converssion of non unicode to unicode?
Thanks in advance,
zubera

Hi
The Link will be helpful to you.
Re: Upgrade 4.6 to ECC - What are the responsibilites
regarding Unicode influence in Standard programs
Very good document:
http://www.doag.org/pub/docs/sig/sap/2004-03/Buhlinger_Maxi_Version.pdf
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d37d1ad9-0b01-0010-ed9f-bc3222312dd8
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/589d18d9-0b01-0010-ac8a-8a22852061a2
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f8e316d9-0b01-0010-8e95-829a58c1511a
You need to use the transaction UCCHECK.
The report documentation is here
ABAP Unicode Scan Tool UCCHECK
You can use transaction UCCHECK to examine a Unicode program set for syntax errors without having to set the program attribute "Unicode checks active" for every individual program. From the list of Unicode syntax errors, you can go directly to the affected programs and remove the errors. It is also possible to automatically create transport requests and set the Unicode program attribute for a program set.
Some application-specific checks, which draw your attention to program points that are not Unicode-compatible, are also integrated.
Selection of Objects:
The program objects can be selected according to object name, object type, author (TADIR), package, and original system. For the Unicode syntax check, only object types for which an independent syntax check can be carried out are appropriate. The following object types are possibilities:
PROG Report
CLAS Class
FUGR Function groups
FUGX Function group (with customer include, customer area)
FUGS Function group (with customer include, SAP area)
LDBA Logical Database
CNTX Context
TYPE Type pool
INTF Interface
Only Examine Programs with Non-Activated Unicode Flag
By default, the system only displays program objects that have not yet set the Unicode attribute. If you want to use UCCHECK to process program objects that have already set the attribute, you can deactivate this option.
Only Objects with TADIR Entry
By default, the system only displays program objects with a TADIR entry. If you want to examine programs that don't have a TADIR entry, for example locally generated programs without a package, you can deactivate this option.
Exclude Packages $*
By default, the system does not display program objects that are in a local, non-transportable package. If you want to examine programs that are in such a package, you can deactivate this option.
Display Modified SAP Programs Also
By default, SAP programs are not checked in customer systems. If you also want to check SAP programs that were modified in a customer system (see transaction SE95), you can activate this option.
Maximum Number of Programs:
To avoid timeouts or unexpectedly long waiting times, the maximum number of program objects is preset to 50. If you want to examine more objects, you must increase the maximum number or run a SAMT scan (general program set processing). The latter also has the advantage that the data is stored persistently. Proceed as follows:
- Call transaction SAMT
- Create task with program RSUNISCAN_FINAL, subroutine SAMT_SEARCH
For further information refer to documentation for transaction SAMT.
Displaying Points that Cannot Be Analyzed Statically
If you choose this option, you get an overview of the program points, where a static check for Unicode syntax errors is not possible. This can be the case if, for example, parameters or field symbols are not typed or you are accessing a field or structure with variable length/offset. At these points the system only tests at runtime whether the code is sufficient for the stricter Unicode tests. If possible, you should assign types to the variables used, otherwise you must check runtime behavior after the Unicode attribute has been set.
To be able to differentiate between your own and foreign code (for example when using standard includes or generated includes), there is a selection option for the includes to be displayed. By default, the system excludes the standard includes of the view maintenance LSVIM* from the display, because they cause a large number of messages that are not relevant for the Unicode conversion. It is recommended that you also exclude the generated function group-specific includes of the view maintenance (usually L<function group name>F00 and L<function group name>I00) from the display.
Similarly to the process in the extended syntax check, you can hide the warning using the pseudo comment ("#EC *).
Applikation-Specific Checks
These checks indicate program points that represent a public interface but are not Unicode-compatible. Under Unicode, the corresponding interfaces change according to the referenced documentation and must be adapted appropriately.
View Maintenance
Parts of the view maintenance generated in older releases are not Unicode-compatible. The relevant parts can be regenerated with a service report.
UPLOAD/DOWNLOAD
The function modules UPLOAD, DOWNLOAD or WS_UPLOAD and WS_DOWNLOAD are obsolete and cannot run under Unicode. Refer to the documentation for these modules to find out which routines serve as replacements.
Regards
Anji

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.

Upgrade 4.6C to ECC 6.0; Unicode - non-Unicode -- Unicode

Hi,
My client has a R/3 4.6c UNICODE, he wants to upgrade to ECC6.0 UNICODE.
According to a SAP document, to upgrade, I upgrade directly to ECC 6.0 NON_UNICODE then convert the system to ECC 6.0 UNICODE.
I'm wonder why Unicode -> non-Unicode --> Unicode.
Regards,
Toan Do

"4.6C is not a unicode system ,ecc6.0 is an unicode system."
Actually, ECC 6.0 only has to be unicode if you are a new installation. If you are upgrading from a non-unicode system, you can upgrade to a non-unicode ECC 6.0 system, this is fully supported by SAP.
However, it is recommended that you perform the upgrade and unicode conversion at the same time. SAP is going to force us to unicod some day anyway.
We have just completed a technical upgrade from 4.7 to ECC 6 non-unicode, and now we are looking at a unicode conversion project. It would have added time to the original upgrade project, but it would have been worth it.
T

Conversion of non - unicode ECC6 to unicode ECC6

Hi,
We are planning to upgrade/ convert the non unicode version of our current SAP system to an unicode version of ECC 6. Is there any standard guide line or road map which we can follow to make this conersion successful.
Regards,
Vadivelan.N.

Hi,
check this thread :
non-unicode to unicode conversion
please kindly search first before asking a question...
hope it help you.
rgds,
Alfonsus Guritno W.N.

Pdf conversion from a non unicode system to a unicode system

Hi,
I have a BSP application that runs on a unicode system which retrieves data to be output in pdf from a non unicode sap system.
We get the data from the non unicode system through a RFC call and store data in table otfdata type itcoo, then we perform the conversion through the following:
perform pdfcnv_convertotf in program saplstxw
tables otfdata
pdf
using
'T'
archive_index
1
'T'
pdf_bytecount
app_tot_xstring
and then perform the hex conversion, but the printout is full of # chars. The good characters are followed by the # char. It looks like the unicode conversion is not good.
Thank you in advance for your help.
Best regards,
Donatella

Welcome to SDN
check out this weblog where Thomas Jung explains unicode conversion for excel, the same thing could be applied in your case as well
/people/thomas.jung3/blog/2004/08/09/bsp-download-to-excel-in-unicode-format
Regards
Raja

MDMP Unicode Conversion problem during ECC upgrade

hi Experts,
I met a problem when upgrade from 4.6c to ecc 6.
in 4.6c, some key users made some chinese written entries in table field while he/she was logon as English, so, the language field in this entry is "EN" although the actual language was written by chinese, after upgrade to ECC6, we found the chinese words became messy code, maybe it was due to the chinese were encoded by english codepage during conversion, my question is, how can I avoid this? I really don't want this happen in our PRD upgrade.
The second question is: if a field contains both chinese and english, then, which language should it be assigned? english or chinese? I'm afraid if we assign this word as "EN" in vocabulary, then, after upgrade, the chinese part will be messy code.
Thank you for your kind suggestions.
Freshman

Hi,
you can either use transaction SUMG (manually) to repair the entries ( you have to add the according table - please check unicode conversion guide for details) or you need to change the language key in the table to Chinese if you want the Unicode conversion to convert the data correctly.
To your second question: If the English texts are restricted to US7ASCII characters ("normal" English without special characters) those texts containing Chinese and English words can (and must !) be assigned to ZH, as US7ASCII characters are included in the Chinese code page.
Best regards,
Nilsn Buerckel

CRM unicode and ECC 6.0 Non unicode.

Hi All,
We have upgraded our system from 4.6C to ECC 6.0
Our ECC 6.0 is non unicode system. We are currently implementing CRM 5.0.
I want to know if we implement unicode CRM system, will there be any inconsistency as our ECC 6.0 is non unicode.
Regards,
Imran

Hi Imran:
I had a problem with middleware when going through a similar scenario to yours. The middleware functions were returning garbage when calling from CRM to ERP systems. See note 651497 which addresses this problem.
I implemented the fix by adding the following line to the beginning of function module BAPI_CRM_SAVE:
call function 'Z_MW_RFC_PING'.
Create a function group containing function module Z_MW_RFC_PING (code below):
FUNCTION Z_MW_RFC_PING .
*"*"Local Interface:
data:
lv_rfcdest type rfcdest.
* Read middleware parameter table to determine R/3 backend system
* name.
select single parval1
    into (lv_rfcdest)
    from smofparsfa
    where parsfakey eq 'CRMCFSOLTP' and
          parname eq 'CRMCFSOLTP'.
* If we get an RFC destination returned, PING it.
if sy-subrc eq 0.
    call function 'RFC_PING'
      destination lv_rfcdest.
endif.
ENDFUNCTION.
Note 777994 addresses some configuration on CRM system. In transaction R3AC6 on CRM system, make the following entries:
Key SMOF, parameter CODEPAGE_CHECK_OFF, value 'X';
Key R3A_COMMON, parameter CRM_SEND_XML, value 'X';
Key R3A_COMMON, parameter DATA_FORMAT, value 'XML'.
You should also do the following configuration:
In table CRMPAROLTP on ERP system set parameter CRM_SEND_XML_FOR_DEFAULT_DESTINATION, user CRM, value 'X'.
In table CRMRFCPAR on ERP system set the "Use XML" flag to 'X' for the CRM consumer. This also avoids code-page issues.
The above took care of conflicts in code-pages for my systems.
Regards,
D.

Non-unicode to Unicode conversion in ECC 6.0

Similar Messages

Maybe you are looking for