MDMP: TWIN Upgrade + Unicode conversion

Hello ,
We have adopted twin upgrade and unicode conversion method and at present we are converting the twin system to unicode conversion.
In Twin system we have completed SPUMG 7 scans. Whether i need to run UMG_TWIN_CREATE_TRANSPORT now to save the results for twin preparation run or i need to perform this step after Additional preparatory step.
Kindly suggest
Regards
Vinay

Hi Vinay,
Excerpt from the UCG:
2.4 Final Preparation Steps
2.4.1 SPUMG Updates
If there is a time difference between the scan and the database export, it may happen that a new table has been created or a Support Package has brought a new table with it. In such a case, the preconversion must be rerun right before the export is carried out to ensure that the data change is reflected in the Export Control Table.
End excerpt
Hence this step is necessary in case of DB changes (e.g. new tables with or without content).
Therefore if you have significant changes, I would recommend to create the twin transport after this step.
However this step has to be repeated in the PRD system as well (see TU&UC-Guide) to reflect the changes between Twin and PRD system. In order to minimize downtime, the differences between the two systems should be small.
Best regards,
Nils Buerckel
SAP AG

Similar Messages

Combined upgrade & Unicode conversion.

Hi
I need some suggestions for my concerns: I would appreciate, if you reply ASAP for below situations and actions.
Current system: HP unix DB: Oracle10.2.0.2
SAP 6.20 with SP 61, single code page
strategy: resource minimized.
Upgrading from 4.7 was 6.20 to ECC6.0 with CU & unicode conversion.
we ran UCCHECK and provide the list to ABAP, but they are not modifying now.
Mean while we started the preconversion steps for unicode conversion and completed. SPUMG.
Upgrade prepare is completed and currently in begining of down-time.
so far ABAP programs are not unicode complaint!!!
we don't know, when would they modify??
If we complete the upgrade and post upg steps for ecc 6.0 and
pre coversion steps for unicode.
is it a problem, if the ABAP programs are not modified yet, can it be done after conversion and before export???
or after import??
Your time is highly appreciated.
Thanks
creddy

Per CU&UC guide, you can do some conversions in parellel
and after upgrade, you have to perform preparation steps and then export, that is what i am following.
What you said is right for single code page conversion method.
upgrade first
unicode conversion second.
I am following CU&UC method.
Thanks
reddy

Combined Upgrade & Unicode Conversion (Consistency & Scans)

Hi
We are doing a combined Upgrade & UC conversion. 4.6C NUC to ECC6 eHP7 UC with an SLO MWB for Data. We have made a clone (System copy) of 4.6C and are running the SPUM4 tool on it (as per the guide) . My question: after I export the glossary from the Cloned 4.6C system and import it into the productive 4.6C system - do I have to run the Consistency Checks & SPUM4 Scans in the productive system or can this be avoided. I know I need the glossary in production so that delta data loads to the MWB can use the glossary, but do I need to run the scans in Production.
Thank you in advance for your help in this question
Robert

Hi Robert,
SPUM4 needs to be executed on the PRD system. Hence you need to import the vocabulary (you called it glossary) and then all the scans need to be executed in CU&UC. This is to ensure that all data on your system is scanned and ends up in the vocabulary / reprocess logs.
Best regards,
Nils Buerckel

Twin Upgrade to NW7.3

We are doing a Twin Upgrade to NW7.3 from 7.01.
We only find the Twin Upgrade Guide for ECC6 (target release).
Are there links for Twin Upgrade for NW7.3?
Thanks for help.

Hello Jennifer,
Refer to the note Note 959698 - Twin Upgrade & Unicode Conversion and attached document in the note. Looks like, TU is only on ECC system and from 7.01 Unicode conversion and upgrade has to be done seperately.
Thanks,
Arjun

Twin upgrade and Unicode conversion: UMG_TWIN_PROCESS_LOGS Could not adjust

