46C EBCDIC to UNICODE upgrade and conversion

Can the UNICODE conversion processed be used directly on a 46C EBCDIC source system? Or is a conversion to 46C ASCII required before a UNICODE conversion?

Hello Will,
as Sally already explained, this is unfortunately not possible ;-((
SAP does not support Unicode with 4.6C ;-(
Therefore, only EBCDIC and ASCII are the options.
As of 4.7 Unicode & ASCII are available.
=> the project could look as follows:
- On 4.6 you need to go from EBCDIC to ASCII - 12 - 24h conversion time
- Upgrade to ERP 6.0 EHP4 ASCII - total Runtime about 40-65h - downtime of that: 10-24h
- Unicode Conversion Latin1 - 6-14h conversion time
=> You see, that the total runtime in one step is pretty long - e.g. for X-mas ...
Otherwise, it is typical, that the ASCII CPC is done in one step and later on Upgrade & Unicode in one further step.
For more details, we should talk together, but at least your project is pretty big ...
Regards
Volker Gueldenpfennig, consolut international ag
http://www.consolut.net - http://www.4soi.de - http://www.easymarketplace.de

Similar Messages

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

Where is the Combined Upgrade and Unicode Conversion Guide

Hi All
Embarassing question time.
I am after the Combined Upgrade and Unicode Conversion Guide for 4.7 to ERP 6.0, but can only find the Combined Upgrade and Unicode Conversion Guide for 46C to ERP 6.0.
Can anyone advise where the 4.7 guide is.
Thanks
Sam

Thank God SAP don't include it in the Install guide. The Install Guides are complex already. BTW if you need more info on unicode and its conversion go here
https://service.sap.com/unicode@sap

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

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

Combined Upgrade and Unicode conversion question

Hello Everyone,
I will be performing combined Upgrade and Unicode conversion soon. Currently i have run Prepare and do not have any errors.
I have already run SPUMG consistency check and i do not have any errors there. Since this is Combined Upgrade and unicode conversion according to guide i do not need to do the Nametab conversion right now. But now if i go this place:
SPUMG -> Status -> Additional Information , i see a status with red for Unicode nametabs are not consistent or not up-to-date.
Please let me know if i can ignore this step and do the nametab conversion after upgrade is complete and before unicode conversion.
Thanks,
FBK

Please follow the instructions from the guides.
The Unicode nametabs will be generated automatically during the upgrade.
An additional check is integrated into the final preparation steps in the target releases.
Regards,
Ronald

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

Combined Upgrade and Unicode Conversion

Hello, I'm planning to implement an Upgrade from I386/ORA8/46C TO I386/ORA10/ECC6 using CUUC method.
According to the guide, I better build up a sperate Sandbox Server for ABAP Program Modification and Testing. Since the customed ABAP Reports used to be related with the customed table, I suppose the best way for the Sandbox Server is to upgrade it to higher version.
I'm running the Prepare and stuck on the Transport Request import. The sandbox server is not ready yet in a few days.
My question is, can I just ignore the ABAP Program Import at the current phase and import it at the end of 'Prepare' and before the 'Upgrade'.
If yes, how? mannually import the TR for Abap Program changes to 46c after the 'Prepare' finished? Any steps that I should pay attention to spcially?
Any experience is welcome.
Thanks in advance and BR, Sam

This would depend on whether your quality and production are consistent in terms of modifications along with your development server. If all changes to quality and production has happened through changes in development and then transporting those changes to qas and prd, then i would suggest when you run your development system upgrade (sandbox in this case) ideally you should do the changes and modifications and record them in transport request using the option "select for transport". Later when you upgrade another sandbox (copy of qas or prd) you should select the transport request to be imported during the prepare.
But as you are now running PREPARE for copy of development, the prompt for importing transport request into this system is irrelevant and you should say " no" and complete the upgrade, and then the process outlined above..
Hope this helps.
Cheers,
Chetan

Unicode upgrade?

What is unicode upgrade?
Venkat

Hi
Upgrade Projects can follow one of the 2 possibility.
1. Technical Upgrade: in which the basis consultant will handle the same & transport the configurations & developments from 5.0 to 6.0. Subsequent to which functional consultant & ABAP er will do the necessary change in configuration or further configuration & ABAP ers will do necessary developments required.
2. Traditional ASAP mythology: which would refer as new implementation as a whole.
STEPS IN TECHNICAL UPGRADE
Basis Team will do the prepare activities. (UNIX, BASIS, DBA).
The client has modified Developer need to run the Transaction SPDD, which provides the details of SAP Standard Dictionary, objects that. Users need to take a decision to keep the changes or revert back to the SAP Standard Structure. More often decision is to keep the change. This is mandatory activity in upgrade and avoids data loses in new system.
After completing SPDD transaction, we need to run SPAU Transaction to get the list of Standard SAP programs that have been modified. This activity can be done in phases even after the upgrade. Generally this will be done in same go so that your testing results are consistent and have more confident in upgrade.
Run SPUMG Transaction for Unicode Conversion in non-Unicode system. SPUM4 in 4.6c.
Then we need to move Z/Y Objects. Need to do Extended programming check, SQL trace, Unit testing, Integration testing, Final testing, Regression Testing, Acceptance Testing etc.,
The main Category of Objects that needs to be Upgraded is
Includes
Function Groups / Function Modules
Programs / Reports
OSS Notes
SAP Repository Objects
SAP Data Dictionary Objects
Domains, Data Elements
Tables, Structures and Views
Module Pools, Sub Routine pools
BDC Programs
Print Programs
SAP Scripts, Screens
User Exits
Please visit the following links:
http://service.sap.com/erp
http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional perspective)
http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2005 --> Upgrade
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
For Functionality Differences pls refer to the below site -
http://solutionbrowser.erp.sap.fmpmedia.com/
After opening the site, please select the Source Release Version which is 4.6 b Then Select the Target Release Version which is "mySAP ERP 2005" or ECC 6.0
Select the Solution Area like Financials, Human Capital Management, Sales....
Select module like MM, PP, SD, QM.....
Click on Search
then it displays the Release Version and the Delta Functionality. Which can be downloaded to a word document if required.
And also check the release notes of ECC 6.0 in service.sap.com.
Hope this helps you.
Do award points if you found them useful.

Wht is the difference between unicode program and non unicode program ?

Hi guru,
wht is the difference between unicode program and non unicode program ?
Regards
Subash

About brief idea about unicode
In the past, SAP developers used various codes to encode characters of different alphabets, for example, ASCII, EBCDI, or double-byte code pages.
ASCII (American Standard Code for Information Interchange) encodes each character using 1 byte = 8 bit. This makes it possible to represent a maximum of 28 = 256 characters to which the combinations 00000000, 11111111 are assigned. Common code pages are, for example, ISO88591 for West European or ISO88595 for Cyrillic fonts.
EBCDI (Extended Binary Coded Decimal Interchange) also uses 1 byte to encode each character, which again makes it possible to represent 256 characters. EBCDIC 0697/0500 is an old IBM format that is used on AS/400 machines for West European fonts, for example.
Double-byte code pages require 1 or 2 bytes for each character. This allows you to form 216 = 65536 combinations where usually only 10,000 - 15,000 characters are used. Double-byte code pages are, for example, SJIS for Japanese and BIG5 for traditional Chinese.
Using these character sets, you can account for each language relevant to the SAP System. However, problems occur if you want to merge texts from different incompatible character sets in a central system. Equally, exchanging data between systems with incompatible character sets can result in unprecedented situations.
One solution to this problem is to use a code comprising all characters used on earth. This code is called Unicode (ISO/IEC 10646) and consists of at least 16 bit = 2 bytes, alternatively of 32 bit = 4 bytes per character. Although the conversion effort for the R/3 kernel and applications is considerable, the migration to Unicode provides great benefits in the long run:
The Internet and consequently also mySAP.com are entirely based on Unicode, which thus is a basic requirement for international competitiveness.
Unicode allows all R/3 users to install a central R/3 System that covers all business processes worldwide.
Companies using different distributed systems frequently want to aggregate their worldwide corporate data. Without Unicode, they would be able to do this only to a limited degree.
With Unicode, you can use multiple languages simultaneously at a single frontend computer.
Unicode is required for cross-application data exchange without loss of data due to incompatible character sets. One way to present documents in the World Wide Web (www) is XML, for example.
ABAP programs must be modified wherever an explicit or implicit assumption is made with regard to the internal length of a character. As a result, a new level of abstraction is reached which makes it possible to run one and the same program both in conventional and in Unicode systems. In addition, if new characters are added to the Unicode character set, SAP can decide whether to represent these characters internally using 2 or 4 bytes.
A Unicode-enabled ABAP program (UP) is a program in which all Unicode checks are effective. Such a program returns the same results in a non-Unicode system (NUS) as in a Unicode system (US). In order to perform the relevant syntax checks, you must activate the Unicode flag in the screens of the program and class attributes.
In a US, you can only execute programs for which the Unicode flag is set. In future, the Unicode flag must be set for all SAP programs to enable them to run on a US. If the Unicode flag is set for a program, the syntax is checked and the program executed according to the rules described in this document, regardless of whether the system is a US or an NUS. From now on, the Unicode flag must be set for all new programs and classes that are created.
If the Unicode flag is not set, a program can only be executed in an NUS. The syntactical and semantic changes described below do not apply to such programs. However, you can use all language extensions that have been introduced in the process of the conversion to Unicode.
As a result of the modifications and restrictions associated with the Unicode flag, programs are executed in both Unicode and non-Unicode systems with the same semantics to a large degree. In rare cases, however, differences may occur. Programs that are designed to run on both systems therefore need to be tested on both platforms.
You can also check out these official SAP locations on the SAP Service Marketplace:
http://service.sap.com/unicode
http://service.sap.com/unicode@SAP
http://service.sap.com/i18n
Regards,
Santosh

Using Audition 2.0 on Windows XP platform. Now have Windows 8.1 on new computer and need to upgrade and load latest version of Audition. Any suggestions? Thanks very much.....R

Using Audition 2.0 on Windows XP platform. Now have Windows 8.1 on new computer and need to upgrade and load latest version of Audition. Any suggestions? Many thanks, R.

VC6. is rather old, but you can try to convert the VC6 project using the upgrade wizard of VC2012. Depending on the content of the project your code will work more or less without problems, at least it will compile without errors.
You could also go the 2nd way and create in VC2012 a project type using the wizard that is very similar to your current VC6 projcet (MDI, SDI, Dialog Based, ...). Than you replace the files generated by the wizard with the content of your project. Sometimes
this way is more successful.
But at all the automated converting success depends on the code of your VC6 project. I had both, conversions without big problems and also conversions that need a lot changes to run on a current VC version.
Best regards
Bordon
Note: Posted code pieces may not have a good programming style and may not perfect. It is also possible that they do not work in all situations. Code pieces are only indended to explain something particualar.

Client Copy between unicode system and non-unicode system

Hello,
we have to build up a new system for japan. It is planned to install a new 4.7Ext200 unicode system and then make a client copy from a non-unicode 4.7Ext200 (language= german, english) system to the unicode system. I don't think that this is possible way, but I can't find information regarding client copies from non-unicode to unicode. I would advice the project to convert the existing non-unicode system to unicode, make a system copy for the new system and then install japan languages. Any information, which can help me.
Regards,
Alexander

Hi,
without conversion client copy is not possible
look at following
Re: Client copy between unicode and Non-unicode
regards,
kaushal

SAP Best Practice For Unicode Upgrades - NetWeaver 2004s

Team SAP,
I have a customer that is starting to plan for a Unicode upgrade. The question from the customer is as follows:
What is the SAP Best Practice for Unicode Upgrades? They will be upgrading from a BW 3.5 System to NetWeaver 2004s, and their question is ... should they:
a) Perform the Unicode Upgrade At The Same Time As Their BW 3.5 > NetWeaver 2004s Upgrade, or
b) Perform NetWeaver 2004s Upgrade first, and then at a later date, perform the Unicode Upgrade?
Thank you in advance for any guidance or counsel you may be able to offer.
-M

