Unicode conversion to UTF-16

try {
            String stringValue = "abc\u5639\u563b";
            byte[] valueInUTF8 = stringValue.getBytes("UTF-8");
            stringValue = new String(valueInUTF8, "UTF-8");            
            System.out.println(string);
        catch (Exception e) { //UnsupportedEncodingException
            e.printStackTrace();
        }current output :- abc??
how can i print it properly in UTF format?

The tranformation            String stringValue = "abc\u5639\u563b";
            byte[] valueInUTF8 = stringValue.getBytes("UTF-8");
            stringValue = new String(valueInUTF8, "UTF-8");            
does nothing except use up memory and CPU cycles. The original content of 'stringValue' is UNICODE characters. The updated 'stringValue' will contain exactly the same characters as the old 'stringValue'.

Similar Messages

  • 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

  • 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

  • Could you pls give the details about the Unicode conversion during Upgrade

    Hi,
    Can anyone give details about the Unicode conversion during SAP Upgradation fro 4.6C to ECC6.
    Waiting for quick response
    Best Regards,
    Padhy

    Hi,
    These are the few points i gathered during my upgradation project.
    Before starting any upgradation project, it is necessary to take up the back-up of the existing systems. As we are going to upgrade the entire system, we will be changing so many things and if something happens, without back-up, we will be in a trouble.
    So it is advised to keep a back-up of the existing system.
    Say for example we have the existing system E4B which is of Version 4.6C. Now we want to upgrade it to Version 4.7. Let us see how we can do it.
    Version upgrades not only means that we need to run the new Version CD over the existing Version System but only involves some other thing.
    Version Upgrade involves the following Steps.
    Say we want to upgrade for Version 4.7 from Version 4.6, which is in the System E4B. Now we created one more system called as E1B in which the upgradation for Version 4.7 can be done.
    • First copy the entire E4B system into the E1B System which is created for Version 4.7.
    • Apply the Version 4.7 CD provided by SAP over the E1B System.
    • Now check whether all the functionalities that was in E4B system works fine with E1B system also.
    Thus the Version Upgrade involves two steps.
    1. SAP Upgradation with the help of the CD
    2. Manual Upgradation.
    1. SAP Upgradation with the help of the CD
    This is nothing but after taking the copy of the existing system into a new system, the upgradation CD from SAP is applied over the new system.
    2. Manual Upgradation.
    This Manual Upgradation involves
    2.1 Upgradation of Standard Objects
    2.1.1 SPAU Objects
    2.1.2 SPDD Objects
    2.2 Upgradation of Custom Objects.
    Upgradation of Custom Objects can be placed under the following three categories.
    Unicode Compliance
    Retrofit
    Upgrade
    Please Find below some of the common Unicode Errors and their solutions
    1. Error:
    In case of Translate Error; ‘Dangerous use of Translate in Multilingual system.’
    Correction:
    To correct the Error occurring on TRANSLATE statement – use this additional statement before the Translate statement.
    SET LOCALE LANGUAGE sy-langu.
    This statement defines the Text Environment of all the programs & internal sessions in the language specified in the LANGUAGE KEY, which in this case is “sy-langu”, i.e. the log on language of the user.
    2. Error:
    In case of Open Dataset Error; ‘Encoding Addition must be included.’
    Correction:
    This Error occurs only when the MODE is TEXT.
    To correct the Error occurring on OPEN DATASET statement – use this statement instead.
    OPEN DATASET dataset_name FOR access IN TEXT MODE ENCODING DEFAULT.
    Where: dataset_name – NAME OF THE DATASET.
    Access – INPUT or OUTPUT or APPENDING or UPDATE.
    DEFAULT - Corresponds to UTF-8 in UNICODE systems &
    NON_UNICODE in NON-UNICODE systems.
    3. Error:
    In case of the usage of the Obsolete FM UPLOAD/DOWNLOAD or WS_UPLOAD/DOWNLOAD; ‘Function module UPLOAD is flagged as obsolete.’
    Correction:
    The FM GUI_DOWNLOAD/UPLOAD is used.
    The variations to be made in the parameters of the FM:
    1. Filename – It must be of STRING type.
    2. Filetype – “DAT” is not used any longer, instead “ASC” is used.
    3. Field Separator – The default value “SPACE” is used, incase for a TAB separated file “X” can be used.
    4. Error:
    In case of CURRENCY/UNIT Addition Error; ‘Use addition CURRENCY/UNIT when outputting.’
    Correction:
    The CURRENCY addition specifies the currency-dependant decimal places for the output of the data objects of type i or p. To obtain the currency-key, the field CURRKEY of the table TCURX is used. The system determines the number of the decimal places from the field CURRDEC of the selected CURRKEY.
    To correct this error follow the following method:
    WRITE: /3 'TOTAL',' ', TOTAL.
    WRITE: /3 ‘TOTAL’,’ ‘, TOTAL CURRENCY ‘2’. --- Where ‘2’is the Currency Key for Getting 2 decimal places.
    5. Error:
    In case of TYPE X Error; ‘Variable must be of C, N, D, T or STRING type.’
    Correction:
    We need to change all the Type X (Hexadecimal) variables to Type C with their values unchanged.
    So the method to be followed is:-
    1. Load the definition of the class CL_ABAP_CONV_IN_CE or CL_ABAP_CHAR_UTILITIES.
    2. Declare the variable as Type C, and use the method UCCP(‘XXXX’) of the class CL_ABAP_CONV_IN_CE where XXXX represents the 8-bit Hexadecimal value and incase the variable holds a Hex value for a Horizontal Tab , then the Attribute “HORIZONTAL_TAB” of the class CL_ABAP_CHAR_UTILITIES can be used directly instead of using the method UCCP.
    E.g.:
    i) *DATA: TAB TYPE X VALUE 09, “Tab character
    CLASS: CL_ABAP_CHAR_UTILITIES DEFINITION LOAD.
    DATA TAB TYPE C VALUE CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB.
    ii) * DATA: CHAR TYPE X VALUE 160.
    CLASS: CL_ABAP_CONV_IN_CE DEFINITION LOAD.
    DATA CHAR TYPE C.
    CHAR = CL_ABAP_CONV_IN_CE=>UCCP(‘00AO’).
    (Here ‘00A0’ is the Hexadecimal equivalent of the decimal 160).
    3. Incase the TYPE X Variable has a length more than 1, then an internal table must be created for the variable.
    E.g.:
    CLASS: CL_ABAP_CONV_IN_CE DEFINITION LOAD.
    DATA : LF(2) TYPE X VALUE 'F5CD'.
    DATA : BEGIN OF LF,
    A1 TYPE C,
    A2 TYPE C,
    END OF LF.
    LF-A1 = CL_ABAP_CONV_IN_CE=>UCCP('00F5').
    LF-A2 = CL_ABAP_CONV_IN_CE=>UCCP('00CD').
    6. Error:
    In case of the Character “-“Error; ‘The Character “-“can’t appear in names in Unicode Programs.’
    Correction:
    The Character “-“(Hyphen) appearing in Variable names is replaced by the character “_” (Under Score) for Unicode/Upgrade Compliance.
    E.g.:
    *wk-belnr LIKE bkpf-belnr,
    *wk-xblnr LIKE bkpf-xblnr,
    *wk-date LIKE sy-datum,
    *wk-wrbtr LIKE bseg-wrbtr,
    *wk-name1 LIKE lfa1-name1,
    *wk-voucher(8) TYPE c.
    wk_belnr LIKE bkpf-belnr,
    wk_xblnr LIKE bkpf-xblnr,
    wk_date LIKE sy-datum,
    wk_wrbtr LIKE bseg-wrbtr,
    wk_name1 LIKE lfa1-name1,
    wk_voucher(8) TYPE c.
    7. Error:
    In case of The SUBMIT-TO-SAP-SPOOL Error; ‘you should not use the statement SUBMIT-TO-SAP-SPOOL without the WITHOUT SPOOL DYNPRO addition. ‘
    Correction:
    1. Declare variables of type PRI_PARAMS, ARC_PARAMS, and a variable of TYPE C which would be used as a VALID FLAG.
    2. Call the FM GET_PRINT_PARAMETERS:
    CALL FUNCTION 'GET_PRINT_PARAMETERS'
    EXPORTING
    ARCHIVE_MODE = '3'
    DESTINATION = P_DEST
    IMMEDIATELY = 'X'
    IMPORTING
    OUT_ARCHIVE_PARAMETERS = archive_parameters
    OUT_PARAMETERS = print_parameters
    VALID = valid_flag
    EXCEPTIONS
    INVALID_PRINT_PARAMS = 2
    OTHERS = 4
    3. Use the SUBMIT-TO-SAP-SPOOL statement.
    E.g.:
    •     submit zrppt500
    •     using selection-set 'AUTO3'
    •     with res_no eq lo_rsnum
    •     with sreserv in preserv
    •     to sap-spool destination p_dest
    •     immediately 'X'. "print immediate
    DATA: print_parameters type pri_params,
    archive_parameters type arc_params,
    valid_flag(1) type c.
    CALL FUNCTION 'GET_PRINT_PARAMETERS'
    EXPORTING
    ARCHIVE_MODE = '3'
    DESTINATION = P_DEST
    IMMEDIATELY = 'X'
    IMPORTING
    OUT_ARCHIVE_PARAMETERS = archive_parameters
    OUT_PARAMETERS = print_parameters
    VALID = valid_flag
    EXCEPTIONS
    INVALID_PRINT_PARAMS = 2
    OTHERS = 4
    Submit zrppt500
    Using selection-set 'AUTO3'
    With res_no eq lo_rsnum
    with sreserv in preserv
    to sap-spool
    SPOOL PARAMETERS PRINT_PARAMETERS
    ARCHIVE PARAMETERS ARCHIVE_PARAMETERS
    WITHOUT SPOOL DYNPRO.
    8. Error:
    In case of Message Error; ‘Number of WITH fields and number of Place Holders are not same ‘.
    Correction:
    Split the statement after WITH into the same number as the place holder for that Message ID.
    E.g.:
    1. * MESSAGE E045.
    MESSAGE E045 WITH '' ''.
    2. in program ZIPI0801
    •     Start of change for ECC6
    •     message e398(00) with 'Could not find access sequence'
    •     'for condition type:'
    •     p_ptype.
    message e398(00) with 'Could not find '
    'access sequence'
    'for condition type:'
    p_ptype.
    •     End of change made for ECC6
    9. Error:
    In case of Move between 2 different Structures; ‘The structures are not mutually convertible in a Unicode program.’
    Correction:
    Make both the Data Types compatible and then assign the contents.
    E.g.:
    The statement –“move retainage_text to temp_text.” Gives an error, where RETAINAGE_TEXT is an internal table and TEMP_TEXT is a string of length 200.
    A Feasible solution for this is to specify from which position to which position of the string, the fields of RETAINAGE_TEXT should be assigned.
    TEMP_TEXT+0(1) = RETAINAGE_TEXT-DQ1.
    TEMP_TEXT+1(1) = RETAINAGE_TEXT-HEX.
    TEMP_TEXT+2(20) = RETAINAGE_TEXT-FILLER1.
    TEMP_TEXT+22(15) = RETAINAGE_TEXT-AMT_DUE.
    TEMP_TEXT+37(8) = RETAINAGE_TEXT-TEXT.
    TEMP_TEXT+45(10) = RETAINAGE_TEXT-DUE_DATE.
    TEMP_TEXT+55(1) = RETAINAGE_TEXT-DQ2.
    10. Error:
    In case of ‘no description found’; ‘add a GUI title’.
    Correction:
    In this type of error gui title is generally missing so add a GUI title to the module pool.
    11. Error:
    In case of ‘writing internal or transparent table’
    Correction:
    Write individual fields.
    E.g.:
    WRITE: / EXT. --> EXT should be a character type field
    WRITE: / EXT-ZZSTATE, EXT-LINE_NO, EXT-LINE_TXT, EXT-AMT, EXT-ZZSKUQTY.
    12. Error:
    In case of ‘combination reference table/field S541-UMMENGE does not exist’
    Correction:
    Was due to error in reference table S541. TABLE S541 has errors
    1)”Foreign key S541- ZZMARKET (ZZMARKET AND KATR2 point to different domains)”
    2)”Foreign key S541-ZZACQUIGRP (ZZACQUIGRP AND KATR8 point to different domains)”
    Changed the domain of ZZMARKET (from ZMKCODE to ATTR2)
    And that of ZMKCODE (from ZACCODE to ATTR8)
    13. Error:
    In case of ‘KEY does not exist’
    Correction:
    The reference table for field KBETR was KNOV earlier changed it to RV61A as KNOV was in turn referring to RV61A.
    14. Error:
    Incase of ‘WRITE’ statement, ‘Literals that take more than one line is not permitted in Unicode systems.’
    Correction: To correct this error, we need to align the spaces accordingly so that the statement doesn’t go beyond the line.
    15. Error:
    Incase of Data statement, ‘The data type ZWFHTML can be enhanced in any way. After a structure enhancement, this assignment or parameter might be syntactically incorrect………..’
    Correction: To correct this error, instead of “like” in the Data statement, use “type”.
    16. Error:
    Incase of DESCRIBE statement, ‘DESCRIBE can be used only with IN BYTE... Or IN CHARACTER mode in Unicode systems.’
    Correction: To correct this error, use additional text, IN BYTE MODE / IN CHARACTER MODE along with this statement.
    CHARACTER MODE is added when the data object is of flat/ character type.
    BYTE MODE is added when the data object is a deep structure.
    Syntax: DESCRIBE FIELD data_obj : LENGTH blen IN BYTE MODE,
    LENGTH clen IN CHARACTER MODE.
    Where blen and clen must be of type I.
    17. Error:
    Incase of DO-LOOP Error,’ In Do loop range addition needed‘
    Correction:
    An internal tables is declared and the two fields (VARYING field and NEXT field) were
    Included inside the internal table
    E.g.: In program SAPMZP02
    DO 11 TIMES
    •     VARYING STATION_STATE FROM STATION1 NEXT STATION2. “ECC6
    CASE SYST-INDEX.
    WHEN ‘1’
    STATION_STATE = STATION1.
    WHEN ‘2’
    STATION_STATE = STATION2.
    WHEN ‘3’
    STATION_STATE = STATION3.
    WHEN ‘4’
    STATION_STATE = STATION4.
    WHEN ‘5’
    STATION_STATE = STATION5.
    WHEN ‘6’
    STATION_STATE = STATION6.
    WHEN ‘7’
    STATION_STATE = STATION7.
    WHEN ‘8’
    STATION_STATE = STATION8.
    WHEN ‘9’
    STATION_STATE = STATION9.
    WHEN ‘10’
    STATION_STATE = STATION10.
    WHEN ‘11’
    STATION_STATE = STATION11.
    18. Error:
    Incase of the parameter QUEUE-ID Error,’ QUEUE-ID’ is neither a parameter nor a select option in program rsbdcbtc.’
    Correction:
    The parameter in program rsbdcbtc is QUEUE_ID and so is changed in this program
    E.g.: In program Z_CARRIER_EDI_INTERFACE
    •     submit rsbdcbtc with queue-id = apqi-qid and return. "ECC6
    •     The parameter name changed by replacing '-' with '_' as in program rsbdcbtc "ECC6
    Submit rsbdcbtc with queue_id = apqi-qid and return. "ECC6
    19. Error:
    Incase of EPC Error,’ Field symbol <TOT_FLD> is not assigned to a field ‘.
    Correction:
    This error couldn't be rectified as the error occurs in a Standard SAP include- LSVIMF29.
    The OS Note - 1036943 needs to be applied.
    Error:
    OPEN DATASET P_FILE FOR OUTPUT IN TEXT MODE.
    Correct:
    OPEN DATASET P_FILE FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
    Error:
    Constants : c_tab type x value '09' .
    Correct:
    Constants : c_tab type abap_char1 value cl_abap_char_utilities=>horizontal_tab .
    Error:
    Data : begin of output_options occurs 0 . Include structure ssfcompop.
    Data : end of output_options .
    Correct:
    Data : output_options type standard table of ssfcompop with header line .
    Error:
    PARAMETERS : NAST TYPE NAST .
    Correct:
    PARAMETERS : NAST TYPE NAST NO-DISPLAY .
    Replace WS_DOWNLOAD and WS_UPLOAD by
    GUI_UPLOAD and GUI_DOWNLOAD and check the import and export parameter types , do the changes accordingly. Because FILENAME paramater type is different because of this it will give dump.
    For issue during Issue using SO_NEW_DOCUMENT_ATT_SEND_API1 Function module, the solution is After this FM we should put COMMIT WORK.
    Issue:
    Moving data from one structure to another structure if those two structures are not compatible
    Solution:
    we should use move-corresponding or field by filed we need to move it.
    If database structures are different in 4.6c and ECC6.0,
    Then we should go with append structure concept.
    While testing the report if it gives dump at Select query level or any database or view level,then just goto that table or view and goto the data base utility(se14) adjust the database. But make sure that selected radio button in se14 transaction should be activate and adjust database
    Also Check this link.
    http://help.sap.com/saphelp_nw04/helpdata/en/62/3f2cadb35311d5993800508b6b8b11/frameset.htm
    Reward points if helpful.
    Regards,
    Ramya

  • 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

  • Combined Upgrade and Unicode conversion of Sap 4.6C to ECC6.0

    Hello all,
    my project team intends to carry out a combined upgrade and unicode conversion of an SAP ERP 4.6C system with MDMP to ECC6.0 (no enhancement package). The system is running on Oracle 10.2.
    In preparation for this upgrade, I have gone through the SAP notes 928729, 54801.
    We need to get a rough estimate of the entire downtime so as to alert our end users. From the CU&UC documentation in 928729, I read up note 857081. However the program in this note cannot be used to estimate the downtime as my system is < SAP netweaver 6.20.
    Is there any other SAP note or tool or program that I can use to estimate the downtime for the entire CU&UC? Thanks a lot!

    Hi,
    Combined upgrade depend upon number of factors like database size, resources on the server and optimization. In order to get idea of how much downtime, it will take, I would suggest you to do combined upgrade and unicode conversion on sandbox system which should be the replica of your production system. And try to optimize it. From there you can get approx. downtime required.
    Also, please read combined upgrade and unicode conversion guides on  http://service.sap.com/unicode@sap
    Thanks
    Sunny

  • SAP R/3 4.6 C to ECC 6.0 Upgrade using CU &UC method- Unicode conversion

    Basis Gurus
       I am working on upgrade from R/3 4.6C to ECC 6.0.
    ECC 6.0 upgrade completed( still in non Unicode).  Now I am in the process of Unicode conversion.
    I have used following methods for the upgrade.
    1. Combined Upgrade & Unicode conversion(CU & UC)
    2. Resource minimized( as I am doing it in Sandbox).
      As I understand I need to perform the DB export and Import now for the unicode conversion.
      According to the Upgrade document, First I need to run Export using R3load in ECC6.0(Non unicode)
      and then install Unicode system and import the same data file.
      My understanding was, when I choose, Resource minimized, I need to run Export and import
      in the same system.
      Can you please help me , whether I need another Unicode system for import ??
    Graham

    Hi,
    Dont get confused with upg strategy and unicode conversion.
    In general Upgrade strategy (either downtime-minimized/resource minimized)
    In unicode conversion you have export/import(exp/imp) of data concept
    In CU&UC approach you have to do in a streach to complete migrate from old release to new realease ECC 6.00.
    Using database independent (sapinst only) or Using database dependent (migration monitor or Distribution monitor)
    It can be done in 2 ways.
    If you dont have addtional server for unicode conversion
           1)you can either do exp on same hardware and take bakup and do import using the exp dump.
           2)Do exp on one server and prepare your target empty database on another server and complete imp of data.
    Hope this is clear.
    Regards,
    Vamshi.

  • 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 situ

    Hi SCN,
    I'm looking at the possibility of running a Combined Upgrade & Unicode Conversion (CUUC) in-situ; i.e. without a migration to new hardware.
    However in all my years of SAP Basis projects any Unicode conversion I've seen has involved a migration to new hardware (which makes good sense as the process is the same as an OSDB migration with R3load/MigMon).
    What I want to know is - has anyone ever run one in-place. I.e. keeping the same server and running the CUUC entirely inplace?
    This seems logically problematic as you need a target system to import to.
    I can imagine a process along these lines though...:
    1. Take SAP layer offline
    2. Run full backup of system
    3. Export system
    4. Drop database* (to make clean ready for new import)
    5. Run SPUMG/SUMG/SAPINST to setup Unicode database ready to receive import...
    6. ....and continue to run import into that database
    7. Complete Unicode conversion process
    However the big issue here for me is
    (a) *dropping the live production system is far from attractive.... I'm presuming everyone would do as I've always seen and combine this with a migration to new improved hardware, so that a backout to the old system is simple
    (b) I'm not sure at what point with the SAP tools (SPUMG/SUMG/SAPINST) this process would become convoluted with it all being in-situ on the same box. I.e. I'm not sure if it's something the SAP tools are really designed to cater for.
    Any input/discussion on these points would be very welcome.
    Regards, doonan_79

    FYI Community. Feeling after reading and research is to use a temorary server to import unicode converted system data into; then swing disks back to the original host. Making all required hostname updates during the process.
    Allowing for parallel export/import, but going back to the original configured host to complete the process.

  • How to go for Unicode conversion?

    Hi All,
    Presently i'm upgrading my SAP 4.7 system (6.2 WAS) in to ERP 2004 (6.40 WAS), which is an non-unicode upgrade.
    Now should i first complete Unicode conversion or apply the latest SP stack.
    Also please tell me how this Support pack will affect me in Unicode conversion?
    Order of this steps will be really helpful for smooth flow of work
    Thanks in Advance

    If you have already completed your upgrade, the best practice would be to install the SP stack first in order to have the latest updates available for the unicode migration tools.  Then proceed with the unicode migration.  There are slight differences in the process between support packages where you may have to create a migration program manually in an older support package and the very same migration program is included in the later support package.  SAP publishes separate unicode migration guides, based on the support package level, due to these updates.

  • 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

  • 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

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

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

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

