Migration Objects For SAP S4HANA Cloud

IMPLEMENTATION GUIDE | PUBLIC
2019-11-23
Migration Objects for SAP S/4HANA Cloud

© 2019 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 Cloud. 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.
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, for the required business roles in the Business Role 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.
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 Business Object Migration Ap

Name Name Type Business Role proach Component
FI - Accounts pay Accounting Docu Transactional data SAP_BR_AP_ACCO File FI-AP

able open item ment UNTANT Staging Table
[page 260]
FI - Accounts re Accounting Docu Transactional data SAP_BR_AR_ACCO File FI-AR

ceivable open item ment UNTANT Staging Table
[page 265]
FI - G/L account Accounting Docu Transactional data SAP_BR_GL_ACCO File FI

balance and open/ Staging Table
ment UNTANT
line item [page
169]
Activity type [page Activity Type Master data SAP_BR_OVERHEA File CO

211] D_ACCOUNTANT Staging Table
Fixed asset - Mas Asset Accounting Master data SAP_BR_AA_ACCO File FI-AA
ter data [page UNTANT Staging Table
151]
Fixed asset - Post Asset Accounting Transactional data SAP_BR_AA_ACCO File FI-AA
ings [page 155] UNTANT Staging Table
Bank [page 20] Bank Master data SAP_BR_CASH_MA File FI
NAGER Staging Table
Bank account bal Bank Account Transactional data SAP_BR_CASH_MA File FI

ance [page 18] NAGER Staging Table

Available Migration Objects PUBLIC 3
Cash memo re Bank Account Transactional data SAP_BR_CASH_MA File FIN-FSCM-CLM-
cord [page 243] NAGER Staging Table CM
TRM - Bank guar Bank Guarantee Transactional data SAP_BR_TREASUR File FIN-FSCM-TRM
antee [page 341] Y_SPECIALIST_F Staging Table
OE
Batch (if Batch is Batch Master data SAP_BR_QUALITY File LO-BM

unique at material _TECHNICIAN Staging Table
level) [page 22]
Material BOM Bill of Material Master data SAP_BR_PRODN_E File PP-BD

[page 26] NG_DISC Staging Table
PM - Equipment Bill Of Material Master data SAP_BR_MAINTEN File PM

BOM [page 110] ANCE_PLANNER Staging Table
PM - Functional lo Bill Of Material Master data SAP_BR_MAINTEN File PM

cation BOM [page ANCE_PLANNER Staging Table
163]
QM - Certificate Certificate Profile Master data SAP_BR_QUALITY File QM

profile incl. assign incl. Assignment _PLANNER Staging Table
ment [page 30]
PSS - Product Chemical Compli Master data SAP_BR_PROD File EHS-SUS

STWRD_SPLST Staging Table
compliance info ance Info
_PCL
[page 107]
SAP_BR_MD_S
PECIALIST_P
CL
PSS - Raw material Chemical Compli Master data SAP_BR_PROD File EHS-SUS
STWRD_SPLST Staging Table
compliance info ance Info
_PCL
[page 104]
SAP_BR_MD_S
PECIALIST_P
CL
Class hierarchy Class Master data SAP_BR_BOM_ENG File CA-CL

[page 40] INEER Staging Table
Characteristic Classification Master data SAP_BR_PRODUCT File CA-CL

[page 34] Characteristic _CONFIG_MODELE Staging Table
R
Class [page 37] Classification Master data SAP_BR_PRODUCT File CA-CL

Class _CONFIG_MODELE Staging Table
R

4 PUBLIC Available Migration Objects
Object classifica Classification Valu Master data SAP_BR_PROD File CA-CL

MASTER_SPEC Staging Table
tion [page 43] ation
IALIST
SAP_BR_MAIN
TENANCE_PLA
NNER
TRM - Commercial Commercial Paper Transactional data SAP_BR_TREASUR File FIN-FSCM-TRM-

paper [page 345] Y_SPECIALIST_F Staging Table TM
OE
PSS - Substance Company Sub Master data SAP_BR_MD_SPEC File EHS-SUS

[page 337] stance IALIST Staging Table
Condition contract Condition Con Master data SAP_BR_SALES_M File LO-AB

[page 51] tract ANAGER Staging Table
Consent [page Consent Transactional data SAP_BR_DATA_PR File CA-GTF-CON

60] IV_SPEC_CONS Staging Table
FI-CA Contract ac Contract Account Master data SAP_BR_APR_ File FI-CA
ACCOUNTANT_ Staging Table
count [page 135]
FICA
SAP_BR_APR_
MANAGER_FIC
A
FI-CA Open item Contract Account Transactional data SAP_BR_APR_ File FI-CA
[page 138] Document
FICA
SAP_BR_APR_
MANAGER_FIC
A
Cost center [page Cost Center Master data SAP_BR_OVERHEA File CO

Customer - extend Customer Master data SAP_BR_BUPA_MA File SD

existing record by Staging Table
STER_SPECIALIS
Credit Manage
T
ment data [page
74]

existing record by STER_SPECIALIS Staging Table
Thailand branch T
code [page 72]


new org levels T
[page 68]
Customer [page Customer Master data SAP_BR_OVER File SD

HEAD_ACCOUN Staging Table
79]
TANT
SAP_BR_BUPA
_MASTER_SPE
CIALIST
Customer Material Customer Material Master data SAP_BR_INTERNA File SD

[page 77] L_SALES_REP Staging Table
DG - Assessment Dangerous Goods Master data SAP_BR_DG_SPLS File EHS-SUS-DG

for unpackaged T_PCL Staging Table
product (text-
based) [page 92]
DG - Assessment Dangerous Goods Master data SAP_BR_DG_SPLS File EHS-SUS-DG

for packaged prod T_PCL Staging Table
uct (text-based)
[page 90]
VC - Dependency Dependency Net Master data SAP_BR_PRODUCT File LO-VC

net [page 88] _CONFIG_MODELE Staging Table
R
TRM - Deposit at Deposit At Notice Transactional data SAP_BR_TREASUR File FIN-FSCM-TRM-

notice [page 348] Y_SPECIALIST_F Staging Table TM
OE
Document info re Document Info Re Master data SAP_BR_DESIGN_ File CA-DMS
cord [page 95] cord ENGINEER Staging Table
ECM - Change Engineering Master data SAP_BR_PRODN_E File PLM-WUI-OBJ-

master [page 32] Change Number NG_PROC Staging Table ECN
PM - Equipment Equipment Master data SAP_BR_MAINTEN File PM

[page 115] ANCE_PLANNER Staging Table
Exchange rate Exchange Rate Master data SAP_BR_GL_ACCO File FI

[page 130] UNTANT Staging Table
FI-CA Contract FI-CA – Contract Master data SAP_BR_BUPA_MA File FI

partner [page partner STER_SPECIALIS Staging Table
132] T

SAP_BR_GL_ACCO File FI
FI - Historical bal Financial Account Transactional data
UNTANT Staging Table
ance [page 174] ing
Fixed asset (incl. Fixed Asset Master data SAP_BR_AA_ACCO File FI-AA
balances and Transactional UNTANT Staging Table
transactions) data
(deprecated)
[page 144]
TRM - Foreign ex Foreign Exchange Transactional data SAP_BR_TREASUR File FIN-FSCM-TRM
change collar - Collar - Contract Y_SPECIALIST_F Staging Table
contract [page OE
356]
TRM - Foreign ex Foreign Exchange Transactional data SAP_BR_TREASUR File FIN-FSCM-TRM-
change spot/ Spot Forward Y_SPECIALIST_F Staging Table TM
forward transac Transaction OE
tion - contract
[page 359]
TRM - Foreign ex Foreign Exchange Transactional data SAP_BR_TREASUR File FIN-FSCM-TRM-
change swap - Swap Contract Y_SPECIALIST_F Staging Table TM
contract [page OE
353]
PM - Functional lo Functional Loca Master data SAP_BR_MAINTEN File PM

cation [page 165] tion ANCE_PLANNER_ Staging Table
TRM - FX option FX Option Transactional data SAP_BR_TREASUR File FIN-FSCM-TRM-

[page 351] Y_SPECIALIST_F Staging Table TM
OE
EHS - Incident Incident Manage Transactional data SAP_BR_INDUSTR File EHS-SUS-IM

[page 245] ment IAL_HYGIENIST Staging Table
QM/PM - Catalog Inspection Code Master data SAP_BR_QUAL File QM

ITY_TECHNIC Staging Table
code group/code Group
IAN (display
[page 301]
only)
SAP_BR_QUAL
ITY_PLANNER
(create)

QM - Inspection Inspection Method Master data SAP_BR_QUAL File QM

method [page
IAN (display
178]
only)
SAP_BR_QUAL
ITY_PLANNER
(create)
QM - Inspection Inspection Plan Master data SAP_BR_QUAL File QM

plan [page 180]
IAN (display
only)
SAP_BR_QUAL
ITY_PLANNER
(create)
QM - Selected set Inspection Se Master data SAP_BR_QUAL File QM

code [page 325] lected Set
IAN (display
only)
SAP_BR_QUAL
ITY_PLANNER
(create)
QM - Selected set Inspection Se Master data SAP_BR_QUAL File QM

[page 323] lected Set
IAN (display
only)
SAP_BR_QUAL
ITY_PLANNER
(create)
QM - Master in Inspection Specifi Master data SAP_BR_QUAL File QM

spection charac cation
IAN (display
teristic [page 251]
only)
SAP_BR_QUAL
ITY_PLANNER
(create)
TRM - Interest rate Interest Rate In Transactional data SAP_BR_TREASUR File FIN-FSCM-TRM
instrument [page strument Y_SPECIALIST_F Staging Table
362] OE
TRM - Interest rate Interest Rate Swap Transactional data SAP_BR_TREASUR File FIN-FSCM-TRM-
swap [page 367] Y_SPECIALIST_F Staging Table TM
OE
JIT - Customer JIT – Customer Master data SAP_BR_MD_SPEC File LE-JIT

[page 253] Data IALIST_JIT Staging Table

JIT - Package JIT – Package Master data SAP_BR_MD_SPEC File LE-JIT

group [page 255] Group IALIST_JIT Staging Table
JIT - Supply con JIT – Supply Con Master data SAP_BR_MD_SPEC File LE-JIT
trol [page 258] trol IALIST_JIT Staging Table
JVA - Joint operat Joint Operating Master data SAP_BR_JVA_ACC File CA-JVA
ing agreement Agreement (JOA) OUNTANT Staging Table
[page 189]
JVA - Joint venture Joint Venture Master data SAP_BR_JVA_ACC File CA-JVA
master data [page OUNTANT Staging Table
202]
JVA - Joint venture Joint Venture Part Master data SAP_BR_MD_SPEC File CA-JVA
partner [page ner IALIST_PCL Staging Table
192]
Legal transaction Legal Transaction Transactional data SAP_BR_LEGAL_C File LCM

[page 208] OUNSEL Staging Table
PM - Maintenance Maintenance Noti Transactional data SAP_BR_MAINTEN File PM

notification [page Staging Table
fication ANCE_PLANNER
102]
PM - Maintenance Maintenance Plan Master data SAP_BR_MAINTEN File PM

plan [page 212] ANCE_PLANNER Staging Table
PM - Equipment Maintenance Task Master data SAP_BR_MAINTEN File PM

task list [page List ANCE_PLANNER Staging Table
112]
PM - Functional lo Maintenance Task Master data SAP_BR_MAINTEN File PM

cation task list List ANCE_PLANNER Staging Table
[page 161]
PM - General Maintenance Task Master data SAP_BR_MAINTEN File PM

maintenance task List ANCE_PLANNER Staging Table
list [page 167]
File LO
Material (depre Material Master data SAP_BR_PRODMAS
cated) [page 233] TER_SPECIALIST Staging Table
Material inventory Material Stock Transactional data SAP_BR_INVENTO File MM-IM

balance [page RY_MANAGER Staging Table
184]

PM - Measuring Measuring Point Master data SAP_BR_MAINTEN File PM

point [page 99] ANCE_PLANNER Staging Table
VC - Object de Object Dependen Master data SAP_BR_PRODUCT File LO-VC

pendencies [page cies _CONFIG_MODELE Staging Table
85] R
PM - Measurement Plant Maintenance Master data SAP_BR_MAINTEN File PM

document [page ANCE_PLANNER Staging Table
97]
TRM - Position Position Value Transactional data SAP_BR_TREASUR File FIN-FSCM-TRM-

value [page 370] Y_SPECIALIST_F Staging Table TM
OE
Condition record Price Condition Master data SAP_BR_PRIC File SD

ING_SPECIAL Staging Table
for pricing (general
IST
template) [page
SAP_BR_PRIC
54]
ING_SPECIAL
IST_PRSV
SAP_BR_PROJ
_MANAGE_COM
M
SAP_BR_PURC
HASER
Condition record Price Condition Master data SAP_BR_PRIC File MM-PUR

for pricing in pur
IST
chasing (re
SAP_BR_PRIC
stricted) [page
ING_SPECIAL
248] IST_PRSV
SAP_BR_PROJ
_MANAGE_COM
M
SAP_BR_PURC
HASER
Condition record Price Condition Master data SAP_BR_PRIC File SD

for pricing in sales
IST
(restricted) [page
SAP_BR_PRIC
317]
ING_SPECIAL
IST_PRSV
SAP_BR_PROJ
_MANAGE_COM
M

Product [page Product Master data SAP_BR_PRODMAS File LO

277] TER_SPECIALIST Staging Table
Product classifica Product Master data SAP_BR_TRD_CLS File SLL

tion - Legal control Staging Table
_SPECIALIST
[page 225]
Material - extend Product Master data SAP_BR_PRODMAS File LO

existing record by TER_SPECIALIST Staging Table
new org levels
[page 219]
Material - Forecast Product Master data SAP_BR_PRODMAS File MM

planning [page TER_SPECIALIST Staging Table
217]
Material inspec Product Master data SAP_BR_PRODMAS File QM

tion setup [page TER_SPECIALIST Staging Table
182]
Material - extend Product Master data SAP_BR_PRODMAS File MM

existing record TER_SPECIALIST Staging Table
with long text
[page 227]
Product classifica Product Master data SAP_BR_TRD_ File SLL

CLS_SPECIAL Staging Table
tion - Commodity
IST
code [page 215]
SAP_BR_PROD
MASTER_SPEC
IALIST
Product consump Product Transactional data SAP_BR_PRODMAS File MM

tion [page 275] Staging Table
TER_SPECIALIST
Warehouse prod Product Master data SAP_BR_WAREHOU File SCM-EWM

uct [page 124] SE_CLERK_EWM Staging Table
Xceptional case - Product Master data SAP_BR_INVENTO File CO-PC-ACT

Material price RY_ACCOUNTANT Staging Table
chng for global
currencies [page
241]
Production version Production Version Master data SAP_BR_PRODN_E File PP

[page 284] NG_DISC Staging Table
Profit center [page Profit Center Master data SAP_BR_OVERHEA File CO


Commercial Project Master data SAP_BR_PROJ_MA File CA-CPD

project [page 287] Transactional NAGE_COMM Staging Table
data
Enterprise project Project Master data SAP_BR_PROJ_FI File PPM

[page 270] N_CONTROLLER Staging Table
FI-CA Provider Provider Contract Master data SAP_BR_APR_ File FI-CA

contract [page
FICA
141]
SAP_BR_APR_
MANAGER_FIC
A
PSM - Fund [page Public Sector Man Master data SAP_BR_BUDG File PSM-FM
ET_RESPONSI Staging Table
290] agement
BLE
SAP_BR_BUDG
ET_SPECIALI
ST
Purchase contract Purchase Contract Transactional data SAP_BR_PURCHAS File MM-PUR

[page 65] ER Staging Table
Purchase order Purchase Order Transactional data SAP_BR_PURCHAS File MM-PUR

(only open PO) ER Staging Table
[page 297]
Purchase schedul Purchase Schedul Transactional data SAP_BR_PURCHAS File MM-PUR

ing agreement ing Agreement ER Staging Table
[page 315]
Purchasing info re Purchasing Info Master data SAP_BR_PURCHAS File MM-PUR
cord- extend exist Record ER Staging Table
ing record [page
291]
Purchasing info re Purchasing Info Master data SAP_BR_PURCHAS File MM-PUR
cord with condi Record ER Staging Table
tions [page 294]
QM - Quality info Quality Info Record Master data SAP_BR_QUAL File QM

ITY_PLANNER Staging Table
record [page 304]
SAP_BR_QUAL
ITY_ENGINEE
R
Real estate con Real Estate Con Transactional data SAP_BR_RECM_SP File RE-FX
tract [page 306] tract ECIALIST Staging Table

Routing [page 309] Routing Master data SAP_BR_PRODN_E File PP

NG_DISC Staging Table
Sales contract Sales Contract Transactional data SAP_BR_SALE File SD

S_MANAGER Staging Table
[page 321]
(display only)
SAP_BR_INTE
RNAL_SALES_
REP (create)
Material determi Sales Material Master data SAP_BR_INTERNA File SD

nation [page 231] Substitution L_SALES_REP Staging Table
Sales order (only Sales Order Transactional data SAP_BR_SALE File SD

S_MANAGER Staging Table
open SO) [page
(display only)
313]
SAP_BR_INTE
RNAL_SALES_
REP (create)
SAP_BR_INTE
RNAL_SALES_
REP_PRSV
SEPA mandate SEPA Mandate Master data SAP_BR_AR_A File FI

CCOUNTANT Staging Table
[page 327]
SAP_BR_APR_
ACCOUNTANT_
FICA
Service contract Service Transactional data SAP_BR_CUSTOME File CRM-S4-SRV

[page 331] R_SRVC_MGR Staging Table
Service order (only Service Transactional data SAP_BR_CUSTOME File CRM-S4-SRV

open SRVO) [page R_SRVC_MGR Staging Table
334]
Software/Hard Software Con Master data SAP_BR_SYSTEMS File PLM

ware constraint straint _ENGINEER Staging Table
[page 339]
Source list [page Source List Master data SAP_BR_PURCHAS File MM-PUR
329] ER Staging Table
Supplier - extend Supplier Master data SAP_BR_BUPA_SP File MM

existing record by ECIALIST Staging Table
Thailand branch
code [page 384]

Supplier - extend Supplier Master data SAP_BR_BUPA_MA File MM

new org levels T
[page 379]
Supplier [page Supplier Master data SAP_BR_BUPA_MA File MM

386] STER_SPECIALIS Staging Table
T
JVA - Cost center Suspended Cost Master data SAP_BR_ADMI File CA-JVA
suspense [page N_JVA Staging Table
Centers
194] SAP_BR_OVER
HEAD_ACCOUN
TANT
JVA - Project sus Suspended Master data SAP_BR_JVA_ File CA-JVA

pense [page 200] ACCOUNTANT Staging Table
Projects
SAP_BR_PROJ
_FIN_CONTRO
LLER
JVA - Venture sus Suspended Ven Master data SAP_BR_JVA_ACC File CA-JVA
pense [page 197] Staging Table
tures OUNTANT
VC - Assign global Variant Character Master data SAP_BR_PRODUCT File LO-VC

dependency to istic _CONFIG_MODELE Staging Table
characteristic R
value [page 375]
VC - Assign global Variant Character Master data SAP_BR_PRODUCT File LO-VC

dependency to istic _CONFIG_MODELE Staging Table
characteristic R
[page 373]
VC - Material var Variant Configura Master data SAP_BR_PROD File LO-VC

iant [page 229] UCT_CON Staging Table
tion
FIG_MODELER
VC - Configuration Variant Configura Master data SAP_BR_PRODUCT File LO-VC

profile [page 58] tion Profile _CONFIG_MODELE Staging Table
R
VC - Variant table Variant Configura Master data SAP_BR_PRODUCT File LO-VC

entry [page 377] tion Table _CONFIG_MODELE Staging Table
R
VC - Variant table Variant Configura Master data SAP_BR_PRODUCT File LO-VC

structure [page tion Table _CONFIG_MODELE Staging Table
16] R

VC - Constraint Variant Constraint Master data SAP_BR_PRODUCT File LO-VC

[page 62] _CONFIG_MODELE Staging Table
R
Warehouse stock Warehouse Stock Transactional data SAP_BR_WARE File SCM-EWM

HOUSE_CLERK Staging Table
[page 127]
_EWM
SAP_BR_INVE
NTORY_MANAG
ER
Warehouse fixed Warehouse Stor Master data SAP_BR_WAREHOU File SCM-EWM

bin assignment age Bin SE_CLERK_EWM Staging Table
[page 120]
Warehouse stor Warehouse Stor Master data SAP_BR_WAREHOU File SCM-EWM

age bin sorting age Bin SE_CLERK_EWM Staging Table
[page 122]
Warehouse stor Warehouse Stor Master data SAP_BR_WAREHOU File SCM-EWM

age bin [page 117] age Bin SE_CLERK_EWM Staging Table
Work center/ Work Center Master data SAP_BR_PRODN_E File PP

Resource [page NG_DISC Staging Table
391]
The Cost rate migration object is no longer supported in SAP S/4HANA Cloud. You can upload activity prices
using the upload function of the new Manage Cost Rates - Plan SAP Fiori app. For more information and
support, refer to the SAP Fiori apps reference library.
 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
After an SAP S/4HANA Cloud release upgrade, any new migration objects won’t get added to existing
migration projects. To be able to use new migration objects, you need to create a new migration project. If
there are still migration objects missing after creating a new migration project, please see SAP Note
2538700 for further information.
Further Information
● 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_CE_MO this very topic: Available Migration Objects
http://help.sap.com/S4_CE_DM the landing page for data migration
● If you want to migrate historical financial transactions into your SAP S/4HANA Cloud using the SAP S/
4HANA migration cockpit, see SAP Note 2587192 .
● If you are using the Fixed asset (incl. balances and transactions) (deprecated) [page 144] 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 2568909 .
1.1 VC - Variant table structure
Available Migration Objects [page 3] in SAP S/4HANA Cloud.
Purpose
Business Object Component/Area Variant Configuration Table (LO-VC)
Business Object Type Master data

Business Object Definition A table used to store consistent combinations of values for
different characteristics in product modeling. See table de
pendency.
In Scope
Migration to SAP S/4HANA Cloud is supported.
Supported Features
The following structures/features are supported in SAP S/4HANA Cloud:
● Basic Data of Variant Tables

● Characteristics in Variant Tables
● Value Assignment Alternatives
● Table Description
Prerequisites
The following objects must already have been maintained or migrated:
● Characteristic [page 34]
Mapping Instructions
Mapping Structure Hierarchy
Level Name
1 Basic data of variant tables

(mandatory)
2 Characteristics in variant ta

bles
2 Table Description field with

the correct code
3 Value assignment alterna

tives

Additional SAP Notes
Information about the used API:
● 1840693
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 SAP S/4HANA Cloud 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

Log on to your SAP S/4HANA Cloud system as Configuration Expert - Data Migration and use the Data
Migration Status app to validate your data in the system. Alternatively, use the following app:
App: Display Table Structure
Business Role: Product Configuration Modeler

(SAP_BR_PRODUCT_CONFIG_MODELER)
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.
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
App: Cash Position
Business Role: Cash Manager (SAP_BR_CASH_MANAGER)
1. Filter by Company Code/Account Number/Currency.

2. User can set filter for account number in the app as well.
3. Select Account Number.
4. Enter the account number and choose OK.
How to Cancel Already Migrated Balance Records
You can delete already migrated balance records using the Delete Data from One Exposure app. For further
information, refer to the SAP Fiori apps reference library and the SAP Help Portal.
 Note
After deletion, balance records with same key can be migrated again using a new migration project.
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
App: Manage Banks
Further Information
Find information about using the Transfer BIC Data app to upload bank directories, compare them with existing
bank data, and save the new and changed data in the bank master table using a global bank directory in the
Cash and Liquidity Management product assistance. Bank directories can be downloaded from the web pages
of central banks. The Monetary Financial Institutions (MFIs): Download area of the European Central Bank is
an example of this.
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
● Characteristic Values
● Control Parameters
Prerequisites
The following objects must have already been maintained or migrated:
● Product [page 277]

● Supplier [page 386]
● If you want to migrate batches with classification data, the following objects need to be migrated first:
○ Characteristic [page 34]
○ Class [page 37]
○ Object classification [page 43]
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

App: Batch Information Cockpit
Batch Overview
Business Role: Quality Technician (SAP_BR_QUALITY_TECHNICIAN)
1.5 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
○ T-Text item
○ K-Class 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, 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.
Validity Period and Dependencies
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.
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 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
App: Display Bill of Material
Business Role: Production Engineer - Discrete Manufacturing

(SAP_BR_PRODN_ENG_DISC)])
Further Information
For this migration object, SAP delivers a prefilled sample XML template that helps you in filling out your data
migration template. Use this link to navigate to the Data Migration Template Samples for SAP S/4HANA Cloud
(for customers and partners only).
1.6 QM - Certificate profile incl. assignment
Purpose
Business Object Component/Area Certificate Profile incl. Assignment (QM)
Business Object Definition A certificate profile controls inspection lot selection, the se
quence of characteristics, the characteristic data for a qual
ity certificate. It can be assigned to materials, material
groups, and material/customer combinations.

