Migration Objects For SAP S/4HANA: Implementation Guide - Public 2020-01-09

IMPLEMENTATION GUIDE | PUBLIC
2020-01-09
Migration Objects for SAP S/4HANA

© 2020 SAP SE or an SAP affiliate company. All rights reserved.
THE BEST RUN

Content
1 Available Migration Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 PUBLIC Content
1 Available Migration Objects
You can use the following table to gain an overview of all migration objects available for SAP S/4HANA. It is
sorted in alphabetical order by Migration Object Name. Choose a migration object name to navigate to the
corresponding documentation for the migration object.
 Note
The migration object documentation for the Transferring Data Directly from an SAP System migration
approach is currently only available in the system.
Use the search field in the relevant column to search for a specific Migration Object Name or Business Object
Name.
Choose Filter to apply further filters for Master data and/or Transactional data in the Business Object Type
column, and for the application component in the Component column to narrow down the results list. If you
want to see more or less information, choose Show/hide columns, and select the respective checkboxes for the
columns you would like to show or hide.
 Tip
Filter the Migration Approach column to only see migration objects relevant for you. Therefore, choose Filter
in the respective column, and select the required approach, Direct Transfer, File, or Staging Table.
You can export the below table in CSV format with the current column visibility and filters applied. Therefore,
choose the CSV button above the table.
Migration Object Business Object

Name Name Business Object Type Migration Approach Component
FI - Accounts payable Accounting Document Transactional data File FI-AP

open item [page 182] Staging Table
FI - Accounts receiva Accounting Document Transactional data File FI-AR

ble open item [page Staging Table
186]
File FI
FI - G/L account bal Accounting Document Transactional data
ance and open/line Staging Table
item [page 116]
Activity price [page Activity Price Master data File CO

21] Staging Table
Activity type [page Activity Type Master data File CO

141] Staging Table

Available Migration Objects PUBLIC 3
Bank account balance Bank Account Transactional data File FI

[page 22] Staging Table
Cash memo record Bank Account Transactional data File FIN-FSCM-CLM-CM

Bank [page 24] Bank Master data Master data File FI

Staging Table
Batch (if Batch is Batch Master data File LO-BM

unique at material Staging Table
level) [page 25]
Batch (if Batch level is Batch Master data File LO-BM

at plant level) [page Staging Table
29]
Material BOM [page Bill of Material Master data File PP-BD

32] Staging Table
PM - Equipment BOM Bill Of Material Master data File PM

PM - Functional loca Bill Of Material Master data File PM

tion BOM [page 106] Staging Table
File IS-PM-PA
PA - Catalog item Catalog Item Master data
PSS - Product compli Chemical Compliance Master data File EHS-SUS

ance info [page 89] Info Staging Table
PSS - Raw material Chemical Compliance Master data File EHS-SUS

compliance info [page Info Staging Table
86]
Class hierarchy [page Class Master data File CA-CL

42] Staging Table
Characteristic [page Classification Charac Master data File CA-CL

36] teristic Staging Table
Class [page 39] Classification Class Master data File CA-CL

Staging Table
Object classification Classification Valua Master data File CA-CL

[page 45] tion Staging Table

4 PUBLIC Available Migration Objects
PSS - Substance [page Company Substance Master data File EHS-SUS

228] Staging Table
Condition contract Condition Contract Master data File LO-AB

Consent [page 61] Consent Record Transactional data File CA-GTF-CON

Staging Table
Cost center [page 135] Cost Center Master data File CO

Staging Table
Customer - extend ex Customer Master data File SD

isting record by Credit Staging Table
Management data
[page 70]

isting record by Thai Staging Table
land branch code
[page 68]
Customer [page 75] Customer Master data File SD

Staging Table

isting record by new Staging Table
org levels [page 65]
Customer Material Customer Material Master data File SD

Document info record Document Info Record Master data File CA-DMS
PM - Equipment [page Equipment Master data File PM

95] Staging Table
Exchange rate [page Exchange Rate Master data File FI

97] Staging Table
File FI
FI - Historical balance Financial Accounting Transactional data
Fixed asset (incl. bal Fixed Asset Master data File FI-AA
ances and transac Transactional data Staging Table
tions) [page 98]

PM - Functional loca Functional Location Master data File PM

tion [page 108] Staging Table
G/L account [page General Ledger Ac Master data File FI

114] count Staging Table
QM/PM - Catalog code Inspection Code Group Master data File QM

group/code [page Staging Table
208]
QM - Inspection Inspection Method Master data File QM

method [page 124] Staging Table
QM - Inspection plan Inspection Plan Master data File QM

QM - Selected set Inspection Selected Master data File QM

[page 223] Set Staging Table
QM - Selected set code Inspection Selected Master data File QM

[page 225] Set Staging Table
QM - Master inspec Inspection Specifica Master data File QM

tion characteristic tion Staging Table
[page 175]
Internal order (re Internal Order Transactional data File CO

stricted) [page 129] Staging Table
Legal transaction Legal Transaction Transactional data File LCM

PM - Maintenance item Maintenance Item Master data File PM

File PM
PM - Maintenance noti Maintenance Notifica Transactional data
fication [page 84] tion Staging Table
PM - Maintenance plan Maintenance Plan Master data File PM

PM - Equipment task Maintenance Task List Master data File PM

list [page 93] Staging Table
PM - Functional loca Maintenance Task List Master data File PM

tion task list [page Staging Table
104]

PM - General mainte Maintenance Task List Master data File PM

nance task list [page Staging Table
110]
JIT - Customer [page JIT – Customer Data Master data File LE-JIT
178] Staging Table
Material [page 162] Material Master data File LO

Staging Table
Material inventory bal Material Stock Transactional data File MM-IM

ance [page 131] Staging Table
PM - Measuring point Measuring Point Master data File PM

Condition record for Price Condition Master data File SD

pricing (general tem Staging Table
plate) [page 55]
Condition record for Price Condition Master data File MM-PUR

pricing in purchasing Staging Table
[page 173]
Condition record for Price Condition Master data File SD

pricing in sales [page Staging Table
219]
Material - Forecast Product Master data File MM

planning [page 148] Staging Table
Material - extend exist Product Master data File LO

ing record by new org Staging Table
levels [page 150]
Material inspection Product Master data File QM

setup [page 128] Staging Table
Material - extend exist Product Master data File MM

ing record with long Staging Table
text [page 158]
Product classification - Product Master data File SLL

Commodity code Staging Table
[page 147]

Xceptional case - Ma Product Master data File CO-PC-ACT

terial price chng for Staging Table
global currencies
[page 169]
File SLL
Product classification - Product Master data
Legal control [page Staging Table
156]
File MM
Product consumption Product Transactional data
Production version Production Version Master data File PP

Profit center [page Profit Center Master data File CO

190] Staging Table
PS - Network [page PS - Network Transactional data File PS

197] Staging Table
PS - Project [page PS - Project Transactional data File PS

198] Staging Table
PS - WBS element PS - WBS element Transactional data File PS

Purchase contract Purchase Contract Transactional data File MM-PUR

Purchase order (only Purchase Order Transactional data File MM-PUR

open PO) [page 205] Staging Table
Purchase scheduling Purchase Scheduling Transactional data File MM-PUR

agreement [page 217] Agreement Staging Table
Purchasing info re Purchasing Info Record Master data File MM-PUR
cord- extend existing Staging Table
record [page 200]
Purchasing info record Purchasing Info Record Master data File MM-PUR
with conditions [page Staging Table
202]
Routing [page 211] Routing Master data File PP

Staging Table

Sales contract [page Sales Contract Transactional data File SD

221] Staging Table
Material determination Sales Material Substi Master data File SD

[page 160] tution Staging Table
Sales order (only open Sales Order Transactional data File SD

SO) [page 215] Staging Table
Software/Hardware Software Constraint Master data File PLM

constraint [page 230] Staging Table
Source list [page 226] Source List Master data File MM-PUR
Staging Table
Supplier - extend exist Supplier Master data File MM

ing record by Thailand Staging Table
branch code [page
236]
Supplier [page 238] Supplier Master data File MM

Staging Table
Supplier - extend exist Supplier Master data File MM

ing record by new org Staging Table
levels [page 232]
File LO-VC
VC - Configuration pro Variant Configuration Master data
file [page 58] Profile Staging Table
Work center/Resource Work Center Master data File PP

Business partner Business partner Master data Direct Transfer - ERP AP-MD-BP
FI-GL Bank account FI-GL Bank account Master data Direct Transfer - ERP FI
FI-GL Bank key FI-GL Bank key Master data Direct Transfer - ERP FI
Characteristic Characteristic Master data Direct Transfer - ERP CA-CL
Class Class Master data Direct Transfer - ERP CA-CL-CLS
General classification General classification Master data Direct Transfer - ERP CA

assignments assignments
Engineering change Engineering change Master data Direct Transfer - ERP CA-GTF-ECM
number number

VC - Object depend VC - Object depend Master data Direct Transfer - ERP LO-VC
ency & dependency ency & dependency
net net
FI-GL House bank FI-GL House bank Master data Direct Transfer - ERP FI
FI-CO Activity group FI-CO Activity group Master data Direct Transfer - ERP CO
FI-CO Activity type - FI-CO Activity type - Master data Direct Transfer - ERP CO-OM
price planning price planning
FI-CO Activity type FI-CO Activity type Master data Direct Transfer - ERP CO
FI-CO Business proc FI-CO Business proc Master data Direct Transfer - ERP CO-OM-ABC
ess ess
FI-CO Business proc FI-CO Business proc Master data Direct Transfer - ERP CO-OM-ABC
ess group ess group
FI-CO Cost center FI-CO Cost center Master data Direct Transfer - ERP CO
FI-CO Cost center FI-CO Cost center Master data Direct Transfer - ERP CO
standard hierarchy and standard hierarchy and
groups groups
FI-CO Cost Element FI-CO Cost Element Master data Direct Transfer - ERP CO
Group Group
FI-CO Internal order FI-CO Internal order Master data Direct Transfer - ERP CO
FI-CO Profit center FI-CO Profit center Master data Direct Transfer - ERP CO
FI-CO Profit Center FI-CO Profit Center Master data Direct Transfer - ERP CO
Standard Hierarchy & Standard Hierarchy &
Groups Groups
FI-CO Secondary cost FI-CO Secondary cost Master data Direct Transfer - ERP CO
element element
FI-CO Statistical key FI-CO Statistical key Master data Direct Transfer - ERP CO
figure figure
FI-AA Fixed asset - in FI-AA Fixed asset - in Transactional data Direct Transfer - ERP FI-AA
cluding balance cluding balance
FI-GL Vendor open FI-GL Vendor open Transactional data Direct Transfer - ERP FI
item - classic GL item - classic GL

FI-GL Vendor open FI-GL Vendor open Transactional data Direct Transfer - ERP FI
item - new GL item - new GL
FI-GL Customer open FI-GL Customer open Transactional data Direct Transfer - ERP FI
item - classic GL item - classic GL
FI-GL Customer open FI-GL Customer open Transactional data Direct Transfer - ERP FI
item - new GL item - new GL
FI-GL Exchange rate FI-GL Exchange rate Transactional data Direct Transfer - ERP FI
FI-GL Account balance FI-GL Account balance Transactional data Direct Transfer - ERP FI
- classic GL - classic GL
FI-GL Account balance FI-GL Account balance Transactional data Direct Transfer - ERP FI
- new GL - new GL
FI-GL General ledger FI-GL General ledger Transactional data Direct Transfer - ERP FI
account account
FI-GL Open item - clas FI-GL Open item - clas Transactional data Direct Transfer - ERP FI
sic GL sic GL
FI-GL Open item - FI-GL Open item - Transactional data Direct Transfer - ERP FI
ledger group specific ledger group specific
FI-GL Open item - new FI-GL Open item - new Transactional data Direct Transfer - ERP FI
GL GL
FI-TRM Additional flow FI-TRM Additional flow Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
FI-TRM Commercial FI-TRM Commercial Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
paper paper
FI-TRM Condition de FI-TRM Condition de Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
tails tails
FI-TRM Foreign ex FI-TRM Foreign ex Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
change collar contract change collar contract
change option change option
change spot/forward change spot/forward
contract contract

change swap contract change swap contract
FI-TRM Interest rate in FI-TRM Interest rate in Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
strument strument
FI-TRM OTC Interest FI-TRM OTC Interest Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
rate derivative swap rate derivative swap
FI-TRM Payment de FI-TRM Payment de Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
tails tails
FI-TRM Settlement FI-TRM Settlement Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
Condition contract Condition contract Transactional data Direct Transfer - ERP LO-GT
VC - Configuration pro VC - Configuration pro Master data Direct Transfer - ERP LO-VC
file file
Batch (if Batch is Batch (if Batch is Master data Direct Transfer - ERP LO-BM
unique at material unique at material
level) level)
Batch (if Batch is Batch (if Batch is Master data Direct Transfer - ERP LO-BM
unique at plant level) unique at plant level)
Material commodity Material commodity Master data Direct Transfer - ERP LO-MD-MM
Material consumption Material consumption Master data Direct Transfer - ERP LO-MD-MM
Material Material Master data Direct Transfer - ERP LO-MD-MM
VC - Material variant VC - Material variant Master data Direct Transfer - ERP LO-VC
Vendor Vendor Master data Direct Transfer - ERP LO-MD-BP
Purchasing info record Purchasing info record Master data Direct Transfer - ERP MM-PUR
Purchase order(only Purchase order(only Transactional data Direct Transfer - ERP MM-PUR
open PO) open PO)
Purchase requisi Purchase requisi Transactional data Direct Transfer - ERP MM-PUR
tion(only open PR) tion(only open PR)
Purchasing contract Purchasing contract Transactional data Direct Transfer - ERP MM-PUR-OA
Quota arrangement Quota arrangement Transactional data Direct Transfer - ERP MM-PUR
Scheduling agreement Scheduling agreement Transactional data Direct Transfer - ERP MM-PUR

Service entry sheet Service entry sheet Transactional data Direct Transfer - ERP MM
Service master Service master Master data Direct Transfer - ERP MM-SRV
Source list Source list Master data Direct Transfer - ERP MM-PUR
Material inventory bal Material inventory bal Transactional data Direct Transfer - ERP MM-IM
ance ance
Equipment Equipment Master data Direct Transfer - ERP PM
Equipment BOM Equipment BOM Master data Direct Transfer - ERP PM-EQM-BM
Equipment task list Equipment task list Master data Direct Transfer - ERP PM-PRM-TL
Functional location Functional location Master data Direct Transfer - ERP PM
Functional location Functional location Master data Direct Transfer - ERP PM-PRM-TL
task list task list
General task List General task list Master data Direct Transfer - ERP PM-PRM-TL
Maintenance order Maintenance order Transactional data Direct Transfer - ERP PM
Maintenance item Maintenance item Master data Direct Transfer - ERP PM
Maintenance plan Maintenance plan Master data Direct Transfer - ERP PM
Measurement docu Measurement docu Master data Direct Transfer - ERP PM

ment ment
Maintenance notifica Maintenance notifica Transactional data Direct Transfer - ERP PM

tion tion
Measuring point Measuring point Master data Direct Transfer - ERP PM-EQM-SF-MPC
Work center Work center Master data Direct Transfer - ERP PM
Functional Location Functional Location Master data Direct Transfer - ERP PM

BOM BOM
Material BOM Material BOM Master data Direct Transfer - ERP PP-BD
Material MRP Area Material MRP Area Master data Direct Transfer - ERP LO-MD-MM
Miscellaneous PRT Miscellaneous PRT Master data Direct Transfer - ERP PP-BD-PRT
Sales order BOM Sales order BOM Master data Direct Transfer - ERP PP-BD

Planned independent Planned independent Transactional data Direct Transfer - ERP PP-MP-DEM
requirement requirement
Production order Production order Master data Direct Transfer - ERP PP
Production version Production version Master data Direct Transfer - ERP PP
Routing Routing Master data Direct Transfer - ERP PP
Work breakdown struc Work breakdown struc Master data Direct Transfer - ERP PP
ture BOM ture BOM
Project system - Net Project system - Net Master data Direct Transfer - ERP PS
work work
Project Project Master data Direct Transfer - ERP PS
Catalog code group Catalog code group Master data Direct Transfer - ERP QM
and code and code
Inspection catalog se Inspection catalog se Master data Direct Transfer - ERP QM
lected sets lected sets
Inspection method Inspection method Master data Direct Transfer - ERP QM
Inspection plan Inspection plan Master data Direct Transfer - ERP QM-PT-IP
Inspection setup Inspection setup Master data Direct Transfer - ERP QM
Master inspection Master inspection Master data Direct Transfer - ERP QM

characteristics characteristics
Quality info record Quality info record Master data Direct Transfer - ERP QM
Inspection catalog se Inspection catalog se Master data Direct Transfer - ERP QM
lected set code lected set code
Customer Customer Master data Direct Transfer - ERP LO-MD-BP
Customer material info Customer material info Master data Direct Transfer - ERP SD-BF
record record
Customer quotation Customer quotation Transactional data Direct Transfer - ERP SD-SLS
Pricing condition (pur Pricing condition (pur Master data Direct Transfer - ERP SD, LO
chasing and sales) chasing and sales)
Sales contract Sales contract Transactional data Direct Transfer - ERP SD

Sales inquiry Sales inquiry Transactional data Direct Transfer - ERP SD-SLS
Sales order (only open Sales order (only open Transactional data Direct Transfer - ERP SD-SLS
SO) SO)
FI-TRM Bank Guaran FI-TRM Bank Guaran Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
tee tee
FI-TRM Security bonds FI-TRM Security bonds Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
FI-TRM Business part FI-TRM Business part Master data Direct Transfer - ERP FIN-FSCM-TRM-TM
ner roles ner roles
FI-TRM Security Class FI-TRM Security Class Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
FI-TRM Fixed Term De FI-TRM Fixed Term De Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
posits posits
FI-TRM Investment FI-TRM Investment Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
certificate certificate
FI-TRM Letter of credit FI-TRM Letter of credit Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
FI-TRM MainFlow de FI-TRM MainFlow de Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
tails tails
FI-TRM Stocks FI-TRM Stocks Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
FI-CO Profit center FI-CO Profit center Master data Direct Transfer - AFS CO
FI-CO Account Bal FI-CO Account Bal Transactional data Direct Transfer - AFS FI
ance-classic GL ance-classic GL
FI-CO Account Bal FI-CO Account Bal Transactional data Direct Transfer - AFS FI
ance-new GL ance-new GL
FI-CO Secondary cost FI-CO Secondary cost Master data Direct Transfer - AFS CO
element element
FI-GL Customer open FI-GL Customer open Transactional data Direct Transfer - AFS FI
Item- classic GL Item- classic GL
FI-GL Customer Open FI-GL Customer Open Transactional data Direct Transfer - AFS FI
Item- new GL Item- new GL
FI-GL General Ledger FI-GL General Ledger Master data Direct Transfer - AFS FI
Account Account

FI-GL Open Item- clas FI-GL Open Item- clas Transactional data Direct Transfer - AFS FI
sic GL sic GL
FI-GL Open Item - FI-GL Open Item - Transactional data Direct Transfer - AFS FI
ledger group specific ledger group specific
FI-GL Open Item-new FI-GL Open Item-new Transactional data Direct Transfer - AFS FI
GL GL
FI-GL Vendor open FI-GL Vendor open Transactional data Direct Transfer - AFS FI
Item -classic GL Item -classic GL
FI-GL Vendor Open FI-GL Vendor Open Transactional data Direct Transfer - AFS FI
Item -new GL Item -new GL
FI-CO Activity Type FI-CO Activity Type Master data Direct Transfer - AFS CO-OM
FI-CO Activity Group FI-CO Activity Group Master data Direct Transfer - AFS CO
FI-CO Activity type- FI-CO Activity type- Master data Direct Transfer - AFS CO-OM
price planning price planning
FI-CO Business Proc FI-CO Business Proc Master data Direct Transfer - AFS CO-OM-ABC
ess ess
FI-CO Cost Center FI-CO Cost Center Master data Direct Transfer - AFS CO
Standard Hierarchy Standard Hierarchy
and Group and Group
FI-CO Profit Center FI-CO Profit Center Master data Direct Transfer - AFS CO
Standard Hierarchy & Standard Hierarchy &
Groups Groups
FI-CO Statistical Key FI-CO Statistical Key Master data Direct Transfer - AFS FI
Figure Figure
FI-CO Cost center FI-CO Cost center Master data Direct Transfer - AFS CO
FI-CO Business proc FI-CO Business proc Master data Direct Transfer - AFS CO-OM-ABC
ess group ess group
FI-CO Cost element FI-CO Cost element Master data Direct Transfer - AFS FI
group group
FI-CO Internal order FI-CO Internal order Transactional data Direct Transfer - AFS CO
FI-GL Exchange rate FI-GL Exchange rate Master data Direct Transfer - AFS FI
FI-GL Bank account FI-GL Bank account Master data Direct Transfer - AFS FI

FI-GL Bank key FI-GL Bank key Master data Direct Transfer - AFS FI
House Bank House Bank Master data Direct Transfer - AFS FI
Purchase grid for arti Purchase Grid for Arti Master data Direct Transfer - AFS LO-RFM-MD-ART
cle cles
Purchase grid for plant Purchase Grid for Plant Master data Direct Transfer - AFS LO-RFM-MD-ART
and article and Article
Purchase grid for Purchase Grid for Master data Direct Transfer - AFS LO-RFM-MD-ART
pur.org., vendor & arti Pur.Org., Vendor & Ar
cle ticle
Purchase grid for pur Purchase Grid for Pur Master data Direct Transfer - AFS LO-RFM-MD-ART
chasing org. and arti chasing Org and Arti
cle cle
Sales grid for article Sales Grid for Article Master data Direct Transfer - AFS LO-RFM-MD-ART
Sales Grid: s.org, Sales Grid: S.Org, Master data Direct Transfer - AFS LO-RFM-MD-ART
dist.ch, cust. grp & ar Dist.Ch, Cust. Grp &
ticle Article
Sales Grid: s.org, Sales Grid: S.Org, Master data Direct Transfer - AFS LO-RFM-MD-ART
dist.ch, customer & ar Dist.Ch, Customer &
ticle Article
Sales Grid: sales org, Sales Grid: Sales Org, Master data Direct Transfer - AFS LO-RFM-MD-ART
dist. channel & article Dist. Channel & Article
Planned indep. require Planned Indep. Re Master data Direct Transfer - AFS PP-MP-DEM
ment at material level quirement at Material
Level
Planned indep. require Planned Indep. Re Master data Direct Transfer - AFS PP-MP-DEM
ment at SKU level quirement at SKU
Level
Planned independent Planned Independent Master data Direct Transfer - AFS PP-MP-DEM
requirement requirement
Routing Routing-Task List Master data Direct Transfer - AFS PP-BD-RTG
Work center Work Center Master data Direct Transfer - AFS PP-BD-WKC
Characteristics for di Characteristics for Di Master data Direct Transfer - AFS CA-CL-CHR
mensions mensions

Characteristics for Characteristics for Master data Direct Transfer - AFS CA-CL-CHR
non-dimensions Non-Dimensions
Classification for batch Classification for Master data Direct Transfer - AFS LO-BM
batches
Engineering change Engineering Change Master data Direct Transfer - AFS CA-GTF-ECM
number Numbers
Batch at plant level Batches at Plant level Master data Direct Transfer - AFS LO-BM
Configuration class for Configuration class for Master data Direct Transfer - AFS CA-CL-CLS
material grid Material Grid
Customer Customer Master data Direct Transfer - AFS LO-MD-BP
Distribution curve con Distribution Curve Master data Direct Transfer - AFS Lo-RFM
dition Conditions
Quantity distribution Quantity Distribution Master data Direct Transfer - AFS LO-RFM
profile Profile
VAS (Sales Area and VAS (Sales Area and Master data Direct Transfer - AFS LO-RFM-CA-VAS
Customer) Customer)
VAS (Sales Area, Cus VAS (Sales Area, Cus Master data Direct Transfer - AFS LO-RFM-CA-VAS
tomer Group and Ma tomer Group and Ma
terial) terial)
VAS (Sales Area, Cus VAS (Sales Area, Cus Master data Direct Transfer - AFS LO-RFM-CA-VAS
tomer and Material) tomer and Material)
Material inventory bal Material Inventory bal Transactional data Direct Transfer - AFS MM-IM
ance ance
Material BOM Material BOM Transactional data Direct Transfer - AFS PP-BD
Purchase order (only Purchase Order Transactional data Direct Transfer - AFS MM-PUR
open PO)
Purchasing info record Purchasing Info Record Transactional data Direct Transfer - AFS MM-PUR
Pricing condition (pur Pricing Condition (pur Master data Direct Transfer - AFS SD-MD-CM
chasing and sales) chasing and sales)
Sales order Sales Order Transactional data Direct Transfer - AFS LO-RFM-SD
Sales order BOM Sales order BOM Transactional data Direct Transfer - AFS CS-OP

