Process of Migration to SAP Accounting powered by SAP HANA

The SAP Simple Finance add-on for SAP Business Suite powered by SAP HANA (short: Finance Add-on) contains the product SAP Accounting powered by SAP HANA. New General Ledger Accounting and New Asset Accounting are part of SAP Accounting powered by SAP HANA.

This document provides an overview of the steps that you have to perform for migrating to SAP Accounting powered by SAP HANA and the steps that the system performs automatically.

Availability

Source Release	Target Release
SAP Simple Finance add-on for SAP Business Suite powered by SAP HANA	SAP Simple Finance add-on for SAP Business Suite powered by SAP HANA

Procedure

Phase	Description and name of the transaction or program
Before the migration	Preparations in Customizing:
	If you are not already using New General Ledger Accounting, execute the following activities in the Customizing system: Define the leading ledger and assign the relevant scenarios. If you also want to use the optional SAP fields, assign these to the leading ledger. Set up the CO-FI real-time integration Make the Customizing settings for foreign currency valuation Make the Customizing settings for the initial balance carryforward
	If you are using the reconciliation ledger and activate the real-time integration on a date in the past, you must reverse all reconciliation postings made after the activation date. To do this, choose transaction KALC (Reconciliation Posting: Initial Screen).
	If you are not yet using New Asset Accounting, import report RASFIN_MIGR_PRECHECK from SAP Note 1939592 and test whether the necessary prerequisites for New Asset Accounting have been fulfilled using report RASFIN_MIGR_PRECHECK (Check Prerequisites for FI-AA Migration).
	If the prerequisites for New Asset Accounting are fulfilled, you create Customizing for New Asset Accounting in the Customizing system.

	Check customer-defined coding:
	Tables are replaced with views (name is kept) due to the migration to SAP Accounting powered by SAP HANA. For more information about the tables that are converted into views, see SAP Note 1976487.
	Check if you have write accesses to the tables in your own customer objects in your customer namespace. You have to replace these accesses, since the views with same names allow only read access.
	Check if you have write or read accesses to the tables in your own customer objects in your customer namespace that no longer exist. You have to replace these accesses, since the views with same names allow only read access.
	Check if you have your own customer-specific views in your own objects in your customer namespace for the tables that no longer exist. You have to replace these views with an open-SQL SELECT or the call of a read module, since the Data Dictionary does not support database views that are based on other views.

	How to treat customer-defined fileds:
	First read SAP Note 1976487. The following scenarios exist for handling customer-defined fields:
	How to handle optional fields when migrating to New General Ledger Accounting (FAGLFLEXA). You can enhance the existing general ledger table with the optional fields provided by SAP. The relevant contents of these fields are updated automatically as soon as as you assign them to the relevant ledger. For more information, see Customizing for Financial Accounting (New) Financial Accounting Global Settings (New) Ledgers Ledger Assign Scenarios and Customer Fields to Ledgers .
	Customer Fields in FAGLFLEXA. If you are already using New General Ledger Accounting and have customer fields in FAGLFLEXA, these fields are generated into the view FAGLFLEXT.
	Customer fields in BSEG and in the index tables for creating views with the same names. If a customer field exists in both the BSEG and in the indexes, it is automatically generated into the view with the same name. It is not transferred into a view with the same name if the customer field only exists in the index. In this case the field must first be included in the BSEG and filled using a customer program.

	Preparing for data migration:
	Execute all scheduled jobs and do not schedule any new jobs.
	Lock all users in the system that do not have any tasks associated with the migration.
	Perform closing for periodic asset postings (with program RAPERB2000).
	Execute the periodic depreciation posting run (with program RAPOST2000).
	Check for update terminations in your system and correct any you find.
	Lock the periods in Financial Accounting and Controlling (Plan/Actual).

	Consistency checks before migrating:
	Perform the following consistency checks: Indexes against documents with report RFINDEX_NACC Documents against transaction figures for all fiscal years in which archiving has not yet been performed. If you are using classic General Ledger Accounting, choose transaction F.03 (Report SAPF190) If you are using new General Ledger Accounting, choose transaction FAGLF03 (Report TFC_Compare_VZ) Execute report RFINDEX_NACC for all of the fiscal years that are in the system.
	If you cannot execute the consistency checks with report RFINDEX_NACC for runtime reasons, perform consistency checks using transactions FINS_RECON_DOC_IAI (check the result with transaction FINS_MIG_MONITOR_RC0) and FINS_MIG_MONITOR_RC0 (check the result with transaction FINS_MIG_MONITOR_RC1) instead. This are available in your test system after you have installed the SAP Simple Finance add-on for SAP Business Suite powered by SAP HANA.
	Reconcile the general ledger with Asset Accounting for the leading valuation and parallel valuation. Use report RAABST02 to do this.
	If you are using Classic General Ledger Accounting, execute the reconciliation for the general ledger and the AP/AR subledgers. Use report SAPF190 to do this.
	If you are using New General Ledger Accounting, execute the reconciliation for the general ledger and the subledgers. Use report TFC_COMPARE_VZ to do this or choose transaction FAGLF03.
	If you have classic Profit Center Accounting EC-PCA active, reconcile line item table GLPCA and totals table GLPCT. Use report RGUSLSEP to do this (compares totals records with the total of the line items).
	Compare the ledgers if you are using new General Ledger Accounting. Use report RGUCOMP4 to do this or choose transaction GCAC.
	Reconcile Materials Management (MM) with GL. Choose report RM07MBST/ RM07MMFI to do this.

	Business reconciliation before the migration:
	Carryforward balances again for all currencies and all ledgers to make sure all balance carryforwards are complete and consistent.
	Create the closing documentation. 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 RFKUML00)
	The customer open item list (report RFKOPO00)
	The customer recurring entry original documents (report RFDAUB00)

	Customizing import into the production system:
	Import the activation of the depreciation calculation in the business function Financials Extension (EA-FIN).
	If you are not currently using new General Ledger Accounting, import Customizing for the following areas from your Customizing system to your production system:
	Ledger definition and assignment of scenarios in new General Ledger Accounting
	Real-time integration of CO and FI
	Foreign currency valuation
	Initial balance carryforward
	If you want to check the Customizing settings for new General Ledger Accounting in your system, activate the Customizing structure for new General Ledger Accounting using report RFAGL_SWAP_IMG_NEW.
	Caution Do not import the activation of the new General Ledger Accounting. End of the caution.

