4.6c to Unicode upgrade

Hi all,
I am moving a report (which has been successfully running in 4.6c) to a new system with UNICODE check. In my current system(4.6c) I want to do a UNICODE syntax check before moving to the new system. If it is possible please let me know with a brief explanations.
Regards and thanks in advance,
Amarjit.S

Hi,
My current system is 4.6c and the transaction UCCHECK is not available.
My query again:
I want to do the syntax check before before moving to UNICODE environment (dev/testing/qlty server)
Is it possible to do any sort of UNICODE syntaxt check in 4.6c ?
Thanks again,
-Amarjit.S

Similar Messages

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

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

Unicode upgrade of Business Objects

Hi All,
Can someone let me know how to do Unicode upgrade of Business objects.
For programs, we can set the unicode attribute, in the similar way how to set this Unicode attribute for Business objects?
Amogh

Hi Amogh.
We have the same issue.
Whe are in the middle of the ABAP unicode enabling and we haven't found a solution for some customer Business Objects - e.g. Z_BUS2017. They are OK (UCCHECK transaction) but they haven't the Unicode flag. The standard Object BUS2017, program MM07MMOB have the Unicode flag activeted (view TRDIR-UCCHECK).
If you have got a solution please, advice us.
Best regards,
Carlos

Download to Excel after Unicode Upgrade not working

Hi
Before the unicode upgrade we downloaded a spreadsheet, specifying the columns and table. Since the upgrade the spreasheet opens and start to create the columns, but as soon as it tries to write the table we get an error at teh following code.
class C_OI_CONTAINER_CONTROL_CREATOR method i_oi_spreadsheet~insert_one_table
Error as follows
\INTERFACE=I_OI_ERROR
I_OI_ERROR~ERROR_CODE           CALL_NOT_FLUSHED
I_OI_ERROR~IS_FLUSHED
I_OI_ERROR~HAS_FAILED           X
I_OI_ERROR~HAS_SUCCEEDED
ERROR_NR                                                   999999-
ERROR_STRING                               50
Does anyone know why this is occuring and what the solution please?
Thanks.

Can you let us know your support package levels? Also you right click and then export it to Excel?
Something to do with packages and xcel levels as well.

CCMS there are no entries in "displays alerts" after unicode upgrade.

Hello
After an Unicode upgrade of an SAP 4.7, there are no entries in "displays alerts".
Table ALALERTDB empty.
Thanks

Hi Gervase,
I don't know what you have done yesterday, but now I can see note 1032334. Thanks.
I closed the sap call again.
Anyways, it was very strange, in transaction SNOTE I tried to download this note but then the message appeared "this note is not released, please inform your sap support". And on sap support portal it was near the same. Now I will implement it and give you a feedback if you wish.
kind regards
Diana

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.

Unicode upgrade & impact on security

Hi All,
One of my clients will be upgrading their system to Unicode in the next few months.
Does anyone have experiences to share of this process with respect to security.
I know that it can cause problems with portals, however that is not an issue here as it's the ABAP stack that I am most interested in.
Cheers
Alex

Hi All,
Unicode upgrade went live in production a while back and no problems to report from a security side.
No issues which have subsequently been identified have been traced back to teh Unicode upgrade being the cause.
Cheers
Alex

Printing in Russian Language - after ECC 6.0 unicode upgrade

Hello ,
Earlier users from russia are able to print in SAP 4.6C using SAPWIN Device type in russian language.
but after unicode conversion and ECC 6.0 EHP 4 upgrade, they are not able to print in russian using SAPWIN.
In print preview ,it is showing correclty, but not in output.
any help ?
regards,
Chaitanya.

Hi,
It should not be necessary to change to SAPWIN5. Device type SAPWIN5 only supports cyrillic fonts like COURCYR, HELVCYR or TIMECYR. Therefore, even if the erong font is used in the form, the device type converts it to a Russian font. If yuo use a correct font for Russian characters in the form, then SAPWIN should also work.
SWINCF should also work with the current form setting.
Regards,
Aidan

BBP_DOCUMENT_TAB- Entries with special charaters afetr unicode upgrade