Distribution curve Distribution Curve Master data Direct Transfer - AFS LO-RFM
Season Season Master data Direct Transfer - AFS LO-RFM-CA-SE
Article Articles Master data Direct Transfer - AFS LO-MD-MM
Vendor Vendor Master data Direct Transfer - AFS LO-MD-BP
Equipment Equipment Master data Direct Transfer - AFS PM-EQM
Scheduling agreement Scheduling Agreement Master data Direct Transfer - AFS MM-PUR
Segmentation struc Segmentation struc Master data Direct Transfer - AFS LO-RFM
ture ture
Segmentation strategy Segmentation strategy Master data Direct Transfer - AFS LO-RFM
Segmentation default Segmentation default Master data Direct Transfer - AFS LO-RFM
values values
Purchasing contract Purchasing Contract Transactional data Direct Transfer - AFS MM-PUR-OA
Sales contract Sales Contract Master data Direct Transfer - AFS LO-RFM-SD
Source list Source list Master data Direct Transfer - AFS MM-PUR
General classification General classification Master data Direct Transfer - AFS CA

assignments assignments
Production Order Production Order Transactional data Direct Transfer - AFS PP-SFC
Warehouse Fixed Bin Warehouse Storage Master data Direct Transfer - EWM SCM-EWM-MD
Assignments Bin
Warehouse Storage Warehouse Storage Master data Direct Transfer - EWM SCM-EWM-MD
Bin Bin
Warehouse Storage Warehouse Storage Master data Direct Transfer - EWM SCM-EWM-MD
Bin Sorting Bin
Warehouse Product Product Master data Direct Transfer - EWM SCM-EWM-MD
Warehouse Stock n/a Master data Direct Transfer - EWM SCM-EWM
Activities Activities Transactional data Direct Transfer - CRM CRM-BTX-ACT
 Caution
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 which should have been
deleted could be interpreted as the processing of personal data without any legally justified purpose.
 Note
For some migration objects there are additions to the migration object name. These additions include
"restricted" and "deprecated". Restricted means that not all fields and structures of the relevant business
processes are covered by this migration object, deprecated means that there is a newer version of this
migration object available. Deprecated objects will be deleted after a couple of releases. Make sure you
always read the migration object documentation for these objects carefully. Also see SAP Note 2698032
for more details on deprecated migration objects.
 Note
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.
 Note
The pre-delivered data migration objects are built for SAP S/4HANA Cloud and the respective SAP Best
Practices Content. You can use these objects also for SAP S/4HANA and the respective SAP Best Practices
Content. Using SAP S/4HANA, the delivered standard migration objects are templates that can be
enhanced according to your needs. The enhancement is only limited by the functionality of the tool and the
capabilities of the underlying API to load the data. Starting with SAP S/4HANA 1610 FPS2, you can enhance
customer projects based on these delivered standard migration objects or you can create your own objects
using the SAP S/4HANA migration object modeler (transaction LTMOM). For further information, please see
SAP Note 2481235 .
Further Information
● Use these SAP Help Portal aliases to access the following sections of our product assistance:
Type this in your browser... To jump to...
http://help.sap.com/S4_OP_MO this very topic: Available Migration Objects
http://help.sap.com/S4_OP_DM the landing page for data migration
● If you are using the Fixed asset (incl. balances and transactions) [page 98] migration object, you can find
additional information about the available fields for each asset class in SAP Note 2468501 .
● If you want to view information about the differences between the current release and the previous release,
see SAP Note 2704618 .

1.1 Activity price
Available Migration Objects [page 3] in SAP S/4HANA.
 Restriction
This object must not be used to migrate activity prices in SAP S/4HANA Cloud. The API used here does not
support the cloud tables For professional services use the Condition record for pricing (general template)
[page 55] migration object.
Purpose
Business Object Component/Area Controlling (CO)
Business Object Type Master data
Business Object Definition To plan and allocate the activities, the system records quan
tities that are measured in activity units. Activity quantities
are valuated using a price. Costs based on the activity quan
tity of an activity type can be posted separately in fixed and
variable portions.
In Scope
Migration to SAP S/4HANA is supported.
Supported Features
The following structures/features are supported in SAP S/4HANA:
● Activity Price Header
Prerequisites
The following objects must have already been maintained or migrated:
● Activity type [page 141]

● Cost center [page 135]

Validity Period and Dependencies
Business objects that reference this object must be created within the correct validity period for this object.
If a successor object is created with a validity period that starts before the validity period of this object, it will
normally cause an error message during the creation or migration of the successor object.
You therefore have to check such time dependencies before you create or migrate your objects. This will avoid
subsequent error messages and inconsistent data on your database.
Mapping Instructions
Mapping Structure Hierarchy
Level Name
1 Activity Price Header (mandatory)
Tasks
1. Download the migration template from the Migration Cockpit.

2. Navigate to the Data Migration to SAP S/4HANA from File (BH5) scope item on SAP Best Practices
Explorer.
There, choose your SAP S/4HANA release from the Version field.
Download the test script from the Details section.
3. Follow the procedure described in the BH5 test script.
Post-Processing
How to Validate your Data in the System
Transaction KP26 Change Plan Data for Activity Types
Transaction KP27 Display Plan Data for Activity Types
1.2 Bank account balance

Purpose
Business Object Component/Area Financial Accounting (FI)
Business Object Type Transactional data
Business Object Definition The Bank Account Balance is the value date balance of each
bank account, which serves the requirement of cash position
analysis for cash managers.
Migration is for initializing the balance for bank accounts

which are operated centrally, that is, in the same system as
Cash Management.
In Scope
Supported Features
● Bank Account Balance
Prerequisites
Bank account needs to be created before initializing the balance, you can find the Technical ID in bank account
master data, on the General data tab and this Technical ID is used as Account ID in the file to be imported.
Cash flow should not be generated for the company code used before migrating this object into the system.
Otherwise the user will get the error message Company code XYZ already has flows generated from
FI in one Exposure.
Level Name
1 Bank master data (mandatory)

Tasks

Explorer.
Post-Processing

To validate your migrated data, you can use the FQM_FLOW table in transaction SE16N. To get results, you have
to enter the values Technical ID and Company Code. You can retrieve these from the FCLM_BAM_AMD table.
Transaction SE16N General Table Display
1.3 Bank
Purpose
Business Object Definition An institution that provides financial services to individuals

and to businesses for profit, generally including taking
money deposits, issuing credit, and processing transactions.
In Scope

Supported Features
● Bank Country
● Bank Key
● Bank Address Data
Level Name
1 Bank master data (mandatory)
Tasks

Explorer.
Post-Processing
Transaction FI03 Display Bank
1.4 Batch (if Batch is unique at material level)

Purpose
Business Object Component/Area Quality Management (QM)
Sales and Distribution (SD)
Production Planning for Process Industries (PP-PI)
Business Object Definition Batch Master Data (if batch is unique at material level).
In Scope
1. Batch basic data

2. Batch classification data
Out of Scope
1. Long texts for batches
Supported Features
● Material Number
● Batch Number
● Plant
● Batch Attributes
● Batch Status
● Characteristic Values
● Control Parameters
Prerequisites
● Material [page 162]

● Supplier [page 238]
● If you want to migrate batches with classification data, the following objects need to be migrated first:
○ Characteristic [page 36]
○ Class [page 39]
○ Object classification [page 45]
Please see the mapping instructions for this object, paying special attention to the Material
Classification for Batches section.
Class Field on the Batch Basic Data Sheet
Please provide here the batch class to which your material is assigned. All the characteristics with reference to
a table field are then created automatically during migration. Example: Class YB_EXP_DATE_002;
Characteristic LOBM_VFDAT refers to table field MCH1-LFDAT. If the Shelf Life Expira. or Best-Before Date field is
filled, the content will be copied into the classification value of Characteristic LBOM_VFDAT.
Field Valuation Type on the Plant Data sheet
If you want to create a batch for a material that is defined by its valuation category as a material valuated in
single batches, you have to provide a valid valuation category. In this case, leaving the field valuation category
empty is not allowed .
VALUE_FROM and VALUE_TO Fields
The values in VALUE_FROM and VALUE_TO always relate to the unit of measurement of the characteristic.
Unit of Measurement (UOM) UNIT_FROM and UNIT_TO Fields
If the unit of measurement specified here does not equal the unit of measurement of the characteristic, the
output is converted into this unit of measurement.
For example, if the Characteristic has the ISO UOM ANN (Year), and the VALUE_FROM field has the value 2, and
if the UNIT_FROM field has the ISO UOM MON, the two years are converted to months, and the system displays
24 months.
How to enter interval values with different units of measure:
For the characteristic, the following numerical intervals are allowed:
● 100,00 kg to 1,00 t
● 10,00 mg to 100,00 g
If you want to assign the interval 100,00 kg to 1,00 t as a value, you have to fill the fields on the Classification
NUM Values sheet like this:
Enter the Internal Floating Point Value From and Internal Floating Point Value To values according to the Base
UoM From (ISO) defined in the Characteristic itself (in this case KGM). The Base UoM From (ISO) and Base UoM
To (ISO) fields are filled with the desired Units of Measure in ISO.

Internal Floating Point Internal Floating Point
Value From Value To Base UoM From (ISO) Base UoM To (ISO)
100 1000 KGM TNE
Relational Operators to Define the Intervals
You have the following input options:
● 1 for EQ (Equal)
● 2 for GE LT (Greater than or equal and Less than)
● 3 for GE LE (Greater than or equal and Less than or equal)
● 4 for GT LT (Greater than and Less than)
● 5 for GT LE (Greater than and Less than or equal)
● 6 for LT (Less than)
● 7 for LE (Less than or equal)
● 8 for GT (Greater than)
● 9 for GE (Greater than or equal)
Input example:
● VALUE_FROM: 20
● VALUE_TO: 28
● VALUE_RELATION: 2
Imported value:
● 20≤ X <28
Level Name
1 Batch Basic Data (mandatory)
2 Classification CHAR/BOOL Values
2 Classification NUM Values
2 Classification CURR Values
2 Plant
New Characteristic Value (DATE) and Characteristic Value (TIME) Columns
Starting with SAP S/HANA 1802, you can now enter values for Lower Boundary for Date-Interval and Upper
Boundary for Date-Interval in the new Characteristic Value (DATE) columns and for Lower Boundary for Time-
Interval and Upper Boundary for Time-Interval in the new Characteristic Value (TIME) columns on the
Classification NUM Values sheet in the migration template. Please note that values entered for Internal Floating
Point Value From and Internal Floating Point Value To in the Characteristic Value columns are always given
priority. When you enter values for these fields, values entered for Characteristic Value (DATE) and
Characteristic Value (TIME) will not be considered when migrating.

Tasks

Explorer.
Post-Processing
Transaction MSC3N Display Batch
1.5 Batch (if Batch level is at plant level)
Purpose
Sales and Distribution (SD)
Business Object Definition Batch Master Data if batch is unique at plant level
In Scope
1. Batch basic data

Out of Scope
1. Long texts for batches
Supported Features
● Material Number
● Batch Number
● Plant
● Batch Attributes
● Batch Status
● Control Parameters
Prerequisites

Level Name
1 Batch Basic Data (mandatory)
2 Classification CHAR/BOOL Values
2 Classification NUM Values
2 Classification CURR Values
Class Field on the Batch Basic Data Sheet

Please provide here the batch class to which your material is assigned. All the characteristics with reference to
a table field are then created automatically during migration. Example: Class YB_EXP_DATE_002;
Characteristic LOBM_VFDAT refers to table field MCH1-LFDAT. If the Shelf Life Expira. or Best-Before Date field is
filled, the content will be copied into the classification value of Characteristic LBOM_VFDAT.
VALUE_FROM and VALUE_TO Fields

The values in the VALUE_FROM and VALUE_TO fields always relate to the unit of measurement of the
characteristic.

If the unit of measurement specified here does not equal the unit of measurement of the characteristic, the
output is converted into this unit of measurement.
For example, if the Characteristic has the ISO UOM ANN (Year), and the VALUE_FROM field has the value 2, and
if the UNIT_FROM field has the ISO UOM MON, the two years are converted to months, and the system displays
24 months.
How to enter interval values with different units of measure:
For the characteristic the following numerical intervals are allowed:
● 100,00 kg to 1,00 t
● 10,00 mg to 100,00 g
If you want to assign the interval 100,00 kg to 1,00 t as a value, you have to fill the fields on the Classification
NUM Values sheet like this:
Enter the Internal Floating Point From and Internal Floating Point To values according to the Base UoM From
(ISO) defined in the Characteristic itself (in this case KGM). The Base UoM From (ISO) and Base UoM To (ISO)
fields are filled with the desired Units of Measure in ISO.
Internal Floating Point From Internal Floating Point To Base UoM From (ISO) Base UoM To (ISO)
100 1000 KGM TNE

● 1 for EQ (Equal),
Input example:
● VALUE_FROM: 20
● VALUE_TO: 28
Imported value:
● 20≤ X <28
New Characteristic Value (DATE) and Characteristic Value (TIME) Columns

Starting with SAP S/HANA release 1809, you can now enter values for Lower Boundary for Date-Interval and
Upper Boundary for Date-Interval in the new Characteristic Value (DATE) columns and for Lower Boundary for
Time-Interval and Upper Boundary for Time-Interval in the new Characteristic Value (TIME) columns on the

Classification NUM Values sheet in the migration template. Please note that values entered for Internal Floating
Point Value From and Internal Floating Point Value To in the Characteristic Value columns are always given
priority. When you enter values for these fields, values entered for Characteristic Value (DATE) and
Tasks

Explorer.
Post-Processing
Transaction MSC3N Display Batch
1.6 Material BOM
Purpose
Business Object Component/Area Production Planning and Control (PP)

Business Object Definition Production Planning - BOM
A complete, structured list of the components that make up

an object. The list contains the description, the quantity, and
unit of measure. The components are known as BOM items.
● BOM categories
In the SAP System, BOMs can form different objects
and manage object-related data. You can maintain the
following BOM categories, for example:
○ Material BOM
○ Document structure
○ Equipment BOM
○ Functional location BOM
○ Sales order BOM
● Technical types
To display product variants and production alternatives,
the system provides two technical types:
○ Variant BOM
○ Multiple BOM
In Scope
1. Currently, you can only process one alternative BOM per one material number, plant and BOM usage, but
this can be any number from 01 to 99.
2. Material BOM
3. For object dependency, only the assignment of global dependency is supported, and only the dependency
types Selection condition and Procedure are supported so far.
4. The following Item Categories (Bill of Material) are supported:
○ L-Stock item
○ N-Non-stock item
○ D-Document item
○ R-Variable size item
○ T-Text item
Out of Scope
1. Document structure
2. Equipment BOM
3. Functional location BOM
4. Sales order BOM

Supported Features
● BOM Header
● BOM Items
● BOM Subitems
● Global dependency
● Local dependency
● Description of local dependency
● Source code of local dependency
● Documentation of local dependency
● Document assignment
Prerequisites
In order that the data remains consistent, the user should make sure that the decimal separator used in the file
is the same as the one in user settings, please check the user settings first.
Business objects that reference this object must be created within the validity period that fits this object.
If a successor object is created with a validity period starting before this object, this will normally cause an error
message during the creation or migration of the successor object.
later error messages and inconsistent data on your database.
Level Name
1 BOM Header
(mandatory)
2 BOM Items (man

datory)

Level Name
2 Document assign
ment
3 BOM Subitems
3 Document assign
ment
4 Global depend
ency
4 Local dependency
5 Description of lo
cal dependency
5 Source code of lo

cal dependency
5 Documentation of
local dependency
Quantity Fields on Header and Item Level

If your quantity contains decimals you must not copy and paste values from another Excel file into these fields,
because Excel will corrupt the data type of that field. This would lead to migration of wrong numbers to the
system. Even the Copy value only functionality in Excel will corrupt the data type.
There are three possible options to fill the quantity fields:
1. Enter the data manually into the downloaded migration template.

2. Enter the values into a text file (for example, use the Notepad app), then copy the values from there, and
use Paste special to paste the values into the column of the migration template as Text or Unicode Text.
3. Format all cells in the source Excel file as Text and use Copy values only to copy the values into the
migration template.
Check that the data type of these fields was not changed from String to Number before uploading the XML file
to Migration Cockpit.
Tasks

Explorer.

Post-Processing
Transaction CS03 Display Material BOM
1.7 Characteristic
Purpose
Business Object Component/Area Classification (CA-CL)
Business Object Definition Property for describing and distinguishing between objects,
such as length, color, or weight.
In Scope
Supported Features
● Basic Data
● Descriptions
● Characteristic Allowed Values
● Characteristic Value Descriptions
● Characteristic Additional Data
● Characteristic Restrictions

Prerequisites
● Class [page 39]
Level Name
1 Characteristic Attributes (mandatory)
2 Characteristic Descriptions (manda

tory)
2 Allowed character based values
2 Allowed numerical values
2 Allowed currency based values
2 Descript. for CHAR based values
2 Check table for References
2 Attributes' Additional data
2 Restrictions to Class Types
Valid From
The value of this field can only be inherited from the change number. If the change number is empty, the Valid
from will be ignored.
Build up a Value Hierarchy of Character Values
This functionality is only supported in SAP S/4HANA.
You can build up a value hierarchy for character-based values.

Here is an example for such a value hierarchy:
Level Name
1 EUROPE
2 GERMANY
3 BAVARIA
3 SAARLAND
3 SAXONIA
2 ITALY
3 SICILIA
To build this value hierarchy for a characteristic name COUNTRY you have to fill the fields on the Allowed
character based values sheet like this:
Characteristic Value (long) Value-High (long)
COUNTRY EUROPE
COUNTRY GERMANY EUROPE
COUNTRY BAVARIA GERMANY
COUNTRY SAARLAND GERMANY
COUNTRY ITALY EUROPE
COUNTRY SICILIA ITALY
Build up an Interval with Different Unit of Measure (UoM)

This functionality is only supported in SAP S/4HANA.
You can build up an interval based on different UoMs from the same dimension.
Here is an example of such an interval based on the numerical values:
The Characteristic Attributes field Base Unit of Measure (ISO) is filled with KGM.
On the Allowed NUMmerical values sheet, you want to have the following intervals:
● 100,00 kg to 1,00 t
● 10,00 mg to 100,00 g
To build this value interval you have to fill the fields on the Allowed NUMerical values sheet like this:
Enter the Internal Floating Point Values based on the UoM defined in the Characteristic Attribute sheet. The
Base UoM fields are filled with the wanted UoMs in ISO.
Internal Floating Point Internal Floating Point

Value From Value To Base UoM From (ISO) Base UoM To (ISO)
100 1000 KGM TNE
0.00001 0.1 MGM GRM

New Characteristic Value (DATE) and Characteristic Value (TIME) columns:
Starting with SAP S/HANA 1802, you can now enter values for Lower Boundary for Date-Interval and Upper
Boundary for Date-Interval in the new Characteristic Value (DATE) columns on the Classification NUM Values
sheet in the migration template. The same applies for Lower Boundary for Time-Interval and Upper Boundary
for Time-Interval in the new Characteristic Value (TIME) columns. Please note that values entered for Internal
Floating Point Value From and Internal Floating Point Value To in the Characteristic Value columns are always
given priority. When you enter values for these fields, values entered for Characteristic Value (DATE) and
Document Details
Starting with SAP S/HANA Cloud 1805, the document details in the additional data are supported.
User-Defined Data Type (031)
The userdefined data type is NOT supported in SAP S/4HANA Cloud.
Tasks

Explorer.
Post-Processing
Transaction CT04 Characteristics
1.8 Class

Purpose
Business Object Definition A group of similar objects described by means of character

istics that they have in common.
In Scope
Supported Features
● Basic Data
● Class Description/Keywords
● Long Texts
● Characteristics
● Document Information
● Standards Data
Prerequisites
● Characteristic [page 36]

Level Name
1 General data (mandatory)
2 Description and Keywords (mandatory)
2 Long texts
2 Characteristics
Class Type
All the class types in the system are supported.
Additional Values in the General Data

The additional fields such as Allowed in BOMs, Base unit of measure (ISO format) and Resulting item category
are only effective in class type 200 and 300, so the input value will be ignored in class types 001 and 023.
Documentation
The combination of the field values for Document type, Document number, Document version, and Document
part is checked against the database.
If a document with the combined values is not stored on the database (Table DRAW), the following error
message appears: Document <Document Type>-<Document number>-<Document version>-
<Document part> not found, please check the values.
Tasks

Explorer.
Post-Processing
Transaction CL01 Create Class
Transaction CL02 Classes
Transaction CL03 Display Class

1.9 Class hierarchy
Purpose
Business Object Definition The classes used to define a multi-level search path.
The initial class has subordinate classes assigned to it, and

you can restrict the search systematically by choosing the
appropriate subordinate class.
Example: Class VEHICLES has the subordinate classes

CARS and TRUCKS. Class CARS has the subordinate classes
SPORTSCARS, STATION_WAGONS, and SEDANS. When you
are looking for a particular car, you can restrict the search
down the hierarchy levels as appropriate.
In Scope
1. Assign class
Out of Scope
1. Assign object (e.g. material, functional location, equipment, vendor...)

Supported Features
● Header
● Class Hierarchy
Prerequisites
● Class [page 39]
Level Name
1 Header (mandatory)
2 Class Hierarchy (mandatory)
Instance class
The instance is the only class without a superior class.
Parent class name

The parent class name contains the class name to which you want to assign the class in child class name.
Child class name

The child class name is the subordinate class of the parent class name.
Each class in the Child class name field also occurs in the parent class name field.
Each class in the Child class name field has exactly one entry without the Link indicator.

If you have a child class without subordinate classes, then this child class name must have an entry in the
parent class name field with an empty child class name field. For example, Class5 is used as a child class
name, and if this class is without a subordinate class, then we must have a new entry in this format:
Input example:
● Instance class name: Class1

● Parent class name: Class5
● Child class name: (empty)
● Level of a hierarchy node: 4 (The value must higher than the level of its parent/superior class)
Hierarchy level
The hierarchy levels (Level) can be anything you like, but we recommend assigning level 1 to the instance, level
2 to its immediate subordinate classes, and so on. The hierarchy level of each class is higher than the level of its
superior class (the one without the Link indicator).
Description (optional)
The field has no function and will be not migrated.
You can enter some comments here to have a better overview of the class hierarchy.
General flag (Link)
When a class is assigned to a second superior class, this field must contain X in the first entry.
Example:Class5 has two superior classes, this means we have two entries which Child class name is Class5,
the link must be set to X in the first entry.
Input:
Instance class name Parent class name Child class name Level Link
Class1 Class1 Class2 1
Class1 Class3 Class5 2 X
Class1 Class5 4
Classification status (optional)
Defines whether the allocation is released for class search, or locked.
Left class name (optional)
Specifies the class name which is is on the left side of child class name.
Right class name (optional)
Specifies the class name which on the right side of child class name.

Tasks

Explorer.
Post-Processing
Transaction CL24N Class Assignments
Transaction CL6C Class Hierarchy
Further Information
● Information about the used API: SAP Note 1350546

● Information for classification: SAP Note 2267878
1.10 Object classification
Purpose
Business Object Definition The assignment of objects to a class.
When you assign objects to a class, you assign values for the
object to the characteristics in that class.

In Scope
1. Assign material classes (assign material class name and characteristic values):
1. Class type Material (001) is supported.
2. Class type Equipment (002) is supported.
3. Class type Functional Location (003) is supported.
4. Class type Vendor Class (010) is supported.
5. Class type Customer Class (011) is supported.
6. Class type Message Item Class (015) is supported.
7. Class type Document Management (017) is supported.
8. Class type Work Center Class (019) is supported.
9. Class type Batch (022 and 023) is supported.
10. Class type Maintenance Plan (080) is supported.
11. Class type Material - Configurable Objects (200) is supported.
12. Class type Variants (300) is supported.
Out of Scope
1. Batch classes will be assigned via the Batch (if Batch is unique at material level) [page 25] migration
object.
Supported Features
● Basic Data
● Characteristic Values (only for material classification)
● Change Number
Prerequisites
● Characteristic [page 36] (dependent on class type)

● Class [page 39] (dependent on class type)
● Material [page 162] (dependent on class type)
● PM - Equipment [page 95] (dependent on class type)
● PM - Functional location [page 108] (dependent on class type)
● Supplier [page 238] (dependent on class type)

● Customer [page 75] (dependent on class type)
● Document info record (manually, dependent on class type)
● Work center/Resource [page 244] (dependent on class type)
Level Name
1 Header data (mandatory)
2 Numerical value allocation
2 Currency value allocation
2 Character value allocation
Material Classification for Batches

Batches are classified via the Batch (if Batch is unique at material level) [page 25] migration object, but you
need to assign the batch class to the material with this object first. To assign the batch class, the source file
must only contain the Header Data sheet and you then fill the following fields:
● Class Type: 023

