Upgrade changes from 4.7 to ECC 5.0 in HR

Hi Experts,
    Can somebody give an idea on changes that took place while upgrading from 4.7 to ECC 5.0?
    1. What are the major uni-code changes that we have in ECC 5.0 compared to 4.7? I know the unicode check is present in 4.7 too (like WS_UPLOAD & WS_DOWNLOAD are obsolete) But are there any major unicode checks that we have to deal with while upgrading to 5.0?
   2. Are there any specific screen flow changes that we need to make a note for HR module?
  3. Any changes that can be found from using transactions SPDD and SPAU?
Any reply would be really appreciated...
Thanks in Advance,
RVSS.

>     Can somebody give an idea on changes that took place while upgrading from 4.7 to ECC 5.0?
http://solutionbrowser.erp.sap.fmpmedia.com
http://service.sap.com/releasenotes
>     1. What are the major uni-code changes that we have in ECC 5.0 compared to 4.7? I know the unicode check is present in 4.7 too (like WS_UPLOAD & WS_DOWNLOAD are obsolete) But are there any major unicode checks that we have to deal with while upgrading to 5.0?
Upgrade and Unicode conversions are two different things.
You may read
Note 367676 - Release upgrade from 4.6 to 6.10 for customer programs
Note 689951 - Release upgrade from 6.20 to 6.40 for customer programs
>    2. Are there any specific screen flow changes that we need to make a note for HR module?
check the corresponding release notes in
http://service.sap.com/releasenotes
>   3. Any changes that can be found from using transactions SPDD and SPAU?
What do you  mean? Those transaction are for the technical modification adjustment.
Markus

