TZBPC1 - 98 Aug 21 2014 Lessons and Labs

1
2
3
4
Before BPC came along we had Business Planning and Simulation (BPS) in the
1990s and Integrated Planning(IP) in 2006 when BW 3.5 came out.
Both of those toolsets featured good BW integration since they used standard BW
Info Objects and InfoCubes. BPS however had its own gui and web user interfaces
and that meant users also had to learn how to use the BW reporting toolsets to do
analysis.
So IP came along and solved the issue of multiple user interfaces by allowing users
to plan in the BEx Analyzer and in the Web Application Designer templates.
5
We have master data and actual transaction data flowing into BW from ECC and
possibly other external systems. Both the BW master data and transaction data (in
the InfoCube) are using BW standard naming convention. (i.e. delivered objects start
with a number and custom objects start with a letter.)
The standard InfoCube could of course be used to report on actuals. The real time
InfoCube gets actual data from the standard InfoCube in this example. Master data
is joined to the InfoCubes via primary and foreign key relationships. In the IP
planning modeler we configure data slices, characteristic relationships and
aggregation levels etc. for an IP planning scenario.
The aggregation level becomes the InfoProvider for the planning enabled query
which can then be used in a BEx Workbook, Analysis for Office, or Web Application
templates.
One of the issues with IP however was that IT had to do most of the setup and there
wasnt a good way to manage the planning process.
6
Originally the product was only offered on the Microsoft platform in version 5.1. The
Microsoft platform did not change very much up until 10.0 when the adobe flex web
client was added for end user activities and the EPM add-in for office became
available. The Microsoft platform will not have a 10.1 version although it will continue
to be enhanced in service pack updates. For example, the web client will be
upgraded to HTML5 to support mobility.
BPC first became available for the NetWeaver platform in version 7.0 using BPC
named InfoObjects and InfoCubes which also have only one key figure.
In version 7.5 there was quite a bit of effort working out the kinks in 7.0 and work
done to better integrate with BW ETL processes for example. In version 10.0, the
user interfaces were re-worked for netweaver as well the new adobe flex web
client not only for end users but also the administrators and the new EPM add-in for
Office.
And then, in June of 2014, 10.1 for NetWeaver became generally available with two
solutions: Embedded and Standard.
PAK is the in memory planning program which allows SAP HANA optimized
execution of IP planning functions.
7
Just like IP, we have actuals coming into a standard InfoCube. In the BPC Web
Client, when BPC models and dimensions are created, the real time InfoCube and
corresponding master data (characteristics) are using the BPC namespace and the
InfoCube only has one key figure.
The BPC Model is then used for planning and reporting for example in the EPM Add-
in or in web reports and input forms. In the lower part of the figure you will find a nice
listing of everything you can do in the web client such as working in the library to
configuring drill through.
8
HTML5 Web Client: faster, good for mobility
Web reports / input forms: new report builder screen, better select member feature,
comments in 1st column
Data access profiles can now be built on properties
Optimization: for BPC on HANA the InfoCube only has one fact table and one
dimension table so only Lite optimization is needed now to compress the data and
trigger a HANA memory update
Large Key Figure supports 24 characters before the decimal pt. and 7 after; normal
is 13 and 7
9
Seeking more of a business centric solution, SAP acquired Outlooksoft in 2007.
Things have changed quite a bit since then.
Since 2007 BPC has caught on quite well going from 700 to over 5,000 customers.
If you ask me why BPC has grown so much since 2007 I would say its because it is
easy to use, it is process oriented, and it is unified.
BPC is used in 10-20 different industries including banking, consumer goods, and
energy companies.
In general BPC is used for three things:
1.Planning
2.Consolidations
3.Reporting
60% of all customers use it for planning with 40% for consolidation i.e. month end
close. All customers use it for reporting and analysis. Companies who use BPC for
planning(i.e. planning budgeting and forecasting) use it mainly for expense and
revenue product planning but there many other examples such as HR, projects, and
cash flow planning.
10
Two separate platforms
11
ECC on a separate data base too
12
13
In the past couple of years, Analytics technology has evolved to a great extent to
help business and best run companies transform the way they run business
reporting and planning - that is business sensitive, dynamic and REAL. We have
seen many CFOs questioning the very basics of reporting, budgeting and thinking
beyond budgeting. This has seen several new use cases and requirements popping
up for reporting and planning.
This has become more demanding, as many best run companies that have already
solved the basic problem of getting the right data for monthly reporting used for
forward planning, are moving into defining a more transformational way of running
their reporting and budgeting/planning processes.
Consequently, planning technologies have been rated as the highest priority in
analytics by CFOs for 2013, from a Gartner survey with CFOs.
14
15
16
So how does 10.1 solve these issues - by storing methods and data in one place, using a central process on one system, and using HANA to give us all the data we
need when we need it.
17
18
Note: Account and Key Figure based InfoCubes
Account based InfoCubes only have a few(or one) key figures so they must rely on
accounts to identify what the data means. In this case the key figure is nothing more
than a data column.
Key Figure based InfoCubes can have many key figures and they have a business
meaning such as revenue, cost of goods sold etc.
19
In order to achieve most of the items mentioned earlier, BPC has essentially been
merged with integrated planning and thus the name Embedded. 10.1 includes two
solutions in the same system, Embedded and Standard BPC (in 10.1) is essentially
the same as 10.0 except it uses the new HTML5 web client.
BW-IP 7.0 could only use an rdbms. As of BW7.3 IP could also be run in memory by
using the planning application kit (PAK). PAK is the in-memory planning program
which allows SAP HANA optimized execution of IP planning functions.
As of BW-IP 7.4 planning objects can be used in BPC Embedded along with BPC
Embedded features including BPFs, work status, data audit and data access profiles.
Correspondingly, as of BPC10.0 BPC can also be run on HANA using the HANABPC
software component. In 10.1, BPC10.0 is referred to as Standard.
In addition, Standard and Embedded are on the same platform and both are
included in one license.
20
As a result now we have a completely integrated all in one solution with a common
architecture and direct access to ERP master data and actuals.
21
Since both BW and ECC sit on HANA there is going to be less data redundancy. In
figure the OLTP box represents ECC and the concept is that the ABAP Planning
Manager can access ECC data via aggregation levels on Composite Providers.
22
Just as in IP, the real time InfoCube uses BW namespace and there is an
aggregation level and planning enabled query.
When it comes to web reports/input forms and the EPM Add-in they are accessed by
selecting the query and the model. The query is the touch point back to IP and the
Model brings in BPC functionality such as data audit, data profiles, and work status
23
24
25
26
In summary, we have discussed the history of SAP planning solutions, the reasons
why BPC is so popular, the planning issues which gave rise to 10.1 Embedded, how
BPC and IP became Embedded and their architecture.
27
28
In the first use case, the customer is using IP with PAK turned on. That means they
already have the performance of HANA but they need the BPC features in
embedded including data audit, work status, BPFs, data profiles, and comments.
They also only need planning and not consolidation (consolidation wont be available
in embedded until 2015).
The recommendation is therefore to go with Embedded.
In order to use Embedded they will need to purchase the new SKU.
Since, all of the BW and IP components can continue to be used in existing planning
applications you can use a phased approach when converting to Embedded planning
applications.
The actual conversion will involve some design and set-up to use the BPC features
as well as in BW security.
Maybe the biggest conversion item effort wise would be the creation of new excel
workbooks in the EPM add-in but this can be done in phases. I dont expect many to
go with Analysis since it cant use the BPC features.
29
The next use case are existing BPS customers. These folks will most likely not be on
HANA so they will be looking for the performance boost from HANA as well as the
BPC planning features of embedded.
Again, the recommendation is embedded.
In order to use Embedded they will need to purchase the new SKU.
Like with IP, a phased approach can be used. Also, the existing BW Info Objects,
Info Cubes, and MultiProviders can be used without any changes.
The actual conversion will involve some design and set-up of the IP planning objects
since they are completely different from BPS. Also, there will be some design and
set-up to use the BPC features as well as in BW security.
Again, the biggest conversion item effort wise would be the creation of new excel
workbooks in the EPM add-in but this can be done in a phased approach. If you
choose to go with Analysis it cant use the BPC features.
30
Our next use case involves existing BPC 7.x NW customers. Since they cannot use
HANA with 7.x they are in for a big performance boost if they decide to go with
HANA in 10.0. Also, the web client and EPM add-in compared to 7.x have more
features and are easier to work with so users can be more productive.
The recommendation is therefore Standard.
There is a program to migrate from 7.5 to 10.1.
The consolidation functionality changed quite a bit from 7.x vs 10.1 since journals
are entirely in the web UI now vs in Excel before and we now have consolidation
central in the web client as well. Also, controls have been re-built from the ground up
they replaced data validation.
EVDRE templates can also be migrated however I would expect them to be entirely
re-built eventually since only simple EVDREs can me migrated and even if they are
migrated, there are left over areas in the workbooks that dont look so great.
The 10.1 web client is completely new in this case, therefore the 7.x Live reports
would need to re-built.
31
Our next use case involves existing BPC 10.0 NW customers not on HANA. Why
would a 10.0 customer want to upgrade in this case? The performance from HANA
will be up there at the top and also the web client provides mobility and efficiency. If
the custom however had low data volumes and did not use the web client that much
then they probably shouldnt upgrade is doesnt make sense to switch just for the
sale of being on the latest version unless it has a feature you need. In case however,
lets say that they need go mobile.
The recommendation would therefore be Standard.
The functionality is basically the same but the web client is based on HTML5 vs.
adobe flex.
There is a program to migrate from 10.0 to 10.1.
32
What if we have a customer new to BPC and they want major business ownership?
Then Standard is the recommendation.
The business manages the models and dimensions from the BPC web client as well
as most of the BPC planning features. They would not need IT to build BW or IP
objects.
In excel, the business users can use the data manager to do some light ETL work
and to run packages for planning.
IT would still take care of the heavy ETL work in BW and complex script logic for
example.
Also, if the customer doesnt have the data volumes to justify HANA, then standard
is the only option since Embedded requires HANA.
33
What about a new BPC customer where EDW BW integration is top priority? Then
Embedded is the way to go.
IT would build the BW and IP objects as well as the BW authorizations for example.
The business could then manage the models from the BPC web client as well as the
BPC planning features.
IT would also take care of all the ETL work in BW just like normal.
34
And then of course they will be a few cases where both Embedded and Standard will
be used at the same time. For example, we have a customer using both IP and
BPC10.0.
They can migrate into 10.1 with very little disruption to their current planning and
reporting activities.
Version 10.1 may help them with the integration to some extent since both solutions
are on the same platform and it will definitely get them closer in terms of features
since Embedded includes some of the key BPC features weve talked about.
Of course, they will still have some BW ETL work to do when it comes to sharing
data between Embedded and Standard models due to the naming differences of the
InfoObjects. This requires mapping in a BW transformation between the BPC
Standard InfoObject and the BPC Embedded InfoObject.
If they dont actually to move data between InfoCubes they can always run EPM
reports where they include from both an Embedded model and Standard model
simultaneously.
35
36
37
Landing Page shows all administration objects as part of an Environment
Enhanced Dimension Management User Interface
Support for multi-select for mass operations saves time
Context sensitive Action Toolbar displays actions you can perform on selected objects
Ability to sort by Dimension Name or Dimension Type makes it faster and easier to manage dimensions
Improved App Management Screen

Mass Maintenance Option
Mouse over provides detailed information for better understanding of the individual applications purpose
Controls replace former Validation business rules. They can be activated for any type of model (consolidation, budgeting).
In the administration console, the Controls home page provides an overview of all existing controls per model.
38
EPM Unwired is available for both 10.0 an 10.1. Although it does not use the Fiore
platform it does have a Fiori UX design.
You install the EPM Unwired application on your iPad by downloading the application
directly from the iTunes app store to your device. There are how to papers for both
10.0 and 10.1.
39
40
41
- Standard model can do this as well, needs HANA though
48
49
HANA is not required to plan on DSOs.
50
BW 7.4 sp8 is required.
Comments in Embedded is not currently planned for the Web interface.
51
There is customizing view in SM30 for table RSADMINCV4 called BEx Values which
sets the value for the field RRXDATANOTEXIST in table RSADMINC. This can also
be overwritten by a rsadmin parameter RSR_FORMAT_NOP_VALEXCP if it does
not fit the NO2 needs as value.
Price planning is supported for BW7.4 sp7 and greater.
52
53
54
55
56
57
58
59
10
61
2
63
Basically the purpose of SAP HANA is to enable easy storage and efficient
processing of huge amounts of data.
Using in-memory hardware and software, you can manage data at massive scale,
analyze it at amazing speed, and give the business instant access to real time
transactional data.
SAP HANA combines in-memory and columnar data storage which means the data
is in RAM and can be processed in parallel for example. Like a lot of new solutions
they evolve quite a bit especially early on. Initially (2011), HANA was delivered as a
sidecar to provide in-memory ECC data with the ECC rdbms still in place. BW on
HANA was delivered in 2012 as the Primary Persistence solution i.e. BW no longer
had an rdbms, all of the data is in HANA. HANA as a Platform is not only for BW
data but also other applications including ECC as part of the SAP Business Suite.
64
The master and transaction data in HANA is stored in tables. That data can then be
consumed in Information Models where the data is transformed into a more
meaningful data set. For example, we join customer ids with region and then link the
transaction data to the customer ids. The information models are constructed by
using view in HANA. There are three main types of views:
1.Attribute View-this represents the master data.
2.Analytic View this is like and InfoCube, it joins the attributes to the fact table.
3.Calculation View this is like a MultiProvider, it is used to union data from multiple
sources.
65
With HANA in general you have a multi processor approach, a large memory and a
low memory latency.
Technological advances have led the way for HANA. Multi-core CPUs (multiple
CPUs on one chip or in one package) are standard, and extremely fast
communication between processor cores enables parallel processing. Also, main
memory is no longer a limited resource. In order to give you a feel for the capability
of HANA, lets take a look at the numbers: (of course these are subject to change)
1.There can be up to 10 cores per CPU
2.There can be up to 8 CPUs per board
3.If you have a 4 board/node server
4.Then, 10 x 8 x 4 = 320 cores in a 4 board i.e. node set-up which provides 4
terabytes of RAM
Row Store
Traditional Relational Database, system has to jump from second value 10 to fifth
value 35 and so on if you report the key figure.
Column Store
The data is stored in columns. A jump from value 10 to 35 is not necessary. This is
what makes HANA very fast.
Example:
Key Figure 1 Key Figure 2
GER 10 20
FR 20 30
USA 45 50
Planning function Revaluation revaluates key figure 1.

Row Store: GER, 10, 20, Fr, 20,30,USA,45,50.
Column Store: GER,FR,USA,10,20,45,20,30,50.
In addition, when you put BW on HANA, the InfoCube structure changes
dramatically. Before HANA, InfoCubes had 2 fact tables and several dimension
tables thereby forming a star schema designed to speed up read performance in an
rdbms.
With HANA, the InfoCube is flattened out so that it only has one fact table and just
one dimension table to keep track of request id processing. Also, you can continue to
use the related MultiProviders, queries, and process chains which means that HANA
can be installed with minimal changes to existing objects. In addition, the rdbms
activities such as rollups and compression are no longer necessary since the data is
now in memory i.e. lower cost of maintenance
73
Here you can see the different parts of the planning model and the various steps that are
necessary for building a simple planning application using BI Integrated Planning.
STEP 1: Create a real-time InfoCube in the Data Warehousing Workbench.
STEP 2: Create an aggregation level using the planning modeler or the planning wizard.
STEP 3: Build the input-ready query on top of the aggregation level.
STEP 4. Use the same input-ready query to create a planning application in the Excel environment
(BEx Analyzer) or in the Web environment (BEx Web Application Designer)
75
With the current solution, the local cache, delta buffer, constraints and the
aggregation engine are part of the application layer. If we want to perform planning
on the data or manipulate it using planning functions, we need to move a large
volume of data from the database to the application layer. This is very costly in terms
of performance.
76
With the help of this approach, we now have a bigger data base layer and a smaller
application layer.
The User Interface Layer is the EPM Excel add-in or the BPC web reports/input
forms. The Application Layer reads in data via the BEx Query along with some
Metadata and the Plan Session data which is locked data in the user buffer. With the
planning functions being run on the data base notice that all of the large data flows
are in the Database Layer where the data is saved into RAM.
77
This is an example of how we reduce the data traffic.
The planner enters a change of 50 which is the disaggregated into 52 weeks x 500
products or 26,000 combinations. Traditionally, the calculation would be performed in
the application layer and then all 26,000 records would be sent to the database but
will HANA the instruction is sent to the database where the calculation occurs
thereby saving the input/output processing.
78
79
The Planning applications kit combines the feature-rich capabilities of BW-IP with the
superior performance of SAP HANA and therefore PAK includes a new infrastructure
for HANA-optimized data management.
PAK is based on components of BW-IP plus new functionality and technology, and is
optimized for in-memory planning with HANA as the database. Customers can very
easily migrate their existing BW-IP configuration to PAK.
The Deep HANA Integration Active setting enables Embedded model for BPC.
81
82
83
AAO Analysis for Office
SAP BusinessObjects Analysis, edition for Microsoft Office is an Excel reporting and
Planning user interface. It is the premium alternative to the BEx Analyzer and can be
used for planning enabled queries.
84
85
86
87
88
The following features in BPC Standard run on the SAP HANA calculation engine:
- Measures
- Dimension Member Formulas
- Allocation Script Logic
- All data reads i.e.., Reporting
- Disaggregation
HANA revision 64 is required to leverage HANA MDX.

