SAP S/4HANA Data Migration Content Development

PUBLIC

SAP S/4HANA Data Migration Content Development, SAP

February, 2020

SAP S/4HANA Data Migration Content DevelopmentNewsletter 2002 V1.0

NOTE: Delete th yellow stickers when finished.

See the SAP Image Library for other available images.

https://www.sapbrandtools.com/imagelibrary/index.html#/

2PUBLIC© 2020 SAP SE or an SAP affiliate company. All rights reserved. ǀ

This document may mention releases of SAP software that are not yet available.

SAP reserves the right to change the scope and the extent of the software to be delivered.

Bear in mind the information about undelivered software releases contained here are subject to change.


Agenda

SAP S/4HANA Cloud News


KBA 2698032 content available on SAP Help Portal:

• SAP S/4HANA Migration Cockpit: Deprecated

Migration Objects

KBA 2726010 content available on SAP Help Portal:

• SAP S/4HANA Migration Cockpit: Support of

Custom Fields

New Content on SAP Help Portal Features Data Migration (Visibility: Customer/Partner)

https://help.sap.com/viewer/cfa2662411a2477091dba17cb733aa41/SHIP/en-US/

https://help.sap.com/viewer/70cd8175333c4d1b9ae3a08fbab81397/SHIP/en-US/2e958fddffe642b8b293a22d100cab37.html

https://launchpad.support.sap.com/#/notes/2698032

https://help.sap.com/viewer/cfa2662411a2477091dba17cb733aa41/SHIP/en-US/




SAP S/4HANA Cloud Data Migration Objects - 135 Objects in 2002


• 35% more objects since 1902

release

• 80% more objects since 1802

release

• 694% more objects than 1511

release

Release 2002 Is Based on 135 Migration Objects


• EHS - Location

• EHS - Location hierarchy

• Product hierarchy

• Product hierarchy assignment

• QM - Inspection plan (New Version 2)

5 New Data Migration Objects in 2002 (Release Comparison)

https://help.sap.com/viewer/25d2ae41d2d74803be976f9c4bda6986/SHIP/en-US/a7f8e5dc36a140f28c29bcbadb0c715b.html



Renamed Data Migration Objects in 2002 (Release Comparison)

Old Name New Name Reason

QM – Inspection plan QM – Inspection plan

(deprecated)

Deprecation phase started, object

replaced by new object

https://help.sap.com/viewer/25d2ae41d2d74803be976f9c4bda6986/SHIP/en-US/aa139b168c444e7e9de7aff91c9c8c29.html


• QM – Inspection plan (deprecated)• Deprecated with 2002

• Will be removed with 2008

• Use new 2002 migration object QM – Inspection plan

Replaced Data Migration Objects in 2002

https://help.sap.com/viewer/636b00275e9c470780b40b7f5a504858/latest/en-US/946fa5ed531c46dc83c5cbbcb0aecea0.html


• Small change in design and

document structure

• Reordered releases to have

latest release on top of the list

• Includes 2002 changes

• Missing 1911 changes added for

object Supplier

SAP S/4HANA Cloud - Release Comparison of Migration Object Templates

https://help.sap.com/viewer/25d2ae41d2d74803be976f9c4bda6986/SHIP/en-US



Changes since last 1911 Newsletter

• Files updated to 2002 release

templates

• New sample data for the objects:

• Fixed asset - Master data

• Fixed asset - Postings

Data Migration Template Samples

https://help.sap.com/viewer/d5aa3caabab04bb68d9cc3352d003330/SHIP/en-US/0df3c7429fa846d2adc47e92a92ce745.html

https://help.sap.com/viewer/d5aa3caabab04bb68d9cc3352d003330/SHIP/en-US/0df3c7429fa846d2adc47e92a92ce745.html


• Direct link

• Updated to 2002 release

• Screen layout changes within:

• SAP_LAND_INTANGIBLES

• SAP_BUILDINGS

• SAP_MACHINERY_EQUIPM

• SAP_VEHICLES

• SAP_COMPUTERS

• SAP_LVA

• SAP_TAXONLY_GOODWILL

• SAP_DEFAULT

• SAP_AUC

2468501 – SAP S/4HANA Cloud –

Available Fields per Asset Class

https://help.sap.com/viewer/bc49894809864d03938df91a17ea28b7/


https://help.sap.com/viewer/bc49894809864d03938df91a17ea28b7/

SAP S/4HANA (on premise) News


This part of the document may mention releases of SAP software that are not yet available.




#4 2755475

Central Collection

Valid for 1709 SPS3

Issues are fixed with SPS4

#2 2672778Customer, Supplier - Data Definition of Sender Fields

