Unicode Conversion in a system landsacpe

Hello,
we are planning a unicode conversion of our productive system.
Our productive system is the source system of several systems like BI, mobile engine, webshop and so on.
About the problems of unicode conversion within the productive system I have found a lot of information.
But what about the scenario: If our productive system is unicode based and the satellite system do not have unicode, is that a problem.
Do we have to keep in mind to convert also the target/satellite system ?
And futher more do we have to analyse the program codes in the satellite system for BI (transfer structure,infoobject and so) ?
Do anybody have expierience with his system landscape ?
Thanks so far,
Komin

hello henning,
are you connected with the other systems via RFC?
if yes it should be no problem, because you can different in you rfc settings, between incoming non-unicode lettes and outging unicode
regards
stefan

Similar Messages

Unicode conversion in NonUnicode system

We are undertaking a project to make all Z* programs Unicode compatible in Non-unicdoe system.
Any suggestions to approach this tasks is welcome..
Thanks.

Below link will give idea about Unicode conversion
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c0ff71ca-1d11-2a10-6a93-88662a6e7bc9

Unicode Conversion: Building Target System in Advance

I already successfully ran ./distribution_monitor.sh -p on the source and have generated the relevant files (i.e., DBSIZE.TPL, DDLORA.TPL, and LABEL.ASC). Per the 'Distribution Monitor 1.9.1 Users' Guide, section 11.2.1, it says to select the "SAPinst option 'Installation using Migration Monitor'". When I start sapinst on the target and navigate attempt to create the target using Software Life Cycle Options, I cannot find "Installation using Migration Monitor" anywhere. I have tried multiple different options, hoping it would finally appear, but no luck. Your advice is appreciated.

Hi,
you need to select ... > system copy > <your DB>
Then under
> (Step 2) Define Parameters
you should tick the option:
> Start Migration Monitor manually
Best regards,
Nils Buerckel
SAP AG

Combined Upgrade and Unicode conversion of Sap 4.6C to ECC6.0

Hello all,
my project team intends to carry out a combined upgrade and unicode conversion of an SAP ERP 4.6C system with MDMP to ECC6.0 (no enhancement package). The system is running on Oracle 10.2.
In preparation for this upgrade, I have gone through the SAP notes 928729, 54801.
We need to get a rough estimate of the entire downtime so as to alert our end users. From the CU&UC documentation in 928729, I read up note 857081. However the program in this note cannot be used to estimate the downtime as my system is < SAP netweaver 6.20.
Is there any other SAP note or tool or program that I can use to estimate the downtime for the entire CU&UC? Thanks a lot!

Hi,
Combined upgrade depend upon number of factors like database size, resources on the server and optimization. In order to get idea of how much downtime, it will take, I would suggest you to do combined upgrade and unicode conversion on sandbox system which should be the replica of your production system. And try to optimize it. From there you can get approx. downtime required.
Also, please read combined upgrade and unicode conversion guides on http://service.sap.com/unicode@sap
Thanks
Sunny

Unicode Conversion ERP6.0 EHP3

Hello
We have for Dev. purpose an ERP6.0 EHP3 SP2 Non-Unicode System, now we should make an Unicode conversion with this system. Does someone have an Idea for me which Conversion Guide I have to use for this ? NW70-14 ?? NW7016 ?? NW701 ?? there must be an NW703 or not ??
thanks,
Stefan

Hi Stefan,
the Unicode conversion guides depend on the Basis/NW support packages / EhPs of your system.
If you have e.g. NW 7.0 EhP 1, then you need the guide 701.
The application support packages / EhPs are not relevant for the UC conversion (since it can be used for ERP,CRM,SCM, ...).
Best regards,
Nils Buerckel
SAP AG
Edited by: Nils Buerckel on Aug 25, 2010 2:46 PM

Changes in source system dyring Unicode conversion

Hi,
I've upgraded our R/3 non-Unicode installation to ERP 6.0 non-Unicode using CU&UC guide. Now I plan to do the export & import phase to migrate the source system to Unicode.
My question is, does the export phase (where the Unicode conversion actually takes place) do any changes in the source system? It' is a production system, and when something goes wrong or the time exceeds the limit I have for the export, I need to stop the export, put it back to production and try another time. So I need to be sure that the export itself doesn't do any changes to the source system.
Thanks in advance
Tomas

