You are on page 1of 7

First Steps for Working with Integrated Business Planning for SA

PDF download from SAP Help Portal:


http://help.sap.com/saphelp_sfin100/helpdata/en/7c/3c805425280e4ee10000000a423f68/content.htm

Created on September 15, 2016

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help
Portal.

Note

This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

2016 SAP SE or an SAP 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 Group") for informational purposes only, without representation or warranty of any kind, and SAP
Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP 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 and other SAP 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 www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

PUBLIC Page 1 of 7
2014 SAP SE or an SAP affiliate company. All rights reserved.
Table of content
1 First Steps for Working with Integrated Business Planning for SA
1.1 Adaptations for Integrated Business Planning
1.1.1 Adapting Planning Applications in the SAP Simple Finance Add-On
1.1.2 Adapting Actual Reporting in the SAP Simple Finance Add-On for S
1.1.2.1 InfoObject Assignment for Operating Concern
1.1.3 Adapting the HANA Views to a New Operating Concern
1.2 Planning View Generation (Optional)

PUBLIC Page 2 of 7
2014 SAP SE or an SAP affiliate company. All rights reserved.
1 First Steps for Working with Integrated Business Planning for
SAP Simple Finance Add-On for SAP Business Suite powered by
SAP HANA

The documentation in this section describes the activities you can perform for using Integrated Business Planning for SAP Simple Finance Add-On for SAP
Business Suite powered by SAP HANA (IBP).

1.1 Adaptations for Integrated Business Planning

SAP delivers the following planning applications:


Cost center planning on years and periods
Project planning on years and periods
Internal order planning on years and periods
Market segment planning on years and periods
Profit center planning on years and periods
Functional area planning on years and periods
P&L planning on years and periods
These applications consist of local BI content. Local means that this BI content is shipped with SAP Accounting powered by SAP HANA and not with the
central BI content. Local content runs on the ERP system directly using the Local BW and does not need a separate BW installation. The content for
integrated business planning consists of SAP HANA views, InfoProviders, MultiProviders, Aggregation Levels, Queries, Filters, Planning functions, Planning
sequences, and Analysis Workbooks.
You can adapt this local content in the same way as you adapt the central content. In principle, there are two ways to proceed:
Change the SAP delivered content. SAP delivers the content in the D-version (delivered). After content activation (part of the setup process) the A-
version (activated) is created. You can adapt and change the A-version without any modification. At any time you can return to the D-version that stays
as delivered by SAP. When SAP delivers a new version of the content, you can decide whether to take this instead of your adapted A-version, stay with
your A-version or even merge the two versions.
Copy the SAP delivered content to your own namespace. This takes more effort and is recommended only if you make major changes to the delivered
content.
You can mix both procedures: For example, use the SAP HANA views, InfoProviders, MultiProviders, and Aggregation Levels delivered by SAP as they are,
or modify them only slightly and create your own queries, planning functions, and Analysis workbooks on top.

Prerequisites
You have completed the relevant activities in the Setup guide.
You are authorized to use the following:
SAP Business Objects Analysis Edition for Microsoft Office
BEx Query Designer
SAP BW Planning Modeler
SAP BW Data Warehousing Workbench
SAP HANA Studio
Depending on the scenario, you typically will need only few of the tools.

Activities
You can do the following:
Adapt UI formatting and personalize Analysis Workbooks
Add additional columns for manual planning
Add own planning functions
Add additional characteristics
If the characteristics are already part of the delivered InfoProvider, you only have to change the Aggregation Level and the objects above.

1.1.1 Adapting Planning Applications in the SAP Simple Finance


Add-On for SAP Business Suite powered by SAP HANA

With the SAP Simple Finance add-on for SAP Business Suite powered by SAP HANA, you can adapt planning applications to suit your needs. There are
adaptation possibilities from top to bottom: from the UI to the back end, from end user to IT, from easy to advanced, for the following.
Analysis workbooks
BEx queries
Planning sequences
Aggregation levels
InfoProviders

PUBLIC Page 3 of 7
2014 SAP SE or an SAP affiliate company. All rights reserved.
Activities

Adapting Analysis Workbooks