Pre-requisite: Environment level HANA accelerator ACCELERATOR_ON is set to X
in IMG.
Set model level setting ENABLE_HANA_MDX to X in IMG. Go to transaction
SPRO -> SAP Reference IMG -> Planning and Consolidation -> Configuration
Parameters -> Set Model Parameters HANA MDX support CANNOT be switched on
if a Model:
Has extra info-provider attached to multi-provider(created by BPC)
Has any member formula, custom measure or script defined with MDX functions
which are NOT supported by HANA MDX syntax.
89
90
10
92
93
2
95
In the top layer we have the EPM Add-in, the HTML5 web browser, Planning
Applications such as ERP, and Analysis for Office.
1. CLASSIC MODEL CONNECTION this is a web services connection used for Standard
BPC
2. FIREFLY this is a homegrown type of connection for an embedded model
Between the first and second layer are three connection types:
1. REST the representation state transfer is used for Standard BPC
2. INA this stands for Information Access and is used for Embedded connections
3. BICS this is the BI Consumer Services connection type used in Analysis for
Office
In the middle of the diagram, youll notice the classic(i.e. Standard) planning
components powered by HANA or another data base. In the SAP BW box are all of
the new software components for the embedded planning components and so forth.
In the lower area of the diagram xDB refers to the fact that BPC Standard could use
an RDBMS. In the HANA box, the ERP Virtual Model represents HANA views on
ECC data, the Planning Engine is referring to IP planning activities and BPC
Planning Functions are referring to Standard BPC activities such as work status,
data audit, and currency translation that are running on HANA.
96
1. Library is the default view of home page. The UI of Library is similar to that of
BPC 10.0.
2. My Activities is the entrance to BPF functions. for reminding purpose, it displays
a bubble immediately after user logon with how many tasks the user needs to
process.
3. Consolidation is the entrance to all consolidation features.
4. Administration is same as before
5. System Reports is the new name for Audit in BPC 10.0.
6. Documents is same as before.
There are only four icons in Embedded environment in this release: Library, My
Activities, Administration, and System Reports
97
98
99
100
Processes and activities are displayed in the same page when My Activities icon is
clicked
Clicking Process Monitor will open a separate page to monitor processes
Clicking each activity will open a separate page to perform the tasks in the activity
101
Clicking any link in the page will open a separated new page
Consolidation is not available in Embedded environment
102
Manage All Environment is removed from Administration; Environment List is the
only entrance to manage all environments
Model and Dimension Defaults is the new name of Context Default
Differences in Embedded environment of this release:

Modeling: cannot edit dimension (edit dimension structure, dimension member and
hierarchy)
Security: can only manage teams
BPF, Workstatus and Audit are supported
No business rules
No journal, drill-through, model and dimension defaults, and document type
103
System Reports is the new name for Audit in BPC 10.0.
Audit is reserved for Data Changes and Administration Activity only to reflect the
original meaning of the term audit.
System reports in Embedded environment of this release:

BPF: instance, activity
Audit: data changes
Other: work status
104
Tag is the new name of sub-type
Multiple tags are allowed
The way of filtering document by context is changed. We allow user to narrow filter
results step by step by specifying criteria further and further. For example, you select
model Planning, then all documents whose model is planning are displayed; after
that, if you select 2014.TOTAL, then immediately only matching documents remain
on the screen.
105
106
Please refer to the two sample files we delivered together with our program.
Where to find the sample files and where to put your customized files:
1.Logon to NW system
2.Open transaction SE80
3.Click Repository Browser, select BSP Application, and type in bpcwebclient,
type enter key
Sample files are

1.Page Fragments/themes/bas/customer_sample.css
2.Page Fragments/customize_sample.json
Customized files should be located and named as

