Notes in SPAU

in SPAU transaction there are notes , so what i have to do in upgradation with notes & some notes have yellow light & green tick smbol & question mark symbol
how to take care of ABAP query in upgradation are the abap querys come after upgradation

SPAU - for repository Objects Changes
see the doc
Please find below, answers to your questions:
1.What objects will come in SPAU and SPDD?
Ans: All the objects which are modified, after tansporting to the current system,
will be listed in SPAU and SPDD. SPDD contains the list of all modified Data Dictionary objects, like tables, dataelements, domains,view...etc. The rest of all the modified repository objects will be listed in SPAU.
What happens to the modifications done in the older version when we upgrade the version? (with Modification assistant and w/o)
Ans: After the initial upgrade happens, we have to do adjustments from SPAU/SPDD to maintain or reset the changes. That is, from the list of objects in SPAU/SPDD, you have to either carry forward the changes to the new version, by choosing the option ADOPT CHANGES (available on right click) or RESET TO ORIGINAL (available on right click).
Will they come in these transactions?
Ans: yes, they will be listed in these transactions, after the BASIS updgrade activity.
And what if we apply some patches(Notes) to the system? What is the impact of these patches to the SPAU transaction?
Ans: Patches will be supported by the version upgrade. In case of notes, we have to verify whether these notes are supported by the new version (you can go into to verify this. Also, we have to analyze whther the code in the note is already incorporated in the new version. In this case you can ignore the chanes choosing RESET TO ORIGINAL option
If you have applied any OSS notes to objects in your system, the hot package may overwrite these objects.
SPDD is used to identify dictionary objects
SPAU (repository objects), will identify any objects where the hot package is overwriting changes you have made through OSS notes.
You must check all objects identified in SPAU and decide whether you need to reapply the OSS note or reset the code to the original SAP Code.
Also once the changes have been done you would see a green traffic light.
If you double click on the modified object it will show you a split window where on the left you will have the original version and on right the modified version. So you can choose which to keep and which to reject. You may keep the modified version incases where you know that the notes will only be pakages in the next version.
Also the following link is very good
Rewards if useful.........

Similar Messages

  • How to remove obsolete oss note from SPAU List

    Dear All,
       How to remove obsolete oss note from SPAU List. Bocz it having yellow trafic Signal and  it is not allowing me to reset to orginal or adopt.
    Please tell me how to reolve this problem.

    Please mention the Netweaver release of your system.
    Next, if you mention the note is obsolete - the traffic light should be grey.
    If its yellow, that means semi-automatic adjustment needs to be made.
    If you click on the obsolete greyed out note, you get a message saying the note correction was delivered with upgrade or support package and it could be reset.
    If you click on the yellow note, the system would try to reapply the note via SNOTE.
    Please try either or the above and let us know the system response.

  • Obsolete notes in SPAU adjustment

    Hello All,
    I am working on adjusting objects using SPAU in our system. In our system there are plenty of notes those are obsolete now, so was running SPAU on those, there is an option where you can select all the notes and then select "reset all " and then it should reset all the notes but whenever I am trying to do, it's only doing it for one note at one time. So can you please tell me if I am missing anything here.

    I solved it myself:
    We need to select each note using shift key and hitting F9 every time, this will select the notes that we want to reset. After selecting the desired notes just click on the Reset to original button and just follow from there and this will reset all the selected notes.

  • What do I do with obsolete notes in SPAU?

    Hi all,
    Am working on some hotpacks which have been installed by our basis team. There are a lot of note corrections grayed out which indicates they are obsolete. I'm unsure what to do with them. I'm confused because if I was to revert to original then my understanding is I would be reverting back to its state where it had bugs and required a fix. Do I ignore the obsolete notes instead?
    Many thanks. Answers will be rewarded.

    SPAU - for repository Objects Changes
    SPDD -for Data Dictionary object changes
    see the doc
    SPAU and SPDD Sights:
    What objects will come in SPAU and SPDD?
    Ans: All the objects which are modified, after tansporting to the current system,
    will be listed in SPAU and SPDD. SPDD contains the list of all modified Data Dictionary objects, like tables, dataelements, domains,view...etc. The rest of all the modified repository objects will be listed in SPAU.
    What happens to the modifications done in the older version when we upgrade the version? (with Modification assistant and w/o)
    Ans: After the initial upgrade happens, we have to do adjustments from SPAU/SPDD to maintain or reset the changes. That is, from the list of objects in SPAU/SPDD, you have to either carry forward the changes to the new version, by choosing the option ADOPT CHANGES (available on right click) or RESET TO ORIGINAL (available on right click).
    Will they come in these transactions?
    Ans: yes, they will be listed in these transactions, after the BASIS upgrade activity.
    And what if we apply some patches(Notes) to the system? What is the impact of these patches to the SPAU transaction?
    Ans: Patches will be supported by the version upgrade. In case of notes, we have to verify whether these notes are supported by the new version (you can go into to verify this. Also, we have to analyze whther the code in the note is already incorporated in the new version. In this case you can ignore the chanes choosing RESET TO ORIGINAL option
    Reward points if useful

  • How to reset OSS Notes with Question mark status in SPAU

    We are doing SPAU adjustments. In that under Note we have many OSS notes with status "Question Mark". We ran SAPRUPGM again. But still we have this question mark.
    We realized some of the notes are not applicable and want to reset. But when I select the note and reset, it gives a pop up to confirm the reset. I select "reset" there. But instead of reseting it gives me a popup asking to download the OSS note. If I cancel it it goes back to the initial SPAU screen. Nothing done. If I okay it it tries downloading the note.
    How to solve this situation?
    Can you also tell me if it is okay to leave the notes without resetting.
    Edited by: Ravikanth Tunuguntla on Aug 12, 2008 5:37 PM

    Appreciate the reply.  I of course did try to re-execute SAPRUPGM.  In background, it runs for 2 seconds and produces no log or spool.  When I run on-line, and un-tick the box for output log file, the resulting list shows these messages for the gree question mark notes.   These notes are no longer visible in SNOTE. Basically I'm stuck - with the green question mark, I don't know how to get rid of these Notes in SPAU.
    Corrections in SAP Note                                                                               
    NOTE 0000683004 0003                                                        Inconsistent data                       
    NOTE 0000693190 0002                                                        Inconsistent data                       
    NOTE 0000731027 0001                                                        Inconsistent data                       
    NOTE 0000764040 0003                                                        Inconsistent data                       
    NOTE 0000768618 0001                                                        Inconsistent data                       
    NOTE 0000770227 0001                                                        Inconsistent data                       
    NOTE 0000772460 0001                                                        Data for SAP Note 0000772460 incomplete 
    NOTE 0000775691 0002                                                        Inconsistent data                       
    NOTE 0000777671 0003                                                        Inconsistent data                       
    NOTE 0000782311 0002                                                        Inconsistent data                       
    NOTE 0000784108 0001                                                        Inconsistent data                       
    NOTE 0000785324 0002                                                        Inconsistent data                       
    NOTE 0000802475 0004                                                        Inconsistent data                       
    NOTE 0000826538 0002                                                        Inconsistent data                       
    NOTE 0000843717 0002                                                        Inconsistent data                       
    NOTE 0000864505 0002                                                        Inconsistent data

  • Clearing of SPAU for outdated OSS notes.

    Hi All,
    We are upgrading our system from 4.6 to ECC 6. Now when we cleared the SPAU we left the OSS notes which are not relavent to ECC 6 and are of lower version. Our question is how to clear those notes from SPAU list? Is there any particulart method?
    Please help me to solve this issue.
    Thanks & Regards,

    For obsolete notes you can select 'Reset to Original'..
    This would mean that you are accepting the original object which is coming with the upgrade and it already contains the note changes.
    Ankur Parab

  • SPAU actions with grey notes

    Hello folks!
    Guide me please,
    There are many threads in SCN about grey notes, but nothing about one thing. Must i import requst with reseted notes, of course, from DEV to PRD system?

    The status of SAP-delivered code really should be in sync between DEV, QAS, and PRD, except for where you have applied Notes or Support Packs in DEV and not yet in the downstream systems.  You should not make the changes in QAS.  You were right the first time, reset the 'grey' Notes in SPAU in DEV and add those resets (along with all your other SPAU changes) to a transport request per the normal SPAU process, then let that transport request be imported automatically as part of your support pack queue in both QAS and PRD.  You need to do it this way in QAS to ensure that the import actually works correctly.  If you "do the changes" in QAS to import into PRD, then you haven't actually tested that PRD queue import anywhere.  This, also, is how DEV systems get badly out of sync.
    The only reason to run SPAU again in QAS is to a) ensure that your transport took care of everything, or b) fix things that are out of sync with DEV because you've been doing it incorrectly in the past.

  • Spau Adjustment with Note Corrections

    Hi All,
    I am working with SPAU for the forst time, I ran SPAU and under the Note Corrections I found one note with a status of "Yellow color traingle ". When I clicked on this it asked me if I want to change the user on this note and I clicked it yes.... and after that it implemented the note and it went away from the note corrections list under SPAU. So my concern is if this is the right way of doing it or do I need to do something else.
    Also I looked for all the notes in SPAU with Yellow lightes and then I looked out for these in SNOTE and found that few of them have the status "can be implemented", some have "incompletely implemented". So i am just wondering what do I need to do in such case.
    Edited by: rajatg on Aug 28, 2009 5:51 PM

    Yellow status means "SAP says the note is applicable for your system, but I cannot apply everything automatically. There are something you need to apply manually"
    SAP Help says
    "The system might display note corrections with a yellow traffic light symbol during modification adjustment (transaction SPAU). The correction implemented previously based on a note was overwritten by a Support Package that does not contain these corrections. Note implementation is restarted if you click the yellow traffic light. "
    So basically yellow means the note is okay for your system but something is wrong with corrections/modifications. I recommend you look the note in OSS and corrections and compare each correction object after applying the note in SPAU. So you might find somethings should be done manually.
    Eventhough yellow notes can be applicable, you can look the note in OSS, then decide not to apply it based on SAP version, support package. So you can choose "Reset to Original" option from toolbar or right click.
    One more thing is important to remember when the notes are applied in SPAU, you have a SAP Net (OSS) connections from your system, so SPAU can check the latest version of the note.

  • Performing SPAU in Production System

    Dear Team,
    We are in the process of upgrading our Production system from EHP3 to EHP7.
    We upgraded our Quality system with SPDD and SPAU transport requests from Development system and it finished successfully.
    But after upgrading our Kernel in Production system and before performing the EHP7 upgrade, we applied two SAP notes in Production system, these notes were transported from our temporary development(un-upgraded) system(parallel landscape).
    While performing the EHP upgrade in Production system,  SUM has prompted us the below message
    “Decide about Incomplete Modification Transport”
    CAUTION: The program has found the transport "MEDK906662"(our SPAU transport) for SPAU but it does not contain all objects which need adjustment.
    When we checked the log file it show that two objects are missing in the SPAU transport.We suspect these are the SAP Notes which we applied after kernel upgrade and are missing in SPAU transport request.
    Please let me know how we can correct this issue in Production system. I know that SPAU will appear in Production system, but will the system allow me to re-apply/reset the SAP note in SPAU as this system will be un-modifiable.

    System Change. Global setting "modifiable". Componenents "modifiable". Namespaces "modifiable".
    Client setting-> select client -> Automatic recording of changes, changes to repository and cross-client customising allowed, protection level 0.
    If that doesn't work, give yourself SAPALL and try again.
    If that doesn't work, contact SAP because something is messed up. I've successfully applied notes in P systems during upgrade. Including ones that modify SAP_APPL.

  • HR Objects in SPAU during upgrade from 4.6C to ECC 6.0

    We are in the process of upgrading and have come to the point in SAPup where we need to address all customizations in SPAU.  There were several HR objects displayed (both logical and physical info objects), and from what I have been reading, there should be no HR objects listed.  I followed the instructions in OSS note 519678 to remove unnecessary HR objects from table SMODILOG using program H99PDSY_REPAIR_SMODILOG.  This did remove quite a few, but I am still left with some.
    Can anyone provide information on what I should do to resolve this issue.  I thought that maybe, the information that HR objects should not be in SPAU could be wrong, so I attempted to reset one object to original.  When I did this, it prompted me to create a new "customizing" transport request, when all of the other objects related to SPAU were put into a "workbench" transport.  I also understand that there should only be one transport for all SPAU adjustments, so this further makes me believe these objects should not be showing up.
    Thank you,

    Hello Leeanna,
    Apply this note. and execute the mentioned report, this deletes all the HR objects
    Note 634146 - SPAU: Objects from the customer namespace in SPAU

  • Message "Carry out modification comparison... No Change possible" and SPAU

    I'm trying to manually implement SAP note 1400194 and 1428579 both need to amend the Include RPCP45GD.
    Every time you try and open the Include in edit mode  to apply the changes manually you get the message
    "Carry out modification comparison for REPS RPCP45GD first. No Change possible"
    So I run SPAU... but the object  RPCP45GD does not exist in SPAU so I can't do a modification comparison on something that's not there !
    Any ideas how I should proceed ?
    cheers Hugh

    Modification assistant is on, otherwise SPAU would not work...
    Activated object but had no effect...
    However I did find a note in SPAU that was unreleased that related to another note that seemed to change the include I am looking at. This may be the reason why it's locked.
    SAP's modification assistant is about as useful as a hole in  the head !

  • SPAU:No SPAU when applying the package in QAS system

    Hello Experts ,
    i was applying SAP_APPL in dev system , and SPAU occured . we sent the conflicts to dev team and got all the
    adjustments done by them and record that in a transport request . we did not release the transport request from
    Dev system.Now i am applying  SAP_APPL in my QAS system , but i am not getting SPAU .
    could anyone help me to understand why i am not getting SPAU here.
    we have not imported the SPAU adjustment to QAS system.
    how/where  can i find (table entry ) to ensure that i get SPAU in QAS system also.
    our patching activity is standstill , any help would be higly appreciated.

    It is not uncommon that you are getting some objects in SPAU in development system but not in quality system. Reasons because: there will be number of standard programs in development system that have been modified but same has not been transported to quality/production system. So, if you are not getting SPAU in quality system then you should not transport SPAU request in quality/production.

  • Insertion in enhancement not possible

    I'm working on an upgrade from 4.6c to ECC 6.0. I have to make a change in a standard function: RV_ACCOUNTING_DOCUMENT_CREATE.
    The change that I want to make, is situated in an enhancement. But the system doesn't allow me to  insert inside the enhancement (not via SPAU, mod. assistant and not in change mode ABAP).
    What can I do?
    thx for your help,

    Iu2019m sorry if Iu2019m not very clear, but Iu2019m still trying to understand how this works.
    This is the situation:
    There is an enhancement section u2026u2026u2026..code, statements that can be changedu2026. u2026u2026u2026u2026..endenhancement-section
    The title of the section is
    enhancement-section   rv_accounting_document_crea_08     spots      es_saplv60b
    code, statements,    change possible
    there are 2 enhancements, for the above enhancement section, and in these enhancements, the code canu2019t be changed ( even in change mode, no changes are allowed by the system )
    ENHANCEMENT 3  AD_BOS_01_SAPLV60B.        "active version
    Code, statements, no change possible
    ENHANCEMENT 5  OI0_COMMON_SAPLV60B.    "active version
    Code, statements, no change possible
    How do I know which code is used?
    If I want a custom change, do I do this in the enhancement-section?
    How does the system know it has to use this code?
    thx for helping me out,

  • Error description of SPAU

    how to do find error description in SPAU. For example i have 1 error in selection view, it involves lot of tables and search helps so on. How do i find what exactly missing from old version (sap 4.6) to new version (ERP2005).

    for DDIC changes u have to see SPDD not in SPAU.

  • What is the impact of R/3 upgradation from 4.7 to ECC 6 on BI

    Dear all,
    Can any one tell me what will be the impact of R/3 Upgradation on BI... as we are shortly going to upgrade our R/3 from 4.7 to ECC 6.
    Do we need to take any precautions in R/3 and aswell as BI
    Please give the information...points will be given 

    Please Refer this as this vll give u the Pros and Cons for upgrade.
    This Wiki contains Rob Moore's ( BW Manager, Edwards Limited) team’s experiences in upgrading Business Warehouse System from 3.0B to BW 7.0.
    1 Upgrading from BW 3.0B to BW 7.0 (Netweaver 2004s)
    2 Introduction
    3 Overview & Scope
    4 Drivers
    5 Environment
    6 Resource & Timescales
    7 High Level Plan
    8 Summary Task List
    8.1 #Support Pack Hike
    8.2 #Plug-in installation
    8.3 #PREPARE process
    8.4 #Dbase upgrades
    8.5 #System Upgrade
    9 Lessons Learnt
    10 Issues & Fixes
    10.1 Unfixed Issues
    10.2 Fixed Issues
    11 Regression Testing Process
    11.1 Introduction
    11.2 Set up
    11.3 Actions
    11.4 Security
    12 Transport Freeze
    13 Web Applications
    13.1 Dashboards
    13.2 Internet Graphics Server (IGS)
    14 Detailed Task Lists
    14.1 Support Pack Hike (detail)
    14.2 Plug-in installation (detail)
    14.3 Dbase upgrades (detail)
    14.4 PREPARE Process (detail)
    14.5 System Upgrade (detail)
    Upgrading from BW 3.0B to BW 7.0 (Netweaver 2004s)
    This Wiki contains my team’s experiences in upgrading our Business Warehouse System from 3.0B to BW 7.0.
    Hopefully it will be useful to anyone else who's about to embark on this. If there's anything I've missed or got wrong, then please feel free to edit it or contact me and I'll try to explain.
    Rob Moore - BW Manager, Edwards Limited.
    Overview & Scope
    This was to be a technical upgrade of BW only. The new BW 7.0 web functionality & tool suite which requires the Java stack rather than the ABAP stack was out of scope. We had heard that the latter was where most of the problems with the upgrade lay. Our plan is to wait for this part of BW 7.0 to become more stable. Also it has a big front end change and the business didn't have sufficient resource to cope with that much change management.
    3.0B at the end of its maintenance
    Opportunities to do better reporting
    Options to utilise BI Accelerator
    Our R/3 system was at 4.6C and was not going to be upgraded. We have APO at version SCM4.0.
    Our BW system is approximately 300 GB, with 125 global users. It was at version 3.0B SP 18
    We have Development, Acceptance and Production environments.
    Resource & Timescales
    The Project ran for 3.5 months from Feb to May 2007. We used the following resources. The percentages are the approx. amount of their time spent on the project.
    Project Manager * 1 – 70%
    BW technical team * 3 – 50%
    ABAP coder * 1 – 10%
    SAP Systems Development expert * 1 – 20%
    Basis * 1 – 25%
    High Level Plan
    These are the basic areas. We planned to complete this process for each environment in turn, learning our lessons at each stage and incorporating into revised plans for the next environment. However we did the Support Packs and Plug-Ins in quick succession on all environments to keep our full transport path open as long as possible.
    Upgrade BW to the minimum support pack.
    Install R/3 Plug-ins PI 2004.1
    Run PREPARE on BW
    Dbase upgrades (Database & SAP Kernel upgrade)
    System Upgrade
    Summary Task List
    This list contains all the basic tasks that we performed. A more detailed check list is shown below for each of the headings.
    #Support Pack Hike
    We moved only to the minimum acceptable SP as this seemed most likely to avoid any problems with the 3.0B system prior to the upgrade.
    Apply OSS 780710 & 485741
    Run Baseline for Regression tests
    Full Backup
    Apply SP's (we were at SP18, going to SP20)
    SPAU list review
    Regression testing
    #Plug-in installation
    Apply SAP note 684844
    Import and patch Basis plugin PI 2004.1
    SPAU list review
    #PREPARE process
    BW Pre-Prepare tasks
    BW - Inconsistent Data fix
    Review of results
    Any showstoppers from PREPARE?
    #Dbase upgrades
    Database Upgrade (FixPak)
    SAP Kernel Upgrade
    #System Upgrade
    Reverse Transport of Queries
    Reconnect DAB & SAB to AAE
    Run Baseline for Regression tests
    Full Backup
    Run the Upgrade
    SPAU list review
    Regression testing
    Lessons Learnt
    Testing is all! We picked up on a lot of issues, but would have picked up more if we'd had a full copy of our production environment to test over.
    Our approach of doing a full upgrade on each environment before moving to the next one paid dividends in giving us experience of issues and timescales.
    Write everything down as you go, so that by the time you get to upgrading production you've got a complete list of what to do.
    We succeeded because we had people on our team who had enough experience in Basis and BW to be able to troubleshoot issues and not just read the manual.
    The SAP upgrade guide is pretty good, if you can understand what they're on about...
    Remember the users! The fact that the loads have been successful doesn't count for anything unless the users can see the data in Excel! There's a tendency to get caught up in the technology and forget that it's all just a means to an end.
    Issues & Fixes
    I've listed the main issues that we encountered. I have not listed the various issues where Transfer rules became Inactive, DataSources needed replication or we had to reinstall some minor Business Content.
    Unfixed Issues
    We could not fix these issues, seems like SP 13 will help.
    Can’t delete individual request from ODS
    After PREPARE had been run, if we had a load failure and needed to set an ODS request to Red and delete it, we found that we could not. We raised an OSS with SAP but although they tried hard we couldn't get round it. We reset the PREPARE and still the issue persisted. Ultimately we just lived with the problem for a week until we upgraded production.
    Error when trying to save query to itself
    Any query with a re-usable structure cannot be saved (more thsan once!)
    OSS 975510 fixed the issue in Dev and Acc, but NOT in Production! SP 13 may solve this once it's released.
    Warning message when running some queries post-upgrade
    Time of calculation “Before Aggregation” is obsolete. Not a big issue so we haven't fixed this one yet!
    Process Chain Scheduling – Timing error
    Process chains get scheduled for the NEXT day sometimes and has to be manually reset.
    See OSS 1016317. Implement SP13 to fix this. We will live with it for now .
    Fixed Issues
    Duplicate Fiscal Period values in Query
    If you open up a drop down box ("Select Filter Value") for Fiscal Year/Period to filter your query, you are presented with duplicate entries for Month & Year.
    Due to Fiscal Year Period InfoObject taking data from Master Data not InfoProvider. Thus it picks up all available periods not just Z2.
    Auto-Emails being delayed
    Emails coming from BW from process chains are delayed 2 hours on BW before being released
    Due to userids that send these emails (e.g. ALEREMOTE) being registered on a diffferent timeazone (i.e. CET) from the BW system (i.e. GMT)
    “Pgm_Not_Found” short dump
    Whenever a query is run via RRMX or RSRT
    Call transaction RS_PERS_ACTIVATE to Activate History and Personalisation
    Characteristics not found
    When running a query the warning message Characteristic does not exist is displayed for the following: 0TCAACTVT, 0TCAIPROV, 0TCAVALID
    We activated the three characteristics listed and the warnings stopped. NO need to make them authorisation-relevant at this stage.(also did 0TCAKYFNM)
    System generated Z pgms have disappeared
    Post-upgrade the system Z-pgms ceased to exist
    Discovered in Development so we compared with pre-upgraded Production and then recreated them or copying them from production.
    Conversion issues with some Infoobjects
    Data fails to Activate in the ODS targets
    For the InfoObjects in question, set the flag so as not to convert the Internal values for these infoobjects
    InfoObject has Conversion routine that fails, causing load to fail
    The routine prefixes numeric PO Numbers with 0’s. SD loads were failing as it was not able to convert the numbers. Presumably the cause of the failure was the running of the Pre-Prepare RSMCNVEXIT pgm.
    Check the Tick box in the Update rule to do the conversion prior to loading rather than the other way round.
    Requests fail to Activate on numeric data
    Request loads OK (different from above issue) but fails to Activate
    Forced conversion within the update rules using Alpha routine. Deleted Request and reloaded from PSA.
    Database views missing after pre-PREPARE work
    Views got deleted from database, although not from data dictionary
    Recreated the views in the database using SE14.
    Workbook role assignations lost
    We lost a few thousand workbook assignments when we transported the role they were attached to into Production
    The workbooks did not exist in Development, thus they all went AWOL. We wrote an ABAP program to re-assign them in production
    Regression Testing Process
    We were limited to what we could do here. We didn't have a sandbox environment available. Nor did we have the opportunity to have a replica of our production data to test with, due to lack of disk space in Acceptance and lack of sufficient Basis resource.
    Set up
    We manually replicated our production process chains into test. We didn't have any legacy InfoPackages to worry about. We asked our super-users for a list of their "Top 10" most important queries and did a reverse transport of the queries from Production back into test (as we do not generally have a dev/acc/prodn process for managing queries, and they are mostly created solely in prodn). We made sure every application was represented. In retrospect we should have done some Workbooks as well, although that didn't give us any problems.
    Prior to the various changes we loaded data via the Process chains and ran the example queries to give ourselves a baseline of data to test against. After the change we ran the same queries again and compared the results against the baseline. We tried to keep R/3 test environments as static as possible during this, although it wasn't always the case & we often had to explain away small changes in the results. After upgrading BW Development we connected it to Acceptance R/3, so that we had pre-upgrade (BW Acceptance) and post-upgrade (BW Development) both taking data from the same place so we could compare and contrast results on both BW systems. We did the same thing once BW Acceptance had been upgrading by connecting it (carefully!) to Production R/3. To get round the lack of disk space we tested by Application and deleted the data once that Application had been signed off. Once we got to System test we involved super-users to sign off some of the testing.
    We chose to implement the new security schema rather than choosing the option to stick with old. For us, with a relatively small number of users we felt we could get away with this & if it all went wrong, just temporarily give users a higher level role than they needed. Our security roles are not complex: we have end user, power-user and InfoProvider roles for each BW application, together with some common default roles for all. In the event we simply modified the default "Reports" role that all our users are assigned, transported it and it all went smoothly. Apart from the fact that everyone's workbooks are assigned to this role and so we "lost" them all !
    Transport Freeze
    Once you've upgraded Development you've lost your transport path. We planned around this as best we could and when absolutely necessary, developed directly in Acceptance or Production, applying those changes back to Development once the project was complete. Depending on what other BW projects you have running this may or may not cause you pain!
    Web Applications
    We had various dashboards designed via Web Application Designer. All these continued to function on the upgraded system. However there were various formatting changes that occurred e.g. Bar graphs were changed to line graphs, text formats on axes changed etc. SAP provides an upgrade path for moving your Web applications by running various functions. However we took the view that we would simply re-format our dashboards manually, as we didn't have very many to do. Plus the external IGS (see below) powered all our environments and needs upgrading separately as part of the SAP method. Thus we couldn't have tested the SAP path in Development without risking Production. Sticking with manual mods was a lower risk approach for us. We did find we had to re-activate some templates from BC to get some of the reports to continue to work.
    Internet Graphics Server (IGS)
    We had an external IGS server with v3.0B. Post-upgrade the IGS becomes part of the internal architecture of BW and thge external server is redundant. We found no issues with this; after the upgrade BW simply stops using the external IGS and no separate config was needed.
    Detailed Task Lists
    Support Pack Hike (detail)
    Apply OSS 780710 & 485741
    Communicate outage to users
    Warning msg on screen
    Stop the jobs which extract data into delta queues
    Clear the delta queues by loading into BW
    Check RSA7 in PAE that delta queues are now empty
    Run Baseline for Regression tests
    Stop Delta queues
    Lock Out users
    Full Backup
    Apply SP's
    Upgrade the SAP kernel from 620 to 640
    SPAU list review
    Apply OSS Notes 768007 & 861890
    Unlock Test users (inc. RFC id's on R/3)
    Regression testing
    Regression sign-off
    Remove warning msg
    Unlock users
    User communication
    Plug-in installation (detail)
    Communicate outage to users
    Warning msg on screen
    Apply SAP note 684844
    Lock out users
    Full Backup
    Empty CRM queues
    Import and patch Basis plugin PI 2004.1
    SPAU list review
    Apply OSS 853130
    Switch back on flag in TBE11 (app. BC-MID)
    Remove warning msg
    Unlock users
    User communication
    Dbase upgrades
    Dbase upgrades (detail)
    Communicate outage to users
    Warning msg on screen
    Run Baseline for Regression tests
    Stop the Data extract jobs
    Full Backup
    Lock Out users
    Apply FixPak13SAP to DB2 database
    Upgrade the SAP kernel from 620 to 640
    Apply OSS 725746 - prevents RSRV short dump
    Unlock Test users (inc. RFC id's on R/3)
    Regression testing
    Regression sign-off
    Remove warning msg
    Unlock users
    User communication
    PREPARE Process (detail)
    Pre-PREPARE Process
    Repair Info objects and recreate the views
    Communicate outage to users
    Warning msg on screen
    Run Baseline for Regression tests
    Stop the Data extract jobs
    Lock Out users
    Full Backup
    If there conversion process runs longer delay the regular backup
    Re-run Baselines and sign off
    If there conversion process Fails repeat the steps on Sunday after the regular backup
    BW work
    Back up customer-specific entries in EDIFCT (note 865142)
    Activate all ODS objects
    Execute report RSUPGRCHECK with flag "ODS objects" (note 861890)
    Check Inconsistent InfoObjects - Upgr Guide 4.4; OSS 46272; Convert Data Classes of InfoCubes - Upgr Guide 4.3
    Execute report SAP_FACTVIEWS_RECREATE (note 563201)
    Make sure Delta queues are empty (RSA7)
    Basis Work
    Full Backup of BW
    Lock users
    Unlock id's RFC id's and designated test users
    Confirm backup complete OK
    Apply OSS 447341 Convert Inconsistent Characteristic Values - Upgr Guide 4.5
    Confirm OK to PREPARE
    Review of results
    System Upgrade (detail)
    Communicate outage to users
    Process errors from PREPARE
    Check disk space availability for PAB
    Warning msg on screen
    Reverse Transport Queries from PAB to SAB & DAB
    Change BW to R/3 connection
    Get backup put on hold, for Ops to release later
    Ensure Saturday night backup is cancelled
    Final run of PREPARE
    Run Baseline for Regression tests
    Clear Delta Queues
    Delete Local Transports
    Remove process chains from schedule
    Lock Out users (with some exceptions)
    Confirm to Ops and Angie that we're ready
    Full Backup
    Incremental backup of Unix files
    Back up kernel
    Unpack latest 700 kernel to upgrade directory
    Check ids required for upgrade are unlocked
    Check no outstanding updates
    Turn off DB2 archiving
    Open up the client for changes
    Stop saposcol, & delete from exe directory
    Run the Upgrade
    Execute the script
    Perform the database-specific actions
    Perform follow-up activities for the SAP kernel
    Reimport additional programs
    Import Support Packages
    Call transaction SGEN to generate ABAP loads
    Transport Management System (TMS)
    Handover to BW Team
    SPAU list review
    Apply OSS Notes from SPAU
    Process Function Module XXL_FULL_API (part of SPAU)
    Restore table EDIFCT (if required)
    Transport Fixes from our BW Issue list
    Convert the chart settings - manually
    Perform activities in the Authorization Area
    Activate hierarchy versions
    Update the where-used list
    Execute the conversion program for the product master
    Transport New roles to PAB
    Unlock selected users
    Regression testing
    Regression sign-off
    Go / No Go decision
    Restore if required
    Remove warning msg
    Tell Ops that the CR is now complete
    Lock down PAB
    Unlock users
    User communication
    Perform the follow-up activities for SAP Solution Manager
    Reschedule background jobs
    Reschedule weekly backup on Ctrl-M
    Drinks all round.
    Vendors mentioned: dBase
    Hope this helps.

Maybe you are looking for