In Scope
Supported Features
● Certificate profile header

● Materials
● Characteristics
● Characteristics text
● Material assignment
● Material/Customer assignment
● Material Group assignment
Prerequisites

Level Name
1 Certificate profile header

(mandatory)
2 Materials
2 Characteristics
3 Characteristics text
2 Material assignment
2 Material/Customer assign
ment
2 Material Group assignment

Tasks

Explorer.
Post-Processing

App: Display Quality Certificate Profile
Business Role: Quality Planner (SAP_BR_QUALITY_PLANNER)
1.7 ECM - Change master
Purpose
Business Object Component/Area Engineering Change Number (PLM-WUI-OBJ-ECN)
Business Object Definition A change number is used to uniquely identify a change mas
ter record. All changes made with reference to a change
number are controlled and logged by the change master re
cord. Numbers are assigned externally.

In Scope
The object management record is only supported for the following objects:

● Material BOM [page 26]
● Document info record [page 95]
Out of Scope
Internal numbering is not supported.
Supported Features
● Change Master Header

● Alternative Dates
● Document Info Record
● Material
● Material BOM
● Only external numbering is supported.

● The Object type active for change number indicator should be set before setting further indicators for any
object type.
● The Object management record generated indicator can be set for the object type if the Management record
required indicator is set together with the Object type active for change number indicator.
● You can only enter an Alternative Date for change objects for which the object management record can be
maintained.

Level Name
1 Change Master Header (mandatory)
2 Alternative Dates
2 Document Info Record
2 Material
2 Material BOM
Tasks

Explorer.
Post-Processing
App: Manage Change Masters (Change Management)
Business Role: Product Engineer- Process Manufacturing

(SAP_BR_PRODN_ENG_PROC)
1.8 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 37]
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.
subsequent error messages and inconsistent data on your database.

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.
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
App: Manage Characteristics

1.9 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
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.

Organizational Area
In SAP S4HANA Cloud, the batch class (023) with organizational area 'S' (Substance / steel), will be converted
to the proportion/production relevant flag. The other combinations are NOT supported.
Organizational Area needs to be filled the same in both Characteristics and on the General data sheet.
The entries possible for the Organizational Area field in General data are a combination of values. An
Organizational Area is represented by an indicator. For example, 'L' or 'S' are organizational area indicators,
which must first be defined and added to a class type in the configuration.
One or both organizational area indicators can be combined. For example, the value 'LS' means the current
class has two organizational areas.
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

App: Manage Classes


1.10 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 37]
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

App: Manage Class Assignments
Business Role: BOM Engineer (SAP_BR_BOM_ENGINEER)
Further Information
● Information about the used API: SAP Note 1350546

● Information for classification: SAP Note 2267878
1.11 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 Document Management (017) is supported.
7. Class type Work Center Class (019) is supported.
8. Class type Batch (022 and 023) is supported.
9. Class type Maintenance Plan (080) is supported.
10. Class type Material - Configurable Objects (200) is supported.
11. 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 22] migration
object.
Supported Features
● Basic Data
● Characteristic Values (only for material classification)
● Change Number

Prerequisites
● Characteristic [page 34] (dependent on class type)

● Class [page 37] (dependent on class type)
● Product [page 277] (dependent on class type)
● PM - Equipment [page 115] (dependent on class type)
● PM - Functional location [page 165] (dependent on class type)
● Supplier [page 386] (dependent on class type)
● Customer [page 79] (dependent on class type)
● Document info record [page 95] (dependent on class type)
● Work center/Resource [page 391] (dependent on class type)
Name of Database Table for Object

Class type (KLART) and object table (OBTAB) should be mapped as per the following table.
KLART OBTAB
001 MARA
002 EQUI
003 IFLOT
010 LFA1
011 KNA1
017 DRAW
019 CRHD
022 MARA
023 MARA
080 MPLA

KLART OBTAB
200 MARA
300 MARA
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 22] 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 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.
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
Unit of Measurement (UOM) UNIT_FROM and UNIT_TO Fields
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
App: Manage Class Assignments
Business Role: Administrator - Recipe Development

(SAP_BR_ADMINISTRATOR_RCP_DEV)
Maintenance Planner (SAP_BR_MAINTENANCE_PLANNER)
BOM Engineer (SAP_BR_BOM_ENGINEER)
Further Information
● For import information for classification see SAP Note 2267878
1.12 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
Prerequisites

● Customer [page 79]
● 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)

Level Name
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
App: Maintain Contract in the Sales Condition Contract

Management catalog
Business Role: Sales Manager (SAP_BR_INTERNAL_SALES_REP)
1.13 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 (restricted) [page 317] or Condition record for pricing in purchasing (restricted) [page 248].
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
App: Set Material Prices

Business Role: Pricing Specialist (SAP_BR_PRICING_SPECIALIST)
Purchaser
(SAP_BR_PURCHASER)
App: Set Service Prices
Business Role: Pricing Specialist-Professional Service

(SAP_BR_PRICING_SPECIALIST_PRSV)
Project Manager-Commercial Services

(SAP_BR_PROJ_MANAGE_COMM)
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
Further Information

1.14 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 43]
(Type 300 for SAP S/4HANA Cloud)
● Change number (optional)
● VC - Object dependencies [page 85]

 Note
1. If the configuration profile needs to be created with a change number, please create a change
number first, and then create a configuration profile using the change number.
2. Material with more than one configuration profile must be loaded with no change numbers or with
change numbers that have a different validity date. Violation leads to an error message, for
example: Changes only allowed with change number or Enter a change number.
3. If Material is not assigned to a class type, the status In Preparation will be assigned to the
configuration profile as standard.
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
App: Variant Configuration Modeling Envmt

1.15 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

App: Manage Consents
Business Role: Data Privacy Specialist - Consent Management

(SAP_BR_DATA_PRIV_SPEC_CONS)
1.16 VC - Constraint
Purpose
Business Object Definition Constraints are interdependencies between objects and

their characteristics, and used as a dependency in variant
configuration. You can use them to set characteristic values
or to check the consistency of assigned values.
In Scope

Supported Features
● General data
● Multi-lingual descriptions
● Documentation
● Source code
Prerequisites

● VC - Dependency net [page 88]
● Change number (optional)
 Note
1. If a constraint needs to be created with a change number, please create a change number first, and
then create a constraint using the change number.
2. If multiple constraints need to be assigned to a dependency net, all constraints should be migrated
with the same change number or with change numbers with different validity-from dates or with no
change number.
Level Name
2 Multi-lingual descriptions (mandatory)
2 Documentation
2 Socurce code (mandatory)
General Data
Constraint net must be unique for every dependency net.
Multi-Lingual Descriptions
Enter a description, one for each language

 Note
The Multi-lingual description sheet should contain at least one description per constraint. Otherwise, an
error message, Maintain at least one description for the dependency, will be displayed.
Documentation
Enter a documentation, one for each language.
 Note
Documentation can't be maintained without description in the corresponding language.
Source Code
Maintain a source code in one line (string), for each constraint.
 Note
Constraints with syntax errors in the source code cannot be loaded. In the case of syntax errors, an error
message will be displayed and the constraint will be skipped for migration.
Tasks

Explorer.
Post-Processing



1.17 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:

● Cost center [page 205]
● WBS element
● Fixed asset - Master data [page 151]
● G/L account (manually; expense account used in account assignment category)
● Purchasing info record with conditions [page 294] (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
2 Header Texts
2 Item Data (mandatory)
3 Delivery Address
3 Account Assignment
3 Item Texts
Tasks

Explorer.

Post-Processing

App: Manage Purchase Contracts
Monitor Purchase Contracts
Business Role: Purchaser (SAP_BR_PURCHASER)
1.18 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. Extend already existing customers with new org levels and extend already existing suppliers/contract
partners as customer with the same number.
2. General data (only fields which might become relevant when you extend a supplier/contract partner as
customer)
3. Additional addresses
4. Sales data including sales partner functions
5. Company data including dunning
6. Bank data
7. Tax numbers
8. Long texts (company and sales)
9. Industry assignments
10. Identification numbers
11. Contact persons, including address data with telephone, fax and email.
Out of Scope
1. Updates of existing fields/records.

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.
3. Time-dependency of addresses.
4. Time-dependency of bank data.
Supported Features
Prerequisites

● If you want to extend already existing suppliers/contract partners as customer with the same number:
○ Supplier [page 386]
○ FI-CA Contract partner [page 132]
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.
If you want to use the Customer ID for integration with external systems, you can activate it 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 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 supplier or contract partner as
customer with the same number. If you extend an existing customer with new org levels it is not necessary to
switch on the key mapping for the Customer ID.
Sensitive Fields for Dual Control

If you have activated the Define Sensitive Fields for Dual Control (Customers) option in the Configure Your
Solution app, you must confirm all related customer changes in the Confirm Customer List app. Migration of
master data records are then considered as changes, and you must confirm them later on. For this reason, you
should consider to deactivate this option before you start with the data migration, and activate it again
afterwards.
Challenge with Cross-References to Another BP

For the customer migration object, you can enter data into fields which could be cross-references to other
business partners, for example alternative payers or ship-to-parties.
If you want to use these references to other business partners, make sure these business partners have been
created in advance.
Gordian Knot Problem

If you use the partner function for the sales data, you might face the following situation.
 Example
You have three customers, A, B, and C. They have the following relation:
● A is ship-to-party for B
● B is ship-to-party for C
● C is ship-to-party for A
Please note that this data constellation can't be handled with the data migration object. Please remove some of
the relations and add them later via the BP maintenance UI or BP mass maintenance app.
Challenge with Partner Functions and Contact Persons

Customers might have contact persons assigned who act in partner capacity. During migration, contact
persons are created as separate business partners using internal numbering. Since this new numbering is only
created during the migration process, you can't use the contact person number as contact ID for partner
functions in one single step.
To assign a contact person as partner, first create the customer with the contact person, but without sales
data. Then, use the Customer - extend existing record by new org levels migration object in a second step to
assign the sales data together with the contact person in partner capacity.

Contact Person ID
You must enter a contact person ID in the respective field in 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 supplier with the corresponding
relationship.
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 a record, the migration of this record will fail. If this
happens, you'll have to provide a more detailed/accurate address, for example, a US Postal code with 9 digits
instead of 5 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
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.
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
2 Identification Numbers
2 Contact Person
Tasks

Explorer.

Post-Processing
App: Maintain Business Partner
Business Role: Master Data Specialist - Business Partner Data

(SAP_BR_BUPA_MASTER_SPECIALIST)
1.19 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
Business Role: Master Data Specialist - Business Partner

1.20 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.
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 the Manage Your Solution app, navigate to Configure Your Solution.

2. Open the Define Events and Follow-On Processes configuration step. You can find it in the following area:
Finance Credit Evaluation and Management Process and Business Transactions .
3. 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.21 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 37]

● 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

App: Manage Customer Materials
Business Role: Internal Sales Representative

(SAP_BR_INTERNAL_SALES_REP)
1.22 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. General data with standard address data

3. Sales data
4. Sales partner functions
5. Company data including dunning
6. Bank data
8. Tax numbers
9. Long texts (general, company, sales)
11. Contact persons, including address data with telephone, fax, email
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 [page 379] object, you can create a supplier
with the same customer number. As a prerequisite, you have to create the customer first.

Supported Features
● General Data
● 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
 Note