1.Page Fragments/WebContent/themes/bas/customer.css
2.Page Fragments/customize.json
107
In BPC 10.1, we support following browsers
On PC: IE9 (with limitation), IE10, Firefox
On iPad: Safari
108
Thanks to HTML5 and JavaScript technologies, we achieved significant logon
performance improvement, which is not possible with Flex technology we used in
BPC 10.0.
109
We developed our own OLAP data grid with HTML5 technology. By rendering only
the visible area in the report, the time to display (to parse and render) the result from
backend is constant, no matter the report is tiny small or extra large. This is not
possible with Flex technology we used in BPC 10.0.
110
10
112
2
114
115
The only difference between report and input form is the data input function.
116
117
118
119
1. We grouped file related operations into one menu to save space and to avoid
confusion with data operations
2. Less menu items in Comments menu. Cell related comment operations, such as
view history, edit and delete comment, are now moved to the context menu of the
data cell.
3. We grouped display related operations into another menu
120
121
122
Context Options is new in BPC 10.1, where report designer can manage context in a
single place.
1.Report designer can define how dimension is displayed and the display in context
options will immediately reflect the change
2.Report designer can decide which dimensions are relevant in the report and should
be displayed in context bar
3.Report designer can lock a dimension in the context to disable dimension member
change by business users. Also new in BPC 10.1.
123
In BPC 10.0, you can change the file type in edit mode. BPC 10.1 has no edit mode
and you can only change the file type by save as.
124
The new design of web report/input form
1.File name is displayed on the left corner of menu bar
2.Report description is displayed on the top center of the report
3.Context bar is displayed closer to data grid
4.Click the pen to edit the report layout directly. It opens the Define Data Grid dialog
you see in slide 7.
5.Excel-like row and column number are displayed
6.Dimension is displayed as a link. You can click to open member selector to change
members of the dimension.
7.Dimension name and dimension members are in same line in column header.
People can easily tell that Plan and Target are members of Category dimension.
125
126
127
128
129
The only difference between report and input form is the data input function.
130
In current release, available query list is not filtered by the model you select, or by
the environment you logged on. All the queries in the system you have access to are
displayed.
You can search by technical name or description. Search is suggested if you know
part of the query name or description.
History is the default view.
It might take some time to list all queries if you have many of them.
You can always do sorting or filtering to quickly find your query.
131
Variable should be set before opening the query.
You have to set the required variable before clicking next button.
You can change variable setting after report creation.
Please refer to limitation note 1916315 for details of variable limitations.
132
133
134
135
136
137
1. Including variable, not supported in Standard reporting; member selector
differences (query based vs. dimension based)
2. Transfer, rollback, submit, cell lock not supported in Standard reporting
3. Context options, context lock not supported in Embedded reporting
4. Scaling, decimal places, parent after/before not supported in Embedded
reporting
5. Drill-through not supported in Embedded reporting
6. Cell comment and inline comment not supported in Embedded reporting
7. Page axis with multiple member selection not supported in Standard reporting
8. Workspace/Book/Dashboard not supported in Embedded reporting
9. select children, select base, select descendant not supported in Embedded
reporting
138
10
140
141
2
2
144
145
146
147
148
149
150
151
152
For example, you can define formulas that use the functions of the transformation
library for the transformation. Basic functions (like and, if, less than, greater
than), various functions for character chains (like displaying values in uppercase),
date functions (like calculating the quarter from the date), mathematical functions
(like division, exponential functions) are offered for defining formulas.
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
Definition
Real-time InfoCubes differ from standard InfoCubes in their ability to support parallel write
accesses. Standard InfoCubes are technically optimized for read accesses to the detriment
of write accesses.
Use
Real-time InfoCubes are used when plan data is entered during BW-integrated planning.
169
170
171
172
10
174
175
2
Modeling in the Planning Modeler
In the planning modeler, you edit the following objects of the planning model:
Aggregation levels
To determine the level on which data can be entered or changed (manually through user input or automatically by a planning
function), you define an InfoCube of type aggregation level. An Aggregation Level consists of a subset of the
characteristics and key figures of a MultiProvider or real-time InfoCube. Real-time InfoCubes are used to store data.
Characteristic Relationships
You use characteristic relationships to model semantic relationships between characteristics (such as product group and
product). In this way you check, for example, whether a particular combination of characteristics can be generated (if this
combination is permitted) or whether a cell is input ready. Characteristic relationships are created for an InfoCube.
Data Slices
You use data slices to globally protect whole areas of data against changes (for example, current values or historic values).
Planning Functions
Planning functions allow system-based processing or generation of data. The BW-BPS function types are provided as
standard. Functions can be executed immediately (using the pushbutton) or in the background as a planning sequence.
You can also define your own function types.
Planning Sequences
A planning sequence is a sequence of planning functions and manual input templates that are executed sequentially. You can
also schedule planning sequences to be processed in the background as a step in a process chain.
Filters
A filter describes a section of a dataset that is processed, for example, in a query or a planning function. (For example,
calendar year 2004 2005, customer group XY).
Variables
Variables can be used in the filter for selecting characteristic values that can be parameterized, or to parameterize planning
functions or planning sequences.
ABAP based Planning Modeler:
There are two different possibilities for using the ABAP Modeler.
BW Adminstration Workbench (Transactioncode: RSA1)
The Modeler is embedded into the Adminstration Workbench. This version allows the administrator
of the planning application the creation and maintenance of the different planning models in one
common UI and it is no longer necessary to jump between two different User Interfaces.
Integration in the SAP menu: SAP Easy Access Menu Business Planning and Simulation
BW-integrierte Planung (Transaction code RSPLAN).
The Transaction Code RSA1 allows a more guided and limited navigation through the planning
model. The end user sees only the selected objects.
1.INFOPROVDER in this screen you maintain characteristic relationships, data slices and select
planning sequences that need to be executed when data is saved.
2. AGGREGATION LEVEL the aggregation level forms a conceptual slice of the real time InfoCube
for a planning scenario and it owns other planning objects. They can be created against real time
InfoCubes, MultiProviders, and local providers.
3.FILTERS Filters are used primarily to define the data region for planning functions bundled into
planning sequences.
4. PLANNING FUNCTIONS these are used to perform mass updates in planning scenarios such as
copying actual to plan, deletions, and calculating revenue for example.
5.PLANNING SEQUENCES these are used for testing and for bundling planning functions to be
executed in real time or in batch mode
CENTRAL SETTINGS this is where I can select a planning sequence to be executed when data is
saved and set a key date for time dependent master data.
CHARACTERISTIC RELATIONSHIPS these are used to provide valid characteristic combinations when
planning and also to perform derivations
DATA SLICE this is used to lock a data region to prevent data changes when a process has been
completed. BPC embedded work status creates data slices automatically therefore we dont need
to create them here.
AGGREGATION LEVEL the aggregation level forms a conceptual slice of the real time InfoCube for a
planning scenario and it owns other planning objects. They can be created against real time
InfoCubes, MultiProviders, and local providers.
Filters are used primarily to define the data region for planning functions bundled into planning
sequences
Input Ready Query: One of the main features of any planning system is the ability to perform
manual input planning in excel workbooks. In our case this means the EPM excel add-in. To be
able to do this we need a planning enabled query.
Planning enabled queries must be created on an aggregation level and not the real time InfoCube.
Using MultiProvders allows for modelling changes
Planning sequences are used to bundle planning functions in a group so they can be executed
sequentially. They are also used to do testing and debugging in the planning modeler.
Planning sequences can be executed the following 3 ways:
On demand: In the planning sequence screen of the planning modeler or the Excel data processing
tab.
In batch mode: Use a BW process chain with the Execute Planning Sequence process type.
As data is saved: Include the planning sequence in the planning modeler Info Provider screen
Central Settings tab.
10
190
191
2
193
The planning functions that are the easiest to use are the predefined planning
functions. They can be set up and maintained by simply entering the required
information in the planning modeler (by entering a target in a copy function for
example). These planning function provide a defined behavior that can only be
influenced within the limits set by the Customizing options.
Fox Formulas can be used to create more powerful planning functions. As they
provide certain functionality that is usually only provided by programming languages
(such as loop statements or if statements) they can be used to cover a wider range
of business requirements than the predefined planning functions. On the other hand,
they are more complex, as the processing logic has to be defined when creating the
planning function.
Customer-defined planning functions are created using ABAP. They therefore offer
the functionality of a full-blown programming language. This type of planning function
is definitely the most complex, but also the most flexible.
In a typical planning scenario, there is a need for a wide range of automatic functions
to change or create plans. BW Planning offers different types of planning functions
that can be used to create all necessary automatic functions: Predefined Planning
Functions: a set of planning functions with fixed behavior that can be easily set up.
Whenever a planning function cannot be achieved using a pre-defined planning
function type, you can use Fox Formulas to create your own planning functions. With
Fox Formulas, BI Planning provides a toolkit for creating simple calculations (such as
a volume times price calculation) as well as a simple to use yet very flexible and
powerful tool for complex formulas. No programming (ABAP, Java, etc.) is necessary
when using Fox Formulas.
Above you can see some examples for planning functions that can be created using
Fox Formulas.
When a planning function cannot be achieved using one of the predefined types or a
Fox Formula, you can create your own type of planning function (using ABAP).
These types of planning functions can have their own screen in Customizing in the
planning modeler and can be reused throughout the system.
198
A planning function can (potentially) use two types of plan data: The data to be changed by the
planning function and the data that the planning function uses as additional information upon
execution. We call the first set of data transaction data and the latter reference data.
Transaction data: A planning function can only change data that is stored in a real-time InfoCube. The
logical level of aggregation of the data records is defined by the aggregation level (in the planning
modeler) upon which the planning function is defined. The transaction data is locked upon execution
of the planning function. The selection of the actual data can be restricted in various ways, depending
on the mode of execution:
A filter defined in the planning modeler can be used in all front ends (when executing a planning
function via a button in a Web application or an Excel Workbook), in the planning modeler, and in
the planning sequences.
The result of a query can be used for filtering via data binding in the web and the Excel
Workbooks.
If the planning function contains conditions, they are used to further restrict the data selection.
Note: The definition of the planning function and of the data selection (filter or query) must match. You
cannot change data that is not contained in the data selection. This means for example that you
cannot copy data into a planning version that is not contained in the filter/query used for the planning
function.
Reference data: The system determines which reference data is necessary from the set up of the
planning function itself. Reference data is not locked when the planning function is executed. Any
InfoCube can be used for reference data. Using a MultiProvider therefore, BI Planning can also
access reference data from Data Store objects for example.
Example: You want to copy data from one version to another, say from version 0 to version 1. Version
0 does not need to be in the filter/query, and the system automatically reads the data in version 0 as
reference data. Version 1 must be contained in the filter/query when executing the planning function
and will be locked.
When you execute a planning function, the changed data is written to the plan buffer. The data is only
transferred to the InfoCube if the user actively saves the data.
200
The first thing you do when creating a planning function is choose the type of
planning function and the aggregation level that the planning function is defined on.
In our example, we want to copy data from an actual InfoCube to a real-time plan
InfoCube.
In each planning function, you have to specify which characteristic values in the data
records are to be changed by the planning function. If we copy from one version to
another and one InfoProvider to another, the characteristics version and InfoProvider
have to be indicated as characteristics that are to be changed.
Conditions can be used to define which actions the planning function performs,
depending on which set of data is actually being changed. In the example above, no
conditions are used. We will go more into detail however when creating planning
function type revaluate.
InfoCube.
InfoCube.
205
We now want to create a revaluation function. Again, we need to select the
corresponding aggregation level and enter a name and a description for the planning
function.
We will revaluate the data that we have copied from the actuals InfoCube into the
plan InfoCube. As we are only working on a single InfoCube, we do not need a
planning level on the MultiProvider containing both InfoCubes but will use one
restricted to our plan InfoCube.
209
When creating a delete function, only key figures are changed. This means once
again that we do not need to specify any characteristics that are to be changed.
As with the other planning functions, you can specify whether you want to delete all
key figures or only individual ones.
Make sure that you run the delete function at the proper level of aggregation. If you
want to make sure that all records in a given selection are deleted, you have to
choose an aggregation level that contains all characteristics.
10
213
2
You can call a function module in fox code that runs hana sql
215
Fox = Formula Extension.
Fox Formulas offer an enhanced formula language for defining planning functions.
In addition to standard mathematical operations and functions, Fox offers:
Statements for accessing data records
Methods for information retrieval (e.g. variable values)
Predefined business functions (e.g. linear digression)
Loop statements:
Different types of Foreach loops
Do loops.
Programming variables
String operations
Calling external (ABAP) function modules.
A formula editor is available that provides help functionality, check functionality,
patterns, and examples.
BW-BPS uses the same Formula syntax. All new features in formulas in BI
Integrated Planning are also available in BW-BPS and all features in formulas that
were available in BW-BPS are now available in BI Integrated Planning.
There are several new loop statements.
In addition to the standard do loop, you can also use the statement do n times where n is a
natural number. You therefore no longer need to create a counter that checks the number of
executions of the do loop.
There are several flavors of the foreach statement. In order to clarify how the statements
work, let us assume that we are looping over the characteristic 0COUNTRY and we are
using the variable COUNTRY:
Foreach COUNTRY: The loop goes through all characteristic values for 0COUNTRY
contained in the (existing!) records in the current block (for blocks see below). In each
loop, the variable COUNTRY is replaced by the one of these values.
Foreach COUNTRY in Refdata: The formula determines the reference data from the
right sides of the statements of the formula. The system then goes through all the values
of 0COUNTRY in the reference data and replaces COUNTRY in each loop accordingly.
Foreach COUNTRY in Selection: The system reads the selection (from the filter for
example) for 0COUNTRY and goes through all characteristic values in this selection.
The execution of the formula does not depend on which records exist or which records
are contained in the current block.
Foreach COUNTRY in Variable: This version behaves similarly to the one above. The
characteristic values for the country are not read from the selection but from the
specified variable.
You can now call ABAP function modules from formulas. The interface of the function
module cannot contain any structured data type such as structures or tables. Simple
data types are supported.
223
224
225
If you need to speed up your characteristic relationship processing you can use
HANA SQLScript as a node (processing step) in calculation scenarios. You can
leverage the Application Programming Interface TREX_EXT_PE_SQL_SCRIPT.
226
229
230
The settings on the properties tab are as follows:
CLASS: this is the ABAP class that will need your coding.
REFERENCE DATA: do you want the function to use reference data
W ITHOUT BLOCKS: do you want the function to use data blocks. (most do)
PROCESS EMPTY RECORDS: do you want the function to process empty records
HIERARCHY NODES SELECTIONS SUPPORTED: allow the use of hierarchy nodes for
member determination
HIDE COLUMN OF CHARS TO BE CHANGED: dont display the characteristics to be
changed selection
DISPLAY FIRST W HEN CREATING: if selected, the characteristic usage screen appears
first; otherwise the parameter screen appears first when configuring the function in
RSPLAN.
In the PARAMETER tab the PARAMETER TYPES are as follows:
ELEMENTARY: The value of a specific InfoObject, meaning that every elementary
parameter is based on an InfoObject and thus inherits its technical properties. If the
InfoObject is a characteristic, the system automatically uses the master data to
check the authorization of a value entered by the user.
INFOOBJECT OF THE INFOPROVIDER: The name of an InfoObject from the current
InfoProvider (aggregation level). The permissible InfoObjects are defined by means
of the restriction for the InfoObject selection.
DATA SELECTION: Data selection parameters can include the selection criteria of
multiple characteristics as they are required for defining filters. Therefore, this is a
special selection table. The permissible characteristics are defined by the restriction
for the characteristic selection.
STRUCTURE: Parameters can be combined to create a structure. These parameters
then form the components of the structure parameter. If you declare the structure
parameter as a table, the structure then forms the row structure of the resulting
table.
KEY FIGURE SELECTION: This parameter type is for selecting the key figures to be
processed. It is therefore a special case of the type InfoObject.
233
234
10
244
245
2
One of the main features of any planning system is the ability to perform manual
input planning in excel workbooks. In our case this means the EPM excel add-in. To
be able to do this we need a planning enabled query.
Planning enabled queries must be created on an aggregation level and not the real
time InfoCube.
To access the query designer go to your start menu:
Choose All Programs Business Explorer Analyzer In the Add-Ins tab select
Create New Query In the Query Designer choose New Query Select the
aggregation level.
When I create queries for BW reporting scenarios I can always pick and choose
which InfoObjects to include in the query. If I dont need to report by material group I
can simply choose not to include it in the query.
When creating queries for planning however the rules are a little different. In this
case I need to include every InfoObject in the query to allow for manual input
planning. The reason being is that when doing manual planning every cell must
represent single characteristic values. That means that any characteristic that is not
the rows or columns must be included in the filter and restricted to single values.
248
249
Our business requirement calls for the rows to be available for input. Queries
normally only display Characteristic values if they have postings in the InfoProvider.
Of course, since this is a planning scenario and I havent created any data yet we
need to set the characteristics to display based on their master data. To do that just
select FISCAL YEAR/MATERIAL GROUP in the ROWS, go to the properties on the upper
right and in the EXTENDED tab choose MASTER DATA.
250
251
1.NOT INPUT READY(NOT RELEVANT FOR LOCKING) use this to read the data but do
block others from changing it while you are viewing it
2.NOT INPUT READY(RELEVANT FOR LOCKING) use this to read the data but lock it so
no else can change it while you are viewing it
3.INPUT READY(RELEVANT FOR LOCKING) - use this to allow write access and block
others from changing it while you are viewing it or changing it
252
253
254
255
10
257
258
2
260
261
262
263
264
265
In our previous scenario we only used one real time InfoCube but in many cases you will need to
use multiple InfoProviders. For example you might want to store granular actual data in one
InfoProvider and less granular plan data in another. Or you might want to plan on product price
data in one InfoProvider and at the same time plan quantities and revenue in another. We can do
this with a MultiProvider.
In reality, multiproviders should always be used even if only one real time InfoCube is needed
because it provides flexibility for modeling changes such as adding a new InfoProvider or switching
to a different InfoProvider. Therefore, using MultiProviders provides a lower cost of maintenance for
design changes.
In our previous scenario we only used one real time InfoCube but in many cases you will need to
use multiple InfoProviders. For example you might want to store granular actual data in one
InfoProvider and less granular plan data in another. Or you might want to plan on product price
data in one InfoProvider and at the same time plan quantities and revenue in another. We can do
this with a MultiProvider.
In reality, multiproviders should always be used even if only one real time InfoCube is needed
because it provides flexibility for modeling changes such as adding a new InfoProvider or switching
to a different InfoProvider. Therefore, using MultiProviders provides a lower cost of maintenance for
design changes.
270
The main use case for local providers is to provide a quick ad hoc reporting and
planning solution.
Local providers are tables in HANA that can be used without any corresponding BW
InfoObjects so it is potentially a low cost of development alternative that can be
configured without any support from IT.
Local providers are not new with 10.1. They were originally offered as part of BW
Workspaces which are used by IT to provide a small sandbox for business users to
perform ETL activities.
To use a Local Provider in Embedded these are the components used in a typical
planning scenario:
Local InfoProvider
Embedded Model
Aggregation Level (system generated)
Planning Functions
Planning Query
EPM Workbook with an EPM Report and Planning Functions
271
To create the local provider, Ill go to the web client and in the Administration screen
choose InfoProviders Local Providers New Enter in a name and description
Choose Next
In the subsequent UPLOAD DATA FILE step 2 in the slide we need to upload a flat file.
The flat file will be used to derive the structure of the resulting HANA table and to
provide the initial result set.
The flat file needs to have a csv extension.
As you can see in figure there are the normal settings used in flat file loads to
indicate if there is a header row, data separators, decimal indicators and so forth.
272
In step 3 MAP INFOOBJECTS we can turn on data audit to track who made changes
to the data. This causes the system to add audit fields into the HANA table.
In the slide I have selected the QTY and REV as the KEY FIGURES. HANA will create
these as data fields.
In the TYPE column I can select the data type for each field. For characteristics, the
Type options are:
Character String with Leading Zeroes
Date (saved as yyyymmdd)
Time(saved as hhmmss)
InfoObject
If I select InfoObject, I can select a characteristic and also choose whether to use its
conversion routine or not.
For the key figure fields, the Type options are:
Integer
Decimal
Floating Point
273
In step 5, the system displays among other things, the name of the aggregation level
and query that it created automatically. (At the time I am writing this, the query must
be created manually.)
274
We can view the generated aggregation level in RSPLAN. In the slide you can see
the generated field names beginning with @3B. Although they appear under the
InfoObjects folder they do not exist in the normal BW data dictionary but only in
HANA. Just so you know, the aggregation level is considered to be an InfoProvider
and can be viewed in RSA1.
The description W ORKSPACE AGGREGATION LEVEL OF LOCAL PROVIDER serves as a
reminder that local providers first came on the scene as a component of
Workspaces.
You can proceed to create planning functions and sequences on the local
aggregation level at this point.
275
Aside from the price planning feature, plannable DSOs can be used to store comments. This can
be used to record planning assumptions for example as comments in the data base and then other
users can run reports on the comments.
A planning enabled DSO is included in a MultiProvider along with a real time InfoCube. The real
time InfoCube contains the transaction data and the DSO is used to store the comments. The input
form has a separate column for comments and that column is a key figure in the DSO with input
planning enabled.
Composite providers are used for unions just like MultiProviders except Composite Providers can
be maintained by business users in BW Workspaces. Workspaces are easy to use web dynpro
screens where business users can model their own ETL solutions in a controlled environment.
Composite Providers can include a local provider for example and a real time InfoCube to access
global plan data. The aggregation level then becomes the touch point to the ABAP Planning
Manager in IP
A Composite Provider is an InfoProvider that combines data from a Transient Provider,
or SAP HANA views or from other InfoProviders by Join or Union, and makes
this data available for reporting and analysis. Storing the data in the SAP HANA
database ensures faster access to data in the query. There are three different types of
Composite Providers, designed for different user groups and application areas.
1. (Central) Composite Provider (in SAP HANA Studio)
2. Ad hoc Composite Provider (in SAP BW Data Warehousing Workbench)
3. Local Composite Provider(in NetWeaver Business Client- BW Workspace
The use case of a virtual provider would be some planning on none BW cube
source, like transaction data in a DDIC table or even from a file.
279
10
281
282
2
Data audit in concept is the same in Embedded as it is in Standard in that it tracks
who entered transaction data into the InfoCube. In general Standard has more
options because you can turn on data audit by model by category and activity (input
forms, data manager, and journals) whereas Embedded data audit is turned on by
InfoProvider and records all activities by default.
284
When audit is turned on for the InfoCube, a new dimension is generated with four
audit characteristics.
1.AUDIT TIME STAMP this is used to record when the data was saved to the
InfoCube
2.USER-this records who saved the data
3.AUDIT MODE-this records how the data was written into the InfoCube. For manual
input planning and planning functions, PLAN is used. For BW data loads, WHM is
used. If audit is turned off, a value of OFF is used.
4.SOURCE OF DATA- this records the name of the BW query for manual input planning
and the planning functions when they are used. If I use a BW data load for the real
time InfoCube, the SOURCE OF DATA is blank.
285
Since these are additional characteristics in the InfoCube, the fact table therefore will
have a four additional key fields:
1.SID_0ATIMSTMP
2.SID_0AUSER
3.SID_0AMODE
4.SID_0ASOURCE
Those of you with a BW background know that SID stands for surrogate id and is
essentially a pointer to the actual characteristic values. Id also like to remind you
that BW on HANA flattens out the InfoCube so that the characteristic SIDs are
joined directly into the fact table.
The main point is however that when you turn data audit on you are adding an
incredible amount of granularity into the data base and even though we are on HANA
it could affect performance. So Im just mentioning this so you remember to do some
stress testing on this setting before you go live with it.
286
If I want to turn data audit off in the web client, I can just click the CONFIGURATION
FOR: PRICE hyperlink to bring up a simple screen where I can choose a status of ON
or OFF. Since this setting is maintained in the easy to use BPC web client it could
easily be made by more of a business type of user as opposed to IT.
287
288
289
290
291
10
As a little refresher, a BPF is defined as a web-based user interface (UI) that is used
to guide users through a sequence of activities in a process. As you also might
recall, the main reasons to use a BPF are to assist businesses in coordination of
their month end close or planning processes by providing visibility of the progress
being made, guiding users through a series of tasks, and emailing users when they
are expected to perform an activity for example.
293
Integrated Planning customers have been looking for a tool like this for years so
being able to use a BPF in Embedded fills a significant void for them. This is a prime
example of where the 10.1 Best of Both Worlds (BPC and IP) comes into fruition
integrated planning customers can now use a BPC BPF.
294
295
296
IDENTITY DIMENSIONS are used to track the status of the activities. When selecting the
identity dimensions, you can see in that the dimensions are actually characteristics
that belong to the InfoProviders assigned to the models in the environment.
Note: BPF Identity Dimensions
When selecting identity dimensions in Standard you have to select the model and
then the identity dimensions (from that model) whereas in Embedded all dimensions
of all models are available.
Activities can be reopened in Embedded as they can be in Standard however there
is a new setting in Embedded called Check only the current step when reopening.
When the checkbox is selected, the step in the business process flow can be
reopened if the user is the performer or reviewer of the current step. Otherwise, the
user needs to be the performer or reviewer for both the current step and the previous
step to reopen the current step in the business process flow.
297
The driving dimension is used to lookup the owner and reviewer for the activity.
In Standard the owner and reviewer properties are normally part of the entity
dimension. But since Embedded uses normal characteristics, they will not normally
be modified to include owner and reviewer.
Therefore, the Driving Dimension can now either be a characteristic in an
InfoProvider being used in the Embedded environment (Internal) or an independent
characteristic (External) can be used to determine the owner and reviewer.
Material Group must have the same members as the external characteristic
298
PLANNING is the name of the BPF Template, the push button COMPLETE is
available if you want to change the status. The CONTEXT is made up of the identity
dimensions CAL. YEAR 4 SPECIAL PERIODS; K4/2016; and version B. The STATUS is
OPEN-TO PERFORM and the PROCESS MANAGER (owner of the instance) is
determined when creating the instance.
299
300
2
302
303
304
305
306
307
308
309
310
311
Note: Embedded Target Actions
In comparison to Standard, Embedded target actions do not have the option to set a
default member or to use the workspace context for input forms. There are also no
related actions in Embedded.
312
313
314
315
10
317
2
You might recall that Standard has five different activities that it controls: Data
manager, Manual input, Journals, Documents, and Comments but Embedded only
has the category called Manual Input. Manual Input includes manually inputting data
from a web and excel input form and it also pertains to planning functions. For
example if version B1 for 2015 is locked that means that you cannot change the date
either manually or with a planning function.
319
Work states are defined by model in Embedded whereas in Standard they are
defined at the environment level. The CONTROLLED BY setting determines who can
change a work state. If it is set to Owner for example, then only the owner of the US
can change the work status. If it is set to Manager then only the Manager of the US
can change the work status and so on.
In the MANUAL ENTRY column of figure 1.15, a value of ALL for UNLOCKED would
mean that anyone can change the data. Listed below you can see the possible
manual entry values what they control:
ALL Anyone can change the data
OWNER Only the Owner can change the data
MANAGER Only the Manager can change the data
NONE No one can change the data
320
321
322
323
The LOCKING DIMENSIONS are in essence used to record the work status and to
determine the users and teams.
In my example I have configured the four locking dimension fields as follows:
1. OWNER DIMENSION this characteristic is used to lookup the owner or team. It
must have a hierarchy along with an attribute to store the owners and an attribute
to store the teams.
2. HIERARCHY this is the hierarchy being used to derive the manager (i.e. the
owner of a parent node is the manager of the child node)
3. OWNER PROPERTY the W ORK STATUS OWNER is the attribute of the characteristic
(MATERIAL GROUP in this case) being used to lookup the owner
4. TEAM PROPERTY the W ORK STATUS OWNER is the attribute of the characteristic
(MATERIAL GROUP in this case) being used to lookup the team
Since the business requirement is usually to lock data regions made up of version,
time, and the owner dimension I also need to turn work status on for year and
version
324
325
Keeping in mind that an Embedded model can be referenced to more than one
InfoProvider, work status can therefore be set for all InfoProviders in a model or just
for a specific InfoProvider. If I did select SET W ORK STATE BY INFOPROVIDER then I will
need to specify which InfoProvider when I set the work state.
326
327
328
329
In Business Planning and Simulation or IP, the data slice feature is used to lock data
intersections. Now, in Embedded work status is used to lock the data and it uses
the same data slice mechanism.
330
331
When you turn on work status for a model, the system automatically generates a BW
virtual cube that is used to feed the report.
If I go into BW to transaction RSA1 the virtual InfoCube is located in the unassigned
InfoArea.
The virtual cube is using InfoObjects to capture the user, timestamp, version,
material group, year, and the Work Status Order (this is the work state number, for
example approved is number 3).
332
10
334
335
2
337
The BW Query provides the link back to the IP objects and the data base connection while the
Embedded model is used to pull in the data audit, data profile, and work status settings.
The BW Query represents a repository of fields to pick from kind of like a Business Objects
Universe so when you create queries for BPC Embedded you should try to include most if not all of
the InfoObjects in the underlying InfoProvider. Of course, if the query is on an aggregation level
then all InfoObjects should be included as a rule to allow manual input planning.
Ssas , BW, ODBO (MDX)=Reporting only ,no input
WS = Input & reporting
We support all this sources
This RKT will focused on Firefly connector/BW BI IP cubes for reporting and
There is a new connection type: SAP BW (INA Provider). This new connection type
is required for Embedded. INA stands for information access. This new connection
type provides the following services:
1. Work with BW queries with or without variables.
2. Retrieve data using EPM reports
3. Enter and save data, using input forms
4. Execute IP planning functions using data processes
Here are the definitions of the parameters:
CONNECTION NAME enter a name of your choice or use the Generate Connection
Name button
CUSTOM SYSTEM provide the server name manually
SAP LOGON use the server from your SAP gui logon
SYSTEM NAME enter a name of your choice
SERVER NAME you can get this from the url for the web client
AUTHENTICATION METHOD use BASIC
HTTP PROTOCOL use HTTP or HTTPS
PORT NUMBER you can get this from the url for the web client
CLIENT NUMBER use the BW server client number
ENVIRONMENT choose an Embedded environment
MODEL choose an Embedded model
340
A wokbook can include Reporting query and Input ready queries, planning
functions, dynamic formatting
341
A query search is displayed where the user can selects its favorites ,double
clicking on the star, it will become yellow
By default the settings of the query is applied for the default report creation: the
context/row, columns axes are fulfilled
Dynamic formatting
Is set by the user but can be copied from one workbook to another
If the query is input- ready query the inputable formatting can be used to retrieve
as example when the nodes are not calculated regarding the setting of the query
Specific formatting can be created for Total member from the BEx query
342
343
The characteristics specified in rows in BEx Query Designer are automatically placed as
dimensions
in the row axis in the EPM add-in.
The characteristics specified in columns in BEx Query Designer are automatically placed
as
dimensions in the column axis in the EPM add-in.
The characteristics specified as "free characteristics" in BEx Query Designer are
automatically placed
as dimensions in the EPM add-in the following way:
the characteristics for which dynamic filters are defined in the "default values" area of BEx
Query
Designer are placed as dimensions in the page axis. The members displayed in the page
axis
are the ones defined as default values in BEx Query Designer. You can then make your own
member selection by using the Member Selector.
the dimensions for which no dynamic filters are defined are placed in the context. The
default
member selection is displayed as (No Selection) in the EPM Context bar since no specific
selection has been made in the EPM add-in. You can then make your own member
selection by
using the Member Selector.
344
Open a query with variables:
The EPM add-in supports queries without variables, and queries with the following types of variables:
dimension, hierarchy, hierarchy node, text, formula.
When you select a query that includes variables, the Set Variables dialog box opens and enables you
to specify the values for the variables. Depending on the variable definition in BEx Query Designer, you
can have various variable types:
Note:
The mandatory variables are displayed in bold.
Dimension member. Select one or more members, by clicking the icon and using the Member
Selector that opens.
Hierarchy. Select a hierarchy from the dropdown list.
Hierarchy node. Select one or more hierarchy nodes, by clicking the icon and using the Member
Selector that opens.
Formula. Enter a numeric value for the formula. The numeric value you enter is used for key figure
calculations defined in BEx Query Designer.
Text. Enter a text. You can enter a text to rename a header in the column or row axis; or to change
the description of a key figure.
The values specified can be then viewed in the Variables tab inside the Report Layout tab of the EPM
pane. The Variables tab is displayed only if variables exist.
Report Layout
Once you have selected the query, the report that is automatically displayed in the EPM add-in is the
Variables can be defined as :
Dimension values
Text, numerical
Hierarchy
Hierarchy nodes
Variables can be selected as:
Operator
Single value authorized
Multiple value
Direct typing
Reset variable value not possible- limitation
345
The EPM Ribbon in general is the same as Standard with the following exceptions:
COMMENTS only available for Standard connections
DATA MANAGER only available for Standard connections
TRANSFER DATA only available for Embedded connections
SPREAD / TREND / W EIGHT only available for Standard connections
LOCK CELLS only available for Embedded connections
DRILL THROUGH only available for Standard connections
EPM Context
The EPM CONTEXT appears in the EPM add-in and can be used for Embedded
connections. Just select a member in the EPM Context and then set a report axis to
use Context.
EPM Pane
The EPM Pane for Embedded has an extra tab called DATA PROCESSING on the lower
right where planning functions and sequences can be stored.
346
the EPM REPORT EDITOR looks very similar to a Standard connection but there are
the following exceptions:
-The characteristic and key figure structure appears in a tree structure on the left.
-The KEYFIGURES structure is available to select the key figures to be displayed in the
report.
-The GET QUERY REPORT push button can be used to re-populate the report with the
query default view. For example if the query has fiscal year in the rows and material
group in the columns, then the Get Query Report button would place fiscal year in
the rows and material group in the columns of the report.
-If you have a structure in the query for example you have 10 divisions fixed in the
rows - it will appear as one row just like just like the key figure structure. (example
coming up)
-The report is using a FIREFLY type connection
-You can select # NOT ASSIGNED to display or input data. This is not available for
Standard. This is useful if you want to input a value for the year but leave period
unassigned until you run the top down distribution which distributes the # to periods
1-12 for example
347
Let me show you an example of what a query structure looks like in a query and then
in an EPM Report and then in the output.
1.In the query definition the Structure contains Juice, Food, Beverages, and Water.
2.In the Report Definition, the structure appears as one item.
3.In the report output, Juice, Food, Beverages, and Water appear in the rows initially.
4.In the member selector for material group, you can see that Juice, Food,
Beverages, and Water are selected.
5.In the revised member selector for material group, you can see that Juice, Food,
Beverages, and Water are selected I have removed Juice.
6.The revised output now excludes Juice.
348
Lets discuss how to use the BW Query to display a rolling 12 month input form. For
example the current month lets say always appears in column E with forecast data.
In the 3 columns to the left of column E well have the prior 3 months with actual
data. To the right of column E will be the 8 subsequent months with forecast data.
In the BW Query, I can build a query with columns made up of a key figure like
Revenue restricted by period. For example, Ill place Revenue for the current period
(period 006 in this example) in column E. For column D Ill use a negative offset of -1
which gives me period 005. For column C Ill use a negative offset of -2 which gives
me period 004.
For column F Ill use an offset of +1 which gives me period 007 and so forth
In addition, we can use a text variable to display the month in the column header and
we can use an SAP Exit variable to determine the current month automatically.
349
If I need to merge data in a MultiProvider it is much easier with Embedded. I can put
a MultiProvider on a quantity and price real time InfoCube for example, create an
aggregation level on the MultiProvider, and a query on the Aggregation level.
If I put the InfoProvider characteristic in the querys free characteristics I can easily
display it in the EPM Report for illustration purposes.
In row 5, the REVPLAN real time InfoCube is displaying SalesQty of 500 while the
PRICEPLAN real time InfoCube is displaying a Price of 25.
350
Report Layout
Once you have selected the query, the report that is automatically displayed in the
EPM add-in is based on the
query definition such as it is defined in BEx Query Designer.
The Variables tab is displayed only if variables exist and only for BI IP source.
The values specified can be then viewed in the Variables tab inside the Report
Layout tab of the EPM
pane.
Connections: All connected sheets in all open workbooks in the current session of
Microsoft Office Excel appear in the tree view list displaying cubes/models, sheets
and reports
Using the Data Processing tab of the EPM pane, you can execute data processes,
which include:
"Planning Functions" that have previously been defined by InfoProviders in SAP
NetWeaver BW
Integrated Planning.
351
(No Selection): Member Selection as Defined in the Query
When a report is created based on a query, the members that are taken into account by default in the
report are the ones that are defined as default values in the query.
(No Selection) is displayed in the page axis. The sum of members is performed.
(No Selection) is displayed in all the dimension dropdown lists in the EPM Context bar. The sum
of members is performed.
You can either keep the default member selection or make your own member selection.
When you open the Member Selector, a sentence indicates that members, as defined in the query, is
used in the report. If you do not want to use this member selection, make your own selection of members.
The sentence will no more be displayed and the members you select are displayed instead.
Working with Context Members
When you open a query, as the query default member selection is applied to the resulting report, context
members are not available.
If you want to work with context members, do as follows:
1. For a dimension placed in the row or column axis, select the dimension dropdown list in the EPM
Context bar and select another member instead of (No Selection). As a result, the member selection
of the query is no more taken into account for this dimension and you are able to use the context
member.
2. From the row or column axis, open the Member Selector for the same dimension. The member you
have just selected is displayed in the list of available members and is indicated with (Context). To
use this member in the report, select the member and click Add Members.
"Total" Member
The "Total" member is taken into account and displayed in the row or column axis of a report and in
the Member Selector, if it has been specified in BEx Query Designer.
Key Figures
Measures are gathered in the EPM add-in into a dimension called Key Figures.
Key figures, calculated key figures and restricted key figures are supported and the result of the key
figures are displayed in the reports.
For input key figures, all types of disaggregation and inversion formulas are supported in the EPM
add-in.
(No Selection) is not available for the dimension Key Figures. The first key figure in the list defined in
BEx Query Designer is taken into account in the context and the page axis.
352
In the Options tab of the Report Editor, the input option is not inherited from the
worksheet options
but it is inherited from the query settings:
If the current query is defined as an input-ready query, the Use as Input Form
option is ckecked
by default and you cannot uncheck it.
If the current query is not defined as an input-ready query, the Use as Input Form
option is not
ckecked by default and you cannot check it.
353
Transfer data: All changed data is transferred to the user buffer and they are checked for
consistency. If the changed
data is correct, the data is recalculated, the amounts are updated and displayed in the input forms.
The
data remains in the user buffer as long as the user is connected. When the user logs off, the data is
removed from the user buffer.
Transfer is possible for worksheet/ or workbook
Roll back the data
Undo all changes since the last save of data to the database
Save the data to the server
When using the Save Data feature, the behavior is as follows:
The new or modified data since the last transfer is automatically transferred to the user buffer.
All the data is saved to the database, including the data from the user buffer. Data is first saved to
the database, then data is refreshed in your input form, taking into account the data you have saved
and recalculating the amounts accordingly.
You can perform the following save-related actions:
Save the data entered in the current worksheet.
Save the data entered in the current workbook.
Save the data entered in the current worksheet and then perform a refresh
354
Several types of planning function:
1. Planning function has no variables and filter has no variables
2. Planning function has variables and filter has no variables
3. Planning function has no variables but filter has variables
4. Planning function and filter have both variables.
No link between Planning functions and query.

The planning functions displays in the member selector the master data cross info
provider for one aggregation level
- the calculated data from planning functions are in the planning buffer for
simulation when the user is ok he saves the data , then the data base is updated.
No difference between display query or input query for planning functions.
No impact from the cell locking from the UI. The planning function is still calculated. -
Variables in planning functions : When source is Members, the value is dimension
members when the member selector is visible, or direct input ( for reevaluation
functions as example)
355
Several types of planning function:
1. Planning function has no variables and filter has no variables
2. Planning function has variables and filter has no variables
3. Planning function has no variables but filter has variables
4. Planning function and filter have both variables.
No link between Planning functions and query.

The planning functions displays in the member selector the master data cross info
provider for one aggregation level
- the calculated data from planning functions are in the planning buffer for
simulation when the user is ok he saves the data , then the data base is updated.
No difference between display query or input query for planning functions.
No impact from the cell locking from the UI. The planning function is still calculated. -
Variables in planning functions : When source is Members, the value is dimension
members when the member selector is visible, or direct input (for reevaluation
functions as example)
356
The EPM feature comparison has some fairly straightforward items such as multiple key
figures since that is clearly not in Standard but is available in Embedded.
Some of the other features may not exist in Embedded for example but there is usually
another way to do something similar. For example, the measures dimension doesnt exist in
Embedded but we can use variables in the query for cumulative YTD values.
Ive included the most important features of the EPM add-in for the comparison even if they
are available in both solutions for clarity. As an example, it is good to know that you can do
EPM Formatting in both Embedded and Standard.
Disaggregation by the way is available in both Standard and Embedded but in Embedded it
is hard coded into the query key figure whereas in Standard the planner uses an interactive
dialog similar to spread trend weight.
The EPM feature comparison has some fairly straightforward items such as multiple key
figures since that is clearly not in Standard but is available in Embedded.
Some of the other features may not exist in Embedded for example but there is usually
another way to do something similar. For example, the measures dimension doesnt exist in
Embedded but we can use variables in the query for cumulative YTD values.
Ive included the most important features of the EPM add-in for the comparison even if they
are available in both solutions for clarity. As an example, it is good to know that you can do
EPM Formatting in both Embedded and Standard.
Disaggregation by the way is available in both Standard and Embedded but in Embedded it
is hard coded into the query key figure whereas in Standard the planner uses an interactive
dialog similar to spread trend weight.
10
361
362
2
364
365
366
In Standard BPC, task profiles are used to control what activities users can perform
such as maintaining environments, models and dimensions for example. In
Embedded, the BW standard authorization objects take on this role.
In 10.1 there are several new authorization objects. These can be viewed in
transaction code SU21 in the RS Class. All of the CLASS/OBJECTS that start with
RSBPC are new.
367
In the slide you can see a listing of each authorization object with the fields that they
use and the activities that they control. Let me explain a few of these to give you a
feel for how they work.
The first one in the slide is RSBPC_ID is used to assign users to Embedded
environments using RSBPC_ID.
In the fifth row of the slide, RSBPC_ENVM is used to control who can manage which
environments. Field 1 is used to assign the environment and the two activities are 03
display and 23 which is create, change, and delete.
In the sixth row of the slide RSBPC_MODL is used to control who can manage which
models. Field 1 is used to assign the environment, Field 2 is used to assign the
model and the two activities are 03 display and 23 which is create, change, and
delete. RSBPC_MODL also has the activity A3 which is used to control who can
change work status and so on.
368
369
370
To control access to data in Embedded I need to make material group authorization
relevant. I can do this in transaction code RSD1, which is used to maintain
characteristics. In the slide you can see that I have made material group
Authorization Relevant.
To do this just go to RSD1 Enter the characteristic Choose Maintain Go to the
Business Explorer tab Select Authorization Relevant Choose Activate.
371
After making the characteristic authorization relevant, then the initial BW analysis
authorizations would be maintained in transaction code RSECADMIN.
In slide Ive created an analysis authorization called ZUNIF_BPC20 for material
group. In the AUTH. STRUCTURE are four CHARACTERISTICS / DIMENSIONS:
0MATL_GROUP this is used to provide the BW data restriction. Under the
INTERVALS column, the green * means that all charactistic values will be available
0TCAACTVT this is the BW display(03) vs change(02) setting. In this case it is set
to 02. (the Intervals column only displays the green brackets regardless)
0TCAIPROV this contains the assignment of the infoprovider. In this case it is the
underlying InfoCube. (the Intervals column only displays the green brackets
regardless)
0TCAVALID this is used to control the validity date of the authorization. In the
example below it is set to all (the green *)
To create the Analysis Authorization follow these steps:
Go to RSECADMIN Choose Ind. Maint Enter the analysis authorization id Choose
Create Input the short text Insert the Special Characters Choose InfoCube
Authorizations Enter the real time InfoCube Select Full Authorizations Continue
Select the authorization relevant characteristic Continue Restrict the authorization
relevant characteristic if needed Change the 0TCAACTVT to Change Choose F3
Activate
372
Once the analysis authorization is activated then it is assigned to the user(s) based
on input from the LOB. In the slide you can see that the TESTUSER user has been
assigned the ZUNIF_BPC20 analysis authorization.
This is achieved in RSECADMIN:
Go to the User Tab Individual Assignment Change Select the analysis
authorization Select the Manual or Generated tab Choose Insert Save
373
If this was an example of a normal BW analysis authorization, that would complete
the set up. However, Embedded BPC also requires that the analysis authorization
be assigned to the environment. This is performed manually in the RSECENVI
transaction code.
In RSECENVI: Select the environment Change Select the analysis authorization
Choose Insert
374
Data access profiles are used to control read and write access to transaction data in
the model / InfoProvider.
In Standard, the data access profiles are maintained exclusively from the BPC web
client.
Embedded however, relies on the underlying BW analysis authorizations (maintained
by IT) initially and then the Line of Business (LOB) can further restrict a users data
access in BPC.
In other words the BW analysis authorizations have been merged with the BPC data
access profiles and since the LOB can further restrict a users access in BPC you
have a much more practical business solution.
On the lower left, the EDW AUTHORIZATIONS (BW) are maintained initially by IT in
RSECADMIN.
Then the ENVIRONMENT AUTHORIZATIONS are defined by IT in RSECADMIN but user
assigments are provided by the LOB.
Then the ENVIRONMENT USER AUTHORIZATIONS are completely maintained by the LOB
in the BPC web client data access profiles.
375
376
BPC data access profiles are not optional.
BPC data access profiles can only further restrict the BW analysis authorizations.
For example if BW allows write access to material group Juice, Soda, and Water,
then the BPC data access profiles can only be used restrict that access. For
example you could restict write access to only include Juice and Water. And just to
be clear, the BPC data access profile cannot be used to gain access to alcoholic
beverages since they are not included in the analysis authorization in the first place.
377
Matrix security is the ability to control data access for a data intersection. I get this
question from students from time to time. It goes something like this: I want give a
user access to all costcenters for one account and a specific cost center for all
accounts.
For example, the user ran a report that shows all accounts (COGS, LABOR,
REVENUE, SERVICES, and Not Assigned) for the ADMIN cost center. If they try to
see all accounts for any other cost center they get an authorization error.
In the bottom part of the slide, the report displays only the COGS account for all cost
centers. If they try to see any other account for all cost centers they also get an
authorization error.
If you try this with Standard, the user would see all costcenters for all accounts.
However matrix security has always been available in BW and therefore we can now
use it in Embedded. To configure matrix security, just use two analysis authorization
objects: one with the COGS account for all cost centers and the second with all
accounts but only for the ADMIN cost center.
378
10
380
Note: Terminology Definition
Migration is used when were talking about system-to-system processes, whereas
upgrading is used when were talking about activities directly on an existing system.
2
Whenever we talk about migrating from one release to another one we focus on
programs that will do most of the work automatically. Then, of course, well get into
what objects etc that we need to convert manually, and subsequently what will have
to built from the ground up like in a bare metal scenario. It is a good idea to allow for
unexpected issues in your migration timelines.
Of course, it is important to keep in mind how the user interfaces are changing/being
replaced from a software install perspective. For example, in 7.5 configuration was
performed in the admin console but in 10.0 we use the adobe flex web client and in
10.1 it is the HTML5 web client. By the way, this chapter is only addressing
customers on the NetWeaver platform not Microsoft however there are plenty of
reference documents available to migrate BPC Microsoft to NetWeaver.
In addition, if you are using Business Planning and Simulation(BPS), your
conversion will be like the one we discuss for Integration Planning to BPC
Embedded with the exception that you will need to create the IP objects to match
BPS. For example a planning level in IP would need to be re-created in IP as an
aggregation level.
382
In our first use case, we have a customer on BPC 7.5 NetWeaver who wants to use
10.1 Standard. Fortunately they dont have to migrate to 10.0 and then to 10.1
because there is a program that goes from 7.5 directly to 10.1. This migration will be
relatively pain free from a back-end BW perspective however the Excel add-in is
completely different so that will be a big area of focus.
While you can implement HANA on your current server, it is best practice to have a
fresh install for HANA.
In addition to the steps discussed below, the BW system will need to be migrated
from 7.0 Enhancement Pack 1 to BW 7.4. In addition, the data base would need to
be migrated to HANA and the BW system needs to have the HANABPC component
installed.
383
When the backup is executed the system will create a zip file which will include the
metadata tables in BW, the master data, and the transaction data. You might decide
to handle the transaction data differently depending on how big it is.
First, use the UJBR transaction code to backup the 7.5 Appset in the 7.5
server EXECUTE BACKUP use this to back-up the Appset (Environments were called
Appsets in 7.x)
EXECUTE RESTORE use this to restore the Appset
EXECUTE IN BACKGROUND/FOREGROUND run the job in the background or
foreground
APPSET ID Select the appset
DOWNLOAD DIRECTORY NAME where to save the zip file
BACKUP METADATA TABLES these are settings and parameter tables
BACKUP MASTER DATA these are settings and parameter tables
BACKUP TRANSACTION DATA these is the data in the InfoCubes
RECORD COUNT use 0 for all records
384
Second, in the 10.1 server, you can then execute the restore in UJBR to convert the
appset to an environment.
Often, you can restore METADATA TABLES and MASTER DATA at the same time, but if
you have large dimensions, run these separately (Metadata first, then Master Data).
USE TECH NAMES FROM BACKUP FILES: Enabled. This allows for BADIs and DTPs to
be used and migrated to different environments. See note 689814 for more
information.
RECORD COUNT = 0. If you are restoring transactional data at the same time, then
enter 0, otherwise this parameter is not taken into consideration when restoring
Metadata Tables and Master Data.
Use SM37 to monitor the restore if needed.
385
Third, run the migration program UJT_MIGRATE_75_TO_101. You can make the
selections as shown
Here is what each setting is used for:
Environment select the environment to migrate
Environments & Parameters migrate the environment and parameters
Security migrate teams, task profiles, and data access profiles
User mapping file use a file to create users in BW
Controls migrate data validation into controls
Library Content migrate documents in the content library
Journal migrate journal templates and journal details
Data Manager migrate data manager packages
Business Process Flow migrate BPFs
Business Rules migrate business rules
Test Run do a test run first as a sanity check
386
In this example, a customer on BPC 10.0 NetWeaver wants to use 10.1 Standard.
This migration will be the simplest to perform since there arent as many changes in
the software such as the Excel add-in.
In addition to the steps discussed below, the BW system will need to be migrated
from 7.3 to BW 7.4. If the 7.3 system is not on HANA, the data base would need to
be migrated to HANA and the BW system needs to have the HANABPC component
installed.
To perform this migration, use the following steps.
First, use the UJBR transaction code to back-up the 10.0 Environment in the 10.0
server.
Second, in the 10.1 server, execute the restore in UJBR to bring in the 10.0
environment.
Third, run the migration program UJT_MIGRATE_10_TO_101
Fourth, put the environment online.
Fifth, rebuild the web web reports and input forms.
387
387
This scenario might be a little rare but could happen if a customer is using BPC10.0
and they want better EDW integration. This scenario is essentially starting from bare
metal since the 10.0 objects in BW have their own namespace. Consequently, there
is no existing tool to migrate a BPC 10.0 NW environment to 10.1 Embedded.
In addition, a 10.0 customer could be using an rdbms or HANA. The steps below do
not include any possible data base migration.
To perform the conversion the following steps need to be followed:
Upgrade the BW server from 7.3 to 7.4
Implement the HANABPC and CPMBPC software components
Create EDW model or use existing EDW model inside BW and create 10.1
Embedded environment and model in BPC.
Move master data and transaction data via BW tools.
Create teams and do other security setting and assignment in BW backend.
Set-up work status and move work status locking data from 10.0 tables to 10.1
Embedded tables if necessary.
Enable data audit (data audit logs from 10.0 cannot be moved to 10.1 Embedded)
Set up BPF templates
Build FOX script to replace BPC logic script
Build planning functions in BW
Build BEx Queries
Build EPM add-in/Web reports/input forms based on BEx Queries
388
Customers using IP can convert to BPC 10.1 Embedded. Their existing
InfoProviders and IP objects can be used without any modification for the most part
(user exits may be affected since ABAP code for BW on HANA is unique).
Of course, an IP customer could be using several implementation scenarios some of
which Ive listed below:
-BW 7.0 on a normal rdbms with or without BI Accelerator
-BW 7.3/7.31 on a normal rdbms or HANA with PAK
-BW 7.4 on a normal rdbms or HANA with PAK
Depending on what scenario you are on currently, there may be data base
migrations that need to take place in addition to the steps Ive listed below.
To convert from IP to 10.1 Embedded use the following steps. (the order can vary
somewhat)
First, set up a BPC environment/model on top of the existing BW and IP objects.
Second, set up the BW security this includes the bpc related bw standard
authorization objects and the analysis authorization objects that will be enhanced in
bpc.
Third, add user/team attributes to the owner dimension for work status. Add an
external characteristic if necessary to look up the owner and reviewers for the BPF.
Fourth, create the BPF template and create a BPF instance.
Fifth, set-up work status, comments, data profiles, and data audit
Sixth, create EPM Reports & Input Forms - Of course, if they are using the BEx
389
Analyzer or Analysis to do planning, similar workbooks in the EPM add-in will need to
be developed this could be the biggest work item. This effort can be carried out in
phases however since the BEx queries will not necessarily be affected.
389
This scenario might be a little rare as well but could happen if a customer is using
BPC10.0 and IP in parallel.
The BPC10.0 environment would be migrated to 10.1 Standard using the process
above.
The IP solution can be converted using the steps in section 7.3 above as well.
In addition, data flows between the Standard InfoCubes and Embedded InfoCubes
would need to be created if data integration is a requirement.
390
In summary we have discussed most of the scenarios that you may encounter when
moving to 10.1. We talked about how to perform a backup and restore of
appsets/environments, how to use the migration programs, and what objects you
need to build from the ground up.
Upgrading to BPC V10.1 isnt something to take lightly. There are definitely
significant numbers of reasons why you may want to or need to migrate to this
version, but its something to review and develop as a project rather than as a lift
and shift process. The features available in BPC V10.1 from a technical as well as a
functional point of view definitely make the move well worthwhile, and the impact of
these features offers the ROI that your corporation is looking for in BPC.
10
392
2
Transports for Embedded work basically the same way as in Standard. It is a
granular type of transport and well use the transport collector in RSA1 just like we
do in Standard.
You might recall that Standard environments had to be taken offline to be tranported.
Since theonline/offline concept doesnt apply to Embedded environments, you have
one less thing to worry about.
Because Embedded uses real time InfoCubes and planning enabled queries I need
to mention that they are still transported using the normal BW procedure using their
own TLOGO objects.
Also, the IP objects including infoprovider settings, aggregation levels, filters,
functions, and planning sequences are still transported using their own TLOGO
objects as well.
394
395
For BPC Embedded, there are five new TLOGO objects:
1.BPC Embedded Enviroment - this can be used to transport environments and also
models, teams, BPFs, and Workspace objects.
2.BPC Embedded Model this is used to tranport models.
3.BPC Team this is used teams and also the user assignments.
4.BPC BPF this is used to transport BPFs.
5.BPC Workspace this is used to transport web reports/input forms, EPM
reports/input forms as well as any custom folders
396
If I need to transport a environment for example, Ill just open the BPC EMBEDDED
ENVIRONMENT folder and search for the environment I need to transport. When I find
it Ill transfer it into COLLECTED OBJECTS and set the grouping to OBJECTS
AFTERWARDS.
397
If a model has multiple InfoProviders that belong to a MultiProvider, you have the
option of transporting the Model, the InfoProviders, and the MultiProvider all at the
same time.
398
10
400
2-2 Logon
Objective: In this lab, you will:

Logon to your environment.
Navigate within the interfaces
Description: Logon (repeated each day)

Note: In order to perform this lab you will need several different user ids and passwords as follows
a. Citrix: a logon username and password may not be required (see below)
b. Remote Desktop: username: train-## password: initial [replace ## with your assigned trainee number]
c. BPC & BW user(BPC logon screen & SAP GUI): username: BPC-## password: training [replace ##
with your assigned trainee number]
d. Logon to Citrix:
If you are on the SAP network: https://wts.wdf.sap.corp/portal/
If you are not on the SAP network: mywts.sap.com
User: will be provided
Password: will be provided
Click on Americas (for example)
Click on Training
If prompted, enter the citrix user and password provided by your instructor
Choose OK
Choose Common Training

