You are on page 1of 15

Configuration Guide

Document version:1.0 2015-03-30

PUBLIC

Configuration Guide for SAP Simple Finance for SAP


Business Suite powered by SAP HANA

Document History

Caution
Before you start the implementation, make sure you have the latest version of this document. You can find the
latest version at the following location: service.sap.com/erp-inst.
The following table provides an overview of the most important document changes.
Table 1

Version

Date

Description

1.0

2015-03-30

Initial version of the Configuration Guide for SAP Simple Finance Add-On for Business Suite
powered by SAP HANA

PUBLIC
Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.

Configuration Guide for SAP Simple Finance for SAP Business Suite powered by SAP HANA
Document History

Content

About this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Operating Concern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

BI Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Configuration Guide for SAP Simple Finance for SAP Business Suite powered by SAP HANA
Content

PUBLIC
Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.

PUBLIC
Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.

Configuration Guide for SAP Simple Finance for SAP Business Suite powered by SAP HANA

About this Document

This document is the single source of information for the configuration of specific functions of the SAP Simple
Finance add-on for SAP Business Suite powered by SAP HANA.
It covers the following topics:

Operating Concern

BI Content

Note
You can find the most current version of this document on SAP Service Marketplace at service.sap.com/erpinst. We strongly recommend that you use the document available there. The guide will be updated according
to updates of the software.

Configuration Guide for SAP Simple Finance for SAP Business Suite powered by SAP HANA
About this Document

PUBLIC
Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.

Operating Concern

As of SAP Simple Finance Add-On 2.0 SPS 00 for SAP Business Suite powered by SAP HANA, the Controlling
(CO) and Financial Accounting (FI) components have been merged. Cost and revenue information - stored in the
universal journal entry - is always up to date and permanently reconciled with the income statement. The new
Simplified Profitability Analysis is based on the universal journal entry as well. Therefore, the use of accountbased profitability analysis is a prerequisite.

Note
Costing-based profitability analysis is still available and you can use both types of profitability analysis in
parallel. However, account-based profitability analysis is the default solution. With account-based profitability
analysis, any revenue posting or cost of goods sold posting is updated under the relevant account and assigned
to the correct market segment characteristics.
In SAP HANA, profitability segment characteristics arent summarized anymore, as this profitability analysis
feature has become obsolete.
If you have not yet used Profitability Analysis, you can find detailed information about the necessary configuration
in the documentation for Profitability Analysis (CO-PA) and in the release notes of the finance add-on. If you are
already using costing-based profitability analysis, you must activate the account-based version and perform some
Customizing steps. These Customizing steps are also required if you have already used account-based
profitability analysis. For more information, see the Migration Guide on SAP Help Portal at help.sap.com/sfin200
Installation and Upgrade Information Migration Guide .

PUBLIC
Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.

Configuration Guide for SAP Simple Finance for SAP Business Suite powered by SAP HANA
Operating Concern

BI Content

The SAP Simple Finance add-on for SAP Business Suite powered by SAP HANA leverages the latest features of BI
Content and integrated business planning applications. The following configuration steps need to be performed in
your finance add-on system:
1.

Configure the BI client for your system.

2.

Activate the BI Content and required business functions.

For detailed step-by-step instructions, see SAP Note 1972819. For detailed information about Integrated Business
Planning for Finance, see SAP Note 2081400.

BI Client Configuration
To use operational data provisioning and classic InfoSets in BI tools, complete the basic configuration for SAP
NetWeaver Business Warehouse on your system. Complete the following settings in Customizing under
Controlling General Controlling Planning Setup for Planning :
1.

Select one client from the finance add-on system as the BI client (typically the productive client) and then
define and assign a logical system to this client.

2.

Complete the setting in Basic Configuration for Operational Analytics (RSRTS_ACTIVATE_R3IS) transaction.

3.

Using the Transport Organizer Tools (SE03) transaction, under

Administration

Set System Change

Option , enter the global setting modifiable for namespaces with the prefixes /BI0/ (Generation
Namespace for SAP BI Content) and /BIC/ (Business Information Warehouse: Customer Namespace).