Migration	New general ledger data migration:
	Start the generation of routines in General Ledger Accounting. Use report RGZZGLUX. to do this.
	Simulate the initial balance carryforward. Use report FGL_MIG_BCF to do this.
	If you are not currently using new General Ledger Accounting, migrate from classic General Ledger Accounting to new General Ledger Accounting using transaction FGL_MIG_NGL_POST. This transaction fills the line item table in new General Ledger Accounting (FAGLFLEXA)
	If you are currently using new General Ledger Accounting and are also using tables in the customer namespace here, you must migrate the data from these tables to the standard tables in SAP Accounting powered by SAP HANA. This aligns the relevant ledger configuration and your processes. Start migrating the G/L tables in your customer namespace using transaction FGL_MIG_CGLT. Or in Customizing, choose Migration to SAP Accounting powered by SAP HANA Migration of Customer G/L Tables , the first Customizing activity.

	SAP Accounting powered by SAP HANA data migration:
	Regenerate the CDS views. Choose transaction FINS_MIG_REGENERATE to do this. Or in Customizing, choose Migration to SAP Accounting powered by SAP HANA Migrating Transaction Data and Documents Regenerate CDS Views .
	Execute the technical reconciliation of Financial Accounting documents. Choose transaction FINS_RECON_DOC to do this. Or in Customizing, choose Migration to SAP Accounting powered by SAP HANA Migrating Transaction Data and Documents Analyze FI Documents .
	Check the result of the reconciliation. Choose transaction FINS_MIG_MONITOR_RC1 to do this. Or in Customizing, choose Migration to SAP Accounting powered by SAP HANA Migrating Transaction Data and Documents Display Status of Consistency Check for FI Documents. .
	Execute the technical reconciliation of Controlling documents using transaction FINS_CO_RECONCILE (test DLL views, replace the totals tables COSP and COSS) and check the result.
	Regenerate the operating concerns of CO-PA. To do this, choose transaction KEA0 (Maintain operating concern). Or in Customizing for Controlling, choose Profitability Analysis Structures Define Operating Concern Maintain Operating Concern .
	Migrate the data using the Migration Framework. Choose transaction FINS_MIGRATION to do this. Or in Customizing, choose Migration to SAP Accounting powered by SAP HANA Migrating Transaction Data and Documents Migrate Transaction Data and Documents .
	Check the result or status. Choose transaction FINS_MIG_MONITOR to do this. Or in Customizing, choose Migration to SAP Accounting powered by SAP HANA Migrating Transaction Data and Documents Display Status of Data Migration .
	The migration of data runs automatically in the following steps: Step 'FAGLFLEXT' processes the data for FAGLFLEXT View Step 'KNCX' processes the data of KNC1 and KNC3 Views Step 'LFCX' processes the data of LFC1 and LFC3 Views Step 'CO' fills the new fields in the accounting documents (BSEG, COEP, COBK) Step 'FAGLBSXS' transfers data from FAGLBSIS and FAGLBSAS to BSEG_ADD Step 'BCF' creates the initial balance carryforward Step 'GLT0' processes the data for the GLT0 View
	Start entering the due dates in FI documents using transaction FINS_MIG_DUE or in Customizing, choose Migrating to SAP Accounting powered by SAP HANA Migrating Transaction Data and Documents Enter Due Dates in FI Documents .
	Check the result or status using transaction FINS_MIG_MONITOR_DUE, or in Customizing, choose Migrating to SAP Accounting powered by SAP HANA Migrating Transaction Data and Documents Display Status of Entry for Due Dates in FI Documents .
	Define the offsetting account determination type. In Customizing, choose Migration to SAP Accounting powered by SAP HANA Migrating Transaction Data and Documents Define Offsetting Account Determination Type .
	Fill the offsetting account in FI documents. Choose transaction FINS_MIG_GKONT to do this. Or in Customizing, choose Migration to SAP Accounting powered by SAP HANA Migrating Transaction Data and Documents Fill Offsetting Account in FI Documents .
	Check the result or status using transaction FINS_MIG_MONITOR_GKO. Or in Customizing, choose Migration to SAP Accounting powered by SAP HANA Migrating Transaction Data and Documents Display Status for Entry of Offsetting Account in FI Documents. .
	Consistency checks to compare against the status before the migration:
	Execute the technical reconciliation of the migrated Controlling documents. Choose transaction FINS_MIG_CHECK to do this. Or in Customizing, choose Migrating to SAP Accounting powered by SAP HANA Migrating Transaction Data and Documents Start Check for Migrated Accounting Documents and check the result using the results list.
	Execute the technical reconciliation of the migrated transaction figures. Choose transaction FINS_RECON_VIEWS to do this. Or in Customizing, choose Migration to SAP Accounting powered by SAP HANA Migrating Transaction Data and Documents Reconcile Transaction Figures .
	Check the result of the reconciliation. Choose transaction FINS_MIG_MONITOR_RC2 to do this. Or in Customizing, choose Migration to SAP Accounting powered by SAP HANA Migrating Transaction Data and Documents Display Reconciliation Status of Transaction Figures .
	If you implement new General Ledger Accounting with the migration from Smart Financials, execute the following actions for the migrated ledgers: Choose transaction GCAC (Ledger comparison): Reconcile general ledger 0 with leading ledger 0L. If you took data for the initial balance carryforward from consolidation ledger 09, reconcile ledger 09 with leading ledger (0L). If you have kept a currency ledger, reconcile this with the leading ledger 0L.
	Activate new General Ledger Accounting by importing the Customizing settings from the Customizing system.
	Activate business functions FIN_GL_CI1, FIN_GL_CI2 and FIN_GL_CI3 by importing the Customizing settings from the Customizing system.
	Import Customizing for new Asset Accounting.