e. Logon to the Remote Desktop Connection
Within Citrix go to Start -> Remote Desktop Connection
Next to Computer enter the server name: HB-HAPBC-###
(### will be assigned by your instructor)
Click Connect
Choose Other User

Enter the following:
Choose -> Choose OK
Goto Start -> Documents
In Documents, double click on the BPC Web Client link

Enter your assigned BPC-## User with a Password of lower case training
Choose Log On
c) Logon to the BW Application Server

Goto Start -> SAP Logon for Windows -> Choose T63
Choose Log On -> Enter the following:
Client: 800
User: BPC-##
Password: training
Hit enter
d) Connect to your assigned Environment
Choose your current Environment Connect BPC 10.1 environment CLASSIC_## [replace## with your
assigned trainee number].
Choose Connect
End of Lab
2-3 Work in the 10.1 Standard Web Client
Objectives:
Navigate the New Web Client
Change Comment Settings for a Model
Add a User to Your Environment
Create a Data Access Profile
Turn on Data Audit
Create a Standard Input Form
Set your Context Menu in the Input Form
Description: In the BPC 10.1 Web Client and Work with the new features
Navigate the Standard Web Client
1. Go to the BPC Web Client for your Classic_## Environment
You are on the Library screen of the Standard Web Client
2. To see how you might launch the EPM, click the EPM Office Add-in on the lower right to see the
options: (but dont select one)
3. Next to Environment Click Classic_##
You get the list of environments
4. Choose Manage All Environments
The Manage All Environment screen appears
5. Highlight your Classic_## environment Change Status
The models in your environment are in read and write mode (Online)
6. Choose OK
7. Close the Manage All Environment screen
8. Close the Administration screen

