Data Migration To SAP S/4HANA From Staging (2Q2)

Data Migration to SAP S/4HANA from Staging (2Q2) PUBLIC
Purpose Error: Reference source not found 1
Test Script PUBLIC

SAP S/4HANA Cloud - 02-04-21
Data Migration to SAP S/4HANA from Staging (2Q2)
Table of Contents
1 Purpose 3
2 Prerequisites 4
2.1 System Access 4
2.2 Roles 4
2.2.1 Technical Roles 4
2.2.2 Business Roles 5
3 Migration Objects for SAP S/4HANA Cloud 6
4 Additional Manual Configuration 7

4.1 Set Up SAP HANA Database as a Service (DBaaS) Connection 7
4.1.1 Create SAP HANA Service Instance 7
4.1.2 Set Up Communication Arrangement 7
5 Business Conditions 8
6 Preliminary Steps 9
6.1 Add Business Roles to the Data Migration User 9
7 Overview Table 10
8 Test Procedures 11
8.1 Start the SAP S/4HANA Migration Cockpit 11
8.2 Create Migration Project 12
8.3 Fill Staging Tables Using Migration Templates 14
8.4 Fill Staging Tables Using Your Preferred Tools 15
8.5 Prepare and Simulate the Migration 17
8.6 Migrate Data to the Target System 18
8.7 Check Data Migration Status 19
8.8 Validate Imported Data 22
9 Appendix 23
9.1 General Topics and Limitations 23
9.1.1 Unit of Measure Conversion 23
9.1.2 ALE/IDoc Distribution After Data Migration 23
9.2 Financials 23
9.2.1 Document Types for Data Migration 23
9.2.2 Document Date 23
9.2.3 Define Settings for Legacy Data Transfer (FINS_MIG_CTRL_1) 24
9.2.4 Transfer Booking Account 25
9.2.5 Migrate Financial Plan Data 25
9.3 Logistics 26
9.3.1 Advanced Variant Configuration 26
9.4 FAQs 27

1 Purpose
SAP S/4HANA Cloud customers can use the included SAP S/4HANA migration cockpit to migrate data. If the customer chooses to use the Migrate Data Using Staging Tables approach, the SAP
S/4HANA migration cockpit creates staging tables for the migration objects that are relevant for your project and migrates data from these staging tables to the target SAP S/4HANA Cloud system.
If you use the Local SAP S/4HANA Database Schema option, the SAP S/4HANA migration cockpit generates the staging tables in the local ABAP schema of the SAP S/4HANA Cloud system. We
recommend using this option if you want to populate the staging tables using the XML template files provided by SAP.
If you use the Remote SAP HANA Database Schema option, you specify the relevant connection to a remote SAP HANA system. The SAP S/4HANA migration cockpit generates the staging tables
there.
Note The scope item covers some technical prerequisites. Please note that additional costs may apply. For the successful communication configuration between SAP HANA Service Instance and
SAP S/4HANA Migration Cockpit, you need to have set up an SAP HANA Database as a Service (DBaaS) on the SAP Business Technology Platform (BTP). After activation, you need to set up the
communication arrangement SAP_COM_0259.
Note SAP S/4HANA refers to the default on-premise suite on the SAP HANA platform, SAP S/4HANA Cloud refers to our cloud suite on SAP Business Technology Platform.
This document provides a detailed procedure for testing this scope item after solution activation, reflecting the predefined scope of the solution. Each process step, report, or item is covered in its
own section, providing the system interactions (test steps) in a table view. Steps that are not in scope of the process but are needed for testing are marked accordingly. Project-specific steps must be
added.
Values in this test script (decimal notation, date formats, and so on) are presented in U.S. standard notation. If your test system is set up to use a different notation, enter values as appropriate.
Data protection legislation may require that personal data is deleted once the data has served its originally defined purpose and is also no longer subject to additional legal data retention
requirements. If data protection legislation is applicable in your case, then migrating personal data that should have been deleted could be interpreted as the processing of personal data without any
legally justified purpose.
Migration objects are built for initial migration of your data to your SAP S/4HANA or SAP S/4HANA Cloud system. This means that you can create data with a migration object, but you can't
change or update existing data with it.
For some migration objects there are "Extend" migration objects available, that you can use to extend existing data to other organizational levels. If you want to change or update existing data, use
the respective maintenance apps (available for all business objects) or mass processing apps (these are only available for selected business objects). Please note that such apps fall outwith the
responsibility of data migration development.
To get the latest information on SAP S/4HANA Migration Cockpit, also check SAP Note 2538700 - Collective SAP Note and FAQ for SAP S/4HANA Migration Cockpit - File/Staging (Cloud /
SAPSCORE)