Hi Michael,
Check these links:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ee7407a0-0501-0010-81ae-e329029b1074
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/7e259990-0201-0010-6085-e7c5aec5af1d
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5411d290-0201-0010-b49b-a6145fb16d15
Bye
Dinesh

How to upgrade AND move between platforms with different Endians...?

Hi, all,
I have two databases - one of 500Gb and one of 50Gb - that are currently running on 10.2.0.4 on AIX 64-bit. They are Production systems.
I have to move them to a brand new Linux (RHEL 5.6 - 64-bit) server that will be running 11.2.0.2.
For test, I'm OK with this being done with Data Pump. But for the eventual move to 'New Prod', this will result in hours' worth of downtime and it's a business-critical system, so I'm trying to mitigate that as much as I can.
I was, naively, hoping to use RMAN to both move the databases from one box to the other, but also to upgrade them. I figure I would do the following (as per Metalink 369644.1) as I have a Recovery Catalog, etc, etc:
Install the binaries on the New Prod server
Connect to the RCAT and restore the database and recovery to a PiT
Manually upgrade the database by putting the DB into STARTUP UPGRADE and running the catupgrd.sql
Unfortunately, I didn't realise the Endian was different between AIX and RHEL (as per 1079563.1). Oops.
It doesn't look like I'll be able to use Transportable Tablespaces (as per 243304.1) either without first having to migrate the data across as a 10g DB and then upgrading.
So my options appear to be:
a) Data Pump and suck the outage up
b) Move the data using Transportable Tablespaces to 10.2.0.4 and then upgrade to 11.2.0.2.
Are there any other options? I have hopes that a logical standby would work in this instance a la rolling upgrade, but suspect that the different O/S AND the different Endian would scupper that idea...
Mark

