SAP BPC

Business Blueprint Document

Document Control

DOCUMENT INFROMATION

Title SAP BPC Business Blue Print Document

Project Phase

Author Bpc.kiran@gmail.com

File Name

Created on

Last Edited on

Reviewed by

REVISION HISTORY

Date Version Author Comments

Deliverable Acceptance
Purpose
The Blueprint Acceptance Forms ensures that the Blueprint deliverable(s) requirements and expectations of the
deliverable(s) is met, approved and accepted.

Project Identification

Project Name Project Type

Customer Name Planned Start/Finish

<Client> Project Manager SAP Project Manager

EPM Product Identification

EPM Product Name

<Client> Team Members <Client> Lead

SAP Team Members SAP Team Lead

BBP Sign-off
<Client> Track Lead Sign-off
Name:

Sign-off Date:
Signature:

<Client> Project Manager Sign-off

Name:

Sign-off Date:
Signature:

SAP Track Lead Sign-off

Name:

Sign-off Date:
Signature:

SAP Project Manager Sign-off

Name:

Sign-off Date:
Signature:
Table of Content
TABLE OF CONTENT ............................................................................................................................................ 5

1) INTRODUCTION – <CLIENT NAME> ............................................................................................................... 7

2) KEY BUSINESS PROCESSES ......................................................................................................................... 7

2.1 KEY PROCESS STEPS ..................................................................................................................................... 7

2.2 BUSINESS PROCESS FLOW CHART ............................................................................................................. 7

2.3 BUSINESS PROCESS DESCRIPTION ............................................................................................................. 8

2.3.1 <ONE SECTION FOR EACH BUSINESS PROCESS OR SUB-PROCESS> ........................................ 8

2.3.2 <ONE SECTION FOR EACH BUSINESS PROCESS OR SUB-PROCESS> ........................................ 8

2.3.3 ….. ........................................................................................................................................................... 8

3) DETAILED BPC DESIGN .................................................................................................................................. 8

3.1 <ONE SECTION FOR EACH SUB-PROCESS> ............................................................................................... 8

3.1.1 ENVIRONMENT ID .................................................................................................................................. 8

3.1.2 MODEL ID ............................................................................................................................................... 9

3.1.3 DIMENSIONS .......................................................................................................................................... 9

3.1.4 DIMENSION MEMBERS ......................................................................................................................... 9

3.1.5 DATA COLLECTION .............................................................................................................................. 9

3.1.6 CALCULATIONS .................................................................................................................................... 9

3.1.7 INPUT SCHEDULES ............................................................................................................................... 9

3.1.8 REPORTS.............................................................................................................................................. 10

3.1.9 WORK STATUS .................................................................................................................................... 10

3.1.10 BUSINESS PROCESS FLOWS (OPTIONAL)...................................................................................... 10

3.1.11 SECURITY ............................................................................................................................................. 10

4) SYSTEM CONFIGURATION CONSIDERATIONS.......................................................................................... 10

5) DESCRIPTION OF FUNCTIONAL DEFICITS ................................................................................................. 11

6) APPROACH TO COVERING FUNCTIONAL DEFICITS ................................................................................. 11

7) NOTES ON FURTHER IMPROVEMENTS ...................................................................................................... 11

8) CONSIDERATIONS ON EXTERNAL INTERFACES ...................................................................................... 11

9) MASTER DATA CONSIDERATIONS .............................................................................................................. 12

10) CONSIDERATIONS ON INTEGRATION POINTS ............................................................................... 12

11) REPORTING CONSIDERATIONS ........................................................................................................ 12

12) SUGGESTIONS FOR TESTING – FUNCTIONAL/SYSTEM ................................................................ 12

1) INTRODUCTION – <CLIENT NAME>

<Describe here the company business, stake holders and establishment>

2) KEY BUSINESS PROCESSES

2.1 KEY PROCESS STEPS

<In this section, briefly list and describe the main steps of the business processes
described in this BBP document. For ex: Annual Operating Plan, Strategic Planning and
Rolling forecast>

2.2 BUSINESS PROCESS FLOW CHART

< Include in this section any appropriate chart describing the business process flow. For ex:
Finance overall planning end to end process>
<Sample VSD template attached for the reference>

BBP BPC VSD

TEMPLATE.vsd

<Sample VSD Screen shot for the reference>

 2.3 BUSINESS PROCESS DESCRIPTION

2.3.1 <ONE SECTION FOR EACH BUSINESS PROCESS OR SUB-

PROCESS>

<Describe here the to-be business process or sub-process in full detail explaining how the
process will work for Client from a solution and standpoint (system and non-system steps)
with emphasis on the system solution approach. If relevant, you may also include diagrams
describing the standard SAP solution.>

<You may also include in this section any additional document or table which will help in the
understanding of the to-be solution (e.g. customer provided charts, detailed requirement
documents). Please note that embedded objects will not open in the BBP document once in
PDF format.>

2.3.2 <ONE SECTION FOR EACH BUSINESS PROCESS OR SUB-

PROCESS>
<Describe here the sub – process in detail. For ex: Revenue Planning 2.3.2, Opex Planning
2.3.3…>

2.3.3 …..

3) DETAILED BPC DESIGN

<Describe here the BPC to-be solution for each sub-process in full detail explaining how the
Environment, Model, Dimension etc. will work for Client from a solution and standpoint with
emphasis on the system solution approach.>