Hi Tomas,
the export simply "copies" the source system (and converts the data to Unicode) - it does not change it.
Therefore you can still use it after the export is finished.
Best regards,
Nils Buerckel
SAP AG

Combined upgrade and Unicode conversion for ECC5 MDMP system

Hello,
We are planning to do Upgrade and Unicode conversion of ECC5 MDMP system to ECC6 EHP4 Unicode. We are adopting Combined upgrade and Unicode conversion strategy to minimise the downtime.
In source version ECC5 we are in support pack level 6. Should we need to update the support pack to any target version to start with CU&UC or we can start with ECC5 with SP 6 itself.
Since we cant afford more downtime for support pack update also, is it ok to start with upgrade and unicode conversion with current version.
please advice.
Regards
Vinay

Hello Vinay,
please note that as a prerequisite the Basis SP should be accurate for an MDMP conversion.
There is no MUST to have the latest Basis SP, but without you could have severe issues in SPUMG.
On the application side, there are in most cases no hard requirements on the SP level.
Best regards,
Nils Buerckel
SAP AG

Job logs from the original system after Unicode conversion.

Dear Globalization experts,
We are doing Unicode conversion and would like to know, if the Job logs from the batch jobs, executed before conversion (system with a 1100 code page), would be readable in the Unicode system after the conversion. We will move job log files from the source to the target system. I . Thank you in advance for your help.
Best regards,
Alik Shapiro

