Unicode Conversion check

Hello All,
We are doing Combined Upgrade and Unicode Conversion from 4.6C to ECC 6.0. We have listed all the Z programs and we need to do unicode conversion check for the same. Hence we have exported the Z programs and imported the same into our IDES server and completed the UCCHECK. But we were not able to activate the same as there are many references missing (example: Z tables). We planned for activating the Z programs in IDES server and use the corrected programs in the upgrade system. But we are not able to proceed due to activation problem
Could you please suggest any other alternative solution or best practise that needs to be followed? Should we upgrade our system to 6.20 / 6.40 Engine first for UCCHECK. Please suggest
Regards,
Anand

Hi ,
As per SAP bes practice there are 2 options
1) You copy and upgrade your SAP Basis 4.6c production system to at least WAS 6.10 (non-unicode) or higher. And here you can perform your preparation steps. You can call this system as UCCHECK system. This is the recommended option.
I had chosen it in my CUUC upgrade from 4.6c to ECC 6.0
2) Option 2 is you can install a sandbox system at lease on version 6.10(non-unicode) or higher. Note that if you choose this option you must make sure that the sandbox system should contain all DDIC objects that are used in Z programs or modified SAP programs.
Then create a transport with Z programs + modified SAP programs in your 4.6c system and import them in sandbox system.
now here you can perform your preparation steps.
Also I will recommend you please go through the CUUC guide. It will clear all your doubts.
Regards,
Sachin Rane.

Similar Messages

Any one having , ABAP Check list for unicode conversion

Now I am in one upgrade project. Its new to me.
Can anyone have
ABAP checklist for unicode conversion in upgrade projects

Hello Uma,
The Link will be helpful to you.
Re: Upgrade 4.6 to ECC - What are the responsibilites
regarding Unicode influence in Standard programs
Very good document:
http://www.doag.org/pub/docs/sig/sap/2004-03/Buhlinger_Maxi_Version.pdf
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d37d1ad9-0b01-0010-ed9f-bc3222312dd8
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/589d18d9-0b01-0010-ac8a-8a22852061a2
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f8e316d9-0b01-0010-8e95-829a58c1511a
Reward If Helpful.
Regards
Sasidhar Reddy Matli.

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

Some character display incorrect after unicode conversion

Dear Experts,
Currently we upgrade our SAP system from 4.6B NU to ECC6.0 UN.
in 4.6B system we had implemented Simple Chinese and French language package to the system. after upgrade to ECC6.0 no-unicode system. we perform a MDMP unicode conversion.currently system running with ECC6.0 unicode interface with language 1EFD. SUMG releated tasks had been finished. Chinese and French language checked OK in ECC6 UN system.
Our issue is. in the past time. some Spanish local end user typing some spanish character in some master date field when they login in 4.6B GUI choice english as login language.these kind of spanish characters could not display correct in current unicode environment.
could you please given us some suggestion for how to fix this issue.
I also sent this message in the Netweaver administrator forums with below links.
Spanish display incorrect after unicode conversion

Hello,
I doubt that the data shown by you in the link was caused by Spanish users logged on in EN.
I think this was rather caused by utf-8 data uploaded into the Non-Unicode system.
In this case, you need to repair the according texts manually, I do not know any automatic repair.
Best regards,
Nils Buerckel
SAP AG

Error in Import during unicode conversion

Hello,
I am doing Combined upgrade and unicode conversion to ECC6 SR3.
Upgrade is completed sucessfully. During import i get an error stating :
bSl Trace: Error 959 in exec_immediate() from oci_execute_stmt(), orpc=0
DbSl Trace: ORA-959 occurred when executing SQL stmt (parse error offset=92)
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "REPOLOAD~0" ON "REPOLOAD" ( "PROGNAME", "R3STATE", "MACH" ) TABLESPACE PSAPSID620 STORAGE (INITIAL 209
7152 NEXT 0000010240K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS )
DbSlExecute: rc = 99
(SQL error 959)
error message returned by DbSl:
ORA-00959: tablespace 'PSAPSID620' does not exist
This tablespace doesnt exist as it was upgraded to PSAPSID700.
I checked DBLORA.TPL and it has two references of 620 :
index storage parameters
loc: APPL0 PSAP@SCHEMAID@                 0000
     APPL1 PSAP@SCHEMAID@                   0000
     APPL2 PSAP@SCHEMAID@                  0000
     CLUST PSAP@SCHEMAID@                  0000
     DDIM PSAPDIMI                                      0000
     DFACT PSAPFACTI                                0000
     DODS PSAPODSI                                   0000
     POOL PSAP@SCHEMAID@                  0000
     SDIC PSAP@SCHEMAID@                     0
     SDOCU PSAP@SCHEMAID@                  0000
     *SLDEF PSAP@SCHEMAID@620              0000*
     *SLEXC PSAP@SCHEMAID@620            0000
     SLOAD PSAP@SCHEMAID@                  0000
     SPROT PSAP@SCHEMAID@                   0000
     SSDEF PSAP@SCHEMAID@700              0000
     SSEXC PSAP@SCHEMAID@700              0000
