22 October 2015

Lars Johansen
Consultant Manager, EPM Planning & Consolidation

Best Practices SAP BPC

 itelligence at a glance

2
2 01.07.2015 itelligence proposal to Sanistål
 itelligence nordic|Offices
Kuala
Lumpur

Stockholm

Oslo

 itelligence Nordic
 Turnover: 2014: MEUR 49.6
 Employees (FTE): 2015: 295 (2014: 260)
 Full service provider – Hosting, installation,
implementation, go-live support, project
management, AMS
 Business Analytics
 Strong Nordic delivery focus
 60+ dedicates consultants
 Technologies
Horsens
Aarhus
Copenhagen

3 10/22/2015 © itelligence
 Business Analytics
 Planning and forecasting
 Financial and operational
solutions
 Paradigms and processes
(driver-based planning,
etc.)
 Migrations
 Consolidation
 Legal and management
consolidation
 IFRS, XBRL and Disclosure
Management
 Fast close processes
 Migrations
4 © itelligence
 Business Intelligence
 KPI’s and business insight
 Reporting and visualization
 IoT
 Data quality
 Mobility
 BI strategy and roadmaps
 Information Management
 Data warehousing
 In-memory
 Big data
 Architecture / landscapes
 Roadmaps
 Governance
itelligence Nordic – selected SAP BPC references
 6

Agenda

1. Considerations to do before, during and after a SAP BPC

implementation
2. What’s the latest news within SAP BPC and what can we expect going
forward?

© 2015 itelligence
10/22/2015
Considerations

© 2015 itelligence
Before, during and after implementation

10/22/2015
 8

Before implementation

 Think holistic when designing the model requirements

 As-is processes vs. to-be processes
 Financial vs. non-financial data
 Planning vs. consolidation
 Data collection vs. reporting
 Strategic vs. operational planning

 Establish project organization and identify stakeholders

 Identify the key persons in your organization, who can contribute to the project
 Finance
 IT (and basis)
 Project manager
 Project owner
 Steering committee
 Reference group
 Remove or mitigate project constraints and ensure resource availability

© 2015 itelligence
 Ensure Management buy-in on the project

10/22/2015
 9

Before implementation

 Agree on responsibilities between IT and business

IT responsibilities Business user responsibilities

 Hardware  Hierarchies and structures
 Security and authorization  Reports
 Users  Excel, Word, PowerPoint
 Roles  Input schedules
 Privileges  Excel, Word, PowerPoint
 Data and application structure  Create and monitor business processes
 Database server
 Application server
 Integration
 OLAP structure

© 2015 itelligence
Self-service financial reporting ensure all users can create information and insight when needed
Wizard driven interface simplify the creation of content and administrative processes

10/22/2015
 10

Before implementation

 Assign super users before project start-up

 Financial administrator
 Super users
 Educate financial administrator and super users as soon as possible
 Make sure the core project team has enough knowledge of the project scope and tool used before project start-up
 Ask for tool training, either by SAP or by the implementation partner

 Identify project risks and mitigate actions

 Typical project risks
 Lack of management focus and decision readiness
 Data quality – historical data
 Resource availability / Threat of go-live deadline
 Project scope creep
 Technical issues

 Evaluate and find implementation partner

© 2015 itelligence
 Ensure to find a partner with proven record within SAP BPC implementations
 Ensure the partner has enough resources available – do not rely on a single person
 Ensure the consultants used are experienced consultants and experienced SAP BPC consultants

 Ask for estimate, including internal resources and roles required during implementation

10/22/2015
 11

During implementation

 Consider using prototyping as implementation method

 SAP BPC is a very flexible tool
 Consider using prototyping as a method during the implementation
 It is our experience that companies better adopt SAP BPC on their own structure and data
 Prototyping is offering this possibility and this approach has been used with success on numerous projects

 Make sure the consultant always conduct a unit test before handing over the elements to you for testing

 Use implementation partner best practice models for acceleration of project

 Implement solutions based on best practices obtained by SAP and gained through comprehensive
project experience by your implementation partner
 E.g. for consolidation itelligence recommends to use “itelligence best practice” for consolidation. itelligence best practice
method consist of 4 steps: Prepare, Intercompany, Collect and Consolidate

 Establish integration to masterdata and hierarchies if as soon as possible, if within scope

 To avoid rework, make sure you have the correct masterdata and hierarchies available for development

© 2015 itelligence
10/22/2015
During implementation

 Participate active in the project

 Make sure you participate in the implementation
 It is of highest importance that project members gain a deep knowledge of the tools used in the process
as well as an understanding of the implementation considerations made during the project
 To ensure you implement a “customer solution” it is important you now and then have access to