Maybe you are looking for

  • Not as fluid as 10.8.3 after update to 10.8.4

    When i update my MBPR from 10.8.3 to 10.8.4 this morning, my Mac become a bit laggy. When i open mission control, the process is not as fluid as before, and also dragging windows on the screen, the process is also not as fluid as before. Does anyone

  • How to detect that ADF page has completely loaded with OpenScript

    In Selenium tests I use AdfPage.isSynchronizedWithServer to detect whether an ADF page has completely loaded. I attempted to do the same with OpenScript by doing something like: boolean loading = true; while (loading) { String[] result = web.document

  • Connection Broker Event 802

    I have a Server 2012 R2 with all Remote Desktop roles and a number of Hyper-V VMs on it. This was all working fine until I replaced the (separate) domain controller. I had trouble with seeing the second domain controller (which is one of the VMs on t

  • Server ALERTs 'from' email address

    Can someone remind me what email address such Alerts are sent from. Is it something like [email protected] or [email protected] We want to process these emails elsewhere and forward to multiple recipients. Just to know where, the

  • KB953804 for delegatesentitemsstyle in Outlook 2003 in combination with Exchange Server 2010 SP1 not working.

    KB953804 Full  title  "Hotfix for An e-mail message does not appear in a user's mailbox if the e-mail message was sent on behalf of the user by a delegate in Outlook 2003."  We have this working for ok Outlook 2003 SP3 in combination with Exchange Se