SAP S/4HANA Conversion in Finance

SAP S/4HANA Regional Implementation Group

June 2021

CUSTOMER
Disclaimers

The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the
permission of SAP. Except for your obligation to protect confidential information, this presentation is not subject to your
license agreement or any other service or subscription agreement with SAP. SAP has no obligation to pursue any
course of business outlined in this presentation or any related document, or to develop or release any functionality
mentioned therein.

This presentation, or any related document and SAP's strategy and possible future developments, products and or
platforms directions and functionality are all subject to change and may be changed by SAP at any time for any reason
without notice. The information in this presentation is not a commitment, promise or legal obligation to deliver any
material, code or functionality. This presentation is provided without a warranty of any kind, either express or implied,
including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-
infringement. This presentation is for informational purposes and may not be incorporated into a contract. SAP assumes
no responsibility for errors or omissions in this presentation, except if such damages were caused by SAP’s intentional or
gross negligence.

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.

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 2

Agenda

Session Focus
System Conversion (without downtime optimization techniques)

Session Objective
Create awareness about particularities of Finance Conversion within SAP S/4HANA Conversion

▪ Conversion Approach
▪ Lessons Learned for Finance
▪ Conversion in Detail/Phases, Check Reports, Finance Table Cleanup After Conversion
▪ Finance Conversion: IMG Activities, Migration Monitor and Error Analysis Navigation

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 3

SAP S/4HANA system conversion
Transition paths overview

SAP ERP 6.0, EHP xx SAP S/4HANA 2020

AnyDB or SAP HANA SAP HANA 2.0

Notes on source system Notes on target system

▪ Unicode is required ▪ SAP S/4HANA 2020 is based on ABAP Platform 2020
▪ ABAP single stack required ▪ Consider different OS coverage since ABAP Platform 1809
▪ SAP HANA database not required

Conversion requirements incl. min./max. SP-level on source system: 2620910 - SAP S/4HANA … and SAP BW/4HANA 1.0:
2884313 - SAP S/4HANA 2020: Release Information Note Recommended Application Server Platforms

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 4

The SAP S/4HANA family and system conversion paths

SAP Business Suite SAP S/4HANA family

(e.g. BS7i2013)

SAP S/4HANA Cloud

SAP S/4HANA

SAP Simple Finance 1503

SAP S/4HANA Finance 1605

SAP ECC System

On-Premise or Private Cloud
(on AnyDB or
on SAP HANA)
Release strategy: 1511 | 1610 | 1709 | 1809* | 1909 | 2020
SAP S/4HANA 2020

*With SAP S/4HANA 2020, FPS02, conversion target 1809 got invalid
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 5
Finance conversion in the context of SAP S/4HANA On-Premise Edition

“Uplifting” an existing SAP ERP system to

System ERP System On-Premise SAP S/4HANA
Conversion
with all its code, configuration and data

▪ Conversion Guide for SAP S/4HANA 2020 refers to note 2332030 for Finance Conversion.
▪ KBA 2741967 How to plan and execute the financial data migration during conversion of SAP ERP solution to S/4HANA.
▪ KBA 2804470 Best practices for the SAP S/4HANA Conversion: General Ledger data migration.
▪ SAP conversion programs read data from old tables and transfer them to new structures.
▪ Compatibility views (tables) are created to make old reports / transaction codes work.
▪ Configuration/customizing has to be adapted in some areas (see Simplification List).
▪ For Finance the customizing has to be done during Conversion. It cannot be prepared in the old system.
▪ With a system Conversion it is not possible to activate new functionalities like document split, parallel ledgers etc.
Classic general ledger is transferred technically to new general ledger/ACDOCA without activating new functionalities.
▪ If you are using SD-Revenue Recognition, you need to migrate (implement) to new RAR before your conversion to
S/4HANA. Note 2582784 FAQ's and Guidance RAR
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 6
SAP S/4HANA Universal Journal
Adoption paths

Classic GL in SAP Migrate to New

Universal Journal
ERP GL
Parallel Ledgers Doc. Splitting Parallel Ledgers Doc. Splitting

Classic GL in SAP Universal Subsequent

ERP Journal Introduction
Parallel Ledgers Doc. Splitting

1610 Parallel Ledgers

1709 Document Split

1809 New Currency

1809 New Depreciation Area

1809: SAP Note 2403248 - FI-AA (new): Availability of RAFABNEW

1809: SAP Note 2334583 - Introduction of new currencies in SAP S/4HANA
1809: SAP Note 2403248 - FI-AA (new): Availability of RAFABNEW
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 1909: SAP Note 2805659 - Public Sector Management restriction note 7
SAP S/4HANA Conversion Project
An overview of a conversion project and the key tools

