Upgrading ECC 5.0 to ECC 6.0

Dear Friends,
We are planning to upgrade our SAP version from ECC 5.0 to ECC 6.0.
I need some information from you all;
1. What are the advantages.
2. If we upgrade 32 - bit to 64 - bit what is the difference and why 64 - bit SAP is preferring, what would be the main advantages.
Please clear me in this, i need your support to enhance my knowledge before start the proposed.
Regards,
Praveen Merugu

Dear Praveen Kumar Merugu, 
Since SAP Basis Release 4.0, the 64-bit SAP kernel has been available. The mySAP.com solutions which are based on Web Application Server 6.10 or higher are - with few exceptions - available as 64-bit versions only for operating systems based on 64-bit-capable hardware.
1. 64-bit mySAP.com, what's behind it?
In order to provide a R/3 system as 64-bit version the source code of the R/3 kernel was re-translated. However, the source code itself was not modified. The functions of the 64-bit and the 32-bit versions therefore do not differ.
Basically, 64-bit software differs from the 32-bit version only in the different manner of addressing the memory. 64-bit software uses a 64-bit address pointer which, in theory, can address 18 billion Gb of memory directly. Actually, a 64-bit application can address a lot less with the different operating systems and the hardware available, but still the addressing of several terabyte (that is several 1000 Gbyte) of memory is possible. This is considerably more than required by the components of the myAP.com software.
For a 32-bit address pointer, the address space is limited to about 4 Gbyte; in reality, even less is available to the application. There are examples where this 4 Gbyte limit prevents an efficient operation of a mySAP.com system.
2. Advantages of the 64-bit technology for mySAP.com
The administration of the SAP system is considerably facilitated.
The SAP software can scale the available hardware (RAM, CPU) to a much higher degree.
3. System requirements for 64-bit mySAP.com
a) 64-bit-capable hardware
A basic requirement for using 64-bit operating systems and 64-bit applications is a 64-bit-capable hardware. In particular the version of the used processors (CPU) determines the 64-bit capability of existing hardware. For information on the compatibility of the hardware with 64- bit operating systems you should contact the responsible person at your hardware partner.
b) 64-bit operating system
For using a 64-bit SAP software, an upgrade to a 64-bit operating system may be required. For releases, please refer to the release notes that are available for each database for each SAP kernel release.
c) 64-bit database
When using a 64-bit mySAP.com software, a combination with a 64-bit database version (RDBMS) is recommended by SAP. Databases of SAP, IBM, INFORMIX, and ORACLE have already been supported as 64-bit versions since SAP release 4.0.
4. Exceptions
a) Operating systems on servers with Intel Pentium processors.
The Intel Pentium processor is a 32-bit processor. For this reason, the SAP Software for Microsoft Server operating systems and Linux will still be available in the 32-bit version for the next years to come. In the long run, SAP will change over to the 64-bit version of the SAP software also on these platforms which requires 64-bit Itanium processors. When changing over to the 64-bit version, SAP will also take into account the investment security of their customers.
b) DB2 UDB for Unix and Windows (DB6):
Since the DB2 UDB database allows a mixed operation of 32-bit and 64-bit database client applications as of version 8 only, SAP will make available 32-bit SAP Software of Release 6.x for DB2 UDB systems until the end of 2003.
5. Availability of 64-bit mySAP.com solutions
The latest information on R/3 Release planning can be found on the SAP Website under http://sapnet.sap.com/platforms. Detailed information on the platform combinations released by SAP can be found in SAP release notes under the XX_SER-SWREL component.
All existing 32-bit 4.x releases are supported with 32-bit versions of the SAP kernel until futher notice.
6. Availability of the different 64-bit mySAP.com solutions
a) R/3
R/3 is available as of release R/3 4.0.
b) Business Information Warehouse (BW)
Business Information Warehouse is available with 64-bit SAP kernel as of version 2.0A.
c) Enterprise Buyer Professional (EBP), former BBP
EBP is available with 64-bit SAP kernel as of version 2.0A.
d) Customer Relationship Management (CRM)
Customer Relationship Management is available with 64-bit SAP kernel as of version 1.2.
e) Advanced Planner and Optimizer (APO)
APO is available with 64-bit SAP kernel as of version 3.0A.
7. Possible combinations of 32-bit and 64-bit
a) Possible combinations within a SAP system
For the SAP releases as of 4.0B, a mixed use of 32-bit and 64-bit instances within one SAP system is supported on application server level. 32-bit and 64-bit SAP instances must reside on separate servers, however. The mixed use of 32-bit and 64-bit SAP instances on the same server is not supported.
For the SAP releases as of 4.0, the combination of 32-bit SAP application servers with a 64-bit database server, and of a 32-bit database with 64-bit application servers is possible in principle. Releases for such combinations are granted in justified cases. In case of a mixed installation of a 32-bit SAP application server and a 64-bit database server or vice versa on a shared host, you need to make sure in particular that the SAP application server uses the correct database libraries. A subsequent manual configuration may be required. The database upgrade guide describes how to proceed (see also Ora Note 406140 or 539922, for example).
b) Possible combinations within a mySAP.com system landscape
Transports with 'tp' or 'R3trans' between 32-bit and 64-bit SAP systems are possible.
There are many differences between a 32-bit and a 64-bit SAP system, e.g. the parameter settings of the HP-UX operating system kernel and SAP kernel that do not take into account a combined configuration of test and production systems.
All features and functions that depend on the parameter settings cannot be sufficiently tested  for a 64-bit production environment in a 32-bit test or development system. This includes in particular the effect of the parameter settings on the memory management and the performance of a SAP system.
For this reason, SAP recommends to have at least one other 64-bit system available for each 64-bit production system within the transport track where the availability of SAP kernel, operating system and database can be tested.
c) Interoperability with 32-bit add-on products
For software products of third-party suppliers used with SAP software it is not important whether a 32-bit or a 64-bit SAP R/3 kernel is used. The use of a 32-bit or 64-bit SAP R/3 kernel is completely transparent for add-on products of third party suppliers as long as these products use SAP certified interfaces.
32-bit and 64-bit applications that directly access shared memory segments cannot be combined. For add-on products of SAP with direct access to the shared memory you have to ensure the bit size corresponds to that of the SAP kernel. This is e.g. valid for the product 'saposcol'. With a 64-bit SAP kernel it is only possible to use a 64- bit saposcol.
8. Preparations for the installation of a 64-bit SAP kernel
In addition to the basic requirements, 64-bit hardware, 64-bit operating system and 64-bit database the following aspects are to be taken into account for preparing the installation of a 64-bit SAP kernel:
a) Shared memory
Since there is virtually no limit of the shared memories in the case of a 64-bit SAP you can set large sizes for all buffers. (Refer to the recommendation of SAP Note 103747 under III).
b) Swap space
Addressing a very large memory requires the configuration of a correspondingly large swap space. To use a 64-bit SAP kernel you must at least configure 20 GB swap space.
c) Operating system kernel parameters
Except for some cases the parameter settings of the operating system kernel for a 32-bit and a 64-bit R/3 are identical.  he most important operating system kernel parameters and their values recommended by SAP can be found in Note 146289. For HP-UX please also refer to Note 172747.
INSTALLATION TIPS
The installation of the 64-bit SAP kernel for Release 4.0B and 4.5B is carried out manually. First the system requirements described above must be fulfilled . The installation of the 64-bit SAP kernel is then simply performed by replacing all existing 32-bit executables of the SAP kernel with the corresponding 64-bit executables.
Example:
Initial state:              SAP release       4.5B
             SAP kernel        4.5B 32-bit
             RDBMS             ORACLE 8.0.5  64-bit
             OS:               HP-UX 11.00   64-bit