Perhaps, I have more experience using concurrent exports/imports using the traditional exp/imp utility than using the parallel option on expdp/impdp. One thing you can do with exp/imp that you cannot do with expdp/impdp is export into a named pipe, start a remove copy of the named pipe to the new server, and then start importing from the named pipe on the new server so that you are importing while still exporting the same objects. We use tables= exports when we did this back when the tables= parameter could only handle 99 tables. We had a separate export for every large table and then a set of exports for 99 tables for each of the other tasks ran 6 to 12 concurrent processes.
One thing to look at is historic data. Potentially some tables can be moved in advance of the majority of the application objects and replaced with synonym to remote objects.
Truely static tables could also potentially be moved in advance even if only a day or two before to reduce the number of objects to be moved.
Build the new database in noarchive log mode to save some processing and switch it over and immediately back it up when you migrate.
And Yes, if the two platforms appear in the view name I gave you then you can use transportable tablespaces with the rman conversion step. Instructions for using rman to do the conversion are in the rman manual.
HTH -- Mark D Powell --

FTP transfer gives incorrect characters after unicode upgrade

Hello all,
We write a file on a FTP drive containing data from an internal table. We use FM FTP_R3_TO_CLIENT to write this file. The internal table contains characters like 'ü'. Before our unicode upgrade this process worked fine. After our unicode upgrade the FTP file contains instead of the 'ü' characters like 'Ã¼'.
The internal table passed to the FM is still ok in the unicode system, only the result seems not. We did set the unicode flag on the SAPFTP RFC destination but this made no difference.
Any idea?
Thanks and best regards,
Boris

Hello Anil,
Below items we checked between MDMP 46B and Unicode ECC6 with production client table SKAT. some Spanish display not correct.
Unicode ECC6.0     46B
Short Text     Short Text
Ant a prov - Gto imp     Ant a prov - Gto imp
Regal¨ªas     Regalías
Prov Herramentales     Prov Herramentales
Provisi¨®n de SLA     Provisión de SLA
Prov Fin Vida (EOL)     Prov Fin Vida (EOL)
Gtos de imp     Gtos de imp
Mat dañado o perdido     Mat dańado o perdido
Papeleria e insumos     Papeleria e insumos
Gastos Vtas-Diseño     Gastos Vtas-Diseńo
Ganancia p fluc camb     Ganancia p fluc camb
Aj anual p inf     Aj anual p inf
Depreciaci¨®n fiscal     Depreciación fiscal
Best Regards
Key

46C EBCDIC to UNICODE upgrade and conversion

Similar Messages

Maybe you are looking for