Overview of Migration (or System Conversion) process

 Pre-Conversion tasks
 Preparing the Conversion
 S/4HANA Installation
 Data Migration
 Post Migration

Pre-requisites and limitations

 Update SPAM to version 66 or higher for SAP S/4HANA 1709 and higher

The following checks can be executed in parallel (without the stack XML from MP)
 Software Update Manager prerequisite check (see SUM conversion guide)
 ABAP custom code checks

Steps in the conversion process

 Maintenance Planner conversion pre-Checks: Checks add-ons and business
functions to ensure compatibility with SAP S/4HANA. Also creates the stack
file used for the actual conversion process.
 Checks the compatibility of add-on software component versions present on a
given ERP technical system with SAP S/4HANA.
 Checks existence of a valid read RFC destination to the technical system from
the SAP Solution Manager in the SAP landscape (required to retrieve the
business function information).
 Checks if there are business functions in the technical system which are not
supported in the SAP S/4HANA. (results of this check may vary based on the
selected support package stack of SAP S/4HANA).
 Checks for existence of a connected Java system. If a dependency exists to a
Java system, the conversion planning stops and can only continue if the
product maintenance dependency in Maintenance Planner is removed.
 Checks if the note 2186164 is deployed on the SAP Solution Manager. If not
applied, the conversion planning is stopped.
 Conversion pre-checks: To check the system, Execute program
/SDF/RC_START_CHECK for SAP S/4HANA 1709 and above targets on the ERP
system.
 Custom code check tool: Checks custom code against a list of simplifications
developed for SAP S/4HANA. Ideally perform these checks at the same time
as your pre-checks.
 General and application-specific preparations: Manual activities to prepare
your system and applications.
 Software Update Manager (SUM): Automates the conversion process and
deploys the SAP S/4HANA software.
 Application-specific follow-up activities: Manual follow-up activities may also
be required.

Pre-conversion tasks

This section implicates technical preparations required before starting

installation/migration process.

 Review System Conversion guide form SAP. Key document for system
conversion.
  Download of OSS Notes needed for the S/4HANA Preparation.
 Perform cleansing and archiving activities. Archive all you can and cleanse
data not relevant like spool and job logs.
 If you do not have Customer Vendor Integration with Business Partner
(Business Partner Approach), you must do this before installation.
 Review versions of SUM, Maintenance Planner.
 Download DVD for installation.

All this will ensure a more efficient and less problematic migration process.

Preparatory Phase:

 Concept Planning
 Create Detail Project
 Business Requirement
 Business Blue Print
 Customizing
 Testing
 Complete Preparation

Execution Phase:

 Online Validation Activate

 Data Consistency Checks
 Enrichment of Open Items with document splitting characteristics
 Document Splitting Activate
 Fiscal Year Close
 Enrichment of Balances
 Carry-forward with Document splitting characteristics
 Reconciliation

Post Processing Phase:

 Manual Adjustment of Opening Balance

 Repost Opening Balance
 Zero Balance Check

Steps in Conversion:

 System Checks in Source system (ECC) including new asset accounting

checks-Up-time activity
 Business Partner Conversion (ECC)- Up-time activity
 Extract recon reports for comparison of data (eg: Trial Balance report)- Up-
time activity
 Installation including SUM import export. During import and export , the data
including configuration is moved to HANA, however the data still resides in
old tables like BSEG, etc and ACDOCA is still empty- Downtime Activity
 Performing conversion activities in SPRO sequence. New GL is automatically
activated during the GL conversion activity. Configure and perform “Migrate
to New asset accounting” activities- Some are Up-time and some are down
time activities.
 Start the Data Migration Monitor in the sequence provided by SAP. During this
ACDOCA is filled and planned depreciation is performed. During this activity if
 you receive any error you have an option to accept the error and go-ahead
with migration- Downtime Activity
 Set the Migration as Complete. This is very important as it enables financial
postings.
 Perform reconciliations of ECC and HANA balances.

Preparing the Conversion

Activities to be performed when you consider your system is ready to start with
conversion process.

 Implement OSS Notes

 Run pre-check programs provided by OSS Notes to ensure your system is in
good shape to migrate to S/4HANA:
o PRECHECK_UPGRADATION_REPORT
o R_S4_TRANSITION_CHECKS
o RASFIN_MIGR_PRECHECK
o Run consistency checks
 Perform corrections based on the results of the checks in point above.
 Ensure that all held documents are posted (or deleted).
 Take baselines of existing information in order to compare with the
information post-migration to ensure consistency. SAP provide some reports
in Conversion Guide but you will probably want to add more checks.
 Implicates the execution of technical installation using SUM.

S/4HANA Installation

Consists of 2 phases, executed by SUM tool. It refers to the actual installation of the
software, but not the migration of transports and some data migration activities.
This is performed by Basis.

 Uptime: during uptime, the system still is accessible. SAP performs some
activities like checking, installation of some components, some structures
creations. The timing depends on the size of the system.
 Downtime: during this phase the system is not accessible. Software is
installed and some tables are completed (not ACDOCA, which is completed
during Data Migration),

Transports