9. Choose System Reports
The Standard BPC System Reports are displayed
10. Choose Consolidation
The components of Consolidation are displayed
11. Choose Administration

You can see the administration activities in Standard
Change the Comment Settings for Planning
1. Go to Models Planning
2. Set the Comment Length to 1332 Save
3. Choose Back
Add a User to Your Environment
1. Expand Security Choose Users
2. Choose Add Select your BPC-## user
Your user appears in the Selected window
3. Choose Next
4. Select the ADMIN Team
You have now added your user to the ADMIN team
5. Choose Next Finish Close
6. Go to Teams ADMIN Select your user as the Team Lead

Now you can save reports / input forms to the team folder for example
7. Choose Save Back

Create a New Data Access Profile Based on a Property
1. Go to Data Access Profiles New
2. Enter the following
3. Under Member Access Choose Planning
4. Under Property Double click Currency
5. Under Value select CAD, USD
Hint: use the add criteria button
6. Choose OK
7. Under Access Rights Choose Read and Write

8. Choose Save Back
Turn on Data Audit
1. Expand Audit Choose Data Changes
2. Choose Configuration for: Planning
3. Under Web Reporting, choose Yes for the Budget Category
4. Choose Save Back
5. Close Administration
Create an Input Form on the Planning Model
1. In the Library screen Choose Input Form
2. Next to Model, select Planning
3. Add Account to the Rows and Time to the Columns
4. Left click Account
The member selection screen appears
5. Make the following selection for Net Income (PL600)
Hint: delete any other selection

6. Choose OK
7. Left click Time
8. Make the following selections
9. Choose OK twice
10. On the upper left, choose New Input Form Save

12. Choose Save
13. Left click Actual Switch it to Budget
14. Enter the following data

15. Save Data Yes
16. Left click the >> hyperlink
17. Choose Add All Dimensions
Now all of your dimensions appear in header
18. Left click the >> hyperlink
19. Choose Context Options Select Display as Without Dimensions

20. Choose OK
Now the dimension members are displayed w/o the dimension names
21. Choose Comments Display Comment Column
Now the Comments column appears with a drop down for time in column B
22. Choose Display Show Chart Only
23. Under Chart Type Select Pie
24. Next to Group Dimension Select Time

25. Choose Display Show Report Only
26. Choose Display Change Format
You can see the format options. The Totals Placement is new.
27. Choose OK
28. On the upper left, choose Planning IF Save
Hint: if Planning IF doesnt appear, use the little black triangle
29. Choose Home

Run the Data Audit Report
1. Go to System Reports
2. Click on Data Changes
3. Next to Model Choose Planning
4. Choose Display Report
You can see the audit trail for the data you entered earlier including 200 for Third Party Sales / Jan
2014
5. In your input form, enter and save 201 for Third Party Sales / Jan 2014
6. Refresh the data audit report
You should see that 201 (the amount entered) was just saved
7. Log off the web client
End of Lab
2-4 IP Modeling

Learn how to Create a Real Time InfoCube
Understand how to create a Planning Enabled DSO
Learn how to create an Aggregation Level on a Real Time InfoCube and a DSO
Learn how to create a Filter, and a Planning Sequence for data input
Browse the data in the InfoCube
Description: You need to understand how Integrated Planning Objects are maintained and how the data is
stored
Create a Sales and Price Planning Real Time InfoCube
1. From the SAP Easy Access SAP NetWeaver Business Warehouse screen, Goto Modeling Data
Warehousing Workbench: Modeling
2. If prompted, select Do Not Show This Question Again and choose No
3. You arrive in the Data Warehousing Workbench: Modeling screen in the InfoProvider tree.
Note: These labs build on each other so follow the instructions as requested. (You can always
experiment on non-class related test objects later)
4. Expand the BPC_Users folder.
5. Goto to your assigned Group## folder
6. To create the Sales Planning InfoCube, right click on Group## Create InfoCube
7. Fill in the fields as shown using your assigned ## and select the Real Time checkbox:
8. Confirm that the Real Time checkbox is checked.
9. Choose F5 to create the InfoCube
10. Expand the folders as shown below

11. Open the Settings folder
12. Check the box to generate a HANA Analytic View to allow additional ways to model and consume
the data.
In the data audit lab, well make an InfoCube auditable.
13. Click Save
14. Click Activate to create the data dictionary objects
The data dictionary objects and analytic view are created.

Before HANA, InfoCubes were star schemas with table joins from the SID table to the Dimension
table to the Fact table and characteristics were grouped into dimension tables.
With BW on HANA the InfoCube is flattened out. The SID tables join directly into the fact table and
there is only one Dimension table which is only used to keep track of uncompressed request ids.
15. Choose Extras Information Log/Status Dictionary/DB Status
16. There are only 2 tables in the InfoCube: the fact (F) table and the dimension (D) table (which is
used to keep track of uncompressed request ids)
17. Choose the green check twice and use F3 to go back to RSA1
18. Right click on TBW370S20 Planning Specific Properties Change Real-Time Load Behavior
19. Select Real-Time Data Target Can Be Planned: Data Loading Not Allowed
Choose Continue When prompted to transport the change Choose No
Create the Price Planning InfoCube
1. To create the Price Planning InfoCube, right click on Group## Create InfoCube
2. Fill in the fields as shown using your assigned ## and select the Real Time checkbox:
3. Confirm that the Real Time checkbox is checked.
4. Choose F5 to create the InfoCube
5. Expand the folders as shown

