You are on page 1of 23

Provisional Master Data in Integrated Business

Planning for SAP Simple Finance


An Example-Based How-To Guide
Applies to:
Integrated Business Planning in SAP Simple Finance

Summary
SAP customers who use Integrated Business Planning for financial planning in Management Accounting are
often in the situation that key figures are to be planned for master data that does not yet exist in the tables of
the ERP system. This How-To guide uses a concrete example to show, step-by-step, how additional
characteristic values can be defined that function in financial planning of Management Accounting as
provisional master data and can be planned, but do not yet exist in the tables of the ERP system.

Author: Gnter Graf


Company: SAP SE
Created on: 9 January 2015

Author Bio
Gnter Graf is a Senior Developer at SAP SE in Walldorf, Germany. He has 8 years experience
in developing SAP standard software, the last 4 years in the ERP Financials area.

Table of Contents
Business Scenario .............................................................................................................................................. 3
Background Information...................................................................................................................................... 3
Step-by-Step Procedure ..................................................................................................................................... 5
Step 1: Create a Delta Characteristic ............................................................................................................. 6
Step 2: Maintain Provisional Master Data ....................................................................................................... 8
Step 3: Create a HANA Master Data View ..................................................................................................... 9
Step 4: Replace the Master Data View in /ERP/MATERIAL......................................................................... 20
Copyright........................................................................................................................................................... 23

Business Scenario
SAP customers who use Integrated Business Planning for financial planning in Management Accounting
often are in the situation that key figures are to be planned for master data that does not yet exist in the
tables of the ERP system. For example, a consumer goods producer plans to market an anti-dandruff
shampoo next year. The person in charge of planning is to take this product into consideration when
planning sales revenue, but the new shampoo is not yet in the master data in ERP.
This How-To guide describes how you can define provisional data for your financial planning that does not
exist in the ERP master data tables, based on the scenarios delivered by SAP for financial planning in
Management Accounting.
The description of following steps, for example, transfer posting of the plan data of the provisional material
to a real material (or its deletion, and so on), could be a topic for future How-To guides.

Background Information
SAP delivers planning scenarios for financial planning in Management Accounting as local BW content
(that is, BW content in the ERP system, not in the central BW system), based on the real-time InfoCube
/ERP/SFIN_R01 (Financials Planning). Analysis Office Workbooks constitute part of the planning scenario.
Customers can use these to enter planned figures in a Microsoft Excel environment.

SAP delivers the following Workbooks:

Cost Center Planning on Years (/ERP/SFIN_A00_WB01)

Cost Center Planning on Periods (/ERP/SFIN_A01_WB01)

Internal Order Planning on Years (/ERP/SFIN_A10_WB01)

Internal Order Planning on Periods (/ERP/SFIN_A11_WB01)

Project Planning on Years (/ERP/SFIN_A20_WB01)

Project Planning on Periods (/ERP/SFIN_A21_WB01)

Market Segment Planning on Years (/ERP/SFIN_A50_WB01)

Market Segment Planning on Periods (/ERP/SFIN_A51_WB01)

Profit Center Planning on Years (/ERP/SFIN_A70_WB01)

Profit Center Planning on Periods (/ERP/SFIN_A71_WB01)

P&L Planning on Years (/ERP/SFIN_A90_WB01)

P&L Planning on Periods (/ERP/SFIN_A91_WB01)

Figure 1 shows the technical architecture of the delivered planning scenarios.

BW
Analysis Office Workbook /ERP/SFIN_A<>_WB01

Input Ready Query /ERP/SFIN_A<>_IRQ<>

Aggregation Level ERP/SFIN_A<>

Multiprovider /ERP/SFIN_M01

Real-Time InfoProvider /ERP/SINF_R01


(Plan Data)

Virtual Provider /ERP/SINF_V01 (Actual


Data)

Plan Data

Characteristics /ERP/<>
BW Characteristics
BW Characteristics

Key Figures /ERP/<>


BW Characteristics
BW Characteristics

HANA Views from Content Package sap.erp.sfin.co.pl


Master Data Views FCO_C_<>
Master Data Views
Master Data Views

HANA Information Model


COPA_DOC (Actual Data)

Figure 1: Architecture of the Delivered Planning Scenarios

On the highest level are the Analysis Office Workbooks, with which the end user can enter planned figures.
The figures entered in this way are persisted in InfoCube /ERP/SFIN_R01.
InfoProvider /ERP/SFIN_V01 is used to read the actual values from the previous year and compare the
planned values of the current year in the Workbooks. A planning function can also be used to copy the actual
values from the previous year as a template for the planned values of the current year in the Workbooks. The
InfoProvider is based on HANA Information Model sap.erp.sfin.co.pl.COPA_DOC.
The characteristics of both InfoProviders read their master data from the ERP master data tables, which are
accessed in HANA Views FCO_C_<>. For example, master data access for characteristic
/ERP/MATERIAL is based on HANA View FCO_C_PRODUCT, which in turn contains ERP master data
tables MARA and MAKT. As a consequence, only figures for characteristic values defined in the ERP
material master can be entered and persisted.
However, it is in the nature of planning to plan things (for example, products) that do not currently exist in the
ERP master data but are to exist in future. For this reason, in this How-To guide, we describe a procedure to
enhance the master data of a characteristic with further provisional characteristic values, which can then be
used in planning based on real-time InfoCube /ERP/SFIN_R01.

Note: This How-To guide shows you how you can enhance ERP master data tables with provisional data. As
mentioned above (see chapter Business Scenario), this provisional data does not exist in the ERP
master data tables and can only be used in a BW environment. This means that several follow-on
processes, such as integrating plan data for provisional master data in an ERP system, are not
possible.

