0. Steve Coan VantagePoint Business Solutions
Project Advice to Accelerate Your SAP Business Planning and Consolidation Implementation or Migration Project
Steve Coan
VantagePoint Business Solutions

1. Disclaimer SAP has not endorsed or approved this presentation.
This is information based on my experience, insights, and current information (and somewhat educated opinion) on the current and future state of the SAP offering.

2. In This Session
Practical, field-tested advice on how to implement BPC successfully and retain your sanity
Advice about data integration, validation, and ETL
The latest BPC 10.1 – Classic or Unified
BPC upgrade paths and approaches
BPC version support matrix and horizon

3. What We’ll Cover
Ten preparation tips for a successful BPC implementation
Five tips for identifying the right data granularity for your project
Migration options for moving to BPC 10.0/10.1 NW
Migration options for moving to BPC 10.0 MS
Migrating from EvDRE to EPM Add-In templates
SAP’s support strategy for all BPC versions
Wrap-up

4. Tip 1 — Executive Sponsorship
Is there willingness to provide sufficient resources and funding?
Does the sponsor have authority to make key decisions across functional areas?
Is the sponsor present?
Is the sponsor engaged?

5. Tip 2 — Financial Vision
Is there a clear vision across all stakeholders?
Gain an understanding of desired output expected from each of the stakeholders
Also gain an understanding of the desired input expected from each of the stakeholders

6. Tip 3 — Communication
Do you have an effective form of communication in place for the project?
Is there a shared directory available for project artifacts?
Personal communication is a must
Regular core team status meetings keep the project on track

7. Tip 4 — Clear Requirements
Do you have existing, well documented processes in place?
Have you discussed potential new processes required and their downstream impact?
Your requirements are always wrong

8. Tip 5 — Data
What is the desired level to plan/analyze, and does your actual data support this desired level?
What other metrics are required?

9. Tip 5 — Data (Validation)
Don’t overestimate your knowledge of your own data
Don’t underestimate the time required for data validation
Don’t even think of validating using a mature, custom report in the source against a brand new custom report in BPC
Be patient and expect multiple iterations. Plan on it. Design for it.

10. Tip 6 — Project Team Do you have the right people for the team?
Are they knowledgeable, cooperative, and results-orientated?
Make process owners and subject matter experts available during the whole process
To mitigate risk, spread the work rather then relying only on key people
Make sure extended team members understand their roles

11. Tip 6 — Project Team (cont.)
Do you have your
Business Savvy Technologist
Technology Savvy Business Person
and your ?

12. Tip 7 — Critical Success Factors
CSFs are those few things that must go well for an endeavor to succeed
Have stakeholders identified and agreed on CSFs?
Have you considered ongoing maintenance and support as a CSF?
"Critical success factors are those few things that must go well to ensure success for…an organization, and, therefore, they represent [what] must be given special and continual attention to bring about high performance. CSFs include issues vital to an organization's current operating activities and to its future success.” - Boynlon, A.C., and Zmud, R.W "An Assessment of Critical Success Factors," Sloan Management Review (25:4), pp

13. Tip 8 — Implementation Partner
Have you developed an adequate RFP to assess vendors?
Make arrangements to meet your finalists in person
Find a partner who has done similar projects before. Many times.
Lean on your partner. Avoid the trap of thinking, “We do things differently around here …”

14. Tip 9 — Project Management
Does your organization contain project management skills?
Will the project manager have proper authority over resources?
A good project manager unshackles talented team members to make great deliveries

15. Tip 10 — Change Management
Do you expect a high level of change to your current process?
Gain an understanding of where your highest resistance will come from, and be proactive in selling the change
Source: Spencer Johnson, M.D.

16. What We’ll Cover
Ten preparation tips for a successful BPC implementation
Five tips for identifying the right data granularity for your project
Migration options for moving to BPC 10.0/10.1 NW
Migration options for moving to BPC 10.0 MS
Migrating from EvDRE to EPM Add-In templates
SAP’s support strategy for all BPC versions
Wrap-up

17. Data Tip 1 — Keep the Focus on Required Insights
What types of questions do you want to ask of your data?
Focus on what is required for planning or reporting and not what data is available
More is not always better

18. Data Tip 2 — Minimize Movement, Maximize Visibility
Focus on minimizing the data movement from one system to another
Use drill-through for access to transactional data or a Web- enabled transaction that is already sufficient in another system
HANA can handle large volumes easily, but getting all the data into BPC involves multiple ETL steps and adds overhead, time lag, and complexity to the environment