6. Click Save
8. Choose F3
Note: the symbol indicates that the InfoCube is a Real Time InfoCube
Note: the symbol indicates an SAP HANA Optimized InfoCube
9. Right click on TBW370P20 Planning Specific Properties Change Real-Time Load Behavior
10. Select Real-Time Data Target Can Be Planned: Data Loading Not Allowed
Choose Continue When prompted to transport the change Choose No
11. Use F3 until you return to the SAP Easy Access SAP NetWeaver Business Warehouse screen
Create an Aggregation Level
1. Goto Business Planning and Simulation BI Integrated Planning
Note: this is transaction code RSPLAN
Note: These labs build on each other so follow the instructions as requested. (You can always
experiment on non-class related test objects later)
2. Next to InfoProvider, enter the real-time InfoCube TBW370S## (## is your group number). This
InfoProvider is for sales quantity and revenue planning.
3. Choose Display to see the InfoObjects in this InfoCube
4. Close the Message Text panel at the bottom of the screen if necessary
Our planning scenario/scope calls for planning by year but not by period and also without customer
and material group initially. Therefore, the aggregation level we create next will not have these
fields.
5. Choose F3 to return back to the Planning Specific Properties of an InfoProvider screen
6. Next to Filters, choose Aggregation Level
Note: Aggregation levels are used to specify the scope of your planning activity
7. To open the dialog box for creating an aggregation level, choose Create
8. Enter the data as follows:
Note: AL stands for aggregation level S stands for Sales
9. Hit enter to proceed (or click the green checkmark)
The empty aggregation level appears on the right
10. Drag the InfoObjects to the Aggregation Level as shown below in order to plan by controlling area
and company code with a specific version value by year for revenue, quantity and contribution
margin
11. Near the top of the screen check the consistency of the aggregation level that you just created
12. Choose Save
13. Choose Activate (Activation will create the InfoProvider.)
14. Choose F3
Create a Filter for aggregation level S##_AL_01
1. To restrict the characteristic values, create a planning filter.
Next to Aggregation Level choose the Filters
2. Choose Create
3. Enter the following:

Note: F stands for filter.
4. Hit enter
5. Next to the Restriction column, use the Selection buttons to select the following
characteristic values:
Note: if you log in using the DE language, use ST for Sales Unit
6. In order to create a variable for Fiscal Year choose the button (not the far right) to the right
of Fiscal Year
7. Next to View, select Variables

8. Choose the Create icon
10. Choose F5
11. Select Mandatory Variable Entry
12. Choose F5
13. Choose the Default Values icon
14. Enter 2010 next to Direct Input
15. Hit enter
16. Choose F5
17. Choose Save
18. Select your variable on the left and Add it to Chosen Selections
19. Choose Continue
The filter now has your variable

20. Choose Save
21. Choose F3
Create a Planning Sequence for Aggregation Level S##_AL_01
Note: Planning sequences are normally used to run multiple planning functions either in a dialog step or
scheduled in a background job in a process chain(used in BW to execute background jobs)
Sequences can be executed manually either in the modeler for testing, or in workbooks by planners
Sequences require at least one filter and would usually contain multiple filters & functions. In this case
however, we just want to use our sequence to create testing data in our cube
Also, after sequences are saved, they can be executed or their individual steps can be executed
In the lab below you will enter data and then change the values so that you can see how delta values are
saved for a real time InfoCube
1. Choose Planning Sequence Create
3. Hit enter
4. Make your selections as follows:
5. Choose Save
6. Close the message tray
7. Select Step 1
8. Choose Execute Step to perform a data selection

9. You will receive a message that No data exists Choose Continue
10. Close the message tray
11. Choose the lower create icon twice

Two rows are created in the Input Template area
12. Enter the data as shown below
13. Choose the lower save icon to Save data from the input template into the InfoCube
14. Scroll to the right if necessary and change the values as shown:
15. Choose the lower save icon to Save the revised data from the input template into the InfoCube
Now we have original and changed data records in the data base.
Note: you are doing this test so that you can see how the system updates the data base
16. We need to input values for 2011 too. Choose the variable icon
17. Choose Input Help

18. Enter 2011 next to Direct Input
19. Continue
20. Confirm
21. Select Step 1
22. Choose Execute Step to perform a data selection for 2011

23. Continue through any messages
24. Choose the lower create icon twice to append two new rows
25. Enter the data as shown below
26. Input the values as shown below for 2011:

27. Choose the lower save icon to Save Data from Input Template
28. Change the values as shown below (scroll to the right if you need to)
29. Choose the lower save icon to Save Data from Input Template
Note: The input template is used exclusively in the modeler to view or enter data into the InfoCube
It is skipped when you run the planning sequence in its entirety. Therefore, input templates are
only used for testing.
30. Choose F3 until you return to the SAP Easy Access NetWeaver Business Warehouse screen
Browse the data in the Infocube
1. Goto the InfoCube data browser by entering transaction code /NLISTCUBE in the command field
and hit enter
2. Next to InfoProvider enter TBW370S##

3. Deselect Display SID if necessary
4. Choose Execute(F8)
5. Choose
6. Select Company Code, Controlling Area, Customer group, Material group, and Fiscal year
7. Choose Execute(F8) twice to view the data records
Note: this activity is carried out for testing by developers. End users would never do this.
8. How is the new data stored in the real-time InfoCube?

As delta records.
Note: This is merely temporary. When the InfoCube is compressed, the data is aggregated over the
common key fields and the data retention for planning activity will go away.
If we need an audit trail, then we can turn that on and the system will track who entered what data
and when.
9. Choose F3 until you reach the SAP Easy Access screen
Create a Planning Enabled Data Store Object
You need to plan at the material level by period and this detailed data set will be consumed in a HANA
analytical view
1. From the SAP Easy Access SAP NetWeaver Business Warehouse menu, Goto Modeling Data
Warehousing Workbench: Modeling
2. You arrive in the Data Warehousing Workbench: Modeling screen in the InfoProvider tree.
3. Open the BPC_USERS folder.
4. Goto to your assigned Group## folder
5. To create the planning enabled DSO, right click on Group## Create Data Store Object
6. Fill in the fields as shown using your assigned ##
Hint: use an InfoCube as the Template

7. Choose F5 to create the DSO
8. Open up the Settings folder
9. Next to Type of DataStore Object choose and select Direct Update > Continue
10. Select Planning Mode and External SAP HANA view (this will generate an Analytic view)
Planning enabled DSOs require that all characteristics are located in the Key fields
11. Right click on Key fields InfoObject Direct Input
12. Enter 0Material Hit enter

13. Drag all characteristics from the Data Fields into the Key fields folder
14. Remove the un-used characteristics and key figures so that you end up with the following:
15. Click Save
The active table and analytic view are generated
17. Choose F3
If you are prompted to Save, choose No
18. You can see that your DSO is set to allow direct input
Note: Aggregation Levels on planning enabled DSOs require that all key figures and characteristics are
included.
End of Lab
3-3 IP Basic Planning Functions

Create a Copy function
Create a Filter
Create a Planning Sequence to test the copy function
Create an Aggregation Level with Material Group
Create a Repost function
Create a Distribution function
Description: You need to know how to configure basic IP planning functions

Note: In order to perform this lab you will need to perform the preceding IP Modeling exercise
For sales quantity planning within aggregation level S##_AL_01, we are following this exercise scenario:
Create a Copy Function
Configure a copy function to copy data from Version A to B.
1. Goto RSPLAN
Hint: You can turn on transaction codes via Extras Settings Display Technical Names
2. Next to InfoProvider, type TBW370S## and hit enter
3. Select the Aggregation Level button
4. Next to Aggregation Level enter S##_AL_01 and hit enter
5. Choose the Planning Function button
Configure the copy function to copy the data from Version A to Version B for the sales quantity key
figure for the aggregation level S##_AL_01
6. Choose Create
7. Next to Function Type select Copy
9. Hit enter
10. Which field is to be selected as "Fields to be changed"? Version
Note: No field is to be selected in the Fields for Conditions area.
11. Near the top of the screen select
12. Restrict execution of the function to the Sales Quantity key figure
13. Choose
14. Select Sales Quantity (0COPASLQTY) Hit enter
15. Select
16. Use the detail buttons to make the following selections:
17. Choose Check Save F3

Create a Filter
1. Choose Filters
2. Enter S##_F_01
3. Choose Copy
4. Enter the following data:
5. Hit enter. The new filter is created and is change mode.
Next to Version select
6. Next to Direct Entry enter value B and choose Add
7. Under Chosen Selections, select version A Remove
8. Hit enter
9. Choose Save F3
Now we have a filter that can be used to copy data to Version B

Create a Planning Sequence to test the Copy function
1. Choose the Planning Sequence button
2. Choose Create
3. Enter the following identifiers for the sequence:
4. Hit enter
5. Use the dropdowns to make the following selections:
6. Choose Save
7. To execute the step in the sequence in trace mode, select Step 1

8. Choose Execute Step with Trace
9. Goto the Trace tab
10. Select Block Number 1
11. Choose the Display Contents button
Data was copied into version B
Note: A Block is a unique set of data that the system loops through when you execute functions.
12. Choose F3 without saving the data

Create an Aggregation Level with Material Group
The planning data for quantity planning in version B represents the default values for the sales managers.
Since the planning granularity of the sales managers is by material group, you need to create a new
aggregation level first.
You then need to create a distribution function that breaks down the summary values to material groups.
Create a new aggregation level by copying aggregation level S##_AL_01 and add the Material Group
characteristic.
1. In RSPLAN go to the InfoProvider screen and enter TBW370S## if necessary.
2. Choose the Aggregation Level button.
3. Enter your 1st aggregation level S##_AL_01
4. Choose Copy.
6. Hit enter
7. Drag Material Group to the Chars folder on the right:

8. Choose Check Save Activate F3
Create a Distribution Function
Now create a distribution function according to keys to distribute the data to the material groups
The data is to be distributed for the sales quantity key figure only
Goto the Planning Function screen.
1. Choose Planning Function
2. In the Edit Planning Functions screen, choose Create
3. Enter the data as shown below:
4. Hit enter
5. Which field is to be selected as Fields to be Changed? Material Group
6. Press the button
7. Select the Sales quantity key figure.

8. Choose the distribution variant Distribute Non-Assigned (#)
9. Under Delete Subrow choose the details button and select JUC for row one:
10. Select the first row and choose
11. Use the details button to select WAT for row two
12. The keys for the distribution to the two material groups Water (WAT) and Juice (JUC) are to be defined
as variables so that the sales manager can set the weighting factors themselves.
For this purpose, use an existing variable for each distribution factor
13. On row one, select the Details button on the right:
14. Choose Variable
15. Select the following
16. Hit enter
17. Use the same technique to select the variable for WAT:
18. Choose Check.
19. Choose Save
20. Choose F3
Create a Repost Function
We now need a function to repost the data from the Water material group to Table Water because the
material group WAT has been phased out (or there was an error)
Modeling is to take place within aggregation level S##_AL_02
2. Choose Create
4. Which field is to be selected as "Fields to be changed"? Material group
5. Choose
6. Select All Key Figures

7. Choose Create
8. Select WAT for the From value
9. Select TWAT for the To value

Create an Aggregation Level for Price Planning
Price and manufacturing cost planning, which is also done by the sales managers, takes place in a
separate real-time InfoProvider
In contrast to quantity planning, the granularity for prices and manufacturing costs is at the material
group level
For this purpose, create an aggregation level against the real-time InfoProvider TBW370P## that is
intended for price and manufacturing cost
In the following, the typical planning process of the sales managers is to be started for price and
production cost planning.
Here is the exercise scenario for Price Planning:
First, the planner will plan manually in Version B1, then copy the data into Version B2 using a copy
function.
Then the planner will use a revaluation function for Version B2, where the sales manager is to set the
revaluation factor as a variable.
Then the data of Version B2 is to be revised manually and finally, the planner will decide whether
Version B1 or B2 is to be the binding or final version.
Then the user can decide in a decentralized fashion which of the two versions is to be copied to version
B by means of a copy function with a variable on the sender version B.
1. In RSPLAN go to the InfoProvider screen and enter TBW370P##
2. Choose Display to see the InfoObjects
3. Choose F3
4. Goto the Aggregation Level button
5. Choose Create
7. Hit enter
8. Include all of the InfoObjects in the aggregation level, except for Customer group and the Posting
period
9. Choose Check Save Activate F3

Create a Copy Function to Copy Prices from Version B1 to B2
Configure a copy function to copy data from Version B1 to B2
Configure the copy function for all key figures for the aggregation level P##_AL_01
2. Choose Create
5. Hit enter
6. Select Version as Fields to be Changed
Note: No field is to be selected in the Fields for Conditions area
9. Select

11. Choose Check
12. Choose Save F3

Create a Revaluation Function to Mark Up Prices in B2
1. Choose Create
2. Next to Function Type select Revaluation
4. Hit enter
5. Since we want to revalue by material group and version select Material Group and Version in Fields for
Conditions
7. Under Conditions, use the detail button

8. Make the following selections:
9. Continue
10. Select row one Choose
11. To the right of Same Factor, choose the variable icon
12. Select the P00_VAR_REV_JUC variable:

13. Choose Create
14. Under Conditions, use the lower detail button to make the following selections using the steps
you did for row 1
This next part is a bit tricky
Choose Choose
15. Highlight row 2
16. To the right of Same Factor, choose the variable icon
17. Select the P00_VAR_REV_TWATER variable:

Create a Delete Function for Price data in Version B2
1. Choose Create
2. Next to Function Type select Delete
4. Hit enter
5. Select Version
7. Choose Select All Key Figures
8. Make the following selections:

9. Choose Check
10. Choose Save F3

Create a Copy Function to Copy Prices to Version B
At the end of the planning process, the sales manager has to decide whether the planning data of
version B1 or B2 describes the real development of the situation in the corresponding fiscal
year.
The sales manager then has to copy the data of this version (B1 or B2) to version B, which also contains
the sales managers quantity planning.
That is why you have to create another copy function that copies a sender version selected by the planner
to receiver version B. This applies to all key figures.
1. Choose Create
4. Hit enter
5. Select Fields to be Changed for Version
Note: No field is to be selected in the Fields for Conditions area.
8. Select

10. Choose Check
11. Choose Save F3
End of Lab
4-2 Planning Queries

Create a planning enabled query for sales planning
Review the key figure planning settings
Review the characteristic settings for planning
Review the query property settings for planning
Create a planning enabled query for price planning
Description: You need to understand how to create planning enabled queries

Note: In order to perform this lab you will need to perform the IP Basic Planning Functions lab
Create a Planning Enabled Query for Sales Planning
Since queries have are covered in the BW305 class, we will copy from an existing query in this case
and instead focus on the planning related settings.
So all you need to do is copy the two queries below and dont change anything except the query
description!
1. Create the query by copying from an existing query on the aggregation level S##_AL_02 (with
material group) to do quantity planning
The query has the following structure:
Controlling Company Mat Sales Sales Revenue Revenue CM CM

area code group Quantity Quantity 2010 2011 2010 2011
2010 2011
row 1 row 2 row 3 col 1 col 2 col 3 col 4 col 5 col 6

2. From the SAP Easy Access Menu, go to Business Explorer Query Copy
4. Execute (F8)
5. Highlight the source query Transfer Selections Continue

6. Replace 00 with your group number ##
7. Delete _1 at the end of the query name
8. Hit Enter twice

You just copied a query from one aggregation level to another.
Note: the new query still has the old description however
Now you need to review the planning related settings and change the description in the BEx
Query Designer.
9. Goto Start All Programs Business Explorer Analyzer
10. Click the Add-ins tab
11. Choose the Tools icon Create New Query
12. Choose System T63
14. Enter a Password of: training

15. Choose OK
16. Choose Open Under Find Select the History button

17. Select the query (S00_AL_02_PQ_S_SALMAN)
18. Choose Open

19. Expand the folders as you see below
Hint: Use the wrench icon to turn on key names when necessary
20. On the upper right, select the drop down next to Properties
21. Select the query
22. Under Description change S00 to S##

23. Goto Query Save
Next you need to review the planning related settings. Please do not make any further changes
to this query.
24. Goto to the Rows/Columns tab
25. Under Columns choose the first Key Figure
26. On the right select the Planning tab
The Sales Quantity key figure is Input-Ready however Disaggregation is turned off
27. Double click the first key figure to see how it is restricted:
Note: Under Description above, the entry &GROUP00_TEXTV& is a text variable that the
system will use to display the Year for that restricted key figure.
28. Choose Cancel
29. Under Rows select Controlling Area
30. Choose the Extended tab:
Controlling Area is set to display Master Data values in the rows (see the Access Type for
Result Values)
31. On the upper right, select the drop down next to Properties Select the top node
32. Choose the Planning tab
This query is set to Start Query in Change Mode (data input allowed)
33. To execute the default query view into a temporary workbook for 2010, choose Query Exit
and use the query
34. Enter 2010 if necessary
35. Choose OK
This is the default query view rendered into the BEx Analyzer temporary workbook
36. Close the workbook: Choose File Close Do not save the Workbook
Create a Planning Enabled Query for Price Planning
1. From the SAP Easy Access Menu, go to Business Explorer Query Copy
2. Execute (F8)
3. Highlight the source query Transfer Selections Continue

4. Under Technical Name of Copy, replace P00 with your group number and delete _1
5. Continue (your log may vary)
6. Continue
7. Go back to the Business Explorer Analyzer and choose the Tools icon Create New
Query
8. Choose Open Select History
9. Select the query you just copied(it should be first) the Name will still show P00 until we
change it in the next step
10. Choose Open

11. Expand the folders as shown
12. On the upper right, select the dropdown next to Properties Select the top node
13. Under Description change P00 to P##

14. Goto Query Save
15. Close the query designer and Excel
End of Lab
5-2 BPC Embedded Modeling

Create a Classic (Embedded) Environment
Create an Embedded Model based on a Real Time Infocube
Create an Input Form on an Embedded Model
Create an Embedded Model based on a Multiprovider
Description: You need to understand the Embedded Environment and Models based on InfoProviders
Note: This lab is independent from the IP Modeling lab
Create an Embedded Environment
1. To log on to the BPC Web Client, go to Start Documents BPC WEB Client
2. Enter user BPC-## and a Password of training
3. Choose Log On
4. At the bottom of the window, left click your current environment
Note: do not create any Standard environments or models during class.
5. Choose Manage All Environments
6. Choose Create