Uninstall ABAP Add-ons Simplification SUM 2.0, incl.

During System Update Item Checks Prerequisite Check

Planning phase Preparation phase Realization phase

Application
Application
Transformation System Maintenance Pre Custom code
code Software Update specific
specific follow-
Navigator requirements planner checks preparation
preparation Manager (SUM) follow-up
up activities *)
activities
For example:
Database migration
Roadmap Cross-application & application specific preparation • Preparation and
activities *) Software update Migration of
Viewer
Customizing
Data conversion

For example:
Simplification List • Data Migration
SAP S/4HANA • IMG Activities after
• Identify and review the relevant Simplification items
Readiness Check Migration
• Run Customizing pre-checks and adapt settings
• Application specific
• Check consistency and reconcile data follow-up activities
Remote Scans with ABAP
• Period end closing activities
Test Cockpit • Material number field
• Document your posting data length extension
Simplification
• Archive data you no longer need
Item Catalog • Testing & Validation
• CVI migration
• Material number field extension
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 8
*)This is not a full list, only some key examples
Agenda

Session Focus
System Conversion (without downtime optimization techniques)

Session Objective
Create awareness about particularities of Finance Conversion within SAP S/4HANA Conversion

▪ Conversion Approach
▪ Lessons Learned for Finance
▪ Conversion in Detail/Phases, Check Reports, Finance Table Cleanup After Conversion
▪ Finance Conversion: IMG Activities, Migration Monitor and Error Analysis Navigation

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 9

Finance Conversion
Key takeaways / Lessons learned

Most of the projects, are having the following pain points, mostly in the Finance area:

▪ Inaccurate project estimates

▪ Unexpected roadblocks after start of the conversion project – functionalities not available, add-ons not
supported..
▪ Data inconsistencies
▪ Lack of expertise
▪ Product related issues in the standard migration programs
▪ Insufficient testing

Accurate project planning can be done only after the first test conversion (in Sandbox/Copy of
production) has been finished. Specifically to Finance data migration, this point is relevant because the
amount of data inconsistencies cannot be accurately foreseen. Additionally, the complexity and the duration
of the Finance tasks cannot be fully comprehended.

Plan sufficient time for testing including roles and changes in authorizations

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 10

Finance Conversion
Key takeaways / Lessons learned

It is recommended to identify items which can be adressed as a preparation within the start release
and consider setting up “pre-projects “, for example:
– Clean-up of FI data inconsistencies
– Clean up of custom code and replace custom code with standard functionality where possible
– Clean-up of vendor/customer master data and activation of CVI
– Check if (consistent) archiving can be done to reduce the data volume to be converted.
– New Depreciation engine activation/ new asset accounting implementation
– Customizing adaptation to meet prerequisites in FI-AA, FI etc

The conversion to SAP S/4HANA requires application consultants with in-depth FI, CO, and Asset
Accounting knowledge, to be already involved in the preparation phase.
Plan a dedicated authorization expert role as well as an SAP Fiori expert role as part of the project team to
work with the busines (functional and basis).

Maintain a detailed ‘run book’ with as much as possible details, all the steps performed, the sequence, the
errors and the resolution and also the time required for each activity, if applicable to be repeated.

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 11

Finance Conversion
Key takeaways / Lessons learned

Finance Conversion has to be finished. There is no possibility of a general roll-back to the old system. So,
Finance Conversion must be Set to Completed.

Finance Conversion is run per client – No exclusion of Company Codes is possible once
FINS_MIG_STATUS has started

Run and analyze all recommended pre-checks in order to identify show-stoppers like inconsistencies in
currency settings, compatibility of add-ons (especially from 3rd-party vendors), customer specific programs
that use standard tables/fields. Check if BW extractors still work in SAP S/4HANA (see SAP Note 2500202).

Create small Business Blueprint for Finance Conversion to clarify additional customizing settings for
target release (and which items are postponed to later).
▪ SAP Fiori and embedded analytics should be considered to leverage the full potential of SAP S/4HANA
▪ Consider migrating from SAPscript forms to Adobe Document Services

Business might have to clarify some topics with auditors (e.g. which check reports to run before/after
Conversion, which errors / warnings are acceptable). Consider to involve them as early as possible.
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 12
Finance Conversion
Key takeaways / Lessons learned

Practice shows that there could be a lot of inconsistency in the Asset Accounting area - start checks and pre-
checks as soon as possible (before conversion project).

Pay special attention to Asset Accounting Conversion: Year-end closing and month-end closing for the
previous month must be run. It will no longer be possible to post into the old structures once the Conversion has
been done. Adjustment postings only to the new tables with the new settings (no reversals with impact on other
modules or sub-ledgers like AA, AP/AR, SD, MM).