Target:              SAP release       4.5B
             SAP kernel        4.5B 64-bit
             RDBMS             ORACLE 8.0.5 64-bit
             OS:               HP-UX 11.0   64-bit
Procedure:
The procedure is described in detail in the following SAP notes:
SAP note: 146248    Installation of SAP R/3 4.0B 64-bit kernel
SAP note: 155355    Installation of SAP R/3 4.5B 64-bit kernel
Installation of the 64-bit SAP kernel as of SAP Basis release 4.6B
As of SAP release 4.6B the installation tool R3SETUP is delivered and supported as 64-bit version on CD.
System copy with 64-bit SAP 4.5B (ORACLE)
While unloading an Oracle database with the R3SETUP (32-bit version) it cannot connect to the database if a 64-bit SAP kernel is used.
If you use the 64-bit SAP kernel for Oracle you automatically use a 64- bit Oracle client library as only a 64-bit library can be loaded for a 64-bit SAP kernel. However, since the R3SETUP is only available as 32- bit version up to Release 4.5B and since the 32-bit R3SETUP is not compatible with the 64-bit Oracle client library the error mentioned above occurs in the case of a system copy (in particular during the unload).
While loading the 32-bit SAP kernel is unpacked first so no problems should occur here.
In order to be able to perform a system copy (unload) with the 32-bit R3SETUP follow the instructions of Note 177724.
UPGRADE TIPS
Upgrade from a 32-bit to a 64-bit SAP system
The operating system upgrade and the SAP upgrade should be performed separately (if possible). The same applies to the change of the 32-bit SAP kernel to the 64-bit kernel to ensure that the phases can be tested and completed separately.
As of 4.6C the change to a 64-bit SAP kernel will be supported during an upgrade.
That means that the individual phases like operating system upgrade, database migration and kernel exchange should be included in the planning.
Database
For a database, you need to check whether the binaries have to be replaced during the operating system upgrade. The binaries for HP-UX 10.20 do not run on HP-UX 11, for example!! The corresponding Oracle software for HP-UX 11 must be installed. When upgrading to a 64-bit Oracle 8 version you have to migrate to a 32-bit Oracle 8 version fist. Only then, you can import the 64-bit RDBMS.
The SAP upgrade should always be carried out before the 32-bit SAP kernel is replaced by the 64-bit SAP kernel, since the latter includes an adjustment of the UNIX kernel and the instance parameters.
Sample scenario 1:
     Initial state:                          R/3 release 3.1I
                         SAP kernel  3.1I (32-bit)
                         RDBMS:      ORACLE 7.3.4 (32-bit)
                         OS:         HP-UX 10.20  (32-bit)
    Target:                         R/3 release  4.6B
                        SAP kernel   3.1I  (32-bit)
                        RDBMS:       ORACLE 8.0.5 64-bit
                        OS:          HP-UX 11.0 64-bit
