Reference Guide

May 2015 English

SAP Simple Finance Implementation with SAP Best Practices Baseline V3.607

2

Customer

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

SAP Simple Finance Implemenation with SAP Best Practices Baseline V3.607

Typographic Conventions

Typographic Conventions

Type Style Description

Example Words or characters quoted from the screen. These include field names, screen titles,

pushbuttons labels, menu names, menu paths, and menu options.

Textual cross-references to other documents.

Example Emphasized words or expressions.

EXAMPLE Technical names of system objects. These include report names, program names,

transaction codes, table names, and key concepts of a programming language when they

are surrounded by body text, for example, SELECT and INCLUDE.

Example Output on the screen. This includes file and directory names and their paths, messages,

names of variables and parameters, source text, and names of installation, upgrade and

database tools.

Example Exact user entry. These are words or characters that you enter in the system exactly as they

appear in the documentation.

Variable user entry. Angle brackets indicate that you replace these words and characters

with appropriate entries to make entries in the system.

EXAMPLE Keys on the keyboard, for example, F2 or ENTER .

SAP Simple Finance Implemenation with SAP Best Practices Baseline V3.607

Document History

2015 SAP SE or an SAP affiliate company. All rights reserved. 3

Document History

Revision Date Change

1.0 Preview version

1.1 1. release version

4

SAP Simple Finance Implemenation with SAP Best Practices Baseline V3.607

2015 SAP SE or an SAP affiliate company. All rights reserved. Table of Contents

Table of Contents

1 Introduction 5 1.1 Purpose of this document 5 1.2 Scope of this document 5 1.3 Out of scope 5

2 Preparation activities before the installation of the SAP Simple Finance add-on 7

3 Migration of Customizing 9 3.1 Preparations and Migration of Customizing 9

3.1.1 Preparations and Migration of Customizing for the General Ledger 9 3.1.2 Preparations and Migration of Customizing for Asset Accounting 10 3.1.3 Preparations and Migration of Customizing for Controlling 11

3.2 Migration 11 3.2.1 Migration of Cost Elements and Customizing 12 3.2.2 Technical Check of Transaction Data 13 3.2.3 Migration - Enrichment of Data 13 3.2.4 Migration of Line Items into New Data Structure 14 3.2.5 Migration of Balances 14 3.2.6 Complete Migration 15 3.2.7 Activities after Migration 16

4 Additional Customizing, Baseline Scenarios Analyzing, SAP Simple Finance Fiori apps Implementation 18

4.1 Additional Customizing 18 4.2 Baseline scenario analyzing 19 4.3 SAP Simple Finance Fiori App 21

5 Appendix 22 5.1 Preparation activities before the installation of the SAP Simple Finance add-on 22

5.1.1 Closing activities in past posting periods 22 5.1.2 Preparation activities prior to the installation 22

SAP Simple Finance Implemenation with SAP Best Practices Baseline V3.607

Introduction

2015 SAP SE or an SAP affiliate company. All rights reserved. 5

1 Introduction

1.1 Purpose of this document

This guide explains how to leverage SAP Best Practices Baseline content (http://help.sap.com/bestpractices)

V3.607 for implementation of SAP Simple Finance, on-premise edition 1503 support package stack 1505 - SAP

Accounting powered by SAP HANA.

Note that the activities recorded in this document represent the status as of May 2015. For the most up-to-date

Simple Finance information, refer to the standard SAP Simple Finance documentation service.sap.com/erp-inst.

Before you decide to implement SAP Simple Finance, check the Simple Finance release note

http://help.sap.com/sfin200 for functional scope and compatibility.

1.2 Scope of this document

Since the SAP Best Practices Baseline content was developed for SAP ERP on HANA technical landscape, the

following approach is necessary:

Step 1) Install an SAP ERP on HANA landscape, referring to the corresponding Quick Guide of the SAP Best

Practices Baseline package.

Step 2) Deploy the selected SAP Best Practices Baseline package without transactional data.

Step 3) Upgrade and install SAP Simple Finance.

Step 4) Execute the Simple Finance migration of customizing; make additional customizing adjustment as well as

process adjustment.

For the steps listed above:

Refer to the individual SAP Best Practices Baseline package for step 1) and step 2) at

http://help.sap.com/bestpractices

Refer to Simple Finance Administrator Guide http://help.sap.com/sfin200 for step 3).

This guide provides details for step 4) based on the experience of migrating the SAP Best Practices Baseline

content for China V3.607, Germany V3.607 and US V3.607 to SAP Simple Finance, on-premise edition 1503

support package stack 1505.

1.3 Out of scope

This document focuses on SAP Accounting powered by SAP HANA. The full function for SAP Cash Management

powered by SAP HANA and SAP Integrated Business Planning is not covered.

This document does not describe SAP Simple Finance in SAP Public Cloud and SAP Managed Cloud scenarios.

This document does not describe a generic implementation of the SAP Simple Finance in a SAP ERP on HANA

landscape.

http://help.sap.com/bestpracticeshttp://service.sap.com/erp-insthttp://help.sap.com/sfin200http://help.sap.com/bestpracticeshttp://help.sap.com/sfin200

6

2015 SAP SE or an SAP affiliate company. All rights reserved. Introduction

Furthermore, it does not describe how to upgrade a previous version of SAP Simple Finance to SAP Simple

Finance, on-premise edition 1503 support package, stack 1505.

The activities presented in this document do not include how to migrate customer's data from a legacy system to

an SAP ERP system with SAP Simple Finance activated. It neither deals with custom code.

This guide does not provide a best practice for all countries and industries that might be implemented in an SAP

ERP system via the SAP Best Practices content activation.

SAP Simple Finance Implemenation with SAP Best Practices Baseline V3.607

Preparation activities before the installation of the SAP Simple Finance add-on

2015 SAP SE or an SAP affiliate company. All rights reserved. 7

2 Preparation activities before the installation of the SAP Simple Finance add-on

After you have performed steps 1) and 2) described in 1.2, you have a pre-configured SAP ERP on HANA

landscape, without FI/CO transactional data.

You need to perform certain preparation activities in the SAP ERP System before the technical installation of the

SAP Simple Finance add-on, as shown in the table below:

IMG Activities Expected Outcome

Check if business function EA-FIN is active. Business function EA-FIN should be active.

Check if the report RASFIN_MIGR_PRECHECK is

available in your SAP ERP system or implement note

1939592 (it contains the report). Run report

RASFIN_MIGR_PRECHECK in all your system.

Report RASFIN_MIGR_PRECHECK runs and checks

the customizing settings in the customizing-, test- and

productive system.

Check and activate the business functions

FIN_AA_PARALLEL_VAL and FIN_AA_CI_1.

Business functions FIN_AA_PARALLEL_VAL and

FIN_AA_CI_1 should be active.

Run the report

ZFINS_MIG_PRECHCK_CUST_SETTNGS in all your

SAP ERP systems (this report is contained in SAP

note 2129306)

The report ZFINS_MIG_PRECHCK_CUST_SETTNGS

is executed in the customizing-, test- and productive

system.

Example of 2 error messages:

For some company codes, currencies were

assigned to non-leading ledger but not to the

leading ledger it is necessary to correct the currency assignment for all company codes, even

if they are not actively used;

The fiscal year variant assigned to the company

code CN01 was different from the one assigned to

the controlling area the fiscal year variant in FI and CO must be the same.

The report was executed again and finished with

status check passed.

Check whether the customizing of the depreciation

areas has been defined correctly in case of parallel

currencies.

The SAP Best Practices Baseline package does not

have depreciation areas in a parallel currency. No

action required.

If you are already using account-based profitability

analysis, perform a delta upload to SAP BW for all

account-based CO-PA DataSources for which you use

the delta method.

The SAP Best Practices Baseline package does not

have account-based profitability analysis. No action

required.

Lock postings periods in FI. All posting periods are locked for FI postings.

Lock posting periods in CO for Plan/Actual postings

(transaction OKP1).

All posting periods are locked for CO postings

Run the report RASFIN_MIGR_PRECHECK again to

make sure that the prerequisites for the Asset

Accounting are met.

The report shall not show any error message.

https://service.sap.com/sap/support/notes/1939592https://service.sap.com/sap/support/notes/2129306

8

2015