3.1 <ONE SECTION FOR EACH SUB-PROCESS>

3.1.1 ENVIRONMENT ID
<Describe here the BPC to-be Environment ID and Description of the Environment>
Environment ID Description
3.1.2 MODEL ID
<Describe here the BPC MODEL ID and Description of the Particular Scenario. Explain
periodic or YTD Model>

Model ID Description Measure Model Type

3.1.3 DIMENSIONS
<Describe here the Dimension list used in MODEL, Secured Dimensions in the model and
Shared Dimensions in the Environment>
Dimension ID Description Dimension Type Secured Shared

3.1.4 DIMENSION MEMBERS

<Describe here the Dimension significance in the Model and whether dimension members
maintained manually or loaded from the BW. List out the properties in the Dimension here>

3.1.5 DATA COLLECTION

<Describe here how the actual data is flowing from ECC to BW and BW to BPC. Also explain
how the BW staging layer helps BPC to load the data. Explain the conversion and
transformation of the actual data>

3.1.6 CALCULATIONS
<Describe here how the planning calculations are managed. What are the calculations
developed using BADIs, What are the calculations developed using Script Logic and
Dimension Member Formula>

3.1.7 INPUT SCHEDULES

<Describe here the input schedules used to capture the planning data. You may also include
in this section excel layout of the input schedule or table which will help in the understanding
of the to-be Solution>
3.1.8 REPORTS
<Describe here the Reports used to capture the planning data. You may also include in this
section excel layout of the Report or table which will help in the understanding of the to-be
Solution>

3.1.9 WORK STATUS

<Describe here the how to lock data once approved by client. You may also include in this
section work states and controlled by understanding of the to-be Solution>

3.1.10 BUSINESS PROCESS FLOWS (OPTIONAL)

<Describe here the logical sequence of business planning execution steps. You may also
include in this activities, workspaces, Hyperlinks, performer and reviewer details for the to-be
solution>

3.1.11 SECURITY

<How will Client manage security in this area? Describe high-level authorization
requirements. Also, make sure the team is aware of system functions and get the process
owners thinking about how to control access to SAP BPC and its data.>

<You may list all the user roles considered for deployment in this business process/scenario
using the table below>

User Org/Fun/Department Category Access Entity Access

1

4) SYSTEM CONFIGURATION CONSIDERATIONS

<Address any issues of importance to Client as they pertain to the configuration of the
system. Provide a description of the configuration steps required to implement the
business process or scenario in SAP as well as links to any relevant detailed
documentation.>
5) DESCRIPTION OF FUNCTIONAL DEFICITS
<Detail any real or perceived gaps in system functions that have become evident through
the business process review sessions. "None are apparent at this time" is appropriate
when there appears to be a good fit for Client’s needs.>

For each functional deficit defined, mention the alternative solutions possible, which might
include coverage of the deficit to a certain extent, or by allowing change in business
process or by defining a workaround solution.

Ref. # Functional Deficit Description Potential Alternate

1

6) APPROACH TO COVERING FUNCTIONAL DEFICITS

<Address real or perceived gaps in system functions including workarounds, BADI’s and
BW developments, If a fix is not evident, the impact on the project must be clear so the
team can decide how best to proceed. Provide a list of links to relevant functional and
technical specifications documents.>

For each deficit define in detail on how it can be covered. Identify the category (e.g. BADI,
BW Development or another SAP Application)

Ref. # How to cover the Deficit Deficit Category Priority

1

7) NOTES ON FURTHER IMPROVEMENTS

<Describe potential or future improvements in this section, for example issues that will be
covered in a future SAP BPC release or project phase. If an issue has been raised in the
process review but is out of scope for the current project, this is the place to note the
topic.>

8) CONSIDERATIONS ON EXTERNAL INTERFACES

<Address any issues of importance to Client as they potentially have an impact on the
interfaces to and from SAP BPC. No need for exhaustive detail but be sure to address any
issues that were raised during the review sessions. Provide a list of links to relevant
functional and technical specifications documents.>
9) MASTER DATA CONSIDERATIONS

<Address any issues of importance to Client as they pertain to master data and data
conversion. If relevant, list the main Dimensions used in the process or scenario,
indicating which ones are considered for data conversion. No need for exhaustive detail
but be sure to address any issues that were raised during the review sessions. If
applicable, provide a list of links to relevant functional and technical specifications
documents.>

10) CONSIDERATIONS ON INTEGRATION POINTS

<Address any issues of importance to Client as they potentially have an impact on the
integration with other SAP modules. Issues related to other projects potentially impacting
the project should also be covered. No need for exhaustive detail but be sure to cover all
dependencies and raised issues.>

11) REPORTING CONSIDERATIONS

<Address any issues of importance to Client as they relate to reporting. No need for
exhaustive detail but be sure to address any issues that were raised during the review
sessions. Provide a list of all SAP BPC reports that will be used in the business process
and identify the need for additional report creation. Provide links to relevant functional and
technical specifications documents.>

<You may list all the reports considered for deployment in this business process/scenario
using the table below. Also include the reports considered for custom development.>

Ref. Description of Report Model Report Name

# Requirements
1
2

12) SUGGESTIONS FOR TESTING – FUNCTIONAL/SYSTEM

<Identify potential test scenarios, mainly describing specific situations raised during the
review sessions. As well, any prerequisites required for testing should be identified in this
section (e.g. data preparation, environment readiness, testing report performance, etc.) >