Managing N+1 Landscape for Upgrade Project

Hello - I'm currently involved in a project that is rolling out a n+1 landscape.  The landscape will look like this:
MNT (maintenance): DEV --> QAS --> PRD
PRJ (project): DEV --> QAS
The project landscape is going to be upgraded to newer enhancement packs and Netweaver versions.  As an example, the maintenance landscape might be on Netweaver 7.30 and the project landscape on 7.40 (not real, just an example).  In a situation like this, how are ABAP code and config changes managed or retrofitted across the two landscapes?
I've been investigating Solution Manager Retrofit as a possible tool to help, but I don't think it will work in this scenario.  Can anyone help provide some high level guidance?

Hi Ethan,
I've been investigating Solution Manager Retrofit as a possible tool to help, but I don't think it will work in this scenario.  Can anyone help provide some high level guidance?
You can manually track the changes which are being imported into Production system of Maintenance Landscape. Perform manual imports into Project landscape development system.
Perform upgrade impact analysis + unit testing on Development system of Project Landscape.
Perform SIT on QAS system of Project landscape
Alternate solution.
If you have CHARM implemented into your landscape , you can use critical object identification using solman. This will automatically highlight which objects needs attention.
Refer blogs http://scn.sap.com/people/dolores.correa/blog/2009/08/27/change-request-management-scenario-retrofit-functionality
Hope this helps.
Regards,
Deepak Kori