Valid for 1709 SPS2Issues are fixed with SPS3

#3 2709468 Customer Extend: Error

message "UoM: Additional customizing required for ISO

code"

Valid for 1709 SPS2Issues are fixed with SPS3

#1 2642266

Equipment: System Runtime

Error

Valid for 1709 SPS2


Transport Based Correction Instructions (TCI) Used to Fix Known Issues in

SAP S/4HANA 1709

SIF_BANK_MASTER 2756499

SIF_FIXED_ASSET 2701197


MAP_KULA 2644750

SIF_CUST_EXTEND 2699116

Always check your current Service Pack level and import all relevant TCIs in the correct order











#3 2792960

Customer / Supplier - Warning

Message DMC_RT_MSG 622

Valid for 1809 FPS0 – FPS2


#2 2793418

JULY 2019 Collection



#1 2755460

MAY 2019 Collection


Issues are fixed with FPS2


SAP S/4HANA 1809 (I)

SIF_GL_ACCOUNT 2742252

MAP_TPLNR 2631870


SIF_BANK_MASTER 2756499


SIF_EQUIPMENT 2781450


SIF_CUSTOMER_2 /

SIF_VENDOR_2

2792960

SIF_MAINT_ITEM 2788950

SIF_MATERIAL 2793305

SIF_CUSTOMER_2 /

SIF_VENDOR_2

2792960

















#6 2871680

DECEMBER 2019 Collection

Valid for 1809 SPS3


#5 2832244

AUGUST 2019 Collection



#4 2809177

Sales Order: Fix - Multiple

Conditions




SAP S/4HANA 1809 (II)


MAP_TPLNR 2631870

SIF_OPEN_ITEM_AP

SIF_OPEN_ITEM_AR

2832778

SIF_CUSTOMER_2

SIF_VENDOR_2

2833190

SIF_CON_CONTRACT 2833233

SIF_SALES_ORDER 2809177


SIF_GENMT_TL 2867146

SIF_CHARACT 2870257













#2 2869983

DECEMBER 2019 Collection

Valid for 1909 FPS0


#1 2860042

NOVEMBER 2019 Collection

Valid for 1909 FPS0



SAP S/4HANA 1909

SIF_GENMT_TL 2867146

SIF_CONSENT 2867634

SIF_CHARACT 2870257

SIF_BOM 2858427

SIF_CUSTOMER_2

SIF_VENDOR_2

SIF_CUST_EXT_2

SIF_VEND_EXT_2

SIF_CUST_UKM

2854777










• You have migrated your G/L accounts

initially using the migration cockpit.

• Now you want to extend your G/L

accounts to an additional company code.

• You get the error message “Account xxx

has been already created in chart of

account yyy" .

See KBA 2855919 for the solution

2855919 - SAP S/4HANA Migration Cockpit: G/L Account: Existing G/L

Accounts cannot be extended





• After upgrading to 1909 you get a syntax

error in already existing Migration objects

• You need to manually add an INCLUDE

into the Target Structures definition of

your object

See KBA 2883014 for the solution

2883014 - SAP S/4HANA Migration Cockpit: An Error message “Field

LO_TIMER is unknown” in migration content after upgrading to SAP

S/4HANA 1909 On-Premise




KBAs, SAP Notes, Help Portal pages you

should know


2872245 - Setting the legacy transfer

date in app Make Company Code

settings gives error FAA_CMP078

2858021 - FAQ – Fiscal Year Change

in Asset Accounting

New KBAs Around Fixed Assets - Data Migration






Migration Objects Support Custom Fields in 2002 (I)

Migration Object

Available w/

Cloud

Release

Available w/

On-Premise

Release Supported Business Context

Commercial project 1811 1909 •Engagement Project

•Work Package

Customer 1902

1905

1909 •Business Partner Core View

•Customer Core View

•Customer Company Code Core (1905)

•Customer Sales Area Core View (1905)

Customer - extend existing record by new org levels 1905 1909 •Customer Company Code Core (1905)

•Customer Sales Area Core (1905)

Supplier 1902

1905

1909 •Business Partner Core View

•Supplier Core View

•Supplier Company Code Core (1905)

•Supplier Purchasing Org Core (1905)

Supplier - extend existing record by new org levels 1905 1909 •Supplier Company Code Core (1905)

•Supplier Purchasing Org Core (1905)

FI-CA Contract partner 1902 1909 •Business Partner Core View

Enterprise project 1908 n/a •Project Header

•Project Element



Migration Objects Support Custom Fields in 2002 (II)

Migration Object

Available w/ Cloud

Release

Available w/ On-

Premise Release Supported Business Context