Any time you add, change or delete a custom field, the migration project must be updated; a new XML
template must be downloaded and used. Thus, if custom fields are added, changed or deleted by an
application expert during migration testing, this must be communicated to, and coordinated with, data
migration.
The Customer (General Data, Company Data, and Sales Data) can be enhanced with the Custom Fields
and Logic app, adding custom fields in the application. If the Customer is enhanced in this way, the
custom fields will be reflected automatically in the XML template as well.
Prerequisites
● Bank [page 20]
The customer will be created with the Customer (FLCU01) role. The Customer (Financial Accounting) (FLCU00)
role will be created if company data is provided in the template.
All mandatory partner functions will be created automatically with the same customer number. If you provide
the partner function with a different customer number on the Partner Functions sheet, this entry will be taken.

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:
 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 persons will always get an internal number for the new business partner.
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 you need to create a business partner 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 379] object to add the appropriate supplier data.
If you want to use the Customer ID for integration with external systems, you can activate it during migration.
At the same time, you must also maintain the Business System ID of your source system (to be used for
store of the SAP S/4HANA system.
If you have activated the Define Sensitive Fields for Dual Control (Customers) option in the Configure Your
Solution app, you must confirm all related customer changes in the Confirm Customer List app. Migration of
master data records are then considered as changes, and you must confirm them later on. For this reason, you
should consider to deactivate this option before you start with the data migration, and activate it again
afterwards.
For the customer migration object, you can enter data into fields which could be cross-references to other
business partners, for example alternative payers or ship-to-parties.
created in advance.

If you use the partner function for the sales data, you might face the following situation.
 Example
You have three customers, A, B, and C. They have the following relation:
● A is ship-to-party for B
● B is ship-to-party for C
● C is ship-to-party for A

Customers might have contact persons assigned who act in partner capacity. During migration, contact
persons are created as separate business partners using internal numbering. Since this new numbering is only
created during the migration process, you can't use the contact person number as contact ID for partner
functions in one single step.
To assign a contact person as partner, first create the customer with the contact person, but without sales
data. Then, use the Customer - extend existing record by new org levels [page 68] migration object in a second
step to assign the sales data together with the contact person in partner capacity.
Contact Person ID
You must enter a contact person ID in the respective field on the Contact person sheet. This number is required
internal number. This business partner is automatically assigned to the customer with the corresponding
relationship.

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
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
In the Suppress Tax Jurisdiction Code check field on the General Data sheet, you can suppress the check and
Level Name

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
Tasks

Explorer.
Post-Processing


Mass change after an initial data migration can be done through:
App: Manage Mass Maintenance – Business Partners (App ID

F2505)

Further Information
● For this migration object, SAP delivers a prefilled sample XML template that helps you in filling out your
data migration template. Use this link to navigate to the Data Migration Template Samples for SAP S/
4HANA Cloud (for customers and partners only).
● 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.23 VC - Object dependencies
Purpose
Business Object Definition Object dependencies can be defined between different ob
jects in configuration.
SAP S/4HANA Supports following types of dependencies.
1. Precondition AVC
2. Selection condition AVC
3. Procedure AVC
4. Selection condition (Classic)
5. Procedure (Classic)
 Note
Classic dependencies are used in maintaining the low-level configuration for Bill of Material (BOM).

In Scope
Supported Features
● Dependencies general data

● Source code
Prerequisites

● Change numbers (optional)
 Note
If the configuration profile needs to be created with a change number, please create a change number first,
and then create a configuration profile using the change number.
Level Name
1 Dependencies general data (manda

tory)
2 Documentation
2 Multi-lingual descriptions
2 Source code

● Dependencies General Data
Dependencies name must be unique.
● Documentation

 Note
Documentation cannot be maintained without description in corresponding language.
● Multi-Lingual Descriptions
Enter a description, one in each language.
 Note
The Multi-lingual description sheet should contain at least one description per object dependency.
be displayed.
● Source Code
Maintain a source code in one line (string), for each dependency.
 Note
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 dependency will be skipped for migration.
Tasks

Explorer.
Post-Processing


1.24 VC - Dependency net
Purpose
Business Object Definition A dependency net is a group of constraints which are de
fined within a solution model and specify the relationships
between the characteristics and characteristic values of sev
eral classes.
In Scope
Supported Features
● General data
● Documentation
Prerequisites
● Change Numbers (Optional)
 Note
If the dependency net needs to be created with a change number, please create a change number first, and
then create a dependency net using the change number.

Level Name
2 Multi-lingual descriptions (mandatory)
2 Documentation

● General Data
Name of the Dependency net must be unique.
● Multi-Lingual Descriptions
Enter a description, one for each language
 Note
The Multi-lingual description sheet should contain at least one description per dependency net.
be displayed.
● Documentation
 Note
Documentation can't be maintained without description in the corresponding language.
Tasks

Explorer.

Post-Processing

1.25 DG - Assessment for packaged product (text-based)
Purpose
Business Object Component/Area Dangerous Goods (EHS-SUS-DG)
Business Object Definition A dangerous goods assessment for a packaged product con
tains classification data, dangerous goods descriptions, and
information about transport permission for the applicable
modes of transport.
In Scope
1. Migration of dangerous goods assessment data to existing compliance views and existing assessments.
Please note that you can only migrate data for compliance assessment based on compliance requirements
with a compliance pattern of type Text-Based.

Out of Scope
1. Creation of new dangerous goods assessments.

2. Migration of attachments.
Supported Features
● Dangerous Goods Assessments

● Modes of Transport
● Dangerous Goods Description for Documents
● Packaging Details
Prerequisites
● DG - Assessment for unpackaged product (text-based) [page 92] (object for migrating dangerous goods
assessments for unpackaged products)
Level Name
1 Regulation (mandatory)
2 Modes of Transport
3 Dangerous Goods Descrip

tion for Documents
2 Packaging Details
Tips on Filling the Migration Template
Packaging details are directly assigned to a compliance view. Even though you need to enter the internal
number, regulation, and processing status as key fields, only the internal number is considered during
migration. Therefore, you need only one line for the packaging details for one compliance view. If you enter
more than one line for one compliance view, the packaging details data must be identical in all lines.

Tasks

Explorer.
Post-Processing

Apps: ● For not released assessments, open the My Packaged

Dangerous Goods app and select a product to navigate
to the Classify Packaged Dangerous Goods app. Select a
regulation to check the classification in the Classify
Dangerous Good - Packaged Product app.
● For released assessments, open the Analyze Packaged
Dangerous Goods app, search for a product, and navi
gate to the Classify Packaged Dangerous Goods app. Se
lect a regulation to check the classification in the
Classify Dangerous Good - Packaged Product app.
Business Role: Dangerous Goods - Product Compliance

(SAP_BR_DG_SPLST_PCL)
1.26 DG - Assessment for unpackaged product (text-based)

Purpose
Business Object Component/Area Dangerous Goods (EHS-SUS-DG)
Business Object Definition A dangerous goods assessment for an unpackaged product

contains classification data, dangerous goods descriptions,
and information about transport permission.
In Scope
1. Migration of dangerous goods assessment data to existing compliance views and existing assessments.
Please note that you can only migrate data for compliance assessment based on compliance requirements
with a compliance pattern of type Text-Based.
Out of Scope
1. Creation of new dangerous goods assessments.

2. Migration of attachments.
Supported Features
● Dangerous Goods Assessments

● Basic Classification Details
● Basic Description
Prerequisites
● PSS - Product compliance info [page 107] (object for migrating compliance views)

Level Name
1 Regulation (mandatory)
2 Basic Description
Tasks

Explorer.
Post-Processing

Apps: ● For not released assessments, open the My

Unpackaged Dangerous Goods app and select a product
to navigate to the Classify Unpackaged Dangerous
Goods app. Select a regulation to check the classifica
tion in the Classify Dangerous Good - Unpackaged
Product app.
● For released assessments, open the Analyze
Unpackaged Dangerous Goods app, search for a prod
uct, and navigate to the Classify Unpackaged Dangerous
Goods app. Select a regulation to check the classifica
tion in the Classify Dangerous Good - Unpackaged
Product app.
Business Role: Dangerous Goods - Product Compliance

(SAP_BR_DG_SPLST_PCL)

1.27 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

App: Manage Document
Business Role: Design Engineer Role (SAP_BR_DESIGN_ENGINEER)
1.28 PM - Measurement document
Purpose
Business Object Component/Area Plant Maintenance (PM)

Business Object Definition The data transferred to the system after the measurement
has been taken at a measuring point or a counter is descri
bed in the SAP system as a measurement document. This
transfer can be performed automatically or manually.
The measurement document is therefore the result of a

measurement or counter reading being entered in the sys
tem.
In Scope
Out of Scope
Basis for measurement reading as Reference object is not supported while creating a measurement document.
You can only create measurement documents for measuring points.
Supported Features
● Measurement document header
Prerequisites
● PM - Measuring point [page 99]
● Only internal numbering is supported.

● Valuation code can only be entered into a measurement document if the associated pointer/counter refers
to a category which enables this functionality.
● Measuring unit for measurement reading will be derived from entered measuring point.
● In most cases, the Reading field is mandatory since its required for the quantitative evaluation but their is
one use case for which its not required to enter value for reading i.e. measuring point is defined for

qualitative valuation only (the Valuation code sufficient for measurement document indicator is marked),
the measurement document only includes the valuation code. All measuring documents that refer to
measuring counters, reading is mandatory.
Level Name
1 Measurement Document (mandatory)
Tasks

Explorer.
Post-Processing
App: Create Measurement Document for Technical Object
Display Measurement Document
Business Role: Maintenance planner (SAP_BR_MAINTENANCE_PLANNER)
1.29 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 115]

● PM - Functional location [page 165]
● QM/PM - Catalog code group/code [page 301]

● 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

App: Display Measuring Point
Business Role: Maintenance Planner (SAP_BR_MAINTENANCE_PLANNER)

1.30 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 Product [page 277]
● Work center/Resource [page 391]
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
App: Create Maintenance Notification
Display Maintenance Notification
Change Maintenance Notification
1.31 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 337]

Level Name
1 Chemical compliance view

(mandatory)
2 Chemical composition
3 Chemical component
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.

Post-Processing
App: Manage Raw Material Compliance
Business Role: Product Stewardship Specialist - Product Compliance

(SAP_BR_PRODSTWRD_SPLST_PCL)
Master Data Specialist - Product Compliance

(SAP_BR_MD_SPECIALIST_PCL)
1.32 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
● Component before and after production
● Legal deviation and substitute substances
● Application
● Material Assignment
● Market Coverage
● Market Request
● Bulk Assignment
● Purpose Assignment
Prerequisites

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

(mandatory)
2 Chemical composition
3 Chemical component
3 Component before and after

production

Level Name
3 Legal deviation and substi

tute substances
2 Application
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)
○ Component before and after production
○ Legal deviation and substitute substances
○ Application
○ Purpose assignment
○ Market request
○ Market coverage
2. Migrate packaged products related to product using the migration template:
○ Bulk assignment
○ Market coverage
Tasks

Explorer.

Post-Processing

App: Manage Basic Compliance Data
Business Role: Product Stewardship Specialist - Product Compliance

(SAP_BR_PRODSTWRD_SPLST_PCL)
Master Data Specialist - Product Compliance

1.33 PM - Equipment BOM
Purpose
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
App: Display Equipment BOM
1.34 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
● 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
App: Display Task List

1.35 PM - Equipment
Purpose
Business Object Definition An individual, physical object that is maintained as an auton

omous unit.
In Scope
Supported Features
● Equipment General Data

● Equipment Manufacturer Data
● Equipment Location
● Equipment Organization
● Equipment Structure
● Equipment Serial Data
● Equipment Partners
Prerequisites

● Commercial project [page 287]

● Superordinate Equipment: To use the Superordinate Equipment field, make sure this value will be
implemented in the PM - Functional location [page 165] 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)
2 Partners
Tasks

Explorer.
Post-Processing

App: Display Technical Object

1.36 Warehouse storage bin
Purpose
Business Object Component/Area Warehouse Management (SCM-EWM)
Business Object Definition A storage bin is the smallest spatial unit in a warehouse.
Therefore, a storage bin represents the exact position in the
warehouse where products can be stored.
Since the address of a storage bin is frequently derived from

a coordinate system, a storage bin is often referred to as a
coordinate. For example, the coordinate 01-02-03 could be a
storage bin in aisle 1, stack 2, and level 3.
In Scope
1. General storage bin data, such as aisle, stack, level, and coordinates
2. Status data, such as putaway and stock removal block
3. Data related to physical inventory, such as physical inventory type and date of last inventory
4. Statistics-related data, such as date and time of last movement or date and time of last bin clearing
In SAP S/4HANA Cloud Warehouse Management, a default bin sorting record is generated for each newly
created storage bin. This functionality also applies for the migration of storage bins. Migration object
warehouse storage bin sorting is available to update the generated default bin sorting data.

Out of Scope
 Note
Only the initial upload is supported. Updating existing fixed bin assignments is not supported.
Supported Features
● Header Data
● Storage Bin Data
● Status
● Physical Inventory
● Statistics
Prerequisites
The following data must have already been maintained or migrated:
● Warehouse number
● Storage types
General Instructions
You can upload storage bins for one warehouse only per file. The same warehouse number must be entered for
all storage bins.
Level Name
1 Storage bin data (mandatory)
Tasks

Explorer.

Post-Processing
App: Display Storage Bins
Business Role: Warehouse Clerk (EWM)

(SAP_BR_WAREHOUSE_CLERK_EWM)
App: Warehouse Monitor
Monitor node: Stock and Bin Storage Bin
You can enter selection criteria for storage bins that you
want to select and then see your uploaded bins.

App: Mass Change to Storage Bins

Further Information

1.37 Warehouse fixed bin assignment
Purpose
Business Object Definition In a warehouse, products can be assigned to specific storage

bins. These storage bins must be assigned the fixed bin stor
age type. The relationship between product and fixed stor
age bin is called fixed bin assignment. During the goods re
ceipt process, the products are put away in the assigned
storage bins only. During the goods issue process, the prod
ucts are picked from only those storage bins.
In Scope
Out of Scope
1. The scope is limited to the assignment itself. Additional attributes, such as quantities, are not supported.
2. Note that only the initial upload is supported. Updating existing fixed bin assignments is not supported.
Supported Features
● Fixed Bin Assignment

Prerequisites

● Warehouse storage bin [page 117]
You can upload fixed bin assignments for one warehouse only per file. The same warehouse number must be
entered for all fixed bin assignments.
Level Name
1 Fixed Bin Assignment (mandatory)
Tasks

Explorer.
Post-Processing

App: Assign Fixed Bins


Monitor node: Stock and Bin Fixed Bin Assignment
You can enter selection criteria for the combination of stor

age bin and product that you want to select and then see
your uploaded fixed bin assignments.

1.38 Warehouse storage bin sorting
Purpose
Business Object Definition A specific ranking of a storage bin into a defined sort se
quence for the combination of warehouse number, activity,
and activity area.
The bin sorting is taken into consideration for specific ware

house processes, such as picking. That is, the order of the
warehouse tasks in the warehouse order is based on the sort
sequence of the respective destination bins.
In Scope
1. An update of existing bin sorting data is supported.

2. Note that you need to create a new migration project because you can only upload the same combination
of key fields once per project.

Supported Features
● Header Data
● Bin Sorting Attributes
Prerequisites
● Storage types
● Activity areas and activities
You can upload bin sorting data for one warehouse only per file. The same warehouse number must be entered
for all bin sorting records.
Level Name
1 Bin Sorting Data (mandatory)
Prefilled Template
In SAP S/4HANA Cloud Warehouse Management, you can download your existing storage bin sorting data. The
downloaded file can be adjusted (especially the Sort Sequence of Storage Bin field) and uploaded using the SAP
S/4HANA migration cockpit. This approach can be used to facilitate the update of existing bin sorting data in
your system. You can perform the download as follows:
Monitor node: Stock and Bin Storage Bin Sorting ;

Download for Migration Cockpit method


Tasks

Explorer.
Post-Processing
Monitor node: Stock and Bin Storage Bin Sorting

Further Information
1.39 Warehouse product

Purpose
Business Object Definition Warehouse-number-dependent view of the product master

data. The warehouse product comprises all the properties of
a product that relate to its storage in a certain warehouse,
such as putaway control.
In Scope
1. General warehouse product data, such as required minimum shelf life and preferred unit of measure
2. Putaway-related data, such as putaway control and bulk storage
3. Stock removal control
Out of Scope
1. Slotting-related data
2. Storage typespecific data
 Note
Only initial upload is supported. An update of existing warehouse product data is not supported.
Supported Features
● Header Data
● General Data
● Putaway
● Stock Removal

Prerequisites
You can upload warehouse products for only one warehouse per file. The same warehouse number must be
entered for all warehouse product data.
Level Name
1 Warehouse Data (mandatory)
Tasks

Explorer.
Post-Processing

App: Manage Product Master Data
Check the Warehouse Management section of the respective

product.

Business Role: Master Data Specialist - Product Data
(SAP_BR_PRODMASTER_SPECIALIST)
Monitor node: Product Master Data Warehouse
Attribute

Further Information
1.40 Warehouse stock
Purpose
Business Object Definition Warehouse stock represents goods that are stored physi
cally in a warehouse. The warehouse stock is an entity that
describes the goods with information such as the name of
the product, the quantity, batch information, packaging in
formation, and storage bin.

In Scope
1. Unpacked stock
2. Stock in handling units (HUs)
3. Sales order and project stock
4. Batch-managed stock
Out of Scope
1. Serial numbers
2. Nested HUs
3. Auxiliary packaging material
4. Subcontractor stock and promotion stock (stock usage)
5. Capacity check: The system does not check whether the selected storage bin has the capacity to store the
quantity that is to be put away.
Supported Features
● Stock Header Data

● Stock Item Data
● Stock Data
● HU Data
● HU Weight Data
● HU Volume Data
● HU Dimension Data
Prerequisites
● Product [page 277] (products and packaging materials for stock in handling units (HUs))
● Batch (if Batch is unique at material level) [page 22] on material level (for batch stock)
● Purchasing info record with conditions [page 294] (for vendor consignment stock)

You can upload stock for one warehouse only per file. The same warehouse number must be entered for all
stock data.
In the stock item data, there are some fields that are mandatory depending on the entered value for the Item
Category for Stock Data Transfer field. Refer to the tooltips for specific information on each field.
The stock header data is made of one structure containing three fields in its key data. These three fields are
also contained in the stock item structure. Each stock item must always have one corresponding header
record. For non-packed stock, leave the Highest-Level HU field blank in both the header and item record. Also
leave the HU ID field blank in the item record.
If you do not enter specific values, the system determines HU fields of the groups HU Weight Data, HU Volume
Data, and HU Dimension Data.
You can enter a posting date on the sheet 'Stock Header Data' . This date is used in inventory management for
the related material and accounting documents. If you leave this field empty, the current date is used as the
posting date. If the posting date field is filled, the same posting date has to be entered for all warehouse
product data. Please consider that the posting date is checked in inventory management. The posting date
must be within one of the permitted posting periods in inventory management. Your settings in inventory
management determine whether posting is permitted only in the current period or also in the previous period.
 Note
If there are existing Inventory Management (IM) managed storage locations, all stock that you migrate into
Warehouse Management is also uploaded to the corresponding IM-managed storage location by default. If
you do not want to upload your stock to IM, you must enter X for the Stock Upload to WM Only field (under
Stock Header Data). You must set this for all header records or for no records. If you do not set this, it may
lead to double stock data and inconsistencies in your IM-managed storage locations.
Level Name
1 Stock header data (mandatory)
2 Stock item data (mandatory)
Tasks

Explorer.

Post-Processing

Monitor node: Stock and Bin Storage Bin Physical
Stock
You can enter selection criteria based on products or HUs

and then see your uploaded stock.

App: Stock - Multiple Materials
You can enter selection criteria based on products and see

the stock that was uploaded to the corresponding IM-man
aged storage locations.
 Note
Note that the stock is only uploaded to the correspond
ing IM-managed storage location if the Stock Upload to
WM Only field (under Stock Header Data) is left blank.
Business Role: Inventory Manager (SAP_BR_INVENTORY_MANAGER)
Further Information
1.41 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

App: Maintain Exchange Rates
Business Role: General Ledger Accountant (SAP_BR_GL_ACCOUNTANT)
1.42 FI-CA Contract partner
Purpose
Business Object Component/Area Business Partner - Contract Accounting (AP-MD-BP, FI-CAC)
Business Object Definition A contract partner is a business partner with the role of con
tract partner. Contract Accounting only supports the usage
of contract partner.
In Scope
1. General Data including address information

The role contract partner (MKK) will automatically be assigned to all partners migrated using this
migration object.
2. Addresses

3. Bank Data
4. Payment Card Data
6. Tax numbers
Out of Scope
1. Relationship to other business partners