2 Prerequisites
This section summarizes all the prerequisites for conducting the test in terms of systems, users, master data, organizational data, other test data and business conditions.
2.1 System Access
System Details
System Accessible via SAP Fiori launchpad. Your system administrator provides you with the URL to access the various apps assigned to your role.
SAP Business In case you're using the Remote SAP HANA Database Schema, you have to create an SAP HANA Service Instance on SAP Business Technology Platform with your
Technology Global account for SAP Business Technology Platform. The SAP HANA Service Instance is needed to create the staging tables used by the migration cockpit. See the Set-
Platform up instructions on SAP Best Practices Explorer for more information about how to create a SAP HANA Service Instance on SAP Business Technology Platform.
2.2 Roles
2.2.1 Technical Roles

Required Standard Roles
Use the following standard role to access the Migrate Your Data - Migration Cockpit (F3473), Data Migration Status (F3280), and Define Settings for Legacy Data Transfer
(FINS_MIG_CTRL_1) apps:
ID (Role Template) Name (Role Template) ID (Space) Name (Space)

SAP_BR_CONFIG_EXPERT_DATA_MIG Configuration Expert - Data Migration SAP_BR_CONFIG_EXPERT_DATA Configuration - Data
_MIG Migration
Only required if Remote SAP HANA Database Schema is used: Configuration Expert - Business Network
SAP_BR_CONF_EXPERT_BUS_NET_INT Integration

Additionally, the corresponding role for each migration object is also required. For example, the Cash Manager (SAP_BR_CASH_MANAGER) role for the Bank migration object.
Key Mapping
Use the following standard role to access the Search Key Mapping (MDG_BS_WD_ANALYSE_IDM) and Manage Key Mapping (MDG_BS_WD_ID_MATCH_SERVICE) apps. You can use these
apps to check the key mappings that were entered in the Unified Key Mapping Service (UKMS) during the data load. Currently, UKMS supports the following migration objects:
● Customer
● Supplier
● FI-CA - Contract partner
● FI-CA - Contract account
● Material (deprecated)
● Product
ID (Role Template) Name (Role Template) ID (Space) Name (Space)

SAP_BR_ADMINISTRATOR_DATA_RE Administrator - Data Replication SAP_BR_ADMINISTRATOR_DATA_RE Administration - Data Replication
PL PL
2.2.2 Business Roles

You can find an extensive table listing all migration objects available for SAP S/4HANA Cloud, as well as the required business roles, in the SAP S/4HANA Cloud product assistance.

3 Migration Objects for SAP S/4HANA Cloud
You can find an extensive table listing all migration objects available for SAP S/4HANA Cloud, together with their respective migration object documentation, in the SAP S/4HANA Cloud product
assistance or via the short link https://help.sap.com/S4_CE_MO.
The data migration object documentation was moved to the SAP Help Portal with SAP S/4HANA Cloud 1905. If you encounter issues opening the documentation from the Migration Cockpit, refer
to SAP Note 2667053 and SAP Knowledge Base Article 2793425.