FI – G/L account balance and open/line item

FI – Accounts payable open item

FI – Accounts receivable open item

1908 1909 •Accounting: Journal Entry Item

•Accounting: Coding Block

•Accounting: Market Segment (CO-PA)

FI-CA Provider contract 1908 n/a •Contract Accounting Provider Contract Item

PSM - Fund 1908 1909 •PSM Funds Management Fund

Product 1911 ~2020 •Master Data: Product General

•Master Data: Product Plant

•Master Data: Product Distribution Chains

•Master Data: Product Storage Location

•Master Data: Product Dimensions

•Master Data: Product Valuation

Fixed asset - Master data 1911 ~2020 •Fixed Asset Master Data

FI-CA Contract Account 1911 n/a •Contract Accounting: Contract Account Partner

Relationship

FI-CA Open item 1911 n/a •Contract Accounting Document: Business Partner

Item

Service contract

Service order

2002 ~2020 •Service Header

•Service Item



In addition to SAP S/4HANA Migration Cockpit

Product Assistance, new KBA is created to

provide more details

2878945 - Migration Cockpit: Parallelization of XML file loads


https://help.sap.com/viewer/9961ea9091534d44a01ab44024b174d9/latest/en-US/2a685103e1c240f588c936b50ce97927.html



SAP S/4HANA Cloud migration cockpit -

Available fields per asset class for fixed asset

data migration: AY 219: Field.... is not ready for

input

Is now Knowledge Base Article 2883430

Higher visibility and easier to find

SAP Note 2468501 transferred to KBA 2883430





• New Collective KBAs per Migration

Object

• 2878950 – Equipment

2538700 – Collective SAP Note and FAQ for SAP S/4HANA Migration Cockpit

(Cloud)





• New collective KBAs per migration

object

• 2878950 – Equipment

• New TCIs for 1709 / 1809 / 1909 added

2537549 – Collective SAP Note and FAQ for SAP S/4HANA Migration Cockpit

(on premise)




Tips & Tricks

Blogs

Data Migration – Status App


Extended Statistics in Data Migration Status App

@SAP S/4HANA Cloud Customer Community

Data Migration - Status Monitoring


Available Blogs on Data Migration – Status App

https://s4hanacloud.community.sap/blogs/show/LITnSQzs8AgmXz3RpQCCBH

https://s4hanacloud.community.sap/blogs/show/K3mr0veXGcRwX5OCdexgaC

https://s4hanacloud.community.sap/blogs/show/LITnSQzs8AgmXz3RpQCCBH

https://s4hanacloud.community.sap/blogs/show/K3mr0veXGcRwX5OCdexgaC

Blog

Business Partner Number Range Buffer


• Number range object “BU_PARTNER” has

buffering enabled

• Numbers being loaded into buffer is 10

• If you leave the session without using up all

of the numbers which have been loaded into

the buffer or when different users/sessions

try to create BP at the same time, then you

might see gaps in the number range

For details see:


Number Range Buffer - Why We Sometimes See Skips in the Number Range

for Business Partners

https://s4hanacloud.community.sap/blogs/show/PNBFudWlC9g0RSPuVOIFBg

https://s4hanacloud.community.sap/blogs/show/PNBFudWlC9g0RSPuVOIFBg

Blogs

How to Fill Staging Tables


To fill the staging tables, you can either use an ETL tool or fill the data directly on the SAP HANA database.

You can also use SAP HANA Studio to fill the data.

There are several blogs listed below to show different methods to load data into the staging tables:

▪ Part 1: Migrating data using staging tables and methods for populating the staging tables

▪ Part 2: Using SAP Data Services to load data to the staging tables

▪ Part 3: Using SAP HANA Smart Data Integration (SDI) to load data to the staging tables

▪ Part 4: Using SAP HANA Studio to load data to the staging tables

Migration Approach “Using Staging Tables”

How to Fill Staging Tables – Blogs in SAP Community

Good to know

https://blogs.sap.com/2019/12/02/sap-s-4-hana-migration-cockpit-migrating-data-using-staging-tables-and-methods-for-populating-the-staging-tables/

https://blogs.sap.com/2019/11/29/sap-s-4hana-migration-cockpit-using-sap-data-services-to-load-data-to-the-staging-tables/

https://blogs.sap.com/2019/12/02/part-3-sap-s-4hana-migration-cockpit-using-sap-hana-smart-data-integration-sdi-to-load-data-to-the-staging-tables/

https://blogs.sap.com/2019/12/02/sap-s-4hana-migration-cockpit-using-sap-hana-studio-to-load-data-to-the-staging-tables/

Running Parallel Jobs in

Data Migration


