Learn the necessary configuration, migration steps, post-migration steps, tips, and tricks during an SAP Simple Finance migration.
After reading this article, you’ll learn:
- Pre-check programs to run before a migration to SAP Simple Finance
- Necessary configuration with logical explanations
- Migration steps with logic
- Post-migration steps
- Tips and tricks
SAP S/4 HANA Finance, On-Premise Edition has product versions SAP Simple Finance 1503 and SAP S/4HANA Finance 1605, the latter being the successor of the former.
If you want to implement and use SAP Accounting powered by SAP HANA, you have to migrate the existing user data from the General Ledger Accounting (FI-GL), Asset Accounting (FI-AA), Controlling (CO), and Material Ledger areas. Such a migration of data is necessary because SAP Accounting powered by SAP HANA rests on a uniform data model for all accounting areas. The universal data table ACDOCA contains all the line item documents from FI, FI-AA and CO. All postings of these applications are written to the new table after the installation and migration are complete.
I describe the migration to SAP Simple Finance 1503 with the entire life cycle covering pre-migration, migration, and post-migration steps. I also shed light on real-life lessons learned during this migration.
This will help companies planning to start the journey of migration to prepare and execute the process.
Before you begin an SAP Simple Finance 1503 migration, the following consideration is required: SAP Note 2119188 should be checked to identify if the industry solutions and other solutions are supported. It is important to get the latest Service Pack Stack (SPS) installed. This reduces the efforts in implementing SAP Notes that could have been a part of the solution had the latest SPS been installed.
You should give special consideration to the following:
Profitability Analysis (CO-PA): Is the company already using CO-PA? If yes, is it costing-based CO-PA, account-based CO-PA, or both? If account-based CO-PA needs to be activated as a part of migration, it is important to inject enough time in the plan to discuss its impact.
Depreciation areas: Consider the completeness of the depreciation areas and if there will be any additional depreciation areas required (for example, depreciation areas for parallel currencies).
Custom reports and enhancements: SAP promises minimal disruption, but any custom program that writes to a table (which is removed and changed to a view) needs to be re-coded. Such situations need proper consideration. SAP provides a code inspector to check such codes.
Localization: Any specific tax reports and country-specific programs should also be considered and a separate localization consultant with apt knowledge on local taxes should be a part of the team.
Pre-Checks Before an SAP Simple Finance Migration
The pre-check is a set of programs run to check the correctness and compatibility of the existing system. During all the test phases (e.g., sandbox, unit, and quality box) I would suggest you run the pre-check and migration on a dump of production. It is done before any kind of upgrade or installation.
Furthermore, it is prudent to ensure consistency across modules. SAP proposes the use of some transaction codes that Ajay Maheshwari writes about in “Plan Your SAP S/4HANA Finance Migration with These Tips.”
For a more comprehensive check, SAP provides some reports that can be installed via SAP Notes. Here are the details:
Check prerequisites for New Asset Accounting: (SAP Note 1939592). Among other things, the report checks:
- If a depreciation area for each parallel currency exists
- If the periodic posting needs to be run
- If there is any component (e.g., classic real estate or joint venture accounting) that the new FI-AA does not support
Check customizing settings: (SAP Notes 2240666 and 2129306): Among other things, the report checks:
- If the currency settings are consistent and adaptable by SAP S/4HANA tables
- If the fiscal year variant of the company code and controlling area are consistent
- If the company code validation checkmark is set in the controlling area
- Are there any valuation scenarios (e.g., transfer prices) that are not compatible with SAP S/4HANA Finance?
Download report RFINDEX_NACC, which is a very comprehensive check report. I recommend you run it at least with the option Indexes vs. Documents for a start. The results will highlight any discrepancy between the table BSEG and index tables (BSXX).
Any discrepancy found in the above check reports should be rectified before proceeding.
Several configuration steps for migration of the SAP General Ledger, CO, new FI-AA, and house banks are required, and I describe some of the important ones in this section.
After the successful installation of the SAP Simple Finance 2.0 add-in, the SAP Project Reference Object (SPRO) screen menu has a new node as highlighted in Figure 1.
A new node for migration in the SPRO screen