Step-by-Step Procedure
The How-To guide describes how you can enhance the HANA master data view so that in addition to the
master data from the ERP tables it can also provide characteristics defined elsewhere that are not in the
standard ERP tables and can function as provisional master data.
The procedure is described on the basis of the characteristic /ERP/MATERIAL (from now on, original
characteristic) delivered by SAP, which reads its master data from the HANA View FCO_C_PRODUCT.
Essentially, you define your own HANA View CV_MATERIAL_W_PREL, which combines the master data of
original view FCO_C_PRODUCT with the master data from auxiliary or delta characteristic ZMAT created for
this purpose. Then you exchange the master data view in the corresponding /ERP/ characteristic used in
/ERP/SFIN_R01 for your own view.
The delta characteristic ZMAT is created as a customer-specific Z-characteristic and reads its master data
from the BW-generated tables /BIC/PZMAT and /BIC/TZMAT. This auxiliary characteristic is required for
generating the master data tables (see above) and for maintaining the provisional master data in these
tables by using transaction RSD1.
Figure 2 shows the relationship of the characteristics described and views/tables.
BW

Characteristic /ERP/MATERIAL

Characteristic ZMAT

HANA DB
View
<yourContentPackage>.CV_MATERIAL_W_PREL

View
sap.erp.sfin.co.pl.FCO_C_PRODUCT

Table /BIC/PZMAT
Table /BIC/TZMAT

Figure 2: Characteristics and Master Data Views/Tables Involved

Step 1: Create a Delta Characteristic


The delta characteristic is the BW characteristic that is to include the provisional master data.
-

To create the delta characteristic, use transaction RSD1. Use the original characteristic as a
template.

Change the master data access type to Default.

Activate your characteristic.

Step 2: Maintain Provisional Master Data


-

Open the master data maintenance dialog. Click the Maintain button.

In the master data maintenance dialog, you can enter your provisional master data as a text:

Delete the empty key entry.

Save your entries.

Step 3: Create a HANA Master Data View


Create the new HANA master data view for characteristic /ERP/MATERIAL. In the HANA Developer Studio,
generate a new calculation view. The view is essentially a union of the original view FCO_C_PRODUCT and
the master data of your delta characteristic. The latter is contained in the master data- and text tables
generated by BW (in the example, these are tables /BIC/PZMAT and /BIC/TZMAT). For the names of the
generated tables, see transaction RSD1 on the Master Data/Texts tab page of your delta characteristic.
The new view then contains the union of the master data from the original view FCO_C_PRODUCT with the
provisional master data from the delta characteristic ZMAT and the generated master data tables
/BIC/PZMAT and /BIC/TZMAT.
-

Create the view with the following settings:

Add a union to the view.

Connect the union with the projection

10

Add the master data view of the original characteristic to the union (in the example, this is delivered
view FCO_C_PRODUCT).

Add a join to the view.

11

Connect the join with the union

Add another projection to your view.

12

Connect the new projection with the join

Add the value table of your delta characteristic to the new projection. In the example, this is table
/BIC/PZMAT.

13

Add all columns of the value table except the CHANGED column to the output of the projection.

Create a filter for the projection that only takes entries with object version A into account.

14

Add the text table of the delta characteristic to the join of the view. In the example, this is table
/BIC/TZMAT.

In the join of the view, connect the projection with the text table as shown. Set the Join Type property
to Text Join and the Language Column property to LANGU.

15

Add all columns except the OBJVERS column of the projection of the value table (Projection_1) and
the column of the text table (TXTMD) to the output of the join.

In the union of the view, use Drag and Drop to define the following columns of view
FCO_C_PRODUCT as target columns:

MATNR

MAKTX

MTART

MATKL

SPART

PRDHA

Connect the source columns from the join with the corresponding target colums of the union as
shown.

16

In the upper projection (containing the union), add all columns to the output.

17

Save and activate your view.

To test your view, click with the secondary mouse button on Semantics and select Data Preview.

18

In the raw data of the preview, you should now see all values from the original master data view plus
the values that you created as provisional master data in the delta characteristic. If the table is too
large, you can sort the table or also filter by the value of the provisional master data.

19

Step 4: Replace the Master Data View in /ERP/MATERIAL


-

Open characteristic /ERP/MATERIAL by using transaction RSD1 in Edit mode. Navigate to the
Master Data/Texts tab page.

20

The characteristic should contain its master data from your new view. In the Master Data Read
Access area, change the HANA package and the HANA view accordingly.

Click the Maintain HANA-Assignments button and check that all attributes have the correct HANA
view field assigned.

Save and activate your characteristic.

Test your characteristic by clicking the Display button to display the master data.

21

You should also see your real and provisional master data here.

The characteristic /ERP/MATERIAL is contained in the delivered InfoCube /ERP/SFIN_R01, so as of now the
real and provisional master data is automatically available in all queries and planning functions based on it.
Analogously, you can do this for any other InfoObject.

22

Copyright
2015 SAP SE SE or an SAP SE affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any
form or for any purpose without the express permission of SAP SE.
The information contained herein may be changed without prior notice.
Some software products marketed by SAP SE and its distributors contain proprietary software components
of other software vendors. National product specifications may vary.
These materials are provided by SAP SE and its affiliated companies (SAP SE Group) for informational
purposes only, without representation or warranty of any kind, and SAP SE Group shall not be liable for
errors or omissions with respect to the materials. The only warranties for SAP SE Group products and
services are those that are set forth in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an additional warranty.
SAP SE and other SAP SE products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP SE in Germany and other countries.
Please see
http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark
for additional trademark information and notices.

23