Hi Alik,
I have strong doubts that this will work ...
From SAP notes 842767 and 901004 you can see, that spool data will not be converted properly by default.
In general this is valid for data stored in TemSe, as this is by definition temporary data (see for example http://help.sap.com/saphelp_nw70/helpdata/en/d9/4a8f9c51ea11d189570000e829fbbd/content.htm ).
However I actually did not test it, so I am not 100% sure.
Best regards,
Nils Buerckel
SAP AG

Export DB for Unicode conversion by SAPInst for distributed System

Hi,
In a distributed SAP system (CI and DB on separate host),
(1) I run SAPInst to export DB for unicode conversion via system copy option in DB host. After the parameter input up to General Unload settings e.g. Unicode Target system ? Yes, Parallel import/export ? No
The following warning/error occurred and drive K:\usr\sap\MD3 is located at CI host.
How to solve it?
WARNING 2007-09-04 22:53:39
Execution of the command "K:\JDKRoot\bin\java.exe -classpath K:\usr\sap\MD3\SYS\global\sltools\sharedlib\launcher.jar -showversion -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain
ebpshd01/sapmnt/MD3/SYS/global/security/lib/tools;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/sap.comsl.ut.infoprovider_lib.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/sap.comsl.ut.manager.offline.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/antlr.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/exception.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/jddi.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/logging.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/offlineconfiguration.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/opensqlsta.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/tc_sec_secstorefs.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/sap.comtcsdtcvlimpl.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/SDMutil.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/SLUtil.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/base.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/util.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/sqlserver.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/spy.jar -export -type=keydb "-expfile=D:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/DISTRIBUTED/AS/EXPDB/usages_data.xml" -log=UTL_load_usages.log -sid=MD3 -dsn=jdbc/pool/MD3 -ssprops=K:/usr/sap/MD3/SYS/global/security/data/SecStore.properties -ssk=K:/usr/sap/MD3/SYS/global/security/data/SecStore.key" finished with return code 1. Output:
java version "1.4.2_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_12-b03, mixed mode)
java.lang.NoClassDefFoundError: com/sap/engine/offline/OfflineToolStart
ERROR 2007-09-04 22:53:39
CJS-30074 Execution of UTL tool 'K:\JDKRoot\bin\java.exe -classpath K:\usr\sap\MD3\SYS\global\sltools\sharedlib\launcher.jar -showversion -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain
ebpshd01/sapmnt/MD3/SYS/global/security/lib/tools;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/sap.comsl.ut.infoprovider_lib.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/sap.comsl.ut.manager.offline.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/antlr.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/exception.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/jddi.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/logging.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/offlineconfiguration.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/opensqlsta.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/tc_sec_secstorefs.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/sap.comtcsdtcvlimpl.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/SDMutil.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/SLUtil.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/base.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/util.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/sqlserver.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/spy.jar -export -type=keydb "-expfile=D:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/DISTRIBUTED/AS/EXPDB/usages_data.xml" -log=UTL_load_usages.log -sid=MD3 -dsn=jdbc/pool/MD3 -ssprops=K:/usr/sap/MD3/SYS/global/security/data/SecStore.properties -ssk=K:/usr/sap/MD3/SYS/global/security/data/SecStore.key' aborts with return code 1. Check 'UTL_load_usages.log' and 'D:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/DISTRIBUTED/AS/EXPDB/UTL.java.log' for more information.
ERROR 2007-09-04 22:53:39
FCO-00011 The step getUsageTypes with step key |NW_Export|ind|ind|ind|ind|0|0|NW_Java_Export_Dialog|ind|ind|ind|ind|5|0|getUsageTypes was executed with status ERROR .
(2) I run Table Splitting Preparation in CI host by SAPInst before using DB export option, there are some files generated under the respective folder of sapinst_instdir. Will these files in CI be used when running SAPinst in DB host for DB export option? Is it required to move these files to DB host ? which is the target location if necessary ?
Regards,
Ricky Chan

=== Reformated it and added further information ===
Hi,
In a distributed (CI and DB on separate host) SAP system NW 7.0 ABAP+JAVA usage type MI ,
(1) I run SAPInst to export DB for unicode conversion via system copy option in DB host. After the parameter input screen up to "General Unload settings" e.g. Unicode Target system ? Yes, Parallel import/export ? No
The following warning/error occurred and drive K:\usr\sap\MD3 is only located at CI host. No such folder in DB host as no SAP instance was installed in it.
============ sapins_dev.log ============
WARNING 2007-09-04 22:53:39 Execution of the command "K:\JDKRoot\bin\java.exe -classpath K:\usr\sap\MD3\SYS\global\sltools\sharedlib\launcher.jar -showversion -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain
ebpshd01/sapmnt/MD3/SYS/global/security/lib/tools;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/sap.comsl.ut.infoprovider_lib.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/sap.comsl.ut.manager.offline.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/antlr.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/exception.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/jddi.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/logging.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/offlineconfiguration.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/opensqlsta.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/tc_sec_secstorefs.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/sap.comtcsdtcvlimpl.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/SDMutil.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/SLUtil.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/base.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/util.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/sqlserver.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/spy.jar -export -type=keydb "-expfile=D:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/DISTRIBUTED/AS/EXPDB/usages_data.xml" -log=UTL_load_usages.log -sid=MD3 -dsn=jdbc/pool/MD3 -ssprops=K:/usr/sap/MD3/SYS/global/security/data/SecStore.properties -ssk=K:/usr/sap/MD3/SYS/global/security/data/SecStore.key" finished with return code 1. Output: java version "1.4.2_12" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03) Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_12-b03, mixed mode) java.lang.NoClassDefFoundError: com/sap/engine/offline/OfflineToolStart
ERROR 2007-09-04 22:53:39 CJS-30074 Execution of UTL tool 'K:\JDKRoot\bin\java.exe -classpath K:\usr\sap\MD3\SYS\global\sltools\sharedlib\launcher.jar -showversion -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain
ebpshd01/sapmnt/MD3/SYS/global/security/lib/tools;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/sap.comsl.ut.infoprovider_lib.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/sap.comsl.ut.manager.offline.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/antlr.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/exception.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/jddi.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/logging.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/offlineconfiguration.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/opensqlsta.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/tc_sec_secstorefs.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/sap.comtcsdtcvlimpl.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/SDMutil.jar;K:/usr/sap/MD3/SYS/global/sltools/sharedlib/SLUtil.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/base.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/util.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/sqlserver.jar;K:/usr/sap/MD3/SYS/exe/nuc/NTAMD64/mssjdbc/spy.jar -export -type=keydb "-expfile=D:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/DISTRIBUTED/AS/EXPDB/usages_data.xml" -log=UTL_load_usages.log -sid=MD3 -dsn=jdbc/pool/MD3 -ssprops=K:/usr/sap/MD3/SYS/global/security/data/SecStore.properties -ssk=K:/usr/sap/MD3/SYS/global/security/data/SecStore.key' aborts with return code 1.
Check 'UTL_load_usages.log' and 'D:/Program Files/sapinst_instdir/NW04S/LM/COPY/MSS/EXP/DISTRIBUTED/AS/EXPDB/UTL.java.log' for more information.
ERROR 2007-09-04 22:53:39 FCO-00011 The step getUsageTypes with step key |NW_Export|ind|ind|ind|ind|0|0|NW_Java_Export_Dialog|ind|ind|ind|ind|5|0|getUsageTypes was executed with status ERROR .
============
The content of file UTL.java.log:
java version "1.4.2_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_12-b03, mixed mode)
java.lang.NoClassDefFoundError: com/sap/engine/offline/OfflineToolStart
=============
File 'UTL_load_usages.log' does not exist in the sapinst_dir folder.
(2) I run Table Splitting Preparation in CI host by SAPInst before using DB export option, there are some files generated under the respective folder of sapinst_instdir.
Will these files in CI be used automatically when running SAPinst in DB host for DB export option?
Is it required to move these files to DB host manually? Which is the target location if necessary ?
(3) Any guide with detail on the preparation of tool or files in a standalone DB host prior to Export DB from it with SAPInst.
Regards,
Ricky Chan

FJS-00003 TypeError: fsTableSplit for system copy and unicode conversion

Dear Sir:
Current I want to do the system copy for unicode conversion, but i go the following message on phase table splitting preparation. did you got this message before? Thanks!
Br,
GX
ERROR      2009-02-05 18:03:12.214 [iaxxejsbas.cpp:204]
FJS-00003 TypeError: fsTableSplit has no properties (in script TableSplitter|in
d|ind|ind|ind, line 69516: ???)
TRACE      2009-02-05 18:03:12.294 [syuxctask.cpp:1382]
           CSyTaskImpl::start(bool)
A child process has been started. Pid = 5708
ERROR      2009-02-05 18:03:12.344 [sixxcstepexecute.cpp:951]
FCO-00011 The step ReadTableSplitList with step key |TableSplitter|ind|ind|ind|
ind|0|0|ReadTableSplitList was executed with status ERROR .

Hi,
Table split option is used for very large databases, you can use normal export/import method.
What is your database size ?
I had done UC for databases upto 1.5 TB, never used table split technique.
Keep it simple while doing complex tasks.
Regards
KT

Error while database export in package SAPDODS_33 (Unicode conversion)

Hello,
I am performing Unicode conversion on an upgraded BI 7.0 system. This is running on AIX/DB2.
When I take database export for conversion, one package fails (SAPDODS_33) with error "The file system is full". In fact, df -k doesn't show that any file system is full.
I am taking the export to the following location: /db2/BWS/sapdata/EXPORT_DIR
There are 3 system-managed temporary tablespaces: PSAPTEMP, PSATEMP16 & SYSTOOLSTMPSPACE which were residing in /db2/BWS/saptemp1/NODE0000. This was getting full during the export. Now these temp.tablespaces have been relocated to a new file system of size 15GB.
But still the package SAPDODS_33 doesn't get exported. Could you please let me know how to solve this issue?
Thanks a lot!
Sundar.
=====================================================================================
SAPDODS_33.log
(DB) INFO: connected to DB
(rscpsumg) Please look also into "SAPDODS_33012.xml".
(rscpMC) Warn: env I18N_NAMETAB_TIMESTAMPS = IGNORE
(rscpMC) Warn: UMGCONTAINER has 1 problems.
(rscpMC) Warn: Global fallback code page = 1160
(rscpMC) Warn: Common character set is not 7-bit-ASCII
(rscpMC) Warn: Collision resolution method is 'fine'
(rscpMC) Warn: R3trans code pages = Normal
(rscpMC) Warn: EXPORT TO ... code pages = Normal
(rscpMC) Warn: Source is 'MDMP'
(rscpMC) Warn: I18N_NAMETAB_NORM_ALLOW = 0
(rscpMC) Warn: I18N_NAMETAB_NORM_LOG   = 0
(rscpMC) Warn: I18N_NAMETAB_ALT_ALLOW = 0
(rscpMC) Warn: I18N_NAMETAB_ALT_LOG    = 0
(rscpMC) Warn: I18N_NAMETAB_OLD_ALLOW = 0
(rscpMC) Warn: I18N_NAMETAB_OLD_LOG    = 0
(GSI) INFO: dbname   = "BWS
(GSI) INFO: vname    = "DB6                             "
(GSI) INFO: hostname = "UNKNOWN
(GSI) INFO: sysname = "AIX"
(GSI) INFO: nodename = "itmlartdev01x"
(GSI) INFO: release = "3"
(GSI) INFO: version = "5"
(GSI) INFO: machine = "002417CA4C00"
(GSI) INFO: instno   = "0020169337"
(EXP) ERROR: DbSlExeRead failed
rc = 99, table "/BIC/B0000786000"
(SQL error -968)
error message returned by DbSl:
SQL0968C The file system is full. SQLSTATE=57011
(DB) INFO: disconnected from DB
/usr/sap/BWS/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/BWS/SYS/exe/run/R3load: END OF LOG: 20071211053119
p/sapinst/sapinst_instdir/NW04S/LM/COPY/DB6/EXP/CENTRAL/AS-ABAP/EXP #

Hi Sundar,
if the problem is due to a high temp space usage. The root cause is typically the
sort during export. If the table is large, the sort spills to temp.
You can avoid the sort by doing an unsorted export or tweak the DB2 optimizer to use the primary key to do the sort.
Before DB2 9, you can reduce the OVERHEAD tablespace parameter to zero. Return this value to its previous value after the successful export. This is a indirect hint to the optimizer that random IOs are cheap. This might not help.
With DB2 9, this should not happen, because the DB2_OPT_MAX_TEMP_SIZE=10240 registry variable is set under DB2_WORKLOAD=SAP which limits the temp space usage to 10GB if possible. You can reduce this parameter further if necessary. Another problem could be that the optimizer has chosen the wrong temp space. The optimizer choses the temp space with the largest amount of pages (not size).
Regards, Jens

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.

Preparing for upgrade and Unicode conversion while on 4.6c

We're currently on 4.6c and preparing to upgrade to ERP 2005 and do a Unicode conversion. I'm trying to compile a list of coding techniques that can used in 4.6c that will minimize changes needed for Unicode. Does anyone have such a list?
Some things I've discovered reading about Unicode include:
1) Use GUI_UPLOAD and GUI_DOWNLOAD rather than WS_UPLOAD and WS_DOWNLOAD.
2) Structures or table headers that contain non-character data need to be identical when moving, comparing, selecting into, updating from, etc. This includes not moving structures/tables with non-character data to a character field or vice-versa.
3) Offsets can't cross non-character data.
4) Assign statement with offset must specify a length.
5) Open dataset must specify "FOR INPUT", "FOR OUTPUT", "FOR APPENDING", or "FOR UPDATE". It no longer defaults to FOR INPUT when omitted.
6) Many implicit conversions from char to numeric are no longer allowed. Use explicit conversion instead; such as the move statement.
I know there are others. Any help would be appreciated.
Regards,
Mark Perrey