● Class Name: <Class Name>
● Object Key: <Material number> to assign to the batch related class
● Status: 1
● Valid from date: (optional) <valid from date> (system date if not filled)
● Value Allocation sheets must not be maintained in this case!
Material Classification
To assign class and characteristic values to material, the source file must contain the Header Data sheet and
the Value Allocation sheets:
● On the Header Data sheet, fill the following fields:

● Class Type: 001
● Class Name: <Material Class Name> (Technical Name)

● Object Key: <Material number> to assign the material related class
● Status: 1
● On the Value Allocation sheets, make the necessary entries.
Material - Configurable Objects Classification

To assign class and characteristic values to materialconfigurable objects, the source file must contain the
Header Data sheet and the Value Allocation sheets. On the Header Data sheet, fill the following fields:
● Class Type: 200

● Class Name: <Material - configurable objects Class Name> (Technical Name)
● Object Key: <Material number> to assign the material - configurable objects related class
● Status: 1
● On the Value Allocation sheets, make the necessary entries.
Variants Classification
To assign class and characteristic values to variants, the source file must contain the Header Data sheet and
the Value Allocation sheets. On the Header Data sheet, fill the following fields:
● Class Type: 300

● Class Name: <Variants Class Name> (Technical Name)
● Object Key: <Material number> to assign the variants related class
● Status: 1
● If you want to use a domain restriction value that is different from the characteristic master, you can enter
the characteristic values. Make the necessary entries on the Value Allocation sheets.
Equipment Classification
To assign class and characteristic values to equipment, the source file must contain the Header Data sheet and
● Class Type: 002

● Class Name: <Equipment Class Name> (Technical Name)
● Object Key: <Equipment number> to assign the variants related class
● Status: 1
the characteristic values. Make the necessary entries on the Value Allocation sheet.
Functional Location Classification

To assign class and characteristic values to functional location, the source file must contain the Header Data
sheet and the Value Allocation sheets. On the Header Data sheet, fill the following fields:
● Class Type: 003

● Class Name: <Functional location Class Name> (Technical Name)
● Object Key: <Functional location> to assign the variants related class

● Status: 1
Vendor Class
To assign class and characteristic values to vendor, the source file must contain the Header Data sheet and the
Value Allocation sheets. On the Header Data sheet, fill the following fields:
● Class Type: 010

● Class Name: <Vendor Class Name> (Technical Name)
● Object Key: <Vendor> to assign the variants related class
● Status: 1
Message Item Class (on-premise only)

To assign class and characteristic values to a message item, the source file must contain the Header Data sheet
and the Value Allocation sheets. On the Header Data sheet, fill the following fields:
● Class Type: 015

● Class Name: <Message Item Class Name> (Technical Name)
● Object Key: concatenate < Notification Number (char(12)) & Item Number in Item Record
(char(4)> with leading zero to assign the variants related class
● Status: 1
Maintenance Plan Class

To assign class and characteristic values to maintenance plan, the source file must contain the Header Data
sheet and the Value Allocation sheets. On the Header Data sheet, fill the following fields:
● Class Type: 080

● Class Name: <Maintenance Plan Class Name> (Technical Name)
● Object Key: <Maintenance Plan> to assign the variants related class
● Status: 1
Customer Class
To assign class and characteristic values to customer, the source file must contain the Header Data sheet and
● Class Type: 011

● Class Name: <Customer Class Name> (Technical Name)

● Object Key: <Customer> to assign the variants related class
● Status: 1
Document Management Class

To assign class and characteristic values to document, the source file must contain the Header Data sheet and
● Class Type: 017

● Class Name: <Document Class Name> (Technical Name)
● Object Key: <Document Info Record key> in concatenated form, which is to concatenate: Document
Type, Document number (with leading 0), Document Version and Document Part, to assign the variants
related class
● Status: 1
Work Center Class

To assign class and characteristic values to work center, the source file must contain the Header Data sheet
and the Value Allocation sheets. On the Header Data sheet, fill the following fields:
● Class Type: 019

● Class Name: <Work Center Class Name> (Technical Name)
● Object Key: concatenate < Plant & Work Center> to assign the variants related class
● Status: 1
Value From and Value To Fields

The values in the Value From and Value To fields always relate to the unit of measurement of the characteristic.
For example, if the unit of measurement of the characteristic is ISO UOM ANN (Year), 2 means two years. The
system ignores units in the Base unit of measure From (ISO Format) field and the Base unit of measure To (ISO
Format) field here. These are only displayed later.

● 1 for EQ (Equal)

Input example:
● VALUE_FROM: 20
● VALUE_TO: 28
Imported value:
● 20≤ X <28

If the unit of measurement value specified here in the classification does not equal the unit of measurement
value of the characteristic, the output is converted into the classification's unit of measurement.
For example, if the characteristic has the ISO UOM ANN (Year), and the VALUE_FROM field has the value 2, and
if the UNIT_FROM field has the ISO UOM MON, then the two years are converted to months, and the system
displays 24 months.
Character-Type Characteristic Values

You can enter values in the Characteristic Value Neutral field. Be aware of using values, that match the format
and domain specification of the characteristic.
The Instance counter field has been removed from SAP S/HANA release 1802, because this field is used in the
userdefined data type, and not supported in SAP S/4HANA, for more details please see SAP Note 2267878 .
Example
● Class Type: 001

● Class Name: MAT_HIER_1
● Object Key: FG29
● Characteristic Name: MAT_C_HIER_1
You have a hierarchy definition like this:
Level Neutral Value
1 AB_Root_Level_1
2 A_First_Level_2
3 A_Second_Level_3
2 B_First_Level_2
If you want to assign A_Second_Level_3, you must fill the entries of the Character value allocations structure as
follows:
1. Fill the key fields as described above.

2. Item number: 001
If you have to set more values for the same characteristic, increase the number by 1.
3. Characteristic Value Neutral Long: A_Second_Level_3.

New Characteristic Value (DATE) and Characteristic Value (TIME) columns:
Starting with SAP S/HANA release 1802, you can now enter values for Lower Boundary for Date-Interval and
Upper Boundary for Date-Interval in the new Characteristic Value (DATE) columns on the Classification NUM
Values sheet in the migration template. The same applies for Lower Boundary for Time-Interval and Upper
Boundary for Time-Interval in the new Characteristic Value (TIME) columns. Please note that values entered for
Internal Floating Point Value From and Internal Floating Point Value To in the Characteristic Value columns are
always given priority. When you enter values for these fields, values entered for Characteristic Value (DATE) and
Tasks

Explorer.
Post-Processing
Transaction CL24N Assigning Objects or Classes to Class
(Choose Class Class Type view)
Further Information
● For import information for classification see SAP Note 2267878
1.11 Condition contract

Purpose
Business Object Component/Area Condition Contract Settlement (LO-GT-CCS)
Business Object Definition Serves as an agreement between dedicated business part

ners like Customers or Suppliers, and contains conditional
information as well as settlement-related information such
as settlement dates etc. Completed integration into pricing,
to determine which conditions are relevant for posting to
FI/CO (Accruals), is the basis on which to create a contract-
based settlement document.
In Scope
Supported Features
● Condition Contract Header

● Header Texts
● Condition Structure Fields
● Item Condition
● Condition Scale
● Business Volume Base
● Calendar Data
● Eligible Partners
● Texts for Eligible Partners
Prerequisites

● Customer [page 75]
● Organizational Data such as company code, sales area, or purchasing org.

Condition Contract Header
The Condition Contract Header structure contains the business partner, the condition contract type, a validity
interval, the document status, currency information, exchange rate, terms of payment, purchasing
organization and sales area.
Header Texts
The Header Texts structure contains the different text objects which are stored on header level of the condition
contract.
Condition Structure Fields
The Condition Structure fields contain the corresponding condition-table-related information. The table
number, the condition type, the validity of the condition , the order key and the condition table key fields must
be specified. The order key, which is defined here for the condition structure, must be used consistently if you
define the item conditions and the condition scale settings.
Item Condition
The Item Condition structure contains the corresponding fields which define the condition such as the amount,
calculation type or currency. The order key must be part of the condition structure field table.
Condition Scale
The Condition Scale contains the corresponding fields which define the condition scales. The order key must
be part of the condition structure field table.
Business Volume Base
The Business Volume Base structure contains the business volume selection criteria. You must specify the
order key, the field combination, the include/exclude indicator and selection fields related to a field
combination.
Settlement Dates
The Settlement Dates structure contains the settlement dates for the different types of settlement (delta
accruals, partial, final, delta, and accruals deferral settlement). You must specify the order key, the settlement
date type, and the settlement date as a minimal data set. All other fields are optional.
Eligible Partners
The Eligible Partners structure contains the eligible partners for the condition contract. You must specify the
order key and an eligible partner as a minimal data set. All other fields are optional. You cannot pass data for
different eligible partner types at the same time.
Texts for Eligible Partners
The Eligible Partner Texts structure contains the different text objects which are stored on the level of the
eligible partner. The order key is used to link the text and the eligible partner entry.

Level Name
1 Condition Contract Header

(mandatory)
2 Header Texts (optional)
2 Condition Structure Fields

(optional)
2 Item Condition (optional)
2 Condition Scale (optional)
2 Business Volume Base (op

tional)
2 Settlement Dates (optional)
2 Eligible Partners (optional)
3 Texts for Eligible Partners

(optional)
Tasks

Explorer.
Post-Processing
Transaction WCOCO Process Condition Contract
1.12 Condition record for pricing (general template)

 Tip
This is the most complex and comprehensive object to migrate condition records for pricing. There are also
tailored migration objects available with limited number of available key fields : Condition record for pricing
in sales [page 219] or Condition record for pricing in purchasing [page 173].
Purpose
Business Object Component/Area Price conditions for sales and purchasing.
During pricing, the system automatically transfers pricing

data from the price conditions, for example in Sales and Dis
tribution. Prices, surcharges and discounts are determined
in sales and billing documents.
Business Object Definition The term pricing is broadly used to describe the calculation
of prices (for external use by customers or vendors). Condi
tions represent a set of circumstances that apply when a
price is calculated.
In Scope
The following condition records are supported (including scales if applicable):
1. Prices
2. Discounts
3. Surcharges
Out of Scope
All condtions that are not white-listed; for further information, please refer SAP Note 2332748 .
Supported Features
All structures/features are supported.

Prerequisites

Level Name
1 Sales condition records (mandatory)
2 Key fields for Conditions (mandatory)
2 Scales
For more information on how to fill the condition keys, please refer to SAP Note 2332748 .
Tasks

Explorer.
Post-Processing
Transaction VK13 Price Conditions
Transaction MEK3 Display Conditions (Purchasing)

Examples
Example of a Quantity-Based Scale:
Scale quantity Scale unit of measure Scale rate Scale currency
1,000 EA 100,00000 EUR
100,000 EA 90,00000 EUR
Example of a Scale based on Gross Weight:
1,000 KG 100,00000 EUR
100,000 KG 90,00000 EUR
Example of a Value Scale:
Scale value Scale currency Scale percentage
100,000000 EUR 5,000000
1000,000000 EUR 10,000000
1.13 VC - Configuration profile
Purpose
Business Object Component/Area Variant Configuration (LO-VC)
Business Object Definition An object in which you enter configuration parameters for a
configurable object. Each Material must be assigned to at
least one class with a class type that supports variant config
uration.

In Scope
Supported Features
● Attributes
● Global dependencies
● Basic data of local dependency
● Descriptions of dependency
● Documentations of dependency
Prerequisites

● Object classification [page 45]
● Change number (optional)
Level Name
1 Attributes (mandatory)
2 Global dependencies (op

tional)
2 Basic data of local depend

ency (optional)
3 Descriptions of dependency
(optional)
3 Documentations of depend
ency (optional)
Detailed Mapping Instructions

● Attributes
Configuration profile name must be unique.

● Global Dependencies
Maintain global dependencies of configuration profile.
● Basic Data of Local Dependency
Maintain local dependencies of configuration profile. Maintain a source code in one line (string), for each
local dependency.
 Note
Local dependencies with syntax errors in the source code cannot be loaded. In the case of syntax
errors, an error message will be displayed and the configuration profile will be skipped for migration.
● Descriptions of Dependency
Enter a local dependency description, one in each language.
 Note
The Descriptions of dependency sheet, should contain at least one description per local dependency.
Otherwise, an error message, Maintain at least one description for the dependency, will
be raised.
● Documentation of Dependency
Enter a local dependency documentation, one in each language.
 Note
Documentation cannot be maintained without description in the corresponding language.
Tasks

Explorer.
Post-Processing
Transaction PMEVC Variant Configuration Modeling Envmt
Transaction CU43 Display Configuration Profile

1.14 Consent
Purpose
Business Object Component/Area Consent (CA-GTF-CON)
Business Object Type Consent Record
Business Object Definition Consent is an assent given by the data subject that allows
lawful processing of their personal data. It facilitates proving
legality and ensures the correct processing of personal data
according to the purpose for which it was given.
In Scope
1. Initial load of Consent Records and the corresponding texts

2. Delta load of Consent Records and the corresponding texts
Supported Features
● Consent
● Consent Text
Level Name
1 Consent (mandatory)
2 Consent text (mandatory)

Tasks

Explorer.
Post-Processing
Transaction CM_DISPLAY_CONSENT Search and Display Consent Records
1.15 Purchase contract
Purpose
Business Object Component/Area Purchasing (MM-PUR)
Business Object Definition A form of longer-term purchase agreement against which

materials or services are released (ordered, or called off), ac
cording to need, over a certain predefined period.
You can migrate two different types of purchase contracts:
● Quantity Contract
● Value Contract
In Scope

1. Header Data
2. Vendor Address
3. Header Texts
4. Item Data
 Note
Only the Standard item category is supported
5. Delivery Addresses
6. Account Assignment
 Note
The following Account Assignment Categories are supported:

○ Cost Center
○ Asset
○ WBS Element
7. Item Texts
Out of Scope
1. Master conditions:
During the creation of outline agreements, you can specify just one time period per variable key. This
means that you can specify a period for the document header (that is, condition table A019), for each item
(that is, condition table A016), and for each item/plant combination (that is, condition table A068).
 Note
If there's an info record already, the price will be taken over from this info record.
2. Scales are not supported during the creation of outline agreements.

3. Volume rebate conditions in outline agreements are not taken into account.
4. No sub items (for example inclusive/exclusive bonus quantity, display, and so on) are taken into account.
5. The control key for quantity management in procurement (EKPO-SSQSS), and the certificate category
(EKPO-ZGTYP) are only taken into account to a certain extent: This information is copied from the
reference contract or the material master record, but can't be changed and no checks are carried out for
these two fields.
6. The revision level (EKPO-REVLV) is not changeable because various quality management routines haven't
been implemented.
7. Version management (document change management) is not supported.
8. External services (planned and unplanned services) are not supported.
9. Creation of configurations is not supported.
10. The following Item Categories are not supported:
○ Third-Party
○ Enhanced Limits
○ Consignment

○ Subcontracting
Supported Features
● Header Data
● Supplier Address
● Header Texts
● Item Data
● Delivery Addresses
● Account Assignment
● Item Texts
Prerequisites
The following objects/data must have already been maintained or migrated:

● WBS element
● Fixed asset (incl. balances and transactions) [page 98]
● G/L account [page 114] (expense account used in account assignment category)
● Purchasing info record with conditions [page 202] (if conditions should be taken over)
● During migration you can choose between internal and external number assignment for the purchasing
document. Item numbers will be migrated 1:1 from the migration template into the data.
● Net Price:Please provide the price as manual price on item level, additional conditions are not supported. If
a purchasing info record for an item already exists, the conditions (inclusive scales) will be taken over from
this info record. You have to take care and check that the conditions validity period matches with the
stipulated validity period of the agreement.
Level Name
1 Header Data (mandatory)
2 Supplier Address

Level Name
2 Header Texts
2 Item Data (mandatory)
3 Delivery Address
3 Account Assignment
3 Item Texts
Tasks

Explorer.
Post-Processing
Transaction ME33K Display Contract
Transaction ME3L Purchasing Documents per Supplier
Transaction ME3K Purchasing Documents per Supplier (General)
1.16 Customer - extend existing record by new org levels
Purpose
Business Object Component/Area Logistics - General (LO-MD-BP, LO-MD-BP-CM)

Business Object Definition A customer is a business partner with whom a business rela
tionship exists, involving the issue of goods or services. The
customer orders goods from the company, and is one of the
most commonly used master data objects, used by almost
all business applications.
At SAP, there are different object models for the customer. In

the traditional SAP ERP system, customer master data is
used. In all new strategic applications, such as SAP CRM,
SAP SRM and many industry solutions, the business partner
approach is used.
In Scope
1. General data (only fields which might become relevant when you extend a supplier/contract partner as
customer)
2. BP Roles
3. Additional addresses
4. Company data including dunning
5. Contact persons
6. Bank data
7. Sales data including sales partner functions
8. Tax numbers
9. Long texts
10. Industry assignments
11. Identification numbers
12. Contact person
Out of Scope
1. No updates of existing fields/records are possible.

2. Sales partners can only be updated together with the related sales data. It is not possible to extend a sales
partner for an existing sales area. The same holds true for sales text data and company text data. Extend
already existing customers with new org levels and extend already existing suppliers/contract partners as
customer with the same number
 Note
This migration object is based on the assumption that business partner and customer are using the same
partner ID. If you have customized your system in a different way, you must adjust the migration object. For
support please reach out to us.

Supported Features
Prerequisites

● If you want to extend already existing suppliers as customer with the same number:
○ Supplier [page 238]
● On the General Data sheet, we offer fields which only become relevant when you extend already existing
suppliers/contract partners as customer with the same number.
● If you want to extend an existing supplier or contract partner as customer with the same number, you have
to fill out either the supplier number or contract partner. It's not possible to provide both fields. If you want
to extend an already existing customer by new org levels, you have to leave the reference numbers empty.
● Please consider: You can't transfer a value in one of the fields provided on the General Data sheet when the
customer already exists.
Level Name
1 General Data (mandatory)
2 Additional Addresses
2 General Texts
2 Sales Data
3 Sales Partner
3 Sales Organization Texts
2 Company Data
3 Company Texts
2 Bank Data
2 Industries
2 Tax Classifications
2 Tax Numbers

Level Name
2 Identification Numbers
2 Contact Person
Dunning Data in On-Premise Version

Dunning data is included in the Company Data sheet. This dunning data does not contain the Dunning Area
field. If a dunning area is needed, you need to adjust the mapping in your project with the SAP S/4HANA data
migration modeler (Transaction LTMOM), create a new structure and maintain the field mapping for this sheet.
Tasks

Explorer.
Post-Processing
Transaction BP Maintain Business Partner
1.17 Customer - extend existing record by Thailand branch code
Purpose
Business Object Component/Area LO-MD-BP
Business Object Type Master Data

Business Object Definition A business partner may have many branches depending on
the various locations from where they operate from. A
branch code is a 4-digit or a 5-digit code assigned by the
Revenue Department in Thailand to uniquely identify each
branch of a business partner. In any case, the head office
branch carries a branch code of 00000 or 0000.
In Scope
1. Branch codes with address information.
Out of Scope
1. More than one address.

2. International address versions.
Supported Features
● All structures/features are supported.
Prerequisites
● The customer master data needs to be migrated as a prerequisite with the Thailand company code
assigned.
● Only one branch code can be marked as default branch code. If only one branch code is assigned, it will be
marked as default automatically.
● If branch codes are already assigned to the customer, additional branch codes can only be uploaded
without a default indicator.

● As the standard method for communication (part of the address information), only the following values are
supported: Fax, E-Mail and Telephone.
Level Name
1 Thailand branch code
Tasks

Explorer.
Post-Processing
1.18 Customer - extend existing record by Credit Management

data
Purpose


approach is used.
In Scope
1. Credit management profile data

2. Credit management segment data
Out of Scope
1. No updates of existing fields/records are possible.

2. Segment data can only be loaded together with the profile data. It is not possible to add profile data if
segment data is already loaded.
 Note
Supported Features

Prerequisites
 Note
If you submit a credit limit amount, the amount value will be stored in the Requested field on the Credit
Limit tab. This is the standard behavior when maintaining the credit limit for a business partner. The reason
for this is the configuration of the system: A credit limit change triggers the Change to Credit Limit
Requested event with the LIMIT_REQ follow-on process. This also happens during migration, because the
same save mechanism is applied. We recommend to turn off the event during migration. If the event is
turned off, the credit limit is stored directly in the target field. To turn off the event, proceed as follows:
1. In Customizing, navigate to Financial Supply Chain Management Credit Management Credit Risk
Monitoring Processes .
2. Execute Define Events and Follow-On Processes.
3. In the Dialog Structure pane on the left, open Events Follow-On Processes .
4. Remove the LIMIT_REQ follow-on process for the Change to Credit Limit Requested event.
Level Name
1 Credit MD for Partner (Profile)
2 Credit MD for Partner (Segment)
Tasks

Explorer.

Post-Processing
1.19 Customer Material
Purpose
Business Object Component/Area SD-MD-AM-CMI
Business Object Definition Customerspecific information about a sales material is

stored in a customer material.
In Scope
Supported Features
● General Data
● CustMat Text
● CustMat Classsification
● CustMat Classsif Numbers
● CustMat Classsif Characteristic
● CustMat Classsif Currency

Prerequisites
● Class [page 39]

● Sales Area
Level Name
2 CustMat Text
2 CustMat Classification
3 CustMat Classif Numbers
3 CustMat Classif Characteris

tic
3 CustMat Classif Currency
Please refer to the tooltips field of the template file for further information.
Tasks

Explorer.
Post-Processing
Transaction VD51 Create Customer-Material Info record

Transaction VD52 Change Customer-Material Info record
Transaction VD53 Display Customer-Material Info record
1.20 Customer
 Tip
For this migration object, the Custom Fields and Logic app is available. If you enhance your business object
with custom fields in the app, these custom fields will automatically be reflected in the XML template of the
corresponding migration object. See SAP Note 2726010 for further details.
Every time you add, change or delete a custom field, the migration project must be updated and a new
migration XML template must be downloaded and used. Thus, if custom fields are added or changed by an
application expert during migration testing, this must be communicated to and coordinated with your data
migration team. Also see the Extensibility section in the SAP S/4HANA Cloud documentation.
Purpose

approach is used.
In Scope

1. Basic data with standard address data
2. BP Roles
4. Company data including dunning
5. Contact persons
6. Bank data
7. Sales data including sales partner functions
8. Tax numbers
9. Long texts
10. Industry assignments
12. Contact person
Out of Scope
1. Relationship to other business partners

2. Customer and Supplier are two separate business partners. Therefore, they have two different numbers.
With the Supplier - extend existing record by new org levels object, you can create a supplier with the same
customer number.
3. Time-dependency of addresses
4. Time-dependency of bank data
 Note
Supported Features
● General Data
● BP Roles
● Additional Addresses
● General Texts
● Sales Data
● Sales Partner
● Sales Organization Texts
● Company Data
● Withholding Tax Data
● Company Texts
● Bank Details

● Payment Card Data
● Industries
● Tax Classifications
● Tax Numbers
● Identification Numbers
● Contact Persons
Prerequisites
 Note
The Customer Account Group field must be in sync with your customizing of the BU grouping. Otherwise,
the grouping will overwrite the account group.
● Bank [page 24]
● The mandatory partner functions will be created automatically with the same customer number.
In the UI, the partner function is displayed language-dependent. For data migration you have to maintain
the language-independent database value. See the following example:
English Migration
SP AG
SH WE
PY RG
BP RE
ER ZM
For further information see SAP Note 2609888 .
● It is possible to assign more than one address to a customer. The address data from the General Data sheet
is always the standard address. If you assign only one address to a customer it is not necessary to provide
an external address number. If you provide additional addresses, the external address number is
mandatory. The external address number must be unique for each customer. You can use the same
external address number for different business partners.
● During migration, you can choose between internal and external number assignment for new customers.
● Assigned contact person will always get an internal number for the new business.
● With the BP Grouping field on the General Data sheet, you arrange the different number ranges (internal or
external) and the customer account group. It is possible to create customers and one-time customers.
● If a business partner needs to be created with both customer and supplier roles, this can be achieved in a
two-step approach. You can extend a customer that has already been migrated, with the Supplier - extend

existing record by new org levels [page 232] (Supplier- extend existing record by new org levels) object to
add the appropriate supplier data.
● If the Customer ID is to be used for integration with external systems, it can be activated during migration.
At the same time, you must also maintain the Business System ID of your source system (to be used for
integration) using the Convert Values step to ensure that the key mapping is added to the central key
mapping store of the SAP S/4HANA system.
Level Name
2 General Texts
2 Sales Data
3 Sales Partner
3 Sales Organization Texts
2 Company Data
3 Company Texts
2 Bank Data
2 Industries
2 Tax Classifications
2 Tax Numbers
2 Contact Person
Contact Person ID
You must enter a contact person ID in the respective field on the Contact person sheet. This number is required
for internal data processing. However, during processing, a new business partner will be created with an
internal number. This business partner is automatically assigned to the customer with the corresponding
relationship.
Dunning Data in the On-Premise Version

Dunning data is included in the Company Data sheet. This dunning data does not contain the Dunning Area
field. If a dunning area is needed, you can use the Dunning Data sheet. Please note that this sheet is not used in
the standard shipment. You need to adjust the mapping in your project with the SAP S/4HANA Data migration
modeler (Transaction LTMOM) and create the structure and field mapping for this sheet.
Tax Jurisdiction Code Determination via Vertex

If Vertex is activated (especially on US installations) the tax jurisdiction code will be determined by the address.
If Vertex determines more than one tax jurisdiction code for one record, the migration of this record will fail. If
this happens, you must provide a more detailed/accurate address: for example US Postal codes with 9 digits
instead of 5 digits.
The more detailed and accurate an address, the more accurately Vertex will be determine the tax jurisdiction
code.

For some addresses, Vertex will always provide more than one tax jurisdiction code. If that's the case you must
maintain this record manually or provide a correct tax jurisdiction code within the template.
In the Suppress Tax Jurisdiction Code check field on the General Data sheet, you can suppress the check and
the automatic determination of the Tax Jurisdiction Code for each record.
Tasks

Explorer.
Post-Processing
Further Information
● SAP Note 2726010 – Migration Cockpit: Support of custom fields (in-App extensibility)
● SAP Note 2609888 – Mandatory partner function SP is missing for sales area
1.21 Document info record
Purpose
Business Object Component/Area Document Management (CA-DMS)

Business Object Definition This fact sheet gives the information associated with a docu
ment that has been created in the Document Management
System. A document is a carrier of information. This infor
mation is either for the user/person responsible or for ex
changing between systems. A document contains informa
tion that can be stored and it can take many different forms
(such as technical drawings, graphics, programs, or text).
When complete, this information gives a full description of
an object. We use the term document info record to refer to
the master record in the SAP System that stores all the busi
ness information for a document. While the document info
record contains the metadata for a document (such as the
storage location), the original file (for example, the design
drawing) contains the actual information in the document.
In Scope
Supported Features
● Document Data
● Object Links
● Descriptions
● Long Text
Prerequisites
● Document info record (to create a Document Info Record with reference)
● Various Business Objects (to link to the Document Info Record)
● Document types (to link to the Document Info Record)

Level Name
1 Document Data (mandatory)
2 Object Links
2 Descriptions
2 Long Text
Document Data
Document Number, Document Type, Version, and Part must be unique.
In order to create a Document Info Record (DIR) with a reference, create the referenced DIR as an initial step
and use the SAP S/4HANA Document Number, Document Part, and Version in the reference fields.
Object Links
Maintain the SAP S/4HANA Object Type and Object Key. These refer to the SAP S/4HANA objects as defined in
the Business Object Repository. For example, an Equipment in SAP S/4HANA can be defined as Object Type:
EQUI and Object Key: 000000000123456781.
Descriptions
In this view, you can maintain additional descriptions (for languages other than those provided on the
Document Data sheet).
If the description is more than 40 characters long, provide up to 40 characters in the Description sheet and
provide the full text as long text.
Long Text
The long text is an extension to the description. If the description is more than 40 characters long, provide up
to 40 characters in the Description sheet and provide the full text as long text. If the initial 40 characters of a
long text are not a part of the Description sheet, the description will be overwritten by the long text.
The long text will be ignored if the length is less than or equal to 40 characters. The long text will not be
migrated if there is no description in the respective language.
Tasks

Explorer.

Post-Processing
Transaction CV03N Display document
1.22 PM - Measuring point
Purpose
Business Object Component/Area PM-EQM-SF-MPC
Business Object Definition Measuring points in the SAP System describe the physical
and/or logical locations at which a condition is described.
For example, the coolant temperature in a nuclear power

station after the coolant has left the pressure vessel, or the
number of revolutions at a rotor shaft of a wind-driven power
plant.
In plant maintenance, measuring points are located on tech

nical objects, in other words, on pieces of equipment or
functional locations.
In Scope
Out of Scope
1. Measurement reading transfer is not supported.

Supported Features
● Header
Prerequisites
● PM - Equipment [page 95]

● PM - Functional location [page 108]
● QM/PM - Catalog code group/code [page 208]
● Only internal numbering is supported.

● If measuring point is a counter, the Counter Data group needs to be filled
● If measuring point is NOT a counter, the Target Value group needs to be filled
● Bear in mind the following rules:
○ If you want to enter quantitative measurement results for the measuring point, you must assign a
numerical characteristic to it with the required unit.
○ If you want to enter qualitative measurement results for the measuring point, you must assign the
required code group to it.
○ If the entry of qualitative measurement results in the form of an evaluation code being sufficient for a
measuring point, you do not need to enter any characteristics for the measuring point. You just specify
one code group and select the ValCode sufficient field.
○ If you want, you can assign both a characteristic and a code group to a measuring point.
Level Name
Tasks

Explorer.

Post-Processing
Transaction IK03 Display Measuring Point
1.23 PM - Maintenance notification
Purpose
Business Object Component/Area PM
Business Object Definition Maintenance notification
Describes the malfunctions or exceptional technical situa

tions of an object in the area of maintenance processing, re
quests the maintenance department to perform a necessary
task, and documents the work that has been performed.
Maintenance notification is the means by which company
notifications are created and managed in the area of plant
maintenance. There are three different types of notifications:
● Maintenance request (M1)

● Malfunction report (M2)
● Activity report (M3)
In Scope
1. All kinds of maintenance notification are supported.

2. Notification Partner is ONLY supported for notification types: M2 and M3

Out of Scope
1. Documents
2. Location Data - Address
3. Location Data - Production Work Center
4. Location Data - Plant Section
5. Location Data - Current Location
6. Assignment of Task List
7. Breakdown Duration
8. Organizational Data
9. Activities - Quantity
10. Causes - Root Cause
Supported Features
● Notification Header
● Notification Item
● Notification Item Cause
● Notification Item Activity
● Notification Item Task
● Notification Activity
● Notification Task
● Notification Partner
Prerequisites

● Assembly via Material [page 162]
● Work center/Resource [page 244]

Level Name
1 Notification Header (manda

tory)
2 Notification Item
3 Notification Item Cause
3 Notification Item Activity
3 Notification Item Task
2 Notification Activity
2 Notification Task
2 Notification Partner
Tasks

Explorer.
Post-Processing
Transaction IW21 Create PM Notification
Transaction IW22 Change PM Notification
Transaction IW23 Display PM Notification
1.24 PSS - Raw material compliance info

Purpose
Business Object Component/Area Sustainability Foundation (EHS-SUS-FND)
Business Object Definition Chemical compliance information is used to manage compli

ance information centrally and satisfy legal and customer re
quirements.
In Scope
Out of Scope
1. Attachments
Supported Features
● Chemical Compliance View

● Chemical Composition
● Chemical Component
● Material Assignment
● Bulk Assignment
● Purpose Assignment
● Supplier Material Assignment
Prerequisites

● PSS - Substance [page 228]

Level Name
1 Chemical compliance view

(mandatory)
2 Chemical composition
3 Chemical component
2 Material assignment
2 Bulk assignment
2 Purpose assignment
2 Supplier material assignment
Preparation Migration Details for Raw Materials
Process the migration in two steps as follows:
1. Migrate bulk raw materials using the following data from the migration template:
○ Chemical compliance view
○ Chemical composition
○ Chemical component (substances)
○ Material assignment
○ Purpose assignment
○ Supplier material assignment
2. Migrate packaged products related to the raw materials using the migration template:
○ Bulk assignment
Tasks

Explorer.

1.25 PSS - Product compliance info
Purpose
Business Object Definition Chemical compliance information is used to manage compli

ance information centrally and satisfy legal and customer re
quirements.
In Scope
Out of Scope
1. Attachments
Supported Features
● Chemical Compliance View

● Chemical Composition
● Chemical Component
● Application
● Material Assignment
● Market Coverage
● Market Request
● Bulk Assignment
● Purpose Assignment

Prerequisites

● PSS - Substance [page 228]
● PSS - Raw material compliance info [page 86]
Level Name
1 Chemical compliance view

(mandatory)
2 Chemical composition
3 Chemical component
2 Application
2 Material assignment
2 Market coverage
2 Market request
2 Bulk assignment
2 Purpose assignment
Preparation Migration Details for Products
Process the migration in two steps as follows:
1. Migrate bulk product using the following data from the migration template:
○ Chemical composition
○ Chemical component (substances or raw materials)
○ Application
○ Purpose assignment
○ Market request
○ Market coverage
2. Migrate packaged products related to product using the migration template:
○ Bulk assignment
○ Market coverage

Tasks

Explorer.
1.26 PM - Equipment BOM
Purpose
Business Object Component/Area Plant Maintenance (PM)
Business Object Definition Plant Maintenance (PM):
A list used to describe the structure of a piece of equipment

and to allocate spares to the piece of equipment for mainte
nance.
An equipment bill of material can be created for each piece

of equipment or for a group of technical objects.
In Scope
The following Item Categories (Bill of Material) are supported:
1. L-Stock item
2. N-Non-stock item
3. T-Text item

Out of Scope
1. Sub-items
2. Document assignment
3. Long text
The following Item Categories (Bill of Material) are not supported:
1. R-Variable-size item
2. K-Class item
Supported Features
● BOM Header
● BOM Item
Prerequisites

Level Name
1 BOM Header (mandatory)
2 BOM Items
Tasks

Explorer.

Post-Processing
Transaction IB03 Display Equipment BOM
1.27 PM - Equipment task list
Purpose
Business Object Definition A description of a series of maintenance activities that are

executed repeatedly in a company.
A maintenance task list is the generic term for all task lists
that are used in plant maintenance.
The following task lists are available:
● Equipment task list

● Functional location task list
● General task list
In Scope

Supported Features
● Task List Header Data

● Operations
● Production Resource/Tools
● Material Components
● Maintenance Packages
Prerequisites
Business objects that reference this object must be created within a validity period that matches this object.
Internal/External number range assignment for Group Counter, with control parameter CTR_TLIST_E_NUM –
you have to decide if it is internal or external during each data load.
Level Name
1 Task List Header data (man

datory)
2 Operations (mandatory)
3 Production resource/tools
3 Material components
3 Maintenance packages

Tasks

Explorer.
Post-Processing
Transaction IA03 Display Equipment Task List
1.28 PM - Equipment
Purpose
Business Object Definition An individual, physical object that is maintained as an auton

omous unit.
In Scope
Starting with SAP S/4HANA release 1809, alternative labeling is supported for the Functional Location field in
the equipment structure.

Supported Features
● Equipment General Data

● Equipment Location
● Equipment Organization
● Equipment Structure
● Equipment SerData
Prerequisites

● Superordinate Equipment: To use the Superordinate Equipment field, make sure this value will be
implemented in the PM - Functional location [page 108] first.
Business objects that reference this object must be created within a validity period that matches this object.
Level Name
1 Equipment master data (mandatory)
Tasks

Explorer.
Post-Processing
Transaction IE01 Create Equipment
Transaction IE02 Change Equipment
Transaction IE03 Display Equipment
1.29 Exchange rate
Purpose
Business Object Definition The relationship between two currencies.
This rate is used to translate an amount into another cur

rency.
In Scope

Supported Features
● Exchange Rates
● Fill only direct or indirect quotation

● During upload, differences in exchange rate factor settings will automatically be adjusted, but there is no
adjustment of direct versus indirect notation
Level Name
1 Exchange rate master data (mandatory)
Tasks

Explorer.
Post-Processing
Transaction OB08 C FI Maintain table TCURR
1.30 Fixed asset (incl. balances and transactions)

Purpose
With this migration object, you perform a legacy data transfer for fixed assets.
Business Object Component/Area Asset Accounting (FI-AA)
Business Object Type Master data and transactional data (asset values)
Business Object Definition A fixed asset is an object, a right, or another item owned by
the enterprise that is intended for long-term use, and can be
identified individually in the balance sheet.
The development of the values of an asset can be viewed for

the asset as a whole, or can be viewed for the asset's com
ponent parts (subnumbers).
Example: Fixed asset "printing press" with asset compo

nents "rollers" and "replacement spindle".
In Scope
Supported Features
● Master Details
● Posting Information
● Time-Dependent Data
● Allocations
● Origin
● Acct Assignment for Investment
● Net Worth Valuation
● Real Estate and Similar Rights
● Leasing
● Depreciation Areas
● Investment Support Key
● Cumulative Values
● Posted Values
● Transactions
● Proportional Values on Transactions
● CountrySpecific
● CountrySpecific - Time-dependent

You use the SAP S/4HANA Migration Cockpit to transfer legacy data for fixed assets.
● You can transfer the asset master records for legacy assets.
 Note
The legacy asset number is migrated to the Original Asset field on the Origin tab page.
 Note
Transfer of asset subnumbers:

○ Asset subnumbers must be migrated within the same migration project. (This is due to the project
specific mapping table of the main asset number.)
○ If internal number assignment is used, the asset subnumbers must be transferred in a separate
file. (Reason: The mapping table for main asset number is only filled after the transfer of a
complete source file of main assets).
● You can transfer balances and transactions that have already been posted:
○ With transfers at the end of a fiscal year, the following applies:
The accumulated acquisition cost (APC) and the accumulated depreciation values are transferred.
○ With transfers during the year, the following applies:
The accumulated APC and the accumulated depreciation values are transferred. In addition to this,
you also transfer the transactions starting from the beginning of the fiscal year up to the time of the
transfer date. By default, you also transfer the posted depreciation of the year of transfer up to the
time of the transfer date. But you have the option not to transfer the posted depreciation in the year of
transfer. In this case, you first perform the legacy data transfer (without depreciation values in the year
of transfer), and then you calculate and post the depreciation in the system. In this case, you select the
corresponding checkbox in the Make Company Code Settings app.
 Note
When using the SAP S/4HANA Migration Cockpit, asset balances are updated automatically. No special
transfer for asset reconciliation accounts in G/L is needed.
Restrictions
The transfer of assets under construction (AUC) is not supported. Data for AUC and WBS must be transferred
manually in a consistent manner, and the information must be linked afterwards.
Prerequisites

● Profit center [page 190]
● Activity type [page 141]

Level Name
1 Master Details (mandatory)
2 Inventory
2 Time-Dependent Data
2 Allocations
2 Origin
2 Acct. Assignmt. for Investment
2 Net Worth Valuation
2 Real Estate and Similar Rights
2 Leasing
2 Depreciation Areas
2 Investment Support Key
2 Cumulative Values
2 Posted Values
2 Transactions
2 Proportional Values on Transactions
2 CountrySpecific
2 CountrySpecific - Time-dependent
Required Customizing Settings
● You have made the Customizing settings for the relevant depreciation areas. These settings determine
which data is accepted from the upload file. The upload is only successful if the values are compatible with
the depreciation area settings.
Here are some examples:
○ Per default, acquisition values must be positive, whereas depreciation values must be negative.
○ Acquisition values should be greater than the depreciation values (considering the absolute values).
It would be incorrect to enter an acquisition value of 3,000 with a depreciation value of -10,000.
○ Only for real depreciation areas do you need to specify transfer values in accordance with the settings
of the depreciation areas. You do not specify values for derived depreciation areas.
If a depreciation is defined to take over acquisition values from other depreciation areas (for example,
areas 15, 31, and 33 take over values from areas 01 and 32), and you enter values in the upload file
anyway, the system will ignore these values.

○ If you have parallel currencies, you must consider the following:
You can decide whether you want to transfer your historical foreign currency values or if you want to
have these values translated automatically instead.
If you do not specify any historical foreign currency values, then the system executes an automatic
translation; the exchange rate is then determined as follows:
○ For accumulated values at the start of the year: With the exchange rate on the capitalization date
of the fixed asset
○ For transactions during the year: With the exchange rate on the date of the legacy data transfer
○ For open items on a line item-managed fixed asset under construction (transaction type 900
and/or 910): With the exchange rate on the date of the legacy data transfer (as with a transaction
during the year)
If you want to transfer historical foreign currency values for the parallel currency areas, specify them
for the legacy data transfer. The system responds to this by not translating anything.
 Note
In the XML template, make sure that you enter your historical foreign currency values consistently
in the Cumulated Values and Posted Values worksheets.
● Make sure that all your asset classes are assigned to the correct number range interval before you start
migrating the fixed assets into your system.
● The offsetting account for the legacy data transfer (asset balance sheet account) must be defined in
Customizing for Asset Accounting under Define Offsetting Account for Legacy Data Transfer.
● You have created a legacy data transfer segment and for it you have specified the transfer date, the
document type and the legacy data transfer status in Customizing for Asset Accounting under Asset
Data Transfer Parameters for Data Transfer Define Transfer Date and Additional Parameters .
● If you want to perform a transfer during the year, you must enter the Last Period Posted
(FAA_DEPR_PERIOD) field on the Posted Values sheet.
You must specify the last posted depreciation period (from the legacy system) for each asset. The system
requires this information to determine the first period for the depreciation that should be posted in the SAP
system.
Required Activities
● The previous fiscal year must be closed in Asset Accounting.

This can be checked in Customizing for Asset Accounting under Preparations for Going Live Tools
Reset Year-End Closing .
● You have extracted the legacy data from your legacy system.
Pretest
We recommend that you perform a pretest in the test system: First, test system settings by performing a
manual legacy data transfer.

You can use the following Customizing activities (transactions) under Asset Accounting Asset Data
Transfer Manual Data Transfer Legacy Fixed Asset .
● Create Master Data for Legacy Asset (transaction AS91)

● Post Transfer Values (transaction ABLDT)
● AUC with Line Item Management: Transfer Line Items (transaction ABLDT_OI)
● Data Transfer During the Fiscal Year: Transfer Line Items (transaction AB01)
After this, you prepare the Microsoft Excel template and fill it with sample assets only (for example, one asset
per asset class). After the test, you should ideally clear the data from the test system:
● For asset master data, you can set a deactivation date to prevent the assets from receiving postings in the
future.
● You reverse the transfer postings.
● You check if the system contains any values for assets.
The productive system must not contain data before the data transfer.
Tasks

Explorer.
Post-Processing
In order to ensure that the legacy data transfer was carried out completely, you reconcile the data in the SAP
system with the data in your legacy system. You must reconcile the legacy data transfer and the corresponding
lists for documentation purposes before you release the SAP system for running operations in Asset
Accounting. This is because you may no longer be able to generate the corresponding lists later with only the
values from the legacy data transfer.

For details about how to reconcile the data, see SAP Note 2304473 .
Changing Transfer Values Subsequently

When uploading the migration template, the system posts the asset values. We recommend the following: If
incorrect transfer values were posted, you should reverse the journal entry and then enter the transfer values
again. You can only change transfer values by reversing the posted transfer document and making a new
posting. For the asset master data already created, you set a deactivation date and block it from receiving
postings. In the productive system, there should be no data before you start the file upload.

Further Information
Product Assistance
For more information, see the SAP Help Portal. Choose the your SAP S/4HANA system, and navigate to
Asset Accounting Legacy Data Transfer .
Further Links
● Fixed asset (incl. balances and transactions): Available Fields per Asset Class
● SAP Note 2427888 – Balance carryforward is required during legacy data transfer to AA in the first fiscal
year
● SAP Note 2208321 – FAQ for legacy data transfer in SAP_FIN 720 and subsequent releases
1.31 PM - Functional location task list
Purpose


In Scope

Supported Features

● Operations
Prerequisites
Internal/External number range assignment for Group Counter with control parameter CTR_TLIST_T_NUM –
you have to decide if it is internal or external during each data load.
Level Name

datory)