During this phase, transports with customizing required for S/4HANA and code
adjustments are migrated.

Data migration

Data migration implicates the activities that happen after S/4HANA is installed. Now
you are in a system with S/4HANA and different steps need to happen in order to
migrate Finance Data. Following SPRO path, we can identify the following:
 Partitioning of Universal Journal Entry Line Items Table: This is not an
“executable” program or step for the migration. This is a recommendation of
doing partition of ACDOCA when it is expected to have more than 500 million
records. And it is a MUST, when ACDOCA is expected to have more than 2
billon records. This size can be determine by doing a migration practice with
production size

 Regenerate CDS Views and Field Mapping: Required to re-generate the

compatibility views and data migration views to adapt them to the
configuration performed.

 Analyze Transactional Data: This steps performs a check on FI documents

before starting data migration. This allows to find inconsistent documents on
tables BKPF, BSEG, BSIS, BSID, BSIK, BSAS, BSAD, and BSAK. It does some
checks like “clearing information missing”, “zero balance”, “line items are
consistent”, etc. After executing, there is a step “Display Status of Analyze
Transactional data”, that will show the errors detected, which have to be
corrected before starting migration.

 Start and Monitor Data Migration: This is the actual migration to table
ACDOCA It is a monitor or cockpit that executes several migration programs,
showing the status of completion and errors. In previous versions like 1503 or
1511 FPS0, the programs were separated steps in different points in SPRO.
Then SAP implemented this monitor, which was really an improvement,
making the process easier. Several programs or activities are performed
under this step. See below:

1. GCC Check Consistency of G/L Accounts and Cost Elements: Checks that GL
accounts and cost elements are consistent before Migration.
2. GCM G/L Account and Cost Element Merge: Merges the cost elements into GL
account master data.
3. DAA Default Assignment of Cost Elements: Default assignments in the former
cost element master (CSKB) are transferred to the default account
assignments
4. R20 Reconciliation of Transactional Data: Checks that FI documents are
consistent and ready to be migrated.
5. ENR Enrich Transactional Data: This data enrichment is required due to the
merge of FI and CO documents. The program performs several activities:
i. fills some fields of BSEG with information from BKPF.
ii. fills some fields of COEP with information of COBK and OBJNR.
iii. filling of profit center into CO line items
 iv. filling of company code data into old CO line items
v. Some adjustments to fix asset depreciation.
6. R22 Check enrichment of transactional data: If any error is displayed, it can
has to be corrected.
7. MUJ Data Migration into Unified Journal: The actual migration of line items
into ACDOCA happens in this step. Items from BSEG or FAGFLEXA, COSP,
COSS, ANEX and ANEP are migrated.
8. R23 Check Migration of Journal Entry: shows the results, and if there are
errors, they need to be corrected and migration restarted.
9. M10 Migrate Material Ledger Master Data: Ensures that the material ledger is
activated for all valuation areas.
10.M20 Check Material Ledger master data: Checks results from previous step.
11.M11 Migrate Material Ledger Order History: If material ledger was not active
in any valuation area before S4 conversion, this step ensures that all existing
PO records are converted into the material ledger currencies.
12.M21 Migrate Check ML Production Order and Purchase Order History: Checks
results of previous step.
13.DLT Data Migration into Unified Journal: Aggregate Deltas: This step also
called Migration of Balances, ensures that the ACDOCA table shows the same
total balances as before migration. Before S/4HANA, financial statements
were based on totals records (like table GLT0), now the total is built from
aggregating on the fly ACDOCA. So this step ensures consistency of those
total balances, due to differences that could come from Balance Carry
Forward, Archiving, and Customer specific programs, etc.
14.R24 Check Migration of Balances: Checks the results from previous step and
display errors.
15.AFA Initial Depreciation Calculation: This activity build the initial depreciation
values for Asset Accounting.
16.R25 Check Initial Depreciation Calculation: Checks results from previous step.
 Migrate General Ledger allocations: all G/L allocation cycles that refer to
the FlexGL sum table FAGLFLEXT are changed to refer to the new view
ACDOCT
 Migration of House Banks: Migrates existing House banks to the bank
account master data in the new application Bank Account Management.

Post-Migration activities

In this section we could include different activities, required to complete the

migration to S/4HANA.

 Specific activities that are in SPRO path:

o Complete Migration:
1. Final reconciliation after migration: SAP recommends some
reports to do this migration.
2. Set Migration to “Completed” –> Users can post again.
o Activities after migration:
1. Transfer Application Indexes
2. Fill due dates in FI documents
3. Fill offsetting accounts in FI documents

 Other activities that are not in the SPRO path for Data Migration, but are part
of the S4 implementation, like the enablement of FIORI.
The points above are just and overview and do not include activities related to other
SAP solutions that you could be using. For example:

 Integration with ARIBA or Success Factors: This requires specific activities for
connecting ARIBA with S4.
 Synchronization with Human Capital Management: If you are using HCM, a
synchronization between HCM and S/4HANA is required so HCM master data
is synchronized with employee vendors that now are Business Partners.
 Enablement of Cash Management and Liquidity Planning if required. It has
specific set of steps.