After the Migration	Business reconciliations to compare against the status before the migration:
	Create the closing documentation to compare the data with the same reports and selection criteria as the documentation before the migration. SAP recommends the following objects for this:
	The financial statements (program RFBILA00)
	The asset history sheet (report 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 balances (program RFSSLD00).
	General ledger line items (program RFSOPO00)
	The compact document journal (program RFBELJ00)
	Vendor sales (program RFKUML00)
	The vendor open item list (program RFKOPO00)
	Customer sales (program RFKUML00)
	The customer open item list (program RFKOPO00)
	Customer recurring entry original documents (program RFDAUB00)

	Postprocessing:
	Unblock all users in the system
	Open the periods in Financial Accounting and in Controlling (Plan/Actual).
	Link the Financial Accounting document with the corresponding Controlling document. Choose transaction FINS_MIG_LINK to do this (Create link between Controlling documents and FI documents). Or in Customizing, choose Migration to SAP Accounting powered by SAP HANA Migrating Transaction Data and Documents Create Links Between Controlling Documents and FI Documents . You can execute this step parallel to the consistency checks after the migration.
	Check the result or status. To do this, either use transaction FINS_MIG_MONITOR_LNK or in Customizing, choose Migration to SAP Accounting powered by SAP HANA Migrating Transaction Data and Documents Display Status of Links Between Controlling Documents and FI Documents .
	Execute the technical reconciliation of the migrated Controlling documents. To do this, use transaction FINS_MIG_CHECK or in Customizing, choose Migration to SAP Accounting powered by SAP HANA Migrating Transaction Data and Documents Start Check for Migrated Accounting Documents .
	Perform an update for Controlling documents. To do this, use transaction FINS_PRC or in Customizing, choose Migration to SAP Accounting powered by SAP HANA Migrating Transaction Data and Documents Fill Profit Center Fields in CO Line Items . The fields Profit Center and Partner Profit Center of the Controlling document are filled in this step.
	Check the result or status using transaction FINS_MIG_MONITOR_PRC. Or in Customizing, choose Migration to SAP Accounting powered by SAP HANA Migrating Transaction Data and Documents Display Status of Filled Profit Center Fields in CO Line Items .
	If you are not currently using new General Ledger Accounting, post the historical CO data in SAP Accounting powered by SAP HANA subsequently. To do this, choose report FAGL_COFI_TRANSFER_CODOCS (Transfer CO documents to external Accounting).
	If you are currently using Data Aging, create cold partitions for the backup tables in the indexes (BSAD_BCK, BSAK_BCK, BSAS_BCK, BSID_BCK, BSIK_BCK, BSIS_BCK, FAGLBSIS_BCK, FAGLBSAS_BCK).
	If you are using Data Aging, start moving the indexes in the coldstore of the database using transaction FINS_MIG_INIT_COLD (Transfer data to cold database area). Or in Customizing, choose Migration to SAP Accounting powered by SAP HANA Transferring Data to Coldstore Transfer Application Indexes .
	Check the result or status using transaction FINS_MIG_MONITOR_CLD (Display Status of Transfer of Data to Cold Database Area). Or in Customizing, choose Migration to SAP Accounting powered by SAP HANA Transferring Data to Coldstore Display Status .