BI Content and Business Function Activation


BI Content bundles contain BW Queries, Operational Data Providers (ODPs), and other BI Content objects. The
concept of BI Content bundles simplifies the activation of all required objects so there is no need to perform the
more cumbersome procedure of collecting and activating objects individually.
Activate the BI Content bundles outlined in the following table using the BI Content Activation Workbench
(transaction BSANLY_BI_ACTIVATION):
Table 2

Business Category

Content Bundle Technical

Content Bundle Name

Name

Required Business
Functions (Transaction
SWF5)

99

FINS_REP_GL_LITB

sFIN GL Reporting: Line Item

Browser etc.
03

/ERP/SFIN_PLANNING

CO Planning

Project planning:

FIN_CO_CCMGMT and
OPS_PS_CI_1
Cost center planning:

FIN_CO_CCPLAN
For more information, see
SAP Note 1836149.

Configuration Guide for SAP Simple Finance for SAP Business Suite powered by SAP HANA
BI Content

PUBLIC
Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.

Business Category

Content Bundle Technical

Content Bundle Name

Name

Required Business
Functions (Transaction
SWF5)

03

/ERP/SFIN_PLANNING

Simplified Financials Planning Project planning:

FIN_CO_CCMGMT and
OPS_PS_CI_1
Cost center planning:

FIN_CO_CCPLAN
For more information, see
SAP Note 1836149.
03

FIN_REP_SIMPL_4

Reporting Financials 4

FIN_REP_SIMPL_4

On the activation screen, specify the RFC connection for your BI client (if the BI client is the current client, you can
specify RFC destination NONE), set Treatment of Already Active Content Objects flag to Copy, and activate the flag
Install all Collected Objects.
Check the activation log to verify there are no errors.

Note
You can activate other options later on even if you have changed the content delivered by SAP by selecting the
Match checkbox. For content objects delivered by SAP, you are asked if you want to merge the new content
version with the active object. Deselect Install all Collected Objects if you only want to activate the new SAPdelivered objects. Automatic choices between Match and Copy depend on the object type (for more
information, see flag MERGEFL in table RSTLOGOPROP).
You must activate the BI Content in each system (development, test, and production) separately. It is part of the
system setup, not part of application customizing.
Activate the business functions based on the Integrated Business planning scenario you want to use.

Data Determination Using BW Queries


The following Web Dynpro applications use the Analytics Component of the Floorplan Manager (FPM):

Accounts List in Chart of Accounts

Receivables (G/L View)

Payables (G/L View)

Work Analysis

WIP Analysis

Income Statement by Market Segment

This FPM component enables you to use BW functions to filter data for drilldown and key/text display. The
graphic below depicts how the data is determined:
For an overview with the technical names of the BI Content objects for the individual reports, see the information
at the end of this chapter.

PUBLIC
Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.

Configuration Guide for SAP Simple Finance for SAP Business Suite powered by SAP HANA
BI Content

Figure1

The Web Dynpro application calls a BW query:


The query contains settings for which characteristics and key figures are to be initial in the lines or columns of the
report. Furthermore, properties (such as the representation of key/text, aggregation behavior, and so on) can be
specified for the characteristics and key figures. Additionally, you make settings in the query for the
characteristics to be shown as further drill-down options and which key figures can also be displayed. You can use
filters as fixed values or variables as selection options in the report. You can also define properties for variables
(such as possible selection options or handling by an SAP Exit).
A query in turn needs an InfoProvider for data retrieval. An Operational DataProvider (ODP) or a MultiProvider is
used as an InfoProvider:

ODP as InfoProvider
In the ODP, all attributes available to the query are exposed. Here, you can specify whether attributes or key
figures are normal, and the semantics that apply to the respective attributes (for example, the fiscal year,
fiscal period, and so on). Furthermore, mapping to other master data ODPs is done in the ODP to make
comprehensive attribute texts and hierarchies available in the report. The authorization objects to be taken
into account are also entered in the ODP.
A DataSource is used as a source. This specifies which attributes are available for exposure in the ODP. The
basis for this DataSource is an extract structure that contains the set of all fields available for the report. This
set is a subset of the output fields of the SAP HANA view that is ultimately responsible for data procurement.
The DataSource contains settings for which fields of the extract structure in the ODP are available as
attributes, and which are key fields.
A BAdI is used to enable data procurement is triggered by a HANA view and not classically by the
DataSource. By implementing BAdI RODPS_ESH_HANA_NAME_MAPPER (Alternative SAP HANA Column View
for ESH ODP Runtime), all fields of the DataSource structure are mapped to the fields of the HANA views
used. Finally, the request from the ODP to the HANA view used is forwarded.

