BPC 7.5 MS Migration From 7.0 MS

Question

Hello Experts,
We have installed new full install 7.5 MS ( Windows 2008/SQL 8) .
This is our test system and we want to know if we can migrate our existing 7.0 MS (2003/ SQL 8) to this new installation.
The upgrade document has Chapter 4 - Migrate Application Sets from 7.0, is it ok to follow the steps.
Procedure:
1.
In the Administration Console, choose Modify Application, without selecting any options. This applies several fixes related to business rules and send governor.
If the application status is "not processed", choose Modify Application, and select all options. To check the application status for an application, choose View application set statistics in the Manage Application Sets action pane.
NOTE
This is only relevant if you are installing Planning and Consolidation 7.5 SP01 or later.
If the regional language option of your Planning and Consolidation server is not English (for example, French, or German), choose Modify Application with the Process Application checkbox selected. This changes the application language property to English to overcome a conflict in decimal values.
2.
A new parameter for validating business rules has been added to the SPRUNELIM, SPICDATA, and SPICBOOKING stored procedures. You must update each logic file that calls one or more of these stored procedures by doing the following:
1.
Log on to the Administration Console.
2.
Expand Manage Logic Library, and open a logic file (such as Consolidation_Library.lgl) that call one or more of the three stored procedures.
3.
Add the [%SCOPETABLE%] parameter to each statement that calls each of the stored procedures.
4.
Validate and save the logic file.
4 Migrate Application Sets from 7.0
2010-11-25 PUBLIC 13/24
5.
Repeat steps 2–4 for each logic file that calls at least one of the stored procedures.
For more information about the new stored procedure, see SAP Note 1374381.
3.
Copy AuditClear.dts and AuditRestore.dts from the previous version of ApShell to your application sets after installing Planning and Consolidation 7.5. See SAP Notes 1355574 and 1357279.
Copy from:\\<FileServer>\..\WebFolders\ApShell\Planning\DataManager\PackageFiles\Examples
Copy to:\\<FileServer>\..\WebFolders\<Application Set>\<Application>\DataManager\PackageFiles\Examples.
4.
If you already have By User security reports, update existing reports by choosing the Publish By User report in Web Administration. See SAP Note 1365430.
5.
If you have a SQL Server 2005 environment, copy Copy from fact table.dtsx from ApShell to your application sets. See SAP Note 1365446.
Copy from:\\<FileServer>\..\WebFolders\ApShell\Planning\DataManager\PackageFiles\Examples
Copy to:\\<FileServer>\..\WebFolders\<AppSet>\<App>\DataManager\PackageFiles\Examples
6.
Planning and Consolidation 7.5 has new tasks. To apply the new tasks, go to the Admin console and run Modify Task Profile without any changes to the existing task profile (reprocess), or create new task profiles for each task and assign appropriate users. See SAP Note 1382583.
If you choose to reprocess existing task profiles:nTÍät
If the task profile type is System Admin, the OfflineAccess task is applied.nTÍät
If the task profile type is Primary Admin, the RemoveBPFInstances, ResetBPFInstances, and ManageEVDREDefaultStyle tasks are applied.nTÍät
The administrator must add the ReOpenBPFStep and PackageExecute tasks to the appropriate task profile.
7.
The ApShell in 7.5 includes the Import SQL or Import SQL into Fact packages that prompt you to enter the SQL database. (In versions 5.1 and 7.0, the prompt was missing.)
To apply the packages, copy the packages from ApShell to your application after upgrading to 7.5. Then modify the package script for your application dimensions.
Copy from:<FileServer>\WebFolders\ApShell\Planning\DataMnager\PackageFiles\Examples
Copy to:<FileServer>\WebFolders\<AppSet>\<App>\DataMnager\PackageFiles\Examples
4 Migrate Application Sets from 7.0
14/24 PUBLIC 2010-11-25
See SAP Note 1355877.
8.
In Planning and Consolidation 7.5, dynamic reports and schedules are provided in EvDRE format. They work in any application. If you want to use new dynamic reports and schedules templates, copy the changed templates from the following location:\\<FileServer>\..\WebFolders\ApShell\Planning\eExcel\Input Schedules (and Reports)\Wizard
For more information about ApShell, see SAP Note 1349656.
9.
If an application set has a custom OLAP partition, you must re-create the partition after restoring the application set (see SAP Note 1395795).
NOTE
The following actions no longer require you to select Process Application when modifying an application (see SAP Note 1284857):!ì,ŠÍQ
Applying the SIGNED_DATA_FORMAT application parameter!ì,ŠÍQ
Applying newly created or modified stored procedures
4 Migrate Application Sets from 7.0
2010-
Please let us know if we are missing any steps here.
Best Regards,
Kannan.M

Answer 1

Hi Raoul,
1. Your understanding is correct.
I dont see any big advantage of installing a separate BI system. However, if you have the BPS or BCS components activated in the exisitng BI system, then you wont be able to install BPC. BPC requires EHP to be installed. But this cannot be installed if BPS component is there. So, in that case, you need to consider a new BI system. Apart from that, I dont see any reason for having a new BI system.
2. In terms of migration, there are few things which you can definitely copy without using the migration tool. For example, when you are trying to create a new dimension and its members. The members from MS can be copied into the NW admin console and then the processing can be done to create the requisite structures at backend. Similarly, you can copy the existing reports and input schedules as well. You can even copy the data. You can export the data from the applications in the MS version. Then use the import DM to upload the data flat file into NW.
Hope this helps.