Reference Guide
May 2015
English
SAP Simple Finance Implementation with SAP Best
Practices Baseline V3.607
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.
2
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.
<Example>
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, F 2 or E N T E R .
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
Document History
Revision
Date
Change
1.0
<2015-04-30>
Preview version
1.1
<2015-05-22>
1. release version
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
Table of Contents
1
1.1
1.2
1.3
Introduction
Purpose of this document
Scope of this document
Out of scope
5
5
5
5
2
Preparation activities before the installation of the SAP Simple Finance add-on
7
3
3.1
Migration of Customizing
Preparations and Migration of Customizing
3.1.1
Preparations and Migration of Customizing for the General Ledger
3.1.2
Preparations and Migration of Customizing for Asset Accounting
3.1.3
Preparations and Migration of Customizing for Controlling
Migration
3.2.1
Migration of Cost Elements and Customizing
3.2.2
Technical Check of Transaction Data
3.2.3
Migration - Enrichment of Data
3.2.4
Migration of Line Items into New Data Structure
3.2.5
Migration of Balances
3.2.6
Complete Migration
3.2.7
Activities after Migration
9
9
9
10
11
11
12
13
13
14
14
15
16
Additional Customizing, Baseline Scenarios Analyzing, SAP Simple Finance Fiori apps
Implementation
Additional Customizing
Baseline scenario analyzing
SAP Simple Finance Fiori App
18
18
19
21
Appendix
Preparation activities before the installation of the SAP Simple Finance add-on
5.1.1
Closing activities in past posting periods
5.1.2
Preparation activities prior to the installation
22
22
22
22
3.2
4
4.1
4.2
4.3
5
5.1
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
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.
SAP Simple Finance Implemenation with SAP Best Practices Baseline V3.607
Introduction
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
5
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.
6
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Introduction
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.
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
Block all users who have no tasks in the migration
project.
Only users involved in the migration project have
access to the system.
Backup the system before installing the add-on.
System backup done.
The full list of preparation activities is available in the online help under Migration to SAP Accounting powered by
SAP HANA.
Now your system administrator should perform a system upgrade and install the SAP Simple Finance add-on. For
details, refer to the SAP Simple Finance Administration Guide http://help.sap.com/sfin200
8
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Preparation activities before the installation of the SAP Simple Finance add-on
3 Migration of Customizing
3.1 Preparations and Migration of Customizing
Once the SAP Simple Finance add-on has been installed, you can start with the migration of the baseline
customizing.
You can find more details in a SAP ERP with SAP Simple Finance system, following this path: IMG  SAP Simple
Finance Add-On for SAP Business Suite powered by SAP HANA  Preparations and Migration of Customizing.
The complete list of activities is also available in the online help under Migration to SAP Accounting powered by
SAP HANA .
3.1.1 Preparations and Migration of Customizing for the
General Ledger
IMG Activities
Expected Outcome
Activate SAP Reference IMG for Financial Accounting
(New)
Not required, IMG menu is already available.
Check and Adopt Fiscal Year Variants
No activity required, since the SAP Best Practices
Baseline packages use the variant K4 for both the
controlling area, and all company codes.
Migrate General Ledger Customizing*
The following settings are migrated:
Define Settings for Journal Entry Ledger

Company code assignments

Currency settings

Fiscal year variant

Open period variant