19. Data Tip 3 — Keep Actuals in Focus
You can’t report data you don’t diligently capture
Plan at the level where comparable actual data is available
Don’t confuse what “is” available with what you “would like to be” available
Example: Planned wiper blade sales for Sedans vs. SUVs
Example: Profitability by Product instead of by Brand or Region
Example: You want to plan how many widgets will sell for installation in cars versus SUV’s. If you don’t have a way to track the final installation target for your widgets, then you could end up assuming that actual=plan.
Example: You want to report profitability for each product, but many costs are regional or brand-specific. It may be better to do brand or regional profitability rather than convey a false idea that costs are recorded to individual products

20. Data Tip 4 — The Right Data for Your Specific Model
Planning models have different requirements from reporting models
A healthy BPC environment has separate models for separate types of data:
Financials and management reporting
Capital Expenditures
Workforce/headcount management
Sales (by customer)
Expenses (by vendors)

21. Data Tip 5 — Remember the Bottom Line
Every bit of data has a cost:
Disk space
Network bandwidth
Performance degradation
Backup and recovery
Interface development
User training
Project management and documentation
Compare value provided vs. additional cost when deciding what data to bring into BPC

22. What We’ll Cover
Ten preparation tips for a successful BPC implementation
Five tips for identifying the right data granularity for your project
Migration options for moving to BPC 10.0/10.1 NW
Migration options for moving to BPC 10.0 MS
Migrating from EvDRE to EPM Add-In templates
SAP’s support strategy for all BPC versions
Wrap-up

23. BPC 10.1 NW Classic vs. Unified
Feature
Classic Model
Unified Model
Data Modeling
Single Key Figure
Protected Namespace
Multi-Key Figure
Full EDW access
Transact Data
All transactional records must be copied into BPC namespace
Transactional records can be sourced directly from the host EDW
Master Data
Must be copied into BPC namespace
Cannot use compound master data
Master data from the host EDW can be utilized
Can use compounded master data definitions
SQL Push Down to HANA
Technically possible with a BAdI
Capability is delivered functionality
Cell locking
Last in wins
First in wins
Source: SAP Platform Solution Group

24. BPC 10.1 NW Classic vs. Unified (cont.)
Feature
Classic Model
Unified Model
Calcs
Script logic (no current plans to execute directly on HANA)
HANA Optimized functions: dimension member formulas, top down planning using HANA, allocations using HANA
FOX Formula logic – many functions capable to execute directly in HANA
HANA Optimized functions: Copy, Repost, Revaluation, Delete, Deletion of Invalid Combinations, Set Key Figure Values, Distribution by Reference Data, Generate Combinations, repost on basis of Characteristic Relationship, Distribution with Keys, and Formula (many restrictions)
Consol
Full function consolidation
Minimal consolidation functionality – more capability on current roadmap
Source: SAP Platform Solution Group

25. BPC 10.1 NW Classic vs. Unified (cont.)
Feature
Classic Model
Unified Model
EPM Add-In
Direct access to BPC model and data
EPM Add-In supported functions available:
Drill thru
Disaggregation model selection
Disaggregation
Requires a BEx query acting as a data provider to support EPM Add-In
Drill thru (on future roadmap)
Disaggregation (on future roadmap), workaround available today through BEx or planning function
User Interface
EPM Add-In and Web
EPM Add-In (via BEx query), Analysis for MS Office, BEx, and Web
Source: SAP Platform Solution Group

26. Migrating to BPC 10.1 NW Re-implement BPC 10.0 NW PAK BW-IP
BPC 10.1 Classic
BPC 10.1 Unified
Re-implement

27. Migrating to Classic BPC 10.0/10.1 NW
Classic BPC NW Migration Paths
7.0 > 7.5 > 10.0 > 10.1
7.0 > 7.5 > 10.1 
(Optional) BW Accelerator (BWA)
7.0 > 7.2

28. Migration Information in the PAM
Prerequisites and dependencies are in the Product Availability Matrix (PAM)
BPC Version
Official Product Name
7.5 MS
SBOP PC 7.5 FOR MICROSOFT
10.0 MS
SBOP PC 10.0 FOR MICROSOFT
7.5 NW
SBOP PC 7.5 FOR SAP NW
10.0 NW
SBOP PC 10.0 FOR SAP NW
10.1 NW
SAP PC 10.1 FOR SAP NW (includes Classic and Unified)