Configuration Guide for SAP Simple Finance for SAP Business Suite powered by SAP HANA
BI Content

PUBLIC
Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.

If you want to use your own BI Content objects instead of those delivered by SAP, pay particular attention to
the Enhancement of BAdI RODPS_ESH_HANA_NAME_MAPPER chapter.

MultiProvider as InfoProvider
In the MultiProvider, all attributes available to the query are exposed. Here, you can specify whether
attributes or key figures are normal, and the semantics that apply to the respective attributes (for example,
the fiscal year, fiscal period, and so on). Furthermore, mapping to other master data views is done in the
MultiProvider to make comprehensive attribute texts and hierarchies available in the report.

The technical names of the BI Content objects for the individual reports are listed here:

Accounts List in Chart of Accounts


Table 3

Query

0FIS_GL_ACC_Q0001 and 0FIS_GL_ACC_Q0002

ODP

0FIS_GL_ACC

DataSource

0FIS_GL_ACCOUNT

Extract Structure

0FIS_GL_ACC

SAP HANA View

sap.hba.sfin700/
GLAccountListInChartOfAccounts

Receivables (G/L View)


Table 4

Query

0FIS_GL_AR_Q0001

ODP

0FIS_GL_APAR

DataSource

0FIS_GL_APAR

Extract Structure

0FIS_GL_APAR

SAP HANA View

sap.hba.sfin700/
ProfitCenterReceivablePayable

Payables (G/L View)


Table 5

Query

0FIS_GL_AP_Q0001

ODP

0FIS_GL_APAR

DataSource

0FIS_GL_APAR

Extract Structure

0FIS_GL_APAR

SAP HANA View

sap.hba.sfin700/
ProfitCenterReceivablePayable

Work Analysis
Table 6

Query

10

/ERP/SFIN_V10_Q0001

PUBLIC
Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.

Configuration Guide for SAP Simple Finance for SAP Business Suite powered by SAP HANA
BI Content

MultiProvider

/ERP/SFIN_V10

WIP Analysis
Table 7

Query

/ERP/SFIN_V11_Q0001

MultiProvider

/ERP/SFIN_V11

Income Statement by Market Segment


Table 8

Query

/ERP/SFIN_M01_Q1000

MultiProvider

/ERP/SFIN_M01

Enhancement of BAdI RODPS_ESH_HANA_NAME_MAPPER

Note
You must pay attention to the information in this document if you want to use your own BI content objects for
determining data for one of the following reports:

Accounts List in Chart of Accounts

Receivables (G/L View)

Payables (G/L View)

Naming Convention for ODPs


You use the Business Add-In (BAdI) RODPS_ESH_HANA_NAME_MAPPER to map an ODP to a HANA Calculation
View. To be able to use this BAdI for your ODPs too, SAP has made the generic implementation
ES_IMP_FIS_HANA_NAME_MAPPER available. This implementation is assigned to the filter areas 0FISZ00000 to
0FISZ99999. Your own ODPs must therefore have a name in this area for the generic implementation to run (for
example, 0FISZ00054).

Assigning an ODP to a HANA View and its Fields


1.

Call transaction SM34.

2.

Enter view cluster FISVC_MAP_ODP and select Maintain.

3.

Choose New Entries.


On the first level, assign your ODP to a HANA View. To enter the following data, you may need to scroll to the
right in the table:

Name of your ODP

Name of the HANA View to be assigned to, including package


Example:
For the view MyView in package tmp.customer.odp, enter the name as tmp.customer.odp/MyView.

