Upgrade from MX 2004 to 11

I have just purchased the Windows upgrade from Director MX
2004 to Director 11.
Will running this upgrade obliterate Director MX 2004 and
replace it with Director 11?
Or will I still have a working copy of Director MX 2004 as
well?
The reason that I ask is that I am not entirely certain that
my computer has the needed horsepower to run Director 11, and in
that tragic event, I'd like to be able to fall back to Director MX
2004 until such a time when extra horsepower can be added.
Cliff

The upgrade will keep older versions intact - and there will
be no conflicts
in running multiple Directors. I have both Director MX 2004
and Director 11
running fine on the same system.
"Cliff Johnson" <[email protected]> wrote in
message
news:gich2u$ilq$[email protected]..
>I have just purchased the Windows upgrade from Director
MX 2004 to Director
>11.
>
> Will running this upgrade obliterate Director MX 2004
and replace it with
> Director 11?
>
> Or will I still have a working copy of Director MX 2004
as well?
>
> The reason that I ask is that I am not entirely certain
that my computer
> has
> the needed horsepower to run Director 11, and in that
tragic event, I'd
> like to
> be able to fall back to Director MX 2004 until such a
time when extra
> horsepower can be added.
>
> Cliff
>

Similar Messages

Limitations of upgrading from ERP 2004 to 2005

We are evaluation completing an upgrade from ERP 2004 to 2005. However, we found a limitation in note 879335 regarding upgrading the portal.
We have an Enterprise Portal instance that is separate from the SAP ECC J2EE add-in. The ESS components including XSS run on the J2EE add-in.
According to this note, we cannot upgrade the XSS component on the J2EE add-in because it
is not running on EP. Does this mean we need to undeploy the XSS components and then upgrade the J2EE and then install the XSS component? or Do we need to import the XSS component on EP and then
upgrade?
Why is this a limitation?

I have isolated the issue further. In the following code fragment the event is being fired twice the first time and never again:
          If pVal.FormType = 133 And pVal.EventType = SAPbouiCOM.BoEventTypes.et_FORM_LOAD Then
               '// get the event sending form
               'SBO_Application.MessageBox("Hello world")
               oForm = SBO_Application.Forms.GetFormByTypeAndCount(pVal.FormType, pVal.FormTypeCount)
               oNewItem = oForm.Items.Add("Button1", SAPbouiCOM.BoFormItemTypes.it_BUTTON)
               oNewItem.Left = 285
               oNewItem.Top = 382
               oNewItem.Width = 100
               oNewItem.Height = 19
               oNewItem.FromPane = 0
               oNewItem.ToPane = 1
               oButton = oNewItem.Specific
               oButton.Caption = "New Button"
          End If
End Sub
The code is an adaptation of the SDK VB.NET sample ('11.SystemFormManipulation'), which is supplied with the latest version of the SDK installation.
The big question is why is the event being fired twice.

Precautions upgrading from MX2004 to DW8

Hiya there
Can someone point me to a set of guidelines that are best for
upgrading from
DWMX 2004 to DW8
i.e. backing up site definitions and folders, telling
DWMX2004 that I'm
changing to a new version etc etc?
Thanks
Jos

If you want to back up site definitions, you can either use
the DW SITE |
Export option to export them, or this excellent utility -
http://mm-exporter.joexx.de
Other than that, leave DMX2004 installed, and install DW8 -
all sites and
extensions should migrate. When you have verified that that
is the case,
then you can uninstall DMX2004.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"Jos Medinger" <[email protected]> wrote in
message
news:ekjpcf$68o$[email protected]..
> Hiya there
>
> Can someone point me to a set of guidelines that are
best for upgrading
> from DWMX 2004 to DW8
>
> i.e. backing up site definitions and folders, telling
DWMX2004 that I'm
> changing to a new version etc etc?
>
> Thanks
>
> Jos
>

Upgrade from SAP Webas 6.40 to SAP Netweaver 2004s

Do we have to change the virtual host name used for high availability clustering environment to local host name before we conduct the upgrade from SAP WebAS 6.40 to SAP NetWeaver 2004's ?

Do we have to change the virtual host name used for high availability clustering environment to local host name before we conduct the upgrade from SAP WebAS 6.40 to SAP NetWeaver 2004's ?