Similar Messages

  • Transaction changes from 4.7 to ECC 6.0

    Hello,
    we are planning a release change from 4.7 to ECC 6.0.
    We need to know which transaction will be replaced or changed.
    We need to know this for planning test etc.
    Gruß
    Toni

    Hi Antonio,
    Please refer this wiiki link for
    Transactions Changed in ECC 6.0 - ERP Upgrade - SCN Wiki
    Regards,
    R.Brahmankar

  • TCodes that have changed from 4.7 to ECC 6

    Hi,
    We are planning a upgrade from 4.7 to ECC6. Is there any readily available list of:
    1) Transaction Codes that have undergone a change from 4.7 to ECC 6?
    2) transactions that have become obsolete?
    Regards
    Peter

    Thanks Gautham for the prompt response.
    That means that I can only come to know of the changed TCodes after I upgrade and not before that? Or can I look at this table in any other company's ECC 6 system and get the data?
    Will company specific cutomisation have any bearing on the changes done by SAP to the std TCodes?
    Also does this table give the complete list of changed TCodes?  Also is there any table, FM etc which also gives what has been changed in these TCodes?
    Peter

  • ABAP Upgrading steps from 4.6 to ECC 6.

    Hi Experts,
    Could you please let me know the steps to upgrade from 4.6 to ECC 6?
    As an abapers what are the steps need to take care during upgradation.
    Please give me the step by step approach.
    Thanks
    Kaki

    Hi,
    First you need to take inventory of all Z developments ( Reports, FM's....)
    Find out the Impacted FM's and programs....!!!
    check for all the cloned programs/Includes...
    check if the system is unicode enabled.
    SPAU corrections
    SPDD corrections
    If System if Unicode ( correct unicode errors )
    correct the obsolete FM's and obsolete declarations.
    Correction for errors at time of testing.....SAP notes will help a lot in correcting many errors..
    post go live support ....!!!
    Few important points :-
    FM “LIST_TO_SPOOL” not in ECC6.0.  use FM is “LIST_TO_ASCII”.
    Table TVARV has become obsolete. New table TVARVC has been introduced. We copied data from TVARV to TVARVC. ( check SAP note for Details )
    Took back up of data in table T512W to T512B .Data can be restored after upgrade using the report “RPU12W0C”. ( check SAP note for Details )
    FMs like “WS_UPLOAD” and “WS_DOWNLOAD” are obsolete now. The new FMs are “GUI_UPLOAD” and “GUI_DOWNLOAD”.
    New Debugger is introduced.....Debugging is easy and user friendly.
    u'll have to change few BDC screen numbers.....whose Screen numbers are changed in ECC...( u'll come accross this errors in Unit testing)
    let me know.......if you need any more information....As you start working on the Upgrade...!!!!
    Regards,
    Nikhil

  • Upgrade procedure from 4.6c to ECC 6.0

    Hi
    I had gone through SAP solution browser tool and observed the differences for 4.6C and 6.0
    Can u please let me know How to start and end  the upgrade project i.e sequence of activities.
    1) should the configuration be done in ECC 6.0 same as 4.6C?
    2)master data upload?
    3)Z-objects movement from 4.6C to 6.0....?
    4)Open PO's and stock upload......in ECC 6.0 ?
    5) what are the precautions to be taken before Go-live?
    Please send any links for upgrade procedure from 4.6C to 6.0 i.e sequence of activities.........
    Thanking you
    Deepak

    Hi,
    About your questions:
    1) should the configuration be done in ECC 6.0 same as 4.6C?
    The configuration (if you mean how the system is configured from the Basis point of view) will be almost the same as you had in 4.6C. Of course you will find new aspects you don't have in the old version (for example the integrated ITS, ICM, etc.), but you will have the system running after the upgrade.
    2)master data upload?
    Master data will be adapted to new version during the upgrade. Unless you need fresh data, you won't need to reload master data.
    3)Z-objects movement from 4.6C to 6.0....?
    Z objects are not touched by the upgrade process. It's your responsibility to keep them running after the upgrade.
    4)Open PO's and stock upload......in ECC 6.0 ?
    Same as question 2). Business data remains in the system after the upgrade.
    5) what are the precautions to be taken before Go-live?
    It is recommended to carry out functional tests, as well as connection tests with external interfaces. In any case, you shouldn't take any special precaution, at least not so different from those you would take in a normal installation.
    Regards
    Francisco

  • Upgrade from 4.7 to ECC 6.0 - screen changes

    Does anyone have a document detailing the  HCM screen changes from 4.7 to ECC 6.0

    As mentioned, there are not many changes in screens - I guess you'll just have to wait and see.
    But this was never a problem during upgrade.
    Be ware of note 783499 and it's implications.
    You will have problems with IT0009 until this note was handled.
    One more thing.  Some of the infotypes no longer accept maintenance of text.  You need to turn this off in T582A, otherwise it looks like you can save text, but nothing is saved.  Whenever you hit T582A you will get an error message if the text maintenance is ticket off and not allowed.  But it is not turned off automatically during upgrade, so you have to check the infotypes.  I seem to remember IT0002, 0006,0021 are some of the infotypes no longer accepting text maintenance.
    Hope this helps
    Kirsten

  • HR Upgrade from 4.6c to ECC 6.0

    Hi,
       I am currently about to start a HR Upgrade project from 4.6c to ECC 6.0. Does anyone have  the checklist of activities to be followed during upgrade process or any plan for upgrade process in detail. Anyone involved in upgrades pls do send across.
    Regards
    Jyothi

    Hi,
    We have recently upgraded from 4.6C to ECC 5.0. Checklist would be like...during upgrade you need to clear SPAU, there you may get cought in Schema, Rule, Functions,,you need to check there. Also check all User exits & BADI's.
    After upgrade you need to check all user defined variants properly since some screen might have changed during upgrade. Also check WT characteristics, since some standard WT charactersistics have been changed.
    Apart from this, there was no major issue in our upgrade. It went on smooth.
    Hope this helps.
    Thanks,
    Sarika.

  • Upgrade From 4.6B TO ECC 5.0

    Hi,
    I am involved in a upgrade project from 4.6B to ECC 5.0 as a Technical Consultant. Kindly let me know if you any document
    you can send it to:  [email protected]
    thanks,
    -suresh

    e.c.c 6.0 to follow the unicode rules.
    ABAP Development under Unicode
    Prior to Unicode the length of a character was exactly one byte, allowing implicit typecasts or memory-layout oriented programming. With Unicode this situation has changed: One character is no longer one byte, so that additional specifications have to be added to define the unit of measure for implicit or explicit references to (the length of) characters.
    Character-like data in ABAP are always represented with the UTF-16 - standard (also used in Java or other development tools like Microsoft's Visual Basic); but this format is not related to the encoding of the underlying database. 
    A Unicode-enabled ABAP program (UP) is a program in which all Unicode checks are effective. Such a program returns the same results in a non-Unicode system (NUS) as in a Unicode system (US). In order to perform the relevant syntax checks, you must activate the Unicode flag in the screens of the program and class attributes.
    In a US, you can only execute programs for which the Unicode flag is set. In future, the Unicode flag must be set for all SAP programs to enable them to run on a US. If the Unicode flag is set for a program, the syntax is checked and the program executed according to the rules described in this document, regardless of whether the system is a US or a NUS. From now on, the Unicode flag must be set for all new programs and classes that are created.
    If the Unicode flag is not set, a program can only be executed in an NUS. The syntactical and semantic changes described below do not apply to such programs. However, you can use all language extensions that have been introduced in the process of the conversion to Unicode.
    As a result of the modifications and restrictions associated with the Unicode flag, programs are executed in both Unicode and non-Unicode systems with the same semantics to a large degree. In rare cases, however, differences may occur. Programs that are designed to run on both systems therefore need to be tested on both platforms.
    Other Changes 
    1.     Bit Statements
    2.     Adding Field Sequences
    3.     Loops with VARY and VARYING
    4.     Creating Subroutines
    5.     Saving Programs
    6.     Assigning Types for GET/SET PARAMETER
    7.     Unreachable Statements
    8.     Function Modules with Incorrect Parameter Names
    1. Bit Statements
    Previously, the system checked for the bit statements SET BIT i OF f [TO g] and GET BIT i OF f [INTO g]whether the field f is character-type; X fields, X strings, and flat structures are usually regarded as character-type. For Unicode programs this is no longer useful, because the types X and XSTRING no longer count as character-type and the bit by bit access to character-type fields or structures is no longer platform-independent. Therefore, with these operations in Unicode programs, the field f must be type X or XSTRING.
    For the bit mask operations f O x, f Z x, and f M x you could previously use all number-type and hence all character-type types for the left operand f. In Unicode programs, the f operand must now be type X or XSTRING.
    2. Adding Field Sequences
    When adding field sequences, restrictions apply to the following statements in Unicode:
    ADD n1 THEN n2 UNTIL nz [ ACCORDING TO sel ] GIVING m ...
    ADD n1 THEN n2 UNTIL nz TO m [ RANGE str ].
    1.     The operands n1, n2, and nz must be type-compatible with one another.
    2.     The distance between nz and n1 must be an integral multiple of the distance between n2 and n1.
    3.     A syntax or runtime error occurs if the fields n1, n2, and nz are not in a structure. This structure must be recognizable statically or its valid area must be marked explicitly using the RANGE addition.
    4.     At runtime, the system ensures that the RANGE area is not left.
    ADD n1 FROM i1 GIVING m [ RANGE str ].
    1.     Field n1 must be within the structure. The structure must be explicitly defined using the RANGE addition if it is not recognizable statically.
    2.     For this variant, the system also checks at runtime whether n1 and the addressed values are within the structure.
    3. Loops
    Loops with the VARY or VARYING addition are also problematic in Unicode, since a type-a access to memory contents cannot be ensured and memory can be overwritten inadvertently.
    DO ... VARYING f FROM f1 NEXT f2.
    For this statement, the fields f, f1, and f2 must be type-compatible with each other. To prevent memory contents being overwritten, a RANGE for valid accesses is introduced implicitly or explicitly for the following statements:
    DO ... TIMES VARYING f FROM f1 NEXT f2 [ RANGE f3 ].
    WHILE ... VARY f FROM f1 NEXT f2       [ RANGE f3 ].
    A syntax or runtime error is caused if f1 or f2 are not included in f3. If the RANGE addition is missing, it is defined implicitly from FROM f1 NEXT f2 as follows:
    1.     If both f1 and f2 are statically recognizable components of the same structure, the valid RANGE area is defined from the smallest structure that comprises f1 and f2.
    2.     A syntax error is triggered if it is recognizable statically that f1 and f2 are not part of the same structure.
    3.     A valid area must be defined explicitly using the RANGE addition if the connection between f1 and f2 is not recognizable statically.
    If you specify a deep structure as the RANGE addition, the system checks for every loop pass that there are no field references, object references, tables, or strings in the area read.
    4. Creating Subroutines
    When automatically generating subroutines using the statement GENERATE SUBROUTINE POOL itab NAME name, the generated program inherits the content of the Unicode flag of the generating program.
    5. Saving Programs
    When automatically generating programs using the statement INSERT REPORT prog FROM itab, default values are set for the TRDIR entry as before. Amongst other things, this statement has the new addition UNICODE ENABLING uc, with which the Unicode flag of the inserted report receives the value of uc. If this addition is missing, the following applies:
    1.     A Unicode program creates a Unicode program.
    2.     A non-Unicode program in turn creates a non-Unicode program.
    3.     A non-Unicode program becomes a Unicode program if it is overwritten by a Unicode program.
    4.     A Unicode program remains a Unicode program if it is overwritten by a non-Unicode program.
    6. Assigning Types for GET/SET PARAMETER
    For the statements GET PARAMETER ID pid FIELD f and GET PARAMETER ID pid FIELD f, f must be character-type. You can use the EXPORT and IMPORT statements for storing non-character-type fields and structures.
    7. Unreachable Statements
    In Unicode programs, unreachable statements cause a syntax error. In non-Unicode programs, there was previously only a syntax warning.
    8. Function Modules with Incorrect Parameter Names
    In Unicode programs, calling a function module, whose parameter names are specified statically as a literal or constant, causes an exception that can be handled if an incorrect parameter name was specified. This only applies to function modules that are not called via Remote Function Call. In non-Unicode programs, an incorrect name was previously ignored.

  • Runtime Error in VL01N after upgrade from 4.6c to ECC 6.0

    hi, 
       We are doing a upgrade project from 4.6c to ECC 6.0 and when we are running the VL01n tcode and as soon as we hit enter in easy access screen its throwing a runtime error as " The key of internal table "XLIPS" contains components of type  'X' or "XSTRING". The "READ TABLE XLIPS" statement is not permitted for such tables in a unicode context'. The xlips is declared as:
    DATA: BEGIN OF XLIPS OCCURS 15.
    INCLUDE STRUCTURE LIPSVB.
    DATA: END OF XLIPS.
    so i have checked the lipsvb structure in that i dont find the key fields of type X or XSTRING all are of type CHAR 4. this LIPSVB is the Reference structure for  XLIPS and YLIPS.
    THANKS IN ADVANCE.

    Please  see the  Patch level of the  SD, FI ,etc...
    and  apply  it   the basis   should   find  it  out  .... for  ECC6.0   then  minimum level  of  patches  should  be   upgraded.
    please  ,login to help.sap.com  ... there  in the  search  see the  document   of the pateches  for the   ECC6.0 for SD & FI ... like wise  for  all  Modules  ....
    Reward  points if it is usefulll ...
    Girish

  • Runtime Error in MIGO after upgrade from 4.6c to ECC 6.0

    hi,
        We are doing a upgrade project from 4.6c to ECC 6.0 and when we are posting the MIGO a runtime error is occuring from the method
    "IF_EX_MB_DOCUMENT_BADI~MB_DOCUMENT_BEFORE_UPDATE" which is
    in the class "ZCL_IM_MMIM_STK_TRANSFER".
    The error is as follows :
    method IF_EX_MB_DOCUMENT_BADI~MB_DOCUMENT_BEFORE_UPDATE
    >>>>>CALL FUNCTION 'Z_MM_STK_TSFR'  
    TABLES     
    T_XMKPF = XMKPF
    T_XMSEG = XMSEG.  
    END METHOD.
    the errror is showing at function  'Z_MM_STK_TSFR'   .
    I would be happy if anyone could give any inputs i hav also put chek in unicode in attributes in main program however still the error is arising.
    thanks in advance

    hi,
         thanks for the inputs i have done the syntax check on the main program and the FM the error which is coming is Field "ENJPREVIEW" is unknown. its neither in one of the specified tables nor defined by a DATA 'statement' . THis error is showing in the include LMEDRUCKF1K.
    Thanks in advance

  • Upgradation from 4.6C to ECC  6.0

    Dear All,
    I have worked on a upgrade project from 4.6C to ECC 6.0.
    I am in the process of maintaining documents for the project. I am just planning to maintain a repository for all the relevant documents.
    I feel that it will act as a useful document for all the consultants involved in upgradation.
    Right now I am engaged in documenting the issues involved with upgradation- Technical and Functional.
    I will collate all the docs and send a copy to all the major contributors. Your contribution is solicited
    Regards,
    Rakesh

    Dear Rakesh,
    Hi, I am Albert from Philippines, and is involved in the 4.6C to ECC6 upgrade as of this writing.
    I am new to SAP--my first two posts here might sound silly to most SAP gurus
    I would appreciate if you could send your documents on the upgrade. Those will really help me.
    Thank you very much in advance.
    Regards,
    Albert
    Edited by: Albert Joseph Canceran on Feb 8, 2008 12:24 PM
    Edited by: Albert Joseph Canceran on Feb 8, 2008 12:25 PM
    Pls email them to me at [email protected]

  • 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]"

  • IDES upgrade from 4.7 to ECC 6.0

    Hi,
    I have windows 32 bit system there I would like to perform an upgrade simulation from 4.7 to ECC 6.0.
    Can I perform IDES R3 4.7 to ECC Non-Ides upgrade or I have to Upgrade to IDES ecc 6.0?
    In case of IDES ECC 6.0 I can not see any Upgrade Export CDs whereas for the Non-Ides version I can see the upgrade export.
    Please give your valuable comment , I am a little bit confused.
    Regards,
    Souren Sharma

    Hi,
    You cannot upgrade your IDES version. You have to install new IDES system as ECC 6.0.
    For more information check SAP Note 164244 - IDES upgrade
    Find below the extract from this note:
    If required, you can carry out a standard upgrade of your IDES installation to a higher release level. However, this is not an IDES upgrade but 'merely' a repository upgrade (ABAP, Dictionary, GUI...). The sample data of IDES client 800 remains unchanged. We cannot guarantee that your IDES scenarios work after the upgrade to the new release level. Therefore, we recommend that you order the required release as a new installation.
    Thanks
    Sunny

  • ERP Upgrade: Changes in Reporting in new version ECC6.0

    Hi Gurus,
    We are just in upgrade process from 4.7c to ECC 6.0. During the test we ascertained that there are certain changes happened in the reporting functions und the reports are not showing some necessary fields in new version. For instance the reports RFDOPO00 and RFKOPO00 are replaced by RFDEPL00 and RFKEPL00 in ECC 6.0, which do not show some important fields of old report. SAP says they are standard reports in ECC 5.0 /6.0.
    How can we maintain old reports (in general, not specifically these above mentioned reports) from 4.7c in our new upgraded system ahead instead of new reporting standard of ECC6.0.
    Please tell me the steps to solve this problem.
    Regards
    SIM

    No, there is slightly difference in reporting between both versions ERP 4.7C and ECC 6.0. For instance in old version 4.7c we can produce reports (RFDOPO00 and RFKOPO00) with Subtotal and Total by currency by making check mark on both these items. In new version this items has been removed. There are also some more items which are not offered by SAP in new version.
    As we have decided to keep some old reports in new system, Can you therefore please tell me how we can keep the old reports in new version?

  • Delta changes from 4.6 to ECC6.0

    Hi Experts,
    Please help me to get delta changes from 4.6 to ECC. It will be great if you provide me indeapth info regarding this.
    Thanks in advance,
    Venkat

    Dear Venkat,
    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/
    After opening the site, please select the Source Release Version which is 4.6 b Then Select the Target Release Version which is "mySAP ERP 2005" or ECC 6.0
    Select the Solution Area like Financials, Human Capital Management, Sales....
    Select module like MM, PP, SD, QM.....
    Click on Search
    Then it displays the Release Version and the Delta Functionality. which can be downloaded to a word document if required.
    and also check the release notes of ECC 6.0 in service.sap.com.
    Hope this helps you.
    Do award points if you found them useful.
    Regards,
    Rakesh

Maybe you are looking for