Tasks

Explorer.
Post-Processing
Transaction IA13 Display FunctLoc Task List
1.32 PM - Functional location BOM
Purpose
Business Object Definition Plant Maintenance (PM)
A list used to describe the structure of a functional location

and to allocate spares to the functional location for mainte
nance.
A functional location BOM can be created for each functional

location or for a group of technical objects.
In Scope

The following Item Categories (Bill of Material) are supported:
1. L-Stock item
2. N-Non-stock item
3. T-Text item
Out of Scope
1. Sub-items
2. Document assignment
3. Long Text
The following Item Categories (Bill of Material) are not supported:
1. R-Variable-size item
2. K-Class item
Supported Features
● BOM Header
● BOM Item
Prerequisites

Level Name
1 BOM header (mandatory)
2 BOM item

Tasks

Explorer.
Post-Processing
Transaction IB13 Display Functional Location BOM
1.33 PM - Functional location
Purpose
Business Object Definition An organizational unit in logistics that structures the mainte
nance objects of a company according to functional, proc
ess-oriented, or spatial criteria.
A functional location represents the place at which a mainte

nance task is performed.
In Scope

Supported Features
● Functional Location - General Data

● Functional Location - Location Data
● Functional Location - Organization Data
Prerequisites

Level Name
1 Functional Location Data (mandatory)
Superior Functional Location

If this field is empty, then the system will automatically determine a superior functional location based on the
structure that you are using. When you create a new functional location, the system will enter its label as a
default value in this field.
You can enter an alternative if necessary, although you should ensure that the structure is kept the same,
otherwise the transfer of data within the functional location structure will be prevented.
In SAP S/4HANA, if the Labeling System for Functional Locations is used, the object will only support installing
superior functional location automatically, so please make sure the Superior Functional Location field is empty
in this case.

Labeling System for Functional Locations
The labeling system is only supported in SAP S/4HANA.
Tasks

Explorer.
Post-Processing
Transaction IL01 Create Functional Location
Transaction IL02 Change Functional Location
Transaction IL03 Display Functional Location
1.34 PM - General maintenance task list
Purpose


In Scope
Supported Features

● Operations
Internal/External number range assignment for Group and Group Counter:
● The Group and Group Counter must be provided in source file, and joint with task list type to distinguish
different type of task list. For the scenario of one Group with several Group Counters, they must be grouped
logically in the source file.

● With control parameter CTR_TLIST_A_NUM, you have to decide if it is internal or external during each data
load.
Level Name

datory)
Tasks

Explorer.
Post-Processing
Transaction IA07 Display General Task List
1.35 G/L account (deprectated)
 Restriction
This migration object is replaced by a newer one. Please use the new G/L account [page 114] migration
object instead.

Purpose
Business Object Definition G/L account master records contain the data that is always
needed by the General Ledger to determine the account's
function. The G/L account master records control the post
ing of accounting transactions to G/L accounts and the
processing of the posting data.
In Scope
The following GL account types are supported:
1. X - Balance sheet account.

2. N - Non-Operating expense or income profit and loss account that is used in FI only.
3. P - Primary costs or revenue profit and loss account that is used in FI and CO.
4. S - Secondary costs profit and loss account that is used in CO only.
Out of Scope
1. Customize GL account type
Supported Features
● Chart of Accounts Area

● Company Code Specific Area
● GL Account Names
● GL Account Keywords

Level Name
2 Company code data
2 GL account names
2 GL account keywords
Tasks

Explorer.
Post-Processing
Transaction KA01 Create Cost Element
Transaction KA06 Create Secondary Cost Element
Transaction FS00 G/L acct master record maintenance
Transaction FSS0 G/L account master record in co code
1.36 G/L account

Purpose
Business Object Definition G/L account master records contain the data that is always
needed by the General Ledger to determine the account's
function. The G/L account master records control the post
ing of accounting transactions to G/L accounts and the
processing of the posting data.
In Scope
The following GL account types are supported:
1. X - Balance sheet account.

2. N - Non-Operating expense or income profit and loss account that is used in FI only.
3. P - Primary costs or revenue profit and loss account that is used in FI and CO.
4. S - Secondary costs profit and loss account that is used in CO only.
Out of Scope
1. Customize GL account type
Supported Features
● Chart of Accounts Area

● Company Code Specific Area
● GL Account Names
● GL Account Keywords

Level Name
2 Company code data
2 GL account names
2 GL account keywords
Tasks

Explorer.
Post-Processing
Transaction KA01 Create Cost Element
Transaction KA06 Create Secondary Cost Element
Transaction FS00 G/L acct master record maintenance
Transaction FSS0 G/L account master record in co code
1.37 FI - G/L account balance and open/line item

Purpose
Business Object Definition G/L account balance: The balance of a G/L account is the
amount resulting from the difference between the debit and
credit balances of the account. There are two types of bal
ance:
● Credit balance (the credit side of the account is greater)

● Debit balance (the debit side of the account is greater)
G/L account open/line item: Open/line items are the items

that are not yet to be cleared. This object loads the open
items/line items and balances for general ledger accounts.
Fixed asset balance: Fixed asset balances are migrated with

the Fixed asset (incl. balances and transactions) [page 98]
migration object. You must NOT migrate these balances with
the FI - G/L account balance and open/line item migration
object. Therefore, you must ensure that your migration file
for G/L account balance does not contain any records for
fixed asset balances.
In Scope
Out of Scope
1. Multiple line items per document post