In order to improve performance, during finance data migration you can increase the number of parallel jobs in the
Mass Data Framework. At this point in time the whole hardware will be available for Finance Conversion (HANA
and Logistics Conversion are finished).

The SAP S/4HANA conversion might not decrease the database footprint initially, because all the obsolete data is
kept in the system. It is recommended to do a clean up of data after conversion- execute:
▪ Clean up obsolete tables in Finance: report FINS_MIG_OBSOLETE_DB_DEL from SAP Note 2190137
▪ Remove content from obsolete tables in MM-IM: see SAP Note 2569435
▪ Use the obsolete data handling tool in SAP S/4HANA: see SAP Note 2661837
▪ HANA sizing report: see SAP Note 1872170 and refer to FAQ document attached for additional steps.

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 13

Finance Conversion
Key takeaways / Lessons learned

Data inconsistencies are usually caused by the following:

▪ Inconsistencies caused by hardware defect (e.g. corrupt blocks)
▪ Inconsistencies caused by user handling errors (e.g. switching off line item display in FI without line item
deletion; missing balance carry forward; etc.)
▪ Customer reports without consistent updates on the database
▪ Manipulation on the database (e.g. direct postings on reconciliation accounts)
▪ Improper customizing changes (without respecting warning messages)
▪ Wrong migration (from former migrations)
▪ Wrong data management strategy (e.g. deletion of wrong data, archiving of FI data of the current fiscal
year)

Consider setting up a “Pre-project” specifically to resolve data inconsistencies in Finance. Several

test iterations might be needed to correct all the issues. Fix the errors in Production to leverage
conversion cycles and to keep estimated dates of the project

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 14

Finance Conversion
Key takeaways / Lessons learned

Application consultant , technical consultants and business people have to work on the data
inconsistencies.

If you consider to accept data inconsistency, consider to also involve auditors in this process.

There is an increased risk of inconsistencies after data conversion projects (for example new GL migration),
New Asset Accounting implementation, SLO projects for additional currencies introduction.

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 15

Finance Conversion
Key takeaways / Lessons learned
In a typical conversion project, multiple SI checks occur manually and automatically (via SUM pre-processing during
Business Uptime) during Preparation phase. If customers experience long running SI check executions then it may be
critical to consider what transactions occur during the Business Uptime phase of the project.

Certain financial transactions, mainly relating to Asset Accounting, if not completely processed, may result in subsequent
errors during the later SI checks and cause SUM execution to stop - resulting in project delays.

Consider blocking asset accounting users and/or transactions after SUM begins its preparation phase to insure success
of all subsequent SUM initiated SI checks.

During the initial SUM SI checks (during the SUM Configuration phase), some discrepancies may be identified as
warnings, and these same issues will cause a hard error when the second SI check (during the SUM Preprocessing
phase) is performed. Care must be taken during this interval to recognize the need for issue resolution before the
second SUM phase. In addition, since this timeframe is occurring during Business Uptime, any new transactions should
also be analyzed to make sure complete processing has occurred to prevent a project stopping error during the second
SUM SI check. See blog for details: https://blogs.sap.com/2018/03/26/sap-s4hana-simplification-item-check-how-to-do-it-right./

Immediately after user lockout, an additional manual SI check may be considered to confirm all FI postings have been
finalized. This additional SI check will proactively identify problems if AA users are allowed to continue performing
transactions during the SUM uptime phase. If the SI check is long running and therefore may impact project timeline,
executing report RAPERB2000 will identify any incomplete depreciation postings. (Note: Depreciation postings must be
completed prior to SUM execution because the depreciation calculation process changes in S/4HANA. Any converted
incomplete postings cannot be easily corrected after moving to a S/4HANA environment).
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 16
Lessons Learned
Project planning aspects: High-level example project plan

System Conversion to SAP S/4HANA

Cycle 1 Cycle 2 Cycle 3 Cycle 4 Cycle 5

PRD to “Sandbox” DEV Conversion QA Conversion PRD to “Sandbox” PRD Conversion

Purpose Purpose Purpose Purpose Purpose

 Test upgrade and migration  Establish SAP S/4HANA  Establish SAP S/4HANA  Mock cutover  Establish new PRD
steps with copy from development environment QA environment environment
 Final dress rehearsal
production  Enhance cookbook
 Refine cookbook  Optimize & validate E2E  Utilize downtime-minimized
 Create upgrade / migration
Note  Testing environment: business downtime approach
cookbook
− Integration  Finalize & validate Note
 Execute multiple technical  Upgrade & conversion
steps will differ from − Functional regression cookbook  Execute end-to-end
iterations to familiarize with
production − Operational readiness  Finalize & validate business downtime
process
− User acceptance cutover plan precisely as defined within
 Perform mandatory code