2. Time-dependency of addresses
3. Time-dependency of bank data
Supported Features
● General Data
● Addresses
● International Address Versions
● Bank Data
● Industries
● Tax Numbers
Prerequisites
● Bank [page 20]
● During data migration you can choose between internal and external number assignment for the new
contract partners.
● If a contract partner needs to be created with customer or supplier roles, these roles need to be
maintained manually.
● It is possible to assign more than one address to a business partner. If you assign several addresses to one
business partner, you have to assign an external address number to this business partner. The external
address number must be unique for each business partner. You can use the same external address number

for different business partners. If you assign only one address you can leave the field external address
number empty.
● During data migration you can choose whether the digital payment token within the payment card data
should be checked or not. If you migrate a huge amount of records with payment card data, the active
check will impact the performance. The digital payment token is different from the payment service
provider (PSP).
● If the Business Partner ID is to be used for integration with external systems, the key mapping can be
switched on during migration. 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 step to ensure that the key
mapping is added to the central key mapping store of the S/4HANA system.
Level Name
2 Addresses
3 International Address Ver

sions
2 Bank Data
2 Payment Card Data
2 Industries
2 Tax Numbers

If Vertex is activated (especially on US installations), the tax jurisdiction code will be determined by the
address.
this happens, you will have to provide a more detailed/accurate address: For example US Postal codes with 9
digits instead of 5 digits.
In the Suppress Tax Jurisdiction Code check field on the General Data sheet, you can suppress the check and
Tasks

Explorer.

Post-Processing



F2505)
1.43 FI-CA Contract account
 Tip

Purpose
Business Object Component/Area FI-CA
Business Object Definition Contract Accounts Receivable and Payable (FI-CA)
An account in which posting data for contracts or contract

items is processed, for which the same collection/payment
agreements apply.
Contract Accounts are managed on an open-item basis

within Contract Accounts Receivable and Payable.
In Scope
1. Contract Account: General (Header) Data

2. Contract Account: Tax Exemptions
3. Contract Account: Partner Relationships
4. Contract Account-Partner-Relationship: Lock Data
5. Contract Account-Partner-Relationship: Alternative Correspondence Recipients
6. Contract Account-Partner-Relationship: Charges and Discounts
Supported Features
● Contract Account: General (Header) Data

● Contract Account: Tax Exemptions
● Contract Account: Partner Relationships
● Contract Account-Partner-Relationship: Lock Data
● Contract Account-Partner-Relationship: Alternative Correspondence Recipients
● Contract Account-Partner-Relationship: Charges and Discounts
Prerequisites
● FI-CA Contract partner [page 132]

● Writing Change Documents is disabled by default.

● Writing Change Documents can be enabled/disabled via mapping.Contract Account-Partner-Relationship:
Alternative Correspondence Recipients
Level Name
1 General Data - Account (mandatory)
2 General Data - Partner (manda

tory)
3 Locks
2 Payments - Taxes (mandatory)
2 Dunning - Correspondence
3 Correspondence Recipients
2 Convergent Invoicing
3 Individual Charges - Dis

counts
2 Tax Exemptions
Tasks

Explorer.
Post-Processing
App: Maintain Contract Account

Business Role: Contract Account-Partner-Relationship: Alternative
CorrespondenceAccounts Payable and Receivable
Accountant (SAP_BR_APR_ACCOUNTANT_FICA)
1.44 FI-CA Open item
Purpose
FI-CAC (Contract Accounts Receivable and Payable)
Business Object Definition Receivable or Payable Open Items in Contract Accounting

are posted as an open document for a specific Contract Ac
count.
In Scope
1. Migration of Contract Accounting Data (General Data, Business Partner Line Items and General Ledger
Line Items)
2. Migration of Document Lock
3. Migration of Payment Card Data
Out of Scope
1. Migration of cleared or partially cleared documents

2. Migration of Repetition Items

3. Migration of Document Relations
4. Migration of Withholding Tax Data for Business Partner Items
Supported Features
● General Data
● Business Partner Line Items
● General Ledger Line Items
● Locking of Business Partner Items
Prerequisites
The following objects/data must have already been maintained or migrated:
● FI-CA Contract partner [page 132] (mandatory)

○ Business partner in the required Contract partner role is mandatory
● FI-CA Contract account [page 135] (mandatory)
○ Only mandatory if account assignment on cost center is necessary
● Profit center [page 272]
○ Only mandatory if account assignment on profit center is necessary
● 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
○ You have to make sure you provide only the Token you receive from SAP digital payment add-on (DP) in
the Token ID field. NEVER provide the real credit card number.
○ The Token ID may be up to 25 characters long.
● Please be aware you have to fill and save amounts in the migration file in number and not in string format.
Check the Excel settings for a delimiter.
● Posting of an internal or external document number will be managed by the given document type in the
migration template. Document types are assigned to either an internal or external number range. For an
internal number assignment, the value of the OPBEL (Number of Contract Account Receivable & Payable

Document) field will be set in the XBLNR (Reference document number) field if XBLNR is not provided in
template.
● Exchange rates between two currencies can be specified in different ways. The example below explains
what you should be aware of.
Example: Local currency is UNI, foreign currency is USD. The relation between the currencies is such that 1
USD = 2.5 UNI. The exchange rate can be quoted in the following forms:
○ (1) 2.50000 (direct quotation, 1 USD = 2.5 UNI)
○ (2) -0.40000 (indirect quotation, 1 UNI = 0.4 USD)
 Note
In the migration template, you have to use the - indicator instead of the known indicator / for the
specified indirect notation.
Level Name
2 Business Partner Line Items

(mandatory)
3 Locking of Business Partner

Items
2 General Ledger Line Items
2 Payment Card Data
Tasks

Explorer.
Post-Processing
Follow-On Activities
It might be necessary to close used reconciliation keys using the Change Reconciliation Key or Delete and Close
Reconciliation Keys apps which are included in the Reconciliation Specialist role
SAP_BR_RECONC_SPEC_APR_FICA.

App: Display Document
Business Role: - Accounts Payable and Receivable Accountant (FI-CA)

(SAP_BR_APR_ACCOUNTANT_FICA)
1.45 FI-CA Provider contract
Purpose
Business Object Component/Area FI-CAC
Business Object Definition A provider contract comprises all legally binding agreements
regarding the provision and billing of services that are en
tered into by a company for a specified period of time.
Each contract item contains a reference to a contract ac

count and a material.
There must be a main item at every point in time from the

contract start to the end of the contract. Contract items are
valid for a limited time. All contract items with the same ex
ternal GUID represent the same contract item from a logical
perspective, however at different points in time.
 Note
During the migration of provider contracts, only the current status of provider contracts is considered.
Changes to the contract in the past, which led to a chronology of the provider contract in the legacy
system, are not transferred.

In Scope
Out of Scope
1. Provider Contract Item Conf Configuration

2. Provider Contract Item Conf Reference
3. Provider Contract Item Conf Instance
4. Provider Contract Item Conf Part
5. Provider Contract Item Conf Value
Supported Features
● Provider Contract: Provider Contract Header

● Provider Contract: Provider Contract Item
● Provider Contract: PC Item Discount
● Provider Contract: PC Item Service Type
● Provider Contract: PC Item Technical Resource
● Provider Contract: PC Item Billing Plan Header
● Provider Contract: PC Item Billing Plan Item
● Provider Contract: PC Item Billing Plan Reference
● Provider Contract: PC Item Conf Configuration
● Provider Contract: PC Item Conf Reference
● Provider Contract: PC Item Conf Instance
● Provider Contract: PC Item Conf Part
● Provider Contract: PC Item Conf Value
Prerequisites
A provider contract relates to exactly one business partner. Creating Business Partners in the required role
(Contract Partner, Contract Accounts and Materials) is mandatory before the migration of Provider contracts.
Please refer to the FI-CA Contract partner [page 132], FI-CA Contract account [page 135], and Product [page
277] migration objects.

Level Name
1 Provider Contract
Header (mandatory)
2 Provider Contract Item

(mandatory)
3 PC Item Discount
3 PC Item Service Type
3 PC Item Technical Re

source
3 PC Item Billing Plan

Header

Item

Reference
3 PC Item Conf Configu

ration
3 PC Item Conf Refer

ence
3 PC Item Conf Instance
3 PC Item Conf Part
3 PC Item Conf Value
Contract Item ID field
Enter the GUID of the contract in the SAP CRM source system. If your source is not an SAP CRM source, please
provide a valid GUID.
You may search on the Internet for GUID Generator to generate valid GUID. The GUID must not be used in the
current SAP S/4HANA or SAP S/4HANA Cloud systems.
Tasks

Explorer.

Post-Processing
App: Maintain Provider Contract
Business Role: Accounts Payable and Receivable Accountant (FI-CA)

Accounts Payable and Receivable Manager (FI-CA)

(SAP_BR_APR_MANAGER_FICA)
1.46 Fixed asset (incl. balances and transactions) (deprecated)
 Caution
This migration object is deprecated as of release SAP S/4HANA Cloud 1911. Until its final deletion, it is
solely available for compatibility reasons. Only customers who started their migration project in release
SAP S/4HANA Cloud 1908 may still use it.
Be aware that the documentation for this migration object which you find below, only reflects the status of
release SAP S/4HANA Cloud 1908.
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
● Inventory
● Posting Information
● Time-Dependent Data
● Origin
● Acct Assignment for Investment
● Depreciation Areas
● Cumulative Values
● Posted Values
● Transactions
● Proportional Values on Transactions
● CountrySpecific
 Note
As of SAP S/4HANA Cloud 1905, the following countryspecific fields for Japan are supported:
● Sort Key 5 (Allocations category) is enabled as city code for the Japan Property Tax Report.
● Property Classification Key (Net worth valuation category) is enabled as Property Classification Code
for the Japan Property Tax Report.
● Reason for Manual Valuation of Net (Net worth valuation category) is enabled as reason code for a
special depreciation rate for the Japan Property Tax Report.
● Leasing Agreement Date (Leasing category) is enabled as leasing agreement date for the Japan
Annex16 Report.
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.)
○ 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.
 Note
As of SAP S/4HANA Cloud 1902, customers with active company codes in the country USA (but not
customers who scoped US Corporate GAAP only) have to consider the following:
In order to fulfill the requirements of the mid-month convention, there is a different period control with 24
real calculation periods (instead of the previously used 12 periods). The change is only relevant for Asset
Accounting; the fiscal year variant used in the general ledger remains unchanged.
You have to take the new system behavior into account when specifying the useful life in the asset master
data. Example: In previous releases, you would have entered 4 years and 5 periods (representing 5 months)
for the useful life; now you have to enter 4 years and 10 periods instead.
Restrictions
External number assignment for assets is not supported. All asset classes must have internal number
assignment.

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

● Activity type [page 211]
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 either use the default setting or you contact the SAP Service Center team.
● 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 the Make Company Code Settings app.
● 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.
● Make sure that the configuration settings in the Q system are the same as in the P system.

Required Activities
● The previous fiscal year must be closed in Asset Accounting.

This can be checked using the Undo Year-End Closing – For Asset Accounting app.
● 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 apps:
● Create Asset Master Record - For Legacy Asset

● Post Transfer Values - For Legacy Asset
● Transfer Open Items of AUC - For Legacy Asset
● Post Miscellaneous Transactions
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.

App: Asset History Sheet
Display Asset Master Worklist
Manage Fixed Assets (can be accessed via the Display Asset

Master Worklist app)
Display Asset
Asset Balances
 Note
You should also check the G/L balances.
Business Role: Asset Accountant (SAP_BR_AA_ACCOUNTANT)
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) (deprecated): 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.47 Fixed asset - Master data
Purpose
With this migration object, you perform a legacy data transfer for asset master records.


If you want to transfer both, asset master data and transaction data, you proceed as follows:
1. You transfer the asset master data with this migration object:Fixed asset - Master data
2. You transfer the transaction data with migration object Fixed asset - Postings [page 155].
In Scope
Supported Features
● General
● Origin
● Allocations
● Account Assignment
● Valuation
● Time-Based Valuation

● CountrySpecific - Time-Independent Data
● CountrySpecific - Precious Materials
● CountrySpecific - Time-Dependent Data
● CountrySpecific - Time-Dependent Data for Valuation
 Note
As of SAP S/4HANA Cloud 1911, countryspecific fields are supported for the following countries:
● Russia
● Japan
● Portugal
● China
● India
You use the SAP S/4HANA Migration Cockpit to transfer legacy data asset master records.
When you want to transfer asset subnumbers, you need to consider the following:
● Asset subnumbers must be migrated within the same migration project. (This is due to the projectspecific
mapping table of the main asset number.)
● 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.)
Restrictions
External number assignment for assets is not supported. All asset classes must have internal number
assignment.
The transfer of assets under construction (AUC) that are integrated with investment measures is not
supported. Data for AUC and WBS must be transferred manually in a consistent manner, and the information
must be linked afterwards.
Prerequisites

● Activity type [page 211]

Level Name
1 General (mandatory)
2 Origin
2 Inventory
2 Allocations
2 Origin
2 Valuation
2 Time-Based Valuation
2 Country-Spec.
2 Country-Spec. - Prec. Mat.
2 Country-Spec. - TDD
2 Country-Spec. - TDD for Val.
Dependencies: If you use the Country-Spec. - TDD for Val. sheet in the migration template, you must also fill in
the Valuation sheet.
Required Configuration Settings
● 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.
● You have created a legacy data transfer segment, and you have specified the transfer date, the document
type and the legacy data transfer status for it in the Make Company Code Settings app.
Required Activities

This can be checked using the Perform/Undo Year-End Closing app.

Pretest
For master records, you can use the Manage Legacy Assets app.
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.
Tasks

Explorer.
Post-Processing
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.


Manage Fixed Assets
Asset Balances
 Note
Changing Transferred Data Subsequently
When uploading the migration template, the system transfers the asset master records. If incorrect data has
been transferred, we recommend the following: 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
Migration object documentation for Fixed asset - Postings [page 155].
Application help (product assistance) under Asset Accounting Legacy Data Transfer .
1.48 Fixed asset - Postings
Purpose
With this migration object, you perform a legacy data transfer for transaction data in asset accounting (asset
values).
Business Object Type Transactional data (asset values)



In Scope
Supported Features
● Posting Key
● Cumulative Values
● Posted Values
● Posting Headers
● Transactions
● Proportional Values
You use the SAP S/4HANA Migration Cockpit to transfer legacy data for asset transactions.
● 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.
● You can also transfer quantities:
○ To transfer quantities, you use the Posting Headers sheet in the migration template.
○ If an opening balance for an asset needs to be posted as a quantity, the Assignment Number field
needs to be filled with the string STARTQUANTITY. Please note the following:
○ Only one such an entry is allowed per asset.
○ Apart from the key fields, the field Base Unit of Measure must be filled as well.

○ The Assignment Number field must be supplied with the string STARTQUANTITY.
○ The quantity must be positive.
 Example
You want to post the quantity 5 pieces as opening balance quantity for the fiscal year of the legacy
transfer.
Fiscal Year = YYYY
Sequence Number of Asset Line Items in Fiscal Year = 1
Assignment Number = STARTQUANTITY
Quantity = 5
Base Unit of Measure = PC
● You use this migration object and its migration template to post accumulated data for amount values as
well as quantity. In either case, you need to transfer the master data beforehand with the Fixed asset -
Master data [page 151] migration object.
 Note
When using the SAP S/4HANA Migration Cockpit, asset-related G/L account balances are updated
automatically. No special transfer for asset reconciliation accounts in G/L is needed.
 Note
Customers with active company codes in the country USA (but not customers who scoped US Corporate
GAAP only) have to consider the following:
To fulfill the requirements of the mid-month convention, there is a different period control with 24 real
calculation periods (instead of the 12 periods previously used). The change is only relevant for Asset
Accounting; the fiscal year variant used in the general ledger remains unchanged.
You have to take the new system behavior into account when specifying the useful life in the asset master
data. For example: In previous releases, you would have entered 4 years and 5 periods (representing 5
months) for the useful life; now you have to enter 4 years and 10 periods instead.
Restrictions
The transfer of assets under construction (AUC) that are integrated with investment measures is not
supported. Data for AUC and WBS must be transferred manually in a consistent manner, and the information
must be linked afterwards.

Prerequisites
The following object must have already been maintained or migrated:
Level Name
1 Posting Key (mandatory)
2 Cumulative Values
2 Posted Values
2 Posting Headers
2 Transactions
2 Proportional Values
Required Configuration Settings
● You have made the configuration 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 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 migration template, make sure that you enter your historical foreign currency values
consistently in the Cumulated Values and Posted Values worksheets.
● The offsetting account for the legacy data transfer (asset balance sheet account) must be defined.
This is done in the Manage Your Solution app under Configure Your Solution Finance Asset
Accounting Configure Asset Accounting Assign General Ledger Accounts . In this configuration step
(SSCUI), you have to make sure, that the Offsetting Account for Legacy Data Transfer (KTLDT) is set, the
default account is 39913000.
● 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 the Make Company Code Settings app.
● If you want to perform a transfer during the year and you want to transfer the posted depreciation, 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 to be posted in the SAP system.
Required Activities

This can be checked using the Perform/undo Year-End Closing app.
Pretest
You can use the following apps:
● Post Transfer Values - For Legacy Asset

● Transfer Open Items of AUC - For Legacy Asset
● Post Miscellaneous Transactions
After this, you prepare the Microsoft Excel migration 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.

Tasks

Explorer.
Post-Processing
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.
Manage Fixed Assets
Asset Balances
Depreciation Lists
Asset Transactions
 Note
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.
In the productive system, there should be no data before you start the file upload.

Further Information
Migration object documentation for Fixed asset - Master data [page 151].
Application help (product assistance) under Asset Accounting Legacy Data Transfer .
1.49 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

1.50 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

App: Display Functional Location BOM
1.51 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.
Tasks

Explorer.
Post-Processing

App: Display Technical Object
1.52 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

1.53 FI - G/L account balance and open/line item

 Tip
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 - Postings [page 155] 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 174] 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 - Postings [page 155] object.
Use the Define Settings for Legacy Data Transfer app 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 130]
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 document date provided.
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 configuration of automatic CO assignment on accounts: Manage Your Solution Configure Your
Solution Finance | General Settings | Journal Entry ; Manage Default Account Assignment step. Please note,
if this required CO object is not provided via template, the default CO assignment will be used automatically for
migration.
Level Name
1 Header + Item (mandatory)
Tasks

Explorer.

Post-Processing
App: Manage Journal Entries (Display)
Display G/L Account Line Items (Display)
Post General Journal Entries (Create)
Further Information
1.54 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 with zero effects. This means that these balan
ces will automatically be reversed on the predefined migra
tion key date in order to have a zero balance. The migrated
historical balances are intended as an approach for report
ing. It is not possible to view the migrated documents them
selves.
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 (manually)

To be posted, G/L accounts must be maintained
● Choose the required migration approach for historical balances in Migration Cockpit via the Import method
for historical balances 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 Movement (NPM): 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. You don't need to reverse any data as this uploaded
data wasn't posted.
● 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. Do not use
different signs (positive and negative) within same record. 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

App: Display G/L Account Balances (Display)
Trial Balance (Display)

1.55 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 323]

● QM - Selected set code [page 325]
● 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

App: Display Inspection Methods
Business Role: Business Role: Quality Planner