reference groups/end-users. These users will furthermore be trained in the solution as part of the
participation

 Knowledge transfer is key to ongoing success

 Knowledge transfer and anchoring of the solution are key focus areas
 Ensure high involvement thru out the implementation high involvement of the customer project
members
 Make it a mission to ensure that you are consultant independent when the implementation is finalized
 Leverage as much as possible of all tasks yourselves with close guidance and quality assurance in
combination with specific training activities by your implementation partner
After implementation

 User acceptance test

 Do not accept the system before a full user acceptance test is conducted
 Do not considered the system delivered before the user acceptance test has been conducted and
approved within the agreed thresholds

 Hand-over process
 Ensuring a solid anchoring in the business is a key to successful implementations
 Ensure the implementation partner hand-over the system and the documentation – and spend the time
to do this
 Train the end-users and provide them with hands-out (end-user guidelines)
 Agree on go-live support from the implementation partner
 Ensure access to the relevant internal key persons in the first critical go-live months

 Agree on support level by implementation partner

 Even the best projects require support after go-live
 Make sure you have an agreement with your implementation partner that fits your need
 Assign critical periods and ensure the relevant consultants are reachable
After implementation

 Evaluate solution
 Evaluate the implemented solution, e.g. with your implementation partner, after the first process
 Identify “room for improvement” and evaluate whether changes must be implemented
News and what‘s next

© 2015 itelligence
what can we expect going forward?

10/22/2015
 16

SAP | Solutions supporting planning

BW IP Analytical SAP BPC 10.1

Planning Applications Standard

Business
Intelligence EPM

SAP BPC 10.1

Embedded
On HANA

Data Information
warehousing management

ERP
 17

BPC | 10.1 Standard

 Stand alone EPM on any DB

 Business Process Flow
 Work status
 Standard file upload functionality
 Consolidation
 BPC10.1 - mobile interface
 18

BPC | BPC 10.1 Embedded

 IP as the core for development

 Key figure based
 No Consolidation
 BPC10.1 - mobile interface
 User interface
 EPM (BPC)
 BOBJ
 Analysis for office
 Design studio
 Roadmap Embedded
 Comments
 Consolidation
 Business rules, journals
 Drill through
 Admin authorization
 19

BPC | Roadmap

 Roadmap (extract)
 Consolidation in Embedded planning
 Deeper integration between standard and embedded
 Real-time data access
 Extended capabilities in Design Studio and Analysis for Office
 Improved collaboration between process flows, work status and comments
 Change Distribution (break-back) method on web report
 Short comment on web report
 Excel Client : Continuous Improvement for Embedded Model
 Full effect of SAP HANA
 Customer specific Web UI extensions
 20

SAP Simple Finance | In a brief

 21

SAP Simple Finance | In a brief

 22

SAP Simple Finance | In a brief

 23

SAP Simple Finance | Impact on planning

 Impact on forecasting
 Better, faster and more reliant forecast
 It’s now possible to do financial closing along with forecasting processes
 Rolling forecast (“always open forecasts”) easily handled
 Updated access to actual/plan variances
 E.g. combined with updated time/price variances
 What-if scenarios on latest development
 Reduce accruals / “last minute booking” issues
 Seamless update of data, structures and hierarchies
 Always reliable data and structures
 Remove next day time lag
 No redundant data across models and/or environments
 Impact on planning
 Faster activity based planning
 24

SAP Cloud for Planning | In a brief

 25

SAP Cloud for Planning | Impact on planning

 A new product
 Yet to show its footprint in the market
 Primarily for larger enterprises
 Is there a place for the product in the Nordic market?
 Close link to SAP BPC
 Will this be the silver bullet for a market entry?
 No on premise cloud
 Is the Nordic market ready for that?
Lars Johansen
Consultant Manager, EPM Planning & Consolidation
phone: +45 2543 8896

© 2015 itelligence
e-mail: Lars.Johansen@itelligence.dk

We make the most of SAP® solutions!

10/22/2015
 27

Copyright itelligence AG - All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of itelligence AG. The information
contained herein may be changed without prior notice.
Some software products marketed by itelligence AG and its distributors contain proprietary software components of other software vendors. All product and service
names mentioned and associated logos displayed are the trademarks of their respective companies. Data contained in this document serves informational purposes
only. National product specifications may vary.
The information in this document is proprietary to itelligence. This document is a preliminary version and not subject to your license agreement or any other
agreement with itelligence. This document contains only intended strategies, developments and product functionalities and is not intended to be binding upon
itelligence to any particular course of business, product strategy, and/or development. itelligence assumes no responsibility for errors or omissions in this document.
itelligence does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is
provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular
purpose, or non-infringement.
itelligence shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use
of these materials. This limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. itelligence has no control over the information that you may access through the use of
hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web
pages.

© 2015 itelligence
10/22/2015