Functional Upgrad from BW 3.x to Netweaver 2004s

Hi Guys,
i have gone through almost entite forum on sdn but i could not get the information/document for functional upgrad. currently i am using BW 3.5 and going for BI 7.0
could some one tell me the steps to do functional upgrad to BI 7.0. i am not talking abt the technical upgrad here. i would really appriciate if some one could send me some document that gives step to step procedure to do the functional upgrad.
ur help will be rewarded in terms of points.
manmit

Hello,
There are multiple resources to review since a functional upgrade requires a value proposition, gap analysis, and in some cases an ROI.
First, all releases below BW 3.5 are currently scheduled to go off maintenance December 2006. So customers need to be at release BW 3.5 or higher by Jan. 1, 2007. This helps with the value proposition!
Please check the delta feature list from BW 3.5 to NW 2004s BI on SDN or the Service Marketplace. As Prakash mentioned, customers should evaluate which features they want to implement and the timeframe. Many customers will focus on a technical upgrade which is what we recommend initially, and also determine which features could be included in the first go-live. Other features can be added to subsequent go-lives, but this is based on customer specific go-live timetables. Some customers have implemented only new functionality while others only chose the most important, i.e. BI accelerator, BEx.
Also, please check the webinar entitled "Upgrading to NW 2004s BI" which covers many of these points and lists the relevant references.
Finally, SAP (and trained partners) will be offering an Upgrade Assessment service beginning of July which will assist customers in planning an upgrade to NW 2004s BI including both technical and functional considerations. Please contact your SAP account team for more information.
Thanks,
Bryan

Upgrade from 4.6B to mySAP ERP 2004 ( i.e. ECC 5.0)

Hi
We are upgrading from 4.6B to ECC 5.0 without unicode conversion.
I came to know the from service/sap.com/upgrade website which shares the delta functionality added by SAP during upgrade.
However, I am still looking around for typical technical hurdles which one faces during the upgrade. As SAP says the upgrade is purely Technical in nature.
Any feedback/documents you have is welcome.
Pls share to my mail id [email protected]
thanks

Hi Satish,
Some of the things which we will do at Upgrades.
1) Identifing additional warings/erros using EPC(Exteneded Program Check) and correcting them.
2) Identifying the obselette statements/function modules and correcting them using proper replacement of function modules or adding additional clauses to statements.
Eg: Replacing oboselette FMs like WS_DOWNLOAD with GUI_DOWNLOAD, UPLOAD with conjuction of CL_GUI_FRONTEND_SERVCIES=>FILE_OPEN_DIALOG with GUI_UPLOAD.
3) BDC Corrections: This has both technical as well as functional scope of changes.
Mainly BDC Corrections related to
a) Addition of new field in upgrade version
b) Screen number change to parcular filed in upgrade version
Thanks,
Vinay

Upgrading from Tiger to Leopard on a G5 Dual processor early 2004 version

I am about to upgrade my OS from Tiger (10.4.11) to the newest version of Leopard on my Dual G5 PPC. I have an ATI Radeon X800 XT video card as well as a third party PCI firewire card added. 3.5G of RAM.
Should I expect any bumps or issues when upgrading? Also, will my system perform the same, slower or faster after install?
I am a heavy user of Aperture, Photoshop as well as Final Cut Express. I will be installing the newest version of Fotomagico once 10.5 is set up.
Any advice is greatly appreciated.
Pete