4 Additional Manual Configuration
The additional manual configuration that is described here is only necessary if you are using the "Remote SAP HANA Database Schema" option. If your are using the “Local SAP S/4HANA
Database Schema” option, you can skip this section.
Before you can test this scope item, you must have completed the additional configuration steps that are described in the Set-Up Instructions for this scope item. These configuration steps are specific
for your implementation and include mandatory settings that are not delivered by SAP and must be created by you. For more information, refer to the Set-Up Instructions for this scope item on SAP
Best Practices Explorer (https://rapid.sap.com/bp/#/browse/scopeitems/<enter the scope item ID>).
4.1 Set Up SAP HANA Database as a Service (DBaaS) Connection

To use the transfer option staging tables of the SAP S/4HANA migration cockpit, you first have to set up the SAP HANA Database as a Service (DBaaS) connection in order to create the staging
tables on SAP Business Technology Platform and set up the communication arrangement to allow the migration cockpit to communicate with these tables.
4.1.1 Create SAP HANA Service Instance

More information about setting up the SAP HANA Service Instance can be found here.
A video tutorial can be found here.
4.1.2 Set Up Communication Arrangement

This link will refer you to the Set-Up Instructions on SAP Best Practices Explorer.

5 Business Conditions
If you are using the Remote SAP HANA Database Schema option, the following business conditions have to be met, before this scope item can be tested.
Business Condition
Business Condition
With the Remote SAP HANA Database Schema:
● Acquire SAP Business Technology Platform user and password
● SAP HANA DBaaS instance is set up in SAP Business Technology Platform
● Communication arrangement to DBaaS is created
Content is activated
Org. structures and additional settings are made.

6 Preliminary Steps
Use
In these steps, you set up the necessary user settings for migrating your data.
6.1 Add Business Roles to the Data Migration User

Use
In this step, you assign the roles, which are necessary for migrating your data, to the data migration user. You can find a list of business roles per migration object here.
Procedure
1. Access the SAP Fiori screen in SAP S/4HANA Cloud.
1. On the Home screen, choose the Maintain Business Users (F1303) tile:
2. Enter the User Name given by your system administrator.
Field Name Description User Action and Values

User Name Name of the Data Migration user User name
3. Choose Go.
4. Select the user in the Users list.
5. Choose Edit.
6. Choose Add Business Roles.
7. In the Add Business Roles list, enter the needed business role into the Search field and press Enter.
8. Select the needed business roles and choose OK.
9. Choose Save.
10. Go back to the Home screen.
11. Go back to the previous screen.
Result
You have added the necessary roles for the specific data migration object to load.

7 Overview Table
This scope item consists of several process steps provided in the table below.
Process Step UI Type Business Condition Expected Results

Start the SAP S/4HANA Migration Cockpit This section describes how you start the SAP S/4HANA migration The migration cockpit is displayed.
Migration Cockpit [page ] cockpit.
11
Create Migration Project Migration Cockpit This section describes how you create a migration project in the A migration project is created.
[page ] 12 migration cockpit.
Fill Staging Tables Using Migration cockpit This section describes how you fill staging tables. The staging table is opened and new data is entered.
Your Preferred Tools [page ] (Web Dynpro)
15
Prepare and Simulate the Migration Cockpit This section describes the steps necessary to prepare for the final The data is ready to be migrated to the target system.
Migration [page ] 17 migration.
Migrate Data to the Target Migration Cockpit This section describes how you import your data into the target system. The data is transferred from the staging table to the target
System [page ] 18 system.
Check Data Migration Status Data Migration This section describes how you use the Data Migration Status (F3280) You are up-to-date with the status of your migration projects
[page ] 19 Status app app to check the status of your migration projects and objects. and objects. Necessary changes in migration projects can then
be made.
Validate Imported Data SAP Fiori launchpad This section describes how you validate completeness and correctness All data from the staging table can be found in the
[page ] 21 of the migrated data in the target system using corresponding business corresponding business functions.
functions.

8 Test Procedures
This section describes test procedures for each process step that belongs to this scope item.
8.1 Start the SAP S/4HANA Migration Cockpit
Test Administration
Customer project: Fill in the project-specific parts.
Test Case ID <X.XX> Tester Name Testing Date Enter a test date.
Business Role(s)
Responsibility <State the Service Provider, Customer or Joint Service Provider and Customer> Duration Enter a duration.
Use
This section describes how you start the SAP S/4HANA Migration Cockpit.
Procedure
Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment
1 Start SAP Fiori launchpad Log on to your SAP S/4HANA Cloud system. The Home page appears.
2 Open Migration Cockpit Choose the Migrate Your Data - Migration Cockpit (F3473) tile.
Note For more information on the SAP S/4HANA Migration Cockpit in SAP S/4HANA Cloud, see the product assistance on the SAP Help Portal.

Result
The Migrate Your Data home screen appears.
8.2 Create Migration Project
Test Administration
Business Role(s)
Use
This section describes how you create a migration project in the migration cockpit.
Procedure
Test Test Step Name Instruction Expected Result Pass / Fail /

Step # Comment
1. Create Migration Choose Create on the Migration Projects home screen. The New Migration
Project Project dialog window
appears.
2. Choose Settings Make the required entry in the New Migration Project dialog window:
for Migration ● Name:
Project
Name of your migration project.

● Mass Transfer ID:
See note below this table.
● Database Connection:
• If you want to use staging tables that are located in the local ABAP schema, choose the option Local SAP
S/4HANA Database Schema.
• If you want to use files to fill the staging tables with data, choose the option Local SAP S/4HANA
Database Schema. The system generates the staging tables in the internal schema of the SAP S/4HANA
system.
• If you want to use staging tables that are located in an SAP HANA schema that isn’t the local ABAP
schema of your system, select the option Remote SAP HANA Database Schema and enter a valid database
connection to the staging system or choose one from the search help list.
See the product assistance for further information.
After making the required entries, choose Step 2.
3. Choose Migration Choose all relevant migration objects for your project. Then, choose the arrow to add them to the Selected Migration
Objects Object table on the right-hand side. When you’ve finished your selection, choose Review.
4. Add Dependent The system checks for dependent object and might ask you whether you want to add additional migration objects to An overview page
Objects (optional) your project. For more details, choose View Details. with your project
Choose Add or Do Not Add as required. settings is displayed.
5. Create Migration Double-check your project settings and choose Create Project.
Project
After an SAP S/4HANA Cloud release upgrade, any new migration objects won’t get added to existing migration projects. To be able to use new migration objects, you need to create a new
migration project. If there are still migration objects missing after creating a new migration project, please see SAP Note 2538700 for further information.
Further Information
Find further information about project settings in the product assistance on the SAP Help Portal.

8.3 Fill Staging Tables Using Migration Templates
Test Administration
Business Role(s)
Use
This section describes how you transfer your data from the migration template to staging tables.
Procedure
Test Test Step Instruction Expected Pass / Fail /

Step # Name Result Comment
1. Upload On the Migration Project screen, select the relevant migration object and choose the action Upload File.
File The system displays the Migration Object Tables screen. On the Files tab, you upload the files and view the status of the validation and
transfer process. To upload a file, you can either choose Upload or use the drag and drop function.
The system uploads the file to the SAP S/4HANA migration cockpit. On the Files tab, you can view the status of the upload.
2. Validate The system validates the data in the file. On the Files tab, you can view the status of the validation as well as information such as the
Data time the process was started.
Find more information about issue handling and validation in the product assistance.
3. Transfer Once the file has been validated successfully, the system automatically starts transferring the data in the file to the staging tables that
Data were generated for that migration object. Once all the data in the file has been transferred to the staging tables, the system displays the
information Data Successfully Transferred to Staging Tables. You can also view information such as the number of transferred
migration object instances.

8.4 Fill Staging Tables Using Your Preferred Tools
Test Administration
Business Role(s)
Use
You can fill the staging tables manually or by using your preferred tools (for example SAP Data Services or SAP Smart Data Integration, SDI).
Procedure
Test Test Step Instruction Expected Result Pass / Fail /

Step # Name Comment
1 Fill Staging Fill the staging tables manually or by using your preferred tools The staging table
Tables Note Make sure the key fields, the mandatory fields and fields' default initial values contain valid data. contains the data.
More information can be found in SAP Note 2733253 – FAQ for SAP S/4HANA migration cockpit. Migration
approach: Transfer / Migrate data from staging tables, and in SAP Community Blogs, for example, here.

Additional Information
● Filling staging tables... Using a secondary database connection Using the same SAP S/4HANA scheme
"Remote SAP HANA Database" "Local SAP HANA Database"
In SAP S/4HANA Cloud SAP Business Technology Platform/DBaaS Only via XML template
Via openSQL, third party ETL Tools or from SAP like SAPHANA Studio, SDI, ADP, SAP Data Services
● Sometimes it's necessary to synchronize staging tables with migration objects. Reasons for that could be changed default views of the migration project, changed active views of the migration
object, or changed migration object content. The staging tables that must be changed have the status Synchronization Required. You must synchronize these tables before you can use them for
data transfer.
• To synchronize all the staging tables of a migration object, choose Start Synchronization on the Migration Object Details screen.
• To synchronize a single staging table, choose Start Synchronization on the Staging Table Details screen of the table.
● To show the documentation of the staging table go to the staging table details screen and choose Show. A window appears that shows information about Field Name, Group, and Description, as
well as which field is Key and which field is Mandatory.
● If you fill the SAP HANA staging tables with values, be aware of the following datatypes and the rules:
• Date fields might be shown in SAP HANA as NVARCHAR length 8 with DEFAULT 00000000. The format of the value is YYYYMMDD, so 2018-DEC-31 must be entered 20181231.
Initial values must be set to the defined DEFAULT value.
• Time fields might be shown in SAP HANA as NVARCHAR length 6 with DEFAULT 000000. The format of the value is HHMMSS, so 2:34:12 pm/14:34:12 must be entered 143412.
Initial values must be set to the defined DEFAULT value.
• Numerical character fields of ABAP data type NUMC must contain leading zeros. You can determine such fields as they are NVARCHAR with a default value with one zero minimum.
So NVARCHAR (3) with DEFAULT 000 is a NUMC field with length 3. The value 90, for example, must be entered as 090, the value 0 as 000. You can cross-check this when you
download the template for this object in a project with transfer option Transfer Data from File. The field is shown in the field list of the template as number with length 3 and 0 decimals.
• Decimal values must have a '.' as decimal separator.
Find more information on this in SAP Note 2733253 – FAQ for SAP S/4HANA migration cockpit - Transfer option: Transfer data from staging tables.
Result
The system created the staging tables automatically, and you entered new data using your preferred tools.

8.5 Prepare and Simulate the Migration
Test Administration
Business Role(s)
Use
Before migrating your data to the productive system, you need to conduct a couple of preparational steps.
Procedure
Test Test Step Name Instruction Expected Pass / Fail /

Step # Result Comment
1. Prepare the On the Migration Project screen, select the relevant migration object.
Staging Tables In the Action column, choose Prepare.
The system will prepare the staging tables so that they can be used to transfer your data.
2. Complete You need to process any open mapping tasks for the migration object before you can proceed with the simulation or the
Mapping of Data migration.
On the Migration Project screen, in the Mapping Tasks column, you can view the number of open and completed tasks for
each migration object.
Find more information about mapping tasks in the product assistance.
3. Simulate the Once you have processed all open tasks for a migration object and prepared the staging tables, you can simulate the
Migration transfer of data
On the Migration Project screen, select the relevant migration object and choose Actions and then Simulate. The system
simulates the migration for all migration object instances in the staging tables for the migration object.
8.6 Migrate Data to the Target System
Test Administration
Business Role(s)
Use
This section describes how you migrate your data into your target system.
Procedure
Test Step Test Step Instruction Expected Pass / Fail /

# Name Result Comment
1. Migrate Data On the Migration Project screen, select the relevant migration object and choose the action Migrate. The system will migrate
all migration object instances in the staging tables for the migration object.
Result
The data is transferred from the staging table to the target system.

8.7 Check Data Migration Status
Test Administration
Business Role(s)
Use
This section describes how you use the Data Migration Status (F3280) app to check the status of your migration projects and objects.
Prerequisite
You've started migrating data to your SAP S/4HANA system for at least one migration object.
Procedure
Test Test Step Instruction Expected Result Pass /

Step # Name Fail /
Commen
t
1 Open Data Choose the Data Migration Status (F3280) app. The Data Migration Status page appears. Here you can see an overview
Migration of all migration objects that you've started using so far. The table shows
Status app the total number of records, the number of imported records, the number
of records that are ready for import, and the number of failed records. In
the right column you find a progress bar on the status of your objects.

2 Optional: You can apply filters on the overview table to find the object you're looking The table is filtered according to your requirements.
Apply for faster. Therefore, choose Expand Header and the filter header expands.
Filters You can use the first field for free text search, or you can use the Migration
Period, Migration Project, Object Name, and Record Status fields for your
query. After you've entered the desired values, choose Go.
3 Drill Down For more information on a migration object, just choose the name of the A pane opens on the right side. In the first table in this pane, you find an
on a respective object. overview of all Records of this migration object. This table shows the
Migration Source ID, Status, Description, Project, and Audit Status. In the second
Object table in this pane, you find an overview of all Messages of this migration
object. This table shows all Message Types, Messages, and the Number
of messages.
4 Optional: You can apply filters on both the Records and the Messages table to find the The table is filtered according to your requirements.
Apply record or message you're looking for faster. For the Records table, you can use
Filters the field for free text search on the right side, or you can use the dropdown list
on the left side to filter for the Status or the Audit Status of the records. For
the Messages table, you can use the message type options – Error and
Warning – to filter for the Message Type.
5 Drill Down For more information on a record or a message, just choose the name of the A pane opens on the right side. In this pane, you find detailed
on a Record respective object. information on the record or the message.
or a
Message
6 Close all You can close every pane by choosing the close symbol in the upper right The panes are closed and you're back on the Data Migration Status page.
Panes corner of the pane.
Result
You are up-to-date with the status of your migration projects and objects, and you can make the necessary changes in your migration projects.
Further Information
Make sure you read the SAP S/4HANA Cloud product assistance. There, you can find detailed information on the features of the Data Migration Status app, for example how to use the audit
function, how to set up notifications, and lots more.
You can find frequently asked questions relating to the Data Migration Status app in the SAP Note 2615787.

8.8 Validate Imported Data
Test Administration
Business Role(s)
Use
This section describes how you validate completeness and correctness of the migrated data in the target system using corresponding business functions.
Procedure
Test Step Test Step Name Instruction Expected Result Pass / Fail /
# Comment
1 Access the Open the corresponding app of the SAP S/4HANA Cloud system and All migrated data is displayed in the corresponding
Corresponding App check completeness of the imported data. SAP S/4HANA Cloud app.
Note Check the migration object documentation for the name of the required app and the corresponding business role, or for the required backend transaction to validate the data in the system.
Result
All migrated data can be found in the corresponding business functions.

9 Appendix
9.1 General Topics and Limitations
9.1.1 Unit of Measure Conversion

Find detailed information in SAP Knowledge Base Article 2907822.
9.1.2 ALE/IDoc Distribution After Data Migration

If you want to distribute data from your SAP S/4HANA or SAP S/4HANA Cloud system to other systems via Application Link Enabling (ALE), carefully read SAP Knowledge Base Article
2858316 before you start migrating the data using the migration cockpit.
9.2 Financials
9.2.1 Document Types for Data Migration

The document type for all open item and open balance migration objects can be freely chosen and entered into the Document Type field.
For migration of general ledger balances, we recommend the document type UE, and for open item migration objects, we recommend the document types DR (Customer Invoice) and KR (Vendor
Invoice), respectively.
9.2.2 Document Date

The document date must be the same date as in the original data record.

9.2.3 Define Settings for Legacy Data Transfer (FINS_MIG_CTRL_1)
Migration Key Date/Posting Date for Financial Documents
Before you go live with SAP S/4HANA, you may want to do an initial transfer of open balances and open items from a legacy system to your SAP S/4HANA system. You transfer such data using
the SAP S/4HANA Migration Cockpit.
To enable the cockpit to transfer your legacy financial transactional data properly, use the Define Settings for Legacy Data Transfer (FINS_MIG_CTRL_1) app to maintain the migration key date
on which you want to complete all preparatory activities for each company code before the actual data transfer.
The migration key date must allow for you to complete the following actions:
● Complete all postings available up to this date, in full, in the source system
● Reconcile and close the journals in the source system for the period
● Extract source data and enter it into the migration templates
● Clean and convert data as needed
● Validate the imported data against your legacy system
The date chosen is usually the end of a period (month, quarter, year) since this will fit in with the normal reconciliation cycle.
Please note that the migration key date is also used as the posting date when the legacy data is actually transferred to your SAP S/4HANA system.
Set the Legacy Data Transfer Status for each migration key date provided:
● In Preparation: migration key date is still unclear (migration of transactional data is not possible)
● Ongoing: required for the initial data transfer (migration of transactional data is possible)
● Completed: after successful completion of the initial data transfer (migration of transactional data is not possible)
For the following financial objects, the posting date will be automatically derived by the predefined migration key date for the related company code which is maintained via the aforementioned app:
● FI - Accounts payable open item
● FI - Accounts receivable open item
● FI - G/L account balance and open/line item
● Material inventory balance
● FI - Historical balance (migration key date is required to allow the migration of historical balances only up until this initial transfer date)
Exception
● For the financial object FI-CA - Open item, a field for posting date is available on the migration template. The posting date is marked as mandatory on the template and must be provided for each
data record. The migration key date has no additional effect on the provided posting date.

● For the financial object Fixed asset - Master data, use the Make Company Code Settings - Asset Accounting-Specific (FAA_CMP) app to specify the data transfer date, document type, and the
legacy data transfer status.
See also General Ledger Accounting > Current Settings in the SAP S/4HANA Cloud product assistance for further information on the configuration of the Migration Key Date before migrating
transactional data.
9.2.4 Transfer Booking Account

The transfer booking accounts to be used for the Open item and Open balance migration objects are as follows:
Account Description Migration Cockpit Object Name

39911000 Initial Entry of Raw Material Balances Material inventory balance
39912000 Initial Entry SF & Finish Gds Balances Material inventory balance
39913000 Initial FI-AM offset Fixed asset - Postings
39914000 Initial FI-AR offset FI - Accounts receivable open item
39915000 Initial FI-AP offset FI - Accounts payable open item
39916000 Initial other G/L offset FI - G/L account balance and open/line item
39917000 Initial other Open Item G/L offset FI - G/L account balance and open/line item
9.2.5 Migrate Financial Plan Data

If you have financial plan data in your legacy system that you want to import to your SAP S/4HANA system, you may do so by using the Import Financial Plan Data (F1711)
This app is available to users with the following business roles:
● SAP_BR_OVERHEAD_ACCOUNTANT
● SAP_BR_SALES_ACCOUNTANT
● SAP_BR_PROJ_FIN_CONTROLLER
By using this app, you can import periodic financial plan data for the following planning areas:
● Cost Centers
● Projects
● Profit Centers
● Market Segments
● P&L
● Balance Sheet
● Functional Areas
For further information on this app, check the SAP Fiori apps reference library and refer to the online help.
9.3 Logistics
9.3.1 Advanced Variant Configuration

To create objects of a configuration model, create the objects in the following order:
# Object Name Comments

1 ECM - Change master If you want to use a change number, create a new change number first.
2 Document info record
3 Characteristic Dependencies must be added manually.
4 Class
5 VC - Variant table structure
6 VC - Variant table entry
7 VC - Object dependencies Only for global dependencies. Create object dependencies with status Released. In case of a syntax error in the dependency the creation of this
dependency will be prevented.
8 Product
9 Object classification - General
template
10 VC - Constraint
11 VC - Dependency net
12 VC - Configuration profile
13 Material BOM
Note Migration of local dependencies is currently not supported for all objects. Please read the migration object documentation carefully to determine which objects support this.

9.4 FAQs
For frequently asked questions regarding migrating data using the SAP S/4HANA Migration Cockpit, see SAP Knowledge Base Article 2733253.

Typographic Conventions
Type Style Description

Example 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.
Example Emphasized words or expressions. www.sap.com/contactsap
EXAMPLE 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.
Example 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.
Example Exact user entry. These are words or characters that you enter in the system exactly as they appear in the
documentation.
<Example> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to
make entries in the system.
EXAMPLE Keys on the keyboard, for example, F 2 or E N T E R .
© 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.
SAP and other SAP products and services mentioned herein as well as their
Data Migration to SAP S/4HANA from Staging (2Q2) respective logos are trademarks or registered trademarksPUBLIC
of SAP SE (or an
Purpose Error:and
SAP affiliate company) in Germany Reference source not
other countries. Allfound
other product 27
and service names mentioned are the trademarks of their respective
companies.
See www.sap.com/copyright for additional trademark information and

notices.

Data Migration To SAP S/4HANA From Staging (2Q2)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Data Migration To SAP S/4HANA From Staging (2Q2)

Uploaded by

Copyright:

Available Formats

Data Migration to SAP S/4HANA from Staging (2Q2) PUBLIC

Purpose Error: Reference source not found 1

Test Script PUBLIC