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

Reference Guide May 2015 English SAP Simple Finance Implementation with SAP Best Practices Baseline V3.607

Typographic Conventions Type Style Example Example EXAMPLE Example Example <Example> Description 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. Emphasized words or expressions. 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. 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. 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. EXAM PLE Keys on the keyboard, for example, F2 or EN TER. 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

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 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 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 Check if business function EA-FIN is 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. Check and activate the business functions FIN_AA_PARALLEL_VAL and FIN_AA_CI_1. Run the report ZFINS_MIG_PRECHCK_CUST_SETTNGS in all your SAP ERP systems (this report is contained in SAP note 2129306) Check whether the customizing of the depreciation areas has been defined correctly in case of parallel currencies. 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. Lock postings periods in FI. Lock posting periods in CO for Plan/Actual postings (transaction OKP1). Run the report RASFIN_MIGR_PRECHECK again to make sure that the prerequisites for the Asset Accounting are met. Expected Outcome Business function EA-FIN should be active. Report RASFIN_MIGR_PRECHECK runs and checks the customizing settings in the customizing-, test- and productive system. Business functions FIN_AA_PARALLEL_VAL and FIN_AA_CI_1 should be active. 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. The SAP Best Practices Baseline package does not have depreciation areas in a parallel currency. No action required. The SAP Best Practices Baseline package does not have account-based profitability analysis. No action required. All posting periods are locked for FI postings. All posting periods are locked for CO postings 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. Backup the system before installing the add-on. Only users involved in the migration project have access to the system. 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 Activate SAP Reference IMG for Financial Accounting (New) Check and Adopt Fiscal Year Variants Migrate General Ledger Customizing* Expected Outcome Not required, IMG menu is already available. No activity required, since the SAP Best Practices Baseline packages use the variant K4 for both the controlling area, and all company codes. The following settings are migrated: Company code assignments Currency settings Fiscal year variant Open period variant Settings for real-time integration of CO-FI Define Settings for Journal Entry Ledger Define Ledger for CO Version Define Document Types for Postings in Controlling Define Document Type Mapping Variants for CO Business Transactions Check and Define Default Values for Postings in Controlling 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. Leading ledger 0L has been assigned to the CO version 0 (Plan/actual version). CO as the document type has been defined to be used for CO postings. Document Type Mapping Variant for CO transaction is made. 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 Define Source Ledger for Migration of Balances Execute Consistency Check of General Ledger Settings Activate Business Functions The recommended option As case 2, but including lime items generated automatically has been selected. 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. The consistency check has run and no errors should be reported. 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 Display Migration Log Perform Additional Manual Activities Check Prerequisites for Activating Asset Accounting (New) The chart of depreciation, which is used in the SAP Best Practices Baseline package, is migrated. 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. 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. The prerequisites for the activation of the New Asset Accounting have been checked with transaction 10 2015 SAP SE or an SAP affiliate company. All rights reserved. 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 Execute BW-Delta Extraction for Account-Based CO- PA Delete Settings for the Change of Profitability Segment Characteristics Maintain Operating Concern Activate Account-Based Profitability Analysis Expected Outcome Because the baseline used only the cost-object based profitability analysis prior the migration, this step is not required. All the settings for profitability segment characteristics (segment level) made in transaction KEQ3 have been deleted by running the report FCO_MIGRATION_COPA. The report FCO_ADD_COPA_FIELD_TO_ACDOCA is started in background and activates the operating concern for 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 Partitioning of Universal Journal Entry Line Items Table Regenerate CDS Views and Field Mapping Expected Outcome No action required. 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 Check Consistency of G/L Accounts and Cost Elements Migrate Secondary Cost Elements to Chart of Accounts (transaction FINS_MIG_GCM) Display Status of Migration of Cost Elements (transaction FINS_MIG_MONITOR_GCM) Migrate Default Account Assignments (transaction FINS_MIG_DAA) Display Status of Migration of Default Account Assignments (transaction FINS_MIG_MONITOR_DAA) Adopt Authorizations Expected Outcome 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. All secondary cost elements, as well as the primary cost elements, are represented as G/L accounts. 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. The default assignments are transferred from the master data table CSKB to the Customizing table TKA3A. 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. 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 Analyze Transactional Data (transaction FINS_RECON_RCO) Display Status of Analysis of Transaction Data (transaction FINS_MIG_MONITOR_RCO) Reconcile Transactional Data (transaction FINS_RECON_RC1) Display Status of Technical Reconciliation of Transactional Data (transaction FINS_MIG_MONITOR_RC1) Expected Outcome The report runs and checks whether all transactional data are complete and correct. You use this report to check the status of the transactional data analysis. The report checks whether all FI documents are consistent and ready to be migrated. It checks prerequisites for the migration. 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 Enrich Transactional Data (transaction FINS_MIGRATION) Display Status of Enrichment of Transactional Data (transaction FINS_MIG_MONITOR) Check of Migrated Documents (transaction FINS_RECON_RC2) Display Status of Check of Migrated Documents (transaction FINS_MIG_MONITOR_RC2) Expected Outcome The report enriches transactional data and documents and then migrates them to SAP Accounting powered by SAP HANA. You use this report to check the status of the transactional data enrichment and migration. This report checks the result of the previous step of the migration. It checks document fields that are used in the following migration steps. 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 Migrate Accounting Documents to Universal Journal Entry Structure (transaction FIND_MIG_UJ) Display Status of Document Migration to Universal Journal Entry (transaction FINS_MIG_MONITOR_UJ) Check Migration of Accounting Documents to Universal Journal Entry (transaction FINS_RECON_RC3) Display Status of Check of Accounting Document Migration (transaction FINS_MIG_MONITOR_RC3) Migrate General Ledger Allocations (transaction FINS_MIG_GL_ALLOC) Expected Outcome 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. You can use this report to monitor the status of the previous step. All data packages are displayed with status green (no issues). This report performs several checks to the migrated documents. You must perform this step before migrating the account balances. You can use this report to monitor the status of the previous step. All checks from the last migration step ended with status green (no issues). All allocations have been migrated to the new Unified Journal Entry structure and no errors are displayed. 3.2.5 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 Migrate Balances (transaction FINS_MIG_DLT) Display Status of Migration of Balances (transaction FINS_MIG_MONITOR_DLT) Calculate Initial Depreciation Values (transaction Expected Outcome 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. You can use this report to monitor the status of the previous step. All data packages are displayed with status green (no issues). The migration from the classical to the New Asset 14 2015 SAP SE or an SAP affiliate company. All rights reserved. Migration of Customizing

AFAR) Check Migration of Balances (transaction FINS_RECON_RC4) Monitor Check of Balances (transaction FINS_MIG_MONITOR_RC4) 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. 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. This report helps you monitoring the previous step. All checks from the last migration step should end with status green (no issues). 3.2.6 Complete Migration IMG Activities Convert Held Documents (transaction FINS_RFTMPBLU 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) Expected Outcome 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. 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. 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. 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 Transfer Application Indexes (transaction FINS_MIG_INIT_COLD) Display Status of Transfer of Application Indexes (transaction FINS_MIG_MONITOR_CLD) Fill Due Dates in FI Documents (transaction FIN_MIG_DUE) Display Status of Filling in Due Dates into FI Documents (transaction FIN_MIG_MONITOR_DUE) Fill the Offsetting Account in FI Documents (transaction FIN_MIG_GKONT) Display Status of Filling the Offsetting Account in FI Documents (transaction FIN_MIG_MONITOR_GKO) Expected Outcome 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. You can use this report to monitor the status of the previous step. All data packages should be displayed with status green (no issues). 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. You can use this report to monitor the status of the previous step. All data packages should be displayed with status green (no issues). 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. 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. You need to add it for the document splitting. Financial Accounting (new) General Ledger Accounting (New) Business Transaction Classify G/L Accounts for Document Splitting Financial Accounting (new) Financial Supply Chain Management Cash and Liquidity Management Bank Account Management Basic Settings Define Number Ranges for Bank Account Technical IDS During migration phase, additional G/L accounts have been generated for the secondary cost elements. You need to add them for the document splitting per Chart of Account. To define Bank Account Management (BAM) related customizing in order to leverage the Cash Management powered by SAP HANA function. 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 2015 SAP SE or an SAP affiliate company. All rights reserved. Additional Customizing, Baseline Scenarios Analyzing, SAP Simple Finance Fiori apps Implementation

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 FAGL_EHP4_T001B_COFI Transaction OB42 S_alr_87001320 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 196 Project with Fixed Price and T&M Billing CJ40 FCOM_IP_PROJ_OVERALL01 WEBDYN 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 Check if business function EA-FIN is active. Check and activate the business functions FIN_AA_PARALLEL_VAL and FIN_AA_CI_1. 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. Run the report ZFINS_MIG_PRECHCK_CUST_SETTNGS in all your SAP ERP systems (this report is contained in SAP note 2129306) Result The Business function EA-FIN is active. The Business functions FIN_AA_PARALLEL_VAL and FIN_AA_CI_1 are active. The Report RASFIN_MIGR_PRECHECK runs and checks the customizing settings in the customizing-, test- and productive system. 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 Check documents against transaction figures for all fiscal years, in which archiving has not yet taken place (transaction FAGLF03). 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). Execute the reconciliation for the Asset Accounting with the General Ledger by executing the report RAABST02 (transaction ABST2). Reconcile the Materials Management with the General Ledger by executing the reports RM07MBST and RM07MMFI. Reconcile the ledgers in the New G/L Accounting (transaction GCAC). Check whether the customizing of the depreciation areas has been defined correctly in case of parallel currencies. Perform closing for periodic asset postings (with program RAPERB2000, transaction AFAB). Execute the periodic depreciation posting run (with program RAPOST2000, transaction ASKB). All inconsistencies have been corrected and the report RFINDEX_NACC does not report any error. 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. The FI documents and FI balances are reconciled. The General ledger and sub ledgers are reconciled. The Asset Accounting and G/L Accounting are reconciled. The MM and FI are reconciled. All ledgers in the New G/L Accounting are reconciled. Only the leading ledger 0L is assigned to the company codes in scope. There is no action item here, since the company codes in the EFE appliance do not have depreciation areas in a parallel currency. The Customizing of depreciation areas in the Asset Accounting is correct. All periodic asset documents have been posted to the General Ledger. In the EFE appliance there are no depreciation areas to be posted periodically. 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 The cost-object based profitability analysis has been SAP Simple Finance Implemenation with SAP Best Practices Baseline V3.607 Appendix 2015 SAP SE or an SAP affiliate company. All rights reserved. 23

account-based CO-PA DataSources for which you use the delta method. Run the carry-forward for all ledgers and all currencies (transaction FAGLGVTR). Lock postings periods in FI. Lock posting periods in CO for Plan/Actual postings (transaction OKP1). Run the report RASFIN_MIGR_PRECHECK again to make sure that the prerequisites for the Asset Accounting are met. Block all users who have no tasks in the migration project. Document the results of key financial reports for each company in scope. SAP recommends the following objects for this: 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. used prior to the migration, this step is not required. All ledgers and currencies are carried forward. All posting periods are locked for FI postings. All posting periods are locked for CO postings The report shall not show any error message. Only users involved in the migration project have access to the system. 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. System backup done. 24 2015 SAP SE or an SAP affiliate company. All rights reserved. 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.