(SAP_BR_QUALITY_PLANNER)
1.56 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 178]
● QM - Master inspection characteristic [page 251]
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)

Level Name
3 Inspection Characteristics
Tasks

Explorer.
Post-Processing

App: Display Inspection Plan
1.57 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

App: Display Material

1.58 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

In case of inventory managed storage locations, the initial entry of inventory data will always create a material
document for each unique identifier entered on the Material Document Header sheet in the Technical
Document Number field. The movement type for all material documents is 561 – initial entry of stock balances.
The GM code for all material documents is 05– initial entry of stock balances.
 Note
If you've activated the Third-Party Warehouse Management System Integration (1ZQ) scope item,
download the respective Set-up instructions from SAP Best Practices Explorer and carefully follow the
instructions. You must migrate the inventory balances before you assign the warehouse number to the
plant/storage location. Otherwise, the initial entry of inventory data will always create an inbound delivery
and the posting date will always be set to the current date by the system, and the posting date won't be
derived via the Define Settings for Legacy Data Transfer app. Material documents would only be posted to
SAP S/4HANA Cloud if the deliveries have been processed in the decentralized warehouse management
system and the confirmation messages have been received by SAP S/4HANA Cloud.
See the Set-up instructions of the Third-Party Warehouse Management System Integration (1ZQ) scope
item.
For Extended Warehouse Management please use the Warehouse stock [page 127] migration object.
● 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
except for the Fixed asset - Master data [page 151] object.

possible)
● Product [page 277]: If you don't provide the external amount for the stock load the system will calculate
the value with the material prices defined in the material master in the accounting data. Please ensure in
that case that the price data provided in the material master is accurate.
● Batch (if Batch is unique at material level) [page 22] (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 386]/Customer [page 79] (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 294] 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 Plant field

You can only provide plants which are assigned to the used company code.
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

App: Stock Single Material
Stock Multiple Materials
Material Inventory Values - Balance Summary
Trial Balance

Business Role: Inventory Manager (SAP_BR_INVENTORY_MANAGER)
General Ledger Accountant (SAP_BR_GL_ACCOUNTANT)
Further Information
● Find FAQs relating to this migration object in SAP Knowledge Base Article 2813720 .
1.59 JVA - Joint operating agreement
Purpose
Business Object Component/Area Joint Venture Accounting for Oil and Gas (CA-JVA)

Business Object Definition Companies in the Oil & Gas industry typically form joint ven
ture partnerships to minimize risks involved in the Oil & Gas
upstream capital-intensive operations that demand a long
payback period. A joint venture partnership consists of an
operating partner (operator) and one or more non-operating
partners who combine monetary or personnel resources to
share a project’s expenses and revenues. The operator man
ages the venture, arranges venture activities, and maintains
accounting records in his or her own financial books. The op
erator remits venture expenses, collects revenues, and dis
tributes these to the partners, according to their ownership
shares.
The Joint Operating Agreement (JOA) contains the contrac

tual agreements between joint venture partners including
the definition of the equity group.
In Scope
Supported Features
● Joint operating agreement

● JOA Desc.
● Equity groups
● Equity group description
● Equity group - Partner
● General overhead
● Stepped rate overhead
● Stat. ratio - Producing
● Stat. ratio - Producing thresholds
● Stat. ratio - Drilling
● Parent company overhead
● Payroll burden
● CI penalties

Prerequisites
● JVA - Joint venture partner [page 192]

● A mixture of external and internal numbering; JOA should be split into separate files for internal and
external number objects and then the control parameter should be set separately for each file and
migration run. Don’t upload and activate both files at the same time, as they'll then be processed in parallel
and the current control parameter setting will be thrown for both files.
Level Name
1 Joint operating agree

ment (mandatory)
2 JOA Desc. (manda

tory)
2 Equity groups
3 Equity group descrip

tion
3 Equity group - Partner
2 General overhead
3 Stepped rate overhead
3 Stat. ratio - Producing
4 Stat. ratio - Producing

thresholds
3 Stat. ratio - Drilling
2 Parent company over

head
2 Payroll burden
2 CI penalties
Tasks

Explorer.

Post-Processing

App: Maintain Joint Operating Agreement
Business Role: Joint Venture Accountant (SAP_BR_JVA_ACCOUNTANT)
1.60 JVA - Joint venture partner
Purpose

accounting records in his own financial books. The operator
remits venture expenses, collects revenues, and distributes
these to the partners, according to their ownership shares.
The Joint Venture (JV) partner defines the Equity Group of a

venture. Before you can set up an Equity Group, you need to
create a JV partner.
In Scope
Out of Scope
1. Substance groups are not supported

2. Attachments are not supported
Supported Features
● Create Master Data

● Edit Master Data
● Delete Master Data
Prerequisites
● Listed Substance must exist (Manage Listed Substance app)

● The organizational structure and master data of the company must have been created in the system
during activation. The organizational structure reflects the structure of the company.
● Master Data for Business Partner FI Customer needs to be available.

Level Name
1 Partner (mandatory)
Tasks

Explorer.
Post-Processing
App: Maintain Joint Venture
1.61 JVA - Cost center suspense

Purpose
Business Object Definition If a partner, or equity group or cost object is suspended, cut
back postings are not executed. When you remove the
project, partner, cost object or equity group from suspense,
cutback processes all expenses incurred during suspense.
Suspended partners do not receive an invoice. When part
ners are removed from suspense, they receive an invoice
that includes expenses for the complete period of suspense.
Suspense:
When you place an object in Suspense, all summary records

with billable RI and one of the objects above in suspense are
transferred to a suspense Recovery Indicator. The billable re
cords are balanced to zero and are therefore not subject to
cutback.
Unsuspense:
When you remove an object from suspense, all summary re

cords with suspense recovery indicator of the unsuspended
objects are transferred to a billable record. The suspended
records are balanced to zero. The billable records are then
cutback in the unsuspense period.
In Scope
1. JV Cost Center in Suspense
Out of Scope
1. Partner
2. Equity group
3. Projects
4. Ventures
5. Orders

Supported Features
● JV Cost Center in Suspense
Prerequisites
 Note
The organizational structure and master data of the company must have been created in the system during
activation. The organizational structure reflects the structure of the company.
● JVA - Joint venture master data [page 202]
Level Name
1 JV Cost center in Suspense
Tasks

Explorer.

Post-Processing

App: Suspend Cost Centers
Overhead Accountant (SAP_BR_OVERHEAD_ACCOUNTANT)
1.62 JVA - Venture suspense
Purpose

then cutback processes all expenses incurred during sus
pense. Suspended partners do not receive an invoice. When
partners are removed from suspense, they receive an invoice
Suspense:
When you place an object in suspense, all summary records

cutback.
Unsuspense:

cords with suspense recovery indicator of the unsuspended
In Scope
1. JVA - Venture suspense
Out of Scope
1. Partner
2. Equity group
3. Cost Centers
4. Projects
5. Orders
Supported Features
● JVA - Venture suspense

Prerequisites
 Note
Level Name
1 JVA - Venture in suspense
Tasks

Explorer.
Post-Processing
App: Suspend Joint Venture

1.63 JVA - Project suspense
Purpose
then cutback processes all expenses incurred during sus
pense. Suspended partners do not receive an invoice. When
partners are removed from suspense, they receive an invoice
Suspense:
When you place an object in suspense, all summary records

cutback.
Unsuspense:

cords with suspense Recovery Indicator of the unsuspended
In Scope
1. JV Project in Suspense
Out of Scope
1. Partner

2. Equity group
3. Cost Centers
4. Ventures
5. Orders
Supported Features
● JV Project in Suspense
Prerequisites
 Note
Level Name
1 JV Project in suspense
Tasks

Explorer.

Post-Processing

App: Suspend Projects
Project Financial Controller

(SAP_BR_PROJ_FIN_CONTROLLER)
1.64 JVA - Joint venture master data
Purpose

accounting records in his own financial books. The operator
remits venture expenses, collects revenues, and distributes
these to the partners, according to their ownership shares.
The Joint Venture is used to identify the type of venture,

such as corporate, operated, or non-operated, as well as the
partners and their working interests within the joint operat
ing agreement.
In Scope
Out of Scope
Internal numbering is not supported in SAP S/4HANA Cloud 1905.
Supported Features
● Joint Venture
● Joint Venture Description
● Equity Group Assignment
● Equity Group JV Level
● Equity Group JV level - Partner Share
● Equity Group - Cross Company Venture
● Equity Group - Substitute Cost Object
● Equity Group JV Level - Funding Currency

Prerequisites
● JVA - Joint venture partner [page 192]

● JVA - Joint operating agreement [page 189]
Level Name
1 Joint Venture (manda

tory)
2 Joint Venture Descrip

tion (mandatory)
2 Equity Group Assign

ment
3 Equity Group JV level -

Partner
4 Equity Group JV Level -

Carried Interest
3 Equity Group - Cross

Company Venture
3 Equity Group - Substi

tute Cost Object
3 Equity Group JV Level -

Funding Currency
Tasks

Explorer.

Post-Processing
App: Maintain Joint Venture
1.65 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
● Main Data
● Basic Data
● Control
● Organizational Units
● Budget Availability Control
● Address
● Communication
● Joint venture
Prerequisites
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.


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
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

App: Manage Cost Centers
Business Role: Cost Accountant - Overhead

(SAP_BR_OVERHEAD_ACCOUNTANT)
Further Information

1.66 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


this happens, you will have to provide a more detailed/accurate address, for example, 9 digit US Postal codes
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)

Further Information
For information regarding the used API see SAP Note 1348099 .
1.67 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
App: Manage Activity Types
Business Role: Cost Accountant - Overhead

(SAP_BR_OVERHEAD_ACCOUNTANT)
1.68 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 112]
● PM - Functional location task list [page 161]
● PM - General maintenance task list [page 167]
● PM - Measuring point [page 99] (performance-based maintenance plan)
● PM - Measurement document [page 97] (performance-based maintenance plan)
● 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

App: Display Maintenance Plan
1.69 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
The following object must have already been maintained or migrated:
Tasks

Explorer.
Post-Processing
App: Classify Products/Reclassify Products
Business Role: Trade Classification Specialist

(SAP_BR_TRD_CLS_SPECIALIST)
1.70 Material - Forecast planning
 Restriction
● To migrate material consumptions please use the new Product consumption [page 275] migration
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

● Forecast Parameters (only for Forecast Values)
Restrictions
You can migrate several org. levels for a specific material with one migration template of a specific project.
Tasks

Explorer.

Post-Processing


1.71 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
184] 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
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.
Level Name
1 Basic Data (mandatory)
2 Plant Data
3 Storage Location Data
3 Forecast Parameters
3 Production Resource Data
2 Warehouse Number Data

Level Name
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
You can use the Material - extend existing record with long text [page 227] migration object to migrate material-
related long texts
You can use the Material - Forecast planning [page 217] migration object to migrate material consumptions and
forecast values (only supported for on premise).


App: Manage Mass Maintenance – Products (App ID F2505)

1.72 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.73 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)
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)
2 Material long text
2 MRP long text
2 Sales long text
Tasks

Explorer.

Post-Processing


1.74 VC - Material variant
Purpose
Business Object Definition The material master record of a material variant is linked to
the configurable material and configured using the charac
teristics of the configurable material. This variant of the con
figurable material can then be manufactured and kept in
stock.
In Scope
1. In SAP S/4HANA Cloud, we only support the data migration to Advanced Variant Configuration (AVC).
2. Class type variants (300) is supported.
3. Multiple values and negative values are allowed for characteristic value

Out of Scope
Interval assignments for characteristic value is not supported in AVC.
Supported Features
● Basic Data
● Characteristic Valuation
Prerequisites

● Object classification [page 43]
(Type 300 for SAP S/4HANA Cloud)
● VC - Configuration profile [page 58]
Level Name
2 Characteristic Valuation
Tasks

Explorer.

Post-Processing

1.75 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

App: Display Material Determination

1.76 Material (deprecated)
Purpose
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 219] 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
184] 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).
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
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 227] 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 219] migration object.

6.  Caution
Data migration doesn’t trigger the replication or the communication arrangement of the product
master via Data Replication (DRF). Nevertheless, you can replicate your product master after all
product master records have been migrated. This can be done with the following apps:
○ Use the Replicate by Object Selection app to specify the product numbers to be replicated and to
execute the replication.
○ Use the Replicate by Replication Model app if many product numbers need to be replicated with
the respective filter criteria, if needed.
For details about the apps, check the related SAP S/4HANA Cloud product assistance on SAP Help
Portal:
○ Replicate by Object Selection
○ Replicate by Replication Model
Also see the SAP Knowledge Base Article 2858316 .
Supported Features
● Basic Data
● Plant Data
● Storage Location Data
● Accounting Data
● Sales Data
● Description Data
● Unit of Measure Data
● Tax Classification Data
● Forecast Parameters
Prerequisites

● Supplier [page 386] (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
mapping store of the SAP S/4HANA system.
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.
with several tiles to manage and start the Manage Mass Maintenance – Products app. The app can be launched
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 enables you to valuate stocks of material for each batch in a different way. You can use it
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
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:
Material No. Valuation Area Valuation Type Valuation Category
A001 1010 X (Automat. Batch)
 Note
For the valuation header record, only price control V - moving average price is possible. For the dependent
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
2 Additional EANs

Level Name
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 227] migration object to migrate material
related long texts.
forecast values (only supported for on-premise solution).
You can use the Product classification - Commodity code [page 215] migration object to migrate product
classification with commodity code.



Further Information
1.77 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
● Price Data
● Prices
Prerequisites

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

Explorer.

Post-Processing

Tile: Manage Material Valuations
Business Role: SAP_BR_INVENTORY_ACCOUNTANT)
1.78 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
App: Manage Memo Records under Basic Cash Operations
Cash Specialist (SAP_BR_CASH_SPECIALIST)
To validate, filter by Company Code/Planning Level/Status/Currency.

1.79 EHS - Incident
 Note
To open the EHS - Incident migration object in the SAP S/4HANA Migration Cockpit, the Industrial Hygienist
(SAP_BR_INDUSTRIAL_HYGIENIST) business role must be assigned to the relevant user.
Purpose
Business Object Component/Area Incident Management (EHS-SUS-IM)
Business Object Definition You can use the EHS - Incident business object to record in
cidents that occur at your organization. You can record a de
scription of the events, when and where the incident occur
red, and which persons were involved. This business object
also allows you to record situations where an incident could
have occurred (near miss) and where any unsafe behavior or
condition could lead to an incident in the future (safety ob
servation).
In Scope
1. Incident: Header Data

2. Incident: General Data Texts
3. Incident: Group Data
4. Incident: Regulation Data
5. Incident: Person Data
6. Incident: Person Texts
7. Incident: Person Role Data
8. Incident: Person Statement Data
9. Incident: Person Statement Texts
10. Incident: Injury/Illness Data
11. Incident: Injury/Illness Texts
12. Incident: Absences and Restrictions
13. Incident: Health and Safety
14. Incident: Health and Safety Texts

Out of Scope
1. Notice of Violation
2. Investigation
3. Reports and documents
4. Tasks
5. Links to incidents
Supported Features
● Incident: Header Data

● Incident: General Data Texts
● Incident: Group Data
● Incident: Regulation Data
● Incident: Person Data
● Incident: Person Texts
● Incident: Person Role Data
● Incident: Person Statement Data
● Incident: Person Statement Texts
● Incident: Injury/Illness Data
● Incident: Injury/Illness Texts
● Incident: Absences and Restrictions
● Incident: Health and Safety
● Incident: Health and Safety Texts
Prerequisites
● Locations
● Business Partners
Incident start date should be in a valid revision of the location.

Level Name
1 Header Data (manda

tory)
2 General Data Texts
2 Group Data
2 Regulation Data
2 Person Data
3 Person Texts
3 Person Role Data
3 Person Statement
Data
4 Person Statement
Texts
3 Injury/Illness Data
4 Injury/Illness Texts
3 Absences and Restric

tions
3 Health and Safety
4 Health and Safety

Texts
Tasks

Explorer.

Post-Processing
How to Validate Your Data in the System
App: Manage Incidents
Business Role: Industrial Hygienist (SAP_BR_INDUSTRIAL_HYGIENIST)
1.80 Condition record for pricing in purchasing (restricted)
 Restriction
This migration object only supports the condition types and key combinations mentioned in the Supported
Combinations of Key Fields for Price Conditions file. For other condition types and key combinations,
please use the Condition record for pricing (general template) [page 54] migration object.
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 (restricted) [page 317])
Supported Features
● This migration object only supports the condition types and key combinations mentioned in the Supported
Combinations of Key Fields for Price Conditions file.
● For other key combinations you must use the Condition record for pricing (general template) [page 54]
migration object.
Prerequisites

Level Name
1 Pricing condition records (mandatory)
2 Scales
For more information on how to fill the condition types and key combinations refer to the Supported

Tasks

Explorer.
Post-Processing
Purchaser (SAP_BR_PURCHASER)


Examples
1,000 EA 100,00000 EUR
100,000 EA 90,00000 EUR

1,000 KG 100,00000 EUR
100,000 KG 90,00000 EUR
Further Information
1.81 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 178]
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)

Level Name
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

App: Display Master Inspection Characteristics
1.82 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
Business Role: Manage JIT Customer Data

(SAP_BR_MD_SPECIALIST_JIT)
App: Manage JIT Customer Data
1.83 JIT - Package group

Purpose
Business Object Definition The package specification enables you to create a package
definition based on which package units can be created for
delivery.
In Scope
1. Migration of Package Specification Detail

2. Migration of Slot Group
3. Migration of Specification Description
Supported Features
● Package Specification Detail

● Slot Group
● Specification Description
Prerequisites
● JIT - Supply control [page 258]

Level Name
1 Package Specification Detail (manda

tory)
2 Slot Group
2 Specification Description (mandatory)
Tasks

Explorer.
Post-Processing
App: Manage Package Specifications for Sequenced JIT Calls
Business Role: Master Data Specialist - Just-In-Time Supply

App: Manage Packing Specifications for Sequenced JIT Calls

1.84 JIT - Supply control
Purpose
Business Object Definition Supply controls enable you to control the business process
ing of JIT calls received from customers.
In Scope
1. Migration of Basic Data

2. Migration of Tolerance
3. Migration of Supply Control Description
Supported Features
● Basic Data
● Tolerance
● Supply Control Description
Prerequisites
● JIT - Customer [page 253]

Level Name
2 Tolerance
2 Supply Control Description (manda

tory)
Tasks

Explorer.
Post-Processing
App: Manage JIT Customer Supply Controls
Business Role: Master Data Specialist - Just-In-Time Supply

App: Manage JIT Customer Supply Controls

1.85 FI - Accounts payable open item
 Tip
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.
7. Use the SAP Fiori app Receive Bill of Exchange to do the manual posting. Make sure your user is assigned to
the countryspecific business role AP_ACCOUNTANT_XX (XX = country code suffix).
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. 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 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.
The exchange rate will be determined using the provided document date.
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 configuration must be predefined: Configure Your Solution Chart of
Accounts Define Alternative Reconciliation Accounts (search for ID 102631).
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
[page 169] migration object.

