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

Similar Messages

  • 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 conversion problem : File Separator

    Hi,
    I need help regarding Unicode conversion error for SAP program. In one program, I need to change the data type which is not unicode compatiable. Can anyone please help me to change the type, which i mentioned below :
    <b>constants: c_fs_delimiter  type x value '1C'.</b>
    concatenate
    <f1>
    <f2>
    into str separated by <b>c_fs</b>.
    Thanks,
    Yogita

    Have a look at CL_ABAP_CHAR_UTILITIES - this has a lot of separators like this pre-defined as attributes.
    SO to use TAB character,  code:
    concatenate
    <f1>
    <f2>
    into str separated by CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB.
    Andrew

  • Unicode conversion problem after MaxDb upgrade

    Hi to all.
    I upgraded a SapDb instance of a SAP ContentServer from 7.3.0.35 Non Unicode to MaxDB 7.7.0.38.
    After that, I saw that the _UNICODE parameter is set to YES.
    I installed the new Odbc driver of MAxDB 7.7 accordingly to note 698915, but the dll extracted is only the unicode: sqlod32w.dll and not the sqlod32.dll.
    The command
    odbcreg LiveCache -i -p c:\sapdb\<DBNAME>\db\pgm
    doesn't found the dll, so I copied sqlod32w.dll to sqlod32.dll and that command goes well (?!?).
    After that, when from Content Server I try to extract some data, I found, in the CS_trace of Content Server, this error message:
    X-ErrorDescription: "FetchDoc ContentStorage, SQLExecute [SAP AG][SDBODBC DLL][MaxDB] General error;-8046 POS(1) Conversion from UNICODE impossible: 6530 ;ODBC State S1000; Error Code -8046"
    Any suggestions?
    Thanks
    Franco

    Hi Franco,
    what is the name of the file you downloaded from SWDC? I downloaded the package MAXDB7606_20-20000534.SAR and MAXDBART7606_20-20000534.SAR and both did contain a SDBODBC.TGZ package which in turn did contain an ASCII driver sqlod32.lib.
    Did you check this TGZ for the ASCII driver?
    Regards,
    Steffen

  • Problem with field-symbols in UNICODE conversion

    Hi all.
    I'm in a UNICODE conversion project and I have a problem with a program that uses field-symbols.
    DATA: BEGIN OF wa_data_aux,
            mandt LIKE zindices-mandt,
            kschl LIKE zindices-kschl,
            datab LIKE zindices-datab,
            valor LIKE zindices-valor,
            descripcion LIKE zindices-descripcion,
            ernam LIKE zindices-ernam,
            erdat LIKE zindices-erdat,
            waers LIKE zindices-waers,
          END OF wa_data_aux.
    FIELD-SYMBOLS:
                   <fs2>  TYPE ANY,
                   <fs3>  LIKE wa_data_aux.
              <fs2> = <fs3>.
    This assignment results in a DUMP.
    Can anybody help me to solve this problem?
    Thanks!!

    TYPES: BEGIN OF wa_data_aux,
              mandt TYPE mandt,
              kschl TYPE kschl,
              erdat TYPE d,
              waers TYPE waers,
          END OF wa_data_aux.
    DATA: w_aux TYPE wa_data_aux.
    FIELD-SYMBOLS:
    <fs2> TYPE ANY,
    <fs3> TYPE wa_data_aux.
    w_aux-mandt = '300'.
    ASSIGN w_aux TO <fs3>.
    ASSIGN <fs3> TO <fs2>.
    WRITE : / <fs2>.
    GBY.

  • Error while database export in package SAPDODS_33 (Unicode conversion)

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

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

  • Syntax Error while running step 34 (35) after unicode conversion

    Hello,
    We are converting our test system to Unicode to find out how to do it
    in our production system. We are at step 34/35 (Starting RFC job's) in
    the database installation so we are almost done but we have encounted a
    problem that we can't find a solution to. The error log in Sapinst give this
    information:
    ERROR      2008-11-09 11:19:19 [iaxxrfcimp.cpp:1103]           CAbRfcImpl::performFunctionCall FRF-00025  Unable to call function.
    Error message: ?`>?/?????????>??????/_???&<?(????????????????????????????????????????????????? .
    At the same time we can read the following text in dev_w1 (and dev_w0 and so on):
    A  *** ERROR => Syntax error in program SAPLBTCH                                 [abgen.c      1388]
    A  *** ERROR => > Include LBTCHF39                                 line 173 [abgen.c      1390]
    A  *** ERROR => > Statement "âu2018âu2018âu2018âu2018âu2018IF" is not defined. Check your spelling. spelling. [abgen.c      1393]
    The error don't always look the same, here is another example:
    A  *** ERROR => Syntax error in program SAPLSALC                                 [abgen.c      1388]
    A  *** ERROR => > Include LSALCU54                                 line 55 [abgen.c      1390]
    A  *** ERROR => > No component exists with the name "MTSYSIDâu2018MTMCNAMEâu2018MTNUMRANGEâu2018MTUIDâu2018". "MTSYSID [abgen.c      1393]
    A  *** ERROR => > âu2018MTMCNAMEâu2018MTNUMRANGEâu2018MTUIDâu2018". [abgen.c 1395]
    The common thing is Syntax error. If we try to log in to the system using SAP Gui we get this message: "Syntax error in program SAPMS380".
    In the file dev_disp we can read a lot of these:
    Tue Nov 11 14:06:32 2008
    *** WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
    But we should have enough WP since noone has loggen on to the system.
    Facts:
    Tue Nov 11 14:06:07 2008
    kernel runs with dp version 138000(ext=102000) (@(#) DPLIB-INT-VERSION-138000-UC)
    length of sys_adm_ext is 524 bytes
    sysno      60
    sid        S01
    systemid   274 (HP (IA-64) with HP-UX)
    relno      6400
    patchlevel 0
    patchno    258
    intno      20020600
    make:      single threaded, Unicode, 64 bit
    pid        20538
    HPUX on Intel IA64 with Oracle 10.0.2.0.2
    SAP ERP Central Component 5.0
    SAP_ABA     640     0021     SAPKA64021
    SAP_BASIS640     0021     SAPKB64021
    Please let me know that there is some small setting that I can change to regenerate the programs or something like that...
    Br Linus Hellsing

    Hello Ralph
    Here they are:
    TOC files
    SAPAPPL0.TOC:
    vn: R6.40/V1.4
    id: 084ac0df0000003d
    cp: 4102
    data_with_checksum
    tab: [HEADER]
    fil: SAPAPPL0.001 1024
    SAPAPPL1.TOC:
    vn: R6.40/V1.4
    id: 084ac0df0000003d
    cp: 4102
    data_with_checksum
    tab: [HEADER]
    fil: SAPAPPL1.001 1024
    EXPORT log:
    SAPAPPL0.log
    /sapmnt/S01/exe/R3load: START OF LOG: 20081029110702
    /sapmnt/S01/exe/R3load: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#27 $ SAP
    /sapmnt/S01/exe/R3load: version R6.40/V1.4
    Compiled Aug 16 2008 18:01:48
    /sapmnt/S01/exe/R3load -ctf E /mnt/s01_exp_uni/DATA/SAPAPPL0.STR /mnt/s01_exp_uni/DB/DDLORA.TPL /mnt/s01_exp_uni/tmp/sapinst_instdir/ECC50/COPY/EXPORT/ABAP/COPY/NUC/DBEXP/SAPAPPL0.TSK ORA -l /mnt/s01_exp_uni/tmp/sapinst_instdir/ECC50/COPY/EXPORT/ABAP/COPY/NUC/DBEXP/SAPAPPL0.log
    /sapmnt/S01/exe/R3load: job completed
    /sapmnt/S01/exe/R3load: END OF LOG: 20081029110703
    /sapmnt/S01/exe/R3load: START OF LOG: 20081029110709
    /sapmnt/S01/exe/R3load: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#27 $ SAP
    /sapmnt/S01/exe/R3load: version R6.40/V1.4
    Compiled Aug 16 2008 18:01:48
    /sapmnt/S01/exe/R3load -datacodepage 4102 -e /mnt/s01_exp_uni/tmp/sapinst_instdir/ECC50/COPY/EXPORT/ABAP/COPY/NUC/DBEXP/SAPAPPL0.cmd -l /mnt/s01_exp_uni/tmp/sapinst_instdir/ECC50/COPY/EXPORT/ABAP/COPY/NUC/DBEXP/SAPAPPL0.log -stop_on_error
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
    (EXP) INFO: check NameTab widths: Ok.
    (DB) INFO: Export without hintfile
    (RSCP) INFO: UMGCOMCHAR read check, OK.
    (RSCP) INFO: init SUMG interface; package name: "SAPAPPL0".
    (RSCP) INFO: "/mnt/s01_exp_uni/tmp/sapinst_instdir/ECC50/COPY/EXPORT/ABAP/COPY/NUC/DBEXP/SAPAPPL0001.xml" created.
    (RSCP) INFO: environemnt variable "I18N_POOL_WIDTH" is not set. Checks are active.
    (RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
    (RSCP) INFO: UMGSETTINGS nametab creation: ok.
    (RSCP) INFO: Global fallback code page = 9491
    (RSCP) INFO: Common character set is  not  7-bit-ASCII
    (RSCP) INFO: Collision resolution method is 'fine'
    (RSCP) INFO: R3trans code pages = Normal
    (RSCP) INFO: EXPORT TO ... code pages = Normal
    (RSCP) INFO: Check for invalid language keys: activated
    (RSCP) INFO: I18N_NAMETAB_NORM_ALLOW = 999999999
    (RSCP) INFO: I18N_NAMETAB_NORM_LOG   = 1000000002
    (RSCP) INFO: I18N_NAMETAB_ALT_ALLOW  = 10000
    (RSCP) INFO: I18N_NAMETAB_ALT_LOG    = 10003
    (RSCP) INFO: I18N_NAMETAB_OLD_ALLOW  = 0
    (RSCP) INFO: I18N_NAMETAB_OLD_LOG    = 500
    (GSI) INFO: dbname   = "S0120081016081020                                                                                "
    (GSI) INFO: vname    = "ORACLE                          "
    (GSI) INFO: hostname = "scar                                                            "
    (GSI) INFO: sysname  = "HP-UX"
    (GSI) INFO: nodename = "scar"
    (GSI) INFO: release  = "B.11.23"
    (GSI) INFO: version  = "U"
    (GSI) INFO: machine  = "ia64"
    (GSI) INFO: instno   = "1220008646"
    (EXP) TABLE: "/BDL/LOCK"
    (EXP) TABLE: "/BEV1/BO_CONT"
    (EXP) TABLE: "/BEV1/BO_ENQUEUE"
    (EXP) TABLE: "/BEV1/CLCONT1"
    (EXP) TABLE: "/BEV1/CLDEB"
    and so on
    (EXP) TABLE: "ADR9S2"
    (CNV) WARNING: code page conversion problem
                   Number of substitutions: 4
          (row 30 of current buffer, table ADRC)
    CLIENT 30 30 30                                        |000             |
    ADDRNUMBER 30 30 30 30 30 31 34 38 36 39                   |0000014869      |
    DATE_FROM 30 30 30 31 30 31 30 31                         |00010101        |
    NATION 20                                              |                |
    (CNV) WARNING: code page conversion problem
                   Number of substitutions: 2
          (row 41 of current buffer, table ADRC)
    CLIENT 30 30 30                                        |000             |
    ADDRNUMBER 30 30 30 30 30 32 31 39 38 32                   |0000021982      |
    DATE_FROM 30 30 30 31 30 31 30 31                         |00010101        |
    NATION 20                                              |                |
    (RSCP) INFO: 51 lines written to /mnt/s01_exp_uni/tmp/sapinst_instdir/ECC50/COPY/EXPORT/ABAP/COPY/NUC/DBEXP/SAPAPPL0001.xml
    (EXP) TABLE: "ADRC"
    (RSCP) INFO: 3 lines written to /mnt/s01_exp_uni/tmp/sapinst_instdir/ECC50/COPY/EXPORT/ABAP/COPY/NUC/DBEXP/SAPAPPL0001.xml
    (EXP) TABLE: "ADRCOMC"
    and then its the same with table SETHEADERT and SKAT and SNAP and STXH.
    I will not include the whole file as it is 14213 lines long.
    SAPAPPL1.log
    /sapmnt/S01/exe/R3load: START OF LOG: 20081029110701
    /sapmnt/S01/exe/R3load: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#27 $ SAP
    /sapmnt/S01/exe/R3load: version R6.40/V1.4
    Compiled Aug 16 2008 18:01:48
    /sapmnt/S01/exe/R3load -ctf E /mnt/s01_exp_uni/DATA/SAPAPPL1.STR /mnt/s01_exp_uni/DB/DDLORA.TPL /mnt/s01_exp_uni/tmp/sapinst_instdir/ECC50/COPY/EXPORT/ABAP/COPY/NUC/DBEXP/SAPAPPL1.TSK ORA -l /mnt/s01_exp_uni/tmp/sapinst_instdir/ECC50/COPY/EXPORT/ABAP/COPY/NUC/DBEXP/SAPAPPL1.log
    /sapmnt/S01/exe/R3load: job completed
    /sapmnt/S01/exe/R3load: END OF LOG: 20081029110702
    /sapmnt/S01/exe/R3load: START OF LOG: 20081029110709
    /sapmnt/S01/exe/R3load: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#27 $ SAP
    /sapmnt/S01/exe/R3load: version R6.40/V1.4
    Compiled Aug 16 2008 18:01:48
    /sapmnt/S01/exe/R3load -datacodepage 4102 -e /mnt/s01_exp_uni/tmp/sapinst_instdir/ECC50/COPY/EXPORT/ABAP/COPY/NUC/DBEXP/SAPAPPL1.cmd -l /mnt/s01_exp_uni/tmp/sapinst_instdir/ECC50/COPY/EXPORT/ABAP/COPY/NUC/DBEXP/SAPAPPL1.log -stop_on_error
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
    (EXP) INFO: check NameTab widths: Ok.
    (DB) INFO: Export without hintfile
    (RSCP) INFO: UMGCOMCHAR read check, OK.
    (RSCP) INFO: init SUMG interface; package name: "SAPAPPL1".
    (RSCP) INFO: "/mnt/s01_exp_uni/tmp/sapinst_instdir/ECC50/COPY/EXPORT/ABAP/COPY/NUC/DBEXP/SAPAPPL1001.xml" created.
    (RSCP) INFO: environemnt variable "I18N_POOL_WIDTH" is not set. Checks are active.
    (RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
    (RSCP) INFO: UMGSETTINGS nametab creation: ok.
    (RSCP) INFO: Global fallback code page = 9491
    (RSCP) INFO: Common character set is  not  7-bit-ASCII
    (RSCP) INFO: Collision resolution method is 'fine'
    (RSCP) INFO: R3trans code pages = Normal
    (RSCP) INFO: EXPORT TO ... code pages = Normal
    (RSCP) INFO: Check for invalid language keys: activated
    (RSCP) INFO: I18N_NAMETAB_NORM_ALLOW = 999999999
    (RSCP) INFO: I18N_NAMETAB_NORM_LOG   = 1000000002
    (RSCP) INFO: I18N_NAMETAB_ALT_ALLOW  = 10000
    (RSCP) INFO: I18N_NAMETAB_ALT_LOG    = 10003
    (RSCP) INFO: I18N_NAMETAB_OLD_ALLOW  = 0
    (RSCP) INFO: I18N_NAMETAB_OLD_LOG    = 500
    (GSI) INFO: dbname   = "S0120081016081020                                                                                "
    (GSI) INFO: vname    = "ORACLE                          "
    (GSI) INFO: hostname = "scar                                                            "
    (GSI) INFO: sysname  = "HP-UX"
    (GSI) INFO: nodename = "scar"
    (GSI) INFO: release  = "B.11.23"
    (GSI) INFO: version  = "U"
    (GSI) INFO: machine  = "ia64"
    (GSI) INFO: instno   = "1220008646"
    (EXP) TABLE: "/BDL/ADDONKEYS"
    (EXP) TABLE: "/BDL/BADHOST"
    and so on until
    (EXP) TABLE: "SEWADATCOL"
    (EXP) TABLE: "SFHX"
    (CNV) WARNING: code page conversion problem
                   Number of substitutions: 1
          (row 3519 of current buffer, table SFIWP)
    LANGU 4a                                              |J               |
    WORDF 82 41 45 82 a8 82 ad 95 4b 97 56 82 aa 82 a0 82 |.AE.¨..K.V.ª. .|
    WORDF c8 82 55 45 82 b7 81 42 20 20 20 20 20 20 20 20 |È.UE.·.B        |
    WORDF 20 20 20 20 20 20 20 20                         |                |
    and table STERM_TEXT. As before I will not include it all, the log file is 7775 lines long.
    IMPORT log
    SAPAPPL0.log
    /sapmnt/S01/exe/R3load: START OF LOG: 20081106102704
    /sapmnt/S01/exe/R3load: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#27 $ SAP
    /sapmnt/S01/exe/R3load: version R6.40/V1.4 [UNICODE]
    Compiled Aug 16 2008 18:23:56
    /sapmnt/S01/exe/R3load -ctf I /mnt/s01_exp_uni/DATA/SAPAPPL0.STR /mnt/s01_exp_uni/tmp/sapinst_instdir/ECC50/COPY/IMPORT/SYSTEM/ABAP/ORA/UC/DB/DDLORA.TPL /mnt/s01_exp_uni/tmp/sapinst_instdir/ECC50/COPY/IMPORT/SYSTEM/ABAP/ORA/UC/DB/SAPAPPL0.TSK ORA -l /mnt/s01_exp_uni/tmp/sapinst_instdir/ECC50/COPY/IMPORT/SYSTEM/ABAP/ORA/UC/DB/SAPAPPL0.log
    /sapmnt/S01/exe/R3load: job completed
    /sapmnt/S01/exe/R3load: END OF LOG: 20081106102705
    /sapmnt/S01/exe/R3load: START OF LOG: 20081106103529
    /sapmnt/S01/exe/R3load: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#27 $ SAP
    /sapmnt/S01/exe/R3load: version R6.40/V1.4 [UNICODE]
    Compiled Aug 16 2008 18:23:56
    /sapmnt/S01/exe/R3load -dbcodepage 4102 -i /mnt/s01_exp_uni/tmp/sapinst_instdir/ECC50/COPY/IMPORT/SYSTEM/ABAP/ORA/UC/DB/SAPAPPL0.cmd -l /mnt/s01_exp_uni/tmp/sapinst_instdir/ECC50/COPY/IMPORT/SYSTEM/ABAP/ORA/UC/DB/SAPAPPL0.log -stop_on_error -k 54FB9C39DB
    DbSl Trace: ORA-1403 when accessing table SAPUSER
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
    (GSI) INFO: dbname   = "S0120081106091135                                                                                "
    (GSI) INFO: vname    = "ORACLE                          "
    (GSI) INFO: hostname = "scar                                                            "
    (GSI) INFO: sysname  = "HP-UX"
    (GSI) INFO: nodename = "scar"
    (GSI) INFO: release  = "B.11.23"
    (GSI) INFO: version  = "U"
    (GSI) INFO: machine  = "ia64"
    (DB) INFO: /BDL/LOCK created #20081106103642
    (IMP) INFO: import of /BDL/LOCK completed (0 rows) #20081106103642
    (DB) INFO: /BDL/LOCK~0 created #20081106103642
    (DB) INFO: /BEV1/BO_CONT created #20081106103642
    and so on until the end:
    (DB) INFO: ZWF_STATUSCHANGE created #20081106173307
    (IMP) INFO: import of ZWF_STATUSCHANGE completed (0 rows) #20081106173307
    (DB) INFO: ZWF_STATUSCHANGE~0 created #20081106173307
    (DB) INFO: disconnected from DB
    /sapmnt/S01/exe/R3load: job completed
    /sapmnt/S01/exe/R3load: END OF LOG: 20081106173307
    /sapmnt/S01/exe/R3load: START OF LOG: 20081107092517
    /sapmnt/S01/exe/R3load: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#27 $ SAP
    /sapmnt/S01/exe/R3load: version R6.40/V1.4 [UNICODE]
    Compiled Aug 16 2008 18:23:56
    /sapmnt/S01/exe/R3load -dbcodepage 4102 -i /mnt/s01_exp_uni/tmp/sapinst_instdir/ECC50/COPY/IMPORT/SYSTEM/ABAP/ORA/UC/DB/SAPAPPL0.cmd -l /mnt/s01_exp_uni/tmp/sapinst_instdir/ECC50/COPY/IMPORT/SYSTEM/ABAP/ORA/UC/DB/SAPAPPL0.log -stop_on_error -k 54FB9C39DB
    DbSl Trace: ORA-1403 when accessing table SAPUSER
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
    (GSI) INFO: dbname   = "S0120081106091135                                                                                "
    (GSI) INFO: vname    = "ORACLE                          "
    (GSI) INFO: hostname = "scar                                                            "
    (GSI) INFO: sysname  = "HP-UX"
    (GSI) INFO: nodename = "scar"
    (GSI) INFO: release  = "B.11.23"
    (GSI) INFO: version  = "U"
    (GSI) INFO: machine  = "ia64"
    (DB) INFO: disconnected from DB
    /sapmnt/S01/exe/R3load: job completed
    /sapmnt/S01/exe/R3load: END OF LOG: 20081107092541
    /sapmnt/S01/exe/R3load: START OF LOG: 20081107111014
    /sapmnt/S01/exe/R3load: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#27 $ SAP
    /sapmnt/S01/exe/R3load: version R6.40/V1.4 [UNICODE]
    Compiled Aug 16 2008 18:23:56
    /sapmnt/S01/exe/R3load -dbcodepage 4102 -i /mnt/s01_exp_uni/tmp/sapinst_instdir/ECC50/COPY/IMPORT/SYSTEM/ABAP/ORA/UC/DB/SAPAPPL0.cmd -l /mnt/s01_exp_uni/tmp/sapinst_instdir/ECC50/COPY/IMPORT/SYSTEM/ABAP/ORA/UC/DB/SAPAPPL0.log -stop_on_error -k 54FB9C39DB
    DbSl Trace: ORA-1403 when accessing table SAPUSER
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
    (GSI) INFO: dbname   = "S0120081106091135                                                                                "
    (GSI) INFO: vname    = "ORACLE                          "
    (GSI) INFO: hostname = "scar                                                            "
    (GSI) INFO: sysname  = "HP-UX"
    (GSI) INFO: nodename = "scar"
    (GSI) INFO: release  = "B.11.23"
    (GSI) INFO: version  = "U"
    (GSI) INFO: machine  = "ia64"
    (DB) INFO: disconnected from DB
    /sapmnt/S01/exe/R3load: job completed
    /sapmnt/S01/exe/R3load: END OF LOG: 20081107111041
    The log file is 81163 lines long.
    SAPAPPL1.log
    /sapmnt/S01/exe/R3load: START OF LOG: 20081106102702
    /sapmnt/S01/exe/R3load: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#27 $ SAP
    /sapmnt/S01/exe/R3load: version R6.40/V1.4 [UNICODE]
    Compiled Aug 16 2008 18:23:56
    /sapmnt/S01/exe/R3load -ctf I /mnt/s01_exp_uni/DATA/SAPAPPL1.STR /mnt/s01_exp_uni/tmp/sapinst_instdir/ECC50/COPY/IMPORT/SYSTEM/ABAP/ORA/UC/DB/DDLORA.TPL /mnt/s01_exp_uni/tmp/sapinst_instdir/ECC50/COPY/IMPORT/SYSTEM/ABAP/ORA/UC/DB/SAPAPPL1.TSK ORA -l /mnt/s01_exp_uni/tmp/sapinst_instdir/ECC50/COPY/IMPORT/SYSTEM/ABAP/ORA/UC/DB/SAPAPPL1.log
    /sapmnt/S01/exe/R3load: job completed
    /sapmnt/S01/exe/R3load: END OF LOG: 20081106102703
    /sapmnt/S01/exe/R3load: START OF LOG: 20081106103529
    /sapmnt/S01/exe/R3load: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#27 $ SAP
    /sapmnt/S01/exe/R3load: version R6.40/V1.4 [UNICODE]
    Compiled Aug 16 2008 18:23:56
    /sapmnt/S01/exe/R3load -dbcodepage 4102 -i /mnt/s01_exp_uni/tmp/sapinst_instdir/ECC50/COPY/IMPORT/SYSTEM/ABAP/ORA/UC/DB/SAPAPPL1.cmd -l /mnt/s01_exp_uni/tmp/sapinst_instdir/ECC50/COPY/IMPORT/SYSTEM/ABAP/ORA/UC/DB/SAPAPPL1.log -stop_on_error -k 54FB9C39DB
    DbSl Trace: ORA-1403 when accessing table SAPUSER
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
    (GSI) INFO: dbname   = "S0120081106091135                                                                                "
    (GSI) INFO: vname    = "ORACLE                          "
    (GSI) INFO: hostname = "scar                                                            "
    (GSI) INFO: sysname  = "HP-UX"
    (GSI) INFO: nodename = "scar"
    (GSI) INFO: release  = "B.11.23"
    (GSI) INFO: version  = "U"
    (GSI) INFO: machine  = "ia64"
    (DB) INFO: /BDL/ADDONKEYS created #20081106103603
    (IMP) INFO: import of /BDL/ADDONKEYS completed (0 rows) #20081106103603
    (DB) INFO: /BDL/ADDONKEYS~0 created #20081106103603
    (DB) INFO: /BDL/BADHOST created #20081106103603
    (IMP) INFO: import of /BDL/BADHOST completed (0 rows) #20081106103603
    (DB) INFO: /BDL/BADHOST~0 created #20081106103603
    And so on until the end:
    (DB) INFO: ZWF_INVH created #20081107211801
    (IMP) INFO: import of ZWF_INVH completed (116640 rows) #20081107211817
    (DB) INFO: ZWF_INVH~0 created #20081107211818
    (DB) INFO: ZWF_INVI created #20081107211818
    (IMP) INFO: import of ZWF_INVI completed (20557 rows) #20081107211820
    (DB) INFO: ZWF_INVI~0 created #20081107211820
    (DB) INFO: disconnected from DB
    /sapmnt/S01/exe/R3load: job completed
    /sapmnt/S01/exe/R3load: END OF LOG: 20081107211820
    The log file is 52583 lines long.
    There are 55 import log files and 28 export log files.
    I hope some of this information is helpful for you and thank you again for your assistance!
    Br Linus Hellsing

  • Preparing for upgrade and Unicode conversion while on 4.6c

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

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

  • Unicode Conversion in a system landsacpe

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

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

  • 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

  • Error with PS text after Unicode conversion

    Hi, we are having problem after doing unicode conversion with special
    character not displayed correctly in a Web interface. In SAP
    (transaction CN04) everything is OK, but if the PS text is displayed
    through a Web interface (BSP for instance) some characters are
    displayed wrong. One of these characters is the apostrophe in French
    language ('). Is there an available tool to perform a conversion of
    existing PS text after performing unicode upgrade ?

    Hima ... try this
    http://<server>/Lighthammer/JCOProxy?Mode=Reset

  • 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

  • Wrong text in ADRC and LFA1 table after Unicode conversion

    Hello,
    We are doing MDMP to Unicode on SAP 4.7 system.
    In post unicode activities,we had corrected the garbage characters in
    table ADRC
    by converting to target langauage ZH using SUMG t-code.
    Condition used for addind table ADRC in SUMG is LANGU ='1' and
    LANGU_CREA = 'EN'
    But after converting and saving the data,most of the records have
    incorrect character in word.
    and text field of search term/company name/city in table LFA1 are also
    wrong in correspond field in table ADRC.
    Thanks
    Harshavardhan

    Hi Harshavardhan,
    Assumption: You have Chinese entries in table ADRC with ADRC-LANGU_CREA = EN
    Now you have to distinguish two problems:
    1) Chinese texts are stored in ADRC fields, which are NOT used for search help texts (most of the fields - e.g. ADRC-NAME1):
    These texts can be handled in two ways:
    a) Change LANGU_CREA = EN to LANGU_CREA = ZH for these entries (e.g. where ADRC-COUNTRY = CN) before the Unicode conversion (by the way, I would not use ADRC-LANGU, since this is the communication language, which does not necessarily comply with the code page of the entry).
    This needs to be done in a similar way as shown in z-reports described in  SAP Note 634839 ( although this specific fool-the-system case is not covered there - you have to adapt those examples)
    b) Use SUMG to repair the entries using language ZH (as you already did)  
    My favourite would be a), as this can be done before the conversion (Note that SUMG ineeds to be executed during downtime !)
    2) Chinese texts are stored in ADRC fields, which are used for search help texts (e.g. ADRC-MC_NAME1):
    a) If these entries were inserted / changed with logon language ZH, then point 1) applies
    b) If users logged on with logon language EN and created the entries, then most of these texts are destroyed already in Non-Unicode system. Then there is no automatic repair possible (at least point 1 does not work). Here my statement from before is valid:
    Those entries need to be generated again - e.g. if you do a dummy change on the name.
    According to my knowledge, this is a manual effort (either before or after the conversion) - but maybe it can be automized ...
    Best regards,
    Nils Buerckel
    SAP AG

  • Skipped tables during UNICODE conversion

    Hello everybody.
    We are making a unicode conversion in a 701 Ehp4 over iSeries.
    The export has finished succesfully but we have detected that some tables have been skipped. In the Export_monitor.log there are some comments like this one:
    INFO: 2010-04-15 01:30:56 com.sap.inst.migmon.LoadTask processPackage
    Unloading of 'AGKO' export package from database will be skipped.
    Task file '/usr/sap/SAPinst/NW04S/EXP/AGKO.TSK' is empty and contains no tasks.
    Does anyone know why have these tables been skipped?
    Do we have to repeat all the process?
    Thank you in advanced.
    Best regards.
    Rubén Garcí

    Hello
    The problem was related with Inplace method
    Regards
    Ruben

Maybe you are looking for