Hi,
We are on SRM 5.0 (SRM_SERVER 550) Sp07. SAp 4.7 backend.
We are upgrading the system to unicode.
What we have observed is after PO creation the BBP_DOCUMENT_TAB has some special characters in the field 'Key'
For example:
BUS2121001##䟅㳤탇ᾣᾣઃ????#?? ######## 01############################
In the non unicode system the entry reads like below
BUS2121001GAEp#?g8Ia#####o# ################ 01###########
This does not cause problems in most of the SRM systems, but in one of the systems, the Clean_reqreq_up job is failing with a message 'Buffer table not up to date'. We are not sure if this is due to the entries in BBP_DOCUMENT_TAB which have special characters or not.
Can someone please explain the impact/risk of such entries in BBP_DOCUMENT_TAB. Is this a known issue. is there any solution for this?
Thanks & regards,
Srivatsan
Edited by: Srivatsan on Feb 29, 2008 1:14 PM

Hi,
The special characters may be due unicode/langauage issue.
See the foll notes:
Note 548016 - Conversion to Unicode
Related Notes
986907 - SQL Server settings for R3load based system copy
971646 - 6.40 Patch Collection Hom./Het.System Copy ABAP
956921 - IDES ERP 2005 ECC 6.0
952514 - Using the table splitting feature
938374 - Additional tools for MDMP --> Unicode conversion preparation
936441 - Oracle settings for R3load based system copy
932779 - Unicode conversion - analysis of nametab problems
928729 - Combined Upgrade & Unicode Conversion (CU&UC) FAQ
920831 - RFC with inactive text language
896144 - mySAP ERP 2005 Upgrade for R/3 or ERP MDMP Customers
895560 - Support for languages only available in Unicode system
871541 - Frequently used text patterns
857081 - Unicode conversion: downtime estimate
855772 - Distribution Monitor
852235 - Release Restrictions for SAP ERP 6.0
814707 - Troubleshooting for RFC connections Unicode/non-Unicode
812821 - Cascading Font settings
806554 - FAQ: I/O-intensive database operations
795267 - System Copy for 'SAP Web AS Java' based systems
793113 - FAQ: Oracle I/O configuration
791199 - Default editor changed to MSWord in SAPscript and SmartForms
750219 - Unicode UTF-8 printing with HP printers
747036 - mySAP ERP 2004 Upgrade for R/3 MDMP Customers
745030 - MDMP - Unicode Interfaces: Solution Overview
742662 - MS Word as Editor in SAPscript and Smart Forms
741821 - Release limitations concerning SAP ERP 2004
693168 - Minimized Downtime Service and Incremental Migration (IMIG)
673244 - SAPGUI: Recent corrections for Unicode support.
647495 - RFC for Unicode ./. non-Unicode Connections
638357 - Transport between Unicode and non-Unicode systems
585116 - Translation after installation of WebAS SP25
573044 - Unicode conversion for HR application
552464 - What is Big Endian / Little Endian? What Endian do I have?
551344 - Unicode Conversion
547444 - RFC Enhancement for Unicode ./. non-Unicode Connections
543715 - BW Migrations and System Copies for BW 2.0B / 2.1 Content
540911 - Unicode restrictions for R/3 Enterprise, ECC 5.0, ECC 6.0
508854 - SAPGUI: How to use Unicode
379940 - Unicode based mySAP availability
355771 - Oracle: Explanation of the new tablespace layout
330267 - Transports between Basis Releases 4.6* and 6.*
316903 - SAPGUI: How to use I18N mode
215015 - Unicode UTF-8 printing with a Lexmark printer
80727 - Transporting non-LATIN-1 texts
79991 - Multi-Language and Unicode support of mySAP solutions
73606 - Supported Languages and Code Pages
BR,
Disha.
Do reward points for useful answers.

Printing of asian characters after ECC 5.0 / unicode upgrade

Does anyone know what do we need to do in order to print documents in asian languages. We have upgraded to ECC5.0/unicode.

I solved my issue as follows.
Here are 4 options I analyzed, you may chose one that best fits your needs.
We chose option 1.1
1.1     PRINTER UPGRADE/REPLACEMENT
This is a h/w based solution. This option requires certain compliant models of the printers and installation of special font card to that printer. It provides faster response times since the fonts dont have to be sent across the network. Although there are less number of fonts available compared to other options, they are sufficient to cover major world languages.
1.2     SAPLPD/SAP SPRINT
This is a s/w service running on a NT Box, also known as Frontend printing. This decentralizes printing landscape from Unix (our SAP instances are on unix) to windows based printing and would require changes to printng support procedure in our landscape.
1.3     OMS
Using a Output Management System ( OMS) such as HP OMS or VPSX ( using a plugin such as Impulse for Double Byte printing).   This is full-fledge output management solution but requires additional resources and capital investment and is suited for organization with significant(sometimes complex) output needs that need to be carefully managed.
1.4     PDF
Convert SAP output to pdf and send the pdf file with fonts embedded inside it to printer. Requires ABAP resource and uncertainty over whether all the different types of output can be converted to pdf besides the pdf printing will add network overhead and cause slowness affecting other processes.May be something for future since SAP is collaborating with adobe on forms/output delivery.