App (general): Manage Journal Entries
Business Role (general): Accounts Payable Accountant (SAP_BR_AP_ACCOUNTANT)
App (country specific for deferred tax): Transfer Deferred Tax
Analyse Deferred Tax Accounts
Business Role (country specific for deferred tax): General Ledger Accountant for Malaysia
(SAP_BR_GL_ACCOUNTANT_MY)
General Ledger Accountant for Spain

(SAP_BR_GL_ACCOUNTANT_ES)
General Ledger Accountant for Bulgaria

(SAP_BR_GL_ACCOUNTANT_BG)
General Ledger Accountant for Italy

(SAP_BR_GL_ACCOUNTANT_IT)
General Ledger Accountant for Slovakia

(SAP_BR_GL_ACCOUNTANT_SK)
General Ledger Accountant for Mexico

(SAP_BR_GL_ACCOUNTANT_MX)
General Ledger Accountant for Russia

(SAP_BR_GL_ACCOUNTANT_RU)
General Ledger Accountant for Greece

(SAP_BR_GL_ACCOUNTANT_GR)
General Ledger Accountant for France

(SAP_BR_GL_ACCOUNTANT_FR)
General Ledger Accountant for Hungary

(SAP_BR_GL_ACCOUNTANT_HU)

Further Information
1.86 FI - Accounts receivable open item
 Tip
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.
7. Manual postings. For manual postings, use the SAP Fiori app Receive Bill of Exchange. Make sure your user
is assigned to the countryspecific business role AP_ACCOUNTANT_XX (XX = country code suffix).
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. 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 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.
The exchange rate will be determined using the provided document date.
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 configuration must be predefined: Configure Your Solution Chart of
Accounts Define Alternative Reconciliation Accounts (search for ID 102631).
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
[page 169] migration object.
App (general): Manage Journal Entries
Business Role (general): Accounts Receivable Accountant

(SAP_BR_AR_ACCOUNTANT)
App (country specific for deferred tax): Transfer Deferred Tax
Analyse Deferred Tax Accounts
Business Role (country specific for deferred tax): General Ledger Accountant for Malaysia
(SAP_BR_GL_ACCOUNTANT_MY)
General Ledger Accountant for Spain

(SAP_BR_GL_ACCOUNTANT_ES)
General Ledger Accountant for Bulgaria

(SAP_BR_GL_ACCOUNTANT_BG)
General Ledger Accountant for Italy

(SAP_BR_GL_ACCOUNTANT_IT)
General Ledger Accountant for Slovakia

(SAP_BR_GL_ACCOUNTANT_SK)
General Ledger Accountant for Mexico

(SAP_BR_GL_ACCOUNTANT_MX)
General Ledger Accountant for Russia

(SAP_BR_GL_ACCOUNTANT_RU)
General Ledger Accountant for Greece

(SAP_BR_GL_ACCOUNTANT_GR)
General Ledger Accountant for France

(SAP_BR_GL_ACCOUNTANT_FR)
General Ledger Accountant for Hungary

(SAP_BR_GL_ACCOUNTANT_HU)

Further Information
1.87 Enterprise project
Purpose
Business Object Component/Area Enterprise Portfolio and Project Management
Business Object Definition Enterprise projects serve as the basis for project planning,
execution and monitoring processes. For simple project sce
narios, the definition of general project data is sufficient. If a
hierarchical project structure is required, for example, for hi
erarchical project accounting purposes or more complex
project management requirements, work packages can be
created to form a project hierarchy.
In Scope

Supported Features
● Project General Data

● Work Package
Prerequisites
● Employee master (via SAP SuccessFactors)

● Plant master (manual load required)
● PSM - Fund
● PM - Functional location
Project General Data

The values in the Project Manager ID field must be synchronized to the business partner before migration.
Fields in the Joint Venture Accounting (JVA) group must only be filled if the Joint Venture has been activated in
the system.
JVA fields are dependent on Company code. Hence, Company code is a mandatory field if JVA fields are
entered.
In order to migrate a project with JVA fields, Joint venture name, Recovery indicator, Equity type, and Object
type must be entered.
Tax Jurisdiction Code is dependent on Company code. Hence, Company code is a mandatory field if a Tax
Jurisdiction Code is entered.
Work Package
Work package ID must be unique across the system. Maintain only a positive (+ve) value in the Sort number
field.
Fields in the Joint Venture Accounting (JVA) group must only be filled if the Joint Venture has been activated in
the system.
JVA fields are dependent on Company code. Hence, Company code is a mandatory field if JVA fields are
entered.
In order to migrate a work package with JVA fields, Joint venture name, Recovery indicator, Equity type, and
Object type must be entered.

If no JVA fields are entered in the work package, the JVA fields will be inherited from Project.
Tax Jurisdiction Code is dependent on Company code. Hence, Company code is a mandatory field if Tax
Jurisdiction Code entered.
Level Name
1 Project general data (mandatory)
2 Work package
Tasks

Explorer.
Post-Processing

App: Project Briefs
Project Builder
Project Control
Business Role: Project Financial Controller

(SAP_BR_PROJ_FIN_CONTROLLER)
1.88 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

App: Manage Profit Centers
Business Role: Divisional Accountant (SAP_BR_DIVISION_ACCOUNTANT)
1.89 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



1.90 Product
Purpose
Business Object Component/Area Product Master (LO-MD)
The total of all product master records.
A company manages the data on all its products in the prod

uct master.
In Scope
1. Initial Load of Products

2. Basic Data
3. Plant Data
4. MRP Area
5. Storage Location
6. Valuation Data
 Note
184] migration object as the system will calculate the values of the stock posting with the price data
provided in the product master if you don't provide the External Amount for loading the stocks.
In the case of Single Batch Valuation, please follow the mapping instructions provided.
7. Distribution Chain 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).
In this view, you can maintain the Tax data (from Sales Org Data 1) .

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.
 Note
For the tax indicator for the product (purchasing), enter the value in the Tax Indicator field in the
Purchasing group on the Plant Data sheet for the country relating to your plant.

12. Data for Quality Management
13. Additional EANs
14. Change Management assignment based on Change Number and Revision Level
Out of Scope
1. Production Resource Tool (PRT) fields in the Product Master

2. Material long text (therefore, use the Material - extend existing record with long text [page 227] migration
object)
3. Data transfer for unplanned consumption
4. Data transfer for total consumption of material
5. Enhance already existing data. For the Product migration object you must currently use the Material -
extend existing record by new org levels [page 219] migration object. But note that this migration object
does not support all of the organizational units which can be migrated using the Product migration object.
For example, the MRP Area structure is only supported by the Product migration object, but not by the
Material - extend existing record by new org levels [page 219] migration object. Please bear this limitation
in mind when using Material - extend existing record by new org levels [page 219] to enhance data
migrated with the Product migration object.
6. Classification data (therefore, use the Object classification [page 43] migration object)
7. Inspection types (therefore, use the Material inspection setup [page 182] migration object)
8. VC - Material Variant (therefore, use the VC - Material variant [page 229] migration object)
9. EWM Product (therefore, use the Warehouse product [page 124] migration object)
10. Product consumption (therefore, use Product consumption [page 275] migration object)
11.  Caution
Data migration doesn’t trigger the replication or the communication arrangement of the product
master via Data Replication (DRF). Nevertheless, you can replicate your product master after all
product master records have been migrated. This can be done with the following apps:
○ Use the Replicate by Object Selection app to specify the product numbers to be replicated and to
execute the replication.
○ Use the Replicate by Replication Model app if many product numbers need to be replicated with
the respective filter criteria, if needed.
For details about the apps, check the related SAP S/4HANA Cloud product assistance on SAP Help
Portal:
○ Replicate by Object Selection
○ Replicate by Replication Model

Also see the SAP Knowledge Base Article 2858316 .
Supported Features
● Basic Data
● Material Descriptions
● Alternative Unit of Measure
● Additional EAN's
● Distribution Chains
● Tax Classification
● Plant Data
● Forecasting Data
● Storage Locations
● MRP Area
● Valuation Data
● Valuation Current Period
● Valuation Future Prices
Prerequisites

● Supplier [page 386] (Manufacturer)
● Be aware of the defined length set for the product number in the system. Do not convert a product number
to a new number longer than the defined length set.
● If the Product 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
mapping store of the SAP S/4HANA system.
Indicator Product 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 set by default 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 product as configurable for products with other product types assigned (not
KMAT), you have to enter this indicator on the Basic Data sheet in the Product 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 product is managed in batches, set the Batch management requirement indicator 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 product. This is applicable for all
plants that are not flagged with the Batch Management not active by default indicator in the SSCUI .
Unit of Weight
If you want to migrate sales data for your product, the Unit of Weight field will be set to the default
automatically if it's assigned to the related Product group. If no default unit of weight is assigned to the Product
group, you have to provide the Unit of Weight field on the Basic Data sheet.
Recommendation on How to Handle Cross-Plant Product Status and Plant-Specific Product

Status
If you set the product status during initial load of the products, 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 product 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 product 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.
with several tiles to manage and start the Manage Mass Maintenance – Products app. The app can be launched
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.
Valuation Data
During migration, you have various possible ways in which to migrate your valuation data. If you only provide
your data on the Valuation Data sheet, 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 for your deviant

currency, you can specify the material ledger price on the Valuation Current Period and Valuation Future Price
sheets (the system will then take over this price and will not automatically convert the currencies using the
exchange rate defined in the system for the specified currency type).
 Example
You provide the prices for company currency on the Valuation Data sheet only . The system will determine
the prices automatically for all deviant currencies, depending on the current exchange rate defined in the
system :
Inventory Inventory
Price Price
Product Valuation Valuation Valuation Price Moving Standard
Number Area Type Category ... Control Currency Average Price ...
A001 1010 S EUR 10,00
A002 1010 V EUR 20,00
 Example
You provide the prices for company currency on the Valuation Data sheet and the prices for the deviant
currencies (for example, group currency with currency type 30) on the Valuation Current Period sheet and
on the Valuation Future Price sheet:
● Valuation Data sheet:
Inven Inven
tory tory
Price Price
Product Valuation Valuation Valuation Price Moving Standard
Number Area Type Category ... Control Currency Average Price ...
A001 1010 S EUR 10,00
A002 1010 V EUR 20,00
● Valuation Current Period sheet:
Inventory Inventory
Price Mov Price
Product Valuation Currency Price Con ing Aver Standard
Number Area ... Type trol Currency age Price ...
A001 1010 30 S USD 15,00
A002 1010 30 V USD 30,00
● Valuation Future Price sheet:
Product Valuation Currency Future Price

Number Area ... Type Currency Future Price From ...
A001 1010 30 USD 16,01 01.04.2020

Product Valuation Currency Future Price
Number Area ... Type Currency Future Price From ...
A002 1010 30 USD 31,02 01.04.2020

Single Batch Valuation enables you to valuate stocks of product for each batch in a different way. You can use it
To work with valuation for a single batch, you must choose valuation category X - for Automat. Batch. Provide
this on the Valuation Data sheet in the Valuation Category field.
 Note
The product itself needs to be managed in batches, therefore you have to provide the Batch management
If you use the single batch valuation for your product, 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.
 Example
● Valuation Data sheet:
Inventory Inventory
Price Price
Product Valuation Valuation Valuation Cur Price Moving Standard
Number Area Type Category rency... Control ... Average Price ...
B001 1010 X (Auto EUR V 21,00

mat.
Batch)
B001 1010 C1 X (Auto EUR S 20,00

mat.
Batch)
B001 1010 C2 X (Auto EUR S 21,00

mat.
Batch)
 Note
For the valuation header record, only price control V - moving average price is possible. For the dependent
For the valuation header record, you can't provide Material Ledger prices on the Valuation Current Period or
Valuation Future Price sheets. This is only possible for the dependent type records with the valuation type
specified.

For example, you'd fill out the Valuation Current Period sheet as follows:
Inventory Inventory
Price Price
Product Valuation Valuation Valuation Currency Price Moving Standard
No. Area Type Category Type Control Currency Average Price Price unit
B001 1010 C1 X (Auto 30 (Group S USD 20,10 1

mat. Currency)
Batch)
B001 1010 C2 X (Auto 30 (Group S USD 22,00 1

mat. Currency)
Batch)
How to Deal with Reference Products

If, during migration, you want to assign a reference product (such as follow-up product) to a newly migrated
product, you have to ensure that you migrate the reference product first. Otherwise, you will get a message to
say that the reference product does not exist and cannot be migrated. Please ensure you migrate these
products in the right sequence. Another possibility is to leave the reference products empty during migration
and assign these afterwards using the Manage Mass Maintenance – Products app.
Level Name
2 Additional EANs
2 Distribution Chains
2 Plant Data
3 Forecasting Data
3 Storage Locations
2 MRP Area
2 Valuation Data
3 Valuation Current Period
3 Valuation Future Price
Tasks

Explorer.

Post-Processing
You can use the Material - extend existing record with long text [page 227] migration object to migrate material
related long texts.
forecast values (only supported for on-premise solution).
You can use the Product classification - Commodity code [page 215] migration object to migrate product
classification with commodity code.
Display Material

Further Information
1.91 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
● Product [page 277] (with ERP data)

● Routing [page 309]

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
App: Manage Production Versions under Process Engineering for

Discrete Manufacturing
Business Role: Production Engineer – Process Manufacturing

(SAP_BR_PRODN_ENG_DISC)

1.92 Commercial project
 Note
This migration object was renamed from CPM project to Commercial project.
 Tip
Purpose
Business Object Component/Area Commercial Project Management (CPM)
Business Object Type Master data and transactional data (sales order)
In Scope
Migration of Commercial Projects in the following phases: In Planning, Contract Preparation, In Execution.
Out of Scope
Migration of Commercial Projects in phase: Completed or Closed. Project duration of more than 5 years is not
recommended. Projects with a longer duration decrease upload performance significantly.
The migration of customer projects (project type "C") and internal projects (project type "I") within a single
source file is not supported. Customer projects and internal projects must be migrated using separate source
files.

Supported Features
● Engagement Project
● Work Package
● Work Item
● Activity Planning
● Expense Planning
● Sales Order Header
● Sales Order Item
● Billing Plan Item
The Commercial project (the Engagement Project and Work Package parts) can be enhanced with the Custom
Fields and Logic app, adding custom fields in the application. If the Commercial project is enhanced in this way,
the custom fields will be reflected automatically in the XML template as well.
 Note
Any time you add, change or delete a custom field, the migration project must be updated and a new XML
application expert during migration testing, this must be communicated to and coordinated with data
migration.
Prerequisites

● Employee Master (via SAP SuccessFactors)
● Service Organization (must be manually created in the configuration)
Level Name
1 Engagement Project
(mandatory)
2 Work Package

Level Name
3 Work Item
3 Plan Data
2 Sales Order Header
3 Sales Order Item
4 Billing Plan Item
Tasks

Explorer.
Post-Processing

App: Create Customer Projects
Customer Projects
Business Role: Project Manager - Commercial Services

Further Information
● Professional Services – Customer Projects Migration blog series in the SAP S/4HANA Cloud Customer
Community

● Migration of Custom Fields for CPM Projects in SAP S/4HANA Cloud blog entry in the SAP Community
1.93 PSM - Fund
Purpose
Business Object Component/Area Public Sector Management (PSM)
Business Object Definition Public Sector Management (PSM) provides solution for
managing the budget of income and expenditure at public
institutions, records the execution of this budget and prevent
budget overruns.
In Scope
Supported Features
● PSM Fund header
Financial management area A000 is supported in SAP S/4HANA Cloud.
Level Name
1 PSM Fund data (mandatory)

Tasks

Explorer.
Post-Processing

App: Manage Funds under Budgetary Master Data
Business Role: Display: Budget Responsible- Funds management

(SAP_BR_BUDGET_RESPONSIBLE)
or
Create/modifiy: Budget Specialist- Funds management

(SAP_BR_BUDGET_SPECIALIST)
1.94 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, new purchasing info
record category or new plant. 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 294]
● If you want to extend an existing purchasing info record with a material group and vendor, you need the
purchasing info record number. If you want to create a new info record number for the same combination,
please use the Purchasing info record with conditions [page 294] object.
● If you use the identical Legacy Number of purchasing info record in the objects Purchasing info record with
conditions [page 294] and Purchasing info record- extend existing record in the same project, then the
mapping of records takes place automatically. After migration of the purchasing info record with the
Purchasing info record with conditions [page 294] object, the info record number is stored in the migration
mapping table. The Purchasing info record- extend existing record object then uses this mapping value.
● If you have provided a different Legacy Number of purchasing info record in the Purchasing info record-
extend existing record object, you have to select the correct info record number in the Convert Values step
in the Mapping of Purchasing info record numbers mapping rule.
● If you have provided the newly created info record number in the Legacy Number of purchasing info record
field, you can check and confirm the Mapping of Purchasing info record numbers mapping rule in the
Convert Values step.
Level Name
1 General Data (manda

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

Tasks

Explorer.
Post-Processing
App: Manage Purchasing Info Records
App: Mass Changes to Purchasing Info Records
Further Information
Find FAQs relating to this migration object in SAP Knowledge Base Article 2776897 .
1.95 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

Migration with identical combinations of material group and vendor leads to different purchasing info record
numbers. The combination of material number and vendor is always unique.
Level Name
1 General Data (manda

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

Explorer.

Post-Processing

App: Manage Purchasing Info Records
App: Mass Changes to Purchasing Info Records
Further Information
1.96 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 313]
● Purchase contract [page 65]
● WBS element
● G/L account (manually; expense account used in account assignment category)
● Purchasing info record with conditions [page 294] (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)
3 Item Address
3 Schedule Line
4 Components for Sub

contracting
3 Item Texts
Tasks

Explorer.

Post-Processing

App: Manage Purchase Orders
Display Purchasing Documents by Supplier
Display Purchasing Documents by Account Assignment
Display Subcontracting Stocks by Supplier
App: Mass Changes to Purchase Orders
1.97 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

App: Display Code Groups
1.98 QM - Quality info record
Purpose
Business Object Component/Area QM
Business Object Definition Quality Info Record
In Scope
1. Quality info record
Supported Features
● Quality info record

Prerequisites

Business objects that reference this object must be created within the validity period that fits this object.
Level Name
1 Quality info record (mandatory)
Tasks

Explorer.

Post-Processing

App: Display Quality Info Records
Manage Quality Info Records
Quality Engineer (SAP_BR_QUALITY_ENGINEER)
App: Manage Quality Info Records
1.99 Real estate contract
Purpose
Business Object Component/Area Real Estate Contract (RE-FX)
Business Object Definition An agreement between parties to sell (respectively pur

chase) or lease flexible contract items (such as real estate
objects). Furthermore, service related to those objects may
also be included.
Supported contract types:
● Lease-out
● Lease-in
● Service

In Scope
1. General Data
2. Partners
3. Term Without Renewal and Notice Rules
4. Objects
5. Conditions
6. Posting Terms
7. Frequency Terms
8. Organization Assignment Terms
Out of Scope
1. Valuation Parameters
2. Adjustment
3. Resubmit
4. Overviews
5. Renewal Rules
6. Notice Rules
7. Adjustment Terms
8. Multiple Posting Terms on one Condition
9. Multiple Frequency Terms on one Condition
10. Multiple Main Partner Assignments
Supported Features
● General Data
● Partners
● Term
● Objects
● Conditions
● Posting
● Frequency
● Organizational Assignment

Business Partner
If you want to assign a partner in a vendor or customer role, you must first create the corresponding partner
and capture the number in the partner assignment structure.
Main Contract Number
If you want to use main contracts, you must first migrate them. The main contract is then available in the
conversion value and can be mapped to a second file, including any contracts referring to these main contracts.
Tax Jurisdiction Code
As the jurisdiction-dependent tax is activated for a US company, the following structure and fields become
mandatory.
● Posting terms will need to be maintained.

● Tax jurisdiction codes will need to be maintained for each posting term.
● In each contract, Tax jurisdiction codes must always be maintained for default posting terms which include
term number.
Level Name
2 Partners
2 Term (mandatory)
2 Objects
2 Conditions
2 Posting
2 Frequency
2 Organizational Assignment
Tasks

Explorer.

Post-Processing
Data which is not migrated, such as renewal and notice rules or organizational information, must be added
during post-processing.
The valuation process must also be part of post-processing, but handled separately, using another role
template (SAP_BR_RECM_VALSPECIALIST).

App: Manage Contract
Business Role: Contract Specialist - Leasing (SAP_BR_RECM_SPECIALIST)
1.100 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 180] migration object.
● For task list of type A (General Maintenance task list), use the PM - General maintenance task list [page
167] migration object.
● For task list of type E (Equipment Task List), use the PM - Equipment task list [page 112] migration
object.
● For task list of type T (Task List for Functional Location), use the PM - Functional location task list [page
161] migration object.
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.

