Documentos de Académico
Documentos de Profesional
Documentos de Cultura
▪ is designed for a
▪ is part of the SAP S/4HANA standard delivery, included in the licenses
▪ resides in the SAP S/4HANA system
▪ has an execution environment – migration cockpit – and a modeling
environment – migration object modeler –
▪ comprises three migration approaches: file, staging, direct transfer
▪ provides guidance through the migration process
▪ contains preconfigured migration objects and rules
▪ includes automatized cross-object value mapping
▪ uses SAP standard APIs to create the data in the target
Transfer data directly from SAP system (new with SAP S/4HANA 1909)
▪ Transfer data from SAP ERP source system to target SAP S/4HANA system
▪ Access source system via RFC connection
▪ Supports data migration scenarios from other applications, e.g. from SAP Apparel and Footwear (SAP AFS) SAP S/4HANA
to SAP S/4HANA for fashion and vertical business, SAP Extended Warehouse Management (SAP EWM) to
decentralized EWM
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3
Getting Started
SAP EWM to decentralized EWM based on SAP S/4HANA
SAP S/4HANA
Preconfigured migration objects
▪ Warehouse Stock
▪ Warehouse Product SAP Decentral EWM
▪ Storage Bin Business Suite EWM* based on SAP S/4HANA
▪ Storage Bin Sorting
▪ Fixed Bin Assignment
*Prerequisite for transfer of data directly from SAP system: DMIS installation in source
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4
Getting Started
SAP Apparel and Footwear (SAP AFS) to SAP S/4HANA
*Prerequisite for transfer of data directly from SAP system: DMIS installation in source
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5
Getting Started
Technical preconditions and preparations
Technical preconditions
▪ SAP ERP to SAP S/4HANA, the lowest supported ERP release is ERP 6.0 (SAP NetWeaver 7.0), SAP Note 2836748
▪ SAP Apparel and Footwear (SAP AFS) to SAP S/4HANA, the lowest supported release is AFS 6.0, SAP Note 2836840
▪ SAP EWM to decentralized EWM, the lowest supported EWM release is EWM 5.1 (SAP NetWeaver 7.0)
Define a mapping strategy between SAP source and SAP S/4HANA target
▪ Standard APIs are used to load the data into SAP S/4HANA target system
▪ Where configuration in the source deviates from the configuration in the target, adequate mappings have to
be defined upfront, such as rename of organizational units, cost centers, document types, ….
▪ In case of questions carefully check the object-related documentation
API-based
SAP S/4HANA
SAP S/4HANA
Transaction:
LTMOM
APPENDIX
FI-CO Cost element group FI-GL Exchange rate FI-TRM Foreign exchange swap contract
FI-CO Internal order FI-GL General ledger account FI-TRM Interest rate instrument
FI-CO Profit center FI-GL House bank FI-TRM OTC interest rate derivative swap
FI-CO Profit center standard hierarchy and groups FI-GL Open item – classic G/L FI-TRM Payment details
FI-CO Secondary cost element FI-GL Open item – ledger group specific FI-TRM Settlement
open@sap.com
Follow all of SAP
www.sap.com/contactsap
System “S4H”
SAP ERP 6.0 with EHP 8 / An RFC connection connects
NetWeaver 7.50 the SAP S/4HANA migration
cockpit to the SAP ERP SAP S/4HANA
source system 1909 FPS00
Cost center
Select data by using criteria: Map & transform data Simulate Migrate
▪ Organizational unit:
Company code
Activity type
▪ Migration object:
FI-CO Cost center
▪ Migration object:
FI-CO Activity type
(1) Create a migration project (in the SAP S/4HANA target system “S4H”)
When saving the project, numerous programs are generated and the migration objects are copied from
the delivered template into your project. This step takes some time. In case of errors during the copy
process you can restart it (error message with link in the header).
The migration cockpit guides you through the various steps of the data migration. You can also flexibly
choose which steps you want to do next (select, simulate, migrate).
Compare the data selected by the SAP S/4HANA migration cockpit with the data in the ERP source system. You can either use the
application transactions as shown below or use transaction SE16 to have a look directly into table CSKS (for cost centers) and CSLA
(for activity types).
With transaction KL13 you see 3 activity
types in the source system in controlling
area 0001
In 1909, the deletion function has not yet been implemented in SAP Fiori but
does exist in the back end: report CNV_PE_MC_DEL_ITEMS
(1) Create a migration project (in the SAP S/4HANA target system “S4H”)
open@sap.com
Follow all of SAP
www.sap.com/contactsap
(1) Create a migration project (in the SAP S/4HANA target system “S4H”)
As soon as the selection has finished, the system automatically creates mapping tasks for each object. For
each source mapping value a target mapping value proposal is created (1:1). The mapping tasks are defined
in the delivered objects.
You can change or create mapping tasks in the migration object modeler.
On this screen, you specify mapping values to transform values from the source system to the target system.
In the migration object modeler, you can upload and download mapping values.
Documentation
for mapping
task
Simulation means the API used in the migration object is executed in the same way as in real mode. The only difference is
that the data is not created and posted in the target system. The simulation brings up the messages from the migration
cockpit as well as from the application.
A few APIs have no simulation function, e.g. migration object FI-GL House bank. If this is the case, it is mentioned in the
migration object documentation and the simulation action is not offered.
On the migration object screen you can execute actions for items you chose individually.
For one instance of migration object FI-CO Activity Type and for six instances of migration object FI-CO Cost
Center the simulation ended with errors.
(1) Create a migration project (in the SAP S/4HANA target system “S4H”)
open@sap.com
Follow all of SAP
www.sap.com/contactsap
(1) Create a migration project (in the SAP S/4HANA target system “S4H”)
In the migration object detail screen, mark the erroneous entry and click Messages
Error Concerned instances Change mapping Create data in the Exclude item
target
KS030: Cost element Activity type: ADMIN Change mapping to an Create the cost element Exclude the
does not exist existing / fitting cost element erroneous item
in the SAP S/4HANA target (activity type
system ADMIN)*
KS070 Area Cost center: KSDT2000C1, Change mapping to an Create the cost center group Exclude the
K0001_HIER cannot KSDT2000C2, KSDT9999C3, existing / fitting cost in the standard hierarchy in erroneous items
be used here KSDT9999C4, KSDT9999C5, center group in the SAP the target
KSDTGERMAN S/4HANA target system
for all 6 cost centers*
Warning
KS096 Profit Center Cost center: KSDT2000C1, Insert target mapping values Exclude the
Accounting active but KSDT2000C2, KSDT9999C3, (currently target is blank as erroneous items
no profit center KSDT9999C4, KSDT9999C5, source profit center is also
specified KSDTGERMAN blank)
Migrate the data. For the migration step, the same possibilities exist as for the simulation: migrate single items (on the
migration object screen), migrate random 10% or random 500 items, migrate only instances with errors, migrate all instances.
Compare the data migrated by the SAP S/4HANA migration cockpit with the data in the SAP S/4HANA target system. You
can either use the application transactions listed below or use transaction SE16 to have a look directly into table CSKS (for
cost centers) and CSLA (for activity types).
(1) Create a migration project (in the SAP S/4HANA target system “S4H”)
open@sap.com
Follow all of SAP
www.sap.com/contactsap
Typical Questions:
▪ How can I adapt the delivered content to my customers' needs? SAP S/4HANA
▪ Is it possible to adjust the existing SAP migration objects?
▪ How can I adjust the selection of data for the direct transfer approach?
▪ How can I create my own migration objects to transfer customer-specific data?
Migration object modeler: modeling environment of the SAP S/4HANA migration cockpit
Gap: migration object “FI-CO Cost ERP source system Logon language: German
centers” currently (OP1909) only transfers
the master data text in the logon language.
If there are also texts in other languages,
an additional migration object is needed.
You see the two standard migration objects that are already assigned to
the project
If you have specific requirements that are not covered by the migration objects provided by SAP, you can
create user-defined migration objects.
Choose: Project -> Create Migration Object -> User-
Defined -> Migrate Data Directly from SAP System.
This path opens a wizard which supports you in
creating your own object.
Pay attention to
the documenation!
In the Source Structures step you define the table(s) from which the selection will read the data. You can also
use customer-own tables here.
Table CSKT does not contain all the fields that are needed to feed the respective BAPI (field valid-from is
missing), so we need a second table CSKS to fill all fields. CSKS is defined as child table in this data model.
Position the cursor on table CSKT and choose Add Child Table
In this step, you define which fields determine a migration object instance in a unique way. In this example, the
Language Key, Controlling Area, Cost Center, and Valid To Date fields define one instance unambiguously.
Assign the function module which will be used to post or create the data in the SAP S/4HANA target system.
You can also assign an own custom API.
Back in the migration cockpit, you see the newly created migration object. This migration object is processed
in the same way as the migration objects delivered by SAP.
open@sap.com
Follow all of SAP
www.sap.com/contactsap
After having finished the steps in the migration object wizard, some more details need to be edited directly in transaction
LTMOM. Then the new migration object is ready to be used. On the Selection Criteria tab you can influence the selection and
define filters.
Filter is a collection of values of the same type that is stored centrally for your project, and therefore available for all
migration objects assigned to the project. A filter can be for example company code, controlling area, plant, …
BUKRS
Simulation Details tab: Define how simulation will work in your customer object. F1 on the input field for Simulation Type
provides detailed documentation about the possible choices.
Check the description of the function
module to get the details about a
possible simulation functionality and
how to fill parameters.
Chose “1”
Choose Add
Structure Mapping tab: What information has to be transferred from the source structure to the structure of the function
module?
Source structure
Drag and drop the source structure CSKT to the target structure (to the function
module BAPI_COSTCENTER_CHANGEMULTIPLE)
The access path defines how the records of child table CSKS will be selected. In the present data model, for each record in
CSKT there is only one dedicated record in CSKS. So the option “Any Line” is chosen.
Click COSTCENTERLIST
Field Mapping tab: Map the fields of the source structure to the fields of the target structure / the function module
Only the mapped fields are shown. You
can change it to “All Fields” if you want
to get all.
Transformation
type is “Move”. This
means all values are
moved unchanged
1:1 from the source
system to the target
SAP S/4HANA
system
Drag and drop the source fields on the left-hand side (from CSKT and CSKS) to the target fields of the function module
BAPI_COSTCENTER_CHANGEMULTIPLE (on the right-hand side). Field DATAB is moved from table CSKS, all other fields from
CSKT. Be careful to expand the correct table (!) under Source Structures in order to chose the fields from the correct table!
The definition of the migration object is now complete. Save it and leave transaction LTMOM.
© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10
Migration Object Modeler: Creating Your Own Migration Object II
Migration cockpit – Execute the selection, execute the simulation
Back in the migration cockpit, execute the selection, then execute the simulation.
Selection result
Simulation result
open@sap.com
Follow all of SAP
www.sap.com/contactsap
In transaction LTMOM, you have the possibility to download and upload mapping, either for dedicated migration objects or
for all migration objects within the project. Transformation Rule is called Mapping Task in the migration cockpit (SAP Fiori).
Download/upload mappings
Mapping
documentation
Original Format: The difference in this option is that the
The program will create a local Excel is filled with values.
XML file. ▪ All values
Compressed: ▪ Created automatically – during the
The program will create a local selection of source items, the Excel is
archive file (.ZIP). filled with 1:1 entries for the fields to be
Signature mapped
▪ Created manually – a user has created
or changed mapping entries
In transaction LTMOM, you can change the selection for each migration object. Note that it is your responsibility to
care for the consistency of the items to be selected.
Double-click opens
up the section below
Double-click
Remember Week 3 Unit 2 on the Here, you can choose/exclude intervals or single
focus topic “Repeated Selection” values for the selection from the source system,
e.g. select only cost centers from 1 to 100
As well as the transformation type MOVE (see example in Week 3 Unit 6), other types are also possible.
With the Simulation button you can test how the source fields are
transferred to the target SAP S/4HANA system. You can specify
whether all the items should be involved or just some items
corresponding to criteria that you provide on the selection screen.
SAP S/4HANA migration cockpit: Transfer data directly from SAP system
open@sap.com
Follow all of SAP
www.sap.com/contactsap