Similar Messages

  • Question about Managing SAP ERP 6.0 Upgrade Projects

    Hi experts,
      Some questions in this link(google: Managing SAP ERP 6.0 Upgrade Projects and download PDF)
    http://www.google.com.tw/url?sa=t&rct=j&q=Managing_SAP_ERP_60_Upgrades_SAP_PRESS_sample&source=web&cd=4&ved=0CDgQFjAD&url=http%3A%2F%2Fmedia.techtarget.com%2FsearchSAP%2Fdownloads%2FManaging_SAP_ERP_60_Upgrades_SAP_PRESS_sample.pdf&ei=vTsVT7PKI4T6mAXL0czcAw&usg=AFQjCNFq83vYG3k14xC5tcoYy96PfllYFw
    1. Is figure 5.3 in page 165 correct?
    I think it should be
    Temporary system: DEV 6.0
    Productive system: DEV' 4.6C -> QAS 4.6C -> PRD 4.6C
    2. Is this transport route possible?
    "During this phase, you continue dual maintenance of the development
    systems. You also transfer changes that you make in DEV' to DEV, and
    transport changes to both quality assurance systems."
    DEV' 4.6C -> DEV 6.0 -> QAS 6.0 -> QAS' 4.6C
    If we modified some standard programs and transport between two different SAP versions, I think the programs can't work, right?

    > 1. Is figure 5.3 in page 165 correct?
    > I think it should be
    > Temporary system: DEV 6.0
    > Productive system: DEV' 4.6C -> QAS 4.6C -> PRD 4.6C
    >
    > 2. Is this transport route possible?
    > "During this phase, you continue dual maintenance of the development
    > systems. You also transfer changes that you make in DEV' to DEV, and
    > transport changes to both quality assurance systems."
    > DEV' 4.6C -> DEV 6.0 -> QAS 6.0 -> QAS' 4.6C
    > If we modified some standard programs and transport between two different SAP versions, I think the programs can't work, right?
    Here, you need to do manual replication between both development system. No transport is possible because of different versions. I am not sure about the document that you posted but same is explained very well in upgrade guide. Please check there.
    Thanks
    Sunny

  • Some tools used for upgrade project

    Hi experts,
    I am looking for some tools used for upgrade project.What are the frequently used tools in an upgrade project.
    Regards,
    Kiran

    Hi,
    There is no specific tool for the upgradation. it dependts on organization. if it has developed its own tool means that is used for the upgradization. noramlly company gets the project based on the presentation of their tool.
    our company has a great tool for the upgradization. which find out all unicode related errors and changes that has to be done in new verion.
    like this each organization might havedeveloped their tools.
    Regards,
    Anki Reddy

  • Cutover Activities for Upgrade Project

    Experts
    What are the cutover support activities for the administration of the ECC 6.0 (SAP) upgrade project. Also please do let me know how to prepare cutover strategy , and how do we develp cutover plans.
    Regards,
    Mahesh

    Hi,
    Check this thread.
    CutOver activities in BI7.0 while doing  production upgrade BI7.0 FromBW3.x
    Regards.

  • BI dual landscape for upgrades

    We recently built a dual / parallel landscape for our BI system to support a support stack upgrade.   I've used the dual landscape concept for many years when doing ERP upgrades, and it has worked very well.   We thought a dual landscape for BI would work also.   However, we did not consider the automatically generated objects in BI.
    What we found is that with 2 development systems, even though BI objects are created with the same logical name, the technical (generated) name will be different between the 2 systems.
    Has anyone successfully implemented a dual-landscape for BI?   If so, how did you syncronize the technical names of objects between development systems without transporting the objects from one development system to the other?   Note: I'm of the opinion that you need to be extremely careful transporting objects between systems with different release/support pack levels and therefore avoid it at all costs . . .  Note 1090842 + several bad experiences.   Therefore, I am very unlikely to consider transporting the objects created in PSD to RLD as a valid solution.
    The following is just an attempt to better describe the issue:
    Production support landscape looks like this:
    PSD  ->  BWP   (these systems have lower release/SP levels than the systems in the release landscape)
    Release landscape looks like this:
    RLD  ->  RLQ    -
    >  Changes will eventually go to BWP after release/SP upgrade in BWP
    Lets say queryA must be developed and transported to BWP prior to the release/SP upgrade in BWP.
    In PSD queryA is created and gets assigned technical name 123456 and is transported to BWP.
    In RLD queryA also gets created, but gets assigned technical name ABCDEF.
    Sometime after the release/SP upgrade, when you are back to a single landscape (RLD -> RLQ -> BWP), a change needs to be made to queryA.   When you transport queryA to BWP, you end up with 2 queryA's, one with technical name 123456 and one with technical name ABCDEF.

    Hey.  I worked for years in a dual landscape environment and at one point, some folks were actually looking at three paths all pointing to production.  The three path idea got squashed fairly quickly, but we had two landscapes for as long as I can remember.  So we essentially had:
    PAD --> PAQ --> Prod
    PBD --> PBQ --> Prod
    This was very helpful to be able to work on major releases and upgrades while still allowing weekly maintenance releases.  I never looked for a document that deeply discussed the concept and pitfalls to watch out for. 
    I will say the system synch-up could often become quite a pain.  This may sound a little crazy but we would transport from landscape A to landscape B but dual code from B to A.  This was because A was for the triannual major releases and upgrades and B was maintenance work.  There were times when we would transport both ways, but we tried to stay away from that (except for queries). 
    The idea was that anything that went to prod as maintnenance, out of B, should be dual coded in parellel in A.  Then once a tri-annual type release went from A, all those new transports and dual coding would be moved to B.  This is how we kept everything in synhc and it worked rather well.  You always had to be careful around the time of the tri-annual go live, but that's to be expected. 
    The only objects we had constant problems with werre queries.  I don't know of anything you can do about that.  We eventually decided to always transport queries between the two landscapes.  We would never manually dual code a query.  We would eventually get the duplicate query issue in production.  The pitfall here is if the same query is getting touched for maintenance and a major release... that was just something we had to workaround.  But we never had any major problems with transporting between the two landscapes.  The times it became a huge headache is when people would forget to dual code, or just plain to a bunch of prototyping in one of these environments when they should have been using a sandbox.
    Not sure if I have answered your question, but hope this helps in some way.  At least you know plenty of us feel your pain!

  • Test scripts , for upgrade project

    hi
    i am doing upgrade project, its my first experience ,
    can someone tell me what is the test scripts for testing, how to prepare it, and what's importance of this for fico side?
    offcourse points to all.
    thanx

    hi plz refer at
    http://www.thespot4sap.com/upgrade_guide_v2.pdf
    asign points if useful
    thanks
    Srilakshmi

  • Prerequisites for Upgrade Project

    Hi Folks,
    Being im a functional consultant - I woudl like to know the activities involved in CRM Upgrade project from 4 to 7.
    I will be looking forward for the Prerequisites activites which needed to take care before starting the project.
    Thanks in Advance
    Amrita.

    Hi Amrita,
    We need to carry out a set of activites before kicking off the upgrade project from CRM 4.0 to CRM 7.0.
    We need to validate whether the current 4.0 system is an unicode or non-unicode system and then plan for the conversion of the system to unicode as SAP CRM 7.0 only supports unicode format.
    Please find below the links which would give you more information on the CRM upgrade from 4.0 to 7.0.
    Comparision of functional areas can be found in CRM Master Upgrade Guide : https://websmp109.sap-ag.de/crm-inst
    Gude for upgrade tasks can be found under : http://wiki.sdn.sap.com/wiki/display/CRM/General+Documents ( Link : SAP CRM 4.0 upgrade to 7.0 Guide for typical upgrade tasks )
    Please let me know if you are looking out for any furhter specific information.
    Best Regards,
    Vamsi.

  • MS System Center Operations Manager 2010 Download required for Upgrade from SCOM 2007 R2 (Select)

    We need the download of SCOM 2012 without Service Pack1.
    Upgrade from SCOM 2007 R2 (select license) fails while upgrade check with error: Logs shows "At least one of the following applications is installed on this computer. Due
    to incompatibility with System Center 2012 - Operations Manager, these applications must be uninstalled."
    Upgrade was started from dos elevated prompt with modified parameters like this:
    setup.exe /silent /upgrade
    /AcceptEndUserLicenseAgreement:1
    /UseLocalSystemDASAccount
    /DataReaderUser:<domain\user>
    /DataReaderPassword:<password>
    Research in internet and we found another person with same issue, which reports that direct upgrade from SCOM 2007 R2 to SCOM 2012 SP1 is not possible but if upgrade is done over
    SCOM 2012 to SCOM 2012 SP1 it succeeds.
    Unfortunately, we don't find any downloads for the first release of System Center 2012  e.g. Operations Manager.
    Everything shows Service Pack 1 or the newer R2.
    Who can help?

    Our “Recommended” rolling upgrade path looks like the following:
    SCOM 2007R2 CU4+ > SCOM 2012 RTM UR2+ >
    SCOM 2012 SP1 UR4+ > SCOM 2012 R2
    Also you can refer below link
    http://blogs.technet.com/b/kevinholman/archive/2014/01/20/do-i-need-a-specific-cumulative-update-release-ur-in-order-to-upgrade-to-scom-2012-or-2012-sp1-or-2012-r2.aspx
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
    Mai Ali | My blog: Technical

  • Include Missing for Upgrade Project?

    We have an include that was never transported vie upgrade to 6.0 processes. Because it was a local transport. And, it gets  generated by the main code. It says not to transport. How can I
    regenerate the include?
    Thanks.

    Hi Gert, Thanks for asking.
    Main Prog was GBS00SET. I resolved the issue:
    Iu2019ve noted the resolution. OSS Note 79156:
    Independent of the release you have to regenerate the coding for validation/substitution. To do this, execute program RGUGBR00. Please select all options, except 'Gen. substn routns in all clnts' and .'Trace prog. generate calls'.
    Thank-You.

  • 4.6 C to ECC 6.0 Upgrade Project Timeline Sheet in MPP format

    Dear all,
    We are now proposing our customer for the 4.6c to ECC 6.0 Upgrade.
    Our customer is currently in 4.6c/oracle 9i/HPUX 11 i. He wants to move to ECC 6.0.
    If you have the project timeline for the above Technical Upgrade, can you pl send it to me.
    If you don't have in MPP format atleast send me the Work Breakdown structure with timelines.
    I shall modity the same to our customer and submit
    Thanks & Regards
    Senthil
    [email protected]

    Preparation Phase* 6 days
    Kick Off Meeting 1 day
    Upgrade Project Procedures Preparation 1 day
    Prepare Upgrade Project Plan 1 day
    Technical Requirements Assessment 3 days
    Assess Training needs of Key-users & End-users 1 day
    Prepare Detailed Basis Activity List for DEV, QA & PRD 1 day
    Business Blueprint Phase 6 days
    Develop System Landscape Upgrade Plan 1 day
    Functional Requirement Checklist 1 day
    ABAP Development check list 1 day
    Develop detailed Training Procedures & Documentation for Key Users & End Users 1 day
    Identify Testing Scope & Scenarios 1 day
    Identify Authorizations Conversion to Roles for SAP ECC 6.0 2 days
    Develop Documents as per Basis Activity List 1 day
    Develop Authorization Matrix for Activity Groups to Roles Conversion 2 days
    Prepare Upgrade Deliverables Checklist 1 day
    Realization Phase 28 days
    Installation of Solution Manager 3.2 System 1 day
    Creation of New Development System for Upgrade Project (Homogenous System Copy - PRD) 2 days
    Upgrade to AIX & Oracle 10g, SAP ECC 6.0 on New Development Server 3 days
    Upgrade Frontend Software 4 days
    Perform SPAU & SPDD Corrections 5 days
    Perform ABAP Development & Corrections 10 days Perform Authorizations Conversions and corrections after upgrade 8 days
    Perform Upgrade Testing for each Application Module 7 days
    Perform Unit & Integration Testing 6 days
    Perform Training to Key Users & End Users (Generic & Specific) 3 days
    Upgrade to AIX, Oracle 10g, SAP ECC 6.0 on Quality System 1 day
    Homogenous System Copy of PRD to New Quality & Upgrade to AIX, Oracle 10g & SAP ECC 6.0 2 days Perform Testing in Quality System 3 days
    Testing by end users on Quality System 1 day
    Production Realization & Go-Live Phase 6 days
    Upgrade to Production System Operating System to AIX (after close of business hours - 23:00) 1 day
    Oracle Upgrade to 10g (after close of business hours - 23:00) 1 day
    SAP Release Upgrade to ECC 6.0(Downtime Minimized - Downtime occurs in non-business hours) 2 days
    User Acceptance Testing 1 day
    Production System Go-Live 1 day
    Post Go-Live Support 14 days
    Post Go-Live Support 14 days Note: This is high level plan subject to change during Business Blue Print Phase 0 days
    This is taken from a post in Ittoolbox, May be this is generic. Hope you can tailor this to meet your requirements.

  • Upgrade projects and Compare and ajust func.???

    Hi All.
    I am trying setting up a demo of the benefits using SolMan for upgrade projects with Compare and Adjust functionality.
    I am following a guide with the following steps:
    1. Create an Implementation project with some processes from BPR (Using SAP R/3 Enterprise 4.7 as logical component).
    2. Model (change) the processes to simulate that a not fully SAP std. process is used at this compagny.
    3. Copy the implementation project to an Upgrade Project (with option "Adjust target project to original of the source project".
    4. Adding logical component SAP R/3 ECC 6.0 to the system landscape.
    5. Executing transaction SA_PROJECT_UPGRADE for the Upgrade project.
    Now, when I go to the project, I see no marking of changes anywhere...
    Could this be because I am using the wrong processes in my Implementation project from BPR?
    Does anyone have a good example of processes that can be good to demo this?
    Thanks in advance!
    /Per

    Hi All.
    I am trying setting up a demo of the benefits using SolMan for upgrade projects with Compare and Adjust functionality.
    I am following a guide with the following steps:
    1. Create an Implementation project with some processes from BPR (Using SAP R/3 Enterprise 4.7 as logical component).
    2. Model (change) the processes to simulate that a not fully SAP std. process is used at this compagny.
    3. Copy the implementation project to an Upgrade Project (with option "Adjust target project to original of the source project".
    4. Adding logical component SAP R/3 ECC 6.0 to the system landscape.
    5. Executing transaction SA_PROJECT_UPGRADE for the Upgrade project.
    Now, when I go to the project, I see no marking of changes anywhere...
    Could this be because I am using the wrong processes in my Implementation project from BPR?
    Does anyone have a good example of processes that can be good to demo this?
    Thanks in advance!
    /Per

  • How To Use SPDD and SPAU Transaction in An Upgrade Project

    Hi Friends,
    I will be working in an upgrade project very soon. this is my first experience for Upgrade project. Though I know these two transaction are used for Upgrade.
    Can anyone give me a step by step document for using these two transactions and other relevant information.
    Also, I have one query where do we use these transactions : On the old system e.g. R/3 4.7 or ECC 6.0
    Thanks,
    Pradeep
    <REMOVED BY MODERATOR - REQUEST OR OFFER POINTS ARE FORBIDDEN>
    Edited by: Alvaro Tejada Galindo on Dec 23, 2008 10:39 AM

    Hi Pradeep,
    For SPDD see this link
    http://help.sap.com/erp2005_ehp_03/helpdata/EN/2e/6d66587d9011d396b60000e82de14a/frameset.htm
    For SPAU
    http://help.sap.com/erp2005_ehp_03/helpdata/EN/c8/61ec66e33611d1954b0000e82de14a/frameset.htm
    Why you need this Adjustments
    http://help.sap.com/erp2005_ehp_03/helpdata/EN/60/d6ba7bceda11d1953a0000e82de14a/frameset.htm
    You use the transactions in the new system.
    Regards

  • What is an Upgrade project mean

    <Moderator Message: Besides you say you searched, I cannot believe that it is true. This question has been asked already a lot of times. May be you need to adjust your search terms>
    Hello All
    I tried to search for the relevant procedure or doc,,but I couldnt able to find the correct one,hence am posting this question.
    What is an Upgrade project mean?
    As we are going to upgrade from 3.5 to 7 version,,But I dont know anyhting of this upgrade and how to do also.Is there any fixed process for doing this.
    Can anyone tell me what are the procedures involved in the Upgrade and what type of work will they expect from us technically as a BW consultant.
    Thanks
    Shankar
    Edited by: Siegfried Szameitat on Feb 19, 2009 10:42 AM

    Hi,
    Search for 'Upgrade Project' or 'Roles of Consultant during upgrade'.
    check this out:
    Activities:
    https://forums.sdn.sap.com/click.jspa?searchID=22518474&messageID=6953087
    https://forums.sdn.sap.com/click.jspa?searchID=22518474&messageID=6729155 this one could be lucky that I wasn't in there because the links provided are not allowed.
    Roles:
    https://forums.sdn.sap.com/click.jspa?searchID=22518710&messageID=6622978
    Siggi

  • Forms 4.5 to 10g upgrade project

    Hello All,
    My client asked me to upgrade its Oracle Forms 4.5 to the latest Oracle Forms 10g. in my 4 years as a Oracle forms developer I never taken any project that will lead to upgrade. I surf the Forms upgrade center but confused about steps to be taken for upgrade.
    My questions are:
    1. When upgrading from 4.5 to 10g is WebUtil is the required tool or are there any other tools out there for upgrade projects?
    2. Why to upgrade 4.5 to 6i(web) first instead of upgrading directly to 10g?
    3. How long it will take for upgrade? Currently the client has 45 forms.
    I appreciated for your reply
    Thanks!
    Rashid

    1. It depends on your current forms if you need webutil or not. If you have client actions in your forms, like HOST or OLE, you need to convert those to webutil.
    2. You can upgrade to 10g if you do it manually (i.e. open the fmb in Forms Builder and do the appropriate actions). The step to 6i first is only needed if you use the migration assistant I believe.
    3. Do a test with one form and see how long it takes and then make an estimate for the total project.
    I did a manual upgrade and started with one form per day, speeding up to 2-3 forms when the returning issues were resolved. There is a thread a few days ago about changing colours, for instance. That was something that took us a while too to figure out, but easily done in the migration once we knew what to do.

  • Some problems about Upgrad project

    Dear,
        I have some question for Upgrade project.shi
    P1: in form ZSD_EXPORT_FECO, check texts, Windows F005 has an error :
         /: AND &V55EFECO-REMA_TEXT2& = ' '
                   Unknown command
           I don’t know how to correct it.
    P2: in program ZFUMSV00, the source code is   sy-repid    = 'RFUMSV00'.
         In 700 version, it checks error: the field “sy-repid” can’t be changed.
         But, in 46c version, it is OK.
            I don’t know how to correct it.

    Hi
    check this doc
    While doing Upgrade You have to aware of all related program like BDC's , Screens related errors and all dictionary related problems.
    Some function modules may become obsolete, and some screens will change
    and some new fields will be added in the new versions etc.
    Also take care of SPAU and SPDD tcodes.
    You should be able to know about Unicode concept in sap.
    check this
    http://www.thespot4sap.com/upgrade_guide_v2.pdf#search=%22upGRADE%20STEPS%20-%20SAP%22
    also chk these 2 notes in service.sap.com
    Technical Upgrade is only a version upgrade without any functionality changes.
    The objects that are needed to be upgraded are:
    Includes
    Function Groups / Function Modules
    Programs / Reports
    OSS Notes
    SAP Repository Objects
    SAP Data Dictionary Objects
    Domains, Data Elements
    Tables, Structures and Views
    Module Pools, Sub Routine pools
    BDC Programs
    Print Programs
    SAP Scripts, Screens
    User Exits
    You can refer to the below links for more information on technical upgrade:
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/07/upgradeFROMR3TOmySAPERP-PARTII&
    https://wiki.sdn.sap.com/wiki/display/profile/UPGRADEFROMR3TOmySAPERP-PARTIII
    http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/2e/6d66647d9011d396b60000e82de14a/content.htm
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5ac31178-0701-0010-469a-b4d7fa2721ca
    Regards
    Anji

Maybe you are looking for