App: Display Routing

Business Role: Production Engineer - Discrete Manufacturing
(SAP_BR_PRODN_ENG_DISC)
Further Information
1.101 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 Item (mandatory)
3 Item Conditions (optional)

Level Name
3 Item Texts (optional)
2 Partner (mandatory)
2 Schedule Line Data (manda

tory)
Tasks

Explorer.
Post-Processing

App: List Sales Orders
Business Role: Sales Manager - Sales Document Lists

(SAP_BR_SALES_MANAGER)
Internal Sales Representative

Internal Sales Representative - Professional Services

(SAP_BR_INTERNAL_SALES_REP_PRSVR)
1.102 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
App: Manage Scheduling Agreements
Change Scheduling Agreements
1.103 Condition record for pricing in sales (restricted)

 Restriction
This migration object only supports the condition types and key combinations mentioned in the Supported
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 (including scales, if applicable):
1. Prices
2. Discounts
3. Surcharges
Out of Scope
1. Purchasing conditions (see migration object Condition record for pricing in purchasing (restricted) [page
248])

Supported Features
● For other key combinations you must use the Condition record for pricing (general template) [page 54]
migration object.
Prerequisites

Level Name
1 Sales condition records (mandatory)
2 Scales
For more information on how to fill the condition types and key combinations refer to the Supported
Tasks

Explorer.

Post-Processing


Examples
1,000 EA 100,00000 EUR
100,000 EA 90,00000 EUR
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

Further Information
1.104 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 54]
Level Name
1 Header Data (mandatory)
2 Additional Header Partners
2 Item (mandatory)
3 Item Partners
Tasks

Explorer.

Post-Processing
App: Manage Sales Contracts

1.105 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
App: Display Selected Sets
1.106 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

App: Display Selected Sets

1.107 SEPA mandate
Purpose
Business Object Component/Area FI-AR, FI-CA
Business Object Definition SEPA Mandate
In conjunction with the Single Euro Payment Area (SEPA),

processing and managing SEPA direct debits and SEPA bank
transfers are supported.
There are two different types of SEPA direct debits:
● SEPA Core Direct Debit

● SEPA Business to Business Direct Debit
Both kinds of SEPA direct debits are supported.
For additional information about SEPA direct debits, visit the

European Payments Council site.
In Scope
Supported Features
● SEPA Mandate Data

Prerequisites
● Bank [page 20]

● FI-CA Contract partner [page 132]
○ Contract Partner Role (FI-CA)
○ Customer Role (FI-AR)
Level Name
1 SEPA Mandate (mandatory)
Template Structure
The template structure lists the minimum mandatory fields for creating a SEPA mandate in status 0 (entered).
For mandate status 1 (active), the following additional fields are mandatory:
● Location of Signature (SIGN_CITY)

● Date of Signature (SIGN_DATE)
● Creditor Identification Number (REC_CRDID)
● SEPA Mandate: Sender Type (SND_TYPE)
● SEPA Mandate: Sender ID (SND_ID)
● IBAN (International Bank Account Number) (SND_IBAN)
● SWIFT/BIC for International Payments (SND_BIC)
Please refer to the tooltips field of the template file for further information.
Tasks

Explorer.

Post-Processing

App: Create SEPA Mandates
Display SEPA Mandates
Change SEPA Mandates
Display SEPA Mandate Lists
Business Role: FI-AR: Accounts Receivable Accountant

(SAP_BR_AR_ACCOUNTANT)
or
FI-CA: Accounts Payable and Receivable Accountant

Further Information
1.108 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 65]
○ Purchase scheduling agreement [page 315]
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
Tile: Manage Source Lists
Business Role: Purchaser (SAP_BR_PURCHASER))
1.109 Service contract

Purpose
Business Object Component/Area Service Contract Management (CRM-S4-SRV-CTR)
Business Object Definition Service contracts are outline agreements with business
partners and define the services offered for a particular pe
riod.
Service contracts represent long-term service agreements

with customers. They define the content and scope of the
services guaranteed within specific tolerance limits for cer
tain parameters, for example, within a predefined time
frame.
In Scope
1. Service contract header

2. Service contract item
Out of Scope
Service contracts that are processed in external systems will not be migrated to SAP S/4HANA.
Supported Features
● Header text
● Item
● Item condition
● Pricing elements

Prerequisites

Level Name
1 Header Data
2 Header Notes
2 Header Item
3 Item notes
3 Item product list
3 Item object list
3 Item pricing condition
Tasks

Explorer.

Post-Processing

App: Manage Service Contracts
Business Role: Customer Service Manager

(SAP_BR_CUSTOMER_SRVC_MGR)
1.110 Service order (only open SRVO)
Purpose
Business Object Component/Area CRM-SRV-SVO
Business Object Definition A customer request to the company for delivery of goods or
services at a certain time. The request is received by a serv
ice area responsible for fulfilling the service order or service
contract.
In Scope
1. Service order header data

2. Service order item data
3. Service order partner data
4. Service order texts on header and item level
5. Service order conditions on item level

6. Service order reference objects on header and item level
Out of Scope
1. Service orders with configurable items

2. Credit card and payment method data
3. Return service orders
Supported Features
All structures and features are supported.
Prerequisites

● Service contract [page 331]
● Only one Employee Responsible can be maintained to the service order.

● Only open service orders that are Open or In Process can be migrated.
● During migration, you can choose between internal and external number assignment for the service
document number and item numbers.
Level Name
2 Item Mandatory

Level Name
3 Item Pricing Elements (op

tional)
3 Item Texts (optional)
3 Item Reference Objects (op

tional)
2 Header Reference Objects

(optional)
2 Person Responsible (relevant

for on-premise only)
Tasks

Explorer.
Post-Processing

App: Manage Service Orders
Business Role: Customer Service Manager

(SAP_BR_CUSTOMER_SRVC_MGR)
For SAP S/4HANA Cloud on-premise related migration, validation of data can be done using the following app:
App: CRM Web UI
Business Role: Service Professional (S4C_SRV_PRO)

1.111 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.

Post-Processing
App: Manage Substances Compliance
Business Role: Master Data Specialist - Product Compliance

1.112 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.113 TRM - Bank guarantee
Purpose
Business Object Component/Area Transaction Manager (FIN-FSCM-TRM-TM)
Business Object Definition Bank Guarantee
In Scope
1. Structure data
2. Condition
3. Single date
4. Collateral data
5. Administration data
6. Other flows data
7. Payment details data
Out of Scope
1. Cash flow
2. Memos
3. Analysis parameter
4. Partner assignment
5. Default risk limit
6. Status

Supported Features
● Structure
● Condition
● Single date
● Collateral
● Administration
● Other Flows
● Payment Details
Reference Date for Calculation

Rule for Date Update - Cal. Rule for Date Update – Due Date Reference Date for Due Date
0 - Regular 0 - Regular
0 - Regular 1 - Relative 1 - Calculation Date Before

Working Day Shift
0 - Regular 1 - Relative 0 - Calculation Date
1 - Relative 0 - Regular 1 - Due Date Before Working

Day Shift
1 - Relative 0 - Regular 0 - Due date
2 - SingleDate 2 - SingleDate
Level Name
1 Structure (mandatory)
2 Condition
3 Single date
2 Collateral
2 Administration(mandatory)
2 Other Flows
2 Payment Details
2 Underlying Sales Order or

Purchase Order
2 Long Text
Other Flows
1. There are two options when determining how to migrate other flows via the control parameter below. You
can control this during the run time.

2. Control Parameter: CTR_TR_OTHERF_C (Indicates whether entries in other flows are complete).
○ Not Complete (by default): means other flows are automatically created from standing instructions
(configuration level), but you can add additional other flows or change existing other flows.
 Note
In this case, if you leave the Other Flow sheet empty, then the system determines the other flow
from configuration level.
○ Complete: means migrate deals including all other flows.
 Note
In this case, the system only takes the other flows from the excel template into account; these are
not related to configuration level.
Payment Details
1. There are two options when determining how to migrate payment details via the control parameter below.
You can control this during the run time.
2. Control Parameter: CTR_TR_PAYDET_C (Indicates whether entries in payment details are complete).
○ Not Complete (by default): means payment details are automatically created from standing
instructions (configuration level), but you can add additional payment details or change existing
payment details.
 Note
In this case, if you leave the Payment Detail sheet empty, then the system determines the payment
detail from configuration level.
○ Complete: means migrate deals including all payment details.
 Note
In this case, the system only takes the payment details from the excel template into account; these
are not related to configuration level.
Tasks

Explorer.

Post-Processing
Follow-on Activities
The Treasury Specialist – Back Office will find the apps for legacy data transfer on the launchpad under Utilities:
● Enter Position Component Values

● Initial Load of Position Values
● Reverse Initial Load of Position Values
● Mark Flows as Posted
● Mark Flows as Reversed
After the import of your financial transactions, the valuation-area-independent information such as quantity
information (for example, units, nominal amounts), the purchase value and cost are transferred.
Depending on your scenario, you might have to post the transactions to the general ledger. Even if you do not
have to post the transactions into the general ledger, you still mark the flows of the financial transactions as
posted. Use the Mark Flows as Posted app to do this.
The flows are indicated as being posted but are not actually posted. A posting log is generated.
The Mark Flows as Reversed app is also available, if needed, to set the flows as reversed:
● Enter the position component values
The remaining valuation-area-dependent position component values are entered in the Legacy Data table using
the Enter Position Component Values app.
● Using the Execute Initial Load of Position Value app (OP: TPM63 Execute Data Transfer), enter the positions
component values in the Positions Management tables.
Should any errors occur, you can reverse the initial load using the Reverse Initial Load of Position Value app .
To check the values entered, you can display the positions component values with the Treasury Position
Reporting or Display Treasury Position Values apps or, available for the Treasury Accountant business role
(SAP_BR_TREASURY_ACCOUNTANT), with the Treasury Position Analysis app.

App: Process Trade Finance Transactions - Collective Processing
Business Role: Treasury Specialist - Front

(SAP_BR_TREASURY_SPECIALIST_FOE)

1.114 TRM - Commercial paper
Purpose
Business Object Definition Commercial Paper transactions are transactions on which

no interest payments are made during the term of the trans
action. Instead, two business partners agree on a repayment
amount to be repaid to the investor, by the borrower, at the
end of the life of the contract.
In Scope
1. Structure data
3. Data migration of contract activities
Out of Scope
1. Conditions are not supported

2. Other flows are not supported
3. Payment details are not supported
4. Cash flows are not supported
5. Data migration of order activities is not supported
Supported Features
● Structure Data
● Administration Data

If a successor object is created with a validity period starting before this object, it will normally cause an error
You must therefore check such time dependencies before you create or migrate your objects. This will avoid
Level Name
1 Structure Data (mandatory)
2 Administration Data (mandatory)
Tasks

Explorer.
Post-Processing

information (for example, units, nominal amounts) the purchase value and cost are transferred.

● Enter the position component values
the Enter Position Component Values app. Alternatively, use the SAP S/4HANA Migration Cockpit app to enter
the position values (see the TRM - Position value [page 370] migration object). If you do not know the financial
transaction number (because this number was generated during the migration of your financial transactions to
the SAP S/4HANA Cloud system), the migration cockpit can derive the financial transaction number if you can
fill one of the following fields or field combinations instead:
● Internal Reference
● Business Partner ID and External Reference
● Legal Basis (SAP S/4HANA Cloud preconfigured value 01) and External Trade ID
 Note
These fields are available in the financial transaction data and should have been filled during the migration
of the financial transaction.
The migration cockpit searches for the corresponding financial transactions and enters the identified financial
transaction number in the Legacy Data Transfer table for position component values.

App: Process MM Transactions


1.115 TRM - Deposit at notice
Purpose
Business Object Definition A deposit at notice is an investment or borrowing without

defined due dates. The deposit at notice, therefore, not only
includes the functions available in the fixedterm deposit
area, but also a function for giving notice; in other words, in
addition to entering the amounts and conditions, you enter
the notice period and the interest payment date and fre
quency.
In Scope
1. Structure data
3. The object only supports the creation of contract activity
Out of Scope
1. Additional conditions are not supported

3. Additional payment details are not supported
4. Additional cash flows are not supported
Supported Features
● Structure Data

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
Tasks

Explorer.
Post-Processing


● Enter position component values
The remaining valuation area-dependent position component values are entered in the Legacy Data table using
the position values (see the TRM - Position value [page 370] migration object ). If you do not know the financial
S/4HANA Cloud system), the migration cockpit can derive the financial transaction number if you can fill one
of the following fields or field combinations instead:
 Note
The fields are available in the financial transaction data and should have been filled during the migration of
the financial transaction.
transaction number in the legacy data transfer table for position component values.

App: Process MM Transactions


1.116 TRM - FX option
Purpose
Business Object Definition The FX option is an option on a spot exchange transaction

and is used as protection from currency fluctuations. The
purchaser of a standard FX option, also known as an OTC
(over the counter) option, has the right to buy a fixed
amount of currency on the exercise date at a previously
agreed rate.
The option purchaser pays a premium for this right. The

amount of the premium paid varies depending on supply and
demand in the foreign exchange market. FX options are
asymmetrical hedging instruments - this means that rights
and obligations are unevenly distributed between the buyers
and sellers.
Unlike listed instruments, these options are traded directly

between business partners with userdefined structure char
acteristics. The main difference with forward exchange
transactions is that the buyer of an option has the right, but
not the obligation, to buy or sell a certain currency amount.
In Scope
1. Structure data
3. Migration of contract activities
4. Only the creation of financial transactions is considered, data transfer for ongoing transactions is not
supported.

Out of Scope
1. External numbering for transaction number is not supported

2. Migration of order activities
Supported Features
● Structure Data
Level Name
1 Structure data (mandatory)
2 Administration data
Tasks

Explorer.
Post-Processing


information (for example, units, nominal amounts), the purchase value, and cost are transferred.
component values in the Position Management tables

App: Process FX Options - Collective Processing

1.117 TRM - Foreign exchange swap - contract

Purpose
Business Object Component/Area Transaction Manager(FIN-FSCM-TRM-TM)
Business Object Definition Foreign exchange swap contract
In Scope
1. Structure data
supported.
Out of Scope
1. Additional other flows

2. Additional payment details
3. Memos
4. Status
5. Analysis parameters
7. Migration of order/fixing activities
Supported Features
● Structure

Level Name
Tasks

Explorer.
Post-Processing

component values in the tables of the Position Management tables.

Reporting or Display Treasury Position Values apps or, available for the Treasury Accountant) business role
App: Process Spots/Forwards - Collective Processing

1.118 TRM - Foreign exchange collar - contract
Purpose
Business Object Definition Foreign exchange collar contract
In Scope
1. Structure data
supported.

Out of Scope
1. Additional other flows

2. Additional payment details
3. Memos
4. Status
Supported Features
● Structure
Prerequisites
The following data must already have been maintained or migrated:
● Business partner with the Counter-Party role
Level Name
Tasks

Explorer.

Post-Processing

After the import of your financial transactions, the valuation area-independent information such as quantity
component values in the Positions Management tables



1.119 TRM - Foreign exchange spot/forward transaction - contract
Purpose
Business Object Definition Foreign exchange spot/forward transaction - contract
In Scope
1. Structure data
3. Other flows data
4. Payment details data
6. Only the creation of financial transactions is considered
Out of Scope
1. Data transfer for ongoing transactions is not supported

2. Memos
3. Status
6. External numbering is not supported

Supported Features
● Structure
● Administration
● Other Flows
● Payment Details
Level Name
2 Administration (mandatory)
2 Other Flows
2 Payment Details
Other Flows
 Note
In this case, if you leave the Other Flow sheet empty, then the system determines the other flow
 Note
In this case, the system only takes the other flows from the excel template into account, these are
Payment Details
payment details.

 Note
detail from configuration level.
 Note
In this case, the system only takes the payment details from excel template into account, these are
Tasks

Explorer.
Post-Processing


the position values (see the TRM - Position value [page 370] migration object. If you do not know the financial
S/4HANA Cloud system), the migration cockpit can derive the financial transaction number if you can fill one
of the following fields or field combinations instead:
 Note
Should errors occur, you can reverse the initial load using the Reverse Initial Load of Position Value app.


1.120 TRM - Interest rate instrument

Purpose
Business Object Definition Interest rate instrument
In Scope
1. Structure data
3. Conditions
4. Main flows
5. Other flows
6. Payment details
supported.
Out of Scope
1. Interest rate adjustments

2. Memos
3. Status
6. External numbering is not supported
Supported Features
● Structure
● Administration
● Conditions
● Main Flows
● Other Flows
● Payment Details

Level Name
2 Administration
2 Conditions
2 Main Flows
2 Other Flows
2 Payment Details
Conditions
1. There are two options when determining how to migrate conditions via the control parameter below. You
2. Control Parameter: CTR_TR_COND_C (Indicates whether entries in conditions are complete).
○ Not Complete (by default): means conditions are automatically created from standing instructions
(configuration level), but you can add additional conditions or change existing conditions.
 Note
In this case, if you leave the Condition sheet empty, then the system determines the condition from
configuration level.
○ Complete: means migrate deals including all conditions.
 Note
In this case, the system only takes the conditions from the excel template into account, these are
Main Flows
1. There are two options when determining how to migrate main flows via the control parameter below.You
2. Control Parameter:CTR_TR_MAINF_C (Indicates whether entries in main flows are complete).
○ Not Complete (by default): means main flows are automatically created from standing instructions
(configuration level), but you can add additional main flows or change existing main flows.
 Note
In this case, if you leave the Main Flow sheet empty, then the system determines the main flow
○ Complete: means migrate deals including all main flows.
 Note
In this case, the system only takes the main flows from the excel template into account, these are