Performance Improvement - Use Max. Data Transfer Jobs

KBA 2878945 - Migration Cockpit:

Parallelization of XML file loads

New



Example

▪ 4 migration objects - 1 project - each one uses 1 load job in parallel

▪ 4 projects – each 1 migration object in parallel

Performance – Batch Jobs

In General

▪ Cloud System: 10 batch job processes on each instance (Q-System: 1 instance / P-System: 2 instances)

▪ Maximum of 80% of all available background jobs can be used

▪ At least 2 batch jobs per migration object: 1 controller job + ´n´ jobs to load data

Hint

▪ Files: split your data into separate files – only then parallel processing is possible

▪ If field “Max Data Transfer Jobs” is set to 2 – 3 jobs are required (including 1 controller job)

▪ If field “Max Data Transfer Jobs” is set to 4, and only 3 files are existing - only 3 jobs will be scheduled

▪ Changes in “Max Data Transfer Jobs” will be taken into account:

− Files: wait until the activity is complete - start again

− Staging: either “Restart Transfer” or “Finish” and “Start Transfer” again

Outlook


This part of the document may mention releases of SAP software that are not yet available.




• Production volume capture

• EFD-Reinf(Escrituração Fiscal Digital de Retenções e

Outras Informações Fiscais)

• FI-CA Dunning History

• FI-CA Payment

• Product - Extend existing record by

new org levels (will also support custom fields, replaces

Material - Extend)

• EHS – Location hierarchy (new 2005 version because of key change)

• Characteristic group

Additional Migration Objects Planned for 2005 or for Later Release

This page may mention releases of SAP software that are not yet available.




SAP S/4HANA Migration Cockpit - Pre-Announcement of New openSAP Course

Course Content

Week 1: SAP S/4HANA Migration Cockpit

Week 2: Migration Object Modeler (File/Staging)

Week 3: SAP S/4HANA Migration Cockpit –

Direct Transfer Approach

Week 4: Additional Migration Topics

Week 5: Final Exam

https://open.sap.com/courses/s4h16




“Good management is the lifeblood of

the healthy corporate body. Getting rid

of it to save costs is like losing weight

by giving blood.” Tom DeMarco, Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency


More Tips & Tricks – See Published Newsletters

http://help.sap.com/disclaimer?site=https://www.sap.com/documents/2019/08/b87f13b1-627d-0010-87a3-c30de2ffd8ff.html

http://help.sap.com/disclaimer?site=https://www.sap.com/documents/2019/11/706de8c5-737d-0010-87a3-c30de2ffd8ff.html

https://help.sap.com/viewer/aa1fd76f0e1245e8ae49b1ada22d9a98/SHIP/en-US/e19194aa32744525a29cc1c7171f985b.html

https://www.sap.com/documents/2019/02/80f57ddb-3a7d-0010-87a3-c30de2ffd8ff.html

https://www.sap.com/documents/2019/06/56c57595-517d-0010-87a3-c30de2ffd8ff.html

Data Migration Status AppThe easy way to monitor

your data migration in SAP S/4HANA Cloud


So meistern Sie Ihr

Migrationsprojekt Schritt für

Schritt!

▪ Der umfassende Leitfaden für die

Vorbereitung, Einrichtung und

Integration

▪ Systemkonvertierung,

Landschaftstransformation und

Neuimplementierung

▪ Ob Cloud oder On-Premise –

detaillierte Anleitungen und Best

Practices für alle Szenarien

Migration nach SAP S/4HANA

572 Seiten, gebunden,

2., aktualisierte und erweiterte Auflage

2018

Buch | E-Book | Bundle

ISBN 978-3-8362-6316-0

Jetzt bestellen: http://www.sap-press.de/4645

http://www.sap-press.de/4645


Your roadmap to SAP S/4HANA

migration!

▪ The comprehensive guide to getting SAP

S/4HANA: new implementation, system

conversion, and landscape transformation

▪ Planning, implementation, integration:

find the information you need for each

project phase

▪ Detailed instructions for cloud, on-

premise, and hybrid scenariosMigrating to SAP S/4HANA

569 pages, 2017

Book | E-Book | Bundle

ISBN 978-1-4932-1449-5

Order now: www.sap-press.com/4247

http://www.sap-press.com/4247

© 2020 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.

www.sap.com/contactsap

Follow us

https://www.sap.com/copyright

https://www.sap.com/registration/contact.html

https://www.linkedin.com/company/sap

https://www.youtube.com/user/SAP

https://twitter.com/sap

https://www.facebook.com/SAP

SAP S/4HANA Data Migration Content Development

Documents

Transcript of SAP S/4HANA Data Migration Content Development