You can adapt analysis workbooks to do the following:
Create user-specific or global variants for the variable screen
Adapt the layout of the workbook (for example, reduce the selection parameter area at the top)
Format the layout by modifying the SAP cell styles
Remove buttons that are not needed
Add additional buttons for planning sequences
Add additional queries on other worksheets
Insert charts

Add a New Workbook


1. Start Analysis Office under Programs Analysis for Microsoft Excel and open a workbook that was defined earlier.
2. In the File menu, select Analysis and press the Save Workbook to the SAP NetWeaver platform button.
3. In the Save Documents dialog box, select Role in the View field, and enter a name and a description.
After saving the assignment, all users who have this role are able to capture plan data using the new workbook.

For more information about business intelligence content (BI content) and creating workbooks, see the SAP Help Portal at http://help.sap.com Analytics
Business Intelligence Analysis SAP Business Objects Analysis for MS Office End-User Information User Guide

Adapting BEx Queries


You can change the delivered queries, copy and adapt them, or create new ones from scratch. Typical changes that are required include the following:
Add additional columns
Remove columns
Change sequence of row characteristics
Use other variables
Change settings such as sort order and hierarchy settings

For more information about the BEx Query Designer, see the SAP Help Portal at http://help.sap.com SAP NetWeaver SAP NetWeaver Platform
SAP NetWeaver 7.4 Application Help SAP NetWeaver Business Warehouse Analyzing and Planning Data

Adapting Planning Sequences


A planning sequence consists of one or more steps, where each step contains a filter and a planning function.
Change the delivered planning sequences, functions, and filters, copy and adapt them, or create new ones from scratch.
You can configure planning functions such as copy, distribute by reference, distribute by keys, revaluate, forecast, formulas, and currency translation.

For more information, see the SAP BW planning modeler documentation athttp://help.sap.com SAP NetWeaver SAP NetWeaver Platform SAP
NetWeaver 7.4 SAP NetWeaver Business Warehouse Analyzing and Planning Data BW Integrated Planning Planning Modeler

Adapting Aggregation Levels


Add additional characteristics to an aggregation level. This is used especially in the area of profitability analysis.

For more information, see the SAP BW planning modeler documentation at http://help.sap.com SAP NetWeaver SAP NetWeaver Platform SAP
NetWeaver 7.4 SAP NetWeaver Business Warehouse Analyzing and Planning Data BW Integrated Planning Planning Modeler

Adapting the InfoProvider


The delivered InfoProviders (the InfoCube /ERP/SFIN_R01, the VirtualProvider /ERP/SFIN_V01 and the MultiProvider /ERP/SFIN_M01) contain a set of
characteristics that is typically needed for financial planning. However, in the area of market segment planning (CO-PA), customers typically need additional,
customer-specific fields.
To include these fields in sFIN planning, perform the following steps;
Assign the needed characteristics to the CO-PA operating concern if required and extend the corresponding HANA views. Refer to the document
Adapting the HANA Views to a New Operating Concern.
Generate missing InfoObjects and master data HANA views corresponding to the new CO-PA operating concern fields. Include the new InfoObjects into
the VirtualProvider and maintain the mapping to the new HANA view fields. Refer to the document Adapting Actual Reporting in the SAP Smart Finance
Add-On for SAP Business Suite powered by SAP HANA.
Include the relevant InfoObjects into the InfoCube /ERP/SFIN_R01 for plan data
Include the new InfoObjects in the MultiProvider
Adapt or create aggregation levels and queries

1.1.2 Adapting Actual Reporting in the SAP Simple Finance Add-


On for SAP Business Suite powered by SAP HANA

The delivered operating concern SFIN contains a set of characteristics that is typically needed for financial reporting. However, in the area of market segment
reporting (CO-PA), customers often need additional characteristics that they can define themselves and add to their operating concern. With the Financials
Add-On for SAP Business Suite powered by SAP HANA , you can adapt the reporting queries on actuals to suit your needs (specifically, queries
/ERP/SFIN_V01_Q2xxx based on virtual provider /ERP/SFIN_V01).

PUBLIC Page 4 of 7
2014 SAP SE or an SAP affiliate company. All rights reserved.
Note
This adaptation is also a precondition for using your new fields in financial planning. For more information, see Adapting Planning Applications in the SAP
Smart Finance Add-On for SAP Business Suite powered by SAP HANA.