Note  Testing environment: cutover plan
adaptations and simple  Business Function Testing
 Check business process code optimizations of new/adapted processes − Infrastructure testing  Execute technical steps
requirements to be − Post-cutover operational precisely as defined in
 Perform post-conversion performance testing
performed and perform cookbook
steps to adapt business
ABAP code analysis, house-
processes  Plan code optimization
keeping before the migration projects

DEV: Development System QA: Quality Assurance System PRD: Productive System

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 17

Agenda

Session Focus
System Conversion (without downtime optimization techniques)

Session Objective
Create awareness about particularities of Finance Conversion within SAP S/4HANA Conversion

▪ Conversion Approach
▪ Lessons Learned for Finance
▪ Conversion in Detail/Phases, Check Reports, Finance Table Cleanup After Conversion
▪ Finance Conversion: IMG Activities, Migration Monitor and Error Analysis Navigation

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 18

Conversion Overview (As Shown in Conversion Guide)

Conversion to SAP S/4 HANA follows a defined process. The following graph gives an overview on
the tools, phases and activities involved in this process.
Prepare Phase Realize Phase

t1,2 t3 t4 t5 t6 t7

Planning & Cross-app & app-

Maintenance Custom Code Software Update
System SI-Check specific follow-on
Planner Migration Manager (SUM)
Requirement activities

Cross-application & application specific DB Migration

preparation activities
Software Update
SAP Readiness check & Simplification Item ** incl. Migration of
Data Conversion
*incl preparation Catalog Finance Customizing
of Financial Data and Data

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 19

 SAP S/4HANA System Conversion
Overview of finance migration steps and checks
Customizing Checks

Analyze Transactional data

2nd SUM SI Check

1st SUM SI Check Data Migration checks

Application specific
SUM prepare phase SUM realize phase
follow-on phase SAP S/4HANA
Target Release
Start Release time
Conversion of Accounting
Preparation Phase Preparation Data Activities After
and Migration
Migration Migration
of Customizing
SAP ERP
6.0x Review the relevant Simplification items
Run detailed (manual) Simplification Item (SI) Check General Ledger migration
Prepare Asset Accounting and Material Ledger Asset Accounting migration
Reconcile subledgers with general ledger and standard Controlling migration
consistency checks Material Ledger migration
Period end closing activities
Migration of house bank accounts
Document your posting data
Migration of financial documents to trade finance
Credit management migration
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER
Migration of accrual engine data 20
Consistency Checks
Preparation Phase