2. External accounting document number
3. Open tax items
○ Open tax must be settled before data migration
○ Exception: Deferred tax can be migrated with the migration activities for Open items payable and Open
items receivable
4. Calculate tax automatically
5. Postings to G/L accounts with open item management
6. Migration of historical financial transactions (use the FI - Historical balance [page 121] migration object;
see SAP Note 2587192 )

Supported Features
● Header
● G/L Account Item
● Currency Item
Prerequisites
Before starting with the initial data transfer, you must define an overall migration key date for each company
code. This migration key date will be used for all migration objects which are posting into financial accounting,
except for the Fixed asset (incl. balances and transactions) [page 98] object.
Use the FINS_MIG_CTRL_1 transaction (Define Settings for Legacy Data Transfer) to maintain these settings:
● Set the Migration Key Date for each required company code
● Set the Legacy Data Transfer Status:
○ 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 finish of the initial data transfer (Migration of transactional data is not
possible)

Only mandatory if account assignment on cost center is necessary.
Posting on tax jurisdiction will be automatically derived by cost center. Therefore, the tax jurisdiction code
must be already maintained for cost center master.
Only mandatory if account assignment on profit center is necessary.
Posting on tax jurisdiction will be automatically derived by profit center. Therefore, the tax jurisdiction code
must be already maintained for profit center master.
● WBS element
○ Only mandatory if account assignment on Work Breakdown Structure (WBS) element is necessary.
○ WBS element must be defined as a billing element.
○ System status of WBS element must be on Released.
○ Sales order item must be assigned to WBS element.
● Order (manually)
○ Only mandatory if account assignment on an order is necessary.
○ The related order is not flagged for deletion.
○ Indicator for Revenue Posting Allowed should be set for the order (adjustment only possible in
customizing of Order Type).
○ System status of the order must be Released or Technically completed.
○ Posting date (which is used for migration of G/L balance) must be within the validity period of the
assigned object for the order, for example, profit center.
● Network Number for Account Assignment

○ Only mandatory if account assignment on network number is necessary.
● Exchange rate [page 97]
Dependencies
Recommended approach for the initial migration of financial data:
Please in keep in mind that no documents will be migrated. Only balances and open items will be taken over.
Clear as many of the open items payable, receivables, taxes and outgoing checks as possible from the
accounts in the source system. By reducing these open items, you will reduce the amount of variables,
resulting in a lower possibility of error as well as reducing the amount of reconciliation needed to verify the data
migration.
From the bank account, only the balance needs to be migrated.
Normally, no items or balances from the tax accounts need to be migrated because they are usually balance
zero (for normal VATs) when the migration takes place. We assume that the tax transfer has already been done
and therefore no tax has to be migrated. Exception: Deferred taxes can be migrated with the migration
activities for Open items payable and Open items receivable.
● Enter only one line per document post into the migration file. The offsetting entry will be automatically
generated for the offsetting G/L account.
● The combination of key fields Company Code + Ledger Group + Reference Document Number + Line Item
Number + G/L Account are used for duplicate check. Data records with this combination should be unique
in the migration template. Otherwise, the migration tool will display a duplicate error message. The Line
Item Number will just be used as an additional key field and will not be migrated.
● Please be aware you must fill and save value amounts in the migration file in number and not in string
format. Check the settings for a delimiter.
● For migration, the posting keys will be controlled by the sign in the amount fields. The sign for negative
values should be set at the beginning:
○ A negative value will use posting key 50 (Credit entry) for G/L Account and 40 (Debit entry) for
Offsetting G/L Account
○ A positive value will use posting key 40 (Debit entry) for G/L Account and 50 (Credit entry) for
Offsetting G/L Account
● The initial offsetting (transfer booking) accounts to be used in the Open items and Open balances
migration objects are described in the BH5 test script :
○ 39914000 (Initial FI-AR offset)
○ 39915000 (Initial FI-AP offset)
○ 39916000 (Initial other GL offset)
○ 39917000 (Initial other Open Item GL offset)

Two approaches for currency and amount:
Provide all relevant currencies and related amounts via the template. In doing this, the provided values will be
adopted from the template regardless of existing exchange rates in the system.
Keep the second local/group currency field and related amount empty in the template. In this case, the amount
will be automatically calculated by valid exchange rates in the system.
The exchange rate will be determined using the provided document or posting date. Which date will be used is
defined in the customizing for each company code (in SPRO via Change Foreign Currency Translation).
Two approaches for CO account assignment for an account that is relevant to cost
accounting:
Provide the required CO account assignment via migration template.
Define in customizing the automatic CO assignment on accounts via tcode OKB9 (Default account assignment).
Please note, if this required CO object is not provided via the template, the default CO assignment will be used
automatically for migration.
Level Name
1 Header + Item (mandatory)
Tasks

Explorer.
Post-Processing
Transaction FB01 Post Document
Transaction FB02 Change Document
Transaction FB03 Display Document

1.38 FI - Historical balance
Purpose
Business Object Definition Historical G/L account balance: The balance of a G/L ac
count is the amount resulting from the difference between
the debit and credit balances of the account.
There are two types of balance:
● Credit balance (the credit side of the account is greater)

● Debit balance (the debit side of the account is greater)
This object loads the historical balance for general ledger ac
counts without any complex plausibility checks into the uni
versal journal. The reversal document will be created auto
matically. The migrated historical balances are intended as
an approach for reporting. It is not possible to view the mi
grated documents themselves.
In Scope
1. Migration of Historical G/L account balances

2. Migration on already closed posting periods before migration key date
3. Postings to G/L accounts with open item management
4. Postings on G/L account without the required assignment to a CO object
5. Direct postings to reconciliation accounts (Customer, Vendor, Asset)
Out of Scope
1. Multiple line items per document post

3. Postings on blocked or non existing G/L accounts

Supported Features

● Currency Item
Prerequisites
possible)
● G/L account [page 114]

To be posted, G/L accounts must be maintained
● Choose the required migration strategy in Migration Cockpit via the Upload Style parameter:
○ Balance Carry Forward (BCF): Post the accumulated balance at the end of each period and reverse the
balance of the previous period.
○ Next Period Reverse (NPR): Post the initial cumulative balance in the first period and the subsequent
movements at the end of each following period. The cumulative balance will be increased or reduced
by the amount of the subsequent movements and will be automatically reversed in the period of the
migration key date which is predefined via the Define Settings for Legacy Data Transfer app.
● Enter only one line per document post for each period into the migration file. The offsetting entry will be
generated automatically to ensure the balance is zero.
● Please be aware you must fill and save value amounts in the migration file in number and not in string
format. Check the settings for a delimiter.
● For migration, the debit/credit indicator will be controlled by the sign in the amount fields. The sign for
negative values should be set at the beginning:
○ A positive value will post a debit entry (S)
○ A negative value will post a credit entry (H)
● Fiscal year and period must be before the migration key date. Postings after this key date are not allowed.

● Currency and amount:
○ All currency amount fields in the migration template are mandatory. The amounts will not be derived
automatically.
○ Transaction/document currency is mandatory. Local/company code currency and group currency are
optional and will be derived automatically by the customizing settings maintained in system. An error
message will be displayed if those currencies are filled in the template but do not match the
customizing settings.
○ Recommendation: provide all currency information via the template to ensure the provided amounts
match to the related currencies. Otherwise, inconsistencies might be migrated.
● Naming convention used as internal document number (for example, DHG0000001):
○ D = Document
○ H = Historical
○ G = GL balance
○ 0000001 = automatically counted up
● Naming convention used for reversal document number (for example, DHR0000001):
○ D = Document
○ H = Historical
○ R = Reversal
○ 0000001 = automatically counted up
Level Name
1 Item (mandatory)
Tasks

Explorer.
Post-Processing
Transaction S_PL0_86000030 G/L Account - Balances
Transaction FAGLB03 G/L Account Balance Display

1.39 QM - Inspection method
Purpose
Business Object Definition Describes the procedure for inspecting a characteristic.
Inspection methods are created as master records and as

signed to master inspection characteristics, or inspection
plans. Several inspection methods can be assigned to a
master inspection characteristic.
In Scope
Supported Features
● Inspection Method General Data

● Inspection Method Short Text
● Inspection Method Long Text
Prerequisites

● QM - Selected set [page 223]
● QM - Selected set code [page 225]

● The version of the inspection methods will be created as '000001'.

● Text line in inspection method long texts. For each inspection method, there may be several languages
here, but each language only has one text line in the source file. The object will separate the text line into
several lines automatically, and then into the long texts for each language.
Validity Period and Dependencies to Other Objects

Business objects that references this object must be created in validityperiod that fits to this object. If a
successor object is created with a validity period starting before this object it will normally cause an error
message during the creation or migration of the successor object. You therefore have to check such time
dependencies before you create or migrate your objects. This will avoid later error messages and inconsistent
data on your database.
Level Name
1 Inspection Method General Data (man

datory)
2 Inspection Method Short Texts (manda

tory)
2 Inspection Method Long Texts
Tasks

Explorer.
Post-Processing
Transaction QS31 Create Inspection Method
Transaction QS32 Create Inspection Method Version
Transaction QS33 Change Inspection Method Version
Transaction QS34 Display Inspection Method Version

1.40 QM - Inspection plan
Purpose
Business Object Definition Description of the quality inspection process for materials in
a plant
In Scope
Supported Features
● Task List Header

● Material Task List Assignment
● Operations
● Inspection Characteristics
Prerequisites

● QM - Inspection method [page 124]
● QM - Master inspection characteristic [page 175]

Flow Variants for Inspection Point Completion
' ' - Quantity, valuation and confirmation (production)
1 - Quantity, valuation (production)
2 - Valuation
3 - Automatic valuation based on insp. point definition
Level Name
1 Task List Header (manda

tory)
2 Material Task List Assign

ment (mandatory)
3 Inspection Characteristics
Tasks

Explorer.

Post-Processing
Transaction QP03 Display Inspection Plan
1.41 Material inspection setup
Purpose
Business Object Component/Area QM Master Data (QM-PT-BD)
Business Object Definition Within this migration object you can assign inspection setup
data to a material.
In Scope
1. Inspection setup data
Supported Features
● Inspection Setup Data

Prerequisites
● During migration, you can choose via control parameter whether the inspection setup data should be taken
from the source file or if it should be taken from the default which is defined in the system.
Level Name
1 Inspection Setup Data (mandatory)
Tasks

Explorer.
Post-Processing
Transaction MM03 Display Material
Choose Quality Management Insp.setup .
1.42 Internal order (restricted)

Purpose
Business Object Component/Area Controlling (CO)
Business Object Definition An internal order is an instrument used to monitor costs

and, in some instances, the revenues of an organization.
Internal orders can be used for the following purposes:
1. Monitoring the costs of short-term jobs

2. Monitoring the costs and revenues of a specific service
3. Ongoing cost control
Order Number Range
All the internal order types Y020- Y600 use internal number
range.
However, Y9A0 uses external number range from

9A0000000000 to 9AZZZZZZZZZZ.
In Scope
Supported Features
● Master Data
● Settlement Rules
Prerequisites
The following objects must already have been maintained or migrated:


Level Name
1 Internal order master data (mandatory)
2 Settlement rule data
Tasks

Explorer.
Post-Processing
Transaction KO03 Display Internal Order
1.43 Material inventory balance
Purpose
Business Object Component/Area Inventory Management (MM-IM)

Business Object Definition A detailed list of all objects in stock at a specific time, result
ing from a physical inventory (stocktaking process).
In Scope
1. Material document header

2. Material document item
3. The following types of transactions/events are supported: GM_Code 05: Other goods receipt
● The following stock types are supported:

○ ‘X’ - Stock in quality inspection
○ ‘S’ - Blocked stock
○ ‘ ’ - Unrestricted use stock
 Note
For special stock indicators ‘O’ and ‘V’, the stock can only be posted in Unrestricted use stock.
● The following special stock indicators are supported:

○ ‘K’ - Vendor consignment
○ ‘W’ - Customer consignment
○ ‘V’ - Returnable packaging with customer
○ ‘O’ - Parts provided to vendor
○ ‘E’ - Orders on hand
○ ‘Q’ - Project Stock
 Note
For Vendor consignment stock, please provide special stock indicator ‘K’ and the vendor.
For Customer consignment stock, please provide special stock indicator ‘W’and the customer.
For Returnable packaging stock, please provide special stock indicator ‘V’ and the customer.
For Parts provided to vendor stock, please provide special stock indicator ‘O’ and the vendor.
For Orders on hand, please provide special stock indicator ‘E’ and the sales order with the corresponding
item
For Project stock, please provide special stock indicator ‘Q’ and the WBS element
For Materials which are serial managed, please provide for each serial number one item with quantity 1.
For Materials which are batch managed, please provide the corresponding batch. If the batch doesn't exist
the system will create it within the goods movement posting.

Out of Scope
1. The following types of transactions/events are not supported:

○ GM_Code 01: Goods receipt for purchase order.
○ GM_Code 02: Goods receipt for production order
○ GM_Code 03: Goods issue
○ GM_Code 04: Transfer posting
○ GM_Code 06: Reversal of goods movements
○ GM_Code 07: Subsequent adjustment with regard to a subcontract order
2. Material document EWM Ref.
3. Service parts for SPM
4. Create item data for catch weight management
5. Material document print control
6. Storage locations with an assignment to an external warehouse are not supported
Supported Features
● Material Document Header Data

● Assign Code to Transaction for Goods Movement
● Material Document Items
● Serial Number
The following structures/features are supported:
● Material Document EWM Ref.

● Service Parts for SPM
● Create Item Data for Catch Weight Management
● Material Document Print Control
Prerequisites
possible)

● Material [page 162]: It is not possible to enter the external value for the stock posting during migration.
The system will calculate the value with the material prices defined in the material master in the
accounting data. Please ensure that the price data provided in the material master is accurate.
● Batch (if Batch is unique at material level) [page 25] (otherwise the system will create the batch
automatically during stock posting).
 Note
In the case of single batch valuation you have to migrate the batches with a valid valuation category
assigned before you can post inventory. In this case we do not allow automatic creation of the batch
and the valuation category during inventory posting.
● Supplier [page 238]/Customer [page 75] (only relevant for special stock: K – vendor consignment , V –
Returnable packaging with customer, and O - Parts provided to vendor)
● WBS element (only relevant for special stock Q - Project stock)
● Purchasing info record with conditions [page 202] with info category Consignment (only relevant for
vendor consignment stock)
General Information
You can use the Technical Item Number field on the Material Document Item sheet itself to determine the
numbers of items posted according to the unique identifier entered on the Material Document Header sheet.
SAP recommends that you structure the document with a maximum of 1000 records per document.
 Note
The Technical Item Number field on the Material Document Item sheet and the Technical Document Number
on the Material Document Header sheet are not mapped to a target field.
Mapping of the Batch Number field on the Material Document Item sheet
You want to post stock for a material that is defined by its valuation category as a material valuated in single
batches. In this case you have to provide a valid batch. The valuation category must be assigned in the batch
itself.
Mapping of the External Amount in Local Currency field on the Material Document Item sheet
The valuation of the stocks to be entered depends on two factors:
● The price and type of price control defined in the accounting data of the material master record
● Whether or not you provide a value for the quantity entered:
For a material valuated at a standard price, the initial entry of inventory data is valuated on the basis of the
standard price. If you provide an alternative value in the External Amount in Local Currency field, the
system posts the difference to a price difference account.
For a material valuated at moving average price, the initial entry of inventory data is valuated as follows:
○ If you enter a value when entering initial data, the quantity entered is valuated at this price. If the
quotient of the value and the quantity of the initial data differs from the moving average price, the
moving average price changes when initial data is entered.

○ If you do not enter a value when entering initial data, the quantity entered is valuated at the moving
average price. In this case, the moving average price does not change.
Level Name
1 Material Document Header (manda

tory)
2 Material Document Item (mandatory)
Tasks

Explorer.
Post-Processing
Transaction MMBE Stock Overview
Transaction MB5L List of Stock Values: Balances
Transaction MB51 with Goods Movement Type 561 Material Doc. List
Transaction MB52 List of Warehouse Stocks on Hand
1.44 Cost center

Purpose
Business Object Component/Area Cost center (CO)
Business Object Definition An organizational unit within a controlling area that repre
sents a defined location of cost incurrence.
A cost center can be defined in various time intervals.
In Scope
Supported Features
● Basic Data
● Control
● Templates
● Address
● Communication
Prerequisites
● Groups for Cost center


Level Name
1 Cost center master data (mandatory)
Language in Which Text is Saved

The LANGU field shows the language in which text is saved. The cost center name and description will be saved
according to the entry in the LANGU field. If the field is not completed, the text will be saved in the user logon
language as the default language. A cost center with a description in a different language is not supported.

If Vertex determines more than one tax jurisdiction code for a record, the migration of this record will fail. If this
happens, you have to provide a more detailed/accurate address, for example, US Postal codes with 9 digits
The more detailed and accurate an address, the better the tax jurisdiction code will be determined by Vertex.
For some addresses, Vertex will always provide more than one tax jurisdiction code. In this case, you will have to
If there is a field available in the migration object template to provide the correct tax jurisdiction within the
record, then fill this field with the correct code and start the transfer again with this new file.
Hierarchy area
Cost center groups entered in the KHINR/Hierarchy area field must be assigned to the standard hierarchy. If
this is not the case, you will get the error message Cost Center Group cannot be used.
Tasks

Explorer.
Post-Processing
Transaction KS03 Display Cost Center

1.45 Legal transaction
Purpose
Business Object Component/Area Legal Content Management (LCM)
Business Object Definition Business object that is used to manage the lifecycle of legal
content as part of a business transaction or a business sce
nario.
A legal transaction collects the involved parties and impor

tant dates, it groups the assigned documents and organizes
the tasks.
In Scope
1. Header Data
2. Entity Data
3. Internal Contact Data
4. External Contact Data
5. Linked Objects Data
6. Renewal and Termination Data
7. Relationship Data
8. Date Data
9. Categories Data
Out of Scope
1. Task Group Templates

2. Tasks

3. Documents
4. Linked Documents
5. Notes; object list cannot be created
Supported Features
● Header
● Entity
● Internal Contact
● External Contact
● Linked Objects
● Renewal and Termination
● Relationship
● Date
● Categories
Prerequisites
Contexts and categories should be created in the system.
Level Name
2 Entity
2 Internal Contact
2 External Contact
2 Linked Objects
2 Renewal and Termination
2 Relationship
2 Date
2 Categories


If Vertex determines more than one tax jurisdiction code for one record, the migration of this record will fail. If
this happens, you will have to provide a more detailed/accurate address, for example, 9 digit US Postal codes
For some addresses, Vertex will always provide more than one tax jurisdiction code. In this case you will have to
maintain this record manually.
If there is a field available in the Migration object template to provide the correct tax jurisdiction within the
Pricing scales are supported

Example for quantity based scale:
1,000 EA 100,00000 EUR
100,000 EA 90,00000 EUR
Tasks

Explorer.
Post-Processing
App: Manage Legal Transactions
Choose Legal Transaction.
Business Role: Legal Counsel (SAP_BR_LEGAL_COUNSEL)
Find more information about SAP Fiori apps in the SAP Fiori apps reference library. This information covers
required business roles and includes links to the respective app documentation.
Further Information
For information regarding the used API see SAP Note 1348099 .

1.46 Activity type
Purpose
Business Object Component/Area Activity types (CO)
Business Object Definition A unit in a controlling area that classifies the activities per
formed in a cost center.
Example: Activity types in production cost centers are ma

chine hours or finished units
In Scope
Supported Features
● Basic Data
● Indicator
● Output
Prerequisites
If you set the TESTRUN flag, the migration will be simulated but no data will be posted to the system.

Level Name
1 Activity master data (mandatory)
Tasks

Explorer.
Post-Processing
Transaction KL03 Display Activity Type
1.47 PM - Maintenance item
Purpose
Business Object Component/Area Maintenance Item (PM)
Business Object Definition A description of the maintenance and inspection tasks re
quired at regular intervals for maintenance objects.

In Scope
Out of Scope
1. Data transfer for settlement rule of maintenance plan item

2. Data transfer for object list item of maintenancep plan item
3. Data transfer for individual accounting and location data
○ These are taken from the reference object when they exist
Supported Features
● Maintenance Item
Prerequisites

● Cost element
● PM - General maintenance task list [page 110]
● PM - Equipment task list [page 93]
● PM - Functional location task list [page 104]
Maintenance Item Number
The Maintenance Item Number will be generated by the system during creation. The Maintenance Item Number
will not be stored. It is only necessary for technical reasons. Every record must have a unique key.

Level Name
1 Maintenance Item (mandatory)
Tasks

Explorer.
Post-Processing
Transaction IP06 Display Maintenance Item
1.48 PM - Maintenance plan
Purpose
Business Object Component/Area Maintenance Plan (PM)

Business Object Definition A list of maintenance and inspection tasks to perform on
maintenance objects. The dates and scope of the tasks are
also defined in the maintenance plan. There are three types
of maintenance plan:
● Single cycle plans (time- or performance-based)

● Strategy plans (time- or performance-based)
● Multiple counter plans
In Scope
1. Data transfer for time- and performance-based maintenance plans

○ Strategy Plans
○ Single Cycle Plans
2. Data transfer for maintenance plan item
Out of Scope
1. Multi-Counter plans
2. Cycle information for strategy plans:
This is taken from the Maintenance Strategy object
3. Data transfer for settlement rule of maintenance plan item
4. Data transfer for object list item of maintenance plan item
5. Data transfer for individual accounting and location data:
This taken from the Reference object, where this exists
Supported Features
● Maintenance Plan
● Maintenance Item
Prerequisites

● PM - Equipment task list [page 93]
● PM - Functional location task list [page 104]
● PM - General maintenance task list [page 110]
● Measuring Points/Counters (performance-based Maintenance Plan)
● Measuring Document (performance-based Maintenance Plan): manually create the measuring
document(s) within the counter before executing the migration of any performance-based maintenance
plans
● During migration you can choose between internal and external number assignment for the maintenance
plan. The Maintenance Item Number will be generated by the system during creation.
● The difference between a single cycle plan and a strategy plan is made via the STRATfield (blank or filled).
Level Name
1 Maintenance Plan Data (mandatory)
2 Maintenance Item Data (mandatory)
Tasks

Explorer.
Post-Processing
Transaction IP03 Display Maintenance Plan or
Transaction IP16 Display Maintenance Plan: Selection Criteria

1.49 Product classification - Commodity code
 Caution
A prerequisite for this object (previously named Material commodity code) to be visible is that either the
Intrastat Processing (BDT) or the SAP Global Trade Services Integration - Primary Master Data (1WA) scope
item is activated. Refer to the Set-up instructions on SAP Best Practices Explorer for BDT and/or 1WA
to activate the respective scope item.
Purpose
Business Object Component/Area Global Trade Services (SLL-LEG)
Business Object Definition You can classify products by commodity code, an official key
as defined in the European Communities' harmonized sys
tem for describing and coding commodities. Commodity co
des are used in the Intrastat declaration and are relevant to
EU foreign trade statistics.
The plant in the migration template is used to determine the

plant country and, depending on that, the numbering
scheme assigned to that country.
New classifications are time-dependent and the validity of

those records is based on the validity of the commodity code
instance found in the system. If several instances of the
same commodity code are found, the one that is currently
valid will be used. If no such instance exists, the last one
chronologically is used.
In Scope
Classification with commodity code.

Supported Features
● Classification on plant level
Prerequisites
● Commodity Code Numbering Schemes are assigned to countries

● Commodity Codes are maintained for relevant numbering schemes
Tasks

Explorer.
Post-Processing
1.50 Material - Forecast planning
 Restriction
● To migrate material consumptions please use the new Product consumption [page 193] migration
object.

● To migrate forecast values you can still use this object.
Purpose
Business Object Component/Area Material Master (LO-MD)
Business Object Definition A quantity usually updated by the system when a material is
withdrawn from the warehouse or stores, indicating how
much of the material has been used or consumed over a par
ticular past period.
In Scope
1. Migration of Forecast values
Supported Features
● Forecast Values
Prerequisites
Restrictions
You can migrate several org. levels for a specific material with one migration template of a specific project.

Tasks

Explorer.
Post-Processing
Choose Forecast view Consumption values Forecast values . Consumption values can also be accessed
via Go To Additional Data Consumption .
1.51 Material - extend existing record by new org levels
Purpose
Business Object Definition Logistics Basic Data (LO-MD)
The total of all material master records.
A company manages the data on all its materials in the ma

terial master.

In Scope
 Note
With this migration object you can extend existing material by new org levels (for example plant, sales org,
or storage location) once per migration project.
A material view, such as Accounting or Costing, contains fields of different org levels (for example basic,
plant, or accounting data). It is therefore not recommended to enhance a material by a different material
view.
1. Extend already existing materials with new org levels