Procedure
1. Assign new characteristics to your CO-PA operating concern and extend the corresponding HANA views, if required. Refer to the document Adapting the
HANA Views to a New Operating Concern, especially step 4.
2. In transaction FCOM_GEN, generate missing InfoObjects and HANA views corresponding to the new CO-PA operating concern fields.
You can either generate new InfoObjects for the CO-PA fields or assign existing ones. The generated InfoObjects belong to the namespace /RKE/ and
also benefit from in-memory planning as they have a predefined HANA view for master data access generated in package system-
local.sap.erp.sfin.co.pl.
For more information, see the documentation of the SAP BW Data Warehousing Workbench at http://help.sap.com under SAP NetWeaver SAP
NetWeaver Platform SAP NetWeaver 7.4 Application Help SAP NetWeaver Business Warehouse Integration, Storage and Management of
Data Data Storage and Data Flow Modeling Enterprise Data Warehouse Layer Creating InfoProviders .
Existing InfoObjects with other data access types can be used too, but in that case all planning functions are executed in ABAP and not within HANA.
Of course, you can also create these HANA views yourself. Package sap.erp.sfin.co.pl contains the calculation views that belong to SAPs
/ERP/* InfoObjects. These master data calculation views typically join a master data table with its corresponding text table. As BW always needs the
characteristic value # (not assigned), this entry has to be added unless it is part of the master data table. If you want to define your own InfoObjects
based on HANA views, you can create your own Calculation views in a similar way.
For more information, see the documentation for SAP HANA models under SAP In-Memory Computing SAP HANA SAP HANA Platform SPS
07 Modeling Information SAP HANA Modeling Guide 6.1 Creating Views .
Generate missing InfoObjects and HANA views as follows:
1. Use transaction FKOM_RKEGEN to open the mapping tool.
For more information, see InfoObject Assignment for Operating Concern.
2. Select your operating concern and click Continue .

Note
Only account-based operations are allowed as input. The tool displays a list of CO-PA characteristics and proposes an equivalent BW
characteristic for each one.

3. In the field list, check your new characteristics. They should have a yellow generation status and the proposed InfoObject should be
/RKE/<field name>. If the proposal does not meet your requirements, click Change next to the entry you want to change and assign your
own choice to the field name of the InfoObject.
The proposed characteristic can be one of the following:
A delivered characteristic in the /ERP/ namespace
A generated or yet-to-be generated characteristic in the /RKE/ namespace
A customer-specific BW characteristic if the customer already has assigned a BW InfoObject to a CO-PA characteristic

Note
Keep in mind that you are changing the assignment for the field name for all operating concerns in the system.

Accept your changes to close the dialog box.


4. Finally, generate missing InfoObjects and corresponding HANA views by pressing F8 .
3. In transaction RSA1, include the new InfoObjects into the VirtualProvider /ERP/SFIN_V01 and maintain the mapping to the new HANA view fields using
the context menu on the assigned InfoObject.
4. Adapt queries (such as /ERP/SFIN_V01_Q2xxx) using the query designer. For more information about the BEx Query Designer, see the SAP Help
Portal at http://help.sap.com under SAP NetWeaver SAP NetWeaver Platform SAP NetWeaver 7.4 Application Help SAP NetWeaver
Business Warehouse Analyzing and Planning Data .

1.1.2.1 InfoObject Assignment for Operating Concern

You use report FCOM_RKEGEN to set up your Business Warehouse (BW) objects to allow reporting on actual values in the context of Next Generation Financial
Planning. It lets you map BW characteristics to CO-PA characteristics and also lets you generate BW characteristics if no suitable BW characteristics exist
yet for some CO-PA characteristics.
You enter the report by choosing an account-based operating concern. The system then proposes a mapping between the characteristics of your operating
concern and BW characteristics.
For each characteristic of your operating concern, this proposed BW characteristic can be one of the following:
A delivered characteristic in /ERP/ namespace
A generated or yet to be generated characteristic in/RKE/ namespace
If the customer has already assigned a BW characteristic to a CO-PA characteristic, a customer-specific BW characteristic
You can change this proposal to suit your own needs (see below).
You can then use these BW characteristics in your BW InfoProvider for Financials Actuals.You must also ensure that the HANA view underlying your
InfoProvider contains a corresponding field that is mapped to the characteristic in the InfoProvider.

Activities
1. Use transaction FCOM_REGEN to open the mapping and generation tool.
2. Select an operating concern and click Continue .

PUBLIC Page 5 of 7
2014 SAP SE or an SAP affiliate company. All rights reserved.
Note that for the first version, only account-based operations are allowed as input. The tool displays a list of CO-PA characteristics and proposes an
equivalent BW characteristic for each one.
3. Unless the proposal meets your requirements, click Change next to the entry that you want to change and assign your own choice there to the field
name of the InfoObject.

Caution
By doing this, you change the assignment for the field name for all operating concerns in the system.

4. Press the Generate button or press F8 . This saves the assignment and generates BW characteristics that do not yet exist in the system. You can
identify these characteristics by the red LED icon in the Generation Status column.
BW characteristics with a green LED already exist and do not need to be generated. BW characteristics with a yellow LED already exist, but will be
regenerated for one of the following reasons:
The characteristics do not yet exist in the logon language
The description of the characteristics has changed
The characteristics have a master data access type that is not SAP HANA View
Display attributes were added or removed
If the characteristic has master data, the system also creates corresponding master data views in the HANA database in package system-
local.sap.erp.sfin.co.pl that are used by the BW characteristics for master data access.
5. View the application logs by pressing the Display Logs button or by pressing Ctrl + F1 .
6. Jump to the Data Warehousing Workbench by pressing the DW Workbench button or pressing Ctrl + F1 ,

1.1.3 Adapting the HANA Views to a New Operating Concern

The standard operating concern provided with SAP Simple Finance is SFIN. If this operating concern meets your needs, you can use it as is. However, you
should not make any changes to operating concern SFIN.

Caution
If you make changes to operating concern SFIN, your changes will be overwritten by the next upgrade. If operating concern SFIN does not meet your
needs, you can create a new operating concern in your own namespace (not in the SFIN namespace).

Note
Due to technical dependencies in reporting, if you create a new operating concern make sure it contains all characteristics used in the standard operating
concern SFIN. If necessary, add any missing characteristics to your new operating concern.

If you create a new operating concern, you need to adapt the HANA views for the logical document so that you can see the data from your new operating
concern. The relevant components for the logical document areas follows:
HANA calculation view COPA_DOC
HANA calculation view FICOPA_DOC_SFIN for the document entry view. This view joins the data from CO-PA for the delivered operating concern SFIN
Report FCO_LOGICAL_DOCUMENT, which is also part of the delivery.
These new views are stored in package sap.hba.sfin700

Procedure
Carry out the following steps to adapt the HANA views for the logical document:
1. Install the SAP HANA studio locally. You can find the installation guide for the SAP HANA studio at http://help.sap.com/ hana under SAP HANA
Appliance Software. The documentation for the SAP HANA studio is located at http://help.sap.com/hana/hana_dev_en.pdf (chapter 6).
2. Copy the HANA calculation view sap.hba.sfin700/FICOPA_DOC_SFIN to a new calculation view named ZFICOPA_DOC_xxxx, where xxxx is the
name of your new operating concern.
Your new operating concern must be in its own package.
3. Delete the assignment of the delivered calculation view to table CE4SFIN. This table stores all CO-PA characteristics and their object numbers for the
operating concern SFIN.
To delete the assignment to table CE4SFIN, select the projection node Op_Concern_SFIN. In the Details area of your screen, select table
CE4SFIN. To delete this table, click the Delete button. You will need to confirm twice that you want to delete the table. You can ignore the warnings
about the use of the fields in other nodes.
4. After you have deleted the assignment to table CE4SFIN, create a new assignment to your table CE4xxxx, where xxxx is name of your new operating
concern. Table CE4xxxx stores all CO-PA characteristics for your new operating concern. Drag table CE4xxxx to the projection node
Op_Concern_SFIN. To do this you need to search for the table in the catalog of your database schema.
5. In the Details area of your screen for the projection node Op_Concern_SFIN, activate the fields from table CE4xxxx that you want to use for
reporting purposes.

Note
Always activate the technical fields MANDT, ERKRS, and PAOBJNR.

6. You now need to join fields for the projection nodes Op_Concern_SFIN and Accounting_Document to achieve the link between CO and CO-PA.
Do this by selecting the join node FI_CO_PA and entering the following join conditions
MANDT <-> MANDT
CE4KEY <-> PAOBJNR
ERKRS <-> ERKRS
7. Activate all required fields (without the technical fields MANDT, ERKRS, and PAOBJNR) for projection node Op_Concern_SFIN in the detail view of the

PUBLIC Page 6 of 7
2014 SAP SE or an SAP affiliate company. All rights reserved.
join node FI_CO_PA.
8. Activate all required fields of the join node FI_CO_PA in the detailed view of the Aggregation aggregation node .
9. Select all required fields in the Semantics detailed view as attributes.
10. Activate the new HANA calculation view.
11. Modify the ABAP report FCO_LOGICAL_DOCUMENT so that the new view ZFICOPA_DOC_xxxx is used instead of
sap.hba.sfin700/FICOPA_DOC_SFIN.
12. Delete the link between the HANA calculation view sap.hba.sfin700/FICOPA_DOC and the view sap.hba.sfin700/FICOPA_DOC_SFIN.
Then create a new link so that the HANA calculation view sap.hba.sfin700/FICOPA_DOC is linked to your new view ZFICOPA_DOC_xxxx.
To change this link, select the projection node FICO_for_generic_OpConcern. In the detailed view, select the view FICOPA_DOC_SFIN. To delete
this view, click the Delete button. You will need to confirm twice that you want to delete the view. You can ignore the warnings about the use of the
fields in other nodes.
Now connect the view FICOPA_DOC to your new view FICOPA_DOC_xxxx.
Drag the view ZFICOPA_DOC_xxxx to the projection node FICO_for_generic_OpConcern. Select all fields of the view. Then choose the
Propagate to Semantics function in the context menu.
13. In the detailed view for the Semantics node, change the type of TIMESTMP field to measure with aggregation method MAX.
14. For reporting and planning purposes, repeat all steps above for the views with the same names from package sap.erp.sfin.co.pl. You also need
to change the BW objects that use the view sap.erp.sfin.co.pl/COPA_DOC as explained in the documentation Adapting Actual Reporting in the
SAP Smart Finance Add-On for SAP Business Suite powered by SAP HANA and Adapting Planning Applications in the SAP Simple Finance Add-On for
SAP Business Suite Powered by SAP HANA.

1.2 Planning View Generation (Optional)

This activity is optional.


You can use report FCOM_GEN_VIEW to generate a dummy proxy view within the financials add-on for SAP Business Suite powered by SAP HANA package
sap.hba.sfin700,

Financial planning data in SAP Business Suite powered by SAP HANA is stored in the Business Warehouse (BW) real-time InfoCube /ERP/SFIN_R01 and
could be used by other applications. It would be possible to access plan data by providing an analytic HANA view within the SAP Business Suite powered by
SAP HANA Financial Planning content. However, this content is not available before content activation, so external SAP applications cannot rely on the
existence of this HANA view, resulting in generation errors.
The dummy proxy view that you generate in package sap.hba.sfin700 is simply an interface for external applications and does not provide any data. After
content generation, the dummy proxy is exchanged for a full proxy view that delivers plan data.

Activities
1. Activate the BI bundle in Customizing for Planning under Controlling General Controlling Planning Activate BI Bundle for Planning .
2. Generate the planning view in Customizing for Planning under Controlling General Controlling Planning Generate Planning View . Click
Execute ( F8 ) to do the following:
Generate the HANA plan data view FCOM_PLAN_DATA for the InfoCube /ERP/SFIN_R01 in package system-local.sap.erp.sfin-co-pl.
Generate the proxy view FCO_PLAN_PROXY, replacing the original dummy proxy in package sap.hba.sfin700.

Caution
If you reimport package sap.hba.sfin700 at a later time, you must repeat step 2. The original dummy proxy is also reimported, so unless you generate
the planning view again, generation errors can occur.

PUBLIC Page 7 of 7
2014 SAP SE or an SAP affiliate company. All rights reserved.