29. Migration Steps to Classic BPC 10.0/10.1
First, migrate software components
Migrate to BW 7.3 or 7.4 (in-place or system copy)
Migrate to BWA 7.2 (optional)
Execute the migration program
7.5 to 10.0 tcode: SE38, program: UJT_MIGRATE_75_TO_10
7.5 to 10.1 tcode: SE38, program: UJT_MIGRATE_75_TO_101
10.0 to 10.1 tcode: SE38, program: UJT_MIGRATE_100_TO_101

30. Migration Steps to Classic BPC 10.0/10.1 (cont.)
Next, migrate customer data and features
Upgrade security from Active Directory or CMS to SAP BW user accounts
Create SAP BW user accounts
Assign security roles and authorizations to the new user accounts
Create a tab-delimited mapping file for use by the migration program to map old users to new users
Deal with problems and unforeseen issues
Migrate features that are not supported by the mapping program (coming slides)
Regression test and validate
Old User (Active Directory)
New User (NetWeaver)
<Domain>\<AD User ID>
<ABAP User_ID>

31. Migration Utility for BPC 7.5 NW to 10.0 NW

32. Migration Utility Parameters

33. BPC Features That Migrate from 7.5 NW to 10.0 NW
Objects, Tasks, Processes
Migrated
Administrative settings
 yes
Applications > Models
Dimensions
Terminology adjustments for new naming conventions
User IDs
Owner and reviewer properties of the dimensions
Security: teams, task profiles, data access profiles, assignments
Journals
Business rules
Validation rules > controls

34. BPC Features That Migrate from 7.5 NW to 10.0 NW (cont.)
Objects, Tasks, Processes
Migrated
Data Manager features, including process chains, script logic, prompts, and all other features
 yes
Content Library
Business Process Flows (BPFs)
Log files from the Data Manager
 no
Live Reports (these are required to be rebuilt in the workspace area of the new version)
Custom web pages and reports (these need to be rebuilt using the new web reporting and input template features)
SAP BusinessObjects Dashboards (Xcelsius)

35. Viable Migration Options for Classic BPC 10.x NW
In-Place
Option 2
Copy
Option 3
Clean Slate
Direct migration on your current system. Migrate BW first, then BPC
The entire system is copied and then migrated
Perform a fresh installation of SAP BW 7.3+ and BPC 10.x Run UJBR to transfer data
Pros:
Straightforward
Technical upgrade, little or no reimplementation
No additional hardware or system requirements
Production not affected
Most controlled and manageable
Clean
Cons
Disruptive
BW and BPC systems are completely unavailable
Exacerbated if problems cause delays
Issues in current environment may be propagated
Requires full installation and configuration of all servers, dependencies, prerequisites, and customizations

36. What We’ll Cover
Ten preparation tips for a successful BPC implementation
Five tips for identifying the right data granularity for your project
Migration options for moving to BPC 10.0/10.1 NW
Migration options for moving to BPC 10.0 MS
Migrating from EvDRE to EPM Add-In templates
SAP’s support strategy for all BPC versions
Wrap-up

37. Migrating to BPC 10.0 MICROSOFT
Migration on the Microsoft platform is different:
No server software migration program — BPC is uninstalled and reinstalled with the new version
Migrating an Appset (7.5) to an Environment (10.0) is accomplished using BPC Server Manager on the Application Server

38. Migration Steps to BPC 10.0 MS
Migration from BPC 7.x to 10.x MICROSOFT
Server Software Migration
Uninstall BPC 7.x
Install BPC 10.0 on the Application Server
Data Migration
Restore the 7.x APPSET backup
Migrate the 7.x APPSET to a 10.0 ENVIRONMENT
Review the Migration Log
Deal with problems and unforeseen issues
Migrate features that are not supported by the mapping program (coming slides)
Regression test and validate

39. BPC Features That Migrate from 7.x MS to 10.0 MS
Objects, Tasks, Processes
Migrated
Fact table data and comments
 yes
Administrative settings
Applications > Models
Dimensions
Terminology adjustments for new naming conventions
User IDs
Owner and reviewer properties of the dimensions
Security: teams, task profiles, data access profiles, assignments
Journals
Business rules