8. Choose Create
9. At the bottom of the window, left click your current environment
10. Choose your BPC_IP_ENV## Connect OK
Hint: if the web client does not respond after a minute or so, shut it down and log back in
Create an Embedded Model based on one InfoProvider
1. Choose ADMINISTRATION
2. Choose Models New
4. Choose Next
5. Select the previously created WSAN1_G## real time InfoCube in your Group## folder
6. Choose Next Create Close
7. Under ID choose PRICE
8. Under InfoProviders choose WSAN1_G##
Now you can see the InfoObjects for the real time InfoCube
9. Choose Aggregation Levels
Now you can see the InfoObjects of your Aggregation Level
10. Shut the web client down and re-launch it

Create a web based Input Form on an Embedded Model with one InfoProvider
1. Select the home icon on the upper right
2. Choose Library
3. Choose Input Form
4. Next to Select Model, choose Price Planning
5. Choose Search Next to Technical Name Enter *G##* Hit enter
6. Choose the WSAN1_PLANNING_QUERY_G##
7. Choose Next and you arrive in the Set Variables step
8. Choose Next and you are in the Define Data Grid step
9. Choose Next OK
You can see that the cells for Price Version B1 and B2 are available for input. (Price Version B is
set to not allow input in the BW query since it will only be written to via a planning function)
10. On the upper left choose Input Form Save
11. Enter the following Name and Title

12. Choose Save
13. Close the input form
14. Go Home
Create an Embedded Model based on a Multiprovider
2. Choose Models New
4. Choose Next
5. Select the previously existing UBW370P## and UBW370S## real time InfoCubes
6. Choose Next Create Close
7. Under ID choose SALES_PRICE
8. Under InfoProviders choose UBW370S##
9. Choose Related Multi-Providers
10. Close the window
11. Shut the web client down and re-launch it

Create a web based Input Form on an Embedded Model with two InfoProviders
1. Select the home icon on the upper right
2. Choose Library
3. Choose Input Form
4. Next to Select Model, select Sales and Price Planning
5. Choose Search
6. Next to Technical Name Enter *m##* Hit enter
7. Choose the M##_AL_PLANQUERY_01_MP
8. Choose Next and you are in the Set Variables step Select K42012
9. Choose Next and you are in the Define Data Grid step
10. Choose Next OK
Note: Proceed through any warnings
11. On the upper left choose Input Form Save
12. Enter the following Name and Title

13. Choose Save
Caution: it is imperative that you log off the web client to clear data locks.
End of Lab
5-3 BPC Security

Create a team manually
Create a team via file upload
Description: You need to understand the security concept of Embedded BPC
Create a BPC Team Manually in a Embedded Environment
1. Connect to your BPC_IP_ENV## environment
2. Goto ADMINISTRATION -> goto Teams
3. Create the ADMIN Team by clicking the New button
4. Add your BPC-## user to the ADMIN Team

5. The ADMIN Team is successfully created and can be used for a BPF or Work Status.
Choose Close
Create BPC Teams From a Flat File
1. Create the following csv file
Hint: Go to Start All Programs Accessories Notepad.

When you save the file to the remote desktop, next to Save as type choose All Files (*.*)
Note: these users already exist in BW
2. Change your internet options security. Go to Tools Internet Options
3. Go to the Security tab Trusted Sites Sites
4. De-select the Require Server Verification checkbox Choose Add
5. Choose Close OK
6. Choose Import
7. Choose TEAM1 -> Select two Team Leads
8. Save -> Back -> Close the admin screen
End of Lab
5-4 Local Providers
Create a Local Provider based on a flat file
Create a Model based on the Local Provider
Create a Planning Enabled Query
Create an Input Form
View the data from HANA
Run the Data Changes report
Description: You need to know how to utilize a Local Provider
Create a Local Provider based on a Flat File
1. Create the following flat file and save it as a csv file to your remote desktop
Hint: Notepad located in All Programs Accessories
Hint: Next to Save as type: Choose All Files(*.*)
2. In the BPC Web Client, connect to your BPC_IP_ENV## environment
3. Goto ADMINISTRATION InfoProviders
4. Choose Local Providers New

5. Enter the ID and Description as follows
6. Choose Next
7. Next to Data File, Select your FLATFILE
8. Choose Next
9. Select Enable Data Audit and Activate Data Audit
10. Select QTY and REV as Key Figures
11. Choose Next
The InfoProvider is created as a table in HANA

Create a Local Model
1. Select Create a new model for this local provider
2. Input an ID and Description as shown below
3. Choose Next
You have created a new model and a table in HANA with the flat file data as well as an Aggregation
Level. The query is not created by the system in this service pack
4. Choose Done
5. Close ADMINISTRATION
6. Go to the SAP Application Server
7. Go to RSPLAN
8. Go to the Aggregation Level screen

