Migration to BPC 10.

1
Dear All,

As we know BPC 10.1 is going to be released very soon.

BPC 10.1 has two environment types

1. Classic (inherited from BPC 10.0)

2. Unified (based EDW data model)

Note :Environments with both types can co-exist on the same BPC System

This Documentation is for Migration from BPC NW versions to BPC 10.1(Unified and Classic)

1 BPC 7.5 NW–> BPC 10.1NW Classic ONLY

2 BPC 10.0 NW–> BPC 10.1 Classic ONLY
3 BPC 10.0 NW–> BPC 10.1NW BPC/PAK only
4 BW-IP/PAK–> BPC 10.1 BPC/PAK only
5 BPC 7.5/10.0 NW–> BPC 10.1 Classic and PAK Unified Mixed
1 BPC 7.5 NW–> BPC 10.1NW Classic ONLY

* Backup environment from BPC 7.5NW and restore to BPC 10.1 NW (Optional, only for two box upgrade
scenario).

* Run Migrate program UJT_MIGRATE_75_TO_101 to migrate environment to be 10.1 ready.

* Manual adjust task profiles for new tasks and different task granularity between 7.5 and 10.1

* Migrate 7.5 EVDRE reports to 10.1 EPM Add-in reports.

* Adapt Badi implementations and other customer ABAP codes with new internal APIs of 10.1

2 BPC 10.0 NW–> BPC 10.1 Classic ONLY

* Backup environment from BPC 10.0NW and restore to BPC 10.1 NW (Optional, only for two box upgrade
scenario).

* Run Migrate program UJT_MIGRATE_75_TO_101(migrate resources used to store in BUI Layer to 10.1
web repository)

3 BPC 10.0 NW–> BPC 10.1NW BPC/PAK only

* Backup environment from BPC 10.0NW and restore to BPC 10.1 NW (Optional, only for two box upgrade
scenario).

* There is no existing tool can migrate BPC 10.0NW environment to 10.1 PAK Unified automatically
Following area need to manually rebuilt:

* Create EDW Model or use existing EDW model inside BW and Create 10.1 unified environment in BPC

* Move master data and transaction data via BW Tools

* Create teams and do other security setting and assignment in NW backend.

* Set work status and move work status locking data from 10.1 to 10.1 unified tables

* Enable data audit, data audit logs from 10.1 cannot be moved to 10.1 unified

* Set up BPF Templates, existing BPC Instance from 10.0 cannot move to 10.1 unified.

* Build FOX script to replace BPC Logic script

* Build up planning function in BW

* Build BEx Queries

* Build EPM Add-in/Web reports/Input forms based on BEx Queries

* Implement BW-PAK Badi

Below featured are not available in BPC 10.1 PAK unified

* Comment

* Activity Audit

* Data Manager

* Consolidation (Control, Journal, Business rules, control and consolidation monitor)

* Member formula.

4 BW-IP/PAK–> BPC 10.1 BPC/PAK only

* Set up BPC Environment/Model on top of existing EDW model in BW

* Add User/team attribute of work status and BPF

* Create BPF template and start BPF Instance

* Enable work status if needed

* Enable data audit if needed

* Create new reports with EPM add-in or web client based on existing BEx Query
5 BPC 7.5/10.0 NW–> BPC 10.1 Classic and PAK Unified Mixed

* For customers use both BPC Classic and PAK Unified with 10.1

* Migrate BPC 7.5/10.0 NW to BPC 10.1 Classic as mentioned with upgrade path 1 and 2.

* Create planning scenario in BPC PAK Unified or migrate existing BW-IP/PAK EDW model to BPC PAK
unified as

described with upgrade path 4.

* Set up data communication between BPC Classic and BPC PAK unified according to business requirements.

SAP BPC Net Weaver Edition 10 is what every customer has been waiting for in this
popular tool. Bringing the BPC planning cubes into the BW environment and the Integrated
Planning option for BPC 10.1 are, by themselves, reason enough to perform the upgrade.
Having your actual and plan data in the same environment allows for the most flexible
reporting and planning scenarios. Upgrade today by contacting ATCG Solutions.
Meanwhile, enjoy reading through the 10 main steps involved in upgrading from BPC NW
7.5 to BPC NW 10.0.

Backend Migration

Step 1: Full Backup of BPC 7.5 application sets using UJBR

Step 2: If the BW environment is greater than or equal to 7.3 go to step 3. Otherwise, you will need
to upgrade BW to v7.3 using the Software Update Manager (SUM).

 Option 1: Add BPC components to upgrade queue and skip step 3

 Option 2: Perform BPC component upgrade separately from BW 7.3 upgrade

Step 3: Upgrade BPC components.

Step 4: Restore BPC Application Sets

Step 5: Run program “UJT_MIGRATE_75_TO_10” in order to complete backend migration

For BW on HANA scenario:

Step 6: Run program “BPC_HANA_MIGRATE_FROM_10”

Step 7: If using BADI’s, update/incorporate latest API changes to your code.

Now for the meat, the content!

Frontend Migration

Step 8: Use conversion tool for existing reports and quick win

Step 9A: Migrate to the new Report Definition concept to maximize performance and functionality.

Step 9B: Analyze existing content for any usage of deprecated functions and migrate to newest
versions.

How To Determine the Level of Effort for Content Migration

Prior to starting the technical upgrade steps above, you should do a full analysis of your existing
content (reports/templates). Any content containing deprecated functions should be documented in a
migration plan and then updated during the clean-up phase.