40. BPC Features That Migrate from 7.x MS to 10.0 MS (cont.)
Objects, Tasks, Processes
Migrated
Data Manager package lists and settings, script logic, prompts, and all other features
 yes
Content Library
Business Process Flows (BPFs), but some have been removed/changed
Published Books
Log files from the Data Manager
Stored procedures and other custom SQL objects
Live Reports (these are required to be rebuilt in the workspace area of the new version)
 no
Custom Data Manager Packages (any package with an SAP BPC task); standard packages (Copy, Move, Admin_Optimize) can be copied from EnvironmentShell to each Model

41. BPC 10.0 MS Server Manager

42. BPC 10.0 MS Server Manager (cont.)

43. BPC 10.0 MS Server Manager (cont.)

44. BPC 10.0 MS Migration Log

45. What We’ll Cover
Ten preparation tips for a successful BPC implementation
Five tips for identifying the right data granularity for your project
Migration options for moving to BPC 10.0/10.1 NW
Migration options for moving to BPC 10.0 MS
Migrating from EvDRE to EPM Add-In templates
SAP’s support strategy for all BPC versions
Wrap-up

46. A Word on EvDRE > EPM Add-In Report Migration
Don’t worry

47. EvDRE Support in the EPM Add-In
EvDRE performs very well in the EPM Add-In
There is a very short list of EvDRE features and EV functions that are not supported in BPC 10.0
Notable:
Insert Member functionality
EvHNV()
EvMNU()
MNU macros (e.g., MNU_eTools_Expand)
Refactoring and testing converted templates can be a time sink

48. Legacy EvDRE Report Migration Strategy
If you have in-house EvDRE expertise:
Train your organization on the new report writer
Migrate the 7.x Appset to 10.x
Identify all mission critical report and input templates
Regression test these EvDRE templates
Remediate as required
Create all new reports and input schedules using the EPM report writer
Do all ad hoc reporting with the new EPM report writer
As proficiency increases and schedule allows, migrate the legacy EvDRE templates

49. Legacy EvDRE Report Migration Strategy (cont.)
If you DO NOT have in-house EvDRE expertise:
Train your organization on the new report writer
Migrate the 7.x Appset to 10.x
Identify all mission critical report and input templates
Regression test these EvDRE templates
Decision point:
Remediate the EvDRE template, then migrate it with the migration tool, or
Recreate from scratch using the new EPM report writer
Create new reports and input schedules using the EPM report writer
Do all ad hoc reporting with the new EPM report writer

50. What We’ll Cover
Ten preparation tips for a successful BPC implementation
Five tips for identifying the right data granularity for your project
Migration options for moving to BPC 10.0/10.1 NW
Migration options for moving to BPC 10.0 MS
Migrating from EvDRE to EPM Add-In templates
SAP’s support strategy for all BPC versions
Wrap-up

51. SAP’s Support Strategy for All BPC Versions
GA*
EOMM**
Location
Migration < From
Calculations
10.1 NW Unified
Jun, 2014
12/31/2020
EDW
BW Integrated Planning (BW-IP), Planning Application Kit (PAK)
FOX, HANA Optimized functions
10.1 NW Classic
/CPMB/
BPC 10.0
BPC Advanced Logic, BAdI
10.0 NW
Apr, 2012
BPC 7.5 NW < BPC 7.0 NW
7.5 NW
Aug, 2010
12/31/2017
BPC 7.0 NW
7.0 NW
Apr, 2009
3/31/2016
N/A
10.0 M
Feb, 2012
Any SQL instance
BPC 7.0 M, BPC 7.5 M
BPC Advanced Logic, Stored Procedures
7.5 M
Dec, 2009
BPC 7.0 M
7.0 M
Aug, 2008
*Generally Available
**End of Mainstream Maintenance

52. What We’ll Cover
Ten preparation tips for a successful BPC implementation
Five tips for identifying the right data granularity for your project
Migration options for moving to BPC 10.0/10.1 NW
Migration options for moving to BPC 10.0 MS
Migrating from EvDRE to EPM Add-In templates
SAP’s support strategy for all BPC versions
Wrap-up

53. Return on Investment
It goes to 11, doesn’t it?

54. Please remember to complete your session evaluation
How to contact me:
Steve Coan
Please remember to complete your session evaluation

55. Disclaimer
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies. Wellesley Information Services is neither owned nor controlled by SAP SE.