Hai Mark
Check the following F.M Replacents
Upgrade Error Details     Suggestions
Function Module "DOCUMENT_REGISTRY_PROGRAM"not found in the target system     Suggest to replace this FM with the function module CV120_GET_APPL_FROM_REGISTRY.
Function Module "RP_HIRE+FIRE"not found in the target system     Suggest to replace this FM with the function module RP_HIRE_FIRE .
Function Module "ME_READ_HEADER_SINGLE" not found in the target system     Suggest to replace this FM with the function module ME_EKKO_SINGLE_READ.
Function Module "ME_READ_ITEM_SINGLE" not found in the target system     Suggest to replace this FM with the function module ME_EKPO_SINGLE_READ.
Function Module "RZL_ALERT_CONTROL" not found in the target system     Function Module "RZL_ALERT_CONTROL" is not available in the Enterprise Version. Suggest to use the function module "TH_SEND_ADM_MESS" to acheive the same functionality of "RZL_ALERT_CONTROL".
Function Module "MM_SELECT_ADDRESS" not found in the target system     Suggest to replace this FM with the function module MM_SELECT_PARTNER.
Function Module "MM_READ_ADDRESS" not found in the target system     Suggest to replace this FM with the function module MM_PARTNERS_FOR_MESSAGING
Function Module "ME_VALUES_T161" not found in the target system     Suggest to replace this FM with the function module HELP_VALUES_BSART.
Function Module "ME_VALUES_T024W" not found in the target system     . Suggest to replace this FM with the function module HELP_VALUES_WERKS.
Function Module "SD_PACKING_REFRESH" not found in the target system     Suggest to replace this FM with the function module HU_PACKING_REFRESH.
Function Module "SD_PACKING_RENAME" not found in the target system      Suggest to replace this FM with the function module V51P_PACKING_RENAME.
Function Module "RV_EXPORT_CONTROL_UPDATE" not found in the target system     Suggest to replace this FM with the function module RV_EXPORT_CONTROL_UPD_PREPARE.
Function Module "RV_INVOICE_COPY" not found in the target system     Suggest to replace this FM with the function module RV_SALES_DOCUMENT_COPY.
Function Module "SD_SCHEDULE_AGREEMENT_PACKING" not found in the target system     Suggest to replace this FM with the function module HU_PACKING_SALES_PROPOSAL.
Function Module "SERIAL_RENUM_WV" not found in the target system     Suggest to replace this FM with the function module IWOL_WV_SWITCH_NUMBER.
Function Module "CUD0_DISPLAY_CONFIGURATION" not found in the target system     Suggest to replace this FM with the function module VC_I_DISPLAY_CONFIGURATION.
Function Module "SD_PACKING_CREATE" not found in the target system     Suggest to replace this FM with the function module V51F_PACKING_CREATE.
Function Module "FI_ARCHIVE_CHECK_DOC" not found in the target system     Function Module FI_ARCHIVE_CHECK_DOC is not available in the Enterprise Version. Suggest to replace this FM with the function module FI_DOCUMENT_ARCH_CHECK_DOCS.
Function Module "OPEN_FI_CHECK" not found in the target system     Function Module OPEN_FI_CHECK is not available in the Enterprise Version. Suggest to replace this FM with the function module OPEN_FI_PERFORM_******_E.
Function Module "SD_PACKING_UPDATE"not found in the target system     Function Module SD_PACKING_UPDATE is not available in the Enterprise Version. Suggest to replace this FM with the function module HU_PACKING_UPDATE.
Function Module "F4_MACO" is being used in the program     Function Module "F4_MACO" is not available in the Enterprise Version. Since the Matchcode objects are not used in the Enterprise Version, Suggest to replace this FM with Search help's Value Request function module F4_SEARCH_HELP.
Function Module "SWZ_AI_RELEASE_S" is used in the program     Suggest to use the function module "SWZ_AI_RELEASE" instead of "SWZ_AI_RELEASE_S".
Function Module "SWW_WI_ORGTASK_READ" is used in the program      Suggest to replace this FM with the function module RH_WI_ORGTASK_READ.
Function Module "RH_READ_EXCEL_PATH" is being used in the program     Suggest to replace this FM with "RH_CHECK_EXCEL_SUPPORT".
Function Module "RZL_ALERT_CONTROL" is used in the program     Function Module "RZL_ALERT_CONTROL" is not available in the Enterprise Version. Suggest to use the function module "TH_SEND_ADM_MESS" to acheive the same functionality of "RZL_ALERT_CONTROL".
Function Module "CONVERT_TO_OTHER_CURRENCY" is used in the program     Suggest to ruse the function module "CONVERT_TO_LOCAL_CURRENCY" for currency conversion.
Function Module "LOAN_TABLECONTROL_SCROLLING" is not available in the Enterprise Version.      Suggest to replace this FM with the function module SCROLLING_IN_TABLE.
CALL FUNCTION 'DOWNLOAD' used in program is obsolete in target system.     "DOWNLOAD function module is obsolete and result in errors on Unicode systems or on systems that may potentially be Unicode enabled.
Suggest to use the unicode enabled methods
FILE_SAVE_DIALOG and GUI_DOWNLOAD
from class CL_GUI_FRONTEND_SERVICES.
Note:
However, to support existing applications, a compatibility mode was added to the function module(enhanced with Support Package) that will forward calls to DOWNLOAD to the new GUI_DOWNLOAD functions."
CALL FUNCTION 'HELP_VALUES_GET_NO_DD_NAME' used in program is obsolete in target system.     "HELP_VALUES_GET_NO_DD_NAME function module is obsolete and result in errors on Unicode systems or on systems that may potentially be Unicode enabled.
Suggest to use the function module F4IF_INT_TABLE_VALUE_REQUEST in the target system."
CALL FUNCTION 'POPUP_TO_CONFIRM_LOSS_OF_DATA' used in program is obsolete in target system.     "POPUP_TO_CONFIRM_LOSS_OF_DATA is obsolete in the target system.
Suggest to use function module POPUP_TO_CONFIRM."
CALL FUNCTION 'POPUP_TO_CONFIRM_STEP' used in program is obsolete in target system.     "POPUP_TO_CONFIRM_STEP is obsolete in the target system.
Suggest to use function module POPUP_TO_CONFIRM."
CALL FUNCTION 'WS_DOWNLOAD' used in program is obsolete in target system.     "WS_DOWNLOAD function module is obsolete and result in errors on Unicode systems or on systems that may potentially be Unicode enabled.
Suggest to use the unicode enabled GUI_DOWNLOAD function module.
Note:
However, to support existing applications, a compatibility mode was added to the function module(enhanced with Support Package) that will forward calls to WS_DOWNLOAD to the new GUI_DOWNLOAD function."
CALL FUNCTION 'WS_FILENAME_GET' used in program is obsolete in target system.     "WS_FILENAME_GET function module is obsolete, and results in errors on Unicode systems.
Suggest to use FILE_OPEN_DIALOG und FILE_SAVE_DIALOG Unicode-enabled methods of the cl_gui_frontend_services class.
Note:
New applications should restart on these methods instead of the function module. The function module is extended by a Support Package so that it diverts calls to the methods without the application having to be changed."
CALL FUNCTION 'WS_UPLOAD' used in program is obsolete in target system.     "WS_UPLOAD function module is obsolete and result in errors on Unicode systems or on systems that may potentially be Unicode enabled.
Suggest to use the unicode enabled GUI_UPLOAD function module.
Note:
However, to support existing applications, a compatibility mode was added to the function module(enhanced with Support Package) that will forward calls to WS_UPLOAD to the new GUI_UPLOAD function."
Function parameters EBENE, GRUPP, DATE_LOW, DATE_HIGH, BANKK. BUKRS, S_BUKRS, S_DISPW in function module CASH_FORECAST_TR_SELECT_ITEM is missing in the target system.     "Function Module CASH_FORECAST_TR_SELECT_ITEM is no longer used, instead it has been split based on the functionalities.
Suggest to use function module
1) CASH_FORECAST_PR_SELECT_ITEM for Payment Arrangements.
2) For TR, WP, DA use function module CASH_FORECAST_TR_ITEM_2.
The IMPORT and TABLES parameters of the above 2 function modules are almost same as CASH_FORECAST_TR_SELECT_ITEM.
The IMPORT parameter BUKRS is not available in the above 2 function modules. Hence suggest to change the coding accordingly."
Import parameter BUKRS in function CASH_FORECAST_LO_SELECT_ITEM is missing in the target system.     "Import parameter BUKRS in function CASH_FORECAST_LO_SELECT_ITEM is not available in the target system.
Also the coding in Function Module based on the parameter BUKRS has been removed, instead the TABLES parameter S_BUKRS and S_GSBER has been used.
Suggest to check the coding in the program accordingly.
Import parameter BUKRS in function CASH_FORECAST_RE_SELECT_ITEM is missing in the target system.     "Import parameter BUKRS in function CASH_FORECAST_RE_SELECT_ITEM is not available in the target system.
Also the coding in Function Module based on the parameter BUKRS has been removed, instead the TABLES parameter S_BUKRS and S_GSBER(new parameter) has been used.
Suggest to check the coding in the program accordingly.
Function Module HELP_VALUES_GET_WITH_MACO is obsolete in target system     Suggest to use F4IF_FIELD_VALUE_REQUEST
Function Module G_OBJECT_GET is obsolete in target system.     Suggest to Use G_INTERVAL_GET_NEXT
Function Module READ_COSTCENTER is obsolete in target system     Suggest to Use K_COSTCENTER_SELECT_SINGLE
Function Module K_BUSINESS_PROCESS_READ_MULTI is obsolete or not available in target system     Suggest to Use K_PROCESSES_SELECT_TAB
G_SET_AVAILABLE     Suggest to Use G_SET_GET_INFO
Function Module G_SET_DOUBLE_CHECK is obsolete or not available in target system     "DO NOT CALL THIS FUNCTION MODULE
FROM 4.0A VERSION ,THIS PROBLEM WILL NOT OCCUR"
Function Module HELP_VALUES_GET is obsolete or not available in target system     Suggest to Use F4IF_FIELD_VALUE_REQUEST
G_SELECT_SET     Suggest to Use G_SET_SELECT
Function Module G_SET_AVAILABLE is obsolete or not available in target system     Suggest to Use G_SET_GET_INFO
Function Module NAMETAB_GET is obsolete or not available in target system     Suggest to Use DDIF_FIELDINFO_GET
Function Module DD_GET_DD03P is obsolete or not available in target system     Suggest to Use DDIF_FIELDINFO_GET / DDIF_TABL_GET
CALL FUNCTION 'POPUP_TO_CONFIRM_WITH_MESSAGE' used in program is obsolete in target system.     Suggest to use function module POPUP_TO_CONFIRM.
CALL FUNCTION 'POPUP_TO_DECIDE' used in program is obsolete in target system.     Suggest to use function module POPUP_TO_CONFIRM.
Function Module HELP_VALUES_GET_WITH_TABLE is obsolete or not available in target system     Suggest to Use F4TOOL_F4FUNCTION_BRIDGE
Function Module CLPB_EXPORT is obsolete or not available in target system     "Suggest to Use Suggest to use the unicode enabled methods
CLIPBOARD_EXPORT from class CL_GUI_FRONTEND_SERVICES."
Function Module SAP_TO_ISO_MEASURE_UNIT_CODE is obsolete or not available in target system     Suggest to Use UNIT_OF_MEASURE_SAP_TO_ISO
Regards
Sreeni