Database structure containing the runtime object of the HANA View. For graphical Calculation Views, this
is _SYS_BIC.

Configuration Guide for SAP Simple Finance for SAP Business Suite powered by SAP HANA
BI Content

PUBLIC
Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.

11

Client Fieldname is the field of the HANA View corresponding to the client. HANA Views are clientindependent, but ODPs must be executed for each client, so the HANA View field that represents the
client needs to be known.

Name of the database connection to the HANA database. As standard, you can enter DEFAULT here to
use the default database connection. However, you can also use another connection of table DBCON for
scenarios with a secondary database connection.

4.

Data Dictionary (DDIC) structure used as the source of the ODP.

On the second level, you can define the field assignment between the ODP and HANA View. If the field names
in the ODP and the HANA View match, you do not need to make any entries; if this is not the case, you must
enter the following data:

Field name in the ODP

Field name in the HANA View

Restriction if the HANA View field is linked to an import parameter or to a variable. Then enter the input
parameter as defined in the PLACEHOLDER instructions for SQL Select.
Example:
The HANA View field OpenOnKeyDate is assigned to the ODP field KEYDAT. This field is linked to import
parameter P_OpenOnKeyDate. The SQL statement of the HANA View is as follows:
select * from <Schema><HANAView>('PLACEHOLDER' = ('$$P_OpenOnKeyDate$
$','20140101')
In this case, enter $$P_OpenOnKeyDate$$ as a restriction for the HANA View field OpenOnKeyDate.

5.

Save your entries.

More Information
For more information on activating BI Content, see SAP Help Portal at help.sap.com SAP ERP
Cross-Application Functions Analytics Infrastructure BI Content Activation Workbench .

12

PUBLIC
Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.

SAP ERP

Configuration Guide for SAP Simple Finance for SAP Business Suite powered by SAP HANA
BI Content

Typographic Conventions

Table 9

Example

Description

<Example>

Angle brackets indicate that you replace these words or characters with appropriate entries
to make entries in the system, for example, Enter your <User Name>.

Example

Example

Arrows separating the parts of a navigation path, for example, menu options

Example

Emphasized words or expressions

Example

Words or characters that you enter in the system exactly as they appear in the
documentation

www.sap.com

Textual cross-references to an internet address

/example

Quicklinks added to the internet address of a homepage to enable quick access to specific
content on the Web

123456
Example

Hyperlink to an SAP Note, for example, SAP Note 123456

Words or characters quoted from the screen. These include field labels, screen titles,
pushbutton labels, menu names, and menu options.

Example

Cross-references to other documentation or published works

Output on the screen following a user action, for example, messages

Source code or syntax quoted directly from a program

File and directory names and their paths, names of variables and parameters, and
names of installation, upgrade, and database tools

EXAMPLE

Technical names of system objects. These include report names, program names,
transaction codes, database table names, and key concepts of a programming language
when they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE

Keys on the keyboard

Configuration Guide for SAP Simple Finance for SAP Business Suite powered by SAP HANA
Typographic Conventions

PUBLIC
Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.

13

14

PUBLIC
Copyright 2015 SAP SE or an SAP affiliate company.
All rights reserved.

Configuration Guide for SAP Simple Finance for SAP Business Suite powered by SAP HANA

www.sap.com

Copyright 2015 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
or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks
of SAP SE (or an SAP affiliate company) in Germany and other
countries. Please see www.sap.com/corporate-en/legal/copyright/
index.epx#trademark for additional trademark information and
notices.
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 or an SAP affiliate company
for informational purposes only, without representation or warranty
of any kind, and SAP SE or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only
warranties for SAP SE or SAP affiliate company 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.
In particular, SAP SE or its affiliated companies have no obligation to
pursue any course of business outlined in this document or any
related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and
SAP SE's or its affiliated companies' strategy and possible future
developments, products, and/or platform directions and
functionality are all subject to change and may be changed by SAP
SE or its affiliated companies at any time for any reason without
notice. The information in this document is not a commitment,
promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various
risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place
undue reliance on these forward-looking statements, which speak
only as of their dates, and they should not be relied upon in making
purchasing decisions.