Start Release
Preparation Phase
Uptime Downtime
Customizing Consistency Checks
Data Quality Check of Customer-Vendor-Integration
Consistency checks of Transactional Data & Totals
manually via SAP ERP standard reports, list of proposed reports (See SAP Note 2332030 for Conversion Guide)
ERP 6.0x
Customizing Consistency Checks Data Quality Check of Customer-Vendor- Consistency checks of Transactional Data
Integration
▪ SAPF190 / TFC_COMPARE_VZ
▪ SimpIifcation Item (SI) check: Report ▪ Pre-conversion check for business
▪ RAABST02 / RAABST01 (SAP Note 2390881)
/SDF/RC_START_CHECK partners is part of the SI check since 1709
▪ RM07MBST/ RM07MMFI
(SAP Note 2399707) release
▪ RGUCOMP4
New in ERP 6.0x ▪ Optional: FAGL_MM_RECON / RFINDEX / RCOPCA44
▪ Please refer to SAP Note 2245333 and 2618023
for error messages and possible solution SAP Note 2755360 - Reconciliation prior (See SAP Blog Post: Consistency checks in Finance)
to S/4HANA Conversion New in ERP 6.0x
▪ Pre-Check Report for migrating to New Asset ▪ FIN_CORR_RECONCILE SAP Note 2896400 - Reconciliation of Asset Accounting
Accounting is part of the SI check since 1809 ▪ FIN_CORR_DISPLAY Inconsistencies in ECC prior to S/4HANA Conversion
release (check the results for element 'Asset New in ERP 6.0x ▪ FIN_AA_CORR_RECONCILE
Accounting' (ID SI2: FIN_AA) ) ▪ FIN_AA_CORR_DISPLAY
SAP Note 2887318 - Analysis and
Correction prior to S/4HANA Conversion
▪ FIN_CORR_MONITOR
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER (SAP Note 2956096 for correctable errors) 21
Consistency Checks
During Conversion of Accounting to S/4HANA
Customizing Checks

Analyze Transactional data

Data Migration checks

S/4HANA

Post Processing Uptime

Target Release

▪ Check Customizing Settings prior to migration: ▪ Analyze Transactional data ▪ Data Migration checks
Report FINS_MIG_PRECHECK_CUST_SETTNGS ✓ Report FINS_MASS_DATA_MASTER ✓ Executed during migration as a part of Start and Monitor
(SAP Note 2129306) ✓ Executed before start of data migration Data Migration activity (Transaction FINS_MIG_STATUS)
▪ Consistency Check of General Ledger Settings ✓ Can be skipped during productive run
Report FINS_CUST_CONSISTENCY_CHECK ✓ Input for automatic correction of certain New 1909
▪ Check the prerequisites for activating new Asset inconsistencies in the source system
Accounting. Report report FIN_CORR_MIG_ERROR_SFIN SAP KBA 2714344 - Financial data
RACHECK_ACTIVATION_PARVAL (SAP Note 2225322) migration to SAP S/4HANA: Most
frequent Error Messages – Information
and Recommendations

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 22

Important Checks During Data Migration Phase

Phase Step Checks – Examples

Migration of Cost Elements and Customizing Check Consistency of G/L Accounts and Check whether the G/L accounts and cost
Cost Elements elements are consistent with each other

Technical Check of Transaction Data Analyze Transactional Data Check whether all FI documents are
complete and correct
Technical Check of Transaction Data Reconcile Transactional Data BSEG vs. FAGLFLEXA; BSEG bal. Zero;
etc.; find missing BKPF
Enrichment of Data Check of Migrated Documents Cross-check of fields replicated from
BKPF to BSEG, COBK to COEP,
Application Index to BSEG_ADD
Migration of Line Items Check Migration of Accounting E.g. BSEG vs. ACDOCA; compatibility
Documents to Universal Journal Entry views are compared with original values

Migration of Balances Check Migration of Balances View vs. Backup table, e.g. view of
FAGLFLEXT vs.
FAGLFLEXT_BCK

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 23

Consistency Checks
During SAP S/4HANA Conversion
Customizing Checks

Analyze Transactional data

Data Migration checks

S/4HANA

SUM Phase Post Processing Uptime

Target Release

Start Release
Preparation Phase
Uptime
Simplification Item (SI) Check
Pre-check of customizing for FI-AA
Downtime
=
Consistency checks of Transactional Data & Totals –
ERP 6.0x manually via SAP ERP standard reports, list of proposed reports (See SAP Note 2332030 for Conversion Guide)

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 24

SAP ERP Consistency Checks of Transactional data vs.
SAP S/4HANA Consistency Checks of Transactional Data
SAP ERP – PRD SAP S/4HANA SAP S/4HANA –
Consistency Checks of Preparation Phase Test System Consistency Checks
Test Environment
▪ Several ERP Standard consistency check reports ▪ Conversion Framework with automatic
▪ Focus general consistency checks parallelization and job scheduling

▪ Start manually
▪ No framework for parallelization
▪ Includes difficult to understand expert reports
= ▪ HANA optimized consistency checks
▪ Checking whole database with all fiscal years
▪ Checks are focused to detect SAP S/4HANA
conversion relevant issues

Impact
▪ In the preparation phase SAP ERP consistency checks are not able to identify all inconsistencies
→ Data correction in SAP S/4HANA conversion is an iterative process
→ Use the S/4HANA checks during a test conversion to clean up your data in the source system
→ There are now available new programs to check and correct data inconsistencies in the area of General Ledger and
Asset Accounting (only checks) . These programs are recommended and they are more comprehensive than the previous
available correction program one based on the input from Analyze transactional data check during test conversion (report
FIN_CORR_MIG_ERROR_SFIN, SAP Note 2225322)

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 25

Finance Migration Preparation Phase
Check and correct your finance data prior to conversion – General Ledger

HOW TO FIND HOW TO RESOLVE

2755360 – Reconciliation prior to S/4HANA Conversion: 2714344 – Financial data migration to SAP S/4HANA: Most
▪ Perform data consistency checks for FI-GL in SAP ERP on anyDB frequent Error Messages – Information and Recommendations

2887318 – Analysis and Correction prior to S/4HANA Conversion

(See the attachment “FIN_CORR_MONITOR_User Manual.docx” )

2956096 – FIN_CORR_MONITOR: Information on correctable errors

Transaction FIN_CORR_RECONCILE

Transaction FIN_CORR_DISPLAY

Transaction FIN_CORR_MONITOR
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 26
Finance Migration Preparation Phase
Check and correct your finance data prior to conversion – Asset Accounting

HOW TO FIND HOW TO RESOLVE

2896400 – Reconciliation of Asset Accounting Inconsistencies in ECC prior to 2714344 – Financial data migration to SAP S/4HANA: Most
S/4HANA Conversion: frequent Error Messages – Information and Recommendation

Transaction FIN_AA_CORR_RECON

Transaction FIN_AA_CORR_DISPLAY

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 27

SAP KBA 2714344 - Financial data migration to SAP S/4HANA: Most frequent Error
Messages – Information and Recommendations
• This Note covers the most frequently seen error messages. It does not cover all error messages that could potentially
come up during the Financial data migration.
• There are some typical reasons for the errors presented, however the particular situation in the project may be different.
You should verify the situation with experienced SAP consultant before applying suggested fixes.

Additional Information / KBAs

2741967 How to plan and execute the financial data migration during conversion of SAP ERP solution to SAP S/4HANA.
2804470 Best practices for the SAP S/4HANA Conversion: General Ledger data migration.
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 28
Finance Table Cleanup After SAP S/4HANA Conversion

Note 2190137 – S/4HANA Finance: Reduce memory footprint of obsolete tables

Describes how customer can reduce the database memory footprint caused by obsolete tables of
several financials application components after data migration to SAP S/4HANA Finance or
conversion to SAP S/4HANA.

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 29

Agenda

Session Focus
System Conversion (without downtime optimization techniques)

Session Objective
Create awareness about particularities of Finance Conversion within SAP S/4HANA Conversion

▪ Conversion Approach
▪ Lessons Learned for Finance
▪ Conversion in Detail/Phases, Check Reports, Finance Table Cleanup After Conversion
▪ Finance Conversion: IMG Activities, Migration Monitor and Error Analysis Navigation

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 30

SAP S/4HANA system conversion
Overview of the Conversion Process - Application specific follow-up activities

Preparation phase Realization phase

Planning & System Maintenance Custom

Custom code Software Update Application
Cross-appspecific
& App-specific
SI-Check
requirements planner preparation
Migration Manager (SUM) follow-up
follow-up activities
activities

Database migration Conversion of Accounting to SAP

S/4HANA
Cross-application & application specific preparation activities Software update
Preparation and Data Activities
Data conversion Migration of After
Customizing Migration Migration
Preparation in Finance
• Preparation and Migration of
Customizing
• Data Migration
There are no more postings allowed after
• Activities after Migration
start of technical conversion with SUM until
completion of conversion of accounting!

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 31

Conversion of Accounting – Realization Phase
Overview (1/2)
Realization Phase
ECC SAP S/4HANA
Conversion of Accounting
Software Preparation and
Activities After
Update Migration of Data Migration
Migration
Manager (SUM) Customizing

Downtime Uptime
No postings allowed
Migration completed

Preparations and Migration of Customizing

▪ Generally steps done in “DEV” and transported to other systems

Data Migration
▪ Required to be done in each system
▪ No postings allowed during these steps

Activities after Migration

▪ System is open for users
▪ Posting is allowed

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 32

Conversion of Accounting – Realization Phase
Overview (2/2)
Realization Phase
ECC SAP S/4HANA
Conversion of Accounting
Software Preparation and
Activities After
Update Migration of Data Migration
Migration
Manager (SUM) Customizing

Downtime Uptime
No postings allowed
Migration completed
Conversion of Accounting to SAP S/4HANA
▪ All the migration activities and documentation are in the IMG
▪ Perform activities in the right sequence
▪ Do not skip any customizing activities
▪ Finance migration has to be executed per client
▪ All company codes are migrated
– Mark company codes as template to disable checks with
FINSC_CO_CD_TEMPLATE: SAP Note 2159452
▪ SAP Note 2522155 for Company Code Specific Conversion with SAP LT
▪ Conversion from start release SAP Simple Finance, SAP S/4HANA Finance or
SAP S/4HANA 1511: SAP Note 2450377
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 33
Conversion to S/4HANA on SAP Help
https://help.sap.com/viewer/p/SAP_S4HANA_ON-PREMISE

Conversion Guide (PDF)

Supports the conversion from SAP ERP
to SAP S/4HANA

Application-Specific Preparations
and Follow-On Activities :
Converting Accounting Components
to S/4HANA Guide attached to note
2332030 for FI Conversion.

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 34

Conversion of Accounting – Realization Phase Preparation and
Customizing
Data Migration
Activities After
Migration

Preparation and migration of Customizing in Finance - Overview

3. Preparations and 4. Preparations and 5. Preparations and

1. Check 2. Set number of
Migration of Migration of Migration of
customizing settings Jobs in Mass Data
Customizing for Customizing for Customizing for
prior to Migration Framework
General Ledger Accrual Engine Asset Accounting

6. Preparations and 7. Preparations and 9. Preparations for 10. Preparations and

8. Preparation for
Migration of Migration of Migration of Migration of
Migration of House
Customizing for Customizing for Financial Documents Customizing Credit
Bank Accounts
Controlling Material Ledger to Trade Finance Management

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 35

Data Migration phase in Finance Preparation and
Customizing
Data Migration
Activities After
Migration

Overview
▪ Start and monitor migration
– Transactional data is transformed into the new data model of the
universal journal (SAP Note 2408083 - FAQ: Data Model of S/4HANA
Finance Data Migration)
– Secondary cost elements are merged into the G/L account master data
▪ As of S/4HANA 1909 FPS01, IMG activity "Transport Accepted Error
Messages" is available
▪ Migrate SD-FT Financial documents to Letters of Credit in TRM
– Financial document master data
– Assignment of sales orders to financial documents
– Risk Check Decisions for the blocked sales documents
▪ Migrate SD Credit management (FI-AR) to S/4HANA Credit
Start
management (FIN-FSCM-CR) Enhanced
1909
– Credit control customer master data(risk category, limit) FPS01

– Transaction UKM_BP to edit master data for credit management Complete

– Credit values of open orders and deliveries to credit exposure
– Create documented credit decisions for blocked sales documents
▪ Reconcile and Compare Migrated Data for before - after comparison.
▪ Set the migration to completed to unblock postings

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 36

Data Migration phase in Finance Preparation and
Customizing
Data Migration
Activities After
Migration

Start and Monitor Migration

Start and Monitor Migration:

FINS_MIG_STATUS is the main transaction to carry out and
monitor the results of data migration to Universal Journal
(ACDOCA). It
▪ Executes the data migration
▪ Ensures right sequence of migration activities
▪ Provides an Overview of all performed migration runs
▪ Provides a Status of activities processed in the run
– If activity runs into error, data migration is stopped
– Correct or accept the error to continue
– IMG activity "Transport Accepted Error Messages" (Report
FINS_MASS_DATA_MONITOR_MSG_TRA) to transport the
accepted errors
▪ Handles Load balancing and provides technical info concerning
the current run
▪ Allows to Repeat and reset migration activities (See SAP Note
2270540 and the detailed documents in the SAP Implementation
Guide)
– IMG: Conversion of Financials to SAP S/4HANA -> Data
Migration -> Start and Monitor Data Migration

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 37

Data Migration phase in Finance Preparation and
Customizing
Data Migration
Activities After
Migration

Start and Monitor Migration

Transaction FINS_MIG_STATUS – Migration Monitor

▪ During 1st Test it is important to get
an overview of all errors.
▪ After 1st test conversion: Errors
should be solved as soon as
possible in production environment
(before the next copy)
▪ Each error must be solved,
otherwise the conversion will be
incorrect
▪ Ignoring errors makes sense only in
specific cases
(e.g. performance test, agreement
with auditors due to old or no longer
used data)

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 38

Data Migration phase in Finance Preparation and
Customizing
Data Migration
Activities After
Migration

Start and Monitor Migration

Transaction FINS_MIG_STATUS
Double-click at any conversion
step (e.g. R21)

Double-click “Error Msg”/

“Issues found”

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 39

Data Migration phase in Finance Preparation and
Customizing
Data Migration
Activities After
Migration

Start and Monitor Migration

Via “Show Error Overview”

Button getting an overview
about errors.

Via “Show Detail” Button

getting a detailed list per
error type.

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 40

Data Migration phase in Finance Preparation and
Customizing
Data Migration
Activities After
Migration

Monitor Migration

Statistics of migration activities

▪ Number of Table Entries
▪ Status
▪ Completion %
▪ Number of errors, warnings
▪ Runtime
▪ CPU time

New 1909

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 41

Data Migration phase in Finance Preparation and
Customizing
Data Migration
Activities After
Migration

Monitor Migration

▪ In FINS_MIG_STATUS, the number of running

jobs can be adjusted dynamically, using the
buttons on Target Number of Jobs.
(Note: The two buttons for increasing or
decreasing the number of jobs are only shown
at runtime)

▪ Current CPU utilization (%): Better not beyond

85%

▪ To configure an appropriate number of parallel

tasks, you should monitor both your SAP (on
OS level) and HANA database (on OS level or
SAP HANA Cockpit) systems for CPU, disk I/O
activity and memory consumption. For more
details, please refer SAP Note 2351294
(section: Observe and manage available
system resources).

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 42

Data Migration phase in Finance Preparation and
Customizing
Data Migration
Activities After
Migration

Migration completion

▪ You can set migration to completed when

– You have finished all activities required for a complete migration
– You have completed your data migration and corrected all erroneous data

▪ Business needs to be involved before setting migration to completed

– To confirm and compare results before and after migration

▪ Last checks are performed automatically

– Customizing consistency
– Redirect check of obsolete tables to compatibility views
– Compare number of records in ACDOCA with BSEG,COEP, FAGLFLEXA
Complete
– All steps of the migration have been performed successfully

▪ After setting migration to completed, postings are allowed again

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 43

Activities after Migration in Finance Preparation and
Customizing
Data Migration
Activities After
Migration

Overview

▪ Data migration must be set to completed.

▪ Downtime is not required but recommended
▪ Transfer application index tables (BSID_BCK, BSAD_BCK,
...) to the cold area of the database to reduce memory
consumption
▪ Fill the new offsetting GL account fields (GKONT..) in
relevant document tables (BSEG*)
▪ Enrich Balance Carryforward of open item managed GL
accounts with additional dimensions not available in GL before
migration (e.g. from ML, AA)
▪ Reduce memory and database footprint
– Deactivate Reconciliation Ledger
– Run report FINS_MIG_OBSOLETE_DB_DEL to remove
obsolete tables from hot store and potentially from database
(SAP Note 2190137)

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 44

Multiple Sandbox iterations

Transports Transports
DEV QAS PRD Corrections

System Copy

System SAP S/4HANA 2020

PRD’ Conversion SAP HANA 2

The typical customer executes
2 – 5 sandbox iterations.

System SAP S/4HANA 2020

PRD’’ Conversion SAP HANA 2

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 45

Challenges of Data Consistency Topic

▪ The data consistency topic should not 5

Knowing how to correct inconsistencies
be underestimated. in an adequate way
▪ It has different knowledge levels.
4
▪ Expert support for resolving data Knowing how to find the root-cause and
inconsistencies might be required. the impact of an inconsistency

3
Knowing how to interpret the results of
Consistency Check Reports

2
Knowing how to correctly
execute Consistency Check Reports

1
Having a list of Consistency Check
Reports

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 46

Which Kind of Errors Can Appear During SAP S/4HANA Conversion?

An error can be caused by?

1 Customizing Inconsistency or
2 Inconsistent Transactional Data or
3 Missing SAP Note → Please check SAP Release Information Notes

Conclusion
• Test cycles should be done at high SPS with the corresponding HANA Revision
• You should check SAP KBA 2714344 - Financial data migration to SAP S/4HANA: Most
frequent Error Messages – Information and Recommendations

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 47

Components

Application Component
FI-GL FI-GL-GL-X
FI-AA FI-AA-AA
MM MM-IM-GF-INC
CO CO-OM
FIN Migration FIN-MIG
FIN Migration FI-AA FIN-MIG-AA
FIN Migration CO FIN-MIG-CO
FIN Migration FI-GL FIN-MIG-GL
FIN Migration ML FIN-MIG-ML

SAP Note 83020 - What is Support – What is Consulting: On Premise Solutions

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 48

SAP S/4HANA Conversion in Finance
Where to find more Information
SAP S/4HANA Conversion in Finance
Where to find more information…

▪ Conversion Guide for SAP S/4HANA: pdf on SAP Help

▪ Converting Accounting Components to SAP S/4HANA: pdf attached to SAP Note 2332030
▪ Migrating to New Asset Accounting (FI-AA (New)): SAP Help
▪ Task List for Conversion of Credit Management to SAP S/4HANA: pdf attached to SAP Note 2270544
▪ Help in Implementation Guide: IMG
▪ Implementation Roadmap for Conversion: SAP Roadmap Viewer
▪ SAP Training S4F03 Finance Migration to SAP S/4HANA : training.sap.com
▪ openSAP - System Conversion to SAP S/4HANA:
– Key Technical Topics in a System Conversion to SAP S/4HANA
– Key Functional Topics in a System Conversion to SAP S/4HANA
▪ SAP S/4HANA Conversion in Finance – Blogs
– Conversion to SAP S/4HANA On-Premise – what are the key problem areas?
– Conversion to SAP S/4HANA- Consistency checks in Finance: Part 1
– Conversion to SAP S/4HANA- Insights into Finance Data Migration
– Conversion to SAP S/4HANA – How to handle errors during finance data migration
– Finance Consistency Checks: FIN_CORR_MONITOR
– Fixed Assets Consistency Checks: FIN_CORR_AA_MONITOR
– SAP S/4HANA Simplification Item Check – How to do it right.
▪ Downtime optimization SAP Note 2293733 and SAP Note 693168 - Minimized Downtime Service (MDS)
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 50
Follow us

www.sap.com/contactsap

© 2021 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.
The information contained herein may be changed without prior notice. 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 or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP 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 platforms, 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, and they
should not be relied upon in making purchasing decisions.
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. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/copyright for additional trademark information and notices.