Hello,
We have done Upgrade of 4.5B MDMP system to ECC6 EHP4 MDMP and currently Unicode conversion in progress.
We adopted TU&UC. Now we are importing twin spumg results of last run to our procution copy system.
During running UMG_TWIN_PROCESS_LOGs. we are facing some errors
INDX lines to be corrected:               4.417
INDX lines corrected      :               4.144
IN that Could not adjust:        SMODISRC, we are referring Note 991654 - UMG_TWIN_PROCESS_LOGS shows errors on SMODISRC.
please suggest for other error tables below
Could not adjust:        VARI 1160
Could not adjust:        MONI
Could not adjust:        BDLDATCOL 1160 DLR000000492TSK0020305440PV1     0000000000DIFF    BDL   000614a01822pr                        000000Field List          S1100
Please suggest what action can be taken
Regards
Vinay

Hi Vinay,
did you already check attachment of SAP note 765475 - "Unicode conversion Troubleshooting guide" ?
Excerpt:
...check if the entries in
<table name> still exist. In some cases those entries only exist in the
Twin System but no longer in the Production System. In such cases the
message is not an error message but only information.
Best regards,
Nils Buerckel
SAP AG

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.

4.7EEx1.10 to ECC6.0 upgrade and Unicode conversion

Hi Experts,
We are going to initiate the upgrade from next month onwards. Subsequently i have started preparing the plan and strategy for the same.
As our current setup is 4.7EEx110/Win 2003 R2-64 bit/Oracle 10.2.0.4.0 (Non unicode). And we have recently migrated on to this setup from WIn2k 32 bit. Also the current hardware is Unicode compatible.
With respect to strategy for achieving this Upgrade and Unicode conversion, i am planning as follows.
Step 1) Perform Unicode conversion on the current landscape (Both Export/import on the same servers)
Step 2) Setup Temporary landscape as part of Dual maintenance strategy and migrate data from the current systems to temporary systems using backup/restore method.
Step 3) Perform the SAP version upgrade on the current landscape and setup transport routes from temporary to current landscape in order to keep it in sync
Step 4) after successful upgrade, decommission the temporary landscape
Please provide your suggestions and valuable advices if there is anything wrong with my strategy and execution plan.
Regards,
Dheeraj

Hi,
Thanks. As i have already referred these notes as i am seeking advise with respect to my upgrade approach.
However i have planned to perform in the following manner.
1) Refresh Sandbox with Prod data and perform Upgrade to ECC6.0 EHP5 & subsequently Unicode conversion on the same server (Since both export & Import has to perform on the same hardware as we have recently migrated on this hardware which is Unicode compatible)
2) Setup temporary landscape for DEv & QAs and establish transport connection to Production system in order to move urgent changes
3) Keep a track of the changes which have transported during upgrade phase so that the same can be implemented in the upgraded systems i.e. Dev & QAS
4) After Sandbox Migration and signoff, we will perform Dev & QAS upgrade & unicode conversion on the same hardware (Note: Since these are running on VMware can we export the data from the upgraded system and import on to a new VM?)
5) Plan for production cutover and Upgrade the Prod system to ECC6.0 Ehp5 and then Unicode conversion. As i am planning to perform upgrade over the weekend and then Unicode conversion activity in the next weekend (Is it a right way?)
My Production setup: DB on one Physical host and CI on separate Virtual host
6) After the stabilization phase, we are planning for OS & DB upgrade as follows:
a) Windows upgrade from 2003 R2 to Windows 2008 R2
b) Oracle Upgrade from 10.2 to 11.2
If anyone thinks that there is anything wrong with my above approach and need changes then please revert.
I have one more doubt as I am going to upgrade 4.7EEx110 (WAS 620, Basis SP64) to ECC6.0 EHp5.As I presume that I can straight away upgrade from the current version to ECC6.0 Ehp5 without installing EHP. Kindly confirm
Thanks

ABAP and Kernel Patches for Upgrade and Conversion in 4.6C

Hi,
We are in a process of upgrade and unicode conversion for the source release 4.6C (Kernel 46D_EXT Patch 2225).
"Combined Upgrade&Unicode Conversion Guide" for "SAP Basis 4.6C u2192 SAP NetWeaver 7.0 application Server ABAP Unicode Including Enhancement Package 1 Support Package 01 - 06" , In Software Requirements step, it says
"3. Import 4.6D Kernel patch 2326 from SAP Service Marketplace according to SAP Note 19466"
We wanted to know whether "IT IS ABSOLUTELY NECCESSARY TO GO FOR THE KERNEL PATCH 2326". We dont have "EBCIDIC code pages" in our MDMP system.
We need to know becauase we are also doing OS migration from AIX to Sun and this step will add to our production downtime.
Please advice what are the other causes we should go for the kernel 2326.
Regards