DME file download unicode upgrade

we are working on an upgrade.
When we try to download DME files form F110. there is a space before each char in the output file,
eg: K P 9 0 2 7 1. expected result "KP90271"
additional information
a)user parameter is set DCP is set to NONE. b) REGUT-CODEPAGE = 4102, RUGUT-SAPRL = 620.
Any suggestion??
Edited by: sarath sirip on Jan 26, 2011 4:56 PM

Hi,
Same issue we faced in 46C NC to ECC UC upgrade.
I guess the program used to generate the DME file is Z program, which might be copied from the SAP standard program in older release. For the same SAP standard program there might be some of the changes related to unicode. Adjust your Z program reference to the SAP standard progam.
Regards
Rahul

Unicode upgrade of ABAP code question.

Hi gurus......
I am involved in upgradation tool...
when we are upgrading ec4 to ec6 some pgms are unicode compatable and we will get errors according to unicode format
so when we get those errors can we replace those stmts by our code
for eg.
data fld(6)
ln(8).
describe filed fld length ln.
should be replaced by
describe filed fld length ln in characer mode
like these can we change pgm according to unicode standards.
thanks pls suggest me.
Edited by: suma chandra on Dec 12, 2008 9:43 AM
Edited by: Julius Bussche on Dec 12, 2008 10:01 AM

>
suma chandra wrote:
> Hi we can update the custom pgms with uniocode standards
>
> but hw it can be done we need to know.........
Hi suma,
To make custom programs with unicode standards,
first step--> goto program attributes, then activate "Unicode checks active" checkbox.
second step--> use "UCCHECK" transaction, give your custom program name, it will displays all unicode errors and obsolete function modules(upload,download).
third step--> its more adviceble to use this transaction eventhough u fixed all errors in second step, use "SLIN" transaction, give your program name and execute, it will displays all type of errors and warnings related to that program. As per the client's scope fix the errors and warning.
I worked for over 14 upgrade projects. The above process is the standard process followed by SAP.
Still you are looking for any information related to upgrade please feel free to contact me.
Regards
Arani Bhaskar
Edited by: arani bhaskar on Feb 16, 2009 10:10 AM

UNICODE upgrade - missing R3lsctl

We are on an as/400 v7r1 system running an upgrade from ASCII to UNICODE on a 4.7 SAP system.
When we start the sapinst.exe we get thru a few steps then the upgrade stops because R3ldctl is missing.
We loaded patch R3ldctl_9-20000359.SAR with APYR3FIX but this looks like it loads R3ldctlDB4.
We copied over a version of R3ldctl from another direcory and the job failed.
Error message from sapinst.exe is below
An error occurred while processing service DB2/iSeries ASCII/Unicode Conversion Kit > ASCII ABAP Database Content Export
( Last error reported by the step :TMKSVR Exception translating call parameters: changeCallForO4Spawn: "\usr\sap\T03\SYS\exe\run\R3ldctl" could not be resolved..). You may now
press Retry to repeat the current step.
press the View Log button to get more information about the error.
stop the task and continue with it later.
Log files are written to Z:\usr\sap/SAPinst/NW04S/EXP.
Where can we get R3ldctl ?
Thanks