You should verify that all your critical software can run under Leopard or that there are upgrades available. Check with which version of Leopard the software is known to be compatible, and don't install a later version of Leopard.
Otherwise I suggest reading this:
Essential Steps Before Updating OS X!
Please do things right before updating OS X in order to avoid problems.
A. Repair Hard Drive and Permissions
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger and Leopard.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now restart normally.
If DU reports errors it cannot fix, then you will need Disk Warrior (4.0 for Tiger, and 4.1 for Leopard) and/or TechTool Pro (4.6.1 for Leopard) to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
B. Clone Using Restore Option of Disk Utility
1. Open Disk Utility from the Utilities folder.
2. Select the destination volume from the left side list.
3. Click on the Erase tab in the DU main window. Set the format type to Mac OS Extended (journaled, if available) and click on the Erase button. This step can be skipped if the destination has already been freshly erased.
4. Click on the Restore tab in the DU main window.
5. Select the destination volume from the left side list and drag it to the Destination entry field.
6. Select the source volume from the left side list and drag it to the Source entry field.
7. Double-check you got it right, then click on the Restore button.
Destination means your backup drive (should be erased first.)
Source means your startup drive or volume.
C. If you are installing a new version of OS X such as upgrading from 10.4.x to 10.5.x, then I suggest you do the following:
How to Perform an Archive and Install
An Archive and Install will NOT erase your hard drive, but you must have sufficient free space for a second OS X installation which could be from 3-9 GBs depending upon the version of OS X and selected installation options. The free space requirement is over and above normal free space requirements which should be at least 6-10 GBs. Read all the linked references carefully before proceeding.
1. Be sure to use Disk Utility first to repair the disk before performing the Archive and Install.
Repairing the Hard Drive and Permissions
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported, then quit DU and return to the installer.
2. Do not proceed with an Archive and Install if DU reports errors it cannot fix. In that case use Disk Warrior and/or TechTool Pro to repair the hard drive. If neither can repair the drive, then you will have to erase the drive and reinstall from scratch.
3. Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When you reach the screen to select a destination drive click once on the destination drive then click on the Option button. Select the Archive and Install option. You have an option to preserve users and network preferences. Only select this option if you are sure you have no corrupted files in your user accounts. Otherwise leave this option unchecked. Click on the OK button and continue with the OS X Installation.
4. Upon completion of the Archive and Install you will have a Previous System Folder in the root directory. You should retain the PSF until you are sure you do not need to manually transfer any items from the PSF to your newly installed system.
5. After moving any items you want to keep from the PSF you should delete it. You can back it up if you prefer, but you must delete it from the hard drive.
6. You can now download a Combo Updater directly from Apple's download site to update your new system to the desired version as well as install any security or other updates. You can also do this using Software Update.
D. Download the Standalone Combo Updater from Apple.
Be sure you quit all running applications and disconnect all peripherals (except original keyboard and mouse) before running the installer. When the installer is running do not use the computer in any way other than to respond to an installer dialog.
Install the update by double-clicking on the installer package icon. When the installation is completed Restart the computer. Your computer will boot twice - this is normal. Upon completion of the update use Disk Utility to repair permissions. Not all permissions will seem repaired. You will get spurious reports regarding permissions related to iTunes, Front Row. These can be ignored. They will appear every time you repair permissions.
Following these basic steps should prevent most if not all updating problems. Note that if you have unrepairable disk problems reported in Step A then DO NOT update your system until those problems are resolved.

Login Error after Upgrading from BW 3.5 to BI 7.0

Hi Experts,
We have carried out an upgrade from BW 3.5 to BI 7.0.
After Upgrade we are not able to login using SAP GUI. we are getting an error saying..
Username or Password not Valid..
During the upgrade (in Netweaver 2004s ) is there procedure necessary to be followed, which we could have missed..
Your response will be greatly appreciated.
Regards
LRaghunahth

Hi
Thanks a lot for your reponse.
Basically I am able to login thru sap* / ddic and can unlock the users / reset the password.
But the customer wants to know why the user is getting locked and it happened because of any procedure miss whil performing the upgrade..
if it is usual that users get locked during upgrade, any SAP Notes to refer..
Thanks a lot for helping in this community.
Best Regards
L Raghunahth

ITunes 6.0.3.5 Upgrade from 6.0.2 Sucessful!!!