Thanks,
FBK

Hi Volker,
Thank you very much. Stupid error :-).
I also did step 2 with fixr3owns yesterday with SAPINST and then it worked. I got to step 3 "iSeries Installation Step", but got an error in SAPINST when "Creating infrastructure for SAP system BND". I logged off SAPINST, patched CRTR3SYS and started SAPINST again and then got the error in step 2 wirh fixr3owns.
I´m now past step 2 and in step 3 "iSeries Installation Step". And I get the same error as I got yesterday...
From the job log:
TMKSVR request processor: request was successful
Processing request from client 10.96.220.5:4350.
EXECUTE CRTR3SYS SID(BND) GLOBALHOST('SAP002') FORCEPROF(*NO)
ADBHOST('SAP002') 1 N
Keyword GLOBALHOST not valid for this command.
Keyword FORCEPROF not valid for this command.
Keyword ADBHOST not valid for this command.
Error found on CRTR3SYS command.
Errors occurred in command.
error: call_AS400_command: "CPF0006" caught after "CRTR3SYS SID(BND)
GLOBALHOST('SAP002') FORCEPROF(*NO) ADBHOST('SAP002')"
I can run "CRTR3SYS SID(BND) GLOBALHOST('SAP002') FORCEPROF(*NO)" manually.
Do you have any ideas?
Best regards
Henrik Hviid

LRAW data Conversion during Unicode Conversion

Hi,
We have upgraded our 46C MDMP system to Unicode system.
After conversion we found that some of the tables with field of LRAW type are having conversion issue.
In 46C system, Russian data which enetered in the MS Cyrillic (Code page 1504), is converted to code page 1500 after unicode conversion.
We have not found any entries for this table in vocabulary, reprocess log or in SUMG.
For example table STXL. This table contains Purchase order text for the material.
Report HRUU_CONVERT_IN_UNICODE does not shows LRAW data field for conversion.
Can you suggest how LRAW data can be converted from 1500 to 1504 code page.
Thanks and Regards
Rahul

Hi Rahul,
STXL is a language dependent INDX type table. Hence SPUMG will not scan this one with the default settings.
Please have a look at the description of INDX type table handling in the Unicode conversion Guide.
In the Unicode system, you can use UMG_ADJUST_STXL for the conversion.
However please be aware of the restrictions:
Once you have decided about the code page and converted the object, this cannot be reverted !
Therefore it is highly recommended to check the display mode first and in addition test it extensively on a sandbox system !
Best regards,
Nils Buerckel
SAP AG

Unicode Conversion : Import Error in ABAP SAPCLUST Error

Hi
I am doing the unicode conversion ..
The export of the database is successful.. But during the import it is giving an error.
Export is done as per note 552464 (Code Page 4103)
Platform is windows server 2003 / Oracle 10.2
Loading of 'SAPCLUST' import package: ERROR
(GSI) INFO: vname    = "ORACLE                          "
(GSI) INFO: hostname = "CTSINTCOSNW5                                                    "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "CTSINTCOSNW5"
(GSI) INFO: release = "5.2"
(GSI) INFO: version = "3790 Service Pack 1"
(GSI) INFO: machine = "8x Intel 801586 (Mod 4 Step 9)"
(DB) INFO: CLU4 deleted/truncated #20070301165425
myCluster (63.7.Imp): 2113: inconsistent field names (source) : physical field K1N05 appears as logic K1N5.
myCluster (63.7.Imp): 2114: further investigation recommended.
myCluster (63.7.Imp): 1952: error when checking key field consistency for logic table TACOPC    .
myCluster (63.7.Imp): 1955: logic table is canonical.
myCluster (63.7.Imp): 1958: received return code 2 from c3_uc_check_key_field_descr_consistency.
myCluster (63.7.Imp): 1252: unable to retrieve nametab info for logic table TACOPC    .
myCluster (63.7.Imp): 8096: unable to acquire nametab info for logic table TACOPC    .
myCluster (63.7.Imp): 2835: failed to convert cluster data of cluster item.
myCluster: CLU4       *00001*
myCluster (63.7.Imp): 320: error during conversion of cluster item.
myCluster (63.7.Imp): 323: affected physical table is CLU4.
(CNV) ERROR: code page conversion failed
             rc = 2