The export ran for about 3.5 hrs and 3 jobs of 16 failed. The failing jobs are
ERROR: 2011-10-11 11:07:08 com.sap.inst.migmon.LoadTask run
Unloading of 'SAPPOOL' export package is interrupted with R3load error.
Process '/usr/sap/T03/SYS/exe/run/R3load -e SAPPOOL.cmd -datacodepage 4102 -l SAPPOOL.log -stop_on_error' exited with return code 2.
For mode details see 'SAPPOOL.log' file.
Standard error output:
¢u2014u2014u2122u201Dz@¢u2014u2122u2021¥M@u2122u2021u0192k@u2122u2021¥]@u02C6¢@u2022u2013£@u201Au2026u2026u2022@u0192u201Cu201Cu2026u201EK%¢u2014u2014u2122u201DMñu0192]z@Õu2013@×u2122u2013u2020u2030u201Cu2026@¤¢u2026u201EK%¢u2014u2014u2122u201Dz@âÁ×âèâãÅÔÕÁÔÅ@u2022u2026u2030£u02C6u2026u2122@u2030u2022@×u2122u2013u2020u2030u201Cu2026@u2022u2013u2122@u2030u2022@Ãu2013u201Du201Du2022u201Eu201Cu2030u2022u2026%
ERROR: 2011-10-11 11:10:26 com.sap.inst.migmon.LoadTask run
Unloading of 'SAPSDIC' export package is interrupted with R3load error.
Process '/usr/sap/T03/SYS/exe/run/R3load -e SAPSDIC.cmd -datacodepage 4102 -l SAPSDIC.log -stop_on_error' exited with return code 2.
For mode details see 'SAPSDIC.log' file.
Standard error output:
¢u2014u2014u2122u201Dz@¢u2014u2122u2021¥M@u2122u2021u0192k@u2122u2021¥]@u02C6¢@u2022u2013£@u201Au2026u2026u2022@u0192u201Cu201Cu2026u201EK%¢u2014u2014u2122u201DMñu0192]z@Õu2013@×u2122u2013u2020u2030u201Cu2026@¤¢u2026u201EK%¢u2014u2014u2122u201Dz@âÁ×âèâãÅÔÕÁÔÅ@u2022u2026u2030£u02C6u2026u2122@u2030u2022@×u2122u2013u2020u2030u201Cu2026@u2022u2013u2122@u2030u2022@Ãu2013u201Du201Du2022u201Eu201Cu2030u2022u2026%
ERROR: 2011-10-11 14:48:42 com.sap.inst.migmon.LoadTask run
Unloading of 'SAPCLUST' export package is interrupted with R3load error.
Process '/usr/sap/T03/SYS/exe/run/R3load -e SAPCLUST.cmd -datacodepage 4102 -l SAPCLUST.log -stop_on_error' exited with return code 2.
For mode details see 'SAPCLUST.log' file.
Standard error output:
¢u2014u2014u2122u201Dz@¢u2014u2122u2021¥M@u2122u2021u0192k@u2122u2021¥]@u02C6¢@u2022u2013£@u201Au2026u2026u2022@u0192u201Cu201Cu2026u201EK%¢u2014u2014u2122u201DMñu0192]z@Õu2013@×u2122u2013u2020u2030u201Cu2026@¤¢u2026u201EK%¢u2014u2014u2122u201Dz@âÁ×âèâãÅÔÕÁÔÅ@u2022u2026u2030£u02C6u2026u2122@u2030u2022@×u2122u2013u2020u2030u201Cu2026@u2022u2013u2122@u2030u2022@Ãu2013u201Du201Du2022u201Eu201Cu2030u2022u2026%
Unfortunatley the log files for sappool.log, sapsdic.log and sapclust.log are not readable.....

R/3 4.7 Unicode upgrade query

Dear All,
I have a very specific and unique query. We are implementing ESS, MSS, MBO for our clients, and in the process have upgraded the production servers to R/3 4.7 version ( Non - Unicode ). We're using EP 6.0 as the front for the same .
My question is as below :
Today the client is not interested in having interface other than english, but moving down the line after 2 years he would like to have a Korean language interface, which might require R/3 4.7 with Koran language unicode and functions converted.
What I want to know is whether this effort in upgrading to the unicode version of Korean on R/3 , before we actually implement ESS / MSS etc is better or should we upgrade to a unicode version 2 years later ?
In either case what are the advantages and disadvantages ?
Expert insight sought,
Regards,
Neeraj S.

Hi Neeraj,
Personally, I would recommend upgrading to Unicode now.
With your client there already appear to be signs that a non-unicode format is unsuitable for the longer term vision of the company...
What if this long term vision becomes a more immediate requirement and they no longer want to wait 2 years?
Additionally upgrading to unicode would mean that all custom programs would have to be made unicode compliant. This is a Particularly arduous problem if there is any hexa-decimal manipulation within the custom programs...
Within a Unicode system all programs are automatically made Unicode compliant (as long as the appropriate flag is checked in the program attributes)...
Therefore, if you can implement Unicode now then I would go for it
I hope this helps.
Hafeez

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

4.6c to Unicode upgrade

Similar Messages

Maybe you are looking for