2. Basic data (only fields which might become relevant when you migrate new organizational units)
3. Plant data
4. Storage Location
5. Accounting data
 Note
The valuation data is a prerequisite for loading the stocks with the Material inventory balance [page
131] migration object, as the system will calculate the values of the stock posting with the price data
provided in the material master.
6. Sales data
7. Descriptions data
8. Units of Measure data
In this view you can maintain Alternative Units of Measure
9. Tax Classifications
In this view you can maintain the tax data (from Sales Org Data 1) and the tax indicator for material
(Purchasing)
For tax data (Sales) please provide the country, the tax category and the tax classification. If you have more
than one tax category for a country, please use the Tax category 2/Tax classification 2 fields and further on,
use the Tax classification sheet to provide the additional tax data.
For the tax indicator for material (Purchasing), please enter the value in the Tax indicator for material field
on the Tax classification sheet for the country relating to your plant.
10. Warehouse Number data
11. Storage Type data
12. Production Resource Tool (PRT) Fields in the Material Master
13. Data Transfer for Forecast Values
Out of Scope
1. Material Long Text

2. Data Transfer for Unplanned Consumption
3. Data Transfer for Total Consumption of Material

4. Data Transfer of MRP Areas
5. Data Transfer of Prices for different Group Currencies
6. Change already existing data
Supported Features
● Basic Data
● Plant Data
● Storage Location Data
● Accounting Data
● Sales Data
● Description Data
● Unit of Measure Data
● Tax Classification Data
● Warehouse Number Data
● Storage Type Data
● Production Resource Tool (PRT)
● Forecast Parameters
Prerequisites

Basic Data
On the Basic Data sheet we only offer fields which might become relevant when you migrate a new
organizational unit. This can be the case, for example when you migrate a new plant including purchasing
relevant data (like purchasing group). Then the Order Unit field on the Basic Data sheet might also become
relevant to provide a value.
Please consider: You can't transfer a value in one of the fields provided on the Basic Data sheet which has
already a value in the related material master. It's not allowed to change already existing values in the related
material master: Therefore you can use the Manage Mass Maintenance – Products app. For further information,
refer to the online documentation of the Manage Mass Maintenance – Products app.

New storage location to an existing plant
If you want to migrate a new storage location to an already existing plant, please provide only the key fields on
the Plant Data sheet and leave all the other fields blank. It is not allowed to change already existing values for an
existing plant. If you provide other values on the Plant Data sheet, an error message will display.
Recommendation on how to handle cross-plant material status and plant-specific material

status
If you set the material status during the initial load of the materials, you need to consider that, depending on
which status you want to assign, follow-on migration objects can't be posted as the posting may lead to an
error depending on the settings of the status.
Example: In SAP standard delivery, material status 01 is configured in such a way that, during the posting of
inventory, you'll get an error message. Consider that when you assign the status, the use of the material can be
restricted. Depending on the status, the system issues either a warning message or an error message for
follow-on postings. Therefore, we recommend that you consider this field carefully so that you won't run into
follow-on problems during the data migration process. You can easily set the content of these fields after the
initial data migration using the Manage Mass Maintenance – Products app.
The Master Data Specialist for Product Data business role (SAP_BR_PRODMASTER_SPECIALIST) provides you
with several tiles to manage and start the Manage Mass Maintenance – Products app. You can open the app
from the SAP Fiori launchpad. You can import a file with changed data (supported formats are Comma-
Separated Values (CSV) and Microsoft Office Open XML spreadsheet (XLSX). You have to provide the following
details:
● Master data objects that are updated

● Tables and fields to be updated and the respective values
For further information, refer to the online documentation of the Manage Mass Maintenance – Products app.
Single Batch Valuation
Single Batch Valuation enables you to valuate stocks of material for each batch in a different way. You can use it
if you want to keep the price and value of each individual batch in inventory management on a value basis.
To work with valuation for a single batch, you must choose valuation category X - for Automat. Batch. Please
provide this on the Accounting Data sheet in the Valuation Category field.
 Note
You need to manage the material itself in batches. Therefore you have to provide the Batch management
requirement indicator on the Basic Data sheet.
If you use the single batch valuation for your material, you have to enter the valuation records as follows:
You have to define a valuation header record with specified valuation category X, an initial valuation type and a
dependent record for each valuation type (one valuation type for each batch) with its own price information.
Material No. Valuation Area Valuation Type Valuation Category
A001 1010 X (Automat. Batch)
A001 1010 C1 X (Automat. Batch)

 Note
For the valuation header record only price control 'V' - moving average price is possible. For the dependent
records for each valuation type, you can choose between moving average price or standard price.
Split Valuation
Split valuation enables you to valuate stocks of material in the same valuation area in different ways. If you use
the split valuation for your material, you have to enter the valuation records as follows:
You have to define a valuation header record with a specified valuation category and initial valuation type and
also a dependent record for each valuation type.
For example:
A001 1010 H (Origin)
A001 1010 Domestic H (Origin)
A001 1010 Foreign H (Origin)
Level Name
1 Basic Data (mandatory)
2 Plant Data
3 Storage Location Data
3 Forecast Parameters
3 Production Resource Data
2 Warehouse Number Data
3 Storage Type Data
2 Accounting Data
2 Sales Data
2 Material Descriptions
2 Alternative Units of Measure
2 Tax Classification
1 Settings Maintenance Status
Maintenance Status Settings
Just like the organizational-dependent data, the material master data is also organized via so-called views
(Purchasing, Accounting view, and so on). These views are represented as tabs in your SAP Fiori app and as
material master transactions (MM01, MM02, MM03) in the on premise system. You can assign fields to
multiple views. The Purchasing Group field, for example, is assigned to the Purchasing and to the MRP views.
Each view may have different mandatory fields to maintain. A view is assigned a specific letter. For example, the
letter D is assigned to the MRP whereas the letter E is assigned to the Purchasing view. There are two different

methods for defining the maintenance status that should be available for a specific material which will be
extended:
1. The maintenance status will automatically be detected by the system for the fields used. In our example,
the Purchasing Group is available for the Purchasing view E and the MRP view D. The maintenance status
will therefore be DE for this field. This procedure will be followed for all mapped fields, after which a
combined maintenance status for all fields will be available, for example: BELV.
2. You, yourself define the views to be created via the Maintenance Status Settings worksheet/tab of your
migration object template. Here, you define a name for your view definition in the Material Views field, for
example, PLANT_HAWA to define the maintenance status for the plantspecific data for materials of that
type, which will be extended. For each view that you want to create, you must enter an x in the specific
Material Views column of that worksheet/tab, for example: PLANT_HAWA
○ Sales Data = X
○ Purchasing Data = X
○ MRP Data = X
○ Storage Data =X
○ Accounting Data = X
You fill out the Material Views field on the Plant Data worksheet/tab with PLANT_HAWA for all trading goods
materials of type HAWA, which you want to extend. You always have to provide values for both fields. As a
result, only the selected views are created for these materials.
 Note
If you maintain the status using method 2, only the selected views will be created.
For example: You maintain the status for Sales Data (V) but not for Accounting Data (B). You maintain
values for fields on the Accounting Data worksheet/tab. As a result, the status for the Accounting view will
not be set.
Additional examples:
● If you want to create a material with a specific Purchasing Group, the system will determine the
Purchasing view and the MRP view to be filled. However, you do not want to maintain the fields in the
MRP view.
Solution: In this case, you also have to provide values for some mandatory fields like Availability Check
and MRP Type in the MRP view. To avoid this, choose method 2 and select only the Purchasing view as a
view to be created.
● You want to automatically have the Storage Location view created for a material and its storage location
by migrating its inventory stock.
Solution: You need to explicitly set the maintenance status for the Storage Location (L) on the Plant
Data level (also refer to SAP Note 62913 ).
Tasks

Explorer.

Post-Processing
Follow-On Activities
You can use the Material - extend existing record with long text [page 158] migration object to migrate
material-related long texts
You can use the Material - Forecast planning [page 148] migration object to migrate material consumptions and
forecast values (only supported for on premise).
Transaction MM50 Material List
1.52 Product classification - Legal control
Purpose
Business Object Component/Area International Trade Classification (SLL-ITR-CLS)
Business Object Definition You can use this migration object to classify products for le
gal control. This includes the assignment of control classes
and control groupings as well as the setting of the control
relevance.
In Scope

Out of Scope
It is not possible to maintain the validity start and validity end of the product classification. The validity is
derived from the control class.
Supported Features
● Legal Control Classification Data
Prerequisites
Required business role:
● Trade Classification Specialist (SAP_BR_TRD_CLS_SPECIALIST)
The following data must have already been set up:
● Legal Regulation
● Control Classes (if used in the template)
● Control Groupings (if used in the template)
Level Name
1 Legal Control Classification (mandatory)
Tasks

Explorer.

Post-Processing
App: Display Classified Products
Business Role: Trade Classification Specialist

(SAP_BR_TRD_CLS_SPECIALIST)
Further Information
International Trade
1.53 Material - extend existing record with long text
Purpose
Business Object Definition You can create different long texts for a material. The key for
long texts is built with text object, text name, text ID and lan
guage key. The text object and text name are provided by the
migration object itself. The text ID defines the various types
of texts relating to a text object. The following table defines
which combinations are permitted for material long texts.
Text Object Text ID
MATERIAL BEST (Purchase order text)

Text Object Text ID
MATERIAL GRUN (Basic data text)
MATERIAL IVER (Internal comment)
MATERIAL PRUE (Inspection text)
MDTXT LTXT (Material memo)
MVKE 0001 (Sales text)
In Scope
1. Material long texts:

Purchase order text, basic data text, internal note, inspection text.
2. MRP long texts:
You can only transfer MRP long texts in the language which is assigned to the plant.
3. Sales long texts
Supported Features
● Material Long Text

● MRP Long Text
● Sales Long Text
Prerequisites
Level Name
1 Material (mandatory)

Level Name
2 Material long text
2 MRP long text
2 Sales long text
Tasks

Explorer.
Post-Processing
1.54 Material determination
Purpose
Business Object Component/Area SD-MD-MM-DET

Business Object Definition Material determination enables you to carry out the follow
ing tasks during sales order processing:
● Automatically substitute materials

● Automatically determine and offer the user a selection
of products based on predefined conditions
In Scope
Supported Features
● General Data
Prerequisites
Level Name
1 Material Substitution (mandatory)
Please refer to the field tooltips of the template file for further information.
Tasks

Explorer.

Post-Processing
Transaction VB11 Create Material Substitution
Transaction VB12 Change Material Substitution
Transaction VB13 Display Material Substitution
1.55 Material
Purpose
Business Object Definition Logistics Basic Data (LO-MD)
The total of all material master records.
A company manages the data on all its materials in the ma

terial master.
In Scope
1. Initial Load of Material Master

2. Split Data Load of Material Master
If you want to save time and load your material master days or weeks before your cutover, you can load the
“pure” material master, without valuation master data, as a first step. Later, you can use the Material -
extend existing record by new org levels [page 150] migration object to migrate the valuation data. This
could also be very helpful if you, for example, migrate Bill of Material objects (Material BOM) where the

material master is a prerequisite. Since the valuation values continue to change until the cutover, they
should be migrated shortly before go live. You can save time by stretching the timeline for the data
migration.
3. Basic Data
4. Plant Data
5. Storage Location
6. Accounting Data
 Note
The valuation data is a prerequisite for loading the stocks with the Material inventory balance [page
131] migration object as the system will calculate the values of the stock posting with the price data
provided in the material master.
In the case of Single Batch Valuation, please follow the mapping instructions provided.
7. Sales Data
8. Description Data
In this view, you can maintain additional descriptions (for languages other than those provided on the Basic
Data sheet).
9. Units of Measure Data
In this view, you can enter Alternative Units of Measure (provide only the Base Unit of Measure on the Basic
Data sheet).
10. Tax Classifications
In this view, you can maintain the Tax data (from Sales Org Data 1) and the Tax indicator for material
(Purchasing).
For Tax Data (Sales), provide the country, the tax category and the tax classification. If you have more than
one tax category for a country, use the Tax category 2/Tax classification 2 fields and, further on, the Tax
classification sheet to provide the additional tax data.
For Tax indicator for material (Purchasing), enter the value in the Tax indicator for material field on the Tax
classification sheet for the country relating to your plant.
11. Maintenance Status Settings (maintain the views for your materials).
For more details, see the Maintenance Status Settings section under Mapping Instructions below.
12. Warehouse Number Data
13. Storage Type Data
14. Production Resource Tool (PRT) Fields in the Material Master
15. Data Transfer for Forecast Values
16. Data for Quality Management
17. Additional EANs
Out of Scope
1. Internal numbering is not supported

2. Material long text (therefore, use the Material - extend existing record with long text [page 158] migration
object)
3. Data Transfer for Unplanned Consumption
4. Data Transfer for Total Consumption of Material

5. Enhance already existing data. If you want to enhance an already existing material use the Material - extend
existing record by new org levels [page 150] migration object.
Supported Features
● Basic Data
● Plant Data
● Storage Location Data
● Accounting Data
● Sales Data
● Description Data
● Unit of Measure Data
● Tax Classification Data
● Warehouse Number Data
● Storage Type Data
● Production Resource Tool (PRT)
● Forecast Parameters
Prerequisites

● Supplier [page 238] (Manufacturer)
● Be aware of the defined length set for the material number in the system. Do not convert a material
number to a new number longer than the defined length set.
● If the Material ID is to be used for integration with external systems, it can be switched on during migration.
In this connection, you must also maintain the Business System ID of your source system (to be used for
integration) in the Convert Values step, to ensure that the key mapping will be added to the central key
Indicator material is configurable

Consider the following: If you are dealing with the KMAT - Configurable materials material type, the system will
always set this indicator. In this case, the Item category will also be defaulted if you do not support this on the
migration template. For KMAT materials the procurement type will always be set to E - In-house production.
If you want to set the indicator material as configurable for materials with other material types assigned (not
KMAT), you have to enter this indicator on the Basic Data sheet in the Material is configurable field.

Batch Management requirement indicator
Starting with SAP S/4HANA Cloud release 1802, you can specify whether batch management at plant level is
active by default or not. You can maintain this setting via the SSCUI. Therefore, open the Manage Your Solution
app, and choose Configure Your Solution. The Specify Batch Management Default by Plant setting allows you to
activate or deactivate batch management by default for specific plants.
During the migration process, the logic is as follows:
If your material is managed in batches, set the Batch management requirement indicator under Multiple View
Data on the Basic Data sheet of the migration template. If you fill out this field, the system will set the Batch
management requirement indicator automatically for all plants defined on the Plant Data sheet for this material.
This is applicable for all plants that are not flagged with the Batch Management not active by default indicator in
the SSCUI .
Recommendation on how to handle cross-plant material status and plant-specific material

status
If you set the material status during initial load of the materials, do consider that, depending on which status
you want to assign, follow-on migration objects can't be posted, as the posting may lead to an error depending
on the settings of the status.
Example: in SAP standard delivery, the material status 01 is configured in such a way that, during posting of
inventory, you will receive an error message. Consider that by assigning this status, the use of the material can
be restricted. Depending on the status, the system issues either a warning message or an error message for
follow-on postings. Therefore, SAP recommends that you consider this field carefully so that you will not run
into follow-on problems during the data migration process. You can easily set the content of these fields after
the initial data migration, using the Manage Mass Maintenance – Products app.
The Master Data Specialist for Product Data business role (SAP_BR_PRODMASTER_SPECIALIST) provides you
with several tiles to manage and start the Manage Mass Maintenance – Products app. The app can be launched
from the SAP Fiori launchpad. You can import a file with changed data (supported formats are Comma-
Separated Values (CSV) and Office Open XML spreadsheet (XLSX). You have to provide the following details:
● which master data objects are to be updated.

● which tables and fields are to be updated, and the respective values.
 Note
For further information, refer to the online documentation of the Manage Mass Maintenance – Products
app.
Single Batch Valuation
Single Batch Valuation enables you to valuate stocks of material for each batch in a different way. You can use it
if you want to keep the price and value of each individual batch in inventory management on a value basis.
To work with valuation for a single batch, you must choose valuation category X - for Automat. Batch. Provide
this on the Accounting Data sheet in the Valuation Category field.
 Note
The material itself needs to be managed in batches, therefore you have to provide the Batch management
requirement indicator on the Basic Data sheet.

If you use the single batch valuation for your material, you have to enter the valuation records as follows:
● You have to define a valuation header record with specified valuation category X, and an initial valuation
type and a dependent record for each valuation type (one valuation type for each batch) with the
respective price information.
For example:
A001 1010 X (Automat. Batch)
 Note
For the valuation header record, only price control V - moving average price is possible. For the dependent
records for each valuation type, you can choose between moving average price or standard price.
Split Valuation
Split valuation enables you to valuate stocks of material in the same valuation area, in different ways. If you use
the split valuation for your material, you have to enter the valuation records as outlined below.
Define a valuation header record with a specified valuation category and an initial valuation type as well as a
dependent record for each valuation type.
For example:
A001 1010 H (Origin)
A001 1010 Domestic H (Origin)
A001 1010 Foreign H (Origin)
Level Name
2 Plant Data
3 Storage Location Data
3 Forecast Parameters
3 Production Resource Data
2 Warehouse Number Data
3 Storage Type Data
2 Accounting Data
2 Sales Data

Level Name
2 Material Descriptions
2 Alternative Units of Measure
2 Additional EANs
2 Tax Classification
1 Maintenance Status Settings
Maintenance Status Settings

As well as the organizational-dependent data, the material master data is also organized via so called views
(Basic, Purchasing, Accounting view, and so on). These views are represented as tabs in your SAP Fiori app and
as material master transactions (MM01, MM02, MM03) in the on-premise system. Fields can be assigned to
multiple views. The Purchasing Group field, for example, is assigned to both the Purchasing and the
Manufacturing views. Each view may have different mandatory fields to maintain. A view is assigned a specific
letter. For example, the MRP view has the letter D whereas the Basic Data view has letter K assigned. A
combination of letters, that represents the available views for a specific material, is stored in a field called
Maintenance Status. The maintenance status can be defined differently for the following sheets in the
Administrative Data field group of the migration object template:
● Basic Data
● Plant Data
You always have to provide the material maintenance status, we do not support an automatic maintenance
status determination.
There are two different procedures to define the maintenance status that should be available for a specific
material:
1. You, yourself, define the views to be created via the Maintenance Status Settings worksheet/tab of your
migration object template.
○ Here, you define a name for your view definition in the Material Views field. For example:
○ BASIC_HAWA to define the overall maintenance status for material of the type trading goods
(Handelsware, HAWA) and
○ PLANT1_HAWA to define the maintenance status for the plantspecific data for materials of that
type (for plant PLANT1).
○ PLANT2_HAWA to define the maintenance status for the plantspecific data for materials of that
type (for plant PLANT2).
○ For each view you want to create, you must enter an X in the specific Material Views column of that
worksheet/tab.
○ For example: BASIC_HAWA
○ Basic Data = X
○ Sales Data = X
○ MRP Data = X
○ Storage Data = X
○ For example: PLANT1_HAWA
○ Sales Data = X

○ For example: PLANT2_HAWA
○ MRP Data = X
○ Storage Data = X
○ You then fill the Material Views field on the Basic Data worksheet/tab with BASIC_HAWA for all trading
goods materials of type HAWA. You also fill the Material Views field on the Plant Data worksheet/tab
with PLANT1_HAWA for all trading goods materials of type HAWA for plant PLANT1, and with
PLANT2_HAWA for plant PLANT2. You must always provide values for both fields. As a result, only the
selected views are created for these materials.
2. If you are familiar with maintenance status and the specific letters, or if the data source is an extract of a
prior SAP ERP System, you can fill the following fields directly with the respective data from the SAP ERP
source table's Maintenance Status field (PSTAT). In this case, it is not necessary to maintain both the
Maintenance Status Settings worksheet/tab and the Material Views source field.
○ Material Maintenance Status field on the Basic Data worksheet/tab.
○ Plant Maintenance Status on the Plant Data worksheet/tab.
○ Possible values and combinations of these:
○ A = Work Scheduling;
○ B = Accounting;
○ D = MRP;
○ E = Purchasing;
○ F = PRT;
○ G = Costing;
○ K = Basic;
○ L = Storage;
○ P = Forecast;
○ Q = QM;
○ S = Warehouse management;
○ V = Sales.
○ For example: BEKLV.
More details on the maintenance status can be found in SAP Note 2145027 .
 Note
If you maintain the status using method 1 or 2, only the selected views will be created.
For example: You maintain the status for Basic Data (K) and Sales Data (V), but not for Accounting Data (B).
You maintain values for fields on the Accounting Data worksheet/tab. As a result, the status for the
Accounting view will not be set.
Additional examples:
● If you want to create a material with a specific Purchasing Group, the system will determine the Purchasing
view and the MRP view to be filled. However, you do not want to maintain the fields in the MRP view.

Solution: In this case, you also have to provide values for some mandatory fields like Availability Check and
MRP Type on the MRP view. To avoid this, choose procedure 2 or 3, and select only the Purchasing view as a
view to be created.
● You want to automatically have the Storage Location view created for a material and its storage location by
migrating its inventory stock.
Solution: You need to explicitly set the maintenance status for the Storage Location (L) on the Plant Data
level (see also SAP Note 62913 ).
Tasks

Explorer.
Post-Processing
You can use the Material - extend existing record with long text [page 158] migration object to migrate material
related long texts.
You can use the Material - Forecast planning [page 148] migration object to migrate material consumptions and
forecast values (only supported for on-premise solution).
You can use the Product classification - Commodity code [page 147] migration object to migrate product
classification with commodity code.
Transaction MM60 Material List
1.56 Xceptional case - Material price chng for global currencies

Purpose
Business Object Component/Area Actual Costing/Material Ledger (CO-PC-ACT)
Business Object Definition During migration of material master, the system will create
the accounting data (prices and values) for the company
code currency. For other deviant currencies (for example,
group currency) the system converts the currency using the
current exchange rate defined in the system. If this is not the
original price, you can use this migration object to change
the price for the other deviant currencies.
If you have to change your price, it is recommended that you

do this before you migrate your material inventory balance.
 Note
The system will post a price change document and, if
stock of the material exists, a revaluation posting will be
created.
In Scope
Out of Scope
1. Split valuation is not supported for Cloud
Supported Features
● Material
● Valuation Area
● Valuation Type
● Price Data
● Prices

Prerequisites

Level Name
1 Header Data (mandatory
2 Price Data (mandatory)
Tasks

Explorer.
Post-Processing
Transaction MR21 Price Change
1.57 Cash memo record

Purpose
Business Object Component/Area Financial Accounting (FI)-Cash Management
Business Object Definition Memo Record is used by cash manager to log the expected
outgoing and incoming payments that are not logged into
the SAP system via various postings.
In Scope
Supported Features
● Cash memo record
Prerequisites
If the source symbol for planning level is BNK (Bank Accounting) for example if planning level is AB, then in that
case Bank account should be existing in the system before creating memo record.
Level Name
1 Cash memo record data (mandatory)
Tasks

Explorer.

Post-Processing
Transaction FF65 List of Cash Management Memo Records
1.58 Condition record for pricing in purchasing
 Restriction
This migration object may only be used for migration in the context of SAP Best Practices.
Purpose
Business Object Component/Area Condition record for pricing in purchasing.

data from the price conditions, for example in sales and dis
tribution. Prices, surcharges, and discounts are determined
Business Object Definition The term pricing is used broadly to describe the calculation
In Scope

The following price conditions are supported:
1. Prices for application M - Purchasing (including scales)
Out of Scope
1. Sales conditions (see migration object Condition record for pricing in sales [page 219])
Supported Features
● This object is strictly restricted to the key field combinations mentioned in 2332748 ( SAP S/4HANA
Supported combinations of key fields for price conditions).
● For other key combinations you must use the Condition record for pricing (general template) [page 55]
migration object.
Prerequisites

Level Name
1 Pricing condition records (mandatory)
2 Scales
For more information on how to fill out the condition keys please refer to SAP Note 2332748 .
Tasks

Explorer.

Post-Processing
Transaction MEK3 Display Conditions (Purchasing)
Examples
1,000 EA 100,00000 EUR
100,000 EA 90,00000 EUR
Example of a Scale-Based on Gross Weight:
1,000 KG 100,00000 EUR
100,000 KG 90,00000 EUR
1.59 QM - Master inspection characteristic
Purpose

Business Object Definition Characteristic on the basis of which an inspection is per
formed.
For inspection characteristics a distinction is made between

qualitative and quantitative characteristic types. Inspection
characteristics are often quality characteristics, but that
does not necessarily have to be the case.
In Scope
Supported Features
● General Data
● Characteristic Control Indicators
● Assign Inspection Methods
● Assign Inspection Catalogs
● Long Texts
Prerequisites

● QM - Inspection method [page 124]

Level Name
1 Master Insp. Char. Basic Data (manda

tory)
2 Insp. Methods or Insp. Char.
2 Charact. Control Indicators (manda

tory)
2 Master Insp. Char. Short Texts (manda

tory)
2 Master Insp. Char. Long Texts

● The version of the master data will be created as '000001'.
● The object only supports the assignment of one catalog, with type '1' (Characteristic attributes only).
● Text line in master inspection characteristic long texts
For each master inspection characteristic, there may be several languages here, but for each language, there is
only one text line in the source file.
The object will separate the text line into several lines automatically into the long texts for each language.
Tasks

Explorer.
Post-Processing
Transaction QS21 Create master insp. characteristic
Transaction QS22 Create Master Insp. Charc Version
Transaction QS23 Change master insp. charac. version
Transaction QS24 Display master insp. charac. version

1.60 JIT - Customer
Purpose
Business Object Component/Area LE-JIT
Business Object Definition Customer Master enables you to manage Customer Data
and receive Just-In-Time requests from these customers.
In Scope
1. Migration of Basic Data

2. Migration of Destinations
3. Migration of External Status Mapping
4. Migration of Additional Reference Text
Supported Features
● Basic Data
● Destinations
● External Status Mapping
● Additional Reference text
Prerequisites

Level Name
2 Destinations
2 External Status Mapping
2 Additional Reference text
Tasks

Explorer.
Post-Processing
App: Manage JIT Customer Data
1.61 PA - Catalog item

Purpose
Business Object Component/Area Patient Accounting (IS-PM-PA)
Business Object Definition Catalog item: Entry in a catalog in Patient Accounting
For example, a catalog entry could represent a service or a

procedure. A catalog item can have the following attributes:
● Unique identification
● Name of catalog entry
● External identification
In Scope
1. Create catalog item.

2. Create texts for the catalog item.
3. Create columns for the catalog item.
Out of Scope
1. New catalog cannot be created

2. Existing catalog item cannot be maintained. It should be maintained by transaction NT02 (Change Catalog
Item ).
Supported Features
● Catalog Item
● Texts
● Columns

Prerequisites
● Institution
● Catalog
● Service Catalog Column Information
Level Name
1 Catalog item (mandatory)
2 Texts
2 Columns
Catalog Item Tab
The External ID field is the ID for this catalog item in your institution. It must be unique in the catalog it belongs
to.
The Unit data is mandatory for a service (esp. EBM).
The Unit data must be entered in ISO format.
Texts Tab
If a text row is created, the short description field is mandatory, and it should be no more than 120 characters.
If the comment field is longer than 30 characters, a long text will be created.
Tasks

Explorer.

Post-Processing
Transaction NT03 Display Catalog Item
1.62 FI - Accounts payable open item
Purpose
Business Object Definition Open items are those items that are not yet to be cleared.
This document describes how to load the Accounts Payable

open items also known as Vendor open items.
In Scope
1. Restricted migration of deferred taxes: only invoice, debit memo, and credit memo are supported
Out of Scope
1. Multiple vendor line items per document post

3. Open tax items (must be settled before data migration. Exception: Deferred tax)

5. Migration of down payment with deferred tax code, composite deferred tax code, for example, VAT + Sales,
reverse charge, etc.
6. The mass migration of Accounts Payable open items with special G/L indicator referring to special G/L
type 'W' is generally not supported. Nor is special G/L indicator leading to noted item. These data must be
posted manually in financial accounting. All other special GL indicators ARE supported.
Supported Features
● Header
● Vendor Item
● One-Time Account Data
● Tax Item
● Withholding Tax Item
● Currency Item
Prerequisites
possible)

Note that posting on tax jurisdiction will be automatically derived by cost center. Therefore, the tax
jurisdiction code must be already maintained for cost center master.
Note that posting on tax jurisdiction will be automatically derived by profit center. Therefore, the tax
jurisdiction code must be already maintained for profit center master.

Dependencies
Please bear in mind that no documents will be migrated. Only balances and open items will be taken over.
accounts in the source system. By reducing these open items, you will reduce the amount of variables resulting
in a lower possibility of error as well as reducing the amount of reconciliation needed to verify the data
migration.
From the bank account, only the balance needs to be migrated.
From the tax accounts, no items and no balances would normally need to be migrated because they are usually
at balance zero (for normal VATs) when the migration takes place. We assume that the tax transfer has already
been done and, therefore, that no tax has to be migrated. Exception: Deferred taxes can be migrated with the
migration activities for open items payable and open items receivable.
● Enter only one line per document post into the migration file. The offsetting entry will be generated
automatically for the offsetting G/L account.
● The combination of key fields Company Code + Reference Document Number + Line Item Number + Vendor
Number are used for duplicate check. Data records with this combination should be unique in the
migration template. Otherwise, the migration tool will display a duplicate error message. The Line Item
Number will just be used as an additional key field and will not be migrated.
● Please be careful to fill and save value amounts in the migration file in number and not in string format.
Check the settings for a delimiter.
For migration, the posting keys are always derived based on the account type and on the special GL
indicator that is submitted in the line item. Additionally, the posting keys are controlled by the sign in the
amount fields. The sign for negative values should be set at the beginning:
○ A negative value will use posting key 31 (Invoice) for vendor and 40 (Debit entry) for Offsetting G/L
Account (only without special GL indicator).
○ A positive value will use posting key 21 (Credit memo) for vendor and 50 (Credit entry) for Offsetting
G/L Account (only without special GL indicator).
 Note
During migration of credit memo line item, the Invoice Reference field will be automatically set by
the BAPI to 'V'. This is hard coded and can not be changed.
● The initial offsetting (transfer booking) accounts to be used in the open items and open balances migration
objects are described in the BH5 test script :

Deferred Tax
For posting of an invoice with deferred taxes, it is necessary to provide a tax account, tax code, tax amount and
a tax base amount via the migration template.
The sign of the tax amounts and tax base amounts must be opposite to the amounts of the vendor item.
If there is at least one deferred tax code in an invoice then full tax information including non-deferred taxes
should be provided in the migration template. This is necessary for a correct proportion calculation.
Two approaches for currency and amount
adopted from the template regardless of the existing exchange rates in the system.
In the template, keep the second local/group currency field and the related amount empty. In this case, the
amount will be automatically calculated by valid exchange rates in the system.
defined in the customizing for each company code (in SPRO via "Change Foreign Currency Translation").
Payment Term / Payment block
If a default payment block is assigned to a payment term, then the open item will be blocked accordingly. This
also happens if the value for payment block is not provided via the template. Use a payment term without a
default payment block to avoid an automatic payment block for the migrated open item.
Alternative Reconciliation Account
In order to use this field, the following IMG activity must be predefined: Financial Accounting Accounts
Receivable and Accounts Payable Business Transactions Posting with Alternative Reconciliation Account
Define Alternative Reconciliation Accounts .
Level Name
Tasks

Explorer.

Post-Processing
The total balance of all migration clearing accounts, which are used for the offsetting postings, must be zero.
To ensure this, the offsetting amounts for the migration clearing accounts must be balanced with the initial G/L
offsetting account for data migration. This can be done with the FI - G/L account balance and open/line item
 Note
For Deferred Tax:
● Check entries in the DEFTAX_ITEM table

● Program RFUMSV50 for deferred tax transfer
1.63 FI - Accounts receivable open item
Purpose
Business Object Definition Open items are items that are not yet to be cleared.
This document describes how to load the Accounts Receiva

ble open items also known as Customer open items.
In Scope

1. Restricted migration of deferred taxes: only invoice, debit memo, and credit memo are supported.
Out of Scope
1. Multiple customer line items per document post.

2. External accounting document number.
3. Open tax items (must be settled before data migration. Exception: Deferred tax).
5. Migration of down payment with deferred tax code, composite deferred tax code, for example, VAT + Sales,
reverse charge, etc.
6. The mass migration of Accounts Payable open items with special G/L indicator referring to special G/L
type 'W' is generally not supported. Nor is special G/L indicator leading to noted item. These data must be
posted manually in financial accounting. All other special GL indicators are supported.
Supported Features
● Header
● Customer Item
● One-Time Account Data
● Tax Item
● Withholding Tax Item
● Currency Item
Prerequisites
possible)


Posting on tax jurisdiction will be automatically derived by cost center. Therefore, the tax jurisdiction code
must be already maintained for cost center master.
Posting on tax jurisdiction will be automatically derived by profit center. Therefore, the tax jurisdiction code
must be already maintained for profit center master.
Dependencies
Please in keep in mind that no documents will be migrated. Only balances and open items will be taken over.
accounts in the source system. By reducing these open items, you will reduce the amount of variables resulting
in a lower possibility of error as well as reducing the amount of reconciliation needed to verify the data
migration.
From the bank account only the balance needs to be migrated.
From the tax accounts, no items and no balances would normally need to be migrated because they are usually
at balance zero (for normal VATs) when the migration takes place. We assume that the tax transfer has already
been done and, therefore, that no tax has to be migrated. Exception: Deferred taxes can be migrated with the
migration activities for open items payable and open items receivable.
● Enter only one line per document post into the migration file. The offsetting entry will be generated
automatically for the offsetting G/L account.
● The combination of key fields Company Code + Reference Document Number + Line Item Number + Vendor
Number are used for duplicate check. Data records with this combination should be unique in the
migration template. Otherwise, the migration tool will display a duplicate error message. The Line Item
Number will just be using as additional key field and will not be migrated.
● Please be careful to fill and save value amounts in the migration file in number and not in string format.
Check the settings for a delimiter.
For migration, the posting keys are always derived based on the account type and on the special GL
indicator that is submitted in the line item. Additionally, the posting keys are controlled by the sign in the
amount fields. The sign for negative values should be set at the beginning:
○ A negative value will use posting key 31 (Invoice) for vendor and 40 (Debit entry) for Offsetting G/L
Account (only without special GL indicator).
○ A positive value will use posting key 21 (Credit memo) for vendor and 50 (Credit entry) for Offsetting
G/L Account (only without special GL indicator).

 Note
During migration of credit memo line item, the Invoice Reference field will be set automatically by
the BAPI to 'V'. This is hard coded and can not be changed.
● The initial offsetting (transfer booking) accounts to be used in the open items and open balances migration
objects are described in the BH5 test script :
Deferred Tax
For posting of an invoice with deferred taxes it is necessary to providea tax account, tax code, tax amount and a
tax base amount via the migration template.
The sign of the tax amounts and tax base amounts must be opposite to the amounts of the vendor item.
If there is at least one deferred tax code in an invoice, then full tax information including non-deferred taxes
should be provided in the migration template. This is necessary for a correct proportion calculation.
Two approaches for currency and amount
adopted from the template regardless of existing exchange rates in the system.
In the template, keep the second local/group currency field and the related amount empty. In this case, the
amount will be automatically calculated by valid exchange rates in system.
defined in the customizing for each company code (in SPRO via "Change Foreign Currency Translation").
Payment Term / Payment block
If a default payment block is assigned to a payment term, then the open item will be blocked accordingly. This
also happens if the value for payment block is not provided via the template. Use a payment term without a
default payment block to avoid an automatic payment block for the migrated open item.
Alternative Reconciliation Account
In order to use this field, the following IMG activity must be predefined: Financial Accounting Accounts
Receivable and Accounts Payable Business Transactions Posting with Alternative Reconciliation Account
Define Alternative Reconciliation Accounts .
Level Name

Tasks

Explorer.
Post-Processing
The total balance of all migration clearing accounts, which are used for the offsetting postings, must be zero.
To ensure this, the offsetting amounts for the migration clearing accounts must be balanced with the initial G/L
offsetting account for data migration. This can be done with the FI - G/L account balance and open/line item
 Note
For Deferred Tax:
● Check entries in table DEFTAX_ITEM

● Program RFUMSV50 for deferred tax transfer
1.64 Profit center

Purpose
Business Object Component/Area Profit center (FI)
Business Object Definition An organizational unit in accounting that reflects a manage

ment-oriented structure of the organization for the purpose
of internal control.
In Scope
Supported Features
● Basic Data
● Indicator
● Address Data
● Communication
● Company Codes
Prerequisites
● Groups for Profit center
These fields are mandatory fields:
● Profit Center
● Controlling Area
● Valid from Date
● Valid to Date
● Profit Center Text
● Person Responsible
● Profit Center Group

Level Name
1 Profit center master data (mandatory)
2 Company code assignment
Language in Which Text is Saved
The LANGU field shows the language in which text is saved. The Profit Center name and description will be
saved according to the entry in the LANGU field. If the field is not completed, the text will be saved in the user
logon language as the default language. A profit center with a description in a different language is not
supported.
happens, you have to provide a more detailed/accurate address, for example, US Postal codes with 9 digits
For some addresses, Vertex will always provide more than one tax jurisdiction code. In this case, you will have to
If there is a field available in the migration object template to provide the correct tax jurisdiction within the
Hierarchy area
Profit center groups entered in the KHINR- Profit center group field must be assigned to the standard hierarchy.
If this is not the case you will get the error message Profit Center Group cannot be used.
Tasks

Explorer.

Post-Processing
Transaction KE53 Display Profit Center
1.65 Product consumption
 Restriction
You can migrate several org. levels for a specific material with one migration template of a specific project.
If you have already migrated material consumptions (org. level view) and you want to extend those
materials by additional consumptions for a different plant, please create a new project and use a new
template.
Purpose
Business Object Definition A quantity usually updated by the system when a material is
withdrawn from the warehouse or stores, indicating how
much of the material has been used or consumed over a par
ticular past period.
In Scope
1. Migration of Total consumptions

2. Migration of Unplanned consumptions

Supported Features
● Material
● Total Consumptions
● Unplanned Consumptions
Prerequisites
Tasks

Explorer.
Post-Processing
Consumption values can also be accessed via Go To Additional Data Consumption .
1.66 Production version

Purpose
Business Object Definition Key determining the various production techniques accord
ing to which a material is to be manufactured. You specify,
for example, the following in the production version:
● The BOM alternative for the BOM explosion

● The task list type, the task list group, and the group
counter for assignment to routings
● Lot-size restrictions for repetitive manufacturing
In Scope
Supported Features
● General Data
Prerequisites
● Material [page 162] (with ERP data)

● Material BOM [page 32]
● Routing [page 211]

Level Name
Task List Group
As the internal group number may be created from the object routing, in this condition, the system will map the
related internal number automatically if the external number has been provided in the template. However,
make sure the two objects routing and production version need to be used in the same project.
Tasks

Explorer.
Post-Processing
Transaction C223 Maintain Production Versions
In MM03, choose MRP 4 View ProdVersions .
Further Information
In Discrete Manufacturing, it was not necessary to have a production version for BOM explosion in the SAP ERP
suite. In this case use the CS_BOM_PORDVER_MIGRATION02 report to create a production version based on
existing BOMs and routings in the new system.

1.67 PS - Network
Purpose
Business Object Component/Area PS
Business Object Definition A network can represent the sequence of activities in a

project or the sequence of a single activity within a project. It
is used as a basis for planning, analyzing, controlling and
monitoring schedules, dates, and resources.(such as per
sonnel, machines, PRTs, materials, documents, and draw
ings).
In Scope
Supported Features
● Scheduling
● Assignments
● Control
● Text
Prerequisites

● PS - WBS element [page 242]
● Sales order (only open SO) [page 215]

Level Name
1 Network data (mandatory)
Tasks

Explorer.
Post-Processing
Transaction CN23 Display Network
1.68 PS - Project
Purpose

Business Object Definition Project definition is the general description of the project
that you want to manage. It is a framework laid down for all
the objects created within a project. It contains organiza
tional data that is binding for the entire project.
In Scope
Supported Features
● Basic Data
● Control
● Text
Prerequisites
Level Name
1 Project Definition (mandatory)
Tasks

Explorer.

Post-Processing
Transaction CJ08 Display Project Definition
1.69 Purchasing info record- extend existing record
Purpose
Business Object Definition A source of information for the procurement of a certain ma
terial from a certain supplier.
In Scope
1. Extend already existing purchasing info records with new purchasing organization or new purchasing info
record category. The following purchasing info categories are supported:
○ Standard
○ Consignment
○ Subcontracting
○ For purchasing info records to material groups, only the Standard and Consignment purchasing info
categories are supported.
2. General Data (only Legacy Number of purchasing info record, Material Number, Material Group and
Supplier's account number)

3. Purchasing Organization Data; when you create an Info Record you can choose the following options:
○ Purchasing info record which is only related to a purchasing organization. That means the price is the
same for all plants.
○ Purchasing info record which is related to a plant. That means the price can be different for each plant.
4. Conditions; the condition type indicates, for example, whether during pricing, the system applies a price, a
discount, a surcharge, or other pricing elements, such as freight costs and sales taxes. For each of these
pricing elements, there's a condition type defined in the system.
5. Scales
6. Purchasing Organization Text
Out of Scope
1. Change already existing data.

2. Create Info Record is not supported; if an info record with a certain supplier and with a specific material or
material group doesn't exist, it's not possible to create this record. Please use the following object:
Purchasing info record with conditions.
3. The Pipeline purchasing info category is not supported.
Supported Features
● General Data
● Purchasing Organization Data
● Conditions
● Scales
● Purchasing Organization Text
Prerequisites

● Purchasing info record with conditions [page 202]

Level Name
1 General Data (manda

tory)
2 Purchasing Organiza
tion Data
3 Conditions
4 Scales
tion Text
Tasks

Explorer.
Post-Processing
Transaction ME13 Display Purchase Order Info Record
Transaction ME1L Info Records per Supplier
1.70 Purchasing info record with conditions

Purpose
Business Object Definition A source of information for the procurement of a certain ma
terial from a certain vendor.
In Scope
1. General Data; only to create info record with material specific or material group
The following Info Categories are supported:
○ Standard
○ Consignment
○ Subcontracting
2. General Text
3. Purchasing Organization Data; when you create an Info Record you can choose the following options:
○ Purchasing info record which is only related to a purchasing organization. That means the price is the
same for all plants.
○ Purchasing info record which is related to a plant. That means the price can be different for each plant.
4. Conditions; the condition type indicates, for example, whether during pricing, the system applies a price, a
discount, a surcharge, or other pricing elements, such as freight costs and sales taxes. For each of these
pricing elements, there is a condition type defined in the system.
5. Scales
6. Purchasing Organization Text
Out of Scope
1. Update Info Record is not supported; if an info record with a certain vendor and with a specific material
exists or with a material group, it is not possible to enhance this record with purchasing organization data.
Supported Features
● General Data
● General Text

● Conditions
● Scales
● Purchasing Organization Text
Prerequisites

Level Name
1 General Data (manda

tory)
2 General Text
tion Data
3 Conditions
4 Scales
tion Text
Tasks

Explorer.

Post-Processing
Transaction ME13 Display Purchase Order Info Record
Transaction ME1L Info Records per Supplier
1.71 Purchase order (only open PO)
Purpose
Business Object Component/Area Purchase Order (MM-PUR)
Business Object Definition A request or instruction from a purchasing organization to a

vendor (external supplier) or a plant to deliver a quantity of
material or to perform services at a certain point in time.
 Note
You can only migrate open purchase orders, that is, items which haven't been delivered and invoiced yet.
In Scope
1. Header Data
2. Header Address
3. Header Texts
4. Item Data; the following Item Categories are supported:
○ Standard
○ Third-Party
○ Enhanced Limits
○ Consignment

○ Subcontracting
5. Item Addresses
6. Item Account Assignments; the following Account Assignment categories are supported:
○ Cost Center
○ Asset
○ Sales Order
○ Project
○ Unknown
7. Item Schedule Lines
8. Purchase Order Item Components for Subcontracting
 Note
If your ordered material is not a BOM, provide the relevant entries on the Schedule Line sheet and the
materials to be provided on the Components for Subcontracting sheet.
 Note
If your ordered material is a BOM, the system will automatically generate the subcontracting
components. You can also provide the components manually on the Components for subcontracting
sheet.
9. Item Texts
Out of Scope
1. Create configurations (you can only use existing ones)

2. Change message records (NAST table) and additional message data (this data can only be determined via
the message determination facility (Customizing))
3. Attach documents to the purchase order
4. Other item categories not mentioned above are not supported, for example, Transport Orders
5. Purchase Orders for Sales Orders and Nonstock sales [Item 1]
Supported Features
● Header Data
● Header Address
● Header Texts
● Item Data
● Item Addresses
● Item Account Assignments
● Item Schedule Lines

● Purchase Order Item Components for Subcontracting
● Item Texts
Prerequisites

● Sales order (only open SO) [page 215]
● Purchase contract [page 62]
● WBS element
● Fixed asset (incl. balances and transactions) [page 98]
● G/L account [page 114] (expense account used in account assignment category)
● Purchasing info record with conditions [page 202] (only relevant for purchase order items with item
category Consignment)
● During migration you can choose between internal and external number assignment for the purchasing
document. Item numbers will be migrated 1:1 from the data in the migration template.
● Consider: During migration there is no defaulting of values from existing purchasing info records.
Exceptional case: purchase order items with item category Consignment.
● Net Price: Please provide the price as manual price on item level. Migration of conditions for example -
discounts or surcharges - is not supported!
● The net price will be automatically set to 0, if the invoice receipt indicator hasn't been set.
● In case of Third-Party, please note the following: When you provide a customer number, the delivery
address is taken from the customer master data record. If you do not provide a customer number, you
must enter a delivery address.
● The Legacy Purchasing Document Number is mapped to the Our Reference field. You can find the content of
this field using the Display Purchase Order app under Communication.
Level Name
1 Header Data (manda

tory)
2 Header Address
2 Header Texts
2 Item Data (mandatory)

Level Name
3 Item Address
3 Account Assignment
3 Schedule Line
4 Components for Sub

contracting
3 Item Texts
Tasks

Explorer.
Post-Processing
Transaction ME23N Display Purchasing Document
Transaction ME2L Purchasing Document by Vendor
Transaction ME2K Purchasing Document by Account Assignment (General)
Transaction ME2O Subcontracting Stocks per Vendor (Subcontracting Stock

Monitor for Vendor)
1.72 QM/PM - Catalog code group/code

Purpose
Business Object Component/Area Quality Management (QM and PM)
Business Object Definition Code group: A key for summarizing code and structuring a
catalog according to various criteria. The assignment of
code to code groups takes place at client level.
Catalog type: Main category by which code groups and co

des are classified according to their contents.
● 0: Action Reasons
● 1: Characteristic attributes
● 2: Tasks
● 5: Causes
● 8: Activities (QM)
● 9: Defect types
● A: Activities (PM)
● B: Object Parts
● C: Overview of damage
● D: Coding
● E: Defect Locations
Code: A key that uniquely identifies the qualitative contents

of a problem in a coded form that can be mechanically proc
essed.
Each code is assigned to a code group in the catalog. A code

can describe:
● a characteristic attribute
● a defect type
● a usage decision
In Scope
1. Supported catalog types for QM are: 1, 2, 5, 8, 9, D, E

2. Supported catalog types for PM are: 0, 2, 5, A, B, C, D

Out of Scope
1. Classification is not supported.
Supported Features
● QM/PM Catalog Code Group

● QM/PM Catalog Short Text for Code Group
● QM/PM Catalog Long Text for Code Group
● QM/PM Catalog Code
● QM/PM Catalog Short Text for Code
● QM/PM Catalog Long Text for Code
Level Name
1 QM/PM catalog code group

(mandatory)

text (mandatory)

long text
2 QM/PM catalog code (man

datory)
3 QM/PM catalog code short

text (mandatory)
3 QM/PM catalog code long

text
Text line in Code group and Code long texts: For each Code group and Code, there may be several languages
here, but for each language, there is only one text line in the source file.
The object will separate the text line into several lines automatically into the long texts for each language.

Tasks

Explorer.
Post-Processing
Transaction QS41 Maintain catalog
1.73 Routing
Purpose
Business Object Definition Production Planning - Routing
A description of the production process used to manufac

ture plant materials or provide services in the manufacturing
industry.
In Scope
Only task list of type N (Routing) is supported with this object.

 Tip
● For task list of type Q (Inspection Plan), use the QM - Inspection plan [page 126] migration object.
● For task list of type A (General Maintenance task list), use the PM - General maintenance task list [page
110] migration object.
● For task list of type E (Equipment Task List), use the PM - Equipment task list [page 93] migration
object.
● For task list of type T (Task List for Functional Location), use the PM - Functional location task list [page
Out of Scope
Task list types other than those mentioned above aren't supported by the data migration content.
Supported Features

● Material Task List Assignment
● Sequences
● Operations
● Sub-Operations
● Component Assignment
● Production Resources/Tools
● Inspection Characteristics
Prerequisites


● For routing migration, for example, the validity period of costing view in work center must be within the
routing validity period, otherwise this will lead to an issue with the cost simulation run.
● For routing as an example, if the valid-from date on operational level starts earlier than the validity start
date of costing view in work center, this will lead to an issue with missing activity types in routing and no
cost being calculated in the cost simulation run.
● Internal/External number range assignment for Group.

○ The Group and Group Counter must be provided in the source file to distinguish different routings. For
the scenario of one Group with several Group Counters, they must be grouped logically in the source
file.
○ For external number range assignment, you must provide the number in accordance with the definition
required by the target system.
○ With the Routing, internal or external numbering control parameter in the Converted Values step of the
guided activity, you have to decide if it's internal or external during each data load.
 Note
The system doesn't support combining internal and external number ranges in one source file.
● The Valid-From Date will be the current date if no value is provided in the source file.
● The Valid-From Date for BOM must be earlier than the Valid-From Date of the Routing. Otherwise, the BOM
can't be expanded and it will return an error.
● The Numerator will be set to 1 if no value is provided in the source file.
● The Denominator will be set to 1 if no value is provided in the source file.
● The BOM Usage and BOM Application are only mandatory for component allocation.
○ The BOM Usage controls the selection of the relevant BOM in the component assignment.
○ The BOM Application, in connection with the BOM Usage, controls the selection of the correct
alternative BOMs.
● BOM Item Category, BOM Component, and BOM Component Description are just provided in the template
to help you allocate the component; this data may be copied from the BOM Data Migration file or from the
target system.
● The Indicator for Relevancy to Costing on Operation Level field is mandatory; with the following options:
○ If you want the Costing Relevancy to be copied from the Control Key on the target system, enter the
value D.
○ If you want the operation to be irrelevant to costing, enter the value N.
○ If you want to enter a value for this field, then the field should be populated with either X, or another
option, as required.
Long Text
If you create a long text in the dialog, then the current logon language will be taken as the long text language.

Any subsequent change of the long text refers to the same long text independent of the logon language.
Level Name
1 Routing group (mandatory)
2 Task list header (mandatory)
2 Material task list assignment

(mandatory)
2 Task list sequences
3 Production resources/tools
3 Sub-operations
3 Component assignment
3 Inspection Characteristics
Tasks

Explorer.
Post-Processing
It's mandatory to migrate all routing in the Q system first and run a cost simulation run in your Q system. Then,
verify the results and check for inconsistencies before starting the data migration into the productive system.
After data migration into the productive system, It's mandatory to run the cost simulation and validation steps
in that system as well.
Transaction CA03 Display Routing

1.74 Sales order (only open SO)
Purpose
Business Object Component/Area Sales and Distribution (SD)
Business Object Definition Sales Order (SD): A customer request to the company for
delivery of goods or services at a certain time. The request is
received by a sales area that is then responsible for fulfilling
the contract.
In Scope
1. Sales order header data

2. Sales order item data
3. Sales order partners data
4. Sales order schedule line data
5. Sales order texts on header and item level
6. Sales order conditions on header and item level
Out of Scope
1. Sales orders with configurable items

2. Credit card data
3. Return sales orders
Supported Features

Prerequisites

● Condition records/Sales Pricing
● The Sold-to Party and Ship-to Party on Header level must be provided in the Partner sheet using 0000 in
the Sales Document Item field.
● The total number of ordered items will be calculated based on the items in the schedule line data.
● During migration, you can choose between internal and external number assignment for the sales
document number and item numbers.
Level Name
2 Header Conditions (optional)
2 Header Texts (optional)
2 Item (mandatory)
3 Item Conditions (optional)
3 Item Texts (optional)
2 Partner (mandatory)
2 Schedule Line Data (manda

tory)
Tasks

Explorer.

Post-Processing
Transaction VA03 Display Sales Orders
1.75 Purchase scheduling agreement
Purpose
Business Object Definition An outline agreement whereby materials are procured at a

series of predefined points in time over a certain period.
In Scope
1. Scheduling agreement header

2. Scheduling agreement items
Out of Scope
1. Scheduling agreements with document conditions (only time-dependent conditions are supported)
2. Creation of delivery schedule

Supported Features
Prerequisites

Level Name
1 SAG Header Data (mandatory)
2 SAG Item Data (mandatory)
Tasks

Explorer.
Post-Processing
Transaction ME38 Maintain Sched. Agreement Schedule

1.76 Condition record for pricing in sales
 Restriction
This migration object may only be used for migration in the context of SAP Best Practices.
Purpose
Business Object Component/Area Condition record for pricing in sales.

data from the price conditions, for example, in Sales and Dis
tribution. Prices, surcharges and discounts are determined
Business Object Definition The term pricing is used broadly to describe the calculation
In Scope
The following price conditions are supported:
1. Prices
2. Discounts
3. Surcharges (including scales)
Out of Scope
1. Purchasing conditions (see migration object Condition record for pricing in purchasing [page 173])

Supported Features
● This object is strictly restricted to the key field combinations mentioned in SAP Note 2332748 .
● For other key combinations you must use the Condition record for pricing (general template) [page 55]
migration object.
Prerequisites

Level Name
1 Sales condition records (mandatory)
2 Scales
For more information on how to fill the condition keys, please refer to SAP Note 2332748 .
Tasks

Explorer.
Post-Processing
Transaction VK13 Display Condition

Examples
1,000 EA 100,00000 EUR
100,000 EA 90,00000 EUR
Example of a Scale Based on Gross Weight:
1,000 KG 100,00000 EUR
100,000 KG 90,00000 EUR
Example of a Value Scale:
Scale value Scale currency Scale percentage
100,000000 EUR 5,000000
1000,000000 EUR 10,000000
1.77 Sales contract
Purpose
Business Object Component/Area Sales and Distribution (SD)
Business Object Definition An outline sales agreement that contains special conditions
negotiated between the vendor and a customer, for example,
price, target value or target quantity. A sales contract is valid
for a specified period. A customer submits a sales order to
release products from the amount agreed in the contract.
Types of sales contract include value contracts and quantity
contracts.

In Scope
1. Sales contract header

2. Sales contract item
3. Sales contract partner
Out of Scope
1. Sales contract with configurable products

2. SD scheduling agreements are not supported.
Supported Features
Prerequisites

● Condition record for pricing (general template) [page 55]
Level Name
1 Header Data (mandatory)
2 Additional Header Partners
2 Item (mandatory)
3 Item Partners

Tasks

Explorer.
Post-Processing
Transaction VA43 Display Contract
1.78 QM - Selected set
Purpose
Business Object Definition Selected Set/Select Set Code
Quality Management (QM)
A range of specific entries (code groups and codes) of a cat

alog. A selected set enables you to choose only those code
groups and codes of a catalog that are required, or allowed,
for a specific purpose.
In Scope

Supported Features
● Inspection Catalog Selected Set

● Long Txt Lines for Insp. Method/Master Insp. Char
Prerequisites
Level Name
1 QM selected set master data (mandatory)

Text line in Selected set long texts: For each Selected set, there may be several languages here, but for each
language, there is only one text line in the source file. The object will separate the text line into several lines
automatically into the long texts for each language.
Tasks

Explorer.
Post-Processing
Transaction QS51 Edit Selected Sets

Transaction QS52 Display selected set index
1.79 QM - Selected set code
Purpose
Business Object Definition Selected Set/ Selected Set Code
Quality Management (QM): A range of specific entries (code

groups and code) of a catalog. A selected set enables the
user to choose only those code groups and code of a catalog
that are required or allowed for a specific purpose.
In Scope
Supported Features
● Inspection Catalog Code for Selected Set
Prerequisites


Level Name
1 QM selected set code master data (mandatory)
Tasks

Explorer.
Post-Processing
Transaction QS51 Edit Selected Sets
Transaction QS52 Display selected set index
1.80 Source list
Purpose
Business Object Component/Area Source List (MM-PUR)

Business Object Definition A list of available sources of supply for a material, indicating
the periods during which procurement from such sources is
possible.
The source list lets you determine the source that is valid (ef
fective) at a certain time.
In Scope
Supported Features
● Purchasing Source List
Prerequisites

● Agreements
There are two types of outline purchase agreement:
○ Purchase contract [page 62]
○ Purchase scheduling agreement [page 217]
If a successor object is created with a validity period starting before this object, it will normally cause an error
You therefore must check such time dependencies before you create or migrate your objects. This will avoid

Level Name
1 Purchasing Source List (mandatory)
Tasks

Explorer.
Post-Processing
Transaction ME03 Display Source List
1.81 PSS - Substance
Purpose
Business Object Definition A substance as a chemical element or a chemical compound

with parts that can only be separated from each other by
chemical reaction, that is used in a company

In Scope
Out of Scope
1. Substance groups
2. Attachments
Supported Features
● Basic Data
● Company Specific Names
● Conditions
Prerequisites
Listed substance must exist ( Manage Listed Substance app) and responsible unit must be configured
(Customizing).
Level Name
2 Company specific names
2 Conditions
Preparation of Migration Details for Company Substance

Process the migration in two options:
1. Migrate a substance linked to an existing listed substance using the following data from the migration
template:
○ Internal Number
○ Internal Name

○ Listed Substance
○ Responsible Unit
2. .
Migrate a substance linked to an new listed substance using the following data from the migration
template:
○ Internal Number
○ Internal Name
○ Listed Substance Name
○ CAS Number
○ EC Number
○ Molecular Formula
○ Responsible Unit
Tasks

Explorer.
1.82 Software/Hardware constraint
Purpose
Business Object Component/Area Product Lifecycle Management (PLM)
Business Object Definition Constraints maintained for a software material to define the
compatibility relationships between this software material
and other materials (such as a bill of materials). A software/
hardware constraint includes a constraint rule, materials
that have a compatibility relationship with the subject soft
ware material, and versions of the software material.

In Scope
Supported Features
● Software Material
Prerequisites
Business objects that must already be entered or migrated in the system:
Level Name
1 Software material (mandatory)
2 Constraint (mandatory)
Tasks

Explorer.

Post-Processing
App: Manage Software Constraints
Business Role: Systems Engineer - Overhead

(SAP_BR_SYSTEMS_ENGINEER))
1.83 Supplier - extend existing record by new org levels
Purpose
Business Object Component/Area Logistics - General (LO-MD-BP, LO-MD-BP-VM)
Business Object Definition A supplier is a business partner who supplies goods and de
livers them to consumers/customers.
The supplier is a frequently-used master data object, used

by almost all business applications. In an SAP ERP system it
is called a vendor.
At SAP, there are different object models for the supplier:
● In the traditional SAP ERP system, the vendor master

data is used.
● In all new strategic applications, such as SAP SRM and
many industry solutions, the Business Partner ap
proach is used.
In Scope
1. Extend already existing suppliers with new org levels and extend already existing customers/contract
partners as supplier with the same number

2. General data (only fields which might become relevant when you extend a customer/contract partner as
supplier)
3. BP Roles
5. General texts
6. Company data
7. Withholding tax data
8. Company texts
9. Purchasing organization data
10. Purchasing partner functions
11. Purchasing texts
12. Bank data
13. Industries
14. Tax numbers
16. Contact persons
17. Address data including telephone numbers, fax number, email and URL
Out of Scope
1. No updates of existing fields

2. Withholding tax data can only extend with related company data. It is not possible to extend withholding
tax data for an already existing company code.
3. Purchasing partner functions can only extend with related purchasing organization data. It is not possible
to extend purchasing partner functions for an already existing purchasing organization.
 Note
This migration object is based on the assumption that business partner and supplier are using the same
Supported Features
● General Data
● BP Roles
● General Texts
● Company Data

● Company Texts
● Partner Functions
● Purchasing Texts
● Bank Details
● Industries
● Tax Numbers
● Contact Persons
Prerequisites

● Customer [page 75]: If you extend already existing customers as supplier with the same number.
● Bank [page 24]
General Data
On the General Data sheet we only offer fields which might become relevant when you extend already existing
customers as supplier with the same number. If you want to extend an existing customer as supplier with the
same number, you have to fill out the customer number (reference number). You also have to fill the BP Roles
sheets. If you want to extend an already existing supplier by new org levels, you have to leave the reference
number empty.
Please consider: You can't transfer a value in one of the fields provided on the General Data sheet when the
supplier already exists.
During the use Supplier ID for integration with external systems step in the Convert Values task, you can switch
on the key mapping for the Supplier ID to be used for integration with external systems. In connection with this,
you must also maintain the Business System ID of your source system (to be used for integration) using the
Convert Values task to ensure that the key mapping is added to the central key mapping store of the SAP S/
4HANA system. This is only relevant if you extend an existing customer or contract partner as supplier with the
same number. If you extend an existing supplier with new org levels it is not necessary to switch on the key
mapping for the Supplier ID.
Level Name
2 BP Roles

Level Name
2 General Texts
2 Company Data
3 Withholding Tax Data
3 Company Texts
2 Purchasing Organization
Data
3 Partner Functions
3 Purchasing Texts
2 Bank Details
2 Industries
2 Tax Numbers
2 Contact Persons
3 Cont. Intern. Address Ver

sions
Contact Person ID
You must enter a contact person ID in the respective field in the Contact person sheet. This number is required
internal number. This business partner is automatically assigned to the supplier with the corresponding
relationship.

happens, you'll have to provide a more detailed/accurate address, for example, a US Postal code with 9 digits
In the Suppress Tax Jurisdiction Code Check field on the General Data sheet, you can suppress the check and
Tasks

Explorer.

Post-Processing
1.84 Supplier - extend existing record by Thailand branch code
Purpose
Business Object Component/Area LO-MD-BP
Business Object Type Master Data
Business Object Definition A business partner may have many branches depending on
the various locations from where they operate from. A
branch code is a 4-digit or a 5-digit code assigned by the
Revenue Department in Thailand to uniquely identify each
branch of a business partner. In any case, the head office
branch carries a branch code of 00000 or 0000.
In Scope
1. Branch codes with address information.

Out of Scope
1. More than one address.

2. International address versions.
Supported Features
Prerequisites
● The supplier master data needs to be migrated as a prerequisite with Thailand company code assigned.
● Only one branch code can be marked as default branch code. If only one branch code is assigned it will be
marked as default automatically.
● If branch codes are already assigned to the customer additional branch codes can only be uploaded w/o
default indicator.
● As standard method for communication (part of the address information) the following values are
supported only: Fax, E-mail and Telephone.
Level Name
1 Thailand branch code
Tasks

Explorer.

Post-Processing
1.85 Supplier
 Tip
For this migration object, the Custom Fields and Logic app is available. If you enhance your business object
with custom fields in the app, these custom fields will automatically be reflected in the XML template of the
corresponding migration object. See SAP Note 2726010 for further details.
Every time you add, change or delete a custom field, the migration project must be updated and a new
migration XML template must be downloaded and used. Thus, if custom fields are added or changed by an
application expert during migration testing, this must be communicated to and coordinated with your data
migration team. Also see the Extensibility section in the SAP S/4HANA Cloud documentation.
Purpose
Business Object Component/Area Logistics - General (LO-MD-BP, LO-MD-BP-VM)

Business Object Definition A supplier is a business partner who supplies goods and de
livers them to consumers/customers.
The supplier is a frequently-used master data object, used

by almost all business applications. In an SAP ERP system
it's called a vendor.
At SAP there are different object models for the supplier:
● In the traditional SAP ERP system the vendor master

data is used.
● In all new strategic applications, such as SAP SRM and
many industry solutions, the Business Partner ap
proach is used.
In Scope
1. General data with standard address data

2. BP roles
4. General texts
5. Company data
6. Withholding tax data
7. Company texts
8. Purchasing organization data
9. Purchasing partner functions
10. Purchasing texts
11. Bank data
12. Industries
13. Tax numbers
15. Contact persons
16. Address data including telephone numbers, fax number, email and URL
Out of Scope
1. Relationship to other business partners

2. Supplier and customer are two separate business partners with, as a consequence, two different numbers.
With the Supplier - extend existing record by new org levels [page 232] data migration object, you're able to
create a supplier with the same customer number. As a prerequisite, you have to create the customer first.

 Note
This migration object is based on the assumption that business partner and supplier are using the same
Supported Features
● General Data
● BP Roles
● General Texts
● Company Data
● Company Texts
● Partner Functions
● Purchasing Texts
● Bank Details
● Industries
● Tax Numbers
● Contact Persons
Prerequisites
 Note
The KTOKK field must be in sync with your customizing of the BU grouping. Otherwise, the grouping will
overwrite the account group.
● Bank [page 24]
● You have to maintain all business partner roles depending on your business transactions.
● You have to maintain all mandatory partner functions.

● It's possible to assign more than one address to a supplier. The address data from the General Data sheet
is always the standard address. If you assign only one address to a supplier, it's not necessary to provide an
external address number. If you provide additional addresses, however, the external address number
becomes mandatory. The external address number must be unique for each supplier. You can use the
same external address number for different business partners.
● During the vendor internal or external numbering step of the Convert Values task, you can choose between
internal and external number assignment for suppliers.
● With the BP Grouping field on the General Data sheet, you arrange the different number ranges (internal or
external) and the vendor account group. It's possible to create a supplier and a one-time supplier.
● If you need to create a business partner with both customer and supplier roles, you can enter this manually
or extend an already migrated customer with the Supplier - extend existing record by new org levels [page
● During the use Supplier ID for integration with external systems step of the Convert Values task, you can
switch on the key mapping for the Supplier ID to be used for integration with external systems. In
connection with this, you must also maintain the Business System ID of your source system (to be used for
integration) using the Convert Values task to ensure that the key mapping is added to the central key
Level Name
2 BP Roles (mandatory for OP)
2 General Texts
2 Company Data
3 Withholding Tax Data
3 Company Texts
2 Purchasing Organization
Data
3 Partner Functions
3 Purchasing Texts
2 Bank Details
2 Industries
2 Tax Numbers
2 Contact Persons
Contact Person ID
You must enter a contact person ID in the respective field in the Contact person sheet. This number is required
internal number. This business partner is automatically assigned to the supplier with the corresponding
relationship.

happens, you'll have to provide a more detailed/accurate address, for example, a US Postal code with 9 digits
In the Suppress Tax Jurisdiction Code Check field on the General Data sheet, you can suppress the check and
Tasks

Explorer.
Post-Processing
Further Information
● SAP Note 2726010 – Migration Cockpit: Support of custom fields (in-App extensibility)
1.86 PS - WBS element

Purpose
Business Object Definition A work breakdown structure (WBS) is a model of the work to
be performed in a project organized in a hierarchical struc
ture.
In Scope
Supported Features
● Basic Data
● Dates
● Assignments
● Control
● User Fields
● Text
Prerequisites
● PS - Project [page 198]
Level Name
1 Project Definition (mandatory)

Level Name
2 WBS element data (mandatory)
Tasks

Explorer.
Post-Processing
Transaction CJ13 Display WBS Element
1.87 Work center/Resource
Purpose
Business Object Component/Area Work Center / Resource (PP/PM)

Business Object Definition 1. Work Center
Logistics - General (LO)
Organizational unit that defines where and by whom an
operation is performed.
The work center has an available capacity. The activities
performed at or by the work center are valuated by
charge rates, which are determined by cost centers and
activity types. Work centers can be:
○ Machines
○ People
○ Production lines
○ Groups of craftsmen
2. Resource
Means of production and persons involved in a produc
tion process that have capacities assigned to them.
Resources are divided into resource categories, such as
production line labor, storage.
Using resources, you can:
○ Create a resource network structure to define the
sequence of the resources used
○ Define a resource hierarchy to group resources for
evaluation
○ Classify the resources to define their suitability for
a purpose or use in an operation
In Scope
The description is always stored in the logon language of the user that is used to migrate the work center data.
 Note
Migration of description in multiple languages is not supported
Supported Features
● Work Center Basic Data

● Work Center Default Values
● Work Center Scheduling
● Work Center Capacities, header data
● Work Center Capacities, Intervals of Available Capacity

● Work Center Capacities, Shift Values
● Work Center Assignment to Cost Center
Prerequisites
Level Name
1 Work Center Header (man

datory)
2 Work Center Capacity
3 Interval of Available Capacity
3 Capacities, shift values
2 Work Center Cost Center

(mandatory)
Tasks

Explorer.

Post-Processing
Transaction CR03 Display Work Center
Transaction CRC3 Display Resource

Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Gender-Related Language
We try not to use genderspecific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.
Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.

248 PUBLIC Important Disclaimers and Legal Information
Important Disclaimers and Legal Information PUBLIC 249
www.sap.com/contactsap
© 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.
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.
Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.
THE BEST RUN

Migration Objects For SAP S/4HANA: Implementation Guide - Public 2020-01-09

Uploaded by

Document Informationclick to expand document information

Document Informationclick to expand document information

Copyright:

Available Formats

Migration Objects For SAP S/4HANA: Implementation Guide - Public 2020-01-09

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

Migration Objects For SAP S/4HANA: Implementation Guide - Public 2020-01-09

Uploaded by

Copyright:

Available Formats

IMPLEMENTATION GUIDE | PUBLIC

Migration Objects for SAP S/4HANA

THE BEST RUN

1 Available Migration Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Migration Objects for SAP S/4HANA

Migration Object Business Object

FI - Accounts payable Accounting Document Transactional data File FI-AP

FI - Accounts receiva­ Accounting Document Transactional data File FI-AR

Activity price [page Activity Price Master data File CO

Activity type [page Activity Type Master data File CO

Migration Objects for SAP S/4HANA

Bank account balance Bank Account Transactional data File FI

Cash memo record Bank Account Transactional data File FIN-FSCM-CLM-CM

Bank [page 24] Bank Master data Master data File FI

Batch (if Batch is Batch Master data File LO-BM

Batch (if Batch level is Batch Master data File LO-BM

Material BOM [page Bill of Material Master data File PP-BD

PM - Equipment BOM Bill Of Material Master data File PM

PM - Functional loca­ Bill Of Material Master data File PM

PSS - Product compli­ Chemical Compliance Master data File EHS-SUS

PSS - Raw material Chemical Compliance Master data File EHS-SUS

Class hierarchy [page Class Master data File CA-CL

Characteristic [page Classification Charac­ Master data File CA-CL

Class [page 39] Classification Class Master data File CA-CL

Object classification Classification Valua­ Master data File CA-CL

Migration Objects for SAP S/4HANA

PSS - Substance [page Company Substance Master data File EHS-SUS

Condition contract Condition Contract Master data File LO-AB

Consent [page 61] Consent Record Transactional data File CA-GTF-CON

Cost center [page 135] Cost Center Master data File CO

Customer - extend ex­ Customer Master data File SD

Customer - extend ex­ Customer Master data File SD

Customer [page 75] Customer Master data File SD

Customer - extend ex­ Customer Master data File SD

Customer Material Customer Material Master data File SD

PM - Equipment [page Equipment Master data File PM

Exchange rate [page Exchange Rate Master data File FI

Migration Objects for SAP S/4HANA

PM - Functional loca­ Functional Location Master data File PM

G/L account [page General Ledger Ac­ Master data File FI

QM/PM - Catalog code Inspection Code Group Master data File QM

QM - Inspection Inspection Method Master data File QM

QM - Inspection plan Inspection Plan Master data File QM

QM - Selected set Inspection Selected Master data File QM

QM - Selected set code Inspection Selected Master data File QM

QM - Master inspec­ Inspection Specifica­ Master data File QM

Internal order (re­ Internal Order Transactional data File CO

Legal transaction Legal Transaction Transactional data File LCM

PM - Maintenance item Maintenance Item Master data File PM

PM - Maintenance plan Maintenance Plan Master data File PM

PM - Equipment task Maintenance Task List Master data File PM

PM - Functional loca­ Maintenance Task List Master data File PM

Migration Objects for SAP S/4HANA

PM - General mainte­ Maintenance Task List Master data File PM

Material [page 162] Material Master data File LO

Material inventory bal­ Material Stock Transactional data File MM-IM

PM - Measuring point Measuring Point Master data File PM

FI - Accounts receiva Accounting Document Transactional data File FI-AR

PM - Functional loca Bill Of Material Master data File PM

PSS - Product compli Chemical Compliance Master data File EHS-SUS

Characteristic [page Classification Charac Master data File CA-CL

Object classification Classification Valua Master data File CA-CL

Customer - extend ex Customer Master data File SD

Customer - extend ex Customer Master data File SD

Customer - extend ex Customer Master data File SD

PM - Functional loca Functional Location Master data File PM

G/L account [page General Ledger Ac Master data File FI

QM - Master inspec Inspection Specifica Master data File QM

Internal order (re Internal Order Transactional data File CO

PM - Functional loca Maintenance Task List Master data File PM

PM - General mainte Maintenance Task List Master data File PM

Material inventory bal Material Stock Transactional data File MM-IM

Material - extend exist Product Master data File LO

Material - extend exist Product Master data File MM

Xceptional case - Ma Product Master data File CO-PC-ACT

Material determination Sales Material Substi Master data File SD

Supplier - extend exist Supplier Master data File MM

Supplier - extend exist Supplier Master data File MM

Measurement docu Measurement docu Master data Direct Transfer - ERP PM

Maintenance notifica Maintenance notifica Transactional data Direct Transfer - ERP PM