9. Enter B* F4 to find the automatically generated Aggregation Level
10. Double click your aggregation level (LOCAL##)
11. Display it
12. Choose F3 until you reach the SAP Easy Access Screen
13. Write down the technical name of your aggregation level ___________
Create a Planning Enabled Query on the Local Aggregation Level
1. Go to the BEx Analyzer
2. Goto Start All Programs Business Explorer Analyzer
3. Choose the Add-ins tab
6. Enter the following and a password of: training
7. Choose New Query
8. Next to Name enter your Aggregation Level B###-#### Hit enter
9. Expand the Characteristic Catalog folder
10. Go to the Rows/Columns tab

11. Drag and Drop the fields as follows
12. Highlight PRODUCT and set the Extended properties to display Master data
13. Highlight the key figures
14. Under Properties, go to the Planning tab
15. Select Input Ready
16. Go to the Filter tab
17. Drag Version, Entity, and DataSource into Characteristic Restrictions

18. Double click Version, Entity, and DataSource and restrict them to the following members
19. Go to Query Save
20. Enter the Description and Technical Name as shown below

21. Choose Save
Create an Input Form
1. Go back to the BPC Web Client
2. In the Library screen Choose Input form
3. Select the LOCAL_MODEL##
4. Search for the query that starts with L_PROV
5. Choose the L_PROVIDER_AL_Q## query Next Next Next OK
You can see the data that is stored in HANA
6. Change the existing values as you see below Submit Data
7. Choose Input Form Save

9. Save
End of Lab
6-2 Fox Formulas

Create a driver based formula
Create a formula with a condition
Create a formula to calculate revenue based on the prior year
Create a formula with a loop
Description: You need to understand the basics of Fox Code

Note:
Create a driver based formula
1. In BW, go to RSPLAN
2. Goto the Planning Function screen
3. Choose Create
5. Choose Continue
6. Choose
7. Choose to see the online help

8. Close the help screen
9. Choose
10. Double click 0COPAREVEN Revenue
11. Type in the equal sign

12. Use the Operands button and manual entry to fill in the rest of the formula:
13. Enter a comment (anything preceded by a *)
14. Check your syntax Save F3
Create a formula with a condition
1. Next to Planning Function, enter CALCREV1_##
2. Choose Copy

4. Choose Continue Select Material Group as a Field for Condition
5. Choose
6. Choose detail view
7. Add JUC to the Chosen Selections Continue

8. Choose Create
9. Select the second row
10. In row 2 choose detail view
11. Add WAT to the Chosen Selections Continue
12. Select row 1 Press the Display/Edit Parameter button
13. Modify your code as follows:

14. Check your syntax
15. Use Ctrl-C to copy the code
16. Select row 2 Press the Display/Edit Parameter button
17. Choose Ctrl-V
18. Modify your code as follows:
Create a formula to calculate revenue based on the prior year
1. Choose Copy
3. Choose Continue Select Fiscal Year as a Field to be changed

Note: Adding Fiscal Year as a Field to be changed will make it an operand in the FOX code
4. Choose Delete the existing code
5. Choose Operands Make the following selections
6. Continue Complete your code as shown
Create a formula with a loop
1. Choose Copy

3. Choose Continue Select Material Group as a Field to be changed
Note: Adding Material Group as a Field to be changed will make it an operand in the FOX code
4. Choose Delete the existing code
5. Choose Data Types

6. Double click Material group Move your cursor to row two
7. Enter in the following:
8. Choose Operands
9. Next to Key Figure Name Choose F4 Select 0COPAREVEN Continue
10. Next to Material group Choose F4 Choose Variables Select MG Continue

11. Continue and complete your code as follows using the same steps:
13. Return to the SAP Easy Access Screen
End of Lab
7-2 Embedded Web Reporting

Create a web report
Perform Manual Input Planning
View Data Locks from SM12
Transfer, Submit, and Rollback data
Display a BW Hierarchy
Use the Disaggregation Feature
Description: You need to understand the Embedded web reporting features.

Note: In order to perform this lab you will need to perform the BPC Modeling exercise
You will use your BPC_IP_ENV## environment
Create a web input form and perform planning activities
1. In the BPC Web Client go to the LIBRARY and click Input Form
2. Next to Name enter the input form name SALES_PRICES_##
3. Select the Price Planning model
4. Choose Search and next to Technical Name enter wsan1_p Choose search
5. Choose the query WSAN1_PLANNINGQUERY_G##

6. Choose Next twice
You can see the report axis
Note: both Currency and Sales Unit are set to single values in the query characteristic restrictions and
therefore they do not need to be included in the input form.
7. Choose Next OK
8. Input the prices for Price - Version B1 and Fiscal Year 2012 as shown below:
9. Click Transfer Data to send the data to your planning buffer and lock it
View the locked data in SM12
1. Goto the BW Application Server
2. Enter /NSM12 into the command field on the upper left
3. Hit enter twice (your data may vary)
Rows 3-5 are the data locks in the example above
Submit, Transfer, and Rollback data from the Web Input Form
1. Return to the BPC Web Client
2. Choose Submit Data
3. Choose OK
4. Change JUC to 15 Transfer Data
5. Choose the dropdown next to Transfer Data Roll Back Data
Your last change is reversed

6. Under Input Form Choose Save
8. Choose Save close the input form
9. Go Home Public
10. You now see your saved Web Input Form in the Public folder.
11. Highlight your new input form
You see the Delete, Rename, and Move to options on the right
On the lower right you have the option to copy the input form url to the clipboard
Close the BPC Web Client

Add a Hierarchy to a BW Query
1. Goto Start All Programs Business Explorer Analyzer Add-ins

Client 800
User BPC-##
Password training
5. Choose Open
6. Next to Name enter G## Open
7. Select your WSAN1_DISAGG_QUERY_## query
8. Choose Open
9. Go to the Rows/Columns tab
10. Select Material Group Goto the Hierarchy Tab
11. Choose the Input Help
12. Next to Hierarchy Name Select BPC_HIER
13. Choose OK
14. Under Expand to Level Select 4
15. Move Fiscal year from the Rows to Free Characteristics
16. In Columns choose Revenue in Ver B
We need to test disaggregating quantity based on revenue so turn on data input for revenue (you
will input revenue data when you do the test)
17. In the Planning tab Select Input-Ready (Relevant for Locking)
18. Go to the Filter tab

19. In Characteristic Restrictions, delete all years except for 2013
Caution: Do not save this query, use Save As to copy it!
20. Goto Query Save As Enter in the following Technical Name and Description as shown
below
21. Choose Save
22. Keep the Query Designer open
Create an Input Form and Test the Hierarchy Roll Up
1. Log into the BPC Web Client

2. Choose the Price Planning Model
3. Search for the WSAN1_DISAGG_HIER_G## query
4. Choose Next Next Next OK
Caution: if you get a data lock error, save the input form as Quantity_Hier_IF## and then re-
launch the web client.
Expand the nodes if necessary
5. Enter the following Sales Price and Revenue values

Choose Transfer Data
The hierarchy rollup is complete

Note: Sales Price is set to hide the total in the query
Disaggregate Sales Quantity
The business requirement calls for the planner to input quantity for a parent and distribute to the
base members based on revenue
1. Enter 20,000 for MATERIAL GROUP in cell B3
2. Choose Transfer Data
Sales Quantity is disaggregated in proportion to Revenue in Version B
Now you know how disaggregation works!

Change the hierarchy selection and sort order
1. Choose the Material group hypertext

2. Expand Beverages parent
You can see the dimensional hierarchy
3. Select Beverages and Material Group 1
They are added to Selected Members
4. Choose OK
Now you know how to re-order the BW hierarchy in a report or input form
5. Save the input form as Quantity_Hier_IF## to your public folder
Caution: it is imperative to log off the web client to clear data locks.
End of Lab
8-2 EPM Add In Reporting

Connect to a model using the EPM Add-In
Create and modify a report based on a BEx query and save it
Execute planning functions
Plan and retrieve data
Format a report for a locked cell
Description: You need to understand the Embedded EPM Add-in features

Note: In order to perform this lab you will need to perform the BPC Modeling and Web Reporting exercise
Caution: Perform this lab exactly as written
Connect to a model
1. Launch Excel 2010 from the Start menu
2. Go to the EPM tab
3. From the Report Actions Manage Connections
The Connection Manager opens
4. Click the Create button.

5. Go to Start Documents, open the Server.txt file and copy the information
6. Under Connection Type select SAP BW (INA Provider) and enter the following system information.
Hint: Paste the Server Name: WDFLBMT7040.WDF.SAP.CORP (this is not case

sensitive)
Note: InA stands for Information Access. This is part of the new SAP HANA UI for Information
Access.
7. Choose Connect
8. Enter your User Name bpc-## and Password training and click the Log On button.
9. Select your BPC_IP_ENV## environment and PRICE model
10. Choose Generate Connection Name

Choose OK twice
Create a price planning input form
Log on to your BPC_IP_ENV## environment by using the new connection.
1. Choose Log On
2. Choose the Connection drop down
3. Select your Price connection and choose OK
5. Choose Log On
6. Under Query Selection enter G## and hit enter (use your own assigned ## )
Note: If you were going to use a previously saved workbook, you would use the Workbook Selection
option.
After a few seconds, you will see a list of your queries
For your sales planning scenario, we will use the WSAN1_PLANNING_QUERY_## to prepare the
sales prices in version B
We will use the WSAN1_DISAGG_QUERY_## to calculate the sales revenues by using a planning
function.
7. Click on under Favorite to mark both queries as your Favorite
8. Double Click your WSAN1_PLANNING_QUERY_## query
In a few seconds, the default report is created automatically based on the definition of the query
We will be working only with 2012 data, so change the row axis
9. On the lower right Left click Fiscal year.Fiscal year
The EPM Member Selector dialog appears
10. Select K4/2012
11. Next to Relationship Choose Member Only
12. Choose Add Members (stay in the screen)

13. Choose to display the member properties
14. Close the K4/2012 dialog
15. Choose Non compound key

Now, year is displayed without the compounded fiscal year variant K4
Note: there is now a way to edit the selected Member Relationship
16. Choose Edit
17. Choose the Relationship drop down
Now you can see the relationship options
18. Choose Cancel OK
Only 2012 should now appear in the rows

Add IP Planning Functions to the Planning Objects tab
1. On the lower right choose the Planning Objects tab
2. Choose the T63 connection
3. Choose Select
4. Enter G## and hit enter
5. Select COPY B1 B2 and Choose OK
The Alias is PF_1 initially. This allows us to use one planning function in a workbook in multiple
ways. For example, a copy function could be executed via a push button or an icon in the ribbon.
If the function has a variable, the variables tab is used to assign values to the variable such as a drop
down box or hard code.
The filter tab is used to restrict the data region for the planning function for characteristics that do not
use variables.
6. Use the same technique as above to add the following planning functions
Save the workbook
1. In the EPM tab Choose Save Save as Input Form to Server Folder
2. Next to File Name enter the following: Price Planning IF ##
3. Choose Save
Input New Price Data and Test the Planning Functions
1. Enter the following values for Price - Version B1:

2. Go to the EPM tab
3. Choose Save Data Yes
4. On the lower right, go to the Planning Objects tab
5. Select planning function COPY B1 -> B2
6. Choose Execute OK
B1 prices are copied to B2
Now markup B2 by 15%
7. Select planning function REVALUE B2
8. On the lower right, enter 15 next to the WSAN1VR_G00 variable

Prices for version B2 are now 28.75
Now copy the version B2 data to version B
10. Select planning function COPY VER? -> B
11. On the lower right, choose to bring up the member selector for version
12. Choose B2
13. Choose OK

15. Choose Save Data
16. Choose Yes
17. Select planning function DELETE B2 Execute OK
18. Next to Transfer Data Choose the drop down Select Rollback Data
B2 Prices are back
Create a price planning input form and execute planning functions
1. Select Sheet2 in the same workbook
2. Place your cursor in cell A1

3. Go to the Report Layout tab on the lower right
4. Choose Select Another Query from the Report Layout Tab of the EPM pane
5. Select your WSAN1_DISAGG_QUERY_G## query and click OK.
Note the checkbox: Create Report From Query
The input is generated based on the query default view. Prices for Version B appear.
Note: When you create an EPM report on a planning query, the report is set to allow input by default
6. Choose Edit Report Options
Under Data Options, Use as Input Form is selected by default
7. Choose Cancel
8. Enter the following Sales Quantities
9. Choose Save Data Yes OK
Next we will add the planning function to calculate revenue
10. On the lower right choose the Planning Objects tab
11. Choose the T63 connection

12. Choose Select
13. Type in G## and hit enter
14. Select CALC REV FOR VER B Choose OK
The CALC REV FOR VER B function is added to the T63 connection in Planning Objects
15. Select CALC REV FOR VER B(PF_5) Choose Execute OK
Revenue has been calculated and can now be saved
Now we can use the disaggregation feature for Quantity

17. Enter a quantity of 500 for the material group Total and Sales Quantity in Version B
18. Choose Transfer Data Yes OK
Total Quantity is spread to the material groups based on Revenue
How could you freeze a material group?
19. Choose the cell for Sales Quantity in Version B and JUC
20. In the EPM ribbon Choose Lock Cells
21. Enter 95 for Total Quantity
All material groups are changed except for JUC

Format the Locked Cell
1. In the EPM Ribbon choose View Formats
You are in the EPMFormattingSheet
2. To the right of Dimension Member/Property Formatting put a check in the checkbox
3. Below Dimension Member/Property Formatting select Priority to the Row Format
Hint: the row numbers may vary from the screen capture below.
4. Select the Apply checkbox in column C for the Rows
5. To the right choose Add Member/Property
6. Go to the Specific Selection tab Choose Locked Cells

7. Choose OK
8. To the right of Locked Cell and column F format a fill of yellow
9. Go back to Sheet2
10. Choose Edit Report Options Select Apply Dynamic Formatting

11. Choose OK
12. Left click in cell C2 (JUC and Quantity intersection)
13. Choose Unlock Cells
14. For JUC and Quantity Enter 5
Note: if you are not able to unlock JUC and Quantity, proceed with the lab.
17. Choose your existing workbook Save Yes (overwrite the previous workbook)
Create a Control Panel
1. Add 6 rows at the top of the worksheet in sheet 2

3. In cell C1 Enter =EPM
4. Double click EPMEnvDatabaseDesc Choose Insert Function
You can leave the Connection name blank
5. Choose OK
Your environment is displayed in C1
6. Use the following functions to complete the header of the report:
Cell Function
C2 =EPMModelCubeDesc()
C3 =EPMRefreshTime()
C4 =EPMUser
Use a Local Member
The planner wants a formula for Revenue marked up by 25%. We can use a local member for that.
Local members are stored with the report and are completely dynamic unlike pure Excel formulas.
1. To use LocalMember recognition, go to Tools Options Sheet Options
2. Select Activate Local Member Recognition
3. Choose OK
4. In the cell to the right of Revenue in Ver B Enter Rev x 1.25
5. In the cell below Rev x 1.25 Enter the formula =E8*1.25
Hint: if the cell under Revenue in Ver B is E7 for example, then the formula would be =E7*1.25
6. Right click on the cell with your formula (F8 in this example) EPM Properties
Note: even though it says All members for 0VERSION etc., the query is restricted to single values.
7. Close the dialog box
8. To see the report specific Local Member Choose Edit Report Local Member tab Choose
LocalMember000
9. Choose Cancel
Use a Push button
Lets copy some code from the on line help
1. In the EPM tab Choose Help
2. Choose Search and enter executeplanningfunction
3. Select ExecutePlanningFunction
4. Copy the code under Example:

5. Close the help dialog
6. Turn on the Developers tab: File Options Customize Ribbon Select Developer OK
7. Choose the Developer tab
8. Go to Visual Basic
9. Turn on the FPMXLClient: Tools References Select FPMXLClient
10. Insert a Module: Right click on Microsoft Excel Objects Insert Module
11. Paste in your code Change PF_1 to PF_5
12. Go back to Excel
13. Go to the Developers tab
14. Choose Insert Form Controls Push Button

15. Draw the button around cell E2 Under Macro name Choose test Ok
The push button is in edit mode, and text can be entered
16. Input text as Calculate Revenue
17. Click in another cell
18. Change the JUC Sales Price per UM in Version B to 30
19. Go to the EPM Tab
21. Choose the Calculate Revenue button
Revenue in Ver B for JUC is re-calculated to 150
23. Enter Price Planning IF ##
24. Change the file type to Excel Macro-Enabled Workbook (*.xlsm)

25. Choose Save
Create a Report from Scratch
1. Go to Sheet3
2. Set the Sheet Options to be in read mode by de-selecting Use as Input Form
3. In the EPM tab Select the following Query
4. With your cursor in A1 Choose New Report
5. Build your report as follows

6. Left click Fiscal year in the Page Axis and make the following selection:
7. Choose OK
8. In the Column Axis Choose Key Figure
9. Select the Quantity key figure only

10. Choose OK twice
11. If you get a Warning, select Do not show this message again
12. Choose OK
13. On the lower right in the Row Axis Choose Material group.0MATL_GROUP Select Show
Totals
14. Choose OK
17. Log off
18. Exit Excel
End of Lab
9-2 Embedded Business Process Flows (BPF)

Create a BPF template
Activate an Instance
Execute the Activities
Description: Create a BPF, Activate it and Test it

Use your training number to replace the ## in IDs and Environment names.
Note: You need to do the BPC Modeling, Web Reporting, and Security lab to do this exercise
Create the BPF Template Process Settings
1. Log in the BPC Web Client and connect to your BPC_IP_ENV## environment
3. Under Business Process Flows click on Process Templates and then click on New
4. Give your Template a name and description of Planning
5. Click the drop down to the right of the Identity Dimensions field.
6. Choose Fiscal Year, Fiscal Year Variant, and Version

7. Choose OK
8. Next to Process Monitors choose the drop down
9. Go to the Teams tab
10. Select the ADMIN team
Create the BPF Template Process Activities
11. Click on the Activities tab
12. Choose New
13. Give your new activity a name and description of Price Planning
14. Configure as shown below

Note: Since none of the characteristics have an owner attribute, use the External Dimension (ZEXTDIM)
for the Driving Dimension.
15. Duplicate the Price Planning activity
16. When prompted, choose OK
A second activity called Price Planning 1 is created
17. Select Price Planning 1 on the upper left
18. Input a Name and Description of Quantity Planning

Create the Price Planning Workspace
1. Choose the Price Planning Activity on the upper left
2. Under Activity Performer choose Create

3. Choose Add Hyperlinks
4. Change the activity name from Hyperlinks to Price Planning
Hint: Hover on Hyperlinks and left click the context menu box and choose Rename
5. Under Edit Hyperlink, configure as shown

Note: the URL is: http://finance.yahoo.com/q?s=SAP&ql=1
6. Next to Validate, choose Add
7. Configure the Web Input Form hyperlink as follows:
8. Save and close the Price Planning workspace
Create the Quantity Planning Workspace
1. Choose Quantity Planning on the upper left
2. Under Activity Performer, choose Create

3. Choose Add Hyperlinks
4. Re-name the activity from Hyperlinks to Plan Quantities
5. Under Edit Hyperlink on the right, add the Quantity_Hier_IF## as shown
6. Save and close the workspace
7. Save the template
8. Choose Back
9. Highlight the new process template and click on Deploy.

Create a New Instance
1. Choose Process Instances New
2. Select your template and click Next
3. Next to Name add your BPC-## user
4. Choose Next
5. In the Select Context step select Fiscal year K4/2014 and Version B
6. Choose Next
7. Use the Change Performer hypertext to assign the ADMIN team to each Activity
8. Choose Next
9. Select Start the process instance
10. Choose Finish Close
You should now see that your new process is Running and available for use
Shut down the web client and log back in
Use the New Instance

1. Go Home My Activities
2. Choose Price Planning for FOOD
3. Choose Price Planning on the upper left
4. Choose Web Input Form (your values may vary)

6. Choose Complete
7. Close the activity by clicking the near the top right of the screen
You can see that the first activity has a Status of Completed
You have now created an Embedded BPF, Activated an Instance, and executed the Instance.
End of Lab
10-2 Embedded Work Status

View the owner and team attributes
Configure work status
Execute and check work status
Identify the virtual InfoCube used for the work status report
Description: You need to understand the BPC lock concept of work status in Embedded
Note: In order to perform this lab you will need to perform the BPC Modeling and Security exercise
View the Owner and Team Attributes
Since work status uses the owner and team attributes of the material group dimension (in this case),
lets go view the attribute values in BW.
1. From the BW application server, enter /NRSD1 in the command field:
Hit Enter
2. Next to InfoObject enter 0MATL_GROUP
3. Click the Display Button
Choose Maintain
4. View the Work Status Owner and Work Status Team attributes. We will use the Team attribute since
your BPC-## user is on the ADMIN team.
Close the web session
Choose F3 until you reach the SAP Easy Access screen
Configure Work Status
1. Logon to your BPC_IP_ENV## environment in the Web Client
Choose Work Status Configuration
Choose the PRICE model
3. Select Enable Work Status
Add the Submitted and Approved work states as shown below
Hint: Work states are defined by model in Embedded whereas in Standard they are defined at the
environment level.
Hint: Manual Entry includes manually inputting data from a web and excel input form and it also
pertains to planning functions
4. Configure the Locking Dimensions as follows:
HINT:
OWNER DIMENSION this characteristic is used to lookup the owner or team. It must have a hierarchy
along with an attribute to store the owners and an attribute to store the teams.
Hierarchy this is the hierarchy being used to derive the manager (ie the owner of a parent node is the
manager of the child node)
Owner Property the Work Status Owner is the attribute of the characteristic (Material group in this
case) being used to lookup the owner
Team Property the Work Status Owner is the attribute of the characteristic (Material group in this
case) being used to lookup the team
5. Add the Other Dimensions as shown below:
Since the business requirement is usually to lock data regions made up of version, time, and the owner
dimension you also need to turn work status on for year and version
Keeping in mind that an Embedded model can be referenced to more than one infoprovider, work status
can therefore be set for all infoproviders in a model or just for a specific infoprovider. By not selecting
SET WORK STATE BY INFOPROVIDER therefore any work state set will be for all infoproviders in the
model. If you do select SET WORK STATE BY INFOPROVIDER then you will need to specifiy which
infoprovider when you set the work state.
6. Save the Work Status setting.
7. Close the BPC Web Client
Execute and check work status
1. Log into the BPC Web Client
2. Open the LIBRARY and click the Input Form link.
3. Select Model: Price Planning
4. Search and click the query WSAN1_PLANNING_QUERY_G##

5. Choose Next 3 times and OK to finish the new input form.
6. Click the Change Work Status button to set the Work Status
Note: your values may vary
7. Change the work status for Food / B1 / 2012 to Submitted
Choose Apply
8. Choose OK
9. Choose Submit Data to store the Work Status data in the database.
Keep the input form open
Run the Work Status Web Report
1. Go Home
2. Navigate to the SYSTEM REPORTS page and open the Work Status report.
3. Select the Price Model
Caution: On this service pack, you may need to delete the local model in order to select the Price
Model.
To do so, choose ADMINISTRATION Models Highlight the row for LOCAL_MODEL##

Delete OK.
Repeat # 2 and 3 above
4. Choose Anytime
5. Display Report
You values my vary

6. Go back to the input form
7. Change the work status for Frozen Foods(R1113 / B1 / 2012 to Approved
8. Choose Refresh
You can see that the cell C5 does not allow input
10. Change the work status for Frozen Foods(R1113 / B1 / 2012 to Submitted
11. Choose Refresh
View the Virtual InfoCube used for the Audit Report
When you turn on work status for a model, the system automatically generates a BW virtual InfoCube
that is used to feed the audit report
1. To see the virtual Infocube go to transaction RSA1
The Virtual InfoCube is located in the unassigned InfoArea.

2. Right click on the InfoCube Display Data Model
It is using InfoObjects to capture the user, timestamp, version, material group, year, and the
Work Status Order (this is the work state number, for example approved is number 2).
3. Choose F3
4. To see the data, right click on the InfoCube Display Data
5. Choose Fld Selection for Output
6. Choose Select All Characteristics
7. Choose F8 twice
You data may vary

End of Lab
11-2 Embedded Data Audit

Learn how to enable data audit for an Embedded Model
View the Audit Characteristics in the InfoCube
Run the Web Client Data Audit report
Turn Data Audit Off
Description: Learn how to enable data audit on an Embedded Model

The BPC Data Modeling lab is a pre-requisite for this exercise
Enabling Data Audit on a BPC 10.1 Embedded Model
1. If necessary, log in the SAP GUI with your BPC-## user id and training password.
2. Go to RSA1
3. In the BPC_USERS folder expand your Group##

4. On the WSAN1_G## InfoCube right click Change
5. Expand Settings and check the box next to Auditable
6. Activate the change
You should now see additional characteristics in the new Audit Dimension
Also, the associated aggregation level will need to be re-activated.

7. Choose F3
8. Right click the WSAN1_G20 InfoCube Manage
9. Go to the Contents tab
10. Click Fact Table

Notice the four SID_OA* characteristics. Audit data is stored in the Fact table.
11. Choose F3 InfoCube Content
The audit characteristics appear. Audit data can also be accessed by running the BPC Data Changes
report or a BEx Query.
12. Choose F3 twice
13. Highlight Group1
14. Choose Refresh
You can see that the WSAN1AG## aggregation level is inactive

15. Right click WSAN1AG## Change Activate
16. Choose F3 until you reach the SAP Easy Access Screen
Test Data Audit in the BPC Web Client
1. Close the BPC Web Client if it is open
2. Open the BPC Web Client and connect to your BPC_IP_ENV## environment
3. In the web client go to Administration
4. Choose Models Select the Price Model

You can see that it is Auditable
5. Choose Back
6. Under Audit Choose Data Changes
7. Choose Configuration for: PRICE
Note: You could disable data audit in this screen by setting the Status to Off
8. Return to the home screen
9. Go to the Library screen
10. Create an input form based on the Price Planning Model and WSAN1_PLANNING_QUERY_G##
11. Change an existing value by 1 and choose Submit Data for FOOD
12. Return to the Home screen
13. Go to System Reports Data Changes
14. Select InfoProvider WSAN1_G##
15. Choose Anytime
16. Choose Display Report

Turn Data Audit Off
1. Go to the BW Server
2. Go to RSA1
3. In the BPC_USERS folder expand your Group##
4. On the WSAN1_G## InfoCube right click Change
5. Expand Settings and un-check the box next to Auditable
6. Activate the change
7. Choose Continue Activation
The audit fields are deleted from the InfoCube
The associated aggregation level will need to be re-activated.
8. Choose F3
9. Right click WSAN1AG## Change Activate
10. Return to the Easy Access Menu

End of Lab
12-2 Migration

Learn how to backup an environment
Learn how to restore an environment
See how to migrate an environment
Description: You need to become familiar with the transaction code and program to backup, restore and
migrate environments.
Backup an environment
1. From the BW application server, enter /NUJBR in the command field:
2. Hit enter and you come to the BPC: Backup & Restore Tool
See How To Migrate an Environment
1. From the BW application server, enter /NSE38 in the command field
2. Enter the program as shown:

3. Choose F8
End of Lab

TZBPC1 - 98 Aug 21 2014 Lessons and Labs

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

TZBPC1 - 98 Aug 21 2014 Lessons and Labs

Caricato da

Copyright:

Formati disponibili

1

Enhanced Dimension Management User Interface

Support for multi-select for mass operations saves time

Improved App Management Screen

Planning function Revaluation revaluates key figure 1.

HANA revision 64 is required to leverage HANA MDX.

Consolidation is not available in Embedded environment

Differences in Embedded environment of this release:

System reports in Embedded environment of this release:

Sample files are

Customized files should be located and named as

Please refer to limitation note 1916315 for details of variable limitations.

No link between Planning functions and query.

No link between Planning functions and query.

Objective: In this lab, you will:

Description: Logon (repeated each day)

Click on Americas (for example)

Choose Common Training

Choose Other User

Goto Start -> Documents

In Documents, double click on the BPC Web Client link

c) Logon to the BW Application Server

d) Connect to your assigned Environment

Navigate the Standard Web Client

1. Go to the BPC Web Client for your Classic_## Environment

You are on the Library screen of the Standard Web Client

You get the list of environments

4. Choose Manage All Environments

The Manage All Environment screen appears

5. Highlight your Classic_## environment Change Status

7. Close the Manage All Environment screen

8. Close the Administration screen

The Standard BPC System Reports are displayed

10. Choose Consolidation

The components of Consolidation are displayed

11. Choose Administration

2. Set the Comment Length to 1332 Save

1. Expand Security Choose Users

2. Choose Add Select your BPC-## user

Your user appears in the Selected window

4. Select the ADMIN Team

You have now added your user to the ADMIN team

5. Choose Next Finish Close

6. Go to Teams ADMIN Select your user as the Team Lead

7. Choose Save Back

1. Go to Data Access Profiles New

2. Enter the following

3. Under Member Access Choose Planning

4. Under Property Double click Currency

5. Under Value select CAD, USD

Hint: use the add criteria button

7. Under Access Rights Choose Read and Write

1. Expand Audit Choose Data Changes

2. Choose Configuration for: Planning

3. Under Web Reporting, choose Yes for the Budget Category

4. Choose Save Back

1. In the Library screen Choose Input Form

2. Next to Model, select Planning

3. Add Account to the Rows and Time to the Columns

4. Left click Account

The member selection screen appears

5. Make the following selection for Net Income (PL600)

Hint: delete any other selection