Settings for real-time integration of CO-FI
In case of multiple accounting principles, e.g. IFRS
and GAAP are assigned to the ledger 0L, the flag
Parallel accounting using additional G/L accounts will
be by default selected.
Define Ledger for CO Version
Leading ledger 0L has been assigned to the CO
version 0 (Plan/actual version).
Define Document Types for Postings in Controlling
CO as the document type has been defined to be used
for CO postings.
Define Document Type Mapping Variants for CO
Business Transactions
Document Type Mapping Variant for CO transaction is
made.
Check and Define Default Values for Postings in
Controlling
If you do not enter a default ledger group, all CO
postings will be done to all G/L ledgers.
SAP Simple Finance Implemenation with SAP Best Practices Baseline V3.607
Migration of Customizing
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
9
Define Offsetting Account Determination Type
The recommended option As case 2, but including
lime items generated automatically has been
selected.
Define Source Ledger for Migration of Balances
Since New G/L Accounting was already active in the
baseline ERP system, the ledger 0L has been selected
as source ledger for the migration of balances.
Execute Consistency Check of General Ledger
Settings
The consistency check has run and no errors should
be reported.
Activate Business Functions
The activation of the business functions is mandatory
for the SAP Simple Finance add-on.
Following business functions have been activated:

FIN_GL_CI_1

FIN_GL_CI_2

FIN_GL_CI_3
* Note: Do not repeat the activity Migrate General Ledger Customizing once you have performed it, every time
you run this transactions, this will overwrite your previous settings!
3.1.2 Preparations and Migration of Customizing for Asset
Accounting
New Asset Accounting is mandatory for the SAP Simple Finance add-on.
The following activities are necessary before migration of the classical Assets Accounting to New Assets
Accounting. By doing these activities, the documents from Asset Accounting are migrated as part of the General
Ledger documents migration. Finally, the planned depreciation values of fixed assets will be recalculated during
the migration phase.
IMG Activities
Expected Outcome
Migration from Classic to New Asset Accounting
Migrate Charts of Depreciation
The chart of depreciation, which is used in the SAP
Best Practices Baseline package, is migrated.
Display Migration Log
If the migration log displays error messages, you
should analyze them and take consequent actions.
Example: If the error message No accounting principle
found for chart of deprec. 10US/deprec. area 01 is
displayed, you should correct the depreciation areas
in the chart of depreciation by assigning the
respective accounting principles.
Perform Additional Manual Activities
Here you should at least perform the mandatory
activity Define Technical Clearing Account for
Integrated Asset Acquisition.
Additionally, in baseline the accounting principle (local
GAAP) is assigned to all depreciation areas.
Check Prerequisites for Activating Asset Accounting
(New)
10
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
The prerequisites for the activation of the New Asset
Accounting have been checked with transaction
Migration of Customizing
FAA_CHECK_ACTIVATION.
If you encounter any error, you need to correct it and
then run this check report again until it ends with the
message No error found and all traffic lights are green.
Activate Asset Accounting (New)
The New Asset Accounting has been activated with
transaction FAA_DO_ACTIVATION.
3.1.3 Preparations and Migration of Customizing for Controlling
IMG Activities
Expected Outcome
Execute BW-Delta Extraction for Account-Based COPA
Because the baseline used only the cost-object based
profitability analysis prior the migration, this step is
not required.
Delete Settings for the Change of Profitability
Segment Characteristics
All the settings for profitability segment
characteristics (segment level) made in transaction
KEQ3 have been deleted by running the report
FCO_MIGRATION_COPA.
Maintain Operating Concern
The report FCO_ADD_COPA_FIELD_TO_ACDOCA is
started in background and activates the operating
concern for account-based Profitability Analysis.
Activate Account-Based Profitability Analysis
The account-based Profitability Analysis is now active
for your concern.
*Since the cost-based CO-PA has been used before
the SAP Simple Finance add-on, after the activation of
account-based CO-PA, both approaches exist and
work correctly in the baseline landscape.
The recommended approach by SAP is the Account Based Profitability Analysis.
3.2 Migration
The following sections list all necessary migration activities. In the Expected Outcome column, issues as well as
related solutions found during the migration of the SAP Best Practices Baseline packages for China, Germany,
and US V3.607 are listed.
The complete migration activities can be found in the SAP ERP system following this path: IMG
 SAP Simple Finance Add-On for SAP Business Suite powered by SAP HANA  Migration.