Procedure:
1st alternative:
9. Upgrading the operating system to HP-UX 11.0
10. Installation of the 7.3.4 RDBMS binaries for HP-UX 11.0
11. Migration to 8.0.5 32-bit RDBMS for HP-UX 11.0 (see the instructions guide). This step is required as the database migration from 7 to 8 must always be performed via Oracle 8 32-bit.
12. Subsequent exchange of the RDBMS 8.0.5 32-bit to 8.0.5 64-bit. This step can be performed after the upgrade as well (prior to the SAP kernel exchange).
13. Upgrade of the R/3 system to 4.6B with a 32-bit SAP kernel. The PREPARE unpacks the 32-bit tools automatically so that no manual intervention is necessary.
14. Exchange of the SAP R/3 kernel on 64-bit prior to the upgrade and adjustment of the R/3 kernel and instance parameters
2nd alternative:
15. Migration to 8.0.5 32-bit on HP-UX 10.20
16. Operating system upgrade to HP-UX 11.0
17. Exchange of RDBMS binaries on 8.0.5 64-bit for HP-UX 11.0
18. Upgrade of the R/3 system to 4.6B with 32-bit SAP kernel
19. Exchange of the SAP R/3 kernel on 64-bit
Or (if required)
3rd alternative:
20. Oracle migration to 8.0.5 32-bit (on HP-UX 10.20)
21. Upgrade of the R/3 system to 4.6B with 32-bit SAP kernel
22. Operating system upgrade to HP-UX 11 64-bit
23. Exchange of the Oracle binaries on 8.0.5 64-bit
24. Exchange of the SAP kernel on 4.6B 64-bit
Sample scenario 2:
Initial state:                R/3 release    3.1I
               SAP kernel     3.1I (32-bit)
               RDBMS          Oracle 7.3.4 (32-bit)
               OS             HP-UX 10.20  (32-bit)