If you have iTunes 6.02 working now upgrading to iTunes 6.03.5 is easy!! Just download "iTunesSetup.exe" from Apple.com and install it "ON TOP" over just "OVERWRITE" the old installation (meaning DON'T uninstall the old version of iTunes and QuickTime Player 7.04.) No problems opening iTunes afterwards. Good job Apple software engineers!! That was a good and fast fix!!
I am not sure if a clean uninstall and re-install of iTunes is needed now for everyone. How is everyone else getting along with upgrading to iTunes 6.03?
Curt Mueller
MSN Premium MVP (Jan. 2004)
Windows Vista Build 5270
PS- There is a "extra" folder in "C:\Program Files\InstallShield Installation Information" with only 1 file in it (instead of 2- "setup.inx" & "Setup.ilg.") Just "Setup.ilg" is in this old "{501BADCD-F8F7-44CB-AC3F-6ED25C1A28B5}" folder from the iTunes 6.02 setup. Maybe we can remove this one?

The iTunes 6.0.3.5 Upgrade from a "clean" installation of iTunes 6.0.2 above (on a clean install of WIndows XP Pro SP2 itself with no previous Apple softeware before this iTunes 6.0.2 and QuickTime Player 7.04 were EVER installed) left a file called "NewShortcut4_8C3BCD70236347B8A53EEE8A82FD5C78.exe" in "C:\WINDOWS\Installer\{501BADCD-F8F7-44CB-AC3F-6ED25C1A28B5}" besides the other file "Setup.ilg" left from iTunes 6.0.2 setup.
Curt Mueller
MSN Premium MVP (Jan. 2004)
Windows Vista Build 5270
HP Pavilion 552w Windows XP Pro Pentium 4 2.8GHz - 2048MB RAM

BW Upgrade from 3.x to 7.0

Folks,
We are planning to upgrade from BW 3.x to BI 7.0, Is it a direct update process or is it in 2 step process? And also I was reading some of the posts its says there are some issues to upgrade from 2004 to 2004s? Can some one point out those issues?
Thanks in Advance,
Kumar

Hi,
Some features of BI 7 are
1. In Infosets now you can include Infocubes as well.
2. The Remodeling transaction helps you add new key figure and characteristics and handles historical data as well without much hassle. This is only for info cube.
3. The BI accelerator (for now only for infocubes) helps in reducing query run time by almost a factor of 10 - 100. This BI accl is a separate box and would cost more. Vendors for these would be HP or IBM.
4. The monitoring has been imprvoed with a new portal based cockpit. Which means you would need to have an EP guy in ur project for implementing the portal !
5. Search functionality hass improved!! You can search any object. Not like 3.5
6. Transformations are in and routines are passe! Yess, you can always revert to the old transactions too.
this is a good PDF on Upgrade from BW 3.5 to BW 7.0
latest on upgrade tp BI7.0
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/2e8e5288-0b01-0010-2ea8-bcd4df5084a7
http://help.sap.com/bp_epv170/EP_US/Documentation/How-to/Planning/Master_Guide_NW2004s.pdf
You can seek more information on BI 7.0 in the SAP NetWeaver2004s Ramp-Up.
/community [original link is broken]
Re: BW 7.0 Release
Re: BW 7.0 Release
Re: BW 7.0
Please reward points.

Upgrading from EP 6.0 to 7.0

Hi ,
We are upgrading from EP6.0 to 7.0 ,We have many webdynpro applications written in 6.0 now if we upgrade to 7.0 do we have to make any changes to the applications , will the applications run on 7.0 with out any modifications??
Regards,
ravi.

Hai,
Some of the Controls added newly in Webdynpro 2004s. some UI elements like IFrame are depricated, but i seen all of my applications developed in 2004 are working in EP7.0 .
This thread discussing the differences between nw04 and nw04s
NW2004 vs. NW2004s
Regards,
Naga

ADWS Broken after in-place upgrade from Server 2008 R2 to Server 2012 R2

I performed an in-place upgrade from 64-bit Server 2008 R2 to Server 2012 R2. This machine ran Active Directory Web Services. After the upgrade ADWS will not start. I get the following event log error:
Log Name: Application
Source: .NET Runtime
Date: 11/21/2014 3:23:02 PM
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: COMPUTER
Description:
Application: Microsoft.ActiveDirectory.WebServices.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ServiceModel.CommunicationObjectFaultedException
Stack:
 at System.ServiceModel.Channels.CommunicationObject.Close(System.TimeSpan)
 at Microsoft.ActiveDirectory.WebServices.WindowsHostService.StartService(System.Object)
 at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
 at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
 at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
 at System.Threading.ThreadHelper.ThreadStart(System.Object)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
 <Provider Name=".NET Runtime" />
 <EventID Qualifiers="0">1026</EventID>
 <Level>2</Level>
 <Task>0</Task>
 <Keywords>0x80000000000000</Keywords>
 <TimeCreated SystemTime="2014-11-21T20:23:02.000000000Z" />
 <EventRecordID>65596</EventRecordID>
 <Channel>Application</Channel>
 <Computer>COMPUTER</Computer>
 <Security />
</System>
<EventData>
 <Data>Application: Microsoft.ActiveDirectory.WebServices.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ServiceModel.CommunicationObjectFaultedException
Stack:
 at System.ServiceModel.Channels.CommunicationObject.Close(System.TimeSpan)
 at Microsoft.ActiveDirectory.WebServices.WindowsHostService.StartService(System.Object)
 at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
 at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
 at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
 at System.Threading.ThreadHelper.ThreadStart(System.Object)
</Data>
</EventData>
</Event>

I compared the registry with a working system but the Counters - and all other keys - looked fine.
At the same time as upgrading a DC a colleague was updating an unrelated server, and he started to see similar events in the event log (but for the Dell OpenManage Essentials service, not ADWS). The error was complaining about KERNELBASE.dll which set my
spider sense tingling. We knew that this server had Windows Updates pending. Fully updating it solved the problem on that server.
I solved the ADWS problem in the end by fully Windows Updating the DC. In particular, the ADWS Service started successfully after installing KB2919355 and rebooting. That also
'unlocked' a further 59 updates pending.
After the in-place upgrade I always fully Windows Update but I'm 99% certain that KB2919355 did NOT show up when I did a Check for Updates straight after a reboot so I thought the DC was up-to-date. I then spent hours investigating the ADWS problem and rebooted
as part of the diagnostics. It was then that I noticed on the logon screen that there were updates pending...
Moral of the story? Windows Update, then Update again, and again, and again. The length of time it takes to Windows Update after an upgrade from 2008R2 to 2012R2 is painful though.

Upgrading from BW 3.1 to BI 7

Hi Experts,
Has anyone of you have experience in working on upgrading project from BW 3.1 to BI 7 ? Please do share it with me.
I have to start working on such project in a month or so...
So I need to know exactly what would be steps I need to go through from the scratch.
Please help me and I will certainly assign points.
Regards,
Akash.

hi Akash,
use the links,
BI Upgrade from 3.x to BI 7.0
http://csc-studentweb.lrc.edu/swp/Berg/articles/Portals%202004%20-%20Upgrade%20strategy%20v8.ppt
/people/prakash.darji/blog/2006/09/22/rolling-out-the-new-sap-netweaver-2004s-bi-frontend-tools
http://wiki.ittoolbox.com/index.php/Upgrade_BW_to_Netweaver_2004s_from_v3.0B
Upgrade to SAP BW 7.0 from 3.1: Impact on Business Content
with hopes
Raja Singh

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
Regards
venu

Hi
Please Refer this as this vll give u the Pros and Cons for upgrade.
Refer
http://wiki.ittoolbox.com/index.php/Upgrade_BW_to_Netweaver_2004s_from_v3.0B
This Wiki contains Rob Moore's ( BW Manager, Edwards Limited) teams experiences in upgrading Business Warehouse System from 3.0B to BW 7.0.
Contents
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)
Introduction
This Wiki contains my teams 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.
Drivers
3.0B at the end of its maintenance
Opportunities to do better reporting
Options to utilise BI Accelerator
Environment
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
Run PREPARE
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.
Cant 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 0s. 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
Introduction
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.
Actions
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.
Security
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
Dashboards
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
RSDG_ODSO_ACTIVATE
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
Run RSMDCNVEXIT Using BSSUPPORT ID
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
Run 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
UPGRADE "START"
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 saproot.sh 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.

Upgrading from BW 3.5 to BI7.0

Hi all,
What is the work involved in a upgrade process?Lets suppose we are upgrading from BW 3.5 to BI 7.0.
Thanks in Advance,
Aravind

Hi
go through this
Up grade 3.5 to BI 7.0
Upgrading BW 3.X to SAP NetWeaver 2004s BI
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/2e8e5288-0b01-0010-2ea8-bcd4df5084a7
/people/prakash.darji/blog
Rolling out the New SAP NetWeaver 2004s BI Frontend Tools
Troubleshoot the SAP NetWeaver 2004s BI Frontend Installation
/people/prakash.darji/blog
hope this helps.
M Kalpana
Message was edited by:
Kalpana M

Upgrade from MX 2004 to 11

Similar Messages

Maybe you are looking for