The full list of activities is also available in the online help under Migration to SAP Accounting powered by SAP
HANA .
SAP Simple Finance Implemenation with SAP Best Practices Baseline V3.607
Migration of Customizing
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
11
IMG Activities
Expected Outcome
Partitioning of Universal Journal Entry Line Items
Table
No action required.
Regenerate CDS Views and Field Mapping
Execute in background the program
FGL_MIG_REGENERATE_CDS and check the progress
in the transaction SLG1 with sub- object
FINS_GENERATE.
3.2.1 Migration of Cost Elements and Customizing
IMG Activities
Expected Outcome
Check Consistency of G/L Accounts and Cost
Elements
An inconsistency could be that no G/L accounts exist
for a primary cost element. Here is an example of an
error found in SAP Best Practices Baseline packages
for China:
Error message:
Primary cost element 41010100/CN01 (type 1) not
found in chart of accts CACN
Solution:
Create the missing G/L account with account type
primary cost element for CN client. Take a similar
account as template for setting up the G/L account
characteristics.
After all corrections, G/L accounts and cost elements
are consistent with each other and G/L account
master records have the right account types.
Migrate Secondary Cost Elements to Chart of
Accounts (transaction FINS_MIG_GCM)
All secondary cost elements, as well as the primary
cost elements, are represented as G/L accounts.
Display Status of Migration of Cost Elements
(transaction FINS_MIG_MONITOR_GCM)
With this transaction, you can monitor the status of
the merge of G/L accounts and cost elements.
In the baseline both company codes 1000 and 1010
use the same chart of accounts. The chart of
accounts tables are updated when report is executed
for the first company code.
Migrate Default Account Assignments (transaction
FINS_MIG_DAA)
The default assignments are transferred from the
master data table CSKB to the Customizing table
TKA3A.
Display Status of Migration of Default Account
Assignments (transaction
FINS_MIG_MONITOR_DAA)
With this transaction, you can check the status of the
transfer of default account assignments. After the
migration, the default account assignments are
accessible via transaction OKB9.
Adopt Authorizations
Because G/L accounts and cost elements are in the
same table in Simple Finance 2.0 system, you need to
adapt the authorization roles for creating/changing
12
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Migration of Customizing
G/L accounts and cost elements.
3.2.2
Technical Check of Transaction Data
Even though there is no transactional data existing, you can run these check fast to ensure everything is in a
consistent status.
IMG Activities
Expected Outcome
Analyze Transactional Data (transaction
FINS_RECON_RCO)
The report runs and checks whether all transactional
data are complete and correct.
Display Status of Analysis of Transaction Data
(transaction FINS_MIG_MONITOR_RCO)
You use this report to check the status of the
transactional data analysis.
Reconcile Transactional Data (transaction
FINS_RECON_RC1)
The report checks whether all FI documents are
consistent and ready to be migrated. It checks
prerequisites for the migration.
Display Status of Technical Reconciliation of
Transactional Data (transaction
FINS_MIG_MONITOR_RC1)
You use this report to check the status of the
transactional data reconciliation.
3.2.3
Migration - Enrichment of Data
Even though there is no transactional data existing, you can run these check fast to ensure everything is in a
consistent status.
IMG Activities
Expected Outcome
Enrich Transactional Data (transaction
FINS_MIGRATION)
The report enriches transactional data and
documents and then migrates them to SAP
Accounting powered by SAP HANA.
Display Status of Enrichment of Transactional Data
(transaction FINS_MIG_MONITOR)
You use this report to check the status of the
transactional data enrichment and migration.
Check of Migrated Documents (transaction
FINS_RECON_RC2)
This report checks the result of the previous step of
the migration. It checks document fields that are used
in the following migration steps.
Display Status of Check of Migrated Documents
(transaction FINS_MIG_MONITOR_RC2)
You use this report to check the status of the previous
step.
All checks from the last migration step should end
with status green (no issues).
SAP Simple Finance Implemenation with SAP Best Practices Baseline V3.607
Migration of Customizing
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
13
3.2.4
Migration of Line Items into New Data Structure
Even though there is no transactional data existing, you can run this check fast to ensure everything is in a
consistent status.
IMG Activities
Expected Outcome
Migrate Accounting Documents to Universal Journal
Entry Structure (transaction FIND_MIG_UJ)
All accounting documents are migrated to the Unified
Journal Entry structure and are enriched with COPA
information.
SAP recommends that you execute this migration
step in all clients, also in clients where there are no
transactional data. This is required so that the
migration status for the client can be set to finished.
Display Status of Document Migration to Universal
Journal Entry (transaction FINS_MIG_MONITOR_UJ)
You can use this report to monitor the status of the
previous step.
All data packages are displayed with status green (no
issues).
Check Migration of Accounting Documents to
Universal Journal Entry (transaction
FINS_RECON_RC3)
This report performs several checks to the migrated
documents.
Display Status of Check of Accounting Document
Migration (transaction FINS_MIG_MONITOR_RC3)
You can use this report to monitor the status of the
previous step.
You must perform this step before migrating the
account balances.
All checks from the last migration step ended with
status green (no issues).
Migrate General Ledger Allocations (transaction
FINS_MIG_GL_ALLOC)
3.2.5
All allocations have been migrated to the new Unified
Journal Entry structure and no errors are displayed.
Migration of Balances
Even though there is no transactional data existing, you can run this check fast to ensure everything is in a
consistent status.
IMG Activities
Expected Outcome
Migrate Balances (transaction FINS_MIG_DLT)
All G/L account balances are migrated.
SAP recommends that you execute this migration
step in all clients, also in clients where there are no
transactional data. This is required so that the
migration status for the client can be set to finished.
Display Status of Migration of Balances (transaction
FINS_MIG_MONITOR_DLT)
You can use this report to monitor the status of the
previous step.
All data packages are displayed with status green (no
issues).
Calculate Initial Depreciation Values (transaction
14
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
The migration from the classical to the New Asset
Migration of Customizing
AFAR)
Accounting is one precondition for migrating to
Simple Finance. Now, after completing the migration
of transactional data and account balances, you need
to recalculate the planned depreciation values for the
Asset Accounting.
After running this report, the initial planned
depreciation values have been calculated and stored
in the respective database tables.
Check Migration of Balances (transaction
FINS_RECON_RC4)
This report checks the result of the previous step of
the migration.
If you find errors, you need to make the respective
corrections and run the migration again. Should you
need to repeat the migration, please read the SAP
note 2138644 first. This SAP note advices on how to
reset the migration in case you need to repeat it.
Monitor Check of Balances (transaction
FINS_MIG_MONITOR_RC4)
3.2.6
This report helps you monitoring the previous step.
All checks from the last migration step should end
with status green (no issues).
Complete Migration
IMG Activities
Expected Outcome
Convert Held Documents (transaction
FINS_RFTMPBLU
You need to convert previously held documents,
before you can create new ones or processing existing
ones.
As a result, all held documents are converted or
deleted.
Reconcile and Compare Migrated Data

Reconcile ledger 0 with ledger 0L (transaction
GCAC).

Compare the company's key figure with the ones
prior to the migration:

The financial statements (program RFBILA00)

The asset history sheet (program
RAGITT_ALV01)

The depreciation run for the planned
depreciations (program RAHAFA_ALV01)

The totals report for cost centers (transaction
S_ALR_87013611)

Sales order selection (program RKKBSELL)

The G/L account balance list (program
RFSSLD00)

The general ledger line items list (program
RFSOPO00)
SAP Simple Finance Implemenation with SAP Best Practices Baseline V3.607
Migration of Customizing
All financial data should be correct and corresponds
to the figures prior to the migration in case there was
transactional data. Otherwise, this step is not
mandatory.
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
15

The compact document journal (program
RFBELJ00)

The vendor sales (program RFKUML00)

The vendor open item list (program RFKEPL00)

The customer sales (program RFKUML00)

The customer open item list (program
RFDEPL00)

The customer recurring entry original documents
(program RFDAUB00)

The cost centers: actual/plan/variance
(transaction GR55 with report group 1SIP)
Set Migration to Completed
Once you set the migration status to complete, users
are allowed to make postings again in the system.
3.2.7 Activities after Migration
IMG Activities
Expected Outcome
Transfer Application Indexes (transaction
FINS_MIG_INIT_COLD)
In this Customizing activity, application indexes are
transferred to the cold partition of the database in
order to reduce main memory consumption.
For this you use Data Aging, therefore it is required to
activate the business function DAAG_DATA_AGING in
your system.
Display Status of Transfer of Application Indexes
(transaction FINS_MIG_MONITOR_CLD)
You can use this report to monitor the status of the
previous step.
All data packages should be displayed with status
green (no issues).
Fill Due Dates in FI Documents (transaction
FIN_MIG_DUE)
In this Customizing activity, due date fields are filled in
the FI line items for customers and vendors and for
G/L account line items that have a base line date.
Display Status of Filling in Due Dates into FI
Documents (transaction FIN_MIG_MONITOR_DUE)
You can use this report to monitor the status of the
previous step.
All data packages should be displayed with status
green (no issues).
Fill the Offsetting Account in FI Documents
(transaction FIN_MIG_GKONT)
The offsetting account is filled in the FI documents.
Precondition for this activity is that you have defined
an offsetting account determination type in the
Customizing activity Define Offsetting Account
Determination Type.
Display Status of Filling the Offsetting Account in FI
Documents (transaction FIN_MIG_MONITOR_GKO)
You can use this report to monitor the status of the
previous step.
All data packages should be displayed with status
16
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Migration of Customizing
green (no issues).
Migrate House Bank accounts (transaction
FCLM_BAM_MIGRATION)
The house bank accounts are migrated.
* You need to perform customizing for Bank Account
Management first and then run the transaction
You will find the customizing activities on the next
page.
SAP Simple Finance Implemenation with SAP Best Practices Baseline V3.607
Migration of Customizing
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
17
4 Additional Customizing, Baseline Scenarios
Analyzing, SAP Simple Finance Fiori apps
Implementation
4.1 Additional Customizing
You need to implement the following additional customizing:
Activity
Reason /Result
Financial Accounting (new)  General Ledger
Accounting (New)  Business Transaction  Classify
Document Type for Document Splitting
During migration phase, an additional document type
CO has been defined.
Financial Accounting (new)  General Ledger
Accounting (New)  Business Transaction  Classify
G/L Accounts for Document Splitting
During migration phase, additional G/L accounts have
been generated for the secondary cost elements.
Financial Accounting (new)  Financial Supply Chain
Management  Cash and Liquidity Management 
Bank Account Management  Basic Settings 
Define Number Ranges for Bank Account Technical
IDS
To define Bank Account Management (BAM) related
customizing in order to leverage the Cash
Management powered by SAP HANA function.
You need to add it for the document splitting.
You need to add them for the document splitting per
Chart of Account.
Financial Accounting (new)  Financial Supply Chain
Management  Cash and Liquidity Management 
Bank Account Management  Basic Settings 
Define Number Ranges for Workflow Change Request
Financial Accounting (new)  Financial Supply Chain
Management  Cash and Liquidity Management 
Bank Account Management  Basic Settings 
Define Settings for Bank Account Master Data
Bank Transfer Clearing Account
Required for Payment Fiori Apps.
18
Additional Customizing, Baseline Scenarios Analyzing, SAP Simple Finance Fiori apps
Implementation
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
4.2 Baseline scenario analyzing
These are the scenarios in the SAP Best Practices Baseline package for US, which are affected:
BB ID
BB Description
Transaction
Code/function in
Classic SAP ERP
New Function in SAP ERP
with SAP Simple Finance
Type of New
Function
Create Accounts and Account
Groups
FS00
FCOM_IP_CC_COSTELEM01
WEBDYN
156
General Ledger
S_PL0_86000030
FIS_FPM_GRID_GLACC_BAL
WEBDYN
157
Accounts Receivables
F.2B
RFINTITAR/RFINTITAP
PROG
159
Period End Closing in Financial
Accounting
FAGL_FC_VAL
FAGL_FCV
Transaction
Opening and
closing posting
period
S_PEN_05000130
Transaction
OB42
S_alr_87001320
Transaction
S_PCO_36000218
FCOM_FIS_AR_OVP
WEBDYN
S_PCO_36000219
FCOM_FIS_AP_OVP
WEBDYN
166
Segment Reporting
FAGL_EHP4_T001B_COFI
196
Project with Fixed Price and
T&M Billing
CJ40
FCOM_IP_PROJ_OVERALL01
WEBDYN
196
Project with Fixed Price and
T&M Billing
CJR2
FCOM_IP_PROJ_COSTELEM01
WEBDYN
197
Internal Projects
CJ40
FCOM_IP_PROJ_OVERALL01
WEBDYN
210
Internal Product Development
KKE1
CKUC
Transaction
KKE2
CKUC
Transaction
221
SAP ERP Reports for
Accounting
S_ALR_87012326
FCOM_FIS_GLACCOUNT_OVP
WEBDYN
766
Internal Order Planning
KPF6
FCOM_IP_ORD_COSTELEM01
WEBDYN
767
Internal Order Actual
KPF6
FCOM_IP_ORD_COSTELEM01
WEBDYN
You can also execute the transaction KP06 with its corresponding WebDynpro transaction
FCOM_IP_CC_COSTELEM01 / NWBC  Role SAP_SFIN_ACC_PLANNING  SFIN Accounting: Planning  Cost
Center Planning.
In the SAP Best Practices Baseline package for Germany, the following scenarios are affected:
BB ID
BB Description
Transaction Code
in Classic SAP
ERP
New Function in SAP ERP
with SAP Simple Finance
Type of New
Function
Create Accounts and Account
FS00
FCOM_IP_CC_COSTELEM01
WEBDYN
SAP Simple Finance Implemenation with SAP Best Practices Baseline V3.607
Additional Customizing, Baseline Scenarios Analyzing, SAP Simple Finance Fiori apps
Implementation
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
19
Groups
156
General Ledger
S_PL0_86000030
FIS_FPM_GRID_GLACC_BAL
WEBDYN
157
Accounts Receivable
F.2B
RFINTITAR/RFINTITAP
PROG
159
Period End Closing in Financial
Accounting
FAGL_FC_VAL
FAGL_FCV
Transaction
166
Segment Reporting
S_PCO_36000218
FCOM_FIS_AR_OVP
WEBDYN
S_PCO_36000219
FCOM_FIS_AP_OVP
WEBDYN
196
Project with Fixed Price and
T&M Billing
CJ40
FCOM_IP_PROJ_OVERALL01
WEBDYN
197
Internal Projects
CJ40
FCOM_IP_PROJ_OVERALL01
WEBDYN
210
Internal Product Development
KKE1
CKUC
Transaction
KKE2
CKUC
Transaction
221
SAP ERP Reports for
Accounting
S_ALR_87012326
FCOM_FIS_GLACCOUNT_OV
P
WEBDYN
766
Internal Order Planning
KPF6
FCOM_IP_ORD_COSTELEM01
WEBDYN
767
Internal Order Actual
KPF6
FCOM_IP_ORD_COSTELEM01
WEBDYN
In the SAP Best Practices Baseline for Germany, the scenario 162 Assets Accounting - Acquisition with Automatic
Offsetting Entry encountered the problem that the Account 69990 and 69991 were defined with Open Item
Management character. As a solution, both accounts have been corrected without Open Item Management. In
addition, within new Assets Accounting, the APC Values Posting and accounts reconciliation are not necessary
any more.
In the SAP Best Practices Baseline package for China, the following scenarios are affected:
BB ID
BB Description
Transaction Code
in Classic SAP
ERP
New Function in SAP ERP
with SAP Simple Finance
Type of New
Function
155
Create Accounts and Account
Groups
FS00
FCOM_IP_CC_COSTELEM01
WEBDYN
156
General Ledger
S_PL0_86000030
FIS_FPM_GRID_GLACC_BAL
WEBDYN
157
Accounts Receivable
F.2B
RFINTITAR/RFINTITAP
PROG
159
Period End Closing in Financial
Accounting
FAGL_FC_VAL
FAGL_FCV
Transaction
166
Segment Reporting
S_PCO_36000218
FCOM_FIS_AR_OVP
WEBDYN
166
Segment Reporting
S_PCO_36000218
FCOM_FIS_AR_OVP
WEBDYN
S_PCO_36000219
FCOM_FIS_AP_OVP
WEBDYN
196
Project with Fixed Price and
T&M Billing
CJ40
FCOM_IP_PROJ_OVERALL01
WEBDYN
197
Internal Projects
CJ40
FCOM_IP_PROJ_OVERALL01
WEBDYN
20
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Additional Customizing, Baseline Scenarios Analyzing, SAP Simple Finance Fiori apps
Implementation
210
Internal Product Development
KKE1
CKUC
Transaction
KKE2
CKUC
Transaction
221
SAP ERP Reports for
Accounting
S_ALR_87012326
FCOM_FIS_GLACCOUNT_OV
P
WEBDYN
766
Internal Order Planning
KPF6
FCOM_IP_ORD_COSTELEM01
WEBDYN
767
Internal Order Actual
KPF6
FCOM_IP_ORD_COSTELEM01
WEBDYN
As a result, these affected transactions should be replaced by new transactions or using the corresponding
WEBDYN transaction.
Refer to the SAP note 1946054 for the detailed SAP ERP transaction comparison.
4.3 SAP Simple Finance Fiori App
Refer to the standard documentation for related technical and configuration information:
http://help.sap.com/sfin200
SAP Simple Finance Implemenation with SAP Best Practices Baseline V3.607
Additional Customizing, Baseline Scenarios Analyzing, SAP Simple Finance Fiori apps
Implementation
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
21
5 Appendix
In case you do have to consider the migration of transactional data, then you have to take into account the steps
mentioned below.
5.1 Preparation activities before the installation of the SAP
Simple Finance add-on
Since the SAP Simple Finance add-on modifies the data structures in FI, it is necessary to perform certain
preparation activities in the SAP ERP System. Once the SAP Simple Finance add-on is installed, there is no way to
switch back to the old data structure.
5.1.1 Closing activities in past posting periods
All period-end closing activities have been properly performed and documented. In principle, the migration to SAP
Simple Finance 2.0 can be executed at any point in time during the year. Make sure to perform the period closing
correctly. In case of inconsistent data, there is no way to change the old FI tables after the migration.
5.1.2 Preparation activities prior to the installation
The complete list of activities to be performed before installing the SAP Simple Finance add-on is available in the
online help under Migration to SAP Accounting powered by SAP HANA .
Preparation activities performed prior to installing the Simple Finance add-on could be (in case you have used a
Baseline solution on ERP on HANA607 landscape).
Activity
Result
Check if business function EA-FIN is active.
The Business function EA-FIN is active.
Check and activate the business functions
FIN_AA_PARALLEL_VAL and FIN_AA_CI_1.
The Business functions FIN_AA_PARALLEL_VAL and
FIN_AA_CI_1 are 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.
The Report RASFIN_MIGR_PRECHECK runs and
checks the customizing settings in the customizing-,
test- and productive system.
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.
At first this report showed 2 error messages for CN
baseline:

For some company codes, currencies were
assigned to the non-leading ledger but not to the
leading ledger  it is necessary to correct the
currency assignment for all company codes, even
22
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Appendix
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 data consistency using the report
RFINDEX_NACC with the parameters specified in the
SAP note 2105948. The report is called with the
following parameterization:
- Documents vs Indexes
- Indexes vs Documents
- Documents - Transaction Figures
- Indexes - Transaction Figures
All inconsistencies have been corrected and the
report RFINDEX_NACC does not report any error.
Check documents against transaction figures for all
fiscal years, in which archiving has not yet taken place
(transaction FAGLF03).
The FI documents and FI balances are reconciled.
Execute the reconciliation for the General Ledger and
the Accounts Receivable and Accounts Payable sub
ledgers by executing the report TFC_COMPARE_VZ
(transaction FAGLF03).
The General ledger and sub ledgers are reconciled.
Execute the reconciliation for the Asset Accounting
with the General Ledger by executing the report
RAABST02 (transaction ABST2).
The Asset Accounting and G/L Accounting are
reconciled.
Reconcile the Materials Management with the General
Ledger by executing the reports RM07MBST and
RM07MMFI.
The MM and FI are reconciled.
Reconcile the ledgers in the New G/L Accounting
(transaction GCAC).
All ledgers in the New G/L Accounting are reconciled.
Check whether the customizing of the depreciation
areas has been defined correctly in case of parallel
currencies.
There is no action item here, since the company
codes in the EFE appliance do not have depreciation
areas in a parallel currency.
Example: one inconsistency could be that no zero
balance is available for a business area. By making
additional manual postings, the zero balance for
document splitting can be forced.
Only the leading ledger 0L is assigned to the company
codes in scope.
The Customizing of depreciation areas in the Asset
Accounting is correct.
Perform closing for periodic asset postings (with
program RAPERB2000, transaction AFAB).
All periodic asset documents have been posted to the
General Ledger.
In the EFE appliance there are no depreciation areas
to be posted periodically.
Execute the periodic depreciation posting run (with
program RAPOST2000, transaction ASKB).
All depreciation documents are posted to the General
Ledger.
Check for update terminations in your system and
correct any you find (transaction SM13).
If you are already using account-based profitability
analysis, perform a delta upload to SAP BW for all
SAP Simple Finance Implemenation with SAP Best Practices Baseline V3.607
Appendix
The cost-object based profitability analysis has been
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
23
account-based CO-PA DataSources for which you use
the delta method.
used prior to the migration, this step is not required.
Run the carry-forward for all ledgers and all
currencies (transaction FAGLGVTR).
All ledgers and currencies are carried forward.
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.
Block all users who have no tasks in the migration
project.
Only users involved in the migration project have
access to the system.
Document the results of key financial reports for each
company in scope. SAP recommends the following
objects for this:
All main closing activities have been documented. The
documentation can be used for comparing the data
before and after the migration to the SAP Simple
Finance.
•The financial statements (program RFBILA00)
•The asset history sheet (report RAGITT_ALV01)
•Depreciation run for planned depreciations
(RAHAFA_ALV01)
•The totals report for cost centers (transaction
S_ALR_87013611).
•Sales order selection (program RKKBSELL)
•The G/L account balance list (report RFSSLD00).
•The general ledger line items list (Report
RFSOPO00)
•The compact document journal (report RFBELJ00)
•The vendor sales (report RFKUML00)
•The vendor open item list (report RFKOPO00)
•The customer sales (report RFDUML00)
•The customer open item list (report RFDOPO00)
•The customer recurring entry original documents
(report RFDAUB00)
•The cost centers: actual/plan/variance (transaction
GR55 with report group 1SIP for CO totals)
Backup the system before installing the add-on.
24
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
System backup done.
Appendix
www.sap.com/contactsap
© 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 http://global.sap.com/corporateen/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.