Target:               R/3 release     4.5B
              SAP kernel      4.5B 64-bit
              RDBMS           Oracle 8.0.5 64-bit
              OS              HP-UX 11.0 64-bit
Procedure:
The procedure is similar to the one described in the 1. scenario. However, in this case it is not possible to already import the 64-bit SAP kernel in the upgrade phase KX_SWITCH as the 64-bit kernel for Release 4.5B will not be delivered on the upgrade CD. The import of the 64-bit SAP kernel must be manually performed after the SAP upgrade. Release 4.5B will not be delivered on the upgrade CD. The import of the 64-bit SAP kernel must be manually performed after the SAP upgrade.
Do let me know in case of any queries.
Hope this helps you.
Do award points if you found them useful.
Regards,
Rakesh

Similar Messages

  • Interview questions on upgrades from 4.7 to ECC

    Hi,
    Can any one please post some potential areas/questions that will be asked for upgrade projects from 4.7 to ECC6.0
    Points will be awarded.
    Thanks

    Hi Frank,
      this is good question,  why because sap upgrades from 4.6b to ecc 6.0 is very risky.
      take one example , in 4.5b , me21n application having 620 screen where as in ecc 6.0 having 9000 screen . that time we will take care of it.
       check the obsolete function modules ,  4.5b , having ws_upload, ws_download.... use cl_gui_frontend_services , under these having differnt type of methods.
      once you change the code in ecc , go to tranx : SLIN check the error where it is exact.

  • Error during Upgrade from 4.6c to ECC 6.0

    Hi All,
      We are facing an error when upgrading from 4.6c to ECC 6.0. We are facing this error on the table COEP - runtime object inconsistancy. What we found is there is ERP upgrade has created new extra fields in the table. In log file the error is specified as : Duplicate Field name, But we not able to find the duplicate field name in the table.  Please kindly help as early as possible. The upgrade process is stuck.
    Regards
    Anil Kumar K

    Hi Anil,
    Is this issue fixed? Can i know how you fixed it?
    replied to your message Re: How to adopt the index changes during upgrade.
    Thanks,
    Somar

  • Unicode error while upgrading from 4.6 to ECC 6.0

    Dear All,
    I am getting unicode errror while upgrading from 4.6 to ECC 6.0, when iam trying to open downloaded file in excel.
    In debugging, error occurs while executing statment "CALL METHOD OF obj_ex_sheet " in the code given below:
    FORM open_downloaded_file_in_excel            *
    FORM open_downloaded_file_in_excel.
      DATA:
        lv_ole_books       TYPE ole2_object,
        lv_ole_sheets      TYPE ole2_object,
        lv_subrc           LIKE sy-subrc,
        lv_title(70)       TYPE c,
        lv_text1(70)       TYPE c,
        lv_text2(70)       TYPE c.
    start excel
      CREATE OBJECT obj_ex_sheet      'EXCEL.SHEET'.
      IF sy-subrc NE 0.
        lv_subrc = sy-subrc.
        FREE OBJECT obj_ex_sheet.
        PERFORM error_handling_ms_excel USING lv_subrc.
      ENDIF.
      CALL METHOD OF obj_ex_sheet     'Application' = obj_ex_app.
      IF sy-subrc NE 0.
        lv_subrc = sy-subrc.
        FREE OBJECT obj_ex_app.
        FREE OBJECT obj_ex_sheet.
        PERFORM error_handling_ms_excel USING lv_subrc.
      ENDIF.
      SET PROPERTY OF obj_ex_app 'Visible' = 1.
    open data file: main file
      CALL METHOD OF obj_ex_app        'Workbooks'  = lv_ole_books.
      CALL METHOD OF lv_ole_books      'Open'       = obj_ex_wbook
        EXPORTING #1  = gv_filename
                  #2  = 2
                  #3  = 0
                  #4  = 1
                  #5  = 0
                  #6  = 0
                  #7  = 1.
      IF sy-subrc NE 0.
        lv_subrc = sy-subrc.
        FREE OBJECT obj_ex_wbook.
        FREE OBJECT obj_ex_app.
        FREE OBJECT obj_ex_sheet.
        PERFORM error_handling_ms_excel USING lv_subrc.
      ENDIF.
      FREE OBJECT lv_ole_books.
      CALL METHOD OF obj_ex_wbook      'Worksheets' = lv_ole_sheets.
      CALL METHOD OF lv_ole_sheets     'Item'       = obj_ex_wsheet
        EXPORTING #1 = 1.
      FREE OBJECT lv_ole_sheets.
      GET PROPERTY OF obj_ex_wsheet    'UsedRange'  = obj_ex_usedrange.
      CALL METHOD  OF obj_ex_usedrange 'AutoFormat'
        EXPORTING #1 = 18.
      SET PROPERTY OF obj_ex_wsheet    'Name'       = sy-tcode.
      FREE OBJECT obj_ex_usedrange.
      PERFORM free_ole_objects.
      CALL FUNCTION 'FLUSH'
           EXCEPTIONS
                OTHERS = 0.
    ENDFORM.                              
    regards,
    Divya

    hi,
    In the OPEN DATASET STATEMENT ADD THE ENCODING ADDITION IN TEXT MODE.
    Regards,
    Balakumar.G
    Reward Points if helpful.

  • Top-Down Distribution - tcode KE28 (release upgrade from 4.6 to ECC 6.0)

    All,
    we are performing a release upgrade from 4.6 to ECC 6.0 and we have a problem with the tcode KE28.
    The variant already set up in the system don't match with the selection fields present in the screen, and the following message is shown:
    Message no. KG346
    The variant does not adhere to the current Customizing setup
    We have saved the variant again, and no problem are present, but the error message refers also to Customizing setup.
    Is there a section in the Customizing where it is possible set up the field to show in the initial screen or the new fields (All Valuation Views, Legal Valuation View and Profit Center Valuation View) are due to the release upgrade?
    If yes, do you know the transaction/path?
    Thanks in advance for your collaboration.
    Regards,
    Jody Mancini.

    Hi Satish,
    Now i am sending some URL for Functional upgrade
    May be those are all useful toyou
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/erp6/transactionsChangedinECC6.0
    http://solutionbrowser.erp.sap.fmpmedia.com/Default.aspx
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/erp6/
    Regards
    Surya

  • Performance issue after Upgrade from 4.7 to ECC 6.0 with a select query

    Hi All,
    There is a Performance issue after Upgrade from 4.7 to ECC 6.0 with a select query in a report painter.
    This query is working fine when executed in 4.7 system where as it is running for more time in ECC6.0.
    Select query is on the table COSP.
    SELECT (FIELD_LIST)
            INTO CORRESPONDING FIELDS OF TABLE I_COSP PACKAGE SIZE 1000
            FROM  COSP CLIENT SPECIFIED
            WHERE GJAHR IN SELR_GJAHR
              AND KSTAR IN SELR_KSTAR
              AND LEDNR EQ '00'
              AND OBJNR IN SELR_OBJNR
              AND PERBL IN SELR_PERBL
              AND VERSN IN SELR_VERSN
              AND WRTTP IN SELR_WRTTP
              AND MANDT IN MANDTTAB
            GROUP BY (GROUP_LIST).
       LOOP AT I_COSP      .
         COSP                           = I_COSP      .
         PERFORM PCOSP       USING I_COSP-_COUNTER.
         CLEAR: $RWTAB, COSP                          .
         CLEAR CCR1S                         .
       ENDLOOP.
    ENDSELECT.
    I have checked with the table indexes, they were same as in 4.7 system.
    What can be the reson for the difference in execution time. How can this be reduced without adjusting the select query.
    Thanks in advance for the responses.
    Regards,
    Dedeepya.

    Hi,
    ohhhhh....... lots of problems in select query......this is not the way you should write it.
    Some generic comments:
    1. never use SELECT
                       endselect.
       SELECT
      into table
       for all entries in table
      where.
       use perform statment after this selection.
    2. Do not use into corresponding fields. use exact structure type.
    3. use proper sequence of fields in the where condition so that it helps table go according to indexes.
        e.g in your case
              sequence should be
    LEDNR
    OBJNR
    GJAHR
    WRTTP
    VERSN
    KSTAR
    HRKFT
    VRGNG
    VBUND
    PARGB
    BEKNZ
    TWAER
    PERBL
    sequence should be same as defined in table.
    Always keep select query as simple as possible and perform all other calculations etc. afterwords.
    I hope it helps.
    Regards,
    Pranaya

  • What are the key points to beconsider while upgrading from 4.7 to ECC 6.0

    hai
    What are the key points to beconsider while upgrading from 4.7 to ECC 6.0
    please provide sufficient material
    points will be rewarded
    regards
    v.sridhar

    Hi Sridhar,
    Please visit the following links:
    http://service.sap.com/erp
    http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional perspective)
    http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2005 --> Upgrade
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
    For Functionality Differences pls refer to the below site -
    http://solutionbrowser.erp.sap.fmpmedia.com/
    After opening the site, please select the Source Release Version which is 4.6 b Then Select the Target Release Version which is "mySAP ERP 2005" or ECC 6.0
    Select the Solution Area like Financials, Human Capital Management, Sales....
    Select module like MM, PP, SD, and QM.....
    Click on Search
    then it displays the Release Version and the Delta Functionality. Which can be downloaded to a word document if required.
    And also check the release notes of ECC 6.0 in service.sap.com.
    When you are upgrading from 4.6C to ECC6
    Nothing major, follow the same process you'd follow if you were updating PI service packs in R/3 or enhancing data sources. Empty queues in RSA7 and lbwq. Also empty setup tables through lbwg as the upgrade doesn't like it if these tables contain data. This is all on the R/3 side (although you empty RSA7 by running each delta TWICE in BW).
    To transfer queues from lbwq to rsa7, execute jobs through LO cockpit (lbwe).
    Some of your data sources could also be using sm13 instead of lbwq, so do check it out as well.
    For installing ECC 6.0 you required a solution manager key. With out solution manager key you cannot install ECC6.0.
    For ECC 6.0 is called net weaver component here you have ABAP+JAVA stack.
    ECC6.0 supports UNCODE.
    For installing 4.6 you don't require solution manager key. It only having ABAP stack.
    4.6C supports NONUNICODE.
    Major difference is ECC6 is netwear product having WASJAVA+ABAP
    secondly support unicode apart from this we have other diff. you can get form master guide from service.sap.com/instguides.
    Please go through the link that is shown here and if there is any doubts then feel free to ask.
    Major difference is ECC6 is net weaver  product having WASJAVA+ABAP
    secondly support Unicode apart from this we have other diff. you can get from master guide from service.sap.com/instguides
    For installing ECC 6.0 you required a solution manager key. With out solution manager key you cannot install ECC6.0.
    For ECC 6.0 is called net weaver component here you have ABAP+JAVA stack.
    ECC6.0 supports UNCODE.
    For installing 4.6 you don't required solution manager key. It only having ABAP stack.
    4.6C supports NONUNICODE.
    Please also Refer sdn thread and make a small search where u can find lot of information Reg this
    olution Browser would give the differences (Features):
    http://solutionbrowser.erp.sap.fmpmedia.com/ Give source and target versions.
    Release Info:
    ECC 6.0:
    http://help.sap.com/saphelp_erp2005/helpdata/en/43/68805bb88f297ee10000000a422035/frameset.htm
    Refer below and search for posts on this topic on sdn
    There are so many differences between the version in different objects
    I
    These are the some of the settings that are differed in the two versions and in that two objects
    Please visit the following links:
    http://service.sap.com/erp
    http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional prespective)
    http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2005 --> Upgrade
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
    For Functionality Differences pls refer to the below site -
    http://solutionbrowser.erp.sap.fmpmedia.com/
    Upgrade from 4.6c to 6.0 ECC
    upgrade from 4.7 to ecc 6.0
    Please Do Reward If Really Helpful,
    Thanks and Regards,
    Sateesh.Kandula

  • Best Practice in Upgrade from ECC 5.0 to ECC 6.0

    Dear All,
    Can someone help in looking for Best practice in Upgrade from ECC 5.0 To ECC 6.0 Project from Functional FI and CO Side.
    Thanks

    Moved to a different forum.

  • Issues during technical upgrade from 4.6c to ecc 6.0

    Hi
    We are doing a technical upgrade from 4.6C to ECC 6.0. Some transactions in QM module when tested in ECC 6.0 test client give a abap termination message (or dump) and certain transactions like qs42,46, qa18, qs34 etc do not get executed (error = no entry foound for......) and similarly in PP-PI module transactions like C203 have similar problems, even though master data does exist. What should I look for?  Can somebody pl. give details on configuration checks and the OSS notes from a functional point of view for a technical upgrade?
    For certain transactions I get the error message - "Central system of distribution SM-P06CLNT430_TRUSTED is unreachable RFC destination SM_P06CLNT430_Trusted does not exist" - what does this mean?
    thanks
    BE

    Hi,
    1. Have you done successfull installation from 4.6C to ECC 6.0 at the time of PrePare ans SAPUP?
    2. Check SP' for QM and PP-PI modules from http://service.sap.com/sp-stacks.
    3. Configure RFC connections correctly, SM_<SID>CLNT<No>_Trusted automatically created, not manually.
    http://service.sap.com/notes --> search for RFC trusted connections for Ecc 6.0
    http://service.sap.com/upgrade.
    Regards,
    Srini Nookala

  • Upgrade from 4.6c to ecc 6.0

    Hi,
    We are doing a technical upgrade from 4.6c to ecc 6.0 without activating New GL. As a functional consultant, what should i look for? I know that we need to test the business processes and check Z programs but anything specific, plzz let me know.
    What changes should be made in Asset Accounting?
    Regards
    Satya

    Thanks for the reply.
    What are the  changes made in Asset accounting after upgrading?
    I heard of RBE tool...how is it used for FI?? (u check for the mostly used transactions or what??)
    Anyone, plzz answer..waiting for ur replies
    Regards
    Satya

  • Upgrade from 4.7 to ecc 6.0

    hi
    it would be great help if you tell me about the upgrade from 4.7 to ecc 6.0 am an sd functional consutlant so wat would be my role in this upgrade and are the transaction codes and menu path same or have some changes in it and could please tell me some sd transaction code and some interview related question wat they ask while taking an upgrade interview for a sd consultant
    thanks in advance
    priti

    Dear Priti,
    Visit the following link:
    http://solutionbrowser.erp.sap.fmpmedia.com/  .......give source and target versions to find the difference.
    Major difference is ECC6 is netwear product having WASJAVA+ABAP secondly support unicode apart from this we have other diff. you can get fom master guide from service.sap.com/instguides.
    For installing ECC 6.0 you required a solution manager key.With out solutionmanager key you cannot install ECC6.0.
    For ECC 6.0 is called netweaver component here you have ABAP+JAVA stack.
    ECC6.0 supports UNCODE.
    For installing 4.6 you don't required solution manager key.It only having ABAP stack. 4.6C supports NONUNICODE.
    http://help.sap.com/saphelp_erp2005/helpdata/en/43/4d2091de9657bfe10000000a155369/content.htm
    Hope this will help.
    Regards,
    Naveen.

  • Upgrade from 4.0B to ECC 6.0

    Hi
    I have few questions related to upgradation from 4.0B to ECC 6.0 (wrt HR)
    To wat extent it is possible, if yes then how simple or difficult it is ?
    Time Factor (Duration)?  ?(assuming the size of the company close to 1000)
    Do we have any set of standard procedures and guidelines that are to be followed ?
    any helpfull documents to understand the process?
    Thanks in advance..
    Regards
    Rao

    Rao,
    My new project is upgrade project from 4.0B to ECC 6.0 in MM/IM/WM area,
    I have to give an estimate of duration to complete this project.
    Have you started your project. how is it going? how long the project? and any other useful documents please pass on "[email protected]"

  • ECC Upgrade from ECC 5.0 to ECC 6.0 EHP4 - impact on XI 3.0

    Hi,
    We are palnning for upgrade our ECC System from ECC 5.0 to ECC 6.0 EHP4. We do not have any plan of upgrade on XI, which is on XI 3.0.
    After ECC upgrade please provide the impact on XI 3.0 ?
    Will XI 3.0 able to work with ECC 6.0 without any change or any change is required in the XI configuration level, please specify?
    Thanks.

    >>Will XI 3.0 able to work with ECC 6.0 without any change or any change is required in the XI configuration level, please specify?
    As far as I know, no change is required in XI configuration.
    Regards,
    Praveen Gujjeti.

  • After upgrading from 4.6C to ECC 6.0 templates not working in smartform

    Hello,
    After upgrading from 4.6C to ECC 6.0 templates not working properly in smartform, although value is flowing to the point the template is getting called and inside the template there are text elements where placeholders are kept to display the value, when the print is taken there are no values being displayed by the text elements.
    Please note - Text elements doesnot have any conditions present in the condition tabstrip.
    Thanks,
    Abhishek

    Hi,
    After the upgrade, you will have to do the security upgrade.
    Please follow these steps.
    1. Go To SU25
    2. Run step 2A to 2D.
    3. In step 2C, you shall get the list of all the affected roles.
    Click on first role. It will take you to authorizations of that role. Click on the "New" tab there to find the new objects added to the role after the upgrade.
    Note: You can open the same role in the unupgraded system to check.
    4. Provide the access to the required authorization objects.
    5. Disable the unwanted authorization objects.
    6. Generate the profile.
    7. Follow the same steps for all the affected roles listed.
    Please note that you will have a list of new objects added.You need to maintain them inorder to avoid any access issues.
    8. After step 2C, complete 2D.
    Regards,
    Imran

  • Upgrade from 4.7 to ECC 6.0 and MICR no longer printing

    Hello,
    We are in the process of upgrading from 4.7 to ECC 6.0.  Our checks in FI and HR which have MICR fonts/lines are no longer printing the MICR lines.  Any ideas on what to check?

    Hi Kenneth,
    If you have any documentation for Upgrading from 4.7 to ECC 6.0 can you pls send it to me ?
    Thanks
    Christine

  • Schema error after upgrade from 4.6C to ECC 5.0

    Hi all,
    We have recently upgraded from 4.6C to ECC 5.0. We are having problem in payroll run. When I did a syntax check in schema, I got "UDPM" rule doesn't exist. I checked, this rule is present in 4.6C. This is the standard rule. If I am right, it should have come with upgrade right?
    or SAP has changed this? From where Can I get the info about this?
    Also similar error I got in Function 'USTAX' parameter 3 is not allowed. If I remove that parameter, I don't know what is the implication of that.
    I checked for SAP notes. I did not find anything.
    Please let me know if any of you have come with such situation.
    Thanks in advance.
    Sarika.

    Hi Sarika,
    We are also in a similar transition i.e. 4.6C to mysap Ecc5.0 . But we are on Canadian Payroll.
    I had search OSS and got a PDF document regarding " Upgrading to SAP R/3 Enterprize - A User Guide to Canadian mysap HR Customers" . U may be can find a similar one for US payroll. I can give u mine, but it wont be of any use as it is for Canadian Payroll.
    In Canadian mysap Upgrade , the function P0224 has been replaced by function KXDTM . Although P0024 is still in used in Schema K00T for conversion purposes.
    Regards,
    Jay Gandhi

Maybe you are looking for