Hello Mr. Nils Buerckel,
Thanks for the reply.
We wanted to be very sure whether we should used Kernel 46D Kernel patch 2326 (As it is specifically mentioned in the SAP CU&UC guide and in SAP Note 867193, It is mentioned that "This patch contains enhancements that are required to execute the "INDX Analysis" scan)
OR
Can we go for the latest kernel patch avaialable at market place? And Will the latest kernel patch also contains the "enhancements that are required to execute the "INDX Analysis" ?
Please reply
Thanks

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.

Unicode Conversion for SAP BI

Hi
We are upgrading out SAP BW 3.1 system to SAP NW 7.0. We are also planning to do a Unicode conversion of the upgraded system.
Please let me know the following:
1. What extra tests we need to do for Unicode Conversion
2. If you have done a Unicode conversion, please share the errors that you have got after the conversion, and the possible solutions.
Best Regards,
Rajib

hi,
Please refer
SAP Note Number: 928729 : Combined Upgrade & Unicode Conversion (CU&UC)
https://wiki.sdn.sap.com/wiki/display/unicode/ChallengesinBIUnicodeconversion
Below is the link for R/3... but still will give you some insight.
/people/tikkana.akurati/blog/2009/02/27/combined-upgrade-and-unicode-conversion-cuuc-cutover-project-plan-execution
This will also help you understand more about unicode...
/docs/DOC-8284#section5 [original link is broken]
Hope this helps
Regards
Raj

Print Servers Impact after unicode conversion

Hi
We are performing an CUUC from 4.6C to ECC 6.0
Our customer has around 4-5 windows special print servers which are used for chinese, japanese, korean printing..etc.
After the upgrade & unicode conversion
- Do we still need to use all these 4-5 special print servers for each languages seperatly? or
- We shall consolidate all these print servers into one print server? Or
- We don't need to have any print servers, all the print queues can be pointed to unix print queues and then to the printers directly.
Kindly advise
Thanks & Regards
Senthil

I would think you could consolidate the print servers, but you still need the separate printers/device types in SAP. We use a single print server for EN/DE/ZH but have different SAP printers (usinging different device types) for EN/DE & ZH printers.

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

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

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

MDMP unicode conversion - Vocabulary maintenace

Hello,
W have upgraded 4.5B MDMP system to ECC4 EHP4 and now we are in process of unicode conversion.
please advice on as specified below.
In SPUMG Scan process, we have completed the following scans:
a) Tables without language Info
b) Tables with Ambiguous language Info
c) Indx Analysis
For maintaining vocabulary we have implemented notes 756534 & 756535, 871541. and Tables with language are also scanned. While handling vocabulary the system has displays 539158 with duplicates and 189314 when duplicates are discarded, which doesnot assigened any languages. We have 9 acive languages.
As per Unicode conversion document i left out with only 2 more option a) HInt management b) Manual assignment
How to handle this? is this a normal situation or any correction can be done?
Thanks and Regards
Vinay

Hi Vinay,
This Thread belongs to the Unicode forum:
Internationalization and Unicode
In my opinion one of the best and most efficient possibility to reduce the number of words
is to make use of hints. Please follow the Unicode Conversion Guide and SAP note 1034188.
Application colleagues should be contacted in order to find proper hints.
Please also note that report umg_vocabulary_statistic or um4_vocabulary_statistic is the best tool to evaluate tables for hint processing.
And the rest of the vocab, which can not be assigned by the hints method or by the SAP notes you mentioned, need to be assigned by native speakers (manual effort !).
As you can see, SPUMG is NOT just a tool to be executed by Basis staff.
It needs in deed collaboration between Basis, Application and native speakers.
And it should be clear that the duration of the scans can be quite high - therefore a trial & error approach will take time (especially for large systems).
Best regards,
Nils Buerckel
SAP AG

MDMP: TWIN Upgrade + Unicode conversion

Similar Messages

Maybe you are looking for