Upgradation project in sap xi

hi expects ,
     i want to know about what would the problem or process in upgradation project.please help me.
                                                                                thank u

Hi,
As an XI Developer one has the following responsibilities
SLD developement is depends upon the Organization.
1)  Developing Interface Objects
2) Developing maping objects
3) Developing Config objects like Creation of Communication channels , Sender and Receiver agreemnets, Interface data and    Receiver  data.
In Addition to this he has to check whether the files are correctly picking and the files are correctly placing in the Target.
Any Mapping related error means he has to look into those
what are the responsibilities of an XI Developer?
A) Steps are as follows.
1) Receives functional specs.
2) Understand the business requirements.
3) Check whether are the required information is provided in Functional specs or not information like, source sturucutre,target strucutre,Transformation rule, test files, validation rules, error handling, data size etc.
4) Raise issue log if there are issues and resolve it with functional team.
5) Start building or designing the tech specs with all the required details like IR and ID part.
6) Develop the object as per the design.
7) Follow the naming convention as per the doc.
8) Test the developed object with test cases and prepare UTC.
9) Then review will happen with other team members.
Regards
Mohammed

Similar Messages

  • Upgrade project : from SAP R/3 4.6C to ECC 6.0 by using SAP Data Services

    Hi All,
    My client is upgrading from SAP R/3 4.6C to ECC 6.0
    We are planning to use SAP Data Services(Data Integrator) in the upgrade plan from SAP R/3 4.6C to ECC 6.0 for Data Migration.
    we have no idea whether we can use this SAP Data Services(Data Integrator) in SAP upgrade data migration.
    The bottom line is we have to make use this Data Services (Data Integrator) product in our upgrade plan for Data Migration.
    Please tell us if anybody already used it such kind of scenario in a data migration project with Data Services(Data Integrator).
    If we can use Data Service(Data Integrator) what are the pros and cons in using this Data Services(Data Integrator).
    Thank You,
    Ashok

    My opinion is you would want to utilize SAP tools to port the data - our SAP BASIS administrator is out this week but we can provide exact tool names when he returns.  ELM (External List Management), IDOC are some of the tools.
    You could use DS/DI to export, cleanse, deduplicate the records prior to importing with SAP tools if that is your end goal.
    We also offer a data quality tool that extends DS/DI to cleanse/deduplicate name/address records as they are entered into the system.  It also comes with batch tools to cleanse/dedup the entire systems name/address information.  See Data Quality Management for SAP for further details.

  • Portal Upgrade Project Duration

    I am in the middle of providing an estimate for the portal upgrade project.
    My portal landscape has 3 environments: Dev, QA and Prod and KM/Trex is used but we are not using Collaboration/Unification.
    I know this question is not easy to answer, because it depends on so many factors, but usually there are statistics around average duration of R/3 upgrade based on sampling of upgrade projects that SAP keeps.
    So is SAP maintaining such statistics and are they available?
    If they are not available, based on your upgrade experiences, what is the high level estimate of an average duration of a portal upgrade project going from EP5.0 SP5 Win/SQL to NW04 Unix/Oracle?
    Thanks in advance for any insights you might share with me.

    It depends on your landscape configuration especially if it comes to migrating KMC. Basically, you would go through three stages: KMC migration tool, EP migration tool, manual post migration steps.
    The first step depends on the amount of content in KMC and on the bandwidth of the data path from the source to the target db (disk and network i/o). I've seen fast infrastructures moving more than 20gb per hour and slow test system with source and target db on the same machine with a slow disk running at less then 500mb per hour.
    The second step, the EP migration tool usually completes in less than 4 hours, sometime much faster.
    Going through the manual post migration steps depends on various things, mostly on familiarity with the system's administration; usually it takes less than a day.
    What I would suggest is a 'test' migration with data from your production system, for example a copy restored from the latest backup. On less powerfull test system hardware that gives a good upper boundary for running the tools without causing any productive downtime.
    Two additional remarks:
    1) you might want to consider migrating to SP14 directly; there will be no further fixes for SR1. And upgrading from
    SR1 to SP13 or SP14 after the migration adds to the production downtime.
    2) make sure that the source system is at the minimum required patch level; detailed info on this is to be found in the migration guides.

  • Upgrade Project.

    Hi everyone ,
    I wanted to have some advice : we have an upgrade project (for SAP HR)coming up in office , it would be from 4.6 to 6 version i guess.
    Presently i am on a support project.
    What is the difference between the upgrade project , support project and implementation project.
    Is it adviceable to work on upgrade other than support.
    Thanks,
    Rohit

    Am implementation is introducing SAP where some other system has been working till now. Implementation requires deep knowledge of the business processes because you have to understand the existing processes of the customer and try to map them to SAP. It is tough because you have to deliver from end to end, right from understanding client requirement, interpreting it, being involved in change management, educating the client, data loading and so on. Thats the reason E2E implementation carries so much weightage in a CV.
    Support starts where implementation ends. You basically have to take care of the problems in an existing system and make some minor changes/improvements in the system. Its not a high pressure job but you never can foresee what you will be facing. Problems can come from anywhere.
    Upgrade is technical upgradation. I think it has been covered very well in the thread.
    Value-wise, Imlementation is considered to be the best while it is true that the best rerources are invariably found in support. Upgrades are rare, comparitively market for the support projects is the best as implementation is done once, upgrade once in a while but support is for lifetime!
    Regards
    Lincoln

  • SAP MM Functional Consultant's role in a Upgrade Project from 4.6C to 6.0

    Hi Guys,
    I will be thrown into a SAP Upgrade Project. I would appreciate if someone could shed some light on what a SAP MM Functional Consultants role would be in this kind of Project.
    I would appreciate a comprehensive guide where it includes role within each stage of the ASAP methodology for Upgrades.
    Thanks guys.

    > I will be thrown into a SAP Upgrade Project. I would appreciate if someone could shed some light on what a SAP MM Functional Consultants role would be in this kind of Project.
    - defining the core processes
    - test and customize them
    - release the customizing transports for production
    > I would appreciate a comprehensive guide where it includes role within each stage of the ASAP methodology for Upgrades.
    Since each project is different and each system has a different customizing/configuration it's not possible to generate a step-by-step guide what you have to do. The requirements are usually defined by the business.
    Your project leader should be able to give you a project plan (e. g. by using Solution Manager Upgrade Project) where you can get an idea based on the system you're going to upgrade.
    Markus

  • Going live check for SAP upgrade projects

    Hello,
    I am interested in "going live check" service and procedures for my upgrade projects. May I find any documentation? Do I have to pay for it?..
    Thanking you in advance and a happy new years!
    Kind regards
    Nilüfer Çalışkan

    Hi Nilufer,
    The following Input as follows :
    Source : http://www.thespot4sap.com/upgrade_guide_v2.pdf
    This service is included as part of your annual maintenance fee.
    The underlying concept of the SAP GoingLive Functional Upgrade Check is
    to ensure smooth operation of your mySAP.com solution by taking action
    proactively, before severe technical problems occur.
    The GoingLive Functional Upgrade Check is made up of three sessions
    (Planning, Analysis and Verification)—two sessions (Planning and Analysis)
    before the upgrade and the other (Verification) after the upgrade.
    Planning Session: This session should be performed as much in advance as
    possible when the upgrade is first being considered.
    Analyses compatibility for the target release with regards to connected
    systems in the Solution Landscape, OS version, DB version, installed Add-
    Ons, Plug-ins, Country Versions, and so on.
    Analysis Session: It is generally performed two months before the
    production upgrade (consider lead time for hardware procurement).
      The focus is on resource planning and system configuration.
      There is a high-level hardware plausibility check (this is not a hardware
    sizing exercise).
      Potential resource bottlenecks are identified.
      Necessary changes will be recommended to prepare the system for the
    productive use of the new release.
    38 SAP Upgrade Guide | Simplifying Your Upgrade
    Verification Session: Generally performed four to six weeks after the
    production upgrade, and the recommendation from the analysis session
    implemented.
      Comparison of performance with results prior to upgrade
      Recommendations on configuration and optimization
    More information and ordering . For more information, see the GoingLive
    Functional Upgrade Check web page at:
    <b>http://service.sap.com/goinglive-fu</b>
    To order a GoingLive Functional Upgrade Check, contact SAP Customer Care
    Center at least eight weeks prior to the planned upgrade of your production
    system.
    For customers of value-added resellers (VARs) such as CBS customers in the
    US, special conditions apply. Contact your VAR.
    Remote Upgrade Service
    Remote Upgrade Service is a technical upgrade that is performed by SAP
    remote consultants. Pricing is based on the complexity of the customer’s
    environment.
    SAP performs the technical upgrade of your system, allowing you to focus on
    the functional and training side of the upgrade. You are still responsible for
    resolving object conflicts.
    See SAP Notes 106447 and 84044.
    The Remote Upgrade Service is an attractive option for CBS sized customers
    with small or non-existent mySAP Technology group.
    For more information see the Remote Upgrade Service web page at:
    http://service.sap.com/remoteupgrade
    Resources
    The following list shows some of the resources you can use as you prepare for
    your upgrade of SAP. These resources include:
      Your installation partner
      Customers and others you have networked with at customer functions and
    conferences such as:
    • ASUG
    Hope this Info helps you.
    <i>Advanced New Year wishes.</i>
    Br,
    Sri
    Award points for helpful answers

  • 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

  • SAP Upgrade project

    Hi Experts,
    I need some inputs to do SAP upgrade from 4.& to ECC 6.0.
    Generally the steps involved in the Upgrade project?
    What is the role of ABAPer in Upgrade project?
    What us the role og Functional consultant in project?
    How the configuration kind of stuff take care?
    Can anyone send me the best document to understand the process..?
    Regards,
    Sekhar.J

    Hi,
    Upgrade Overview
    The objective on SAP Technical version upgrade would be to bring in enhanced SAP functionality while retaining the custom development in the original system. The enhanced functionality is not necessarily implemented during the upgrade. The upgraded system is tested for all the functional scenarios existing in the original system and the custom objects are tested for its functioning as in the original system.
    Upgrade project consists of 5 phases:
    1.     Project Preparation
    2.     Blueprinting
    3.     Realization
    4.     Production Preparation
    5.     Go Live & Support
    ABAPer Role
    a) Syntax Correction
    b) Upgrade Correction (Replacement of obsolete statement)
    c) BDC Program correction
    d) BDC to BAPI conversion
    e) Unicode testing using UCCHECK transaction
    Functional consultant role
    Unit Testing
    Test Scripts preparations for Changes
    Regards
    Praneeth

  • 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

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

  • What do you mean by changing a Function Group in upgradation projects

    Hi ABAPers,
    I am new to upgradation project will any one help me in understanding the concepts like.
    1) what do you mean by changing a Function Group in upgradation projects
    2) what is the relation b/w the Maintenance view and function group
    3) what happens when we regenerate the table maintenance in se11
    4) how can i restore the changes that have done to FG after regenerating
    5) Suggest me is there any Tcode or procedure to see the code in Remote system (like how we compare the versions of remote system)
    Could you please help me ..
    Any relevant docs you can send it to  [email protected]
    Thanks in advance..

    Hello Smriti,
              Exploding a BOM means to display all the components and sub-components for a BOM in a particular transaction (eg) VA01,CO01,ME22N etc..
    You can use the SAP FM's depend on the Functionality:
    CS_BOM_EXPLOSION               General BOM explosion
    CS_BOM_EXPLOSION_EQUI          BOM explosion - initial screen: equipment
    CS_BOM_EXPLOSION_MAT           BOM explosion (old version); as of 3.0, use CS_BOM_EXPL_MAT_V2
    CS_BOM_EXPL_EQU_V2             BOM explosion for equipment
    CS_BOM_EXPL_KND_V1             BOM explosion for material
    CS_BOM_EXPL_MAT_V2             BOM explosion for material
    CS_BOM_EXPL_PSP_V1
    CS_BOM_EXPL_TPL_V1             BOM explosion for functional location
    CSS7                           Explode BOM (Document)
    CS_BOM_EXPL_DOC_V1             BOM explosion: document sub-assemblies
    CS_BOM_EXPL_GNRL2_V1           General BOM explosion: document sub-assemblies
    CSSO
    CS_SO_MODE_BOM_EXPLOSION
    As per Garet in response to your question better talk to the Functional team to get the better underatanding for your requirement.
    Check the below link for more details on BOM:
    http://sap-img.com/sap-sd/what-is-bom-referring-to-sap-sd.htm
    Thanks,
    Greetson

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

  • NWDI in upgrade project - Recommendations

    Dear All,
    We are upgrading ECC and Portal. Earlier client doesn't have NWDI.
    Now we are using NWDI, so the customer wants the below recommendations.
    1. Provide a recommendation for use of NWDI within the Upgrade project.
    2. Provide a recommendation for possible ongoing / expanded usage of NWDI at the project.
    Please provide your suggestions.
    Thanks.

    Hi,
    1. If you are implementing ESS/MSS you can upgrade the components using NWDI.
    In general for deploying components you either use JSPM or SDM to deploy. And NWDI uses the same method to deploy the components.
    It's upto you to use NWDI or to deploy them directly.
    Recommendation would be if implementing ESS/MSS you can use NWDI. If you are not modifying the standard SAP Delivered component then you can deploy the components directly.
    2. It depends on what all things are you planning to implement.
    Hope this helps.
    Cheers-
    Pramod

  • Upgrade Project - 4.7 to ECC 6.0

    Hello Gurus,
    I am HR Functional consultant and assigned to work on upgrade project (4.7 to ECC 6.0) for the first time. I am new to this environment. Can any one help me with suitable documents to start with. My mail id: [email protected]
    Points assured..
    Thanks in advance
    Regards
    kasi

    Dear kasi raj,
    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
    P.S. you can send me a mail at my mail id [email protected] for any specific details

  • BW Upgradation Project from BW 3.5 t o BI 7.0

    Dear SDNS,
                             We got an requirement to do an upgradation project for BW 3.5 to BI 7.0... This is the first time am involving for Upgradation..Am An BW Technical Consultant.. Can anyone one sugggest at scratch level wat are the roles should play by BW Technical consultant.. And Wat are the activities whould done by BW technical consultant.. An can anyone tell me.. How many SAP Consultants should involve in this Project.. i.e like how many Basis Consultants and how many ABAP Consultants should involve.. Who plays the Vital Role for Upgradation...
    Can anyone send me the Documents Related for BIW Upgradation for BW 3.5 to BI 7.0.. If anyone send me screen shots related to BW Tehcnical Consultant work it would be helpful.....
    My E-Mail - [email protected]
    Answering Getz Appreciated,
    Thanks & Regards,
    Aluri

    Hi
    I have some checklist ,do not exactly remember from where i got it but its really usefull
    There is no standard SAP checklist as it used to exist in 3.x for nw2004s upgrade and trust the master data guide available on market place is not upto the mark and expectations
    So Heads up..
    /message/2979584#2979584 [original link is broken]
    /message/2765713#2765713 [original link is broken]
    /message/2979576#2979576 [original link is broken]
    /message/3214476#3214476 [original link is broken]
    /message/3024448#3024448 [original link is broken]
    You may wish to have a look at draft portrayed below,rest you learn when you drive
    Lessons Learnt - Upgrade
    1)Convert Data Classes of InfoCubes. Set up a new data class as described in SAP OSS Note 46272.
    2)Pay attention to the naming convention. Execute the RSDG_DATCLS_ASSIGN report.
    3)Run the report RSUPGRCHECK to activate objects.
    4)Upgrading ABAP and JAVA in parallel may cause issues. If there is no custom development on J2EE instance, it is recommended to drop the J2EE instance and re-install the latest J2EE instance after the upgrade.
    5)Apply SAP OSS Note 917999 if you include the Support Patch 6 with the upgrade or you will get the error at PARCONV_UPG phase. When you upgrade to a product containing Basis 700, the phase PARCONV_UPG terminates. You included Basis Support Packages up to package level 6 (SAPKB70006) in the upgrade. The job RDDGENBB_n terminates with the error RAISE_EXCEPTION. In addition to this, the syslog contains the short dump TSV_TNEW_PAGE_ALLOC_FAILED. The program SDB2FORA terminates in the statement "LOOP AT stmt_tab". An endless loop occurs when the system creates the database table QCM8TATOPGA.
    6)Apply the OSS note 917999 if you get the following error during PARCONV_UPG phase: PARCONV_UPG terminates with TSV_TNEW_PAGE_ALLOG_FAILED
    Critical OSS Notes:
    819655 – Add. Info: Upgrade to SAP NW 2004s ABAP Oracle
    820062 - Oracle Database 10g: Patchsets/Patches for 10.1.0
    839574 – Oracle database 10g: Stopping the CSS services ocssd.bin
    830576 – Parameter recommendations for Oracle 10g
    868681 – Oracle Database 10g: Database Release Check
    836517 – Oracle Database 10g: Environment for SAP Upgrade
    853507 – Usage Type BI for SAP Netwaevers 2004s
    847019 - BI_CONT 7.02: Installation and Upgrade Information
    818322 – Add. Info: Upgrade to SAP NW 2004s ABAP
    813658 - Repairs for upgrades to products based on SAP NW 2004s AS
    855382 – Upgrade to SAP SEM 6.0
    852008 – Release restrictions for SAP Netweaver 2004s
    884678 - System info shows older release than the deployed one
    558197 – Upgrade hangs in PARCONV_UPG
    632429 – The upgrade strategy for the add-on BI_CONT
    632429 - The upgrade strategy for the add-on FINBASIS
    570810 - The upgrade strategy for the add-on PI_BASIS
    632429 - The upgrade strategy for the add-on SEM-BW
    069455 - The upgrade strategy for the add-on ST-A/PI
    606041 - The upgrade strategy for the add-on ST-PI
    632429 - The upgrade strategy for the add-on WP-PI
    Post upgrade Steps :-
    1. Read the Post Installation Steps documented in BW Component Upgrade Guide
    2. Apply the following SAP OSS Notes
    47019 - BI_CONT 7.02: Installation and Upgrade
    558197 - upgrade hangs in PARCONV_UPG, XPRAS_UPG, SHADOW_IMPORT_UPG2
    836517 – Oracle Database 10g: Environment for SAP Upgrade
    3. Install the J2EE instance as Add-in to ABAP for BI 7.0 and apply the Support Patch that equivalent to ABAP Support Patch.
    4. Run SGEN to recompile programs.
    5. Install the Kernel Patch.
    6. Missing Variants - (also part of test script)
    look at the RSRVARIANT table in SE16. If it is empty, then you will definitely need to run RSR_VARIANT_XPRA
    program - RSR_VARINT_XPRA
    OSS -953346 and 960206 1003481
    7. Trouble Shootauthorizations
    820183 - New authorization concept in BI
    I think the above material is sufficient but in case you face any issues feel free to revert back
    Reward suiatble points

Maybe you are looking for