Unicode conversion in situ

Hi SCN,
I'm looking at the possibility of running a Combined Upgrade & Unicode Conversion (CUUC) in-situ; i.e. without a migration to new hardware.
However in all my years of SAP Basis projects any Unicode conversion I've seen has involved a migration to new hardware (which makes good sense as the process is the same as an OSDB migration with R3load/MigMon).
What I want to know is - has anyone ever run one in-place. I.e. keeping the same server and running the CUUC entirely inplace?
This seems logically problematic as you need a target system to import to.
I can imagine a process along these lines though...:
1. Take SAP layer offline
2. Run full backup of system
3. Export system
4. Drop database* (to make clean ready for new import)
5. Run SPUMG/SUMG/SAPINST to setup Unicode database ready to receive import...
6. ....and continue to run import into that database
7. Complete Unicode conversion process
However the big issue here for me is
(a) *dropping the live production system is far from attractive.... I'm presuming everyone would do as I've always seen and combine this with a migration to new improved hardware, so that a backout to the old system is simple
(b) I'm not sure at what point with the SAP tools (SPUMG/SUMG/SAPINST) this process would become convoluted with it all being in-situ on the same box. I.e. I'm not sure if it's something the SAP tools are really designed to cater for.
Any input/discussion on these points would be very welcome.
Regards, doonan_79

FYI Community. Feeling after reading and research is to use a temorary server to import unicode converted system data into; then swing disks back to the original host. Making all required hostname updates during the process.
Allowing for parallel export/import, but going back to the original configured host to complete the process.

How to go for Unicode conversion?

Hi All,
Presently i'm upgrading my SAP 4.7 system (6.2 WAS) in to ERP 2004 (6.40 WAS), which is an non-unicode upgrade.
Now should i first complete Unicode conversion or apply the latest SP stack.
Also please tell me how this Support pack will affect me in Unicode conversion?
Order of this steps will be really helpful for smooth flow of work
Thanks in Advance

If you have already completed your upgrade, the best practice would be to install the SP stack first in order to have the latest updates available for the unicode migration tools. Then proceed with the unicode migration. There are slight differences in the process between support packages where you may have to create a migration program manually in an older support package and the very same migration program is included in the later support package. SAP publishes separate unicode migration guides, based on the support package level, due to these updates.

Unicode Conversion in a system landsacpe

Similar Messages

Maybe you are looking for