.--============--
RSCP - Error
`----
(DB) INFO: disconnected from DB
D:\usr\sap\ABU\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
D:\usr\sap\ABU\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20070301165425
Can any one help please ?
Thanks in advance

hi,
could you please have a look to SAP Note 902817 - Inconsistencies in cluster tables (log vs phys field name)
Cheers,
-Sunil

SRM can not open attachment after unicode conversion

Hi,
Our system is SRM4.0, last week we do a unicode conversion project.
After we convert to unicode, some attachment in SC and PO can not be openned, these attachment file name include some chinese. If the attachment file name is all English, no problem to open it.
I think it is the cause by unicode conversion, do you have any idea what is the root of this problem?
Thanks.

Hi,
Please check in table :BBP_PDATT
If you have created a shopping cart with attachment. The attachment will be in the above table
Regards
G.Ganesh Kumar

U00C9 becomes u00C3 after unicode conversion

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

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

Spanish display incorrect after unicode conversion

Dear Experts,
Currently we upgrade our SAP system from 4.6B NU to ECC6.0 UN.
in 4.6B system we had implemented Simple Chinese and French language package to the system. after upgrade to ECC6.0 no-unicode system. we perform a MDMP unicode conversion.currently system running with ECC6.0 unicode interface with language 1EFD. SUMG releated tasks had been finished. Chinese and French language checked OK in ECC6 UN system.
Our issue is. in the past time. some Spanish local end user typing some spanish character in some master date field when they login in 4.6B GUI choice english as login language.these kind of spanish characters could not display correct in current unicode environment.
could you please given us some suggestion for how to fix this issue.

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

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

Unicode Attribute - Necessary before Unicode Conversion?

We are about to upgrade to ECC 6.0 with a Unicode conversion.
I know that the "Unicode Checks Active" flag must be set in every
customer program in order for the code to run in an ECC 6.0 unicode environment.
My question is does this HAVE to be done before we do the unicode
conversion. What we would like to do is convert the system to ECC 6.0
with Unicode and then apply the transports which set the "Unicode
Checks Active" flag. Since some of these transports contain new
objects, we would prefer to upgrade to ECC 6.0, then convert to unicode
first and apply the transports afterwards, to reduce the risk of potentially needing to rerun
scans.
Ideally we would have cleared all this before the upgrade, but we only
found this issue in our test system after we had upgraded it.
Is this a bad plan?

Hi Chris,
it is not necessary to set the Unicode flag for programming objects in order to succeed with the technical Unicode conversion.
However please keep in mind that the programs without flag will not work in the Unicode environment (as you already stated).
Best regards,
Nils Buerckel
SAP AG

Unicode Conversion

Hi ,
       We are into the initial phase of upgradation from 4.6 to ECC6 .
ineed some of the questions below ...
1.    what is mean by unicode conversion ?
2.    in an object example reoprt or script or bdc or module pool objects what are      need to be done to convert it as ab unicode object ?
3.    next is after working on the unicode object we need to work on the spoue objects .what is mean by that ?
could you guys can clear my dought for the above mentioned question ?
thanks,
vinay

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

Unicode Conversion Problems~

Dear Expert:
I tried to import SAP_BASIS 700_15 to Ecc6 after an upgrade ECC 6.0.
(The Unicode Conversion Guide told me to do some step but need to import the Basis package to 18)
but an error occured return code 8.
check the SAP note 822379 and it said:
SAPKB70011 - SAPKB70016
Symptom: After you import the Support Packages SAPKB70011, SAPKB70012, SAPKB70013, SAPKB70014, SAPKB70015, and SAPKB70016, syntax errors occur in the class CL_GUI_ALV_GRID because corrections from notes have been partially overwritten. This may cause important Basis functions (such as the background systems) to no longer work.
Solution: Before you import the specified Basis Support Packages, see the information in Note 1249184.
after I refer to the note and upload and implement the 1174095 as it said,and import the SAP_BASIS 700_15 again but the error still occured like below.
   R3TRFUGRSPOO was repaired in this system
   R3TRFUGRSPOO was repaired in this system
   R3TRCLASCL_GUI_ALV_GRID was repaired in this system
what should i do ?
Regards
Jack lee

Dear Expert:
after doing what you said.
a error occured as below:
Runtime Errors         SYNTAX_ERROR
Date and Time          03.09.2009 14:43:21
Short text
     Syntax error in program "SAPLKKBL ".
What happened?
     Error in the ABAP Application Program
     The current ABAP program "CL_GUI_ALV_GRID===============CP" had to be
      terminated because it has
     come across a statement that unfortunately cannot be executed.
     The following syntax error occurred in program "SAPLKKBL " in include "LKKBLF01
      " in
     line 238:
     "Activation ID "ALV_PRINT_PARAMS" is unknown."
thank you for your help~
Regards
Jack Lee

Unicode conversion with MDMP, Errors in various TC´s SAINT , SNOTE,

Hallo All,
We perform CU&UC of R/3 4.6C sandbox system to the ERP 6.0 EHP5.
Currently the upgrade phase is completed and Unicode conversion should
be started (we are in the step "Additional Preparation Steps in NW 7.02
non-UC" in the CU&UC guide).
In various transactions (PFCG - Generating of profiles, SPAM/SAINT ) we
received an error "SAP characters 00367 and 00065 are not unique in
character set 1180". As a workaround we temporarily deleted Polish
language (PL) in program RSCPINST and activated (so only codepage 1100
was active). Currently we have activated the Polish language again.
In the source 4.6C system TMB (created by System Copy from productive
system PMB) there was also the configuration in RSCPINST of more than 1
codepage (1100, 1401) and in TCPDB table 1180 codepage was configured
(see attached pictures).
Our question :
How is it possible to avoid this situation in upgrades of following
system (IMB, QMB, PMB)? Could this configuration cause any
problems/inconsistencies during/after Unicode conversion export &
import ?
Regards Peter Gauer

Hello Nils,
After upgrade, before unicode conversion we got the following error message in PFCG, SAINT,..
"SAP characters 00367 and 00065 are not unique in character set 1180"
I got the information from T-Systems that they excluded polish languages out of RSCINST,
then codepage 1100 was used, than T-Systems added polish language again to have the original situation.
First message I got with the simulation (choose blank latin-1)
The required language combination is supported
only in Unicode systems
Please refer to SAP Note 73606.
Now I Choose: 4EU, EuropTranslit
and simulation showed no message above, but went to the next page.
see below
S e l e c t e d   S e t t i n g s :
Language(s):
EN (E) English
FR (F) French
DE (D) German
PL (L) Polish
ES (S) Spanish
Country code:
4EU    EuropTranslit
R e s u l t s :
Code page configuration type:
Non-Unicode - Single Code Page configuration
Processed language entry:
DEFLS
Language(s) and Corresponding Code Page(s):
EN (E) 1180   Transliteration from Latin-2 (...) to Latin-1
FR (F) 1180   Transliteration from Latin-2 (...) to Latin-1
DE (D) 1180   Transliteration from Latin-2 (...) to Latin-1
PL (L) 1180   Transliteration from Latin-2 (...) to Latin-1
ES (S) 1180   Transliteration from Latin-2 (...) to Latin-1
T a s k s :
Required OS locales and their current status:
Locale installed     = the locale is installed correctly
Set locale failed    = the locale needs to be corrected on the app server
citmb07_TMB_07       de_DE.ISO-8859-1               Locale installed
                     en_US.ISO-8859-1               Locale installed
                     fr_FR.ISO-8859-1               Locale installed
                     de_DE.ISO-8859-1               Locale installed
                     es_ES.ISO-8859-1               Locale installed
Required profile parameter modifications:
RSCPINST does NOT change the value of profile parameter.
Please check the value of below parameter(s) after activation.
1) Please update zcsa/installed_languages.
    e.g. Copy the new value and paste it into a field in transaction RZ10
New:                  DEFLS
Current (sorted):
citmb07_TMB_07       DEFLS
2) Please proceed with Check result for below parameter(s):
OK     Checked and no inconsistency found.
Regards Peter

Unicode Conversion check

Similar Messages

Maybe you are looking for