Other Flows
 Note
In this case, if you leave the Other Flow sheet empty, then the system determines the other flows
 Note
In this case, the system only takes the other flows from the excel template into account, these are
Payment Details
payment details.
 Note
details from configuration level.
 Note
In this case, the system only takes the payment details from the excel template into account, these
are not related to configuration level.
Tasks

Explorer.

Post-Processing

After the import of your financial transactions, the valuation area-independent information such as quantity
information (for example, units, nominal amounts,) the purchase value and cost is transferred.
The Mark Flows as Reversed app is also available, if needed, to set the flows as reversed
the Enter Position Component Values app:
Should errors occur, you can reverse the initial load using the Reverse Initial Load of Position Value app .

App: Process MM Transactions - Collective Processing


1.121 TRM - Interest rate swap
Purpose
Business Object Definition An exchange transaction with a term of more than one year,
based on different interest rates using the same currency.
In the SAP system, the exchange of fixed for variable interest

rates, or of variable interest rates for variable interest rates,
can be represented based on different interest rates.
An exchange transaction based on the interest rate/

currency.
There are three basic types of swap in SAP Treasury Man

agement:
1. Currency swap: A combination of a cash transaction

and an offsetting forward transaction
2. Interest rate swap: A swap transaction with a term of
more than twelve months, based on varying interest
rates in the same currency
3. Cross-currency interest rate swap: An exchange of pay
ment flows, comprising interest payments and capital
payments in different currencies
In Scope
1. Structure data
3. The object only supports the creation of a contract activity

Out of Scope
1. Additional conditions are not supported

3. Additional payment details are not supported
4. Additional cash flows are not supported
Supported Features
● Structure Data
If a successor object is created with a validity period starting before this object it will normally cause an error
You must therefore check such time dependencies before you create or migrate your objects. This will avoid
Level Name

● 1903011
Tasks

Explorer.
Post-Processing

The Mark Flows as Reversed app is also available, if needed, to set the flows as reversed
the Enter Position Component Values app. Alternatively, you can use the SAP S/4HANA Migration Cockpit app
to enter the position values (see the TRM - Position value [page 370] migration object). If you do not know the
financial transaction number (because this number was generated during the migration of your financial
transactions to S/4HANA Cloud system), the migration cockpit can derive the financial transaction number if
you can fill one of the following fields or field combinations instead:
 Note
The fields are available in the financial transaction data and should have been filled during the migration of
the financial transaction.

App: Process IR Derivatives

1.122 TRM - Position value
Purpose
Business Object Definition Valuation-area-dependent data for MM, FX, OTC transac
tions
In Scope

Supported Features
● Position Value
Prerequisites
To migrate the position value data, the financial transaction should exist in the system. This means that the
following objects should be migrated before the position object.
● TRM - Foreign exchange spot/forward transaction - contract [page 359]

TRM - Foreign exchange swap - contract [page 353]
TRM - Interest rate swap [page 367]
TRM - Deposit at notice [page 348]
TRM - Commercial paper [page 345]
TRM - Interest rate instrument [page 362]
TRM - FX option [page 351]
TRM - Bank guarantee [page 341]
Level Name
1 Position value data (mandatory)
Enter the financial transaction number to import the position value data. If the transaction number is not
available (because this number was generated during the migration of your financial transactions to the SAP
S/4HANA Cloud system), there are the following three fields or field combinations which you can fill instead, to
determine the transaction number.
● Internal Reference.
● Business Partner Number and External Reference.
● Legal Basis (SAP S/4HANA Cloud preconfigured value 01) and External Trade ID.
 Note

Tasks

Explorer.
Post-Processing

After the import of position value data, you can execute the initial load of position data.

App: Enter Position Component Values
Business Role: Treasury Specialist - Back Office

(SAP_BR_TREASURY_SPECIALIST_BOE)

1.123 VC - Assign global dependency to characteristic
Purpose
Business Object Component/Area LO-VC-DEP
Business Object Definition The object dependency is used to define dependencies be
tween different objects in a configuration.
By defining object dependencies, you can determine, for ex

ample:
● which combinations of characteristic values are allowed

in a configuration
● which characteristics are to appear in the configuration.
In Scope
1. Assign global dependency
Supported Features
● Header
Prerequisites


You can only create object dependencies assigned to one Engineering Change Number in one migration run.
Level Name
2 Global Dependencies (mandatory)
Tasks

Explorer.
Post-Processing


Further Information
1.124 VC - Assign global dependency to characteristic value
Purpose
Business Object Component/Area LO-VC-DEP
Business Object Definition The object dependency is used to define dependencies be
tween different objects in a configuration.
By defining object dependencies, you can determine, for ex

ample:
● which combinations of characteristic values are allowed

in a configuration
● which characteristics are to appear in the configuration
In Scope
1. Assign global dependency to characteristic value
Supported Features
● Header

Prerequisites

● The Characteristic [page 34] must be created in the same project using the SAP S/4HANA Migration
Cockpit; a manually-created version of the characteristic cannot be used in this object.
● Even if the Characteristic [page 34] object has been migrated in a previous release of SAP S/4HANA Cloud,
it still can't be used in this object, because the Characteristic [page 34] migration object was enhanced
with SAP S/4HANA Cloud 1911. You will get a warning message if you try to use a manually-created version.
● You can only create object dependencies assigned to one Engineering Change Number in one migration
run.
The characteristic name and item can be retrieved from the Characteristic [page 34] migration object.
Therefore, fill out the second sheet of the migration template, Character. value dependency. It's not necessary
to enter a value, but make sure you have entered the correct item number for the correct characteristic.
Level Name
2 Character. value dependency (manda

tory)
Tasks

Explorer.

Post-Processing

Further Information
1.125 VC - Variant table entry
Purpose
Business Object Definition A table used to store consistent combinations of values for
different characteristics in product modeling.
In Scope

Supported Features
● Variant table
● Contents of Variant Table
Prerequisites
Value Space for characteristics
1. You have defined not only the value Space but also a value description in the characteristic master.
2. The values for the table content are transferred to the VAR_TAB_ENTRIES table. If a characteristic uses the
value Space, you must specify the value description in the VTVALDESCR field.
Level Name
1 Variant Table (mandatory)
2 Contents of Variant Table

● 1840693
● 1963379
Tasks

Explorer.

Post-Processing
App: Table Maintenance

1.126 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)
4. Company data
5. Withholding tax data
6. Purchasing organization data
7. Purchasing partner functions
8. Bank data
9. Industries
10. Tax numbers
12. Contact persons, including address data with telephone, fax and email
Out of Scope
1. Updates of existing fields/records.

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.
Supported Features
● General Data
● Company Data
● Partner Functions
● Bank Details
● Industries
● Tax Numbers

● Contact Persons
Prerequisites

● If you want to extend already existing customers/contract partners as supplier with the same number:
○ Customer [page 79]
○ FI-CA Contract partner [page 132]
On the General Data sheet, we only offer fields which might become relevant when you extend already existing
customers/contract partners as supplier with the same number. If you want to extend an existing customer or
contract partner as supplier with the same number, you have to fill out either the customer number or contract
partner. It's not possible to provide both fields. If you want to extend an already existing supplier 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
supplier already exists.
If you want to use the Supplier ID for integration with external systems, you can activate it during migration. At
the same time, you must also maintain the Business System ID of your source system (to be used for
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.

If you have activated the Define Sensitive Fields for Dual Control (Vendors) option in the Configure Your Solution
app, you must confirm all related vendor changes in the Confirm Supplier List app. Migration of master data
records are then considered as changes, and you must confirm them later on. For this reason, you should
consider to deactivate this option before you start with the data migration, and activate it again afterwards.

For the supplier migration object, you can enter data into fields which could be cross-references to other
business partners, for example goods supplier or invoicing party.
created in advance.

If you use the partner function for the purchasing data, you might face the following situation.

 Example
You have three suppliers, A, B, and C. They have the following relation:
● A is goods supplier for B

● B is goods supplier for C
● C is goods supplier for A

Suppliers might have contact persons assigned who act in partner capacity. During migration, contact persons
are created as separate business partners using internal numbering. Since this new numbering is only created
during the migration process, you can't use the contact person number as contact ID for partner functions in
one single step.
To assign a contact person as partner, first create the supplier with the contact person, but without purchasing
data. Then, use the Supplier - extend existing record by new org levels migration object in a second step to
assign the purchasing data together with the contact person in partner capacity.
Contact Person ID
relationship.

Level Name
2 BP Roles
2 General Texts

Level Name
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
Tasks

Explorer.
Post-Processing

Mass change after an extend existing record by new org level migration can be done through:

App: Manage Mass Maintenance Business Partners
1.127 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 supplier, 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

Business Role: Master Data Specialist - Business Partner

1.128 Supplier
 Tip
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

3. Company data
4. Withholding tax data
5. Purchasing organization data
6. Purchasing partner functions
7. Bank data
8. Industries
9. Tax numbers
11. Contact persons, including address data with telephone, fax, email
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 379] 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.

Supported Features
● General Data
● Company Data
● Partner Functions
● Bank Details
● Industries
● Tax Numbers
● Contact Persons
 Note
Any time you add, change or delete a custom field, the migration project must be updated; a new XML
application expert during migration testing, this must be communicated to, and coordinated with, data
migration.
The Supplier (General Data, Company Data, and Purchasing Organization Data) can be enhanced with
the Custom Fields and Logic app, adding custom fields in the application. If the Supplier is enhanced in
this way, the custom fields will be reflected automatically in the XML template as well.
Prerequisites
● Bank [page 20]
The supplier will be created with the Supplier (FLVN01) role. The Supplier (Financial Accounting) (FLVN00) role
will be created if company data is provided in the template.
All mandatory partner functions will be created automatically with the same supplier number. If you provide the
partner function with a different supplier number on the Partner Functions sheet, this entry will be taken.
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 migration, you can choose between internal and external number assignment for new suppliers.
Assigned contact persons will always get an internal number for the new business partner.
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 379]
migration object.
If you want to use the Supplier ID for integration with external systems, you can activate it during migration. At
the same time, you must also maintain the Business System ID of your source system (to be used for
store of the SAP S/4HANA system.

If you have activated the Define Sensitive Fields for Dual Control (Vendors) option in the Configure Your Solution
app, you must confirm all related vendor changes in the Confirm Supplier List app. Migration of master data
records are then considered as changes, and you must confirm them later on. For this reason, you should
consider to deactivate this option before you start with the data migration, and activate it again afterwards.

For the supplier migration object, you can enter data into fields which could be cross-references to other
business partners, for example goods supplier or invoicing party.
created in advance.

If you use the partner function for the purchasing data, you might face the following situation.
 Example
You have three suppliers, A, B, and C. They have the following relation:
● A is goods supplier for B

● B is goods supplier for C
● C is goods supplier for A

Suppliers might have contact persons assigned who act in partner capacity. During migration, contact persons
are created as separate business partners using internal numbering. Since this new numbering is only created
during the migration process, you can't use the contact person number as contact ID for partner functions in
one single step.
To assign a contact person as partner, first create the supplier with the contact person, but without purchasing
data. Then, use the Supplier - extend existing record by new org levels [page 379] migration object in a second
step to assign the purchasing data together with the contact person in partner capacity.

Contact Person ID
relationship.

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

Tasks

Explorer.
Post-Processing



F2505)
Further Information
1.129 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
Production Planning for Process Industries (PP-PI)
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 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

Tile: Display Work Center
Business Role: - Production Engineer - Discrete Manufacturing
SAP_BR_PRODN_ENG_DISC)

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.

Important Disclaimers and Legal Information PUBLIC 395
www.sap.com/contactsap
© 2019 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 S4HANA Cloud

Uploaded by

Document Informationclick to expand document information

Document Informationclick to expand document information

Copyright:

Available Formats

Migration Objects For SAP S4HANA Cloud

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 S4HANA Cloud

Uploaded by

Copyright:

Available Formats

IMPLEMENTATION GUIDE | PUBLIC

Migration Objects for SAP S/4HANA Cloud

THE BEST RUN

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

Migration Objects for SAP S/4HANA Cloud

Migration Object Business Object Business Object Migration Ap­

FI - Accounts pay­ Accounting Docu­ Transactional data SAP_BR_AP_ACCO File FI-AP

FI - Accounts re­ Accounting Docu­ Transactional data SAP_BR_AR_ACCO File FI-AR

FI - G/L account Accounting Docu­ Transactional data SAP_BR_GL_ACCO File FI

Activity type [page Activity Type Master data SAP_BR_OVERHEA File CO

Bank [page 20] Bank Master data SAP_BR_CASH_MA File FI

NAGER Staging Table

Bank account bal­ Bank Account Transactional data SAP_BR_CASH_MA File FI

Migration Objects for SAP S/4HANA Cloud

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

Material BOM Bill of Material Master data SAP_BR_PRODN_E File PP-BD

PM - Equipment Bill Of Material Master data SAP_BR_MAINTEN File PM

PM - Functional lo­ Bill Of Material Master data SAP_BR_MAINTEN File PM

QM - Certificate Certificate Profile Master data SAP_BR_QUALITY File QM

PSS - Product Chemical Compli­ Master data SAP_BR_PROD File EHS-SUS

Class hierarchy Class Master data SAP_BR_BOM_ENG File CA-CL

Characteristic Classification Master data SAP_BR_PRODUCT File CA-CL

Class [page 37] Classification Master data SAP_BR_PRODUCT File CA-CL

Migration Objects for SAP S/4HANA Cloud

Object classifica­ Classification Valu­ Master data SAP_BR_PROD File CA-CL

TRM - Commercial Commercial Paper Transactional data SAP_BR_TREASUR File FIN-FSCM-TRM-

PSS - Substance Company Sub­ Master data SAP_BR_MD_SPEC File EHS-SUS

Condition contract Condition Con­ Master data SAP_BR_SALES_M File LO-AB

Consent [page Consent Transactional data SAP_BR_DATA_PR File CA-GTF-CON

Cost center [page Cost Center Master data SAP_BR_OVERHEA File CO

Customer - extend Customer Master data SAP_BR_BUPA_MA File SD

Customer - extend Customer Master data SAP_BR_BUPA_MA File SD

Migration Objects for SAP S/4HANA Cloud

Customer - extend Customer Master data SAP_BR_BUPA_MA File SD

Customer [page Customer Master data SAP_BR_OVER File SD

Customer Material Customer Material Master data SAP_BR_INTERNA File SD

DG - Assessment Dangerous Goods Master data SAP_BR_DG_SPLS File EHS-SUS-DG

DG - Assessment Dangerous Goods Master data SAP_BR_DG_SPLS File EHS-SUS-DG

VC - Dependency Dependency Net Master data SAP_BR_PRODUCT File LO-VC

TRM - Deposit at Deposit At Notice Transactional data SAP_BR_TREASUR File FIN-FSCM-TRM-

ECM - Change Engineering Master data SAP_BR_PRODN_E File PLM-WUI-OBJ-

PM - Equipment Equipment Master data SAP_BR_MAINTEN File PM

Exchange rate Exchange Rate Master data SAP_BR_GL_ACCO File FI

FI-CA Contract FI-CA – Contract Master data SAP_BR_BUPA_MA File FI

Migration Objects for SAP S/4HANA Cloud

PM - Functional lo­ Functional Loca­ Master data SAP_BR_MAINTEN File PM

TRM - FX option FX Option Transactional data SAP_BR_TREASUR File FIN-FSCM-TRM-

EHS - Incident Incident Manage­ Transactional data SAP_BR_INDUSTR File EHS-SUS-IM

QM/PM - Catalog Inspection Code Master data SAP_BR_QUAL File QM

Migration Objects for SAP S/4HANA Cloud

QM - Inspection Inspection Method Master data SAP_BR_QUAL File QM

QM - Inspection Inspection Plan Master data SAP_BR_QUAL File QM

QM - Selected set Inspection Se­ Master data SAP_BR_QUAL File QM

QM - Selected set Inspection Se­ Master data SAP_BR_QUAL File QM

QM - Master in­ Inspection Specifi­ Master data SAP_BR_QUAL File QM

JIT - Customer JIT – Customer Master data SAP_BR_MD_SPEC File LE-JIT

Migration Objects for SAP S/4HANA Cloud

Migration Object Business Object Business Object Migration Ap

FI - Accounts pay Accounting Docu Transactional data SAP_BR_AP_ACCO File FI-AP

FI - Accounts re Accounting Docu Transactional data SAP_BR_AR_ACCO File FI-AR

FI - G/L account Accounting Docu Transactional data SAP_BR_GL_ACCO File FI

Bank account bal Bank Account Transactional data SAP_BR_CASH_MA File FI

PM - Functional lo Bill Of Material Master data SAP_BR_MAINTEN File PM

PSS - Product Chemical Compli Master data SAP_BR_PROD File EHS-SUS

Object classifica Classification Valu Master data SAP_BR_PROD File CA-CL

PSS - Substance Company Sub Master data SAP_BR_MD_SPEC File EHS-SUS

Condition contract Condition Con Master data SAP_BR_SALES_M File LO-AB

PM - Functional lo Functional Loca Master data SAP_BR_MAINTEN File PM

EHS - Incident Incident Manage Transactional data SAP_BR_INDUSTR File EHS-SUS-IM

QM - Selected set Inspection Se Master data SAP_BR_QUAL File QM

QM - Selected set Inspection Se Master data SAP_BR_QUAL File QM

QM - Master in Inspection Specifi Master data SAP_BR_QUAL File QM

PM - Maintenance Maintenance Noti Transactional data SAP_BR_MAINTEN File PM

PM - Functional lo Maintenance Task Master data SAP_BR_MAINTEN File PM

VC - Object de Object Dependen Master data SAP_BR_PRODUCT File LO-VC

Product classifica Product Master data SAP_BR_TRD_CLS File SLL

Material inspec Product Master data SAP_BR_PRODMAS File QM

Product classifica Product Master data SAP_BR_TRD_ File SLL

Product consump Product Transactional data SAP_BR_PRODMAS File MM

Warehouse prod Product Master data SAP_BR_WAREHOU File SCM-EWM

Purchase schedul Purchase Schedul Transactional data SAP_BR_PURCHAS File MM-PUR

Material determi Sales Material Master data SAP_BR_INTERNA File SD

Software/Hard Software Con Master data SAP_BR_SYSTEMS File PLM

JVA - Project sus Suspended Master data SAP_BR_JVA_ File CA-JVA

VC - Assign global Variant Character Master data SAP_BR_PRODUCT File LO-VC

VC - Assign global Variant Character Master data SAP_BR_PRODUCT File LO-VC

VC - Material var Variant Configura Master data SAP_BR_PROD File LO-VC

VC - Configuration Variant Configura Master data SAP_BR_PRODUCT File LO-VC

VC - Variant table Variant Configura Master data SAP_BR_PRODUCT File LO-VC

VC - Variant table Variant Configura Master data SAP_BR_PRODUCT File LO-VC

Warehouse fixed Warehouse Stor Master data SAP_BR_WAREHOU File SCM-EWM

Warehouse stor Warehouse Stor Master data SAP_BR_WAREHOU File SCM-EWM

Warehouse stor Warehouse Stor Master data SAP_BR_WAREHOU File SCM-EWM