MigrationObjects OP en

Implementation Guide | PUBLIC
Document Version: SAP S/4HANA 2020 FPS02 – 2021-08-19
Migration Objects for SAP S/4HANA

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

1 Available Migration Objects
You can use the following table to gain an overview of all migration objects available for SAP S/4HANA. It’s
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 Migration Object Name column to search for a specific migration object.
Choose Filter to apply further filters for Master data and/or Transactional data in the Business Object Type
column, and for the application component in the Component column to narrow down the results list. If you
want to see more or less information, choose Show/hide columns, and select the respective checkboxes for the
columns you would like to show or hide.
 Tip
Filter the Migration Approach column to only see migration objects relevant for you. Therefore, choose Filter
in the respective column, and select the required approach, Direct Transfer, File, or Staging Table.
You can export the below table in CSV format with the current column visibility and filters applied. Therefore,
choose the CSV button above the table.
Migration Object Name Business Object Type Migration Approach Component
FI - SEPA mandate [page Master data File/Staging Table FI

1066]
ECM - Change master [page Master data File/Staging Table PLM-WUI-OBJ-ECN

793]
PM - Measurement docu Master data File/Staging Table PM

ment [page 864]
QM - Inspection plan [page Master data File/Staging Table QM

922]
Service order (only open Transactional data File/Staging Table CRM-S4-SRV

SRVO) [page 1055]
JVA - Joint operating agree Master data File/Staging Table CA-JVA

ment [page 933]
JVA - Joint venture partner Master data File/Staging Table CA-JVA

[page 935]
JVA - Cost center suspense Master data File/Staging Table CA-JVA

[page 937]
JVA - Venture suspense Master data File/Staging Table CA-JVA

[page 940]
JVA - Project suspense [page Master data File/Staging Table CA-JVA

942]

2 PUBLIC Available Migration Objects
JVA - Joint venture master Master data File/Staging Table CA-JVA

data [page 944]
CO - Business process [page Master data File/Staging Table CO-OM-ABC

817]
FI - G/L account - extend ex Master data File/Staging Table FI

isting record by new org lev
els [page 905]
FI - G/L account [page 907] Master data File/Staging Table FI
Product - extend existing re Master data File/Staging Table LO

cord by new org levels [page
1015]
CO - Statistical key figure Master data File/Staging Table CO

[page 819]
Product [page 1021] Master data File/Staging Table LO
FI - Accounts payable open Transactional data File/Staging Table FI-AP

item (restricted) [page 1000]
Material listing and exclusion Master data File/Staging Table SD

[page 952]
DG - Assessment for unpack Master data File/Staging Table EHS-SUS-DG

aged product (content-
based) [page 854]
DG - Assessment for pack Master data File/Staging Table EHS-SUS-DG

aged product (text-based)
[page 856]
DG - Assessment for unpack Master data File/Staging Table EHS-SUS-DG

aged product (text-based)
[page 859]
FI - Accounts receivable open Transactional data File/Staging Table FI-AR

item (restricted) [page 1005]
FI - G/L account balance and Transactional data File/Staging Table FI
open/line item (restricted)

[page 909]
CO - Cost rate [page 777] Master data File/Staging Table CO
CO - Activity type [page 954] Master data File/Staging Table CO
FI - Bank account balance Transactional data File/Staging Table FI

[page 779]
FI - Cash memo record [page Transactional data File/Staging Table FIN-FSCM-CLM

987]

Available Migration Objects PUBLIC 3
Bank [page 781] Master data File/Staging Table FI
Batch unique at material and Master data File/Staging Table LO-BM

client level [page 783]
Batch unique at plant level Master data File/Staging Table LO-BM

[page 786]
Material BOM [page 790] Master data File/Staging Table PP-BD
PM - Equipment BOM [page Master data File/Staging Table PM

881]
PM - Functional location Master data File/Staging Table PM

BOM [page 897]
PSS - Product compliance Master data File/Staging Table EHS-SUS

info [page 879]
VC - Material variant [page Master data File/Staging Table LO-VC

974]
QM - Inspection plan (depre Master data File/Staging Table QM

cated) [page 920]
PSS - Raw material compli Master data File/Staging Table EHS-SUS

ance info [page 876]
Class hierarchy [page 804] Master data File/Staging Table CA-CL
Characteristic [page 796] Master data File/Staging Table CA-CL
Class [page 801] Master data File/Staging Table CA-CL
Object classification - Gen Master data File/Staging Table CA-CL

eral template [page 807]
PSS - Substance [page 1070] Master data File/Staging Table EHS-SUS
Condition contract [page Master data File/Staging Table LO-AB

821]
Consent [page 829] Transactional data File/Staging Table CA-GTF-CON
CO - Cost center [page 947] Master data File/Staging Table CO
Customer - extend existing Master data File/Staging Table SD

record by Credit Manage
ment data [page 842]


record by Thailand branch
code [page 840]
Customer [page 846] Master data File/Staging Table SD

record by new org levels
[page 833]
SD - Customer Material Master data File/Staging Table SD

[page 844]
Document info record [page Master data File/Staging Table CA-DMS

861]
PM - Equipment [page 885] Master data File/Staging Table PM
Exchange rate [page 888] Master data File/Staging Table FI
FI - Historical balance (re Transactional data File/Staging Table FI
stricted) [page 914]
Fixed asset (incl. balances Master data File/Staging Table FI-AA

and transactions) [page 889] Transactional data
PM - Functional location Master data File/Staging Table PM

[page 899]
QM/PM - Catalog code Master data File/Staging Table QM

group/code [page 1044]
QM - Inspection method Master data File/Staging Table QM

[page 918]
EFD - Reinf report [page 871] Transactional data File/Staging Table FI-LOC-FI-BR
QM - Selected set [page 1062] Master data File/Staging Table QM
EHS - Location hierarchy Master data File/Staging Table EHS-SUS-FND

[page 873]
JIT - Package group [page Master data File/Staging Table LE-JIT

996]
JIT - Supply control [page Master data File/Staging Table LE-JIT

998]
EHS - Location [page 874] Master data File/Staging Table EHS-SUS-FND
QM - Selected set code [page Master data File/Staging Table QM

1064]

QM - Master inspection char Master data File/Staging Table QM

acteristic [page 992]
CO - Internal order [page Transactional data File/Staging Table CO

926]
Legal transaction [page 949] Transactional data File/Staging Table LCM-GF
PM - Maintenance item [page Master data File/Staging Table PM

955]
PM - Maintenance notifica Transactional data File/Staging Table PM
tion [page 868]
PM - Maintenance plan [page Master data File/Staging Table PM

957]
PM - Equipment task list Master data File/Staging Table PM

[page 883]
PM - Functional location task Master data File/Staging Table PM

list [page 895]
PM - General maintenance Master data File/Staging Table PM

task list [page 902]
JIT - Customer [page 994] Master data File/Staging Table LE-JIT
Material (deprecated) [page Master data File/Staging Table LO

977]
Material inventory balance Transactional data File/Staging Table MM-IM

[page 928]
PM - Measuring point [page Master data File/Staging Table PM

866]
Condition record for pricing Master data File/Staging Table SD

(general template) [page
824]
Condition record for pricing Master data File/Staging Table MM-PUR

in purchasing (restricted)
[page 989]
Condition record for pricing Master data File/Staging Table SD

in sales (restricted) [page
1057]

Material - Forecast planning Master data File/Staging Table MM

[page 961]
Material- extend exist record Master data File/Staging Table LO

by new org levels (depre
cated) [page 963]
Material inspection setup Master data File/Staging Table QM

[page 925]
Material - extend existing re Master data File/Staging Table MM

cord with long text [page
971]
Product classification - Com Master data File/Staging Table SLL-ITR-CLS

modity code [page 960]
Xceptional case -Mat price Master data File/Staging Table CO-PC-ACT

chng for global curr (depre
cated) [page 985]
Product classification - Legal Master data File/Staging Table SLL-ITR-CLS
control [page 969]
Product consumption [page Transactional data File/Staging Table MM
1013]
Production version [page Master data File/Staging Table PP

1029]
CO - Profit center [page 1011] Master data File/Staging Table CO
PS - Network [page 1031] Transactional data File/Staging Table PS
PS - Project [page 1033] Transactional data File/Staging Table PS
PS - WBS element [page Transactional data File/Staging Table PS

1116]
MM - Purchase contract Transactional data File/Staging Table MM-PUR

[page 830]
MM - Purchase order (only Transactional data File/Staging Table MM-PUR

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

agreement [page 1053]

MM - Purchasing info record- Master data File/Staging Table MM-PUR

extend existing record [page
1034]
MM - Purchasing info record Master data File/Staging Table MM-PUR

with conditions [page 1038]
Routing [page 1047] Master data File/Staging Table PP
SD - Sales contract [page Transactional data File/Staging Table SD

1060]
SD - Material determination Master data File/Staging Table SD

[page 975]
SD - Sales order (only open Transactional data File/Staging Table SD

SO) [page 1050]
Software/Hardware con Master data File/Staging Table PLM-ESD-ESC

straint [page 1072]
MM - Source list [page 1068] Master data File/Staging Table MM-PUR
Supplier - extend existing re Master data File/Staging Table MM

cord by Thailand branch
code [page 1105]
Supplier [page 1107] Master data File/Staging Table MM
Supplier - extend existing re Master data File/Staging Table MM

cord by new org levels [page
1098]
VC - Configuration profile Master data File/Staging Table LO-VC
[page 826]
Work center/Resource [page Master data File/Staging Table PP

1117]
TRM - Commercial paper Transactional data File/Staging Table FIN-FSCM-TRM-TM

[page 1074]
TRM - Deposit at notice Transactional data File/Staging Table FIN-FSCM-TRM-TM

[page 1076]
TRM - FX option [page 1079] Transactional data File/Staging Table FIN-FSCM-TRM-TM
TRM - Foreign exchange Transactional data File/Staging Table FIN-FSCM-TRM-TM

swap - contract [page 1082]
TRM - Foreign exchange col Transactional data File/Staging Table FIN-FSCM-TRM

lar - contract [page 1085]

TRM - Foreign exchange Transactional data File/Staging Table FIN-FSCM-TRM-TM

spot/forward transaction -
contract [page 1087]
TRM - Interest rate instru Transactional data File/Staging Table FIN-FSCM-TRM

ment [page 1091]
TRM - Position value [page Transactional data File/Staging Table FIN-FSCM-TRM-TM

1095]
VC - Characteristics group Master data File/Staging Table LO-VC

[page 799]
FI - SEPA Mandate [page Master data Direct Transfer - ERP FI-AR

177]
RE-FX - Architectural object Master data Direct Transfer - ERP RE-FX-BD

[page 385]
Batch unique at material and Master data Direct Transfer - ERP LO-BM
client level [page 79]
Batch unique at plant level Master data Direct Transfer - ERP LO-BM
[page 76]
FI - Accounts payable open Transactional data Direct Transfer - ERP FI

item (classic G/L) [page
157]
FI - Accounts payable open Transactional data Direct Transfer - ERP FI

item (new G/L) [page 160]
RE-FX - Building [page 388] Master data Direct Transfer - ERP RE-FX-BD
RE-FX - Business entity [page Master data Direct Transfer - ERP RE-FX
391]
Business partner [page 83] Master data Direct Transfer - ERP AP-MD-BP
Catalog code group and code Master data Direct Transfer - ERP QM
[page 86]
Characteristic [page 89] Master data Direct Transfer - ERP CA-CL
Class [page 92] Master data Direct Transfer - ERP CA-CL
Condition contract [page Master data Direct Transfer - ERP LO-AB

95]
Customer [page 98] Master data Direct Transfer - ERP SD
SD - Customer material Master data Direct Transfer - ERP SD

[page 406]
SD - Customer quotation Transactional data Direct Transfer - ERP SD

[page 403]
ECM - Change master [page Master data Direct Transfer - ERP PLM-PLC
137]

PM - Equipment [page 281] Master data Direct Transfer - ERP PM
PM - Equipment BOM [page Master data Direct Transfer - ERP PM

297]
PM - Equipment task list Master data Direct Transfer - ERP PM

[page 284]
Fixed asset (including bal Transactional data Direct Transfer - ERP FI-AA
ance) [page 180]
CO - Activity type group Master data Direct Transfer - ERP CO

[page 106]
CO - Activity type [page 104] Master data Direct Transfer - ERP CO
CO - Cost rate [page 121] Master data Direct Transfer - ERP CO-OM
CO - Business process [page Master data Direct Transfer - ERP CO-OM-ABC

109]
CO - Business process group Master data Direct Transfer - ERP CO-OM-ABC

[page 111]
CO - Cost center [page 114] Master data Direct Transfer - ERP CO
CO - Cost center group [page Master data Direct Transfer - ERP CO

116]
CO - Cost element group Master data Direct Transfer - ERP CO

[page 119]
CO - Internal order [page Transactional data Direct Transfer - ERP CO

124]
CO - Profit center [page 127] Master data Direct Transfer - ERP CO
CO - Profit center group Master data Direct Transfer - ERP CO

[page 129]
CO - Secondary cost element Master data Direct Transfer - ERP CO

[page 132]
CO - Statistical key figure Master data Direct Transfer - ERP CO

(ERP) [page 135]
FI - G/L account balance Transactional data Direct Transfer - ERP FI

(classic G/L) [page 145]
FI - G/L account balance Transactional data Direct Transfer - ERP FI

(new G/L) [page 148]
FI - Bank account [page 169] Master data Direct Transfer - ERP FI
Bank [page 81] Master data Direct Transfer - ERP FI
FI - Accounts receivable open Transactional data Direct Transfer - ERP FI

item (classic GL) [page 163]

FI - Accounts receivable open Transactional data Direct Transfer - ERP FI

Exchange rate [page 140] Master data Direct Transfer - ERP FI
FI - G/L account [page 142] Master data Direct Transfer - ERP FI
FI - House bank [page 171] Master data Direct Transfer - ERP FI
FI - G/L open item (classic Transactional data Direct Transfer - ERP FI

G/L) [page 151]
FI - Ledger groupspecific Transactional data Direct Transfer - ERP FI

open item [page 174]
FI - G/L open item (new G/L) Transactional data Direct Transfer - ERP FI
[page 154]
TRM - Additional flow [page Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
415]
TRM - Bank guarantee [page Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
418]
TRM - Business partner role Master data Direct Transfer - ERP FIN-FSCM-TRM-TM
[page 422]
TRM - Commercial paper Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM

[page 425]
TRM - Condition detail [page Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
185]
TRM - Facility [page 187] Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
TRM - Fixed term deposit Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
[page 191]
TRM - Foreign exchange col Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
lar contract [page 198]
TRM - FX option [page 195] Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
TRM - Foreign exchange Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM

spot/forward contract [page
428]
TRM - Foreign exchange Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM

swap contract [page 202]
TRM - Interest rate instru Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
ment [page 432]
TRM - Investment certificate Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM

[page 206]
TRM - Letter of credit [page Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
209]

TRM - Main flow detail [page Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
213]
TRM - Interest rate swap Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
[page 215]
TRM - Payment detail [page Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
219]
TRM - Security bond [page Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
435]
TRM - Security class [page Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
439]
TRM - Stock [page 442] Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
PM - Functional location Master data Direct Transfer - ERP PM

[page 288]
PM - Functional location Master data Direct Transfer - ERP PM

BOM [page 291]
PM - Functional location task Master data Direct Transfer - ERP PM

list [page 294]
Object classification (general Master data Direct Transfer - ERP CA

template) [page 278]
PM - General maintenance Master data Direct Transfer - ERP PM

task list [page 300]
QM - Selected set code [page Master data Direct Transfer - ERP QM

380]
QM - Selected set [page 377] Master data Direct Transfer - ERP QM
QM - Inspection method Master data Direct Transfer - ERP QM

[page 364]
QM - Inspection plan [page Master data Direct Transfer - ERP QM

367]
QM - Material inspection Master data Direct Transfer - ERP QM

setup [page 372]
JVA - Joint venture master Master data Direct Transfer - ERP CA-JVA
(step 1) [page 46]
JVA - Cost center suspense Master data Direct Transfer - ERP CA-JVA
[page 222]
JVA - Joint operating agree Master data Direct Transfer - ERP CA-JVA
ment (step 1) [page 228]
JVA - Joint venture partner Master data Direct Transfer - ERP CA-JVA
[page 230]
JVA - Order suspense [page Master data Direct Transfer - ERP CA-JVA
225]

JVA - Project suspense [page Master data Direct Transfer - ERP CA-JVA
233]
JVA - Venture suspense Master data Direct Transfer - ERP CA-JVA

[page 235]
RE-FX - Land [page 394] Master data Direct Transfer - ERP RE-FX-BD
PM - Maintenance item [page Master data Direct Transfer - ERP PM

320]
PM - Maintenance notifica Transactional data Direct Transfer - ERP PM

tion [page 314]
PM - Maintenance order Transactional data Direct Transfer - ERP PM

[page 310]
PM - Maintenance plan [page Master data Direct Transfer - ERP PM

317]
QM - Master inspection char Master data Direct Transfer - ERP QM

Product [page 354] Master data Direct Transfer - ERP LO
PP - Material BOM [page 337] Master data Direct Transfer - ERP PP-BD
MM - Material commodity Master data Direct Transfer - ERP LO-MD-MM

[page 244]
MM - Material consumption Master data Direct Transfer - ERP MM

[page 247]
MM - Material inventory bal Transactional data Direct Transfer - ERP MM-IM

ance [page 238]
PP - Material MRP assign Master data Direct Transfer - ERP PP-MRP

ment [page 323]
PM - Measurement docu Master data Direct Transfer - ERP PM-EQM-SF-MPC

ment [page 307]
PM - Measuring point [page Master data Direct Transfer - ERP PM

304]
PP - Production resource/ Master data Direct Transfer - ERP PP

tool [page 331]
PP - Planned independent re Transactional data Direct Transfer - ERP PP-MRP

quirement [page 340]
Pricing condition (purchasing Master data Direct Transfer - ERP SD

and sales) [page 351] MM-PUR
PP - Production order [page Transactional data Direct Transfer - ERP PP

328]
PP - Production version Master data Direct Transfer - ERP PP

[page 343]

PS - Project [page 360] Transactional data Direct Transfer - ERP PS
PS - Network [page 358] Transactional data Direct Transfer - ERP PS
MM - Purchase order [page Transactional data Direct Transfer - ERP MM-PUR

268]
MM - Purchase requisition Transactional data Direct Transfer - ERP MM-PUR

(only open PR) [page 272]
MM - Purchase contract Transactional data Direct Transfer - ERP MM-PUR

[page 250]
MM - Purchasing info record Master data Direct Transfer - ERP MM-PUR

[page 253]
QM - Quality info record Master data Direct Transfer - ERP QM

[page 375]
MM - Quota arrangement Transactional data Direct Transfer - ERP MM-PUR

[page 275]
RE-FX - Real estate contract Transactional data Direct Transfer - ERP RE-FX
[page 382]
RE-FX - Rental object [page Master data Direct Transfer - ERP RE-FX
397]
PP - Routing [page 333] Master data Direct Transfer - ERP PP
SD - Sales contract [page Transactional data Direct Transfer - ERP SD

408]
SD - Sales inquiry [page 400] Transactional data Direct Transfer - ERP SD
SD - Sales order (only open Transactional data Direct Transfer - ERP SD

SO) [page 412]
PP - Sales order BOM [page Master data Direct Transfer - ERP PP-BD
345]
MM - Purchase scheduling Transactional data Direct Transfer - ERP MM-PUR

MM - Service entry sheet Transactional data Direct Transfer - ERP MM

[page 260]
MM - Service master [page Master data Direct Transfer - ERP MM-SRV

263]
MM - Source list [page 265] Master data Direct Transfer - ERP MM-PUR
VC - Configuration profile Master data Direct Transfer - ERP LO-VC

[page 445]
MM - Material variant [page Master data Direct Transfer - ERP LO-VC

242]
VC - Object dependency and Master data Direct Transfer - ERP LO-VC

dependency net [page 448]

Supplier [page 451] Master data Direct Transfer - ERP MM
PP - Work breakdown struc Master data Direct Transfer - ERP PP

ture BOM [page 348]
PP - Work center [page 325] Master data Direct Transfer - ERP PM
JVA - Joint operating agree Master data Direct Transfer - ERP CA-JVA
ment (step 2) [page 44]
JVA - Joint venture master Master data Direct Transfer - ERP CA-JVA
(step 2) [page 50]
TRM - Cap/Floor [page 58] Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM
TRM - Deposit at notice Transactional data Direct Transfer - ERP FIN-FSCM-TRM-TM

[page 62]
Document info record (DMS) Master data Direct Transfer - ERP CA-DMS
[page 29]
VC - Variant table structure Master data Direct Transfer - ERP LO-VC

[page 74]
VC - Variant table entry [page Transactional data Direct Transfer - ERP LO-VC
71]
JIT - Customer [page 41] Master data Direct Transfer - ERP LE-JIT
EHS - Location [page 34] Master data Direct Transfer - ERP EHS-SUS-FND
EHS - Location hierarchy Master data Direct Transfer - ERP EHS-SUS-FND

[page 36]
VC - Assign global depend Master data Direct Transfer - ERP CA-CL

ency to characteristic [page
67]
Product classification (legal Master data Direct Transfer - ERP SLL-ITR-CLS

control) [page 53]
RE-FX - Business partner role Master data Direct Transfer - ERP AP-MD-BP
[page 55]
VC - Interface design (char Master data Direct Transfer - ERP LO-VC

acteristic group) [page 69]
VC - Assign global depend Master data Direct Transfer - ERP CA-CL

ency to class [page 39]
Recipe [page 21] Master data Direct Transfer - ERP PP-PI-MD-MRC
FSCM - Credit management Master data Direct Transfer - ERP FIN-FSCM-C

role [page 26]
PP - Work center hierarchy Master data Direct Transfer - ERP PP-BD-WKC

[page 24]

AFS - Article [page 483] Master data Direct Transfer - AFS IS-AFS-MM
LO-FSH
Batch unique at plant level Master data Direct Transfer - AFS LO-BM
[page 523]
AFS - Dimensional character Master data Direct Transfer - AFS CA-CL

istic [page 496]
AFS - Non-dimensional char Master data Direct Transfer - AFS CA-CL

AFS - Configuration class for Master data Direct Transfer - AFS IS-AFS-BD
material grid [page 490]
Customer [page 559] Master data Direct Transfer - AFS SD
AFS - Distribution curve Master data Direct Transfer - AFS IS-AFS-BD

[page 487]
AFS - Distribution curve con Master data Direct Transfer - AFS IS-AFS-BD
dition [page 492]
ECM - Change master [page Master data Direct Transfer - AFS PLM-PLC
565]
PM - Equipment [page 632] Master data Direct Transfer - AFS PM
Fixed asset (including bal Transactional data Direct Transfer - AFS FI-AA
ance) [page 570]
CO - Activity type group Master data Direct Transfer - AFS CO

[page 528]
CO - Activity type [page 525] Master data Direct Transfer - AFS CO
CO - Cost rate [page 530] Master data Direct Transfer - AFS CO-OM
CO - Business process [page Master data Direct Transfer - AFS CO-OM-ABC

533]
CO - Business process group Master data Direct Transfer - AFS CO-OM-ABC

[page 536]
CO - Cost center [page 538] Master data Direct Transfer - AFS CO
CO - Cost center group [page Master data Direct Transfer - AFS CO

541]
CO - Cost element group Master data Direct Transfer - AFS CO

[page 543]
CO - Internal order [page Transactional data Direct Transfer - AFS CO

546]
CO - Profit center [page 549] Master data Direct Transfer - AFS CO
CO - Profit center group Master data Direct Transfer - AFS CO

[page 551]

CO - Secondary cost element Master data Direct Transfer - AFS CO

[page 554]
CO - Statistical key figure Master data Direct Transfer - AFS CO

[page 557]
FI - G/L account balance Transactional data Direct Transfer - AFS FI

(classic G/L) [page 591]
FI - G/L account balance Transactional data Direct Transfer - AFS FI

(new G/L) [page 594]
FI - Bank account [page 586] Master data Direct Transfer - AFS FI
Bank [page 521] Master data Direct Transfer - AFS FI
FI - Accounts receivable open Transactional data Direct Transfer - AFS FI

item (classic GL) [page 574]
FI - Accounts receivable open Transactional data Direct Transfer - AFS FI

Exchange rate [page 568] Master data Direct Transfer - AFS FI
FI - G/L account [page 588] Master data Direct Transfer - AFS FI
FI - House bank [page 602] Master data Direct Transfer - AFS FI
FI - G/L open item (classic Transactional data Direct Transfer - AFS FI

G/L) [page 597]
FI - Ledger group specific Transactional data Direct Transfer - AFS FI

open item [page 605]
FI - G/L open item (new G/L) Transactional data Direct Transfer - AFS FI
[page 600]
FI - Accounts payable open Transactional data Direct Transfer - AFS FI

item (classic G/L) [page 580]
FI - Accounts payable open Transactional data Direct Transfer - AFS FI

Object classification (general Master data Direct Transfer - AFS CA

template) [page 608]
PP - Material BOM [page 636] Master data Direct Transfer - AFS PP-BD
MM - Material inventory bal Transactional data Direct Transfer - AFS MM-IM

ance [page 611]
AFS - Planned independent Transactional data Direct Transfer - AFS PP-MRP

requirement at material level
[page 508]
AFS - Planned independent Transactional data Direct Transfer - AFS PP-MRP

requirement at SKU level
[page 499]

PP - Planned independent re Transactional data Direct Transfer - AFS PP-MRP

quirement [page 642]
Pricing condition (purchasing Master data Direct Transfer - AFS SD

and sales) [page 657] MM-PUR
PP - Production order [page Transactional data Direct Transfer - AFS PP

648]
PP - Production version Master data Direct Transfer - AFS PP

[page 645]
MM - Purchase order [page Transactional data Direct Transfer - AFS MM-PUR

618]
MM - Purchase contract Transactional data Direct Transfer - AFS MM-PUR

[page 614]
MM - Purchasing info record Master data Direct Transfer - AFS MM-PUR

[page 623]
AFS - Quantity distribution Master data Direct Transfer - AFS IS-AFS-PP-MAN

profile [page 505]
PP - Routing [page 639] Master data Direct Transfer - AFS PP
SD - Sales contract [page Transactional data Direct Transfer - AFS SD

660]
SD - Sales order [page 663] Transactional data Direct Transfer - AFS SD
PP - Sales order BOM [page Master data Direct Transfer - AFS PP-BD
651]
MM - Purchase scheduling Transactional data Direct Transfer - AFS MM-PUR

AFS - Season [page 510] Master data Direct Transfer - AFS IS-AFS-SD
AFS - Segmentation default Master data Direct Transfer - AFS IS-AFS-BD

value [page 513]
AFS - Segmentation strategy Master data Direct Transfer - AFS IS-AFS-BD

[page 516]
AFS - Segmentation struc Master data Direct Transfer - AFS IS-AFS-BD

ture [page 518]
MM - Source list [page 629] Master data Direct Transfer - AFS MM-PUR
Supplier [page 667] Master data Direct Transfer - AFS MM
PP - Work center [page 654] Master data Direct Transfer - AFS PM
Document info record (DMS) Master data Direct Transfer - AFS CA-DMS
[page 467]
Class [page 464] Master data Direct Transfer - AFS CA-CL

FI - SEPA Mandate [page Master data Direct Transfer - AFS FI-AR

472]
VC - Assign global depend Master data Direct Transfer - AFS CA-CL

ency to characteristic [page
477]
VC - Assign global depend Master data Direct Transfer - AFS CA-CL

ency to class [page 480]
VC - Object dependency and Master data Direct Transfer - AFS LO-VC

dependency net [page 475]
AFS - Purchase grid condi Master data Direct Transfer - AFS IS-AFS-BD
tion record [page 456]
AFS - Sales grid condition re Master data Direct Transfer - AFS IS-AFS-SD
cord [page 459]
AFS - Value-added service Master data Direct Transfer - AFS IS-AFS-SD

[page 461]
Warehouse fixed bin assign Master data Direct Transfer - EWM SCM-EWM
ments [page 675]
Warehouse storage bin [page Master data Direct Transfer - EWM SCM-EWM
678]
Warehouse storage bin sort Master data Direct Transfer - EWM SCM-EWM
ing [page 683]
Warehouse product [page Master data Direct Transfer - EWM SCM-EWM

680]
Warehouse stock [page 686] Master data Direct Transfer - EWM SCM-EWM
Warehouse application log Master data Direct Transfer - EWM SCM-EWM

settings [page 689]
Physical inventory settings Master data Direct Transfer - EWM SCM-EWM

[page 692]
Shipping and receiving set Master data Direct Transfer - EWM SCM-EWM
tings [page 694]
Production supply area [page Master data Direct Transfer - EWM SCM-EWM
697]
Resource and user mainte Master data Direct Transfer - EWM SCM-EWM
nance [page 699]
Resource group and queue Master data Direct Transfer - EWM SCM-EWM
settings [page 702]
Resource execution settings Master data Direct Transfer - EWM SCM-EWM

[page 705]
Work center determinations Master data Direct Transfer - EWM SCM-EWM

[page 707]
Work center dependent set Master data Direct Transfer - EWM SCM-EWM
tings [page 709]

Material flow system [page Master data Direct Transfer - EWM SCM-EWM
712]
Route [page 715] Master data Direct Transfer - EWM SCM-EWM
Carrier profile [page 718] Master data Direct Transfer - EWM SCM-EWM
Zone [page 720] Master data Direct Transfer - EWM SCM-EWM
Zones hierarchy [page 722] Master data Direct Transfer - EWM SCM-EWM
Condition records (ware Master data Direct Transfer - EWM SCM-EWM

house dependent) [page
728]
Condition records (ware Master data Direct Transfer - EWM SCM-EWM

house independent) [page
725]
CRM - Activities [page 672] Transactional data Direct Transfer - CRM CRM-BTX-ACT
eSPP - Location [page 762] Master data Direct Transfer - eSPP SCM-BAS-MD
eSPP - Product [page 765] Master Data Direct Transfer - eSPP SCM-BAS-MD
eSPP - MRP Area [page 767] Master Data Direct Transfer - eSPP SCM-BAS-MD
eSPP - Location Product Master Data Direct Transfer - eSPP SCM-BAS-MD

[page 769]
eSPP - Transportation Lane Master Data Direct Transfer - eSPP SCM-BAS-MD

[page 771]
eSPP - Bill of Distribution Master Data Direct Transfer - eSPP SCM-BAS-MD

(BoD) [page 773]
eSPP - Product BoD Assign Master Data Direct Transfer - eSPP SCM-BAS-MD
ment [page 775]
 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’s a newer version of this
migration object available. Deprecated objects will be deleted after a couple of releases. Make sure you
always read the migration object documentation for these objects carefully. Also see SAP Note 2698032
for more details on deprecated migration objects.

 Note
Migration objects are built for initial migration of your data to your SAP S/4HANA or SAP S/4HANA Cloud
system. This means that you can create data with a migration object, but you can't change or update
existing data with it.
 Note
The predelivered data migration objects are built for SAP S/4HANA Cloud and the respective SAP Best
Practices Content. You can use these objects also for SAP S/4HANA and the respective SAP Best Practices
Content. Using SAP S/4HANA, the delivered standard migration objects are templates that can be
enhanced according to your needs. The enhancement is only limited by the functionality of the tool and the
capabilities of the underlying API to load the data. Starting with SAP S/4HANA 1610 FPS2, you can enhance
customer projects based on these delivered standard migration objects or you can create your own objects
using the SAP S/4HANA migration object modeler (transaction LTMOM). For further information, please see
SAP Note 2481235 .
Further Information
● Use these SAP Help Portal aliases to access the following sections of our product assistance:
Type this in your browser... To jump to...
http://help.sap.com/S4_OP_MO this very topic: Available Migration Objects
http://help.sap.com/S4_OP_DM the landing page for data migration
● If you want to view information about the differences between the current release and the previous release,
see SAP S/4HANA – Release Comparison of Migration Object Templates (for the File/Staging Table
migration approach only, and for customers and partners only).
● If you’re using the Fixed asset (incl. balances and transactions) [page 889] migration object, we provide
background information on asset classes and available fields per asset class here (for customers and
partners only).
● For information regarding mapping of unit of measures, see SAP Knowledge Base Article 2907822 .
1.1 Recipe
Available Migration Objects [page 2] in SAP S/4HANA.

Purpose
This migration object enables you to migrate recipe data from the source ERP system to the target SAP S/
4HANA system based on the default selection criteria set for the migration object. This migration technique
transfers data to the target system using Business Application Programming Interfaces (BAPIs).
Related Business Object: Master Recipe
Business Object Component/Area User Menu Path: Logistics Production - Process
Master Data Master Recipes Recipe and Material List
Create
Component: PP-PI-MD-MRC
Business Object Type Master data
Business Object Definition A description of an enterprisespecific process in the proc

ess industry that does not relate to a specific order. The
master recipe is used for producing materials or supplying
services.
Available Scenarios
Migration to SAP S/4HANA
Selection Criteria
This object is not delimited by the company codes specified when defining the migration scope.
In Scope
The following data is set for migration to SAP S/4HANA:
● Recipe header data

● Task list types (PLKZ-PLNTY) with the value "2"
● Material assignments
● Operations
● Suboperations
● Secondary resources
● Relationships
● Change number data
 Note
Material Assignments, Operations, Phases, Secondary Resources, and Relationships that you set for
deletion with respect to change numbers are not supported.

Out of Scope
● Material components
● Object dependencies
● Header long texts
● Item long texts
● Classification
● Quality Management
● Process instructions
Note that the information given here is not exhaustive.
Prerequisites
For a consistent migration, you have ensured that all relevant Customizing for the migration object is available
in the target SAP S/4HANA system.
You have migrated or defined settings in the following migration objects:
● Product
● PP - Material BOM
● PP - Production version
● PP - Routing
● PP - Work center
Roles and Authorizations
Source System
Not relevant
Target System
To carry out the migration, assign the following authorization object or objects to the user:
C_ROUT (Authorizations for Routings)
Note that the information given here is not. exhaustive.
Technical Information
Name of this migration object: S4_PP_MASTER_RECIPE
Name of the BAPI or BAPIs used in this migration object:
CL_PPH_MASTER_RECIPE (Master Recipe API)

Virtual Tables
● AS_PLPO: To handle operations or activities of task lists
● AS_TEXT_HDR: To handle long texts
Note that virtual tables do not exist in the database.
Post-Processing
Follow-On Activities
Not relevant
With the transaction codes shown below, you can change the view and maintain the object. However, these
codes also have some builtin validation capabilities that you can use as checks.
Activity Transaction Code
Change C202
Display C203
1.2 PP - Work center hierarchy
Purpose
This migration object enables you to migrate work center hierarchy data from the source ERP system to the
target SAP S/4HANA system based on the default selection criteria set for the migration object. This migration
technique transfers data to the target system using Application Programming Interfaces (APIs).
Related Business Object: Work Center Hierarchy
Business Object Component/Area User Menu Path: Logistics Production Master Data
Work Centers Hierarchy
Component: PP-BD-WKC

Business Object Definition The representation of a structure in which work centers and
their relationships to each other are displayed in levels. Work
center hierarchies are used in capacity planning to cumulate
available capacities or capacity requirements. The hierarchy
can also be used to locate work centers.
Available Scenarios
Selection Criteria
This migration object derives plants from the company codes you specified when defining the migration scope.
This migration object automatically selects work center hierarchies from the CRHH table for the derived plants.
In Scope
● General data
● Work center assignments
● Hierarchy data
Out of Scope
Not relevant
Prerequisites
● CO - Business process
● CO - Cost center
● CO - Internal order
Source System

Not relevant
Target System
Not relevant
Name of this migration object: S4_PM_WORK_CENTER_HIERARCHY
Name of the API or APIs used in this migration object:
CRAP_HIERARCHY_CREATE (API Hierarchy: Check Hierarchy)
Virtual Tables
AS_CRHS: To store the hierarchy structure
Post-Processing
Not relevant
How to Validate your Data in the System

codes also have some built-in validation capabilities that you can use for checks.
Display CR23
Further Information
1.3 FSCM - Credit management role

Purpose
This migration object enables you to migrate FSCM credit management role data for a business partner from
the source ERP system to the target SAP S/4HANA system. The migration is based on the default selection
criteria set for the migration object. This migration technique transfers data to the target system using
Application Programming Interfaces (APIs).
Related Business Object: Business Partner
Business Object Component/Area User Menu Path: Accounting Financial Supply Chain
Management Credit Management Master Data
Business Partner Master Data
Component: FIN-FSCM-CR
Business Object Definition A customer is a business partner with whom a business rela
tionship exists whereby the customer orders goods or serv
ices from the company. This is one of the most commonly
used master data objects, used by almost all business appli
cations.
All credit-relevant business partner data that you want to

use in SAP Credit Management for monitoring credit risks is
contained in the credit master data. You define and update
credit master data in the master data record of the respec
tive business partner.
Available Scenarios
Selection Criteria
This migration object derives credit control areas from the company codes you specified when defining the
migration scope. This migration object automatically selects the credit segment data from the
UKMBP_CMS_SGM table for the derived credit control areas.
In Scope
● Credit management profile data

● Credit management segment data

Out of Scope
● Updating existing fields or records

● You cannot add profile data if segment data is already loaded. Segment data can only be loaded together
with the profile data.
Prerequisites
Before you can start the migration process, for example, ensure the following Customizing in the source
system:
FSCM Credit Management (FIN-FSCM-TR) is active in the source client
Target System
You have migrated or defined settings in the Customer migration object.
Source System
Not relevant
Target System
B_BUP_PCPT (Business Partner: Purpose Completed)
B_BUPA_RLT(Business Partner: BP Roles)
Name of this migration object: S4_FI_TRM_CR_ROLE
CMD_MIG_BP_CVI_CREATE (RFC to create a new BP with CVI and new segments)

Post-Processing
Not relevant
Display UKM_BP
Further Information
1.4 Document info record (DMS)
Purpose
This migration object enables you to migrate document info record data from the source ERP system to the
Related Business Object: Document Info Record
Business Object Component/Area Component: CA-DMS ( Cross-Applications: Document Man

agement )

Business Object Definition Master record containing all information necessary to man
age a document. The data is sorted according to various cri
teria. A document info record contains both descriptive data
(such as language and laboratory) and control data (such as
change number and status).Document management at SAP
has two sides: on one side are the originals, which can be in
any format, and on the other side is the document info re
cord, which makes the originals available to other SAP ob
jects by means of object links.
Available Scenarios
Selection Criteria
 Note
All document info records are automatically selected for migration. You can restrict the selection in the
LTMOM transaction.
In Scope
● Document data for document info records

● Descriptions data for document info records
● Originals data for document info records
● Content versioning data
● Additional files
● Long texts
● Status information (not including status change logs)
 Note
● Document info records you set for deletion in the source ERP system are not migrated.
● Important: Migrate document info records in the same sequence as the sequence of versions to
ensure consistency.
Additional Migration Considerations
Migrate classification details linked to the document info record separately using the Object classification
(general template) migration object.
You can migrate object links related to the document info record separately for the following migration
objects:.
● PM - Equipment

● PM - Maintenance notification
● Product
Out of Scope
● Classifications
● Document hierarchies
● Document structures
● Object links
● Change numbers
● Change logs
● Document distribution data
● Digital signature
● Status change logs
 Note
● If you have multiple steps for migration, you can simulate only this feature: Document info record
metadata.
● The following feature is out of scope for simulation: Originals/Attachments.
● During the migration phase, errors may occur for features that were not in scope during simulation
even though simulation was successful.
Prerequisites
Target System
Before you can start the migration process, ensure the following Customizing in the target system:
● The Version Assignment checkbox is deselected for the relevant document types in the IMG path: Cross-
Application Components Document Management Control Data Define Document Types .
● Important: To ensure classification assignments for those document info records that have the Locked (S-
type) status, change the status type from Locked (S) to ' ' (space) for all document types in the Define
Document Types configuration. After migraton, change the status type back from ' ' (space) to Locked (S).
● In the mapping task for the Document Number (DOKNR) field, the number range is set to external for the
DOKUMENT number range object.
● No explicit changes made to mapping tasks for document versions
● Content repository and storage category to store the originals
● MIME types in the IMG path: Cross-Application Components Document Management General Data
Define Workstation Application

 Note
Storage type: The same content repository should be used in the source and target systems. If you are
using an SAP system database as the content repository in the source system, you should configure the
same content repository as an HTTP server pointing to the source R/3 system in the target system.
Source System
system:
 Note
Documents are checked into the source system to enable them to be opened by different users in the
target system
Its recommended that, Document types have one-to-one mapping in the source and target systems with
similar configurations
 Note
Implement SAP Note 685521 in the source system. The HTTP server you are pointing to in the target
system, is the host address in the source system.
Source System
Not relevant
Target System
C_DRAW_TCD( Authorization for document activities )
C_KLAH_BKL ( Authorization for Classification )
C_TCLA_BKA ( Authorization for Class Types )
C_DRAD_OBJ ( Create/Change/Display/Delete Object Link )
C_DRAW_TCS ( Status-dependent Authorizations for documents )
To carry out data migration, assign table maintenance or table access authorizations and enter the relevant
values for the migration user.

Name of this migration object: S4_CA_DIR
Name of the BAPI used in this migration object:
BAPI_DOCUMENT_CREATE2 Create Document
Virtual Tables
AS_LONGTEXTS: To store long texts for DIR
Post-Processing
After migration, select the Version Assignment checkbox on the Define Document Types: Overview screen for
each document type. (Relevant transaction: DC10)
After migration, change the status type back from ' ' (space) to Locked (S) for all document types with the DIR
Released status for classification assignments.
This migration object creates:
● Document info records and document statuses with the migration date
● Originals data with the user and date information from the source system
codes also have built-in validation capabilities that you can use for checks.
Find Document CV04N
Change CV02N
Display CV03N
Further Information

1.5 EHS - Location
Purpose
This migration object enables you to migrate location data for Environment, Health and Safety (EHS) from the
source ERP system to the target SAP S/4HANA system based on the default selection criteria set for the
migration object. This migration technique transfers data to the target system using Application Programming
Interfaces (APIs).
Related Business Object: Location
Business Object Component/Area Component: EHS-SUS-FND
Business Object Definition An identified real place, virtual space, or object. The location
is a central master data object that can be organized in a hi
erarchy to represent where a location exists spatially or func
tionally in a company. Examples of a location are a plant, a
piece of equipment, or a work area.
Available Scenarios
Selection Criteria
In Scope
● Locations with multiple revisions

● Basic details
● Address details
● Persons responsible

Out of Scope
● Documents
● Plant Maintenance (PM) links
● Authorization groups
Prerequisites
Before you can start the migration process, for example, ensure the following Customizing in the target system:
● Location types
● Company codes
● Plants
● Storage locations
● Business areas
● Controlling areas
● Storage types
● Storage bins
 Note
This migration object transfers location names (same or updated names) to the target system. Therefore,
to prevent errors, ensure that location names are not configured in the target system.
You have migrated or defined settings in the Business partner migration object.
Source System
Not relevant
Target System
SAP_EHSM_HSS_HYGIENIST (Industrial Hygienist)
SAP_EHSM_HSS_INCIDENT_MANAGER (Incident Manager)
SAP_EHSM_HSS_ENVMGR (Environmental Manager)

Name of this migration object: S4_EHS_LOCATION
Name of the API used in this migration object:
EHFND_API_LOC_IMPORT: API for Import of Location data
Virtual Tables
● IT_LOC_REVISION: To store one or more header revision details data

● IT_LOC_REVISION_TEXT : To store one or more language texts
● IT_LOC_RESPONSIBLE : To assign responsible persons for the location
Post-Processing
Not relevant

Activity Fiori Apps
Create/Change/Display Incident Management
Further Information
1.6 EHS - Location hierarchy
Purpose
This migration object enables you to migrate location hierarchy data for Environment, Health and Safety (EHS)
from the source ERP system to the target SAP S/4HANA system based on the default selection criteria set for

the migration object. This migration technique transfers data to the target system using Application
Programming Interfaces (APIs).
Related Business Object: EHS Location Hierarchy
Business Object Component/Area Component: EHS-SUS-FND
Business Object Definition The Location Structure shows the hierarchy of locations and
their sublocations. Under the Location Structure, the user
can set a location as My Location. This serves as the starting
point in the location hierarchy as it is then displayed as the
first node. This avoids displaying the whole location struc
ture.
Available Scenarios
Selection Criteria
In Scope
● Hierarchies
● Revisions
Out of Scope
Not relevant
Prerequisites

You have migrated or defined settings in the EHS - Location migration object:
Source System
SAP_EHSM_HSS_INCIDENT_MANAGER (Industrial Hygienist )
Target System
SAP_EHSM_HSS_INCIDENT_MANAGER (Industrial Hygienist )
Name of this migration object: S4_EHS_LOCATION_HIERARCHY
EHFND_API_LHR_IMPORT: Location Hierarchy Migration
Post-Processing
Not relevant

Activity Fiori Apps
Create Incident Management
Change Incident Management

Display Incident Management
Further Information
1.7 VC - Assign global dependency to class
Purpose
This migration object enables you to assign global object dependencies to classes after migration from the
Interfaces (APIs).
Related Business Object: Class
Business Object Component/Area Component: CA-CL
Business Object Definition A group of similar objects described by means of character

istics that they have in common.
Available Scenarios
Selection Criteria
All classes that have global object dependencies assigned are automatically selected from the KLAHtable.

In Scope
● Class dependencies (Global)

● Overwritten value dependencies (Global)
● Deletion of global dependencies assignments
Out of Scope
Assignments without change numbers
 Note
During migration, this migration object checks whether class characteristics have been changed with a
change number in the target system.
If changes have taken place, the migration object uses the change number information in the source
system to assign global dependencies to the Class object and the overwritten class values.
Prerequisites
● Class
● VC - Object dependency and dependency net
Source System
Not relevant
Target System
To carry out the migration, assign the following authorization object to the user:
C_TCLA_BKA (Authorization for Class Types)

Name of this migration object: S4_CA_CLASS_ASSIGN_GLOBALOBJ_DEP
Names of the APIs used in this migration object:
● BAPI_CLASS_ALLOC_GLOB_DEP BAPI Klasse globales Beziehungwissen zuordnen

● CLCM_CLASS_FEATURE_KNOWL_VAL_O Overwrite Dependencies for Characteristic Value of Class
Virtual Tables
● AS_CLS_AENNR: To store engineering change number data

● AS_CLASS_ALLOC_DEP: To store assignment data of class dependencies
● AS_CLASS_OVERWR: To store assignment data of overwritten values
Post-Processing
Not relevant

Create CL01
Change CL02
Display CL03
Further Information
1.8 JIT - Customer

Purpose
This migration object enables you to migrate JIT customer data from the source ERP system to the target SAP
S/4HANA system based on the default selection criteria set for the migration object. This migration technique
transfers data to the target system using Application Programming Interfaces (APIs).
Related Business Object: JIT Customer
Business Object Component/Area Component: LE-JIT
Business Object Definition Indicates the party (usually original equipment manufac
turer) who receives delivery of the goods
Available Scenarios
Selection Criteria
This migration object derives sales organizations from the company codes you specified when defining the
migration scope. This migration object automatically selects JIT customers from the JITCU table if JIT
customers are defined for ship-to-party customers that belong to the derived sales organizations.
In Scope
● Basic data
● Conversion of external status information
● Destinations
Out of Scope
● Lead times
● Components group types
Prerequisites

External status and internal processing status (JIT)
You have migrated or defined settings in the Customer migration object.
Source System
Not relevant
Target System
JIT_CUSTMR (JIT Supply to Customer: JIT Customers)
Name of this migration object: S4_JIT_CUSTOMER
NJIT_MIG_CUSTOMER (Just-In-Time Customer Migration)
This migration object:
● Migrates JIT customers from the SAP ERP system to JIT Processing (Next -Generation) in the SAP S/4
HANA system.
● Identifies the ship-to-party for each JIT customer defined for the sold-to-party and partner description
combination from the KNVP (partner function) table in the source system.
● Provides a mapping task to map the Destination of JIT Customer field from the source system to the
Customer Supply Area field in the target system.
The standard API creates draft documents if the migration of JIT customers results in errors. You can delete
these draft documents manually after data migration, if required
Post-Processing
To enable the viewing of data, assign the following role to the user:
SAP_BR_MD_SPECIALIST_JIT (Master Data Specialist - Just-In-Time Supply)

You can use the Manage JIT Customer Data application to view and maintain the object in SAP Fiori.
Further Information
1.9 JVA - Joint operating agreement (step 2)
Purpose
This migration object enables you to migrate joint operating agreement data from the source ERP system to
the target SAP S/4HANA system based on the default selection criteria set for the migration object. This
migration technique transfers data to the target system using Application Programming Interfaces (APIs).
Related Business Object: Joint Operating Agreement
Business Object Component/Area User Menu Path: Accounting Joint Venture Accounting
Master Data Joint Operating Agreement
Component: CA-JVA
Business Object Definition A joint operating agreement contains the contractual agree
ments between joint venture partners. Joint venture and
equity groups are linked with each other via the equity type
and assigned within a joint operating agreement..
Available Scenarios
Selection Criteria
All joint operating agreements from the T8JU table are automatically selected for the company codes you
specified when defining the migration scope.

In Scope
● Joint operating agreements

● Stepped rate parameters at the project-level
● Parent company overheads
Out of Scope
Not relevant
Prerequisites
● Overhead rate types

● Number ranges
● Joint Operating Agreement matches the Customizing in the source system
● Joint Venture Accounting is active
● JVA - Joint operating agreement (step 1)

● PS - Project
Please migrate the Joint operating agreement (step 1) migration object before you migrate the Joint
operating agreement (step 2) migration object. Please ensure that both migration objects are included in the
same JVA migration project.
Source System
Not relevant
Target System
J_JVA_JOA (Joint Venture Accounting: Joint Operating Agreement Master)

Name of this migration object: S4_JVA_JOINT_OPERAT_AGREE_UPDATE
DMC_MIG_JVA_JOA Joint Operating Agreement Migration
Virtual Table
MANUAL_TABLE: To restrict joint operating agreements that do not have cost centers, internal orders, and WBS
elements.
Post-Processing
Not relevant
Create GJA1
Change GJA2
Display GJA3
Further Information
1.10 JVA - Joint venture master (step 1)

Purpose
This migration object enables you to migrate joint venture master data from the source ERP system to the
Related Business Object: Joint Venture
Master Data Joint Venture Maintenance
Component: CA-JVA
Business Object Definition A joint venture in the SAP System is a summarization of cost
objects whose costs are split up among partners. A joint ven
ture is usually lead by an operating authority, who is respon
sible for the costs incurred. At the end of a period, all the
costs incurred are split up and allocated to the partners in
volved. Joint ventures are created to keep costs as low as
possible for the operating authority and the partners. This is
achieved by distributing the costs incurred to the partici
pants of the joint venture.
Available Scenarios
Selection Criteria
All joint ventures from the T8JV table are automatically selected for the company codes that you specified
when defining the migration scope.
In Scope
● Basic data
● Equity type data
● Equity group data
● Burden rate type
Out of Scope
● Cross-company code data under equity groups

● Substitute cost object data
● Parent company code overhead data
● Operator code data
Prerequisites

● Joint Venture Accounting is active for the relevant company code
● Joint Venture Agreement is present with the same Customizing as in the source system
● Inter-company code is selected
● Venture class
● Equity types
● Recovery indicator
● Funding groups
● Number ranges
● Billing structures
● Billing formats
● Operator as partner
● JVA - Joint operating agreement (step 1)

● FI - House bank
 Note
If you renamed an equity group in a joint operating agreement,provide the same mapping for equity groups
in the joint venture master.
Source System
Not relevant
Target System
J_JVA_VNT (Joint Venture Accounting: Venture Master)

Name of this migration object: S4_JVA_MASTER
DMC_MIG_JVA_VENTURE Joint Venture API
Post-Processing
Migrate S4_JVA_MASTER_UPDATE (JVA - Joint venture master (step 2) ) to update the current joint venture
with this data:
● Cross-company codes
● Substitute cost objects
● Parent company overheads
● Operator codes for joint venture
If required, manually define this data:
● Inter-company mappings
● Intra-company mappings
● Adjust number ranges to the required values in the SAP S/4HANA system
Create GJVV
Change GJVV
Display GJVV
Further Information

1.11 JVA - Joint venture master (step 2)
Purpose
This migration object enables you to migrate joint venture master data from the source ERP system to the
Related Business Object: Joint Venture
Master Data Joint Venture Maintenance
Component: CA-JVA
Business Object Definition A joint venture in the SAP System is a summarization of cost
objects whose costs are split up among partners. A joint ven
ture is usually lead by an operating authority, who is respon
sible for the costs incurred. At the end of a period, all the
costs incurred are split up and allocated to the partners in
volved. Joint ventures are created to keep costs as low as
possible for the operating authority and the partners. This is
achieved by distributing the costs incurred to the partici
pants of the joint venture.
Available Scenarios
Selection Criteria
All joint venture data from the T8JV table is automatically selected for the company codes you specified when
defining the migration scope.
In Scope
● Basic data
● Cross-company code data from the Equity Groups tab

● Substitute cost object data
● Parent company code overhead data
● Operator code data
Out of Scope
● Equity type data

● Equity group data
● Burden rate type
Prerequisites

● Joint Venture Accounting is active for the relevant company code
● Joint Venture Agreement is present with the same Customizing as in the source system
● Inter-company code is selected
● Joint ventures
● Cost centers
● Internal orders
● WBS elements or projects
● JVA - Joint venture master (step 1)

● JVA - Joint venture agreement (step 2)
 Note
If you renamed an equity group in a joint operating agreement,,provide the same mapping for equity groups
in the joint venture master.
Source System
Not relevant
Target System

J_JVA_VNT (Joint Venture Accounting: Venture Master)
Name of this migration object: S4_JVA_MASTER_UPDATE
DMC_MIG_JVA_VENTURE Joint Venture API
Virtual Tables
● INTER_CODE: To store joint venture inter-company code data

● FILTER_DUMMY: To store WBS element references for substitute cost objects
● FILTER_T8JV: To store WBS element references for operator codes and filterrelevant joint ventures
Post-Processing
Adjust number ranges to the required values in the SAP S/4HANA system.
You can manually define inter-company mappings and intra-company mappings, if required.
Create GJVV
Change GJVV
Display GJVV
Further Information

1.12 Product classification (legal control)
Purpose
This migration object enables you to migrate legal control data from the source ERP system to the target SAP
Related Business Object: Product
Business Object Component/Area Component: SLL-ITR-CLS
Business Object Definition Classification of products for legal control. This includes the
assignment of control classes and control groupings as well
as the setting of the control relevance.
Available Scenarios
Selection Criteria
1. This migration object derives plants from the company codes you specified when defining the migration
scope.
2. This migration object automatically selects materials from the MARC table for the derived plants.
3. This migration object also selects the same materials from the MAEX table as the materials selected from
the MARC table.
In Scope
Legal control data
Out of Scope
● Valid-from dates
● Valid-to dates

Prerequisites
Before you can start the migration process, ensure the following Customizing in the both the source and target
systems:
● Legal regulations
● Control classes
● Control groups
You have migrated or defined settings in the Product migration object.
Source System
Not relevant
Target System
M_MATE_MAR (Material Master: Material Types)
M_MATE_MTA (Material Master: Change Material Type)
M_MATE_STA (Material Master: Maintenance Statuses)
M_MATE_WGR (Material Master: Material Groups)
Name of this migration object: S4_MM_MATERIAL_LEGAL_CONTROL
/SAPSLL/LEGCON_CLS_MIGR_BAPI Migration of Legal Control Classification
Post-Processing
To validate data, assign the SAP_BR_TRD_CLS_SPECIALIST (Trade Classification Specialist) business role to
the user in the target system.

You can validate the data using the Classify Products - Legal Control application in SAP Fiori.
1.13 RE-FX - Business partner role
Purpose
This migration object enables you to migrate RE-FX business partner role data from the source ERP system to
Business Object Component/Area Component: AP-MD-BP
Business Object Definition An organization or a private individual in which you have a

business interest. It can be a person, organization, or group
inside or outside of the company.
Available Scenarios
Selection Criteria
This migration object selects all flexible real estate documents for the company codes you specified when
defining the migration scope. This migration object picks up the flexible real estate documents from the
following tables:
● VIBDBE
● VICNCN
● VIBDPR
● VIBDBU
● VIBDRO
The migration object next selects all business partners for the flexible real estate documents from the
VIBPOBJREL table.

In Scope
● Flexible real estate business partner roles:

○ Administrator (TR0806)
○ Applicant (TR0640)
○ Appraiser (TR0815)
○ Architect ( TR0809)
○ Bank for Rent Deposit (TR0636 )
○ Correspondence Partner (TR0860)
○ Holder (TR0823)
○ Janitor (TR0808)
○ Land Lease Right Holder (TR0812)
○ Land Registry (TR0810)
○ Legal Owner (TR0811)
○ Manager w. Vendor Acct (TR0606)
○ Notary (TR0802)
○ Obligated Party (TR0824)
○ Owner (TR0800)
○ Owner (TR0605)
○ Primary Contractor (TR0804)
○ Property Developer (TR0803)
○ Subsidizer (TR0624)
○ Survey Office (TR0820)
○ Tax Office (TR0821)
○ Technology (TR0807)
● Ratings
● Creditworthiness data
○ Credit standings
○ Status of credit standing information
○ Affidavits
○ Launch bankruptcy proceedings
○ Foreclosures
● Financial reporting data
● Employment data
● Additional information
● Additional names
● Fiscal year data
Out of Scope
● Company code specific data

● Fiscal data
● Tax compliance data
● Creditworthiness data
○ Date of credit standing information
○ Additional credit standing information
○ Institutes providing credit standing information
○ Ratings
Prerequisites
You have migrated or defined settings in the Business partner migration object.
Source System
Not relevant
Target System
● B_BUPA_RLT (Business partner: BP roles)

● B_BUPA_GRP (Business partner: Authorization groups)
Name of this migration object: S4_REFX_BUSINESS_PARTNER
CMD_MIG_BP_CVI_CREATE Migration interface for BP and CVI
Post-Processing
Not relevant

Create BP
Change BP
Display BP
Further Information
1.14 TRM - Cap/Floor
Purpose
This migration object enables you to migrate cap and floor contract data from the source ERP system to the
technique transfers data to the target system using Business Application Programming Interfaces (BAPIs).
Related Business Object: Cap/Floor
Management Treasury and Risk Management
Transaction Manager Derivatives Trading Create
Financial Transaction
Component: FIN-FSCM-TRM-TM
Business Object Type Transaction data

Business Object Definition Cap: A series of interest rate options that can be exercised if
the interest rate exceeds an agreed maximum interest rate
or interest rate ceiling. The interest rate cap is compared to
the agreed reference interest rates on predefined dates. If
the reference interest rate is higher than the interest rate
cap, the buyer receives a corresponding compensation pay
ment from the seller. Opposite of a floor.
Floor: A series of interest rate options that can be exercised

if the interest rate falls below an agreed minimum interest
rate. The interest rate floor is compared to the agreed refer
ence interest rate on predetermined dates. If the reference
interest rate is lower than the interest rate floor, the buyer re
ceives a corresponding compensation payment from the
seller. Opposite of a cap.
Available Scenarios
Selection Criteria
Cap and floor contracts with the active activity categories Contract and Settlement are relevant for migration.
The relevant cap and floor contracts from the VTBFHA table are automatically selected for the company codes
you specified when defining the migration scope.
In Scope
● Structure data
● Administration data
● Additional main flows
 Note
To migrate the complete cap/floor data, ensure that these migration objects are defined in the same
project:
● TRM - Condition detail

● TRM - Additional flow
● TRM - Payment detail
Out of Scope
● Terminated transactions

● Reversed transactions
● Order activities
● Exclusive indicator and month-end indicator in main flow
● Default risk limit
● Trade repository
 Note
If you have multiple steps for migration, you can simulate only the Contract Data feature.
The following features are out of scope for simulation:
● Main Flow
● Settlement
During the migration phase, errors may occur for features that were not in scope during simulation even
though simulation was successful.
 Note
Interest rate adjustments are not migrated to the target system. You need to manually update this
information in the target system after migration.
Prerequisites
● Currency type and currency key of the controlling area assigned to the source and target company codes
must match
● Currency keys assigned to currency types belonging to different organizational units must be the same in
source and target systems.
● Factory calendars relevant for Treasury.
● Business partners with necessary authorizations
● Valuation areas for selected company codes and initialization of parallel valuation areas
● Cash flow calculation set to "Parallel Condition" under product types for premium conditions
● Product types, flow types and update types
● House banks
● Business partner
● CO - Profit center

Source System
T_DEAL_PD (Authorization for Product/Transaction Types)
F_T_TRANSB (Treasury: Transaction Authorization)
Target System
T_DEAL_PF (Portfolio Authorization)
T_POS_ASS (Assign Attributes to Positions)
T_DEAL_AG (Authorization for an Authorization Group)
B_BUPA_RLT (Business Partner: BP Roles)
B_BUPR_BZT (Business Partner Relationships: Relationship Categories)
Name of this migration object: S4_FI_TRM_INT_OPTIONS_CAP_FLOOR
BAPI_FTR_CAPFLOOR_CREATE: Create OTC Interest Rate Derivative Cap/Floor
BAPI_FTR_SETTLE: Settle Financial Transaction
Name of the API or APIs used in this migration object:
CNV_OT_APPL_FI_TRM_MAINFLOW: Update BAPI for TRM Main Flow Details
Virtual Tables
INT_CAP_FLOOR: To store the details of the cap/floor structure

Post-Processing
With the help of this migration object, you have migrated valuation-area-independent data such as quantity
data (for example, units, nominal amounts), purchase value, cost, and accrued interest to the target system. To
migrate valuation area-dependent data for SAP TRM, use the Legacy Data Transfer tool.
Create FTR_CREATE
Change FTR_EDIT
Display FTR_EDIT
Further Information
1.15 TRM - Deposit at notice
Purpose
This migration object enables you to migrate deposit at notice data from the source ERP system to the target
SAP S/4HANA system based on the default selection criteria set for the migration object. This migration
Related Business Object: Deposit at Notice

Transaction Manager Money Market Trading Deposit
At Notice Fast Entry
Business Object Type Transactional data
Business Object Definition An amount of money invested or borrowed for a term that is
unknown when the contract is concluded. Taking into ac
count a predetermined period of notice, the remaining term
is fixed when notice is given.
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 fixed term 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.
Available Scenarios
Selection Criteria
Deposit at notice transactions with the active activity categories Contract, Rollover, and Settlement are
relevant for migration. The relevant deposit at notice transactions from the VTBFHA table are automatically
selected for the company codes you specified when defining the migration scope .
In Scope
● Main condition
● Main flow of investment
● Main flow of borrowing
● Structure
● Administration
● Other flows
● Payment details

Out of Scope
● Correspondence data
● Default risk limit
● Analysis parameter data
 Note
You can simulate only the Create a deposit at notice transaction feature.
● Rollover of the transaction

● Settlement of a contract/rollover
Prerequisites
must match
source and target systems
● Conditions types and flow types
● Product types, transaction types, and update types
● Position management and links to accounting components
● All cash flows until the migration cutoff date are posted to Financial Accounting
● TRM - Business partner roles
● TRM - Facility

Source System
B_BUPA_GRP (Business Partner: Authorization Groups)
B_BUPA_PGM (Grouping Characteristic for SAP BP-FS)
Target System
Name of this migration object: S4_FI_TRM_DEPOSIT_AT_NOTICE
Names of the BAPIs used in this migration object:
BAPI_FTR_DAN_CREATE Create Deposit at Notice
BAPI_FTR_DAN_SETTLE Settle Deposit at Notice
BAPI_FTR_DAN_ROLLOVER Roll Over Deposit at Notice
BAPI_FTR_DAN_SETTLE Settle Deposit at Notice
BAPI_FTR_CONDITION_CHANGE RFC for Method Condition Change
Virtual Tables

● DAN_TAB: To store data related to the Deposit at Notice conditions
● SINGLE_DATES: To store data related to single-dates in conditions
Post-Processing
The problem of double balances: The source system contains flows related to financial transactions occurring
before migration. Please note that the information related to flows is already included in the balance sheet
migrated from the source system to the SAP S/4 HANA system. If you post these flows again in the receiver
system, the migration tool updates the general ledger twice. This means that the corresponding financial
transaction that was created in the receiver system during migration needs to be excluded from further
processing of flows.
How to avoid double balances: To avoid the double posting of flows, you can go to the TBB1_LC transaction
and select the Flag Flows as Posted check box. This transaction enables the generation of posting logs. In the FI
area, you can see the accounts to which postings need to be made to reconcile the data. This information is
required for account assignment reference transfers at a later stage of the business process. The data is also
available in the posting journal (transaction TPM20).
Valuation areas: With the help of this migration object, you have migrated valuation-area-independent data
such as quantity data (for example, units, nominal amounts), purchase value, cost, and accrued interest to the
target system. To migrate valuation area-dependent data for SAP TRM, use the Legacy Data Transfer tool.
Create FTR_CREATE, TM11
Change FTR_EDIT, TM12
Display FTR_EDIT, TM13
Further Information

1.16 VC - Assign global dependency to characteristic
Purpose
This migration object enables you to assign global object dependencies to characteristics after migration from
the source ERP system to the target SAP S/4HANA system based on the default selection criteria set for the
Interfaces (APIs).
Related Business Object: Characteristics
Business Object Definition A special allocation function that enables allocation of global
dependencies to characteristics.
Object dependencies can be defined between characteris

tics and characteristic values. They can be described in a de
pendency editor using a special syntax.
Available Scenarios
Selection Criteria
All characteristics that have global object dependencies assigned are automatically selected from the CABN
table.
In Scope
● Global dependencies for characteristics

● Overwritten values for characteristics

Out of Scope
Deletion of global object dependencies in characteristics
Prerequisites
● VC - Global object dependency and dependency net

● Characteristic
Source System
Not relevant
Target System
C_CABN (Create Characteristics)
Name of this migration object: S4_CA_CHARACTERITICS_ASGNGLOBDEP
CNV_PE_S4_CA_CHAR_GLOB_OBJ_DEP Wrapper for Global Object Dependency Allocation for Characteristics
Virtual Tables
● CABN_AS: To hold characteristics

● CAWN_AS: To hold characteristic values
● VCUOB_AS: To hold characteristic value assignments to dependencies
● VCUKB_AS: To hold maintenance information for characteristic value dependencies
● TCME_AS: To hold the validity of characteristics
● CCUOB_AS: To hold characteristic assignments to dependencies
● CCUKB_AS: To hold maintenance information for characteristic dependencies

Post-Processing
Not relevant

Create/Change/Display CT04
Further Information
1.17 VC - Interface design (characteristic group)
Purpose
This migration object enables you to migrate interface design data from the source ERP system to the target
Related Business Object: Interface Design (Characteristic Group)
Business Object Component/Area Component: LO-VC
Business Object Definition You can assign an interface design to several materials that
are assigned to the same class and therefore have the same
characteristics. When you configure these materials, you au
tomatically start with the characteristics groups that you de
fined in your interface design.
Available Scenarios

Selection Criteria
In Scope
● Basic data
● Descriptions for characteristics groups
● Format data
● Borders
● Border descriptions
Out of Scope
Advanced variant configuration
Prerequisites
You have migrated or defined settings in the VC - Configuration profile migration object.
Source System
Not relevant
Target System
C_LOVC_DSG (Interface design)

Name of this migration object: S4_LO_VC_INTERFACE_DESIGN
BAPI_UI_SAVEM Create or Change Interface Design
Virtual Tables
● ART_CECUSD: To handle basic data

● ART_CECUSDT: To handle descriptions for characteristics groups
● ART_CECUFM: To handle formats
● ART_CABN: To handle formats
● ART_CECUSF: To handle borders
● ART_CECUSFT: To handle border descriptions
Post-Processing
Not relevant

Create CU42,CU50
Change CU42, CU50
Display CU43, CU50
Further Information
1.18 VC - Variant table entry

Purpose
This migration object enables you to migrate variant table entry data from the source ERP system to the target
Related Business Object: Variant Table Entry
Business Object Component/Area Component: LO-VC
Business Object Definition A table used to store consistent combinations of values for
different characteristics in production modeling.
Available Scenarios
Selection Criteria
This object is not delimited by the company codes specified when defining the migration scope. This object
automatically selects all variant table entries from the table CUVTAB.
In Scope
Variant table maintenance data
Out of Scope
Change overview data
Prerequisites
● Characteristic
● VC - Variant table structure

Source System
Not relevant
Target System
C_LOVC_TAB (Variant Table - Structure)
C_LOVC_TCN (Variant Table - Contents)
Name of this migration object: S4_LO_VC_VARIANT_TABLE_ENTRY
CARD_TABLE_READ_ENTRIES Variant Tables - External APIs
VCH_TABLE_MAINTAIN_ENTRIES Wrapper API for Variant Table Entries Maintenance
Virtual Tables
● AS_CABN: To handle characteristic value formats

● AS_AENR: To handle change numbers
Post-Processing
Not relevant

Create CU60
Change CU60
Display CU60

Further Information
1.19 VC - Variant table structure
Purpose
This migration object enables you to migrate variant table structure data from the source ERP system to the
Related Business Object: Variant Table Structure
Business Object Component/Area User Menu Path: Logistics Central Functions Variant
Configuration Tools Table Structure
Component: LO-VC
Business Object Definition A table used to store consistent combinations of values for
different characteristics in product modeling.
Available Scenarios
Selection Criteria
This migration object automatically selects all variant table structure records from the CUVTAB table in the
source system.
In Scope
● Basic data

● Characteristics
● Value assignment alternatives
● Descriptions
 Note
Variant table structures with the Locked status are migrated with the Released status to the target SAP S/
4HANA system.
Out of Scope
Not relevant
Prerequisites
You have migrated or defined settings for the Characteristic migration object.
Source System
Not relevant
Target System
C_LOVC_TAB (Variant Table Structure)
C_LOVC_DBI (Variant Table Link to Database Table)
Name of this migration object: S4_LO_VC_VARIANT_TABLE_STRUCT
VCH_TABLE_MAINTAIN_STRUCTURE (Wrapper API for variant table maintenance)
Virtual Tables

AS_CUVTAB_IND: To handle value assignment alternatives
Post-Processing
Not relevant
Create CU61
Change CU62
Display CU63
Further Information
1.20 Batch unique at plant level
Purpose
This migration object enables you to migrate batch data unique at the plant level from the source ERP system
to the target SAP S/4HANA system based on the default selection criteria set for the migration object. This
migration technique transfers data to the target system using Business Application Programming Interfaces
(BAPIs).
Related Business Object: Batch

Business Object Component/Area User Menu Path: Logistics Central Functions Batch
Management Batch
Component: LO-BM
Business Object Definition A subset of a material in stock, managed separately from

other subsets of the same material.
Available Scenarios
Selection Criteria
This migration object automatically selects all unique batch data at the plant level from the MCHA table for the
derived plants.
In Scope
● Basic data
● Classification data
Out of Scope
● Internal number range

● Long texts for batches
Prerequisites
● Characteristic
● Class
● Object classification (general template)
● Product
● Supplier

Source System
Not relevant
Target System
M_MATE_CHG (Material Master: Batches/Trading Units)
Name of this migration object: S4_MM_BATCHES_PLANT
BAPI_BATCH_SAVE_REPLICA BAPIs for Batch
Post-Processing
Not relevant
Create MSC1N
Change MSC2N
Display MSC3N
Further Information

1.21 Batch unique at material and client level
Purpose
This migration object enables you to migrate batch data at material and client level from the source ERP
system to the target SAP S/4HANA system based on the default selection criteria set for the migration object.
This migration technique transfers data to the target system using Business Application Programming
Interfaces (BAPIs).
Management Batch
Component: LO-BM

Available Scenarios
Selection Criteria
If both Product and Batch unique at material and client level migration objects are set for migration:
This migration object first identfiies materials assigned to the company codes you specified during migration
scope. For the relevant materials, this mgiration object automatically selects all batch data unique at the
material and client levels from the MCH1 table.
If only the Batch unique at material and client level migration object is set for migration:
This object is not delimited by the company codes specified when defining the migration scope. This mgiration
object automatically selects all batch data unique at the material and client levels from the MCH1 table for
migration.
In Scope
● Basic data

Out of Scope
● Internal number ranges

Prerequisites
● Characteristic
● Class
● Product
● Supplier
Source System
Not relevant
Target System
Name of this migration object: S4_MM_BATCHES
BAPI_BATCH_SAVE_REPLICA BAPIs for Batch

Post-Processing
Nor relevant

Create MSC1N
Change MSC2N
Display MSC3N
Further Information
1.22 Bank
Purpose
This object enables you to migrate bank data from the source ERP system to the target S/4HANA system
based on the default selection criteria set for the migration object. This migration process enables you to
transfer data to the target system using Business Application Programming Interfaces (BAPIs).
Related Business Object: Bank Master
Business Object Component/Area User Menu Path: Accounting Financial Accounting
Banks Master Data Bank Master Record
Component: FI

Business Object Definition A unique number or code that uniformly identifies a bank in
the system.
Available Scenarios
Selection Criteria
This migration object automatically selects all bank keys from the BNKA table in the source system.
In Scope
● Bank country/region
● Bank key
● Bank address data
● Other address data of the bank
Out of Scope
● Check digit calculation method

● File formats with bank data
● IBAN rules
● SEPA B2B direct debit
● SEPA COR1 direct debit
● SEPA returned debits (R transactions)
● Internal bank categories
Prerequisites
Source System

Not relevant
Target System
F_BNKA_MAN (Banks: General Maintenance Authorization)
Name of this migration object: S4_CA_BANKMASTER
BAPI_BANK_CREATE Create Bank
Post-Processing
Not relevant

Create FI01
Change FI02
Display FI03
Further Information
1.23 Business partner

Purpose
This migration object enables you to migrate business partner data from the source ERP system to the target
Business Object Component/Area Component: AP-MD-BP
Business Object Definition A person, organization, or group of people/organizations in

which a company has a business interest. It can be a person,
organization, or group inside or outside of the company.
Available Scenarios
Selection Criteria
All business partners from the BUT000 table are automatically selected for the company codes you specified
In Scope
● Address data
● Address overview
● Identification data
● Control data
● Payment transactions
● Tax numbers
● Status
 Note
By default, business partners with all of the following roles are selected for migration:
● Customer
● Vendor
● Customer and vendor
Contact SAP if you want to migrate business partners with only one assigned role, such as vendor,
customer, or TRM.

Out of Scope
● Address-independent communication data

● Business hours in control data
● Status management data
Prerequisites
You have migrated or defined settings for the Bank migration object.
Source System
Not relevant
Target System
● B_BUPA_RLT (Business partner: BP roles)

● B_BUPA_GRP (Business partner: Authorization groups)
Name of this migration object: S4_AP_BUSINESS_PARTNER
CMD_MIG_BP_CVI_CREATE RFC for Creating New BP with CVI and New Segments Insertion
Post-Processing
Not relevant

Create BP
Change BP
Display BP
Further Information
1.24 Catalog code group and code
Purpose
This migration object enables you to migrate catalog code group and code data from the source ERP system to
the target SAP S/4 HANA system based on the default selection criteria set for the migration object. This
(BAPIs).
Related Business Object: Catalog Code Group
Business Object Component/Area Component: QM-PT-BD-CAT

Business Object Definition A catalog is a collection of codes with related contents. Cata
logs are used to encode qualitative contents described in
text form in a format that can be machine processed. Sub
sets of codes can be grouped within a catalog according to
various criteria. Selected sets of codes can also be created
for a particular purpose. The most widely-used catalogs con
tain: Characteristic attributes, usage decisions, tasks, and
defect types.
A code group is key for summarizing codes and structuring a

catalog according to various criteria. The assignment of co
des to code groups takes place at client level.
A code is a key that uniquely identifies the qualitative con

tents of a problem in a coded form that is machine readable.
Each code is assigned to a code group in the catalog. A code
can describe: a characteristic attribute, a defect type or a us
age decision.
Available Scenarios
Selection Criteria
In Scope
Catalog code group and code data
Out of Scope
● Classification
● Statuses set to Can no longer be used
Prerequisites

Source System
Not relevant
Target System
Q_CAT_GRP (Catalog Maintenance of Group Codes and Codes)
Name of this migration object: S4_QM_CATALOG_CODE
BAPI_QPGR_SAVEREPLICA Replication of QM Code Groups/Catalogs
Post-Processing
Not relevant
Create / Edit QS41
Display QS42
Further Information

1.25 Characteristic
Purpose
This migration object enables you to migrate characteristic data from the source ERP system to the target SAP
Related Business Object: Characteristic
Business Object Component/Area User Menu Path: Cross-Application Components
Classification System Master Data Characteristics
Component: CA-CL
Business Object Definition Property for describing and distinguishing between objects,
such as length, color, or weight.
Available Scenarios
Selection Criteria
 Note
All characteristics from the CABN table in the source system are automatically selected for migration.
In Scope
● Basic data
● Names
● Characteristic values
● Additional data
● Restrictions
● Document info record assignments

● Basic data of local dependencies
● Descriptions of local dependencies
● Documentations of local dependencies
● Source code of local dependencies
● Long texts for characteristics and characteristic values
 Note
● You can migrate only the allowed values from the value check strategy.
● If there are any dependency source code errors, dependencies with the Released status are migrated
with the Locked status.
Out of Scope
● Value check strategies other than allowed values

● Assignment of global dependencies
● Advanced variant configuration for dependencies
 Note
You can simulate only this feature: Create characteristic
● Changes related to change numbers

● Characteristic dependencies
Prerequisites
● CA - Document info record (DMS)

● ECM - Change master
Source System
Not relevant

Target System
C_CABN (Authorization for Characteristics Maintenance)
Name of this migration object: S4_CA_CHARACTERISTICS
BAPI_CHARACT_CREATE BAPI for Characteristics - Create
BAPI_CHARACT_CHANGE BAPI for Characteristics - Change
CTMV_CHARACT_CHANGE_KNOWL API Function: Maintaining object dependencies for characteristics
CTMV_CHARACT_CHANGE_KNOWL_VAL API Function: Maintaining object dependencies for characteristics
Virtual Tables
● CABN_AS: To store characteristic basic data

● CABNT_AS: To store characteristic texts
● CABNT_LONGTXT: To store characteristic long texts
● CAWN_AS: To store characteristic values
● CAWNT_AS: To store characteristic value texts
● VCUOB_AS: To store characteristic values object dependencies
● VCUKB_AS: To store characteristic values dependency administration information
● VCUKBT_AS: To store characteristic values dependency texts
● VCUKN_AS: To store dependency source code for characteristic values
● VDOC1_AS: To store dependency long texts for characteristic values
● CAWNT_LONGTXT: To store long texts for characteristic value
● TCME_AS: To store validity of global characteristics
● CCUOB_AS: To store characteristic object dependencies
● CCUKB_AS: To store administration information for characteristic dependencies
● CCUKBT_AS: To store characteristic dependency texts
● CCUXREF_AS: To store cross references for source code object dependencies
● CCABN_AS: To store internal characteristics
● CCUKN_AS: To store administration information for characteristics
● CDOC1_AS: To store dependency long texts for characteristics
Note that these tables do not exist in the database.

Post-Processing
Not relevant

Create CT04
Change CT04
Display CT04
Further Information
1.26 Class
Purpose
This migration object enables you to migrate class data from the source ERP system to the target SAP S/
Classification System Master Data
Component: CA-CL

Available Scenarios
Selection Criteria
This migration object automatically selects all classes from the KLAH table in the source system.
In Scope
● Class basic data

● Class standard data
● Class keywords
● Class characteristics
● Class long texts
● Class local dependencies
● Characteristic overwritten values
● Characteristic overwritten value local dependencies
Out of Scope
● Long texts for characteristic overwritten values

● Deletion of local dependencies for classes
● Deletion of local dependencies for characteristic overwritten values
● Changes of local dependencies for classes using change numbers
● Changes of local dependencies for characteristic overwritten values using change numbers
● Linkages between class and document
● Class global dependencies
● Characteristic overwritten value global dependencies
● Simulation

Prerequisites
● Characteristic
Source System
Not relevant
Target System
C_TCLA_BKA (Create/Validate)
Name of this migration object: S4_CA_CLASS_ECN
Name of the APIs used in this migration object:
BAPI_CLASS_CREATE Create Class BAPI
BAPI_CLASS_CHANGE BAPI Change Class
BAPI_CLASS_MAINT_LOCAL_DEP BAPI Klasse lokales Beziehungswissen zuordnen / löschen
CLCM_CLASS_FEATURE_KNOWL_VAL_O Overwrite Dependencies for Characteristic Value of Class
Virtual Tables
● AS_CLS_AENNR: To handle change numbers

● AS_CLASS_ALLOC_DEP: To handle class allocation dependencies
● AS_CLASS_LCL_DEP_DESCR: To handle local dependency descriptions for classes
● AS_CLASS_LCL_DEP_LTXT: To handle local dependency long texts for classes
● AS_CLASS_LONG_TEXTS: To handle class long texts
● AS_CLASS_OVERWR: To handle characteristic overwritten values for classes
● AS_CLS_OVRWR_DSCR: To handle characteristic overwritten descriptions for classes

Post-Processing
Not relevant

Create CL01
Change CL02
Display CL03
Further Information
1.27 Condition contract
Purpose
This migration object enables you to migrate condition contract data from the source ERP system to the target
Related Business Object: Condition Contract
Business Object Component/Area User Menu Path: Logistics Settlement Management
Condition Contract Management Master Data
Component: LO-AB

Business Object Definition A document used to record conditions that a partner (usu
ally a vendor) grants to a limited group of eligible partners
(usually customers).
Available Scenarios
Selection Criteria
In Scope
● Condition contract header data

● Eligible partner data
● Condition table data including scale data
● Condition contracts with New or Released system statuses
● Condition object types (KONDIND-OBTYP) with the value 20
Out of Scope
● Condition contract header texts

● Post processing framework actions
● Settlement calendar data
● Business volume base data
● Condition contracts that do not have the New or Released system statuses
Prerequisites
● Customer
● Exchange rate
● Product
● Supplier

Source System
Not relevant
Target System
● W_COCO (Controls whether documents from a condition contract type can be processed)
● W_COCO_ORG (Controls whether documents from a condition contract type can be processed for the
specified organizational units)
Name of this migration object: S4_GT_CONDITION_CONTRACT
BAPI_CONDITION_CONTRACT_CREATE Create Condition Contract
Virtual Tables
● AS_COND_KEY: To handle condition key data

● AS_SCALE: To handle condition scale data
Post-Processing
Not relevant
Create WCOCO
Change WCOCO
Display WCOCO

Further Information
1.28 Customer
Purpose
This migration object enables you to migrate customer master data from the source ERP system to the target
Related Business Object: Customer
Business Object Component/Area User Menu Path: Logistics Sales and Distribution
Master Data Business Partner Customer
Component: SD
Business Object Definition A business partner with whom a business relationship exists,
involving the issue of goods or services.
Available Scenarios
Selection Criteria
migration scope. This migration object automatically selects all customers from the KNA1 table for the
company codes and derived sales organizations.
In Scope
● Basic data
● Company data including dunning

● Contact persons
● Bank data
● Sales data including sales partner functions
● Industry assignments
● Credit management control data
● Extensions of existing customers to new organization levels
● Credit card data
● Only the following long texts
○ Customer texts
○ Company code texts
○ Sales organization texts
○ Contact person texts
● International versions of addresses
 Note
● If a customer in the source system is extended to multiple company codes, after data migration, the
customer in the target system is extended only to the participating company codes.
● If a customer in the source system has multiple sales organizations, after data migration, the customer
in the target system contains only the selected sales organizations.
Out of Scope
● Documents assigned to the customer

● Classifications
● Updates to existing fields
● Extensions of withholding tax or dunning or texts data to the existing company codes
● Extensions of partner functions of existing sales organizations
● Extensions of existing addresses with an international address version.
● Extensions of sales organizations belonging to existing company codes
Prerequisites
Source System
Before you can start the migration process, ensure that you have defined values for all fields set as mandatory
in the target system. Otherwise, errors may occur after migration. Alternatively, blank values are populated in
the mandatory fields after data migration.
Target System
Before you can start the migration process, you have:

● Defined all mandatory Customizing for customer-vendor integration (CVI) in the target system.
● Provided the customer account group in the Customer Account Group (MAP_KTOKD) mapping task.
Doing so enables the migration object to determine the business partner grouping and roles from the
following customizing paths:
Business Partner Info Customizing (IMG) Path
Business partner role Cross-Application Components Master Data

Synchronization Customer/Vendor Integration
Business Partner Settings Settings for Customer
Integration Define BP Role Direction Customer to BP
Business partner group Cross-Application Components Master Data

Integration Field Assignment for Customer Integration
Assign Keys Define Number Assignment for Direction
Customer to BP
● Registered the CVI_EI_INBOUND_REQ_ACTIVATE function module using the CRMC_BUT_CALL_FU

transaction code with the following entries:
Column Names Values to Be Filled
Event CRM Inbound
Object Business Partner
Item <Value less than 10000>
Function Name CVI_EI_INBOUND_REQ_ACTIVATE
Call Selected
● Bank
● FI - G/L account
If a business partner is linked to a customer in the source system, please migrate the Business partner
migration object before you migrate the Customer migration object. Please ensure that both migration
objects are included in the same migration project.
● Supplier
○ If the customer and vendor refer to the same business entity in the source system, please migrate the
Customer migration object before you migrate the Supplier migration object. Please ensure that both
migration objects are included in the same migration project.
○ If the business partner is linked to both the customer and vendor in the source system, please migrate
the Business partner migration object first, followed by the Customer migration object, and finally the
Supplier migration object. Please ensure that all three migration objects are included in the same
migration project.

Source System
Not relevant
Target System
To carry out the migration, assign the following authorization objects to the user:
F_KNA1_GEN (Customer: Central Data)
F_KNA1_BUK (Customer: Authorization for Company Codes)
F_KNA1_APP (Customer: Application Authorization)
F_KNA1_GRP (Customer: Account Group Authorization)
F_KNA1_BED ( Customer: Account Authorization)
V_KNA1_VKO (Customer: Authorization for Sales Organizations)
Name of this migration object: S4_SD_CUSTOMER_MASTER

This migration object identifies the business partner category from the TSAD3 Customizing table belonging to
the customer title. If, for example, the customer title in the source system is "company", the business partner
category is "organization".
Handling Referenced Customer Accounts
Migration Context Migration Object Behavior User Action Required
If the customer account has referenced This migration object migrates the cus 1. Set the referenced customer ac
customer accounts such as sold-to counts for migration or manually
tomer account, but not the referenced
party or ship-to part party in the source create the referenced customer
customer accounts. The migration ends
system, but only the customer account accounts in the target system.
is set for migration. in error.
2. Migrate the migration object again.
If the customer account has referenced This migration object migrates all cus Not relevant
customer accounts in the source sys tomer accounts along with the referen
tem, and all relevant customer ac ces among the relevant customer ac
counts are set for migration. counts.

If the customer account has referenced This migration object migrates the cus 1. Migrate the migration object again.
customer accounts in the source sys tomer account first and the referenced 2. This migration object updates ref
tem, and all relevant customer ac customer accounts later. The migration erences among the relevant cus
counts are set for migration. ends in error. tomer accounts.
Virtual Tables
● ADRC_VRN: To store international address versions

● KNB1_TEXT: To store company long text headers for customers
● KNB1_TEXT_DATA: To store customer company text data
● KNVV_TEXT: To store sales long text headers for customers
● KNVV_TEXT_DATA: To store sale long text data for customers
● TAXNUMBER: To store tax numbers
● BP_GENERAL: To store business partner general data
● ADRC_C: To store contact person addresses
● ADR2_C: To store telephone numbers for contact persons
● ADR3_C: To store fax numbers for contact persons
● ADR4_C: To store teletex numbers for contact persons
● ADR5_C: To store telex numbers for contact persons
● ADR6_C: To store e-mail addresses for contact persons
● ADR7_C: To store remote mail addresses (SAP - SAP - Communication; BAS) for contact persons
● ADR8_C: To store X.400 numbers for contact persons
● ADR9_C: To store RFC destinations for contact persons
● ADR10_C: To store ADR10 printer information for contact persons
● ADR11_C: To store SSF information for contact persons
● ADR12_C: To store FTP and URL data for contact persons
● ADR13_C: To store pager information for contact persons
● ADRT_C: To store communication data texts for contact persons
● ADRU_C: To store the communication usages of contact persons
● ADRCT_C: To store address texts for contact persons
● ADRC_C_VRN: To store the international address versions for contact persons
● KNVK_TEXT: To store contact long text headers for customers
● KNVK_TEXT_DATA: To store contact long text data for customers
● KNA1_TEXT: To store long text header for customers
● KNA1_TEXT_DATA: To store customer text data
● BP_ROLES: To store business partner roles
● KNZA_GEN: To store alternative payer data that is common for all company codes
Mapping Task Information
Use Case Enter Values for In the Mapping Tasks

If the customer and the vendor refer to Customer and Vendor Customer Number (MAP_KUNNR)
the same business entity in the source
and
system.
Vendor Number (MAP_LIFNR) respec
tively
For example: Customer ABC and ven

dor XYZ refer to the same business en
tity in the source system. When cus
tomer ABC is migrated to the target
system, assume business partner PQR
is created with customer roles. Later,
when you migrate the vendor migration
object, the business partner PQR is au
tomatically assigned to the supplier
XYZ.
If BUPA business function is active in Business partner, Business Partner (MAP_BU_PART

the source system, and the business
NER)
partner is related to both the customer Customer and
and vendor in the source system Customer Number (MAP_KUNNR)
Supplier
and

tively
If the customer is not related to the Customer Customer Number (MAP_KUNNR)

business partner or the vendor in the
source system (classical scenario)
If the customer account group is as Customer Customer Number (MAP_KUNNR)

signed to an external number range
If the customer account group is as Customer (Enter a blank.) Customer Number (MAP_KUNNR)
signed to an internal number range
Post-Processing
Not relevant.
Maintain Business Partner BP

Further Information
1.29 CO - Activity type
Purpose
This migration object enables you to migrate activity type master data from the source ERP system to the
Related Business Object: Activity Type
Business Object Component/Area User Menu Path: Accounting Controlling Cost Center
Accounting Master Data Activity Type
Component: CO
Business Object Definition A unit in a controlling area that classifies the activities per
formed in a cost center.
Available Scenarios
Selection Criteria
This migration object derives the controlling area from the company codes you specified when defining the
migration scope. This migration object automatically selects all activity types from the CSLA table for the
derived controlling areas.
In Scope
● Basic data
● Activity type texts

Out of Scope
Not relevant
Prerequisites
● Cost center categories

● Activity type categories
● CO - Activity type group

● CO - Secondary cost element
Source System
Not relevant
Target System
K_CSLA (CO-CCA: Activity Types Master)
Name of this migration object: S4_CO_ACTIVITY_TYPE
BAPI_ACTTYPE_CREATEMULTIPLE Create One or More Activity Types
Post-Processing

Create KL01
Change KL02
Display KL03
Further Information
1.30 CO - Activity type group
Purpose
This migration object enables you to migrate activity type group master data from the source ERP system to
(BAPIs).
Related Business Object: Activity Type Group
Accounting Master Data Activity Type Group
Component: CO
Business Object Definition An organizational unit to combine several activity types.
Available Scenarios
Selection Criteria

migration scope. This migration object automatically selects activity type groups belonging to set classes from
the SETHEADER table for the derived controlling areas.
 Note
The migration object selects the set class with the value 0105 (Activity Type Group) for transfer.
In Scope
● Basic data
● Groups and values
 Note
This migration object transfers activity type groups maintained in the source system to the target system
without any changes. If you want to rename an activity type during migration, you may have to manually
modify the activity type names in the groups.
Out of Scope
Not relevant
Prerequisites
Source System
K_CSLA_SET ((CO:CCA: Activity Type Groups))
Target System

Name of this migration object: S4_CO_ACTIVITY_GROUP
Name of the BAPIs used in this migration object:
Target System
BAPI_ACTIVITYTYPEGRP_CREATE Object BUS1115 (Activity Type Group) - Method Create
Source System
BAPI_ACTIVITYTYPEGRP_GETDETAIL Object BUS1115 (Activity Type Group) - Method GetDetail
Virtual Tables
● TAB_NODES: Hierarchy Nodes

● TAB_VALUES: Hierarchy Values
Post-Processing
Not relevant

Create KLH1
Change KLH2
Display KLH3
Further Information

1.31 CO - Business process
Purpose
This migration object enables you to migrate business process data from the source ERP system to the target
Related Business Object: Business Process
Business Object Component/Area User Menu Path: Accounting Controlling Activity-
Based Costing Master Data Business Process
Component: CO-OM
Business Object Definition Process in a company that uses resources and can involve
the activities of different departments.
A business process can consume the output of multiple cost

centers in a controlling area.
Available Scenarios
Selection Criteria
migration scope. This migration object automatically selects all business processes from the CBPR table for the
In Scope
● Basic data
● Organizations
● Attributes
● Allocation
● Templates

Out of Scope
Not relevant
Prerequisites
You have migrated or defined settings in the following migration object:
● CO - Business process group
Source System
Not relevant
Target System
K_ABC (CO-ABC: General Authorization Object, Business Processes)
K_CBPR_SET (CO-ABC: Business Process Groups)
Name of this migration object: S4_CO_BUSINESS_PROCESS
BAPI_PROCESS_CREATEMULTIPLE: Create One or More Business Processes
Post-Processing
Not relevant

Create CP01
Change CP02
Display CP03
Further Information
1.32 CO - Business process group
Purpose
This object enables you to migrate business process groups and assigned standard hierarchies from the source
ERP system to the target S/4HANA system based on the default selection criteria set for the migration object.
This migration process enables you to transfers data to the target system using Business Application
Programming Interfaces (BAPIs).
Related Business Object: Business Process Group
Based Costing Master Data Business Process Group
Component: CO-OM-ABC

Business Object Definition When you create a business process, you must assign it to a
group, which can be either the standard hierarchy itself or a
business process group that belongs to the standard hierar
chy. The standard hierarchy is the business process group
that you create before you define the first business process.
You can create additional business process groups as subor
dinate nodes under the standard hierarchy.
Available Scenarios
Selection Criteria
migration scope. This migration object automatically selects all business process groups and the standard
hierarchies from SETHEADER table for the derived controlling areas.
In Scope
● Basic data
● Standard hierarchies assigned to the controlling area
 Note
After the business process master data is migrated to the target system, the respective business process is
assigned to the corresponding hierarchy area.
Out of Scope
Values assigned to standard hierarchies
Prerequisites
● Standard hierarchies for business processes

● Assignment of standard hierarchies to controlling areas

Source System
Not relevant
Target System
● K_CBPR_SET (CO-ABC: Business Process Groups)

● K_ABC (CO-ABC: General Authorization Object, Business Processes)
Name of this migration object: S4_CO_BUSINESS_PROCESS_GROUP
BAPI_BUSPROCESSCOGRP_CREATE Object BUS1114 (Business Process Group) - Method Create
Post-Processing
Not relevant
Create CPH1
Change CPH2
Display CPH3
Further Information

1.33 CO - Cost center
Purpose
This migration object enables you to migrate cost center data from the source ERP system to the target SAP
Related Business Object: Cost Center
Accounting Master Data Cost Center
Component: CO
Business Object Definition An organizational unit within a controlling area that repre
sents a defined location of cost incurrence.
The definition can be based on:
● Functional requirements
● Allocation criteria
● Physical location
● Responsibility for costs
Available Scenarios
Selection Criteria
migration scope. This migration object automatically selects all cost centers from the CSKS table for the
In Scope
● Basic data
● Company code data
● Address data

● Validity
● Communication data
Out of Scope
Not relevant
Prerequisites
● CO - Cost center group

Source System
Not relevant
Target System
K_CCA (CO-CCA: Gen. Authorization Object for Cost Center Accounting)
K_CSKS (CO-CCA: Cost Center Master)
K_CSKS_SET (CO-CCA: Cost Center Groups)
Name of this migration object: S4_CO_COST_CENTER
BAPI_COSTCENTER_CREATEMULTIPLE Create Cost Center

Post-Processing
Not relevant

Create KS01
Change KS02
Display KS03
Further Information
1.34 CO - Cost center group
Purpose
This migration object enables you to migrate cost center groups and assigned standard hierarchies from the
migration object. This migration technique transfers data to the target system using standard Business
Application Programming Interfaces (BAPIs).
Related Business Object: Cost Center Group
Business Object Component/Area User Menu Path Accounting Controlling Cost Center
Accounting Master Data Cost Center Group
Component: CO

Business Object Definition A hierarchical group of cost centers defined and organized
according to selected criteria.
Available Scenarios
Selection Criteria
migration scope. This migration object automatically selects cost center groups and the assigned standard
hierarchies from the SETHEADER table for the derived controlling areas.
In Scope
Cost center groups
Standard hierarchies assigned to the controlling area
Out of Scope
● Values assigned to standard hierarchies

● Values assigned to related cost center groups
● Standard hierarchies belonging to controlling areas where the enterprise organization is active
Prerequisites
Standard hierarchies belonging to cost center groups are assigned to the relevant controlling area.
Source System

Target System
Name of this migration object: S4_CO_COST_CENTER_GROUP
BAPI_COSTCENTERGROUP_CREATE Object BUS1112 (Cost Center Group) - Method Create
Virtual Tables
TAB_NODES: To store the nodes of the standard hierarchy
Post-Processing
Not relevant

Create KSH1
Change KSH2
Display KSH3
Further Information

1.35 CO - Cost element group
Purpose
This migration object enables you to migrate cost element group data from the source ERP system to the
Related Business Object: Cost Element Group
Accounting Master Data Cost Element Group
Component: CO
Business Object Definition An organizational entity that combines cost elements of the
same type. Cost element groups can serve various purposes.
For example, they can be used to create reports or to proc
ess several cost elements in one business transaction.
Available Scenarios
Selection Criteria
This migration object derives the chart of accounts from the company codes you specified when defining the
migration scope. This migration object automatically selects the cost element groups from the SETHEADER
table for the derived charts of accounts.
In Scope
● Basic data
 Note
This migration object transfers cost element groups maintained in the source system to the target system
without any changes. If you want to rename a cost element during migration, you may have to manually
modify the cost element names in the groups.

Out of Scope
Not relevant
Prerequisites
Source System
K_CSKA_SET (CO-CCA: Cost Element Groups)
Target System
Name of this migration object: S4_CO_COST_ELEMENT_GROUP
BAPI_COSTELEMENTGRP_CREATE: Create Cost Element Group
Virtual Tables
● TAB_NODES: To store group nodes

● TAB_VALUES: To store group ranges

Post-Processing
Not relevant

Create KAH1
Change KAH2
Display KAH3
Further Information
1.36 CO - Cost rate
Purpose
This migration object enables you to migrate cost rate data from the source ERP system to the target SAP S/
Related Business Object: Activity Price
Accounting Planning Activity Output/Prices
Component: CO-OM

Business Object Definition The amount charged for services performed for external or
internal receivers.
Available Scenarios
Selection Criteria
migration scope. This migration object automatically selects all cost rate data from the CSSL table for the
controlling areas.
Additional selection criteria
All cost rate data from the CSSL table is automatically selected for the current fiscal year, previous fiscal year,
and the upcoming fiscal year. Fiscal year data enables a comparison of planned and actual cost rates.
In Scope
● Header information
● Objects for plan activity
● Period values for plan activity
● Control values for plan activity
 Note
Cost rates for business processes in the source system are not migrated
Out of Scope
Not relevant
Prerequisites
● CO - Activity type

Source System
Target System
K_CBPR_PLA (CO-ABC: Business Process Planning)
Name of this migration object: S4_CO_ACTIVITY_PRICE
BAPI_COSTACTPLN_CHECKACTOUTPUT: Activity/Price Planning: Check
Virtual Tables
FLTR_CSSL: To store cost rate data of the previous, current, and upcoming fiscal years.
Note that the virtual tables do not exist in the database.
The migration object transfers cost rate information to the target system with default values for the following
fields:
Field Default Value
PERIOD_FROM 001
PERIOD_TO 012
PLAN_CURRTYPE C
Post-Processing
Not relevant


Create KP26
Change KP26
Display KP27
Further Information
1.37 CO - Internal order
Purpose
This migration object enables you to migrate internal order data from the source ERP system to the target SAP
Related Business Object: Internal Order
Business Object Component/Area User Menu Path: Accounting Controlling Internal
Orders Master Data Special Functions Order
Create
Component: CO
Business Object Definition An internal order is an instrument used to monitor costs

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

● Monitoring the costs and revenues of a specific service
● Ongoing cost control
Available Scenarios
Selection Criteria

This migration object derives controlling areas from the company codes you specified when defining the
migration scope. This migration object automatically selects internal orders from the AUFK table for the
In Scope
● Basic data
● Internal order description
 Note
After migration, all internal orders are set to the Created status regardless of the status in the source
system.
Out of Scope
Not relevant
Prerequisites
● Plant
● Object class
● Business area
● Functional area
● SD - Customer quotation
● PS - Network
If you want to set the status of all migrated internal orders to Released: You have set the order profile in the
KOT2_OPA transaction and selected Release Immediately before migration.

 Note
With this setting, after migration, all internal orders are set to the Released status regardless of the status
in the source system.
Source System
Not relevant
Target System
K_ORDER (CO-OPA General authorization object for internal orders)
B_URSERST_T (Status Management Set/Delete User Status using Transaction)
S_ADMI_FCD (System Authorizations)
Name of this migration object: S4_CO_INTORDER
BAPI_INTERNALORDER_CREATE Create Internal Order from Transferred Data
If you have set the number range object to internal, the BAPI still treats it as an external number range object.
As a result, errors might occur even though migration was successful.
Post-Processing
Not relevant


Create KO01
Change KO02
Display KO03
Further Information
1.38 CO - Profit center
Purpose
This migration object enables you to migrate profit center data from the source ERP system to the target SAP
Related Business Object: Profit Center
Business Object Component/Area User Menu Path: Accounting Controlling Profit Center
Accounting Master Data Profit Center
Component: CO
Business Object Definition An organizational unit in Accounting that reflects a manage

ment-oriented structure of the organization for the purpose
of internal control. Operating results for a profit center can
be analyzed using either the cost of sales approach or the
period accounting approach. By analyzing the fixed capital
as well, you can expand your profit center for use as an in
vestment.
Available Scenarios
Selection Criteria

migration scope. This migration object automatically selects all active profit centers from the CEPC table for
the derived controlling areas.
In Scope
● Basic data
● Address data
● Validity information
Out of Scope
Inactive profit centers
Prerequisites
● CO - Profit center group

Source System
Not relevant
Target System
K_PCA EC-PCA: Responsibility Area, Profit Center

Name of this migration object: S4_CO_PROFIT_CENTER
BAPI_PROFITCENTER_CREATE Create Profit Center
 Note
If the profit center is assigned to several company codes, this migration object assigns only the specified
company codes to the profit center in the target system. This migration object sets the ASSIGN_TO_PRCTR
parameter to X in the CEPC_BUKRS table for the BAPI BAPI_PROFITCENTER_CREATE.
Post-Processing
Not relevant
Create KE51
Change KE52
Display KE53
Further Information
1.39 CO - Profit center group

Purpose
This migration object enables you to migrate profit center groups and assigned standard hierarchies from the
migration object. This migration technique transfers data to the target system using Business Application
Related Business Object: Profit Center Group
Accounting Master Data Profit Center Group
Component: CO
Business Object Definition A profit center group is a hierarchical structure of profit cen
ters.
Available Scenarios
Selection Criteria
migration scope. This migration object automatically selects profit center groups and the assigned standard
In Scope
Profit center groups
Out of Scope

● Values assigned to related profit center groups

Prerequisites
Standard hierarchies belonging to profit center groups are assigned to the relevant controlling area.
Source System
K_PCA (EC-PCA: Responsibility Area, Profit Center)
Target System
K_PCAP_SET (EC-PCA: Planning Hierarchy)
F_UNI_HIER (Universal Hierarchy Access)
K_PCA_MD (EC-PCA: Authorization Object for Profit Center Master Data)
Name of this migration object: S4_CO_PROFIT_CENTER_GROUP
BAPI_PROFITCENTERGRP_CREATE: Object BUS1116 (Profit Center Group) - Method Create
Virtual Tables
TAB_NODES: To store nodes of the standard hierarchy

Post-Processing
Not relevant.

Create KCH1
Change KCH2
Display KCH3
Further Information
1.40 CO - Secondary cost element
Purpose
This migration object enables you to migrate secondary cost element master data from the source ERP system
Related Business Object: Secondary Cost Element
Business Object Component/Area User Menu Path: Accounting Controlling Cost
Element Accounting Master Data Cost Element
Individual Processing Edit Cost Element
Component: CO

Business Object Definition A cost element that is used to allocate costs for internal ac
tivities.
Available Scenarios
Selection Criteria
This migration object derives the controlling area from company codes you specified when defining the
migration scope. This migration object automatically selects all secondary cost elements from the CSKB table
for the derived controlling areas.
In Scope
● Basic data
● Chart of accounts data
● General texts
Out of Scope
Default account assignments
Prerequisites
Company code assignments to the controlling area
FI - G/L account
Source System
Not relevant

Target System
K_CSKB (CO-CCA: Cost Element Master)
Name of this migration object: S4_CO_SECONDARY_COST_ELEMENT
GL_ACCT_MASTER_SAVE G/L Account Master Record
If a group chart of accounts is assigned to a chart of accounts, use the values in the MAP_KTOPL_BILKT
mapping task.
If a countryspecific/local chart of accounts is assigned at the company code level, use the values in the
MAP_BUKRS_ALTKT mapping task.
If a group chart of accounts is assigned to a chart of accounts, and a countryspecific/local chart of account is
assigned at the company code level, use the values in both the MAP_KTOPL_BILKT and MAP_BUKRS_ALTKT
mapping tasks.
Fixed values defined in this migration object for secondary elements:
● Type of general ledger account is S

● P&L statement account type is X
● G/L account group is SECC
● Field status group is SECC
● Cost element category is 21, 31, 41, 42, 43, 50, 51, 52 or 61
Post-Processing
Not relevant

Create FS00
Change FS00

Display FS00
Further Information
1.41 CO - Statistical key figure (ERP)
Purpose
This migration object enables you to migrate statistical key figure data from the source ERP system to the
Related Business Object: Statistical Key Figure
Accounting / Cost Center Accounting Master Data
Statistical Key Figures Individual Processing Create
Component: CO
Business Object Definition The statistical values describe the following
● Cost center
● Business process
● Profit center
There are the following types of statistical key figures:
● Fixed value: They are carried forward from the current

posting period to all subsequent posting periods.
● Total value: They are posted in the current posting pe
riod only.
Available Scenarios
Selection Criteria

migration scope. This migration object automatically selects the statistical key figures from the TKA03 table for
In Scope
● Basic data
● Statistical key figure descriptions in one of available languages
Out of Scope
LIS data for statistical key figures
Prerequisites
● Statistical key figure hierarchies
Source System
Not relevant
Target System
S_ADMI_FCD(System Authorizations)
Name of this migration object: S4_CO_STAT_KEY_FIGURE

BAPI_KEYFIGURE_CREATEMULTIPLE Create One or More Statistical Key Figures
Post-Processing
Not relevant
Create KK01
Change KK02
Display KK03
Further Information
1.42 ECM - Change master
Purpose
This migration object enables you to migrate engineering change number data from the source ERP system to
(BAPIs).
Related Business Object: Engineering Change Number

Engineering Change Management Change Number
Component: LO-ECH
Business Object Definition A component that allows objects to be changed with history
(with date validity) or dependent on specific conditions (with
parameter effectivity).
The different processing statuses of the object are saved. All

changes are made with reference to a change master record.
In the SAP system, object types can be changed with refer
ence to a change number, such as:
● Bills of material
● Task lists
● Documents
● Materials
Available Scenarios
Selection Criteria
In Scope
● Object types
○ Bills of material
○ Documents
○ Materials
○ Characteristics
○ Class characteristics
○ Task lists
○ Classifications
○ Object dependencies
○ Configuration profiles
○ Variant tables
● Alternative dates
● Change header long texts
 Note
Engineering change numbers you set for deletion in the source ERP system are not migrated.

Out of Scope
● Effectivity data
● Object assignments
● Engineering change request
Prerequisites
Source System
Not relevant
Target System
C_AENR_ERW (CC Eng. Chg. Mgmt. Enhanced Authorization Check)
C_AENR_BGR (CC Change Master - Authorization Group)
Name of this migration object: S4_CA_ENGG_CHANGE_NUMBERS
BAPI_ECN_CREATE BAPI ECN Create
Virtual Tables
AENR_TEXT: To store header texts
During migration, for each object type in the migration scope for Engineering Change Number, this migration
object clears the values for the GEN_NEW and GEN_DIALOG fields in the target system. Clearing is necessary to
ensure that there are no dependencies on other master data objects during migration.

Post-Processing

Create CC01
Change CC02
Display CC03
Further Information
1.43 Exchange rate
Purpose
This migration object enables you to migrate exchange rate data from the source ERP system to the target SAP
Related Business Object: Exchange Rate
Business Object Component/Area User Menu Path: SAP Netweaver General Settings
Currencies Enter Exchange Rates
Component: FI

Business Object Definition Exchange rate defines the relationship between two curren
cies. They are used to translate an amount into another cur
rency.
Available Scenarios
Selection Criteria
Exchange rates are defined at the client level and are relevant across company codes. Hence, this migration
object migrates all exchange rates maintained in the TCURR table in the source system to the target system.
In Scope
Exchange rate
Out of Scope
Incomplete exchange rates. For example, exchange rate information that is available in the TCURR table is
missing in the TCURF table.
Prerequisites
● Currencies
● Exchange rate types
● Translation ratios
Source System
Not relevant
Target System

To migrate exchange rates, assign table maintenance or table access authorizations and enter the relevant
Name of this migration object: S4_FI_EXCHANGE_RATE_V2
BAPI_EXCHRATE_CREATEMULTIPLE Insert One or More Exchange Rates in SAP Tables
Virtual Tables
AT_FACTORS : To create structures for the migration BAPI
Post-Processing
Not relevant
Maintain OC41
Further Information
1.44 FI - G/L account

Purpose
This migration object enables you to migrate G/L accounts and primary cost elements from the source ERP
This migration technique transfers data to the target system using Application Programming Interfaces (API).
Related Business Object: G/L Accounts
General Ledger Master Records G/L Accounts
Individual Processing Centrally
Component: FI
Business Object Definition A structure that records value movements in a company

code and represents the G/L account items in a chart of ac
counts. A G/L account has transaction figures that record
changes to the account during a posting period. These fig
ures are totals that are used for G/L reporting.
Available Scenarios
Selection Criteria
This migration object derives the charts of accounts from the company codes you specified when defining the
migration scope. This migration object automatically selects all G/L accounts from the SKA1 table for the
derived charts of accounts.
 Note
The selected G/L accounts should be present in the SKB1 table for the specified company codes.
In Scope
● Standard G/L account types

● Company code views
● Chart of accounts views
● Types/descriptions
● Control data
● Create/bank/interest data
● Keyword/translation data
● G/L accounts present in a Chart of Accounts view

Out of Scope
● Blocked G/L accounts

● Custom G/L account types
Prerequisites
● Languages assigned to the charts of accounts in the source and target systems must match.
● If a group chart of accounts is active, all group accounts are maintained or migrated.
● If an alternate group account is active, all alternate accounts are maintained or migrated.
● P/L statement account types
● Company IDs of trading partners
● House banks
You have migrated or defined settings in the FI - House bank migration object.
Source System
Not relevant
Target System
F_SKA1_BUK (G/L Account: Authorization for Company Codes)
F_FICB_FKR (Cash Budget Management/Funds Management FM Area)
F_SKA1_BES (G/L Account: Account Authorization)
F_SKA1_KTP (G/L Account: Authorization for Charts of Accounts)
F_SKA1_AEN (G/L Account: Change Authorization for Certain Fields)
Name of this migration object: S4_FI_GL_ACCOUNT_MASTER

GL_ACCT_MASTER_SAVE G/L account master: Check and save
Post-Processing
Not relevant
Create FS00
Change FS00
Display FS00
Further Information
1.45 FI - G/L account balance (classic G/L)
Purpose
This migration object enables you to migrate G/L account balance data (for the current fiscal year) from the
Related Business Object: G/L Account Balance

General Ledger Account Display Balances (New)
Component: FI
Business Object Definition 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 balances:
● Credit balance (the credit side of the account is greater)

● Debit balance (the debit side of the account is greater)
Available Scenarios
Selection Criteria
This migration object automatically selects the following data for the company codes you specified when
defining the migration scope:
All G/L account balances from the GLT0 table belonging to non-open item managed accounts and profit & loss
accounts.
Additional selection criteria:
The following fields in the G/L account are set to space:
● Open-Item Managed (XOPVW)

● Account is Reconciliation Account (MITKZ)
● Clearing Specific to Ledger Groups (XLGCLR)
In Scope
● G/L account balances belonging to the general ledger 00 and additional currency ledgers assigned to the
specified company codes
● As-is values of any additional local currencies customized in the source system only if the same currencies
are defined in the target system for the company codes
 Note
If additional local currencies are assigned to company codes only in the target system, (and not in the
source system), the system calculates the values of the local currencies in the target system.

Out of Scope
External number ranges
Prerequisites
● Currency type and the currency key of the controlling area (assigned to the specified company codes)
match in the source and target systems
● Currency keys assigned to currency types belonging to different organizational units match in the source
and target systems
● You have created and activated the ACC_DOCUMENT BAdI implementation in the target system. Please see
SAP Note 2717381 for information about BAdI implementations.
Source System
Not relevant
Target System
Not relevant
Name of this migration object: S4_FI_GL_ACC_BALANCE_CLASSIC_GL
BAPI_ACC_DOCUMENT_POST: Mass Maintenance for Material Master Data
Virtual Tables
FLTR_TOTALS: To store cumulative account balance data

Post-Processing
Not relevant
Display FS10N
Further Information
1.46 FI - G/L account balance (new G/L)
Purpose
Component: FI


Available Scenarios
Selection Criteria
All G/L account balances from the FAGLFLEXT table belonging to non-open item managed accounts and profit
& loss accounts

In Scope
● G/L Account balances belonging to leading and non-leading ledgers that are assigned to the participating
company codes.
● As-is values of any additional local currencies that are customized in the source system only if the same
currencies are defined in the target system for company codes.
 Note
If additional local currencies are assigned to company codes only in the target system (and not in the
Out of Scope

Prerequisites
● The leading and non-leading ledgers assigned to the specified company codes match in both the source
and target systems.
and target systems
Source System
Not relevant
Target System
Not relevant
Name of this migration object: S4_FI_GL_ACC_BALANCE_NEW_GL
BAPI_ACC_DOCUMENT_POST Accounting Posting
Virtual Tables

Post-Processing
Not relevant
With the transaction codes shown below, you can change the view for the object. However, this code also has
some built-in validation capabilities that you can use for checks.
Display FAGLB03
Further Information
1.47 FI - G/L open item (classic G/L)
Purpose
This migration object enables you to migrate G/L open item data from the source ERP system to the target
Related Business Object: General Ledger
General Ledger Posting
Component: FI

Business Object Definition G/L open item records contain the open items posted to an
open item managed account. Accounts that are managed on
an open item basis include:
● Bank clearing account

● Payroll clearing account
● Cash discount clearing account
● GR/IR clearing account
Available Scenarios
Selection Criteria
All G/L open items from the BSIS table are automatically selected for the company codes that you specified
In Scope
● Line items of open item managed accounts
 Note
Out of Scope
Tax lines
Prerequisites
● G/L account master data is available

● The tax category is removed from all the open item managed accounts
must match
● Exchange rate
● FI-AA Fixed asset - including balance
● PS - Network
● PS - Project
Source System
Not relevant
Target System
Not Relevant
Name of this migration object: S4_FI_GL_OI_CLASSIC_GL
BAPI_ACC_DOCUMENT_POST Accounting: Posting
Post-Processing
Assign the tax category in the master data for the open item managed account.


Create FB50
Change FB02
Display FB03
Further Information
1.48 FI - G/L open item (new G/L)
Purpose
Component: FI

Available Scenarios
Selection Criteria

when defining the migration scope
In Scope
● General ledger views from the FAGLFLEXA table

Note that the information give here is not exhaustive.
 Note
Out of Scope
● Tax lines
● Clearings specific to ledger groups
● Postings in non-leading ledgers (BKPF-BSTAT = "L") only
Prerequisites

must match

● Exchange rate
● PS - Network
● PS - Project
Source System
Not relevant
Target System
Not Relevant
Name of this migration object: S4_FI_GL_OI_NEW_GL
Post-Processing

Create FB50
Change FB02

Display FB03
Further Information
1.49 FI - Accounts payable open item (classic G/L)
Purpose
This migration object enables you to migrate accounts payable open items from the source ERP system to the
Related Business Object: Accounts Payable
Accounts Payable
Component: FI
Business Object Definition Accounts payable are liabilities currently owed by a person
or business. The Accounts Payable application component
records and administers accounting data for all vendors. Ac
counts payable open items are those items that are yet to be
cleared.
Available Scenarios
Selection Criteria
All accounts payable open items from the BSIK table are automatically selected for the company codes that

In Scope
● Accounts payable open items

 Note
source system), the system calculates the values of the local currencies in the target system..
Out of Scope
● Tax lines
● Vendor noted items
● Down payment requests
Prerequisites
● G/L account to post offsetting lines

● Tax category is removed from the master data for the vendor reconciliation account
● Currency keys related to currency types belonging to different organizational units match in the source and
target systems
● Exchange rate
● Fixed asset (including balance)
● FI - House bank

● Material
● Vendor
Source System
Not relevant
Target System
Not relevant
Name of this migration object: S4_FI_AP_OI_CLASSIC_GL
Post-Processing
Assign the tax category in the master data for the vendor reconciliation account.

Create FB01
Change FB02
Display FB03
Further Information

1.50 FI - Accounts payable open item (new G/L)
Purpose
Accounts Payable
Component: FI
cleared.
Available Scenarios
Selection Criteria
In Scope

● General ledger views generated using the FAGLFLEXA table

 Note
 Note
Document splitting is available if you have ensured that document splitting is active for the specified
company codes in both source and target systems.
Out of Scope
● Tax lines
● Customerspecific split characteristics
Prerequisites

target systems

● Vendor
● Exchange rate
● FI - House bank

Source System
Not relevant
Target System
Not relevant
Name of this migration object: S4_FI_AP_OI_NEW_GL
Post-Processing
Create FB01
Change FB02
Display FB03
Further Information

1.51 FI - Accounts receivable open item (classic GL)
Purpose
This migration object enables you to migrate accounts receivable open items from the source ERP system to
(BAPIs).
Related Business Object: Accounts Receivable
Accounts Receivable
Component: FI
Business Object Definition Open items are items that are not yet cleared.
The Accounts Receivable application component records

and administers accounting data for all customers. Accounts
Receivable open items, are also known as Customer open
items.
Available Scenarios
Selection Criteria
All accounts receivable open items from the BSID table are automatically selected for the company codes that
In Scope
● Accounts receivable open items


 Note
Out of Scope
● Tax lines
● Customer noted items
● SEPA mandate details such as validity and administrative data
 Note
If multiple mandates are assigned to a single line item, only the latest mandate is migrated.
Prerequisites

● Tax category is removed from the master data for the customer reconciliation account
target systems
● Customer
● Exchange rate
● FI - House bank
● FI - SEPA mandate

● Product
● SD - Sales contract
Source System
Not relevant
Target System
Not relevant
Name of this migration object: S4_FI_AR_OI_CLASSIC_GL
Virtual Tables
SEPA: To store information for one-time SEPA mandates
Post-Processing
Assign the tax category in the master data for the customer reconciliation account.
Create FB01
Change FB02
Display FB03

Further Information
1.52 FI - Accounts receivable open item (new G/L)
Purpose
(BAPIs).
Accounts Receivable
Component: FI

items.
Available Scenarios
Selection Criteria
All accounts payable open items from the BSID table are automatically selected for the company codes that

In Scope

 Note
Out of Scope
● Tax lines
 Note
Prerequisites

target systems

● Exchange rate
● FI - House bank
● Product
Source System
Not relevant
Target System
Not relevant
Name of this migration object: S4_FI_AR_OI_NEW_GL
Virtual Tables
SEPA: To store data related to one-time mandates
Post-Processing


Create FB01
Change FB02
Display FB03
Further Information
1.53 FI - Bank account
Purpose
This migration object enables you to migrate bank account data from the source ERP system to the target S/
Related Business Object: House Bank Account
Banks Master Data House Bank and House Bank
Accounts
Component: FI
Business Object Definition An internal representation of a company's bank account at a

house bank. It contains all control information required for
processing payment relevant processing.
Available Scenarios
Selection Criteria
All house bank accounts from the T012K table are automatically selected for the company codes you specified

In Scope
● Master data for bank accounts

● Descriptions in master data for bank accounts
● Currencies in master data for bank accounts
● Bank records
● Linkages between bank accounts and house bank accounts
Out of Scope
● Overdraft limits in the master data of bank accounts

● Signatories
● Simulation
Prerequisites
● FI - Bank
● FI - House bank
Source System
Not relevant
Target System
F_CLM_BAM (Authorization for Bank Account Management)
Name of this migration object: S4_CA_BANK_ACCOUNTS

BAPI_FCLM_BAM_AMD_BNKANT BAM Master Replication
Post-Processing
Not relevant
Create FI12_HBANK
Change FI12_HBANK
Display FI13_HBANK
Further Information
1.54 FI - House bank
Purpose
This migration object enables you to migrate the house bank data from the source ERP system to the target S/
Related Business Object: House Bank

Accounts
Component: FI
Business Object Definition A business partner that represents a bank through which
you can process your internal transactions.
Available Scenarios
Selection Criteria
All house banks from the T012 table are automatically selected for the company codes that you specified when
In Scope
● Transfer structure object T012: House Bank

● Foreign payment transactions
● Data medium exchange (DME) parameters
Out of Scope
● Bank record structures

● Simulation
Prerequisites
You have migrated or defined settings in the FI - Bank migration object.

Source System
Not relevant
Target System
F_BNKA_BUK (Banks: Authorization for Company Codes)
Name of this migration object: S4_CA_HOUSE_BANK
BAPI_HOUSE_BANK_REPLICATE House Bank and House Bank Account Replicate
Post-Processing
Not relevant
Create FI12_HBANK
Change FI12_HBANK
Display FI13_HBANK
Further Information

1.55 FI - Ledger group-specific open item
Purpose
This migration object enables you to migrate open item data specific to ledger groups from the source ERP
Interfaces (BAPIs).
Related Business Object:General Ledger
Component: FI
Business Object Definition You can use the function for all items that, due to parallel ac
counting, are posted to multiple ledgers and valuated differ
ently in those ledgers, in particular for provisions (such as
provisions for commission or process risks, or provisions for
creating and checking year-end closing).
Available Scenarios
Selection Criteria
All ledger groupspecific postings from the FAGLBSIS table are automatically selected for the company codes
that you specified when defining the migration scope.
In Scope
● Ledger groupspecific postings

● General ledger views
● Header data

 Note
Out of Scope
Tax lines
Prerequisites

must match
 Note
Before migration, create and activate the ACC_DOCUMENT BAdI implementation in the target system. For
more information, see SAP Note 2717381 .
● Exchange rate
● PS - Network
● PS - Project

Source System
Not relevant
Target System
Not relevant
Name of this migration object: S4_FI_GL_OI_LEDGER_SPEC_NEW_GL
Virtual Tables
● LEDGER: To retrieve the entry views of the document.

● FAGL_REP_LED: To retrieve the data of the representative ledger.
Post-Processing
Deactivate the BAdI implementation after migration and before posting any new documents in the target
system.
Create FB50L
Change FB02
Display FB03

Further Information
1.56 FI - SEPA Mandate
Purpose
This migration object enables you to migrate SEPA mandate data from the source ERP system to the target
Related Business Object: SEPA Mandate
Accounts Receivable Master Records SEPA
Mandates
Component: FI
Business Object Definition Payers use SEPA mandates to grant their vendors or service
agents the authorization to debit their account with the ap
propriate payment amount as part of a SEPA direct debit.
Available Scenarios
Selection Criteria
All SEPA mandates from the SEPA_MANDATE table belonging to Financial Accounting are automatically
selected for the company codes that you specified when defining the migration scope.
● ANWND is set to F (Financial Accounting)

● MVERS is set to 0 (Current version)
● SND_TYPE is set to BUS3007 (Customer payer ID)
● REF_ID is set to space (Blank contract ID)

 Note
For the selection criteria listed above, the company codes are stored in the Recipient ID field of the
SEPA_MANDATE table.
In Scope
● Basic data
● Payer information
● Payment recipients
● Use data for SEPA mandates with the Active status
 Note
After migration, the system treats a SEPA mandate with blank use data as a new (first use) mandate.
During a payment run (F110), all related fields are updated for new mandates, thereby possibly increasing
the processing time of payment instructions. To avoid an increase in processing time, this object migrates
use data for SEPA mandates with an active status from the source ERP system to the target SAP S/4HANA
system. During the migration, document numbers and dates remain unchanged. For the purpose of easy
identification, the ID number of the Payment Run of First Use field is migrated with the value CNV_MC_MIG.
Out of Scope
● Previous versions of SEPA mandates

● One-time SEPA mandates where the sender type (business object) is Accounting Document Line Item
(BSEG).
 Note
Validation of dependencies (such as customer and bank data business objects) is not carried out during
migration of SEPA mandate data for these statuses:
● Canceled
● Locked
● Obsolete
● Completed

Prerequisites
● Customer
● FI - Bank account
Before migration, check in the source ERP system if a SEPA mandate that is used in the payment details of an
FI-TRM transactions has any of the following statuses:
● Canceled
● Locked
● Obsolete
● Completed
If the statuses listed above are present, please change the status to "Entered" or "To Be Confirmed" for that
SEPA mandate in the SEPA Mandate Status mapping task.
Source System
Not relevant
Target System
F_SEPA_MDT (Authorization for Processing a Global SEPA Lock)
Name of this migration object: S4_FI_AR_SEPA_MANDATE
SEPA_MANDATES_API_MIG_CREATE Create Mandate (Migration Cockpit)
Virtual Tables
USE_SEPA_MANDATE: To process the SEPA mandate use data

Post-Processing
You can update use data manually using the FSEPA_M4 transaction code.

Create FSEPA_M1
Change FSEPA_M2
Display FSEPA_M3
Further Information
1.57 Fixed asset (including balance)
Purpose
This migration object enables you to migrate legacy data for fixed assets from the source ERP system to the
Related Business Object: Fixed Asset
Fixed Assets
Component: FI-AA
Business Object Type Master data and transactional data

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".
Available Scenarios
Selection Criteria
All fixed assets from the ANLA table, which do not have a deactivation date, are automatically selected for the
company codes you specified when defining the migration scope .
In Scope
● Asset classes with an internal number assignment

● Master details
● Inventory
● Posting information
● Time-dependent data
● Allocations
● Origin
● Account assignments for investment
● Net worth valuations
● Real estate and similar rights
● Depreciation areas
● Investment support keys
● Cumulative values
● Posted values
● Transactions
● Assets under Construction (AuC)
Time of Transfer
● If you transfer balances at the end of a fiscal year, this migration object transfers the accumulated
acquisition cost and the accumulated depreciation values.
● If you transfer balances during a fiscal year, this migration object transfers:
○ The accumulated acquisition cost
○ Accumulated depreciation values

○ Transactions dated from the beginning of the fiscal year until the transfer date
By default, the posted depreciation from the beginning of the fiscal year until the transfer date is
transferred.
Assets under Construction (AuC)
● AuC open items are transferred with the transaction type "900".
● Down payments for AuC are transferred with the transaction type "910".
● AuC line items and assigned documents are transferred to the target system.
● Credit memos with the transaction type "105" and containing negative values are migrated with the
transaction type "100". The BAPI does not accept negative values.
● The migration object posts cumulative values as transactions since cumulative values are not allowed for
AuC.
 Note
This migration object accumulates transaction values and transfers them as acquisition values with the
transaction type "100".
Out of Scope
● AuC that are 100% settled in the source system

● Down payments for AuC that are already cleared in the source system
● Insurance data
● Retirement data
● Investment measures
● Proportional values on transactions
● External number assignment for assets
 Note
If a depreciation is defined to take over acquisition values from other depreciation areas (Areas 15, 31, and
33, for example, take over values from Area 01 and 32), and you transfer the acquisition values, the system
ignores the acquisition values. For the depreciation areas 31 and 33, the system derives the values from the
leading depreciation area (01, 32). Therefore, you do not need to transfer cumulative values for these
depreciation areas.
Prerequisites
Source System
system:
● You have completed the Balance Carry Forward process using the FAGLGVTR transaction.
● You have closed the previous fiscal year in Asset Accounting.

Target System
● You have made the settings for the relevant depreciation areas. These settings determine the type of data
migrated from the source system. The migration is successful only if the values are compatible with the
depreciation area settings. Depreciation area Customizing should match in the sender and target systems.
● You have defined the offsetting account for legacy data transfer (asset balance sheet account) for Asset
Accounting in the Define Offsetting Account for Legacy Data Transfer activity.
● You have specified the transfer date, the document type, and the legacy data transfer status.
● If you want to do a year-end migration, you have set the Transfer Year Information mapping task to the
value "X". , If you want to do a mid-year migration, you have set the value in the mapping task as blank.
● You have set the transfer date in the target system as the last day of the month. For example, if you want to
set the transfer date in the month of November 2021, you need to set the date to November 30, 2021.
● You have ensured that the transfer date is the end date of the period.
 Example
If you set the transfer date to September 22, 2018 (22.09.2018) on the Legacy Data Transfer tab, set
the end date to September 30, 2018 (30.09.2018). If you enter any other date as the end date, the
system displays a warning during simulation and migration.
● PS - Project
● Supplier
Source System
Not relevant
Target System
A_A_VIEW (Asset: View)
A_S_ANLKL (Asset Master Data Maint: Company Code/Asset Class)
A_S_KOSTL (Asset Master Record Maintenance: Company Code/Cost Center)
A_S_GSBER (Asset Master Data Maintenance: Company Code/Business Area)

Name of this migration object: S4_FI_AA
BAPI_FIXEDASSET_OVRTAKE_CREATE BAPI for Legacy Data Transfer
Virtual Tables
● CUMULATEDVALUES: To store cumulative values

● POSTEDVALUES: To store posted values
● TRANSACTIONS: To store transactions values
Post-Processing
To ensure that the legacy data transfer is carried out completely, reconcile the data in the target system with
the data in your source system. Ensure that you reconcile the legacy data transfer and the corresponding lists
for documentation purposes before you release the SAP system to run operations in Asset Accounting.
Display AS03
Further Information
For more information about how to reconcile data, see SAP Note 2304473 .
For more information about Balance Carry Forward, see SAP Note 2427888 .
For more information about legacy data transfer in SAP_FIN 720 and relevant releases, see SAP Note 2208321
.

1.58 TRM - Condition detail
Purpose
This migration object enables you to migrate condition data for a TRM transaction from the source ERP system
Related Business Object: Deposit at Notice, Interest Rate Swap, Cap/Floor
Transaction Manager Derivatives Trading Edit
Business Object Definition A condition is a contractually agreed element of a financial

transaction or financial instrument. It describes the struc
ture of the transaction in terms of the period and amount
(interest, repayment, and so on).
Available Scenarios
Selection Criteria
Relevant conditions are automatically selected from the VTBFINKO table for the company codes you specified
Selection criteria for conditions:
● Conditions for product categories "610", "620", and "520"

● Contracts for product category "520" with these active activity categories: "Contract" ,"Settlement",
"Rollover", "Rollover Settlement"
● Contracts for product categories "610" and "620"with these active activity categories : "Contract" or
"Settlement"
In Scope
● Creation of new conditions

● Modification of existing conditions

Out of Scope
Not relevant
Prerequisites
must match
● Factory calendars relevant for Treasury
● Cash flow calculation set to "Parallel Condition" under product types for premium conditions
● TRM - Cap/Floor
● TRM - Deposit at notice
● TRM - Interest rate swap
Source System
Target System

Name of this migration object: S4_FI_TRM_CONDITION_DETAIL
CNV_OT_APPL_FI_TRM_COND_DETAIL: Update BAPI for TRM condition details
Virtual Tables
● FLTR_COND_DATA: To store condition details

● SINGLE_DATES: To store single dates for the conditions
● FORMULAVARIABLES: To store formula variables for the conditions
Post-Processing
Not relevant
Create FTR_EDIT
Change FTR_EDIT
Display FTR_EDIT
Further Information
1.59 TRM - Facility

Purpose
This migration object enables you to migrate bilateral facility data from the source ERP system to the target
Related Business Object: Facility
Transaction Manager Money market Trading Create
Business Object Definition Facilities are agreements between a lender and a borrower,
which control the general conditions for a series of drawings
against a credit line. The lender can give drawing authoriza
tion to several people (= borrowers), who are entitled to
draw varying amounts at any time up to the total approved
credit line. The utilization of this credit option for a facility is
called a drawing.
Available Scenarios
Selection Criteria
Bilateral facility transactions with the active activity categories Contract and Settlement are relevant for
migration. The relevant transactions from the VTBFHA table are automatically selected for the company codes
 Note
This object is relevant to the creation of a facility transaction. This migration object must be migrated
before you can assign any other money market transactions to this facility.
In Scope
● Structures
● Profiles
● Rules

● Other flows
● Payment details
Out of Scope
● Charges data
● Syndicated facility data
● Trade repository data
 Note
You can simulate only the Create a facility transaction feature.
The settlement of the facility transaction is out of scope for simulation
Prerequisites
must match
● FI - House bank
 Note
Before migration, ensure that for each rule category on the Rules tab, each value in the source system has a
unique and corresponding value in the target system.

Source System
Not relevant
Target System
Name of this migration object: S4_FI_TRM_FACILITY
BAPI_FTR_FAC_DEALCREATE Completely Create a Facility Transaction
Virtual Tables
● VTB_RULESET_ALL: To store the All indicator information for a rule category in the Facility transaction.
● VTB_RULESET_TAB: To store details of the Rules tab in the Facility transaction.
● VTB_ASGN_LIMIT_TAB: To store the credit limit values for the Facility transaction.
Post-Processing
and select the Flag Flows as Posted check box. This transaction enables the generation of posting logs. In the FI

such as quantity data (for example, units, nominal amounts), purchase value, cost or accrued interest to the

Create FTR_CREATE
Change FTR_EDIT
Display FTR_EDIT
Further Information
1.60 TRM - Fixed term deposit
Purpose
This migration object enables you to migrate fixed term deposit data from the source ERP system to the target
Related Business Object: Fixed Term Deposit
Business Object Component/Area User Menu Path: Accounting Treasury Treasury
Management Money Market Trading Fixed Term
Deposit

Business Object Definition An amount of money invested or borrowed at a fixed rate for
an agreed term, which is defined when the transaction is
concluded.
Available Scenarios
Selection Criteria
Fixed term deposits with the active activity categories Contract and Settlement are relevant for migration .The
relevant fixed term deposits data from the VTBFHA table is automatically selected for the company codes that
In Scope
● Structure data
● Contracts
● Contract settlements
● Other flows
● Payment details
● Cash flows
Out of Scope
● Concluded transactions
● Offer transactions
● Replaced transactions
● Simulation transactions
Prerequisites

Before you can start the migration process, for example, carry out the following Customizing in the target
system:
1. Create business partners, assign the corresponding roles to these partners, and define authorizations for
relevant transactions.
2. Set the standing instructions (correspondence and payment details) and release the business partner.
3. Define the product type.
 Note
If you don't want to use one of the standard product types delivered with the systems, you can define
your own product types.
You create financial transactions and manage positions based on product types. A fixedterm deposit is
an example of a product type in the Money Market area.
4. Define the transaction type
 Note
Transaction types determine the type of transactions that can be concluded with a particular product
type. Transaction types also control the transaction and position management process. An example of
this is an investment or the borrowing of fixedterm deposits.
5. Define the flow type. Flow types describe the changes to the cash flows.
6. Assign flow types to transaction types.
7. Define the condition type. This setting controls the structural characteristics that are displayed when you
create transactions. Example: Nominal Interest
You have also defined these settings in the target system:
● Relevant SEPA mandate IDs (if in use)

● House banks
● Master agreements
Source System
Target System

T_POSS_ASS (Assign Attributes to Positions)
Name of this migration object: S4_FI_TRM_FIXED_TERM_DEPOSIT
BAPI_FTR_FTD_DEALCREATE Create Fixed Term Deposit
BAPI_FTR_SETTLE Settle Financial Transaction
Virtual Tables
● IRATEFTD: To store information about interest rate data

● CONDITIONS: To store information about conditions data
● SINGLEDATE: To store information about single date data
Post-Processing
before the migration process. Please note that the information related to flows is already included in the
balance sheet, which was migrated from the source system to the SAP S/4 HANA system. If you post these
flows again in the receiver system, the migration tool updates the general ledger twice. This means that the
corresponding financial transaction, which was created in the receiver system during migration, needs to be
excluded from further processing of flows.
and select the Flag Flows as Posted checkbox. This transaction enables the generation of posting logs. In the FI

Create TM01
Change TM02
Display TM03
Further Information
1.61 TRM - FX option
Purpose
This migration object enables you to migrate FX option (foreign exchange option) data from the source ERP
Interfaces (BAPIs).
Related Business Object: Foreign Exchange Option
Transaction Manager Foreign Exchange Trading Forex
Fast Entry
Business Object Definition The FX option is an option on an FX transaction and is used

as protection from currency fluctuations. The purchaser of a
standard FX option has the right to buy a fixed amount of
currency on the exercise date at a previously agreed rate.
Available Scenarios

Selection Criteria
FX option contracts with the active activity categories Contract and Settlement are relevant for migration. The
relevant FX option contract data from the VTBFHA table is automatically selected for the company codes you
specified when defining the migration scope
In Scope
● Structure data
● Underlying data
● Other flows
● Payment details
● Contracts converted from Order to Contract
Out of Scope
● Orders
● Fixing
● Knock-in, Knock-out transactions
 Note
You can simulate only the Create an FX option transaction feature.
The settlement feature for the FX option transaction is out of scope for simulation:
Prerequisites
must match
source and target system

● FI - House bank
● TRM - Business partner role
Source System
Not relevant
Target System
Name of this migration object: S4_FI_TRM_FX_OPTIONS
BAPI_FTR_FXOPTIONS_DEALCREATE Create Currency Option Deal
Virtual Tables
● FOREX: To store details of the fields in the Forex structure.

● GENERALCONTRACTDATA: To store details of the fields in the General Contract Data structure.

Post-Processing
such as quantity data (for example, units, nominal amounts), purchase value, cost, and accrued interest to the
Create FTR_CREATE, TI4A
Change FTR_EDIT
Display FTR_EDIT
Further Information
1.62 TRM - Foreign exchange collar contract

Purpose
This migration object enables you to migrate foreign exchange collar contract data from the source ERP
Interfaces (BAPIs).
Related Business Object: Foreign Exchange Collar Contract
Transaction Manager Foreign Exchange Trading
Currency Option Entry - Spread
Component: FIN-FSCM-TRM
Business Object Definition A collar FX option involves the purchase of a call option and
the sale of a put option, or vice versa.
Available Scenarios
Selection Criteria
FX collar contracts with the active activity categories Contract and Settlement are relevant for migration. The
relevant FX collar contract data from the VTBFHA table is automatically selected for the company codes you
In Scope
● Structure data
● Underlying data
● Contracts
 Note
Contracts with the status Terminate, Give Notice, Exercise, or Expiration are not migrated.

 Note
This migration object only migrates foreign exchange collar contracts and does not migrate payment
details or additional flows. Hence, migrate this object before you migrate the TRM - Additional flow and
TRM - Payment detail objects.
Out of Scope
● Order transactions
● Fixing transactions
● Default risk limit data
● Knock-in, Knock-out transactions
Prerequisites
must match
● Cash flows until the migration cutoff date need to be posted to Financial Accounting
● FI - House bank
Source System

Not relevant
Target System
● F_T_TRANSB (Treasury: Transaction Authorization)

● B_BUP_PCPT (Business Partner: Purpose Completed)
● B_BUPA_GRP (Business Partner: Authorization Groups)
● B_BUPA_PGM (Grouping Characteristic for SAP BP-FS)
● T_DEAL_PD (Authorization for Product/Transaction Types)
● T_POS_ASS (Assign Attributes to Positions)
Name of this migration object: S4_FI_TRM_FX_COLLAR_CONTRACT
● BAPI_FTR_CREATE_FXCOLLAR: Create Currency Option

● BAPI_FTR_SETTLE: Settle Financial Transaction
Virtual Tables
● FOREX: To store amount data of mirror transactions, which is a part of the FX collar contract.
● GENERALCONTRACTDATA: To store contract data of mirror transactions, which is a part of the FX collar
contract.
Post-Processing
and select the Flag Flows as Posted checkbox. This transaction enables the generation of posting logs. You can
see the accounts in the FI area to which postings need to be made to reconcile the data. This information is


Create TI4B
Change FTR_EDIT
Display FTR_EDIT
Further Information
1.63 TRM - Foreign exchange swap contract
Purpose
This migration object enables you to migrate foreign exchange swap contract data from the source ERP system
(BAPIs)
Related Business Object: Foreign Exchange Swap Contract
Transaction Manager Foreign Exchange Trading
Create Forex Swap

Business Object Definition The combination of a spot transaction and a forward trans
action in the opposite direction (that is, where a currency is
sold spot and purchased forward simultaneously).
The currency amount sold in the spot transaction is repurch

ased when the forward transaction matures. Two currencies
are swapped at a price previously agreed for the period be
tween the settlement dates of the two transactions. The rate
of the forward transaction is based on the rate of the spot
transaction and the swap rate for the interval between the
two settlement dates.
Available Scenarios
Selection Criteria
Foreign exchange swap contracts with the active activity categories Contract and Settlement are relevant for
migration. The relevant foreign exchange swap contract data from the VTBFHA table is automatically selected
for the company codes you specified when defining the migration scope.
In Scope
● Structure data
● Administrative data
● Contracts
 Note
Transactions with the Rollover, Premature Settlement, or Expiration statuses are not migrated.
 Note
This migration object only migrates forex swap contracts and does not migrate payment details or
additional flows. Hence, migrate this object before you migrate the TRM - Additional flow and TRM -
Payment detail objects.

Out of Scope
● Orders
● Fixing data
● FX hedge management data
● Default risk limits
Prerequisites
must match
● Relevant securities accounts
Source System
Not relevant
Target System

● T_POS_ASS (Assign Attributes to Positions)

Name of this migration object: S4_FI_TRM_FX_SWAP_CONTRACT
BAPI_FTR_FXT_CREATESWAP Create a Foreign Currency Swap
Virtual Tables
AT_VTBFHA: To store swap transaction data
Note that virtual tables do not exist in the database..
Post-Processing
processing of flows..

Create TX10
Change FTR_EDIT

Display FTR_EDIT
Further Information
1.64 TRM - Investment certificate
Purpose
This migration object enables you to migrate investment certificate contract data from the source ERP system
(BAPIs).
Related Business Object: Investment Certificate
Transaction Manager Securities Trading Create
Business Object Definition An investment certificate is a share in a fund, which is man

aged by an investment trust. The owner of the share gets
dividends but does not have other rights.
Some investment funds communicate and pay their divi

dends in a monthly or yearly rhythm and others communi
cate their dividends, for example, per day (=accrued divi
dend) but pay monthly the sum of the accrued dividends
(=accumulated dividend).
Available Scenarios

Selection Criteria
Investment certificate contracts with the active activity categories Contract and Settlement are relevant for
migration. The relevant investment certificate contract data from the VTBFHA table is automatically selected
for the company codes you specified when defining the migration scope.
In Scope
● Structure data
● Trading data
● Other flows
● Payment details
Out of Scope

 Note
Cash flows generated from corporate actions, security account transfers, security rights, or any other back
office actions are not migrated to the target system. You need to manually update this information in the
target system after migration.
Prerequisites
must match
the source and target systems
● Valuation areas for specified company codes and initialization of parallel valuation areas
● Product types, flow types, and update types


● TRM - Security class
● FI - House bank
Source System
Not relevant
Target System

● B_BUPA_RLT (Business Partner: BP Roles)
● T_DEAL_DP (Authorization for Securities Account)
● T_DEAL_PF (Portfolio Authorization)
● T_DEAL_AG (Authorization for an Authorization Group)
Name of this migration object: S4_FI_TRM_INVESTMENT_CERTIFICATE
● BAPI_FTR_SECURITY_DEALCREATE : Completely Create a Security Transaction

● BAPI_FTR_SECURITY_SETTLE : Settle Financial Transaction
Post-Processing

Create TS01
Change TS02
Display TS03
Further Information
1.65 TRM - Letter of credit
Purpose
This migration object enables you to migrate letter of credit data from the source ERP system to the target SAP
Related Business Object: Letter of Credit

Transaction Manager Trade Finance Trading Create
Business Object Definition A letter issued by a bank to obtain payment for goods. When
a letter of credit is confirmed, the advising bank guarantees
payment only if all stipulations in the letter of credit are con
formed to exactly.
Available Scenarios
Selection Criteria
This migration object automatically selects all financial transaction data from the VTBFHA table .
In Scope
● Structure data
● Presentation data
● Other flows
● Payment details
● Contracts
Out of Scope
● Collateral data
● Cash flows
● Memos
● Partner assignment data
● Status information

Prerequisites
You have migrated or defined settings in the Profit center migration object.
Before you can start the migration process, for example, ensure the following Customizing in the target system.
Proceed as follows:
● Create business partners, assign the corresponding roles to these partners, and define authorizations for
the relevant transactions.
● Set the standing instructions (correspondence and payment details) and release the business partner.
● Define the product type.
 Note
If you don't want to use a standard product type delivered with the system, you can define your own
product types.
● Define the transaction type.
 Note
Transaction types determine the type of transactions that can be concluded with a particular product
type. Transaction types also control the transaction and position management process.
● Define the flow type. Flow types describe the changes to the cash flows.
● Assign flow types to transaction types.
● Define the condition type. This setting controls the structural characteristics that are displayed when you
create transactions.
You have additionally defined these settings in the target system:

● House banks
Source System


● T_DEAL_LC (Authorization for Letter of Credit)
FTR_LC_NUMBER (Letter of Credit Number)
Target System

Name of this migration object: S4_FI_TRM_LETTER_OF_CREDIT
BAPI_FTR_LC_DEALCREATE Create Letter of Credit Completely
Post-Processing
Not relevant
Create FTR_CREATE
Change FTR_CHANGE
Display FTR_DISPLAY

Further Information
1.66 TRM - Main flow detail
Purpose
This migration object enables you to migrate main flow data for a TRM transaction from the source ERP system
(BAPIs).
Related Business Objects: Bank Guarantee, Letter of Credit, Deposit at Notice
Transaction Manager Money Market Trading Edit
Business Object Definition Nominal amount increases or decreases in the term.
Available Scenarios
Selection Criteria
Relevant main flow information is automatically selected from the VTBFHAPO table for the company codes you
Selection criteria for main flow information:
● Main flows for product categories "850", "860", and "520"

● Contracts for product categories "850" and "860" with these active activity categories "850" and "860":
"Contract", "Settlement"
● Contracts for product category "520" with these active activity categories: "Contract", "Settlement",
● Areas of flow or conditions are "HPTA" or "NOMA"

In Scope
Creation of additional main flows
Out of Scope
Exclusive indicator
Month-end indicator
Prerequisites
● Flow types
must match
● TRM - Bank guarantee

● TRM - Letter of credit
Source System
Not relevant
Target System

Name of this migration object: S4_FI_TRM_MAINFLOW_DETAIL
BAPI_FTR_MAINFLOW_CREATE: Create Main Flow
Post-Processing
Not relevant

Create FTR_EDIT
Change FTR_EDIT
Display FTR_EDIT
Further Information
1.67 TRM - Interest rate swap
Purpose
This migration object enables you to migrate interest rate swap contract data from the source ERP system to
(BAPIs).

Related Business Object: Interest Rate Swap
Transaction Manager Derivatives Trading Create
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 on the basis of different interest rates.
Available Scenarios
Selection Criteria
Interest rate swap contracts with the active activity categories Contract and Settlement are relevant for
migration. The relevant interest rate swap contracts from the VTBFHA table are automatically selected for the
company codes you specified when defining the migration scope.
In Scope
● Structure data
● Additional main flows
 Note
To migrate the complete interest rate swap contract data, ensure that these migration objects are defined
in the same project:
● TRM - Additional flow

● TRM - Condition detail
● TRM - Payment detail

Out of Scope
● Terminated transactions
● Order activities
● Default Risk limit
● Exclusive indicator and month-end indicator in main flow
 Note
If you have multiple steps for migration, you can simulate only the contract data feature.
● Main flow
● Settlement
 Note
Prerequisites
must match.
● House banks
● Business Partner

Source System
Target System
B_BUPR_BZT (Business Partner Relationships: Relationship Categories)
Name of this migration object: S4_FI_TRM_INT_RATE_SWAP
● BAPI_FTR_SWAP_CREATE: Create an OTC Interest Rate Derivative Swap

● BAPI_FTR_SETTLE: Settle Financial Transaction
Name of the API or APIs used in this migration object
CNV_OT_APPL_FI_TRM_MF_IRS: Update BAPI for TRM Mainflow Details (Interest Rate Swap)
Virtual Tables
OTCINTRATESWAP: To store the details of the interest rate swap structure.

Post-Processing
With the help of this migration object, you have migrated valuation-area-independent data such as quantity
data (for example, units, nominal amounts), purchase value, cost, or accrued interest to the target system. To
migrate valuation area-dependent data for SAP TRM, use the Legacy Data Transfer tool.
Create FTR_CREATE
Change FTR_EDIT
Display FTR_EDIT
Further Information
1.68 TRM - Payment detail
Purpose
This migration object enables you to migrate payment detail for a TRM transaction from the source ERP
Interfaces (BAPIs).
Related Business Object: Cap/Floor, Commercial Paper, Deposit at Notice, Interest Rate Swap, Foreign
Exchange Swap Contract, Foreign Exchange Collar Contract

Transaction Manager Money Market Trading Edit
Business Object Definition Data that is required for making transactions with your busi
ness partner.
Available Scenarios
Selection Criteria
Relevant payment details are automatically selected from the VTBZV table for the company codes you
Selection criteria for payment details:
● Payment details for product category "520", "530", "600","610", "620", and "760"
● Contracts for product categories "530", "600", "610", "620", and "760" with these active activity
categories: "Contract", "Settlement"
● Contracts for product category "520" with these active activity categories: "Contract", "Settlement",
In Scope
Payment details under Create
Out of Scope
Not relevant
Prerequisites

must match
● House banks
● FI - House bank
● TRM - Cap/Floor
● TRM - Commercial paper
● TRM - Interest rate swap
● TRM - Foreign exchange swap contract
● TRM - Foreign exchange collar contract
Source System
Not relevant
Target System
Name of this migration object: S4_FI_TRM_PAYMENT_DETAILS
BAPI_FTR_PAYDET_CREATE: Create Payment Details

Virtual Tables
FLTR_PAY_DATA: To store payment details
Post-Processing
Not relevant
Create FTR_EDIT
Change FTR_EDIT
Display FTR_EDIT
Further Information
1.69 JVA - Cost center suspense
Purpose
This migration object enables you to migrate cost center suspense data from the source ERP system to the
Related Business Object: Cost Center Suspense

Master Data Suspense Suspense Cost Center
Component: CA-JVA
Business Object Definition If a partner, or equity group, or cost object is suspended,

cutback 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.
Available Scenarios
Selection Criteria
All cost center suspense records from the T8J_SUS_CC table are automatically selected for the company
codes you specified when defining the migration scope.
In Scope
● Suspense cost center data

● Unsuspense cost center data

Out of Scope
Not relevant
Prerequisites
● Joint Venture Accounting is active in the target client

● Joint Venture is active for the relevant company code and cost center
● Joint venture and cost center master data is maintained or migrated
You have migrated or defined settings in the CO - Cost center migration object:
Source System
Not relevant
Target System
To migrate cost center suspense data, assign table maintenance or table access authorizations and enter the
relevant values for the migration user.
Name of this migration object: S4_JVA_COST_CENTER_SUSPENSE
DMC_MIG_JVA_COST_CENTER_SUSP: Cost Center Suspense
Post-Processing
Not relevant

Create GJ_SUS_CC
Change GJ_SUS_CC
Display GJ_SUS_CC_DISP
Further Information
1.70 JVA - Order suspense
Purpose
This migration object enables you to migrate order suspense data from the source ERP system to the target
Related Business Object: Order Suspense
Master Data Suspense Suspense Order
Component: CA-JVA

Business Object Definition If a partner, equity group, or cost object is suspended, cut
back postings are not executed. When you remove the
Available Scenarios
Selection Criteria
All order suspense records from the T8J_SUS_ORD table are automatically selected for the company codes you
In Scope
● Suspense order data

● Unsuspense order data
Out of Scope
Not relevant
Prerequisites

● Joint Venture is active for the relevant company codes
● Internal order transactional data is maintained or migrated
You have migrated or defined settings in the CO - Internal order migration object.

Source System
Not relevant
Target System
To carry out the migration, assign table maintenance or table access authorizations and enter relevant values
for the migration user.
Name of this migration object: S4_JVA_ORDER_SUSPENSE
DMC_MIG_JVA_ORDER_SUSPENSE : Joint Venture Order Suspense Master
Post-Processing
Not relevant
Create GJ_SUS_ORD
Change GJ_SUS_ORD
Display GJ_SUS_ORD_DISP
Further Information

1.71 JVA - Joint operating agreement (step 1)
Purpose
This migration object enables you to migrate joint operating agreement data from the source ERP system to
Related Business Object: Joint Operating Agreement
Master Data Joint Operating Agreement
Component: CA-JVA
Business Object Definition A joint operating agreement contains the contractual agree
ments between joint venture partners. Joint venture and
equity groups are linked with each other via the equity type
and assigned within a joint operating agreement..
Available Scenarios
Selection Criteria
All joint operating agreements from the T8JU table are automatically selected for the company codes you
In Scope
● Joint operating agreements

● Descriptions for joint operating agreements
● Equity groups at the JOA level
● Partners at the JOA level
● Producing statistical ratio assignments
● Producing statistical ratio thresholds
● Drilling statistical ratios

● Overhead burden rate percentages
● Recovery percentages for penalty categories
Out of Scope
● Overhead offsets for cost centers

● Stepped rate overheads
Prerequisites

● Number ranges
● Joint Operating Agreement matches the Customizing in the source system
● JVA - Joint venture partner

● CO - Statistical key figure
Source System
Not relevant
Target System
J_JVA_JOA (Joint Venture Accounting: Joint Operating Agreement Master)
Name of this migration object: S4_JVA_JOINT_OPERATING_AGREEMENT

DMC_MIG_JVA_JOA Joint Operating Agreement Migration
Post-Processing
Not relevant
Create GJA1
Change GJA2
Display GJA3
Further Information
1.72 JVA - Joint venture partner
Purpose
This migration object enables you to migrate joint venture partner data from the source ERP system to the
Related Business Object: JV Partners

Master Data Business Partners JV Partners
Component: CA-JVA
Business Object Definition 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.
Available Scenarios
Selection Criteria
All JV partners from the T8JO table are automatically selected for the company codes you specified when
In Scope
JV partners
Out of Scope
Not relevant
Prerequisites
● Inter-company codes
● Joint Venture is active for the relevant company codes
● Customer master data is maintained or migrated
You have migrated or defined settings in the Customer migration object

Source System
Not relevant
Target System
J_JVA_PRC (Joint Venture Accounting: Processing)
Name of this migration object: S4_JVA_JOINT_VENTURE_PARTNER
DMC_MIG_JVA_PARTNER : JV Partner API
Post-Processing
Not relevant

Create GJ2B
Change GJ23
Display GJ2A
Further Information

1.73 JVA - Project suspense
Purpose
This migration object enables you to migrate project suspense data from the source ERP system to the target
Related Business Object: Project Suspense
Master Data Suspense Suspense Project
Component: CO-JVA

Suspense:

transferred to a suspense recovery indicator. The billable re
cutback.
Unsuspense:

Available Scenarios
Selection Criteria

All projects from the T8JP table are automatically selected for the company codes that you specified when
In Scope
● Suspense data
● Unsuspense data
Out of Scope
Not relevant
Prerequisites

● Joint Venture Accounting is active for relevant company codes and WBS elements
● Joint venture data and WBS element data is present in the system
You have migrated or defined settings in the PS - Project migration object.
Source System
Not relevant
Target System
To migrate project suspense data, assign table maintenance or table access authorizations and enter the
Name of this migration object: S4_JVA_PROJ_SUSPENSE

DMC_MIG_JVA_PROJECT_SUSPENSE Joint Venture Project Suspense Master
Post-Processing
Not relevant
Create GJ34
Change GJ34
Display GJ3A
Further Information
1.74 JVA - Venture suspense
Purpose
This migration object enables you to migrate venture suspense data in Joint Venture Accounting (JVA) from
the source ERP system to the target SAP S/4HANA system based on the default selection criteria set for the
Interfaces (BAPIs).
Related Business Object: Venture Suspense

Master Data Suspense Suspense Venture
Component: CA-JVA

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:

cutback.
Unsuspense:

Available Scenarios
Selection Criteria
All venture suspense records from the T8J_SUS_VENTURE table are automatically selected for the company
codes you specified when defining the migration scope.
In Scope
● Suspense venture data assigned to the specified company codes

● Unsuspense venture data assigned to the specified company codes

Out of Scope
Not relevant
Prerequisites

● Joint Venture is active for the relevant company codes and ventures
● Joint venture master data is maintained or migrated
JVA - Joint venture master (step 1)
Source System
Not relevant
Target System
To migrate venture suspense data, assign table maintenance or table access authorizations and enter the
Name of this migration object: S4_JVA_VENTURE_SUSPENSE
DMC_MIG_JVA_VENTURE_SUSPENSE Joint venture suspense master
Post-Processing
Not relevant

Change GJ_SUS_VE
Display GJ_SUS_VE_DISP
Further Information
1.75 MM - Material inventory balance
Purpose
This migration object enables you to migrate material inventory balance data from the source ERP system to
(BAPIs).
Related Business Object: Inventory
Business Object Component/Area User Menu Path: Logistics Materials Management
Inventory Management Goods Movement
Component: 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).
Available Scenarios
Selection Criteria

This migration object automatically selects all materials from the MARC table for the derived plants.
In Scope
● Material document header data

● Material document items
● Stock types:
○ Unrestricted use stock (" ")
○ Stock in quality inspection ("X")
○ Blocked stock ("S")
● Special stock indicators:
○ Parts provided to vendor ("O")
○ Customer consignment stock ("W")
○ Returnable transport packing stock to customer ("V")
○ Sales order stock ("E")
○ Project stock ("Q")
○ Vendor consignment stock ("K")
○ Returnable transport packing stock to vendor ("M")
 Note
● Material Valuation:: If materials have a standard price control indicator or a moving average price
control indicator, the system migrates stock values from the following tables:
○ Table MBEW - for material valuation
○ Table QBEW – for project stock
○ Table OBEW – for sales order stock
● Transaction or Event for Migration

○ GM_CODE = ‘05’ (Other Goods Receipts)
○ Movement type = '561' (Initial Entry of Stock Balances)
Out of Scope
● Userdefined fields
● Special stock indicators other than specified in the in-scope section
● Industry solutionspecific fields
● Serial numbers
● Transactions/events:
○ 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
● Material document EWM references
● Service parts for SPM
● Item data for Catch Weight Management
● Print control for material documents
● Stocks in transit
Prerequisites
● Batch unique at plant level

● Batch unique at material and client level
● Product
Depending on your scenario, you have also migrated or defined settings in the following migration objects:
● Supplier: Migrate the Supplier migration object if the special stocks are:
○ Vendor consignment (“K”)
○ Returnable transport packing stock to vendor ("M”)
○ Parts provided to the vendor (“O” )
● Customer: Migrate the Customer migration object if the special stocks are:
○ Customer consignment stock (“W”)
○ Returnable transport packing stock to customer ("V”)
● PS - Project: Migrate the PS - Project migration object if the special stock is project stock (“Q”).
● MM - Purchasing info record: Migrate the MM - Purchasing info record migration object for the
Consignment info category if the special stock is vendor consignment stock (“K”).
● SD - Sales order: Migrate the SD - Sales order migration object if the special stock is sales order stock
(“E”).
Source System
Not relevant
Target System
To carry out the migration, assign the following authorization objects or objects to the user:
M_MSEG_BWA (Goods Movements: Movement Type)

M_MSEG_WWA (Goods Movements: Plant)
M_MSEG_LGO (Goods Movements: Storage Location)
Name of this migration object: S4_MM_STOCK
BAPI_GOODSMVT_CREATE Post Goods Movements with MB_CREATE_GOODS_MOVEMENT
Virtual Tables
STKTAB : To store the inventory data for a material
System Actions
Batch-managed materials: If the target batch is set to blank in the batch mapping task, the system
automatically creates batches during migration. However, the new batch does not have other batch-relevant
information such as classification.
Posting date(YYYYMMDD) mapping tasks: The system picks up the posting date from the Posting
Date(YYYYMMDD) mapping task for all inventory postings.
Post-Processing
Not relevant
Stock Overview MMBE
List of Stock Values: Balances MB5L
Material Document List MB51

Further Information
1.76 MM - Material variant
Purpose
This migration object enables you to migrate material variant data from the source ERP system to the target
Related Business Object: Material Variant
Business Object Component/Area User Menu Path: Logistics General Material Master
Component: LO-VC
Business Object Definition A product variant of a configurable material. The material

master record of a material variant contains assigned char
acteristic values.
Available Scenarios
Selection Criteria
This migration object automatically selects:
● All plantspecific material variants from the MARC table for the derived plants AND
● All cross-plant material variants from the MARA table.
In Scope
● Cross-plant material variants

● Plantspecific material variants
 Note
Materials set for deletion in the source ERP system are not migrated.
Out of Scope
● Material variants with interval values

● Planning variant configuration
Prerequisites
● Characteristic
● Class
● General classification assignments
● Product
● VC - Configuration profile
Source System
Not relevant
Target System
To migrate, assign the following authorization object or objects to the user:
M_MATE_WRK (Material Master: Plants)
M_MATE_MAN (Material Master: Data at Client Level)

Name of this migration object: S4_MM_MATERIAL_VARIANT
VCH_MATERIAL_CONFIG_CREATE Creation of Configuration for Material Variants
Virtual Tables
● AS_MARA_MARC: To handle materials for material variants

● AS_MATVAR_CUCFG: To handle configuration data for material variants
● AS_MATVAR_CUINS: To handle instance data for material variants
● AS_MATVAR_CUVAL: To handle characteristic valuation data for material variants
Post-Processing
Not relevant

codes also have some built-int validation capabilities that you can use for checks.
Create MM01
Change MM02
Display MM03
Further Information
1.77 MM - Material commodity

Purpose
This migration object enables you to migrate material trade classification data containing commodity codes
from the source ERP system to the target SAP S/4HANA system based on the default selection criteria set for
the migration object. This migration technique transfers data to the target system using Business Application
Business Object Component/Area Component: LO-MD-MM
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/region and, depending on that, the numbering
scheme assigned to that country/region.
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.
Available Scenarios
Selection Criteria
This migration object derives the plant, purchasing organization and sales organization from the company
codes you specified when defining the migration scope. This migration object automatically selects all
materials from the MARC table for the derived plants.
In Scope
Classification with company code
 Note
Materials you set for deletion in the source ERP system are not migrated

Out of Scope
Not relevant
 Note
Prerequisites
● Commodity code numbering schemes are assigned to countries or regions

● Commodity codes are defined for relevant numbering schemes
You have migrated or defined settings in the Material migration object.
 Note
The Product migration object needs to be migrated along with forecast parameters to enable the
forecasting view.
Source System
Not relevant
Target System
ITM_CLS_NS (Trade Classification: Authorization for Numbering Scheme)
Name of this migration object: S4_MM_MATERIAL_COMMODITY
SAPSLL_COMCO_CLS_MIGR_BAPI Migrate Classification with Commodity Code

Post-Processing
Not relevant
Create MM01
Change MM02
Display MM03 Choose the International Trade Import tab page
Further Information
1.78 MM - Material consumption
Purpose
This migration object enables you to migrate material consumption data from the source ERP system to the
Business Object Component/Area Component: LO-MD-MM

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.
Available Scenarios
Selection Criteria
This migration object derives the plant, purchasing organization and sales organization from the company
codes you specified when defining the migration scope. This migration object automatically selects the
materials from the MARC table for the derived plants.
In Scope
● Forecast values
● Planned consumptions
● Unplanned consumptions
 Note
The Product migration object needs to be migrated with forecast parameters to enable the forecasting
view.
 Note
If the material you provided in the mapping already exists in the target system, it is overwritten with
material consumption data from the source system after migration.
Out of Scope
● Materials that are not enabled for forecasting views

● Overwriting of existing forecasting values
 Note
Overwriting leads to the system error: "Duplicate entries for parameter FORECASTVALUES"
 Note

Prerequisites
You have migrated or defined settings in the Material migration object:
 Note
The Material migration object needs to be migrated with forecast parameters to enable the forecasting
view.
Source System
Not relevant
Target System
ITM_CLS_NS (Trade Classification: Authorization for Numbering Scheme)
Name of this migration object: S4_MM_MATERIAL_CONSUMP
BAPI_MATERIAL_SAVEREPLICA Mass Maintenance for Material Master Data
Post-Processing
Not relevant


Create MM01
Change MM02
Display MM03
After migration, choose the Forecasting tab page. Choose Consumption Values or Forecast Values to see the
relevant information.
Further Information
1.79 MM - Purchase contract
Purpose
This migration object enables you to migrate purchase contract data from the source ERP system to the target
Related Business Object: Purchase Contract
Business Object Component/Area Component: MM-PUR (Outline Agreements)
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.
Available Scenarios
Selection Criteria
This migration object derives the purchasing organization from the company codes you specified when

This migration object automatically selects all purchase purchasing contract from the EKKO table for the
derived purchasing organizations and for the central purchasing organizations.
 Note
The relevant purchasing document category (BSTYP) for this migration object is K (Purchasing Contract).
In Scope
● Purchasing document header data

● Purchasing document item data
● Item condition validity data
● Item conditions
● Account assignment in purchasing document data
● Item condition scale value data
● Conditions (1-dimensional value scale) data
● Conditions (1-dimensional quantity scale) data
● Conditions header data
● Conditions item data
● Partner roles in purchasing data
● Delivery address data
● Vendor address data
● Item texts
● Header texts
● Plant addresses (default delivery address)
 Note
Ensure that you maintain the delivery address in the source document to enable migration of delivery
addresses.
If you maintain the delivery address as a reference address in the source document, you can map new
delivery addresses in the Number of Delivery Address mapping task.
Out of Scope
● Account profit segment data

● VAS items
● Extensions in
● Technical data

Prerequisites
● Product
● Project definition
● PS - Project
● Supplier
Source System
Not relevant
Target System
M_RAHM_BSA (Authorization check for Document Type in Outline Agreement )
M_RAHM_EKO (Authorization check for Purchasing Organization in Outline Agreement )
M_RAHM_EKG (Purchasing Group in Outline Agreement )
M_RAHM_WRK (Plant in Outline Agreement )
V_KOND_VEA (Maintain Condition: Auth. for Use/Appl./Cond.Type/Table )
V_KONH_VKS (Condition: Authorization for Condition Types )
Name of this migration object: S4_MM_PURCHASING_CONTRACT
BAPI_CONTRACT_CREATE BAPI to Create a Purchase Contract
Virtual Tables
● ITM_TXT: To handle item long texts

● HDR_TEXT : To handle header texts
● AS_KONH: To handle condition headers
● AS_KONP : To handle item conditions
● AS_KONM : To handle 1-dimensional quantity scale conditions
● AS_KONW : To handle 1-dimensional value scale conditions
● AS_EKPO : To handle purchasing contract items
● AS_ADRC : To handle Vendor address
Post-Processing
Not relevant
Create ME31K
Change ME32K
Display ME33K
Further Information
1.80 MM - Purchasing info record

Purpose
This migration object enables you to migrate purchasing info record data from the source ERP system to the
Related Business Object: Purchasing Info Record
Purchasing Master Data Info Record
Component: MM-PUR
Business Object Definition A source of information for the procurement of a certain ma
terial from a certain vendor.
Available Scenarios
Selection Criteria
This migration object automatically selects all purchase info records (except pipeline records) from the EINA
table for the derived plants.
In Scope
● Info record types

○ Standard
○ Consignment
○ Subcontracting
● General data
● Purchase organization data
● Conditions
● Texts
 Note
Condition records with expired valid-to dates in the source ERP system are not migrated.

Out of Scope
● Pipeline info record type

● Any document references such as quotations, purchase requisitions, purchase orders, and the last
purchase order number
● Conditions with expired validity periods
● Industryspecific fields
Prerequisites
● Product
● Supplier
Source System
Not relevant
Target System
M_EINF_EKO (Purchasing Organization in Purchasing Info Record)
M_EINF_EKG (Purchasing Group in Purchasing Info Record)
M_EINF_WRK (Plant in Purchasing Info Record)
Name of this migration object: S4_MM_PURCH_INFO_RECORD
ME_INFORECORD_MAINTAIN_MULTI RFC Function Module to Create and Change Multiple Info Records
Virtual Tables
● EINE_EXTRA: To store additional EINE fields

● PIR_COND_VALIDITY: To store PIR condition validities
● PIR_CONDITION: To store PIR conditions
● PIR_COND_VALSCL: To store value scales for PIR conditions
● PIR_COND_QTYSCL: To store quantity scales for PIR Condition
● PIR_TEXT: To store related texts for info records
Post-Processing
Not relevant

Create ME11
Change ME12
Display ME13
Further Information
1.81 MM - Purchase scheduling agreement
Purpose
This migration object enables you to migrate purchase scheduling agreement data from the source ERP
Interfaces (BAPIs).

Related Business Object: Purchase Scheduling Agreement
Purchasing Outline Agreement Scheduling
Agreement
Component: MM-PUR (Outline Agreements)
Business Object Definition An outline agreement against which materials are procured
at a series of predefined points in time over a certain period.
Available Scenarios
Selection Criteria
This migration object automatically selects all purchase scheduling agreements from the EKKO table for the
 Note
The relevant purchasing document category (BSTYP) for this migration object is L (Purchase Scheduling
Agreement).
In Scope
● Standard purchasing scenarios

● Consignment scenarios
● Subcontracting scenarios
● Third-party scenarios
● Scheduling agreements with time-dependent conditions (EKKO-STAKO = "X")
● Scheduling agreement header data
● Scheduling agreement items data
● Header and item long texts
● Account assignment data
● Delivery schedule lines
● Shipping data for stock transport orders
● Header conditions data
● Item conditions data
● Validity period of header conditions

● Validity period of item conditions
● Value scale and quantity scale of header conditions
● Value scale and quantity scale of item conditions
● Foreign trade data
● Partner data
● Delivery addresses
 Note
Purchase scheduling agreements you set for deletion in the source ERP system are not migrated
Out of Scope
● Account profitability segment calculation data

● Shipping export data
● Stock transport scheduling agreements
● Release strategy
Prerequisites

● MM - Purchasing info record
● Product
● PS - Network
● Supplier
Source System
Not relevant

Target System
● M_RAHM_BSA (Create/Update/Display outline agreements using the document type)

● M_RAHM_EKO (Create/Update/Display outline agreements using the purchasing organization)
● M_RAHM_EKG (Create/Update/Display outline agreements using the purchasing group)
● M_RAHM_WRK (Create/Update/Display outline agreements using the plant)
Name of this migration object: S4_MM_SCHEDULING_AGREEMENT
BAPI_SAG_CREATE Create a Scheduling Agreement
Virtual Tables
● ITM_TXT: To handle item long texts

● HDR_TXT: To handle header long texts
● AS_KONH: To handle header conditions
● AS_KONP: To handle item conditions
● AS_KONM: To handle quantity scale conditions
● AS_KONW: To handle value scale conditions
● AS_ADRC: To handle addresses
Post-Processing
Not relevant

Create ME31L
Change ME32L
Display ME33L

Further Information
1.82 MM - Service entry sheet
Purpose
This migration object enables you to migrate service entry sheet data from the source ERP system to the target
Related Business Object: Service Entry Sheet
Service Entry Sheet
Component: MM
Business Object Definition A list of services performed by a vendor on the basis of a

purchase order, containing service descriptions and details
of quantities and values. The descriptions of planned serv
ices deriving from the purchase order are used as default de
scriptions in the service entry sheet. Unplanned services
that were entered in the purchase order without descriptions
using value limits are precisely specified in the entry sheet.
Available Scenarios
Selection Criteria
This migration object derives purchase organizations from the company codes you specified when defining the
migration scope. This migration object automatically selects all service entry sheets from the ESSR table for
relevant purchase orders.
Relevant purchase orders are those orders that belong to the derived purchase organizations and the central
purchase organizations. For more information, see the documentation for the MM - Purchase order migration
object.

In Scope
● Service entry sheets deselected for acceptance (ESSR-KZABN = space)

● Header data
● Planned services
● Unplanned services
● Account assignments
● Values/links to service account assignments
● Service long texts
● Long texts for service entry sheet headers
 Note
Service entry sheets you set for deletion in the source ERP system are not migrated.
Out of Scope
Not relevant
Prerequisites
● MM - Purchase order (only open PO)

● MM - Service master
Source System
Not relevant
Target System
● M_BEST_BSA (Document Type in Purchase Order)

● M_BEST_EKG (Purchasing Group in Purchase Order)
● M_BEST_EKO (Purchasing Organization in Purchase Order)

● M_BEST_WRK (Plant in Purchase Order)
Name of this migration object: S4_MM_SERVICE_ENTRY_SHEET
BAPI_ENTRYSHEET_CREATE Create Entry Sheet
Virtual Tables
● AS_SHEET_TXT: To handle long texts for service entry sheets

● AS_SRV_TXT: To handle service long texts
Note that these table do not exist in the database.
Post-Processing
Not relevant
Create ML81N
Change ML81N
Display ML82
Further Information

1.83 MM - Service master
Purpose
This migration object enables you to migrate service master data from the source ERP system to the target
Related Business Object: Service Master
Business Object Component/Area User Menu Path: Logistics Material Management
Service Master Service
Component: MM-SRV
Business Object Definition A repository for the descriptions of all services that a firm
frequently procures. There is a service master record for
each service description. The service master database is a
source of default data set by the system when you create
service specifications (for example, for invitations to bid sent
to potential subcontractors during a competitive bidding
process).
Available Scenarios
Selection Criteria
This migration object automatically selects all service master records from the ASMD table in the source
system.
In Scope
● Service master long texts

● Basic data
● Standar service categories

● Time management data
● Purchase data
● Internal work data
● Sales and distribution data
Out of Scope
Userdefined fields
Prerequisites
Source System
Not relevant
Target System
M_SRV_LS (Create/Update of Service Master)
Name of this migration object: S4_MM_SERVICE_MASTER
BAPI_SERVICE_CREATE Creation of a service master record
Virtual Tables
HDR_TXT : To handle service master long texts

Post-Processing
Not relevant
Create AC01
Change AC02
Display AC03
Further Information
1.84 MM - Source list
Purpose
This migration object enables you to migrate source list data from the source ERP system to the target SAP S/
Related Business Object: Source List
Business Object Component/Area Component: MM-PUR (Source List )

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 (effective) at a certain time.
Available Scenarios
Selection Criteria
This migration object derives plants and materials from the company codes you specified when defining the
migration scope. This migration object automatically selects the materials from the MARC table for the derived
plants.
 Note
If the new source list you provided in the mapping already exists in the target system, after migration, the
target system data is overwritten with the source list data from the source system.
In Scope
● Material number
● Plant
● Source list usage in materials planning
● Agreement number
● Agreement item
● Purchasing organization
● Valid To field in the source list record
● Fixed Supplier indicator
● Blocked source of supply
● Valid From field in the source list record
Out of Scope
● Logical system
● Product fields relevant for Purchasing

Prerequisites
● Product
● Supplier
● MM - Purchase contract
● MM - Purchase scheduling agreement
Source System
Not relevant
Target System
M_ORDR_EKO (Purchasing Organization in Source List)
Name of this migration object: S4_MM_SOURCE_LIST
ME_INITIALIZE_SOURCE_LIST Initializes the source list
ME_DIRECT_INPUT_SOURCE_LIST Creates a source list and fills the mappings of the EORD table
ME_POST_SOURCE_LIST_NEW Posts the source list in the receiver system
 Note
The migration object stores the sequence of these BAPIs in a return evaluation class
Post-Processing
Not relevant

Create ME01
Change ME02
Display ME03
Further Information
1.85 MM - Purchase order
Purpose
This migration object enables you to migrate purchase order data from the source ERP system to the target
Related Business Object: Purchase Order
Business Object Component/Area User Menu Path: Logistics Material management
Purchasing Purchase order
Component: 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.
Available Scenarios
Selection Criteria

This migration object derives purchasing organizations from the company codes you specified when defining
the migration scope. This migration object automatically selects relevant purchase orders from the EKKO table
for the company codes and derived purchasing organizations.
Relevant selection criteria
● The value in the Purchasing Document Category (BSTYP) field is F (order) AND
● The Delivery Completed Indicator (ELIKZ) field is not set for the purchasing document item AND
● The Final Invoice Indicator (EREKZ) field is not set for the purchasing document item AND
● If the value for the scheduled quantity (MENGE) does not match the value for the quantity of goods
received (WEMNG), the purchasing quantity is not processed.
In Scope
● Header data
● Header address data
● Header texts
● Item data
Only the following item categories:
○ Standard
○ Third-party
○ Enhanced limits
○ Consignment
○ Subcontracting
○ Service and limits
● Item address data
● Item account assignments
Only the following account assignment categories:
○ Cost center
○ Asset
○ Sales order
○ Project
○ Unknown
● Item schedule lines
● Purchase order item components for subcontracting
● Item texts
● Pricing data
● Manual service conditions
 Note
Purchase orders you set for deletion in the source ERP system are not migrated

Out of Scope
● Held (not yet complete) purchase orders

● Item data set for deletion
● Changes in message records (in the NAST table) and additional message data
● Documents attached to the purchase order
● Item categories not mentioned in the scope list such as transport orders
● Purchase orders for sales orders and non stock sales
● Release strategy data
● Export data
● Shipment data
● Planning data
Prerequisites

● MM - Purchase requisition (only open PR)
● Pricing condition (purchasing and sales)
● Product
● PS - Network
● Supplier
● Service master
Source System

Not relevant
Target System
M_BEST_BSA (Document type in PO)
M_BEST_EKG (Purchasing group in PO)
M_BEST_EKO (Purchasing organization in PO)
M_BEST_WRK (Plant in PO)
Name of this migration object: S4_MM_PURCHASE_ORDER
BAPI_PO_CREATE1 Create Purchase Order
Virtual Tables
● ITEM_TEXT: To handle item texts

● ESLH_AS: To handle service lines
● ESLL_AS: To handle service lines
● ESKL_AS: To handle account assignment distribution for service lines
● ESUC_AS: To handle service contract limits
● ESLLT_AS: To handle service long texts
● ESUH_AS: To handle service limits
● HEADER_TEXT: To handle header texts
● HEADER_ADRC: To handle vendor addresses
Post-Processing
Not relevant

Create ME23N
Change ME23N
Display ME23N
Further Information
1.86 MM - Purchase requisition (only open PR)
Purpose
This migration object enables you to migrate open purchase requisition data from the source ERP system to
(BAPIs).
Related Business Object : Purchase Requisition
Purchasing Purchase Requisition
Component: MM-PUR
Business Object Definition A request or instruction to Purchasing to procure a quantity

of a material or service so that it is available at a certain
point in time.
Available Scenarios
Selection Criteria
This migration object derives plants and purchasing organizations from the company codes you specified when
defining the migration scope. This migration object automatically selects relevant purchase requisitions from
the EBAN table for the derived plants and purchasing organizations.

● The Deletion Indicator in the Purchasing Document (LOEKZ) field is blank.

● The Purchase Requisition Closed (EBAKZ) field is blank.
● The Purchase Requisition Not Yet Complete (MEMORY) field is blank.
In Scope
● Header data
● Header texts
● Item data
○ Standard
○ Consignment
○ Subcontracting
○ Third-party
○ Stock transfer
● Item texts
 Note
Purchase requisitions you set for deletion in the source ERP system are not migrated.
Out of Scope
● Held (not yet complete) purchase requisitions

● Service data
Prerequisites


● Product
● PS - Network
● PS - Project
● Supplier
Source System
Not relevant
Target System
● M_BANF_BSA (Document type in purchase requisition)

● M_BANF_WRK (Plant in purchase requisition)
● M_BANF_EKG (Purchasing group in purchase requisition)
● M_BANF_EKO (Purchasing organization in purchase requisition)
Name of this migration object: S4_MM_PURCHASE_REQUISITION
BAPI_PR_CREATE Create Enjoy Purchase Requisition
Virtual Tables
● ART_EBAN: To handle item data

● ART_EBKN: To handle account assignment data
● ART_PRPS: To handle account assignment data
● ART_RESB: To handle components
● ART_ADRC: To handle delivery addresses
● ART_ADR6: To handle delivery addresses

● ART_PRHEADERTEXT: To handle header texts
● ART_PRITEMTEXT: To handle item texts
Post-Processing
Not relevant
Create ME51N
Change ME51N
Display ME51N
Further Information
1.87 MM - Quota arrangement
Purpose
This migration object enables you to migrate quota arrangement data from the source ERP system to the
Related Business Object: Quota Arrangement

Business Object Component/Area User Menu Path: Materials Management Purchasing
Quota Arrangement
Component: MM-PUR
Business Object Definition Quota arrangements enable the system to compute which
source of supply to assign to a requirement for a material.
The quota arrangement facilitates the determination of the
applicable sources of supply for a purchase requisition at a
certain time. Setting quotas permits the automatic appor
tionment of a total material requirement over a period to dif
ferent sources. A quota arrangement consists of quota ar
rangement records identifying the source (such as a vendor
or an internal plant), the validity period, and the quota.
Available Scenarios
Selection Criteria
This migration object automatically selects quota arrangement data from the EQUK table
In Scope
● Header data
● Component item data
Out of Scope
Not relevant
Prerequisites

● MM - Purchase info record
● Product
● Supplier
Source System
Not relevant
Target System
M_QUOT_WRK Plant(Quotas)
Name of this migration object: S4_MM_QUOTA_ARRANGEMENT
CNV_PE_S4_QUOTA_ARRANGEMENT Wrapper Function Module for Quota Arrangement
Post-Processing
Create MEQ1
Change MEQ4
Display MEQ3

Further Information
1.88 Object classification (general template)
Purpose
This migration object enables you to migrate object classification data from the source ERP system to the
Related Business Object: Classification
Business Object Component/Area User Menu Path: Cross Application Components
Classification System Assignment Assign Object to
Classes
Component: CA
Business Object Definition The assignment of objects to a class. When you assign ob
jects to a class, you assign values for the object to the char
acteristics in the class.
Available Scenarios
Selection Criteria
In Scope
● Material class type (001)

● Equipment class type (002)

● Functional location class type (003)
● Master inspection characteristic class type (005)
● Inspection method class type (006)
● Catalog code group/code class type (007)
● Selected set class type (008)
● Production resource/tool class type (009)
● Vendor class type (010)
● Customer class type (011)
● Maintenance notification class type (015)
● Document info record (DMS) class type (017/201)
● Equipment task list class type (019)
● Functional location task list class type (019)
● General maintenance task list class type (019)
● Work center class type (019)
● Variant class type (300)
Out of Scope
Change numbers
Class types for batch classification: 022 and 023
 Note
Prerequisites
● Catalog code group/code

● Characteristic
● Class
● Customer
● Document info record (DMS)
● Maintenance notification
● PM-Equipment
● PM-Equipment task list
● PM-Functional location
● PM-Functional location task list

● PM-General maintenance task list
● PP-Production resource/tool
● PP-Work center
● Product
● QM-Inspection method
● QM-Master inspection characteristic
● QM-Selected set
● Supplier
Source System
Not relevant
Target System
C_KLAH_BKP (Authorization for Class Maintenance)
C_TCLS_BER (Authorization for Org. Areas in Classification System)
C_KLAH_BKL (Authorization for Classification)
C_TCLS_MNT (Authorization for Characteristics of Org. Area)
Name of this migration object: S4_CA_CLASSIFICATION_ASSIGNMENT
BAPI_OBJCL_CREATE Classification BAPI: Create Assignment
Virtual Tables
● CLASSES: To store the list of classes assigned to object classifications

● ALLOCVALUESNUM: To store numeric characteristic values
● ALLOCVALUESCHAR: To store character characteristic values
● ALLOCVALUESCURR: To store currency characteristic values

Post-Processing
Not relevant

Create CL20N
Change CL20N
Display CL20N
Further Information
1.89 PM - Equipment
Purpose
This migration object enables you to migrate equipment data from the source ERP system to the target SAP S/
Related Business Object: Equipment
Business Object Component/Area User Menu Path: Logistics Plant Maintenance
Management of Technical Objects Equipment
Component: PM

Business Object Definition An individual, physical object that is maintained as an auton
omous unit.
Available Scenarios
Selection Criteria
This migration object automatically selects the equipment from the ILOA table for the derived plants.
In Scope
● General data for technical objects

● Equipmentspecific data
● Vehiclespecific data
● Valid-from date for equipment
● Object links for document info records
● Installation date for equipment
 Note
● You can migrate only the latest time segment data (valid-from date for equipment) to the target
system.
● You can set only one language for the migration of equipment data.
● Equipment data with the DLFL system status is migrated with the AVLBsystem status.
Out of Scope
● Linear assets management data

● User defined fields
● Industrial solutionspecific fields
● User definedstatus
● Equipment long texts
● Classification
● Equipment address
● Partners
● Measuring points/counters
● Change documents
● Historical equipment data

 Note
You can simulate only this feature: Create equipment.
The following feature is out of scope for simulation: Document info record assignment
Prerequisites

● PM - Functional location
● PS - Project
Source System
Not relevant
Target System
I_BETRVORG (PM: Business Operation)
Name of this migration object: S4_PM_EQUIPMENT
BAPI_EQUI_CREATE PM BAPI: Create Equipment
BAPI_DOCUMENT_CHANGE2 BAPIs for document info records

Virtual Tables
● ILOA_WC: To store internal work center numbers

● ILOA_WBS: To store internal WBS elements
● ILOA_FLOC: To store internal functional location names
● EQUZ_WC: To store internal main work center numbers
System Actions
Equipment Number mapping task: If the target equipment number is set to blank, the system creates
equipment using internal numbers defined for that equipment category.
Superordinate equipment: If superordinate equipment is assigned to an equipment, you need to migrate the
superordinate equipment before migrating the equipment. If you don't follow this migration sequence , the
system displays the Equipment could not be read error.
Post-Processing
You can migrate the Object classification (general template) object to assign classifications to equipment.

Create IE01
Change IE02
Display IE03
Further Information
1.90 PM - Equipment task list

Purpose
This migration object enables you to migrate equipment task list data from the source ERP system to the
Related Business Object: Equipment Task List
Preventative Maintenance Work Scheduling Task Lists
For Equipment
Component: PM
Business Object Definition A maintenance task list with a link to a piece of equipment.
You can use equipment task lists to:
● Define and update maintenance tasks for a piece of

equipment
● Prepare maintenance plans and orders for a piece of
equipment.
Available Scenarios
Selection Criteria
This migration object automatically selects the equipment task list data from the EAPL table for the derived
plants.
In Scope
● Task list header data

● Operations
● Suboperations
● Production resources/tools
● Maintenance packages
● Relationships
● Long texts
● Service packages for operations

● Assignment of object dependencies (local and global) to operations and service packages
Change Numbers
Any data you created using a change number is migrated if the change number was created on or before the
current date. Note that the change number itself is not migrated.
 Example
On the Display Equipment Task List initial screen, you enter 2 in the Group Name field and TEST_C01 in the
Change Number field for the current date. Choose Header. to enter a description in the Group Counter field.
Save your data.
This migration object transfers the description you entered since it is the latest information for the
TEST_C01 change number. However, the migration object does not transfer either TEST_C01.
 Note
Action dependency types are migrated to the target system as procedure dependency types.
Out of Scope
● Values belonging to the Internal Distribution field (VERTN) in the Operations view
● Inspection characteristics
● Service packages for suboperations
 Note
Validation of dependencies is not carried out during migration for these statuses:
● In Preparation
● Locked
Prerequisites

● PM - Equipment
● Product

Source System
Not relevant
Target System
I_ROUT1 (PM: Task Lists by PM Planning Plant, Work Scheduler, Status)
Name of this migration object: S4_PM_EQUIPMENT_TL
● EAM_TASKLIST_CREATE: Create API for Task List

● EAM_TASKLIST_POST: Trigger Posting
● CUKD_API_ALLOCATIONS_MAINTAIN: Dependency Maintenance
Virtual Tables
● AS_REL: To handle relationships

● AS_OP: To handle operations and suboperations
● AS_TEXT_HDR: To handle long texts of meta data
● AS_TEXT_ITEM: To handle long texts of actual data
● AS_CUOB: To handle assignments of objects to dependencies
● AS_CUKB: To handle the basic data of dependencies
● AS_CUKBT: To handle dependency descriptions
● AS_DOCU: To handle dependency documentation
● AS_CUKN: To handle the source code of dependencies
● AS_CUXREF: To handle dependency cross-references
● AS_CABN: To handle characteristics used in dependencies
● AS_SPACK_OUTLINES: To handle service package outlines
● AS_SPACK_LINES: To handle service package lines
● AS_SPACK_LIMITS: To handle service package limits
● AS_SPACK_CLIMITS: To handle contract limits for service packages

Post-Processing
Not relevant

Create IA01
Change IA02
Display IA03
Further Information
1.91 PM - Functional location
Purpose
This migration object enables you to migrate functional location data from the source ERP system to the target
Related Business Object: : Functional Location
Management of Technical Objects Functional Location
Component: PM

Business Object Definition An organizational unit in Logistics that structures the main
tenance objects of a company according to functional, proc
ess-oriented, or spatial criteria. A functional location repre
sents the place at which a maintenance task is performed.
Available Scenarios
Selection Criteria
This migration object automatically selects functional locations from the ILOA table for the derived plants.
In Scope
● Basic data
● Data origin-related data
 Note
You can set only one language for the migration of functional locations.
Out of Scope

● User defined fields
● Userdefined statuses
● Functional location long texts
● Classifications
● Functional location addresses
● Partners
● Historical data
 Note
You can simulate only this feature: Create functional location
The following feature is out of scope for simulation: Data origin-related data

Prerequisites
● PS - Project
Source System
Not relevant
Target System
Name of this migration object: S4_PM_FUNCLOC
BAPI_FUNCLOC_CREATE PM BAPI: Create Functional Location
BAPI_FUNCLOC_INHERIT_CHANGE API for Data Origin
Virtual Tables
● APS_IFLOT: To store superior functional location internal number

● APS_CRHD: To store work center internal number
System Actions
Superior functional location: If a superior functional location is assigned to a functional location, you need to
migrate superior functional location data before migrating functional location data. If you don't follow this
migration sequence, the system displays the Equipment could not be read error.

Post-Processing

Create IL01
Change IL02
Display IL03
Further Information
1.92 PM - Functional location BOM
Purpose
This migration object enables you to migrate bill of materials (BOM) data from the source ERP system to the
Related Business Object: Bill of Materials
Management of Technical Objects Bill of Materials
Functional Location BOM
Component: PM

Business Object Definition 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.
Available Scenarios
Selection Criteria
This migration object automatically selects the bills of material from the TPST table for the derived plants.
In Scope
● Bills of material of type “T”

● Header data
● Sub-items
 Note
Functional location BOM data you set for deletion in the source ERP system is not migrated.
Out of Scope
● Sub-items
● Document assignments
● Long texts
● R-Variable size items
● K-Class items
Prerequisites

● Material
Source System
Not relevant
Target System
● M_MATE_WRK (Material Master: Plants)

● C_TCLA_BKA (Access to Classes Using the Class Type)
● C_STUE_NOH (Create/Update/Display of BOM)
● C_STUE_BER (Create/Update/Display of Bills of Material)
● C_STUE_WRK (Create/Update/Display the Allocation of a BOM to a Plant)
Name of this migration object: S4_PP_FUNC_LOC_BOM_AREA
CSAI_BOM_MAINTAIN: Mass Maintenance for Bill of Materials
Post-Processing
Not relevant

Create IB11
Change IB12
Display IB13

Further Information
1.93 PM - Functional location task list
Purpose
This migration object enables you to migrate task list data for functional locations from the source ERP system
Related Business Object: Functional Location Task List
For Functional Location
Component: PM
Business Object Definition A maintenance plan with a link to a specific functional loca
tion in order to:
● Define and update tasks for a functional location

● Prepare maintenance plans and maintenance orders for
a functional location
Available Scenarios
Selection Criteria
This migration object automatically selects the task list data for functional locations from the TAPL table for
the derived plants.

In Scope

● Operations
● Suboperations
● Relationships
● Long texts
Change Numbers
 Example
On the Display Functional Location Task List initial screen, you enter 2 in the Group Name field and
TEST_C01 in the Change Number field for the current date. Choose Header to enter a description in the
Group Counter field. Save your data.
TEST_C01 change number. However, the migration object does not transfer TEST_C01.
 Note
Out of Scope
 Note
● In Preparation
● Locked

Prerequisites

● PM - Equipment
● PM - Work center
● Product
Source System
Not relevant
Target System
I_ROUT1 (PM: Task Lists by PM Planning Plant, Work Scheduler, Status)
Name of this migration object: S4_PM_FUNCLOC_TL

Virtual Tables


Post-Processing
Not relevant
Create IA11
Change IA12
Display IA13
Further Information
1.94 PM - Equipment BOM

Purpose
This migration object enables you to migrate equipment BOM data from the source ERP system to the target
Related Business Object : Equipment Bill of Material
Management of Technical Objects Bill of Material
Equipment BOM
Component: PM
Business Object Definition 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.
Available Scenarios
Selection Criteria
This migration object automatically selects all equipment numbers from the EQST table for the derived plants.
In Scope
● Basic data
● Equipment BOM descriptions
● BOM items
● BOM subitems
● Modified records using engineering change numbers
● Long texts
Out of Scope
● Document assignments
● Records that are deleted without using engineering change numbers

Prerequisites
You have migrated or defined settings in these migration objects:

● PM - Equipment
● Product
Source System
Not relevant
Target System
To carry out migration, assign the following authorization object or objects to the user:
● C_STUE_BER: CS BOM Authorizations

● C_STUE_WRK: CS BOM Plant (Plant Assignments)
● C_STUE_NOH: CS Authorization to process BOMs without a change number
● C_TCLA_BKA: Authorization for Class Types
Name of this migration object: S4_PM_EQUIPMENT_BOM
CSAI_BOM_MAINTAIN: API Stücklisten: Stückliste pflegen (E,T,M,K,P)
Virtual Tables
● ITM_TXT: To store long texts for BOM items

● BOM_TXT: To store long texts for BOM headers
● DRAD_ITM: To store document-object links

Post-Processing
Not relevant

Change IB02
Display IB03
Further Information
1.95 PM - General maintenance task list
Purpose
This migration object enables you to migrate general task list data from the source ERP system to the target
Related Business Object: General Maintenance Task List
General Maintenance Task Lists
Component: PM

Business Object Definition Standardized sequence of operations for performing main
tenance work on technical objects.
The general maintenance task list is not linked to a technical

object.
It contains all the operations, materials, and maintenance re

sources that are required for a maintenance task.
General maintenance task lists or general task lists help you

when performing work scheduling in maintenance orders.
They make it easy to create maintenance plans, because you
can refer to them in the maintenance plan or copy them to it.
Available Scenarios
Selection Criteria
In Scope
● Task list types (PLKZ-PLNTY) with the value " A"

● Task list data not set for deletion (Deletion Indicator (PLKO-LOEKZ) is set to space)
● Operations
● Suboperations
● Relationships
● Long texts
Change Numbers
 Example
On the Display General Task List initial screen, you enter 2 in the Group Name field and TEST_C01 in the
Change Number field for the current date. Choose Header to enter a description in the Group Counter field.
Save your data.

TEST_C01 change number. However, the migration object does not transfer either TEST_C01.
 Note
Out of Scope
 Note
● In Preparation
● Locked
Prerequisites

● PM - Equipment
● Product
 Note
You have set the number range object ROUTING_A to external number range in the target system before
migrating general task lists. You can choose to set the number range object back tointernal number range
after migration.

Source System
Not relevant
Target System
● I_ROUT1 (PM: Task Lists by PM Planning Plant, Work Scheduler, Status)

● C_ROUT (Authorizations for Routings)
Name of this migration object: S4_PM_GENERAL_TL

Virtual Tables


Post-Processing
Not relevant

Create IA05
Change IA06
Display IA07
Further Information
1.96 PM - Measuring point
Purpose
This migration object enables you to migrate measuring point data from the source ERP system to the target
Related Business Object: Measuring Point
Management of Technical Objects Environment
Measuring Points
Component: PM-EQM-SF-MPC

Business Object Definition A physical or logical place at which a status is described.
 Example
Temperature inside a reactor
Speed of revolution of a wind wheel
The status is described using measurement readings.
Measuring points are stored in the SAP system as master

data.
Available Scenarios
Selection Criteria
The PE_S4_OBJNR migration filter retrieves equipment or function location data from the ILOA table for the
derived plants.
Next, the migration filter retrieves object numbers (OBJNR) from the Equipment or Function Location tables.
Finally, the migration filter sends the object numbers to the IMPTT table to obtain the measuring points.
In Scope
● Measuring point object type: Equipment

● Measuring point object type: Function Location
● Measuring point category: M
● Measuring point category: V
● Counters
● Position numbers
● Description
● Code groups
● Authorization groups
Out of Scope
● Classifications
● Valuation codes
● Long texts
● Characteristics

Since measuring points are recreated in the target system, the following data does not match the data in the
source system:
● Name of user who created the measuring point

● Name of user who last changed the measuring point
● Date that the measuring point was created
● Date that the measuring point was changed
Prerequisites
● PM - Equipment
Source System
Not relevant
Target System
To migrate, assign the following authorization object or objects to the user:
I_BEGRGP: PM Authorization Group
Name of this migration object: S4_PM_MEASURINGPOINT
MP_RFC_SINGLE_CREATE NOTRANSL: RFC: Messpunkt anlegen
Virtual Tables
IMPTT_CHAR_VALUES: To convert floating point data to characters

Post-Processing
Not relevant

Change IK02
Display IK03
Further Information
For information about measuring point corrections and measurement document corrections, see SAP Note
2917243 .
1.97 PM - Measurement document
Purpose
This migration object enables you to migrate measurement document data from the source ERP system to the
Related Business Object: Measurement Document
Management of Technical Objects Function Location/
Equipment Measurement Document
Component: PM-EQM-SF-MPC

Business Object Definition A record of measurement or a measuring point or counter at

a particular time.
Available Scenarios
Selection Criteria
This object is not delimited by the company codes specified when defining the migration scope. (Note that the
predecessor migration object, Measuring point, has a company code derivation.)
For each measuring point selected, this migration object selects the corresponding measurement document.
In Scope
● Measuring point
● Position number of measuring point
● Functional location
● Equipment
● Measurement reading
● Target value
● Valuation codes
● Short texts
● Long texts
● Counter readings
Out of Scope
● Processing status
● Previous and last measurement documents
● External number ranges
● Reversal indicator
● Characteristics
Since measurement documents are recreated in the target system, the following data does not match the data
in the source system:
● Name of user who created the measurement document

● Name of user who last changed the measurement document
● Date that the measurement document was created
● Date that the measurement document was changed

Prerequisites
You have migrated or defined settings in the Measuring point migration object.
Source System
Not relevant
Target System
I_BEGRP (PM : Authorization Group)
Name of this migration object: S4_PM_MEASUREM_DOCUMENT : PM - Measurement document
CNV_PE_S4_PM_MEASUREM_DOCUMENT: Create Measurement Document
Virtual Tables
TEXT_TABLE: To handle text tables for measurement documents.
Post-Processing
Not relevant


Change IK12
Display IK13
Further Information
For information about measuring point corrections and measurement document corrections, see SAP Note
2917243 .
1.98 PM - Maintenance order
Purpose
This migration object enables you to migrate maintenance order data from the source ERP system to the target
Related Business Object : Maintenance Order
Business Object Component/Area User Menu Path: Plant Maintenance Maintenance
Processing Order
Component: PM-WOC-MO

Business Object Definition A detailed planning aid for maintenance tasks to be per
formed. Particular order types are the investment order, the
calibration order, and the refurbishment order. You can use
an order to:
● Plan tasks with specific reference to type, scope, dead

lines, and resources
● Monitor the performance of tasks
● Define rules for account assignment and settlement, as
well as for the budget
● Record, display, and settle the costs generated by the
tasks
Available Scenarios
Selection Criteria
This migration object automatically selects maintenance orders from the AUFK table for the derived plants
provided the following conditions are met:
● The maintenance orders have these order types: PM01, PM02, or PM03
● The maintenance orders have these system statuses at the header level: Order Created or Order Released
● The maintenance order contain tasks with Created or Released statuses
In Scope
● Maintenance order header data

● Operations data
● Component data
● Cost information
● Partner information
● Object data
● Additional data
● Location information
● Control information
● Permit information
● Settlement rule data

Out of Scope
● Service packages
● Maintenance object addresses
● Long texts for components
 Note
Follow-on orders and suborders are migrated as standalone orders. Hence, before migration, ensure
business process completion for all follow-on orders and suborders that have these system statuses:
Created or Released.
Prerequisites

● Customer
● MM - Purchase requisition (only open PR)
● PM - Equipment
● PM - Maintenance notification
● Product
● PS - Network
● SD - Sales order
● SD - Sales order (only open SO)
● Supplier
● WBS element

Source System
C_AFKO_ACT (Activities on network header level)
C_AFKO_AWK (CIM: Plant for order type of order)
C_AFKO_DIS (Network: MRP group (plant) and transaction type)
C_AFVG_TYP (PS: Activity types for network act. and activity elements )
C_AFVG_APL (PS: Work center for network activities and activity elements)
Target System
C_AFKO_AWK (CIM: Plant for order type of order)
I_AUART (PM: Order Type)
I_IWERK (PM: Maintenance Planning Plant)
I_QMEL (PM/QM: Notification Types)
I_SWERK (PM: Maintenance Plant)
Name of this migration object: S4_PM_MAINTANANCE_ORDER
BAPI_ALM_ORDER_MAINTAIN Process Maintenance/Service Order
Virtual Tables
● AT_AFVC_PRPS: To handle WBS elements for order operations

● AT_COMPONENTS: To handle maintenance order components
● AT_PRPS: To handle WBS elements for order master data
● AT_COBRB_PRPS: To handle WBS elements for order settlement
● AT_RELATION: To handle order relationships
● AT_OBJECTLIST: To handle object lists

Post-Processing
Not relevant

Create IW31
Change IW32
Display IW33
Further Information
1.99 PM - Maintenance notification
Purpose
This migration object enables you to migrate maintenance notification data from the source ERP system to the
Related Business Object: Maintenance Notification
Business Object Component/Area Component: PM-WOC-MN
Business Object Definition Means with which company notifications are created and
managed in the area of Plant Maintenance.
Available Scenarios

Selection Criteria
This migration object automatically selects the materials from the MARC table for the derived plants.
In Scope
● Notifications header data

● Items
● Items/causes
● Items/tasks
● Items/activities
● Tasks
● Activities
● Classification
● Long texts for notifications
● DIR links
● Maintenance notifications with notification types (QMMART): "M1" ,"M2" or "M3".
● Maintenance notifications with OSNO or OSTS statuses at the header level and TSOS status at the task level
 Note
Migrate classification details linked to the maintenance notification separately using the Object
classification (general template) migration object.
Out of Scope
● Status handling
● Addresses
● Reference objects
● Measurement documents
● Long texts for DIR object links

Prerequisites
● Product
● PM - Equipment
● PM - Measuring point
● Catalog code group and code
Source System
Not relevant
Target System
I_QMEL (PM: Notification Types)
Name of this migration object: : S4_MM_MAINT_NOTIFICATION
CNV_PE_S4_PM_NOTIF_CREATE Create Maintenance Notification
Virtual Tables
AS_LONG_TEXTS: To store long texts

Post-Processing
Not relevant

Create IW21
Change IW22
Display IW23
Further Information
1.100 PM - Maintenance plan
Purpose
This migration object enables you to migrate maintenance plan data from the source ERP system to the target
Related Business Object: Maintenance Plan
Preventive Maintenance Maintenance Planning
Maintenance Plans
Component: 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 plans:
● Single cycle plans (time or performance-based)

● Strategy plans (time or performance-based)
● Multiple counter plans
Available Scenarios
Selection Criteria
This migration object derives maintenance planning plants from the company codes you specified when
defining the migration scope. This migration object automatically selects relevant maintenance plans from the
MPLA table for the derived maintenance planning plants.
 Note
Deleted maintenance plans are excluded from data selection
In Scope
● Time-based maintenance plans

○ Strategy plans
○ Single-cycle plans
● Maintenance plan items
● Long texts for maintenance plans and maintenance plan items
Out of Scope
● Performance-based maintenance plans

○ Multi-counter plans
○ Strategy plans
○ Single cycle plans
● Settlement rules for maintenance plan items
● Object list items for maintenance plan items
● Individual accounting and location data

Prerequisites
● Define an external number range for maintenance items and

● Provide external numbers in the Maintenance Item mapping task.
Since this migration object generates both migration items and maintenance plans, the Customizing described
above enables the generation of maintenance items.
After a successful migration, you can adjust the number ranges to internal.
● PM - Equipment
● PM - Equipment task list
● PM - Functional location task list
● PM - General maintenance task list
Source System
Not relevant
Target System
I_TCODE (PM: Transaction Code)
I_BEGRP (PM: Authorization Group)
Name of this migration object: S4_PM_MAINTENANCE_PLAN
MPLAN_CREATE Create Maintenance Plan
Virtual Table
MPLA_TEXT: To store long texts for maintenance plans

Note that virtual table do not exist in the database.
Post-Processing
Create IP01
Change IP02
Display IP03
Further Information
1.101 PM - Maintenance item
Purpose
This migration object enables you to migrate the maintenance item data from the source ERP system to the
target SAP S/4HANA system based on the default selection criteria selected for the migration object. This
Related Business Object: Maintenance Item

Preventive Maintenance Maintenance Planning
Maintenance Plans Maintenance Items
Component: PM
Business Object Definition A description of the maintenance and inspection tasks re
quired at regular intervals for maintenance objects.
You can specify the reference objects directly in the mainte

nance item or by using an object list.
You can describe the required activities in a maintenance

task list that you assign to the maintenance item.
Available Scenarios
Selection Criteria
This migration object derives maintenance planning plants from the company codes you specified when
defining the migration scope. This migration object automatically selects relevant maintenance items from the
MPOS table for the derived maintenance planning plants. The relevant maintenance items are those items that
are not assigned to any maintenance plans.
 Note
Maintenance items assigned to the maintenance plan are migrated with the Maintenance plan migration
object.
In Scope
● Planning data
● Task lists
Out of Scope
● Settlement rules for maintenance plan items

● Object list items for maintenance plan items
● Individual accounting and location data

Prerequisites
● PM - Equipment
● PM - Equipment task list
● PM - Functional location task list
Source System
Not relevant
Target System
I_TCODE (PM: Transaction Code)
Name of this migration object: S4_PM_MAINT_PLAN_ITEM
MPLAN_ITEM_CREATE Create Maintenance Plan Item
Virtual Table
MPOS_TEXT: To store long texts for maintenance plan items
Post-Processing

Create IP04
Change IP05
Display IP06
Further Information
1.102 PP - Material MRP assignment
Purpose
This migration object enables you to migrate material MRP data from the source ERP system to the target SAP
transfers data to the target system using Application Programming Interface (API).
Related Business Object: Material Master
Component: LO-MM
Business Object Definition The total of all material master records. A company man
ages the data on all its materials in the material master..
Available Scenarios
Selection Criteria
This migration object automatically selects MRP data from the MDMA table for the derived plants.

In Scope
● MRP area type 02 (Storage Location)

● MRP area type 03 (Subcontractor)
● Forecast parameters at the MRP level
Out of Scope
Consumption values
Prerequisites
You have migrated or defined settings in the MM - Product migration object.
Source System
Not relevant
Target System
Name of this migration object: S4_PP_MATERIAL_MRP_AREA
MD_MRP_LEVEL_CREATE_DATA Create MRP data

Post-Processing
Not relevant
Create MM01
Change MM02
Display MM03
 Note
To verify the data, choose the MRP1 tab and then choose
the MRP Areas button. From the MRP areas list, select
an item to display information about that MRP area.
Further Information
1.103 PP - Work center
Purpose
This migration object enables you to migrate work center data from the source ERP system to the target SAP
Related Business Object: Work Center

Business Object Component/Area User Menu Path: Logistics Production Master data
Work centers Work center
Business Object Definition Organizational unit that defines where and by whom an oper
ation is performed. The work center has an available ca
pacity. The activities performed at or by the work center are
valuated by charge rates, which are determined by cost cen
ters and activity types. Work centers can be:
● Machines
● People
● Production lines
● Groups of craftsmen
Available Scenarios
Selection Criteria
This migration object automatically selects all work centers from the CRHD table for the derived plants.
In Scope
● Basic data
● Default values
● Capacities
● Scheduling information
● Costing information
● Technical data
 Note
Work centers you set for deletion in the source ERP system are not migrated.
Out of Scope
Work centers set for deletion
Work center description in languages other than the logon language

Prerequisites
● CO Business process
● CO Cost center
● CO Internal order
Source System
Not relevant
Target System
C_ARPL_WRK (CIM: Work center- plant)
C_ARPL_ART (CIM: Work center category)
Name of this migration object: S4_PM_WORKCENTER
CRAP_WORKCENTER_CREATE API work centers: create work center
Virtual Tables
CRCO_RCVAPI: To handle work center assignments to cost centers.
Post-Processing
Not relevant

Create CR01
Change CR02
Display CR03
Further Information
1.104 PP - Production order
Purpose
This migration object enables you to migrate production order data from the source ERP system to the target
Related Business Object: Production Order
Business Object Component/Area User Menu Path: Logistics Production Shop Floor
Control Order
Component: PP-SFC
Business Object Definition An authorization from the production department to pro

duce a specific quantity of material within a predefined time.
The production order contains all the information required
for the execution of the production process.
Available Scenarios

Selection Criteria
All production orders from the AUFK table are automatically selected for the company codes you specified
In Scope
● Production orders with materials

● Production orders for sales orders
● Production orders for projects
● Production orders with create status
● Production orders with release status
● Production orders with technically complete status
 Note
Production orders you set for deletion in the source ERP system are not migrated
Out of Scope
● Production orders without materials

● Collective conversion of planned orders
● Production orders from planned orders
● Order combinations
● Fashion data
● Production orders with lock status
● Production orders with unlock status
● Production orders with close status
Prerequisites
● Product
● PP - Routing
● PS - Project

Source System
Not relevant
Target System
C_AFKO_ATY (CIM: Order Category)
C_AFKO_AWA (CIM: Authorization for Prod. Order/Order Type/Plant/Activity)
C_AFKO_AWK (CIM: Plant for Order Type of Order)
C_STUE_BER (CS BOM Authorizations)
C_STUE_WRK (CS BOM Plant (Plant Assignments)
Name of this migration object: S4_PP_PRODUCTION_ORDER
BAPI_PRODORD_CREATE: BAPI: Generate Production Order
BAPI_PRODORD_RELEASE: BAPI: Release Production Orders
BAPI_PRODORD_COMPLETE_TECH: BAPI: Technically Complete Production Orders
Post-Processing
Not relevant

Create CO01
Change CO02
Display CO03
Further Information
1.105 PP - Production resource/tool
Purpose
This migration object enables you to migrate production resource/tool (PRT) data from the source ERP system
Related Business Object: Production Resource/Tool
Master Data Production Resources/Tools Production
Resources/Tools PRT Master (Misc.)
Component: PP-BD-PRT
Business Object Definition A moveable operating resource used in production or plant

maintenance.
Available Scenarios
Selection Criteria

In Scope
● Basic data
● Defaults
● Deletion flags
● Long texts
● Formula constants
● Document data
 Note
The Object classification (general template) migration object transfers classification data.
Out of Scope
Change documents
Prerequisites
Document info record (DMS)
Source System
Not relevant
Target System
C_CRFH_BRG (Create Production Resource/Tool)

Name of this migration object: S4_PP_MISC_PRT
● CF_ST_FHM_UPDATE: NOTRANSL: Anlegen/Ändern FHM-Daten

● INIT_TEXT: SAPscript: Initialize Test Work Areas
● SAVE_TEXT: SAPscript: Save Text
● DOCUMENT_ASSIGNMENT_REFRESH: Initialize Document Allocation
● DOCUMENT_ASSIGNMENT_DIRECT: Allocate Document to Several Objects
Virtual Tables
● AS_DOC: To handle document info record assignments

● AS_TEXT_LINES: To handle long texts
Post-Processing
Not relevant

Create CF01
Change CF02
Display CF03
Further Information
1.106 PP - Routing

Purpose
This migration object enables you to migrate routing data from the source ERP system to the target SAP S/
Related Business Object: Routing Group
Routings Routings Standard Routings
Component: PP-BD-RTG
Business Object Definition A description of the production process used to manufac

ture plant materials or provide services in the manufacturing
industry.
Available Scenarios
Selection Criteria
This migration object automatically selects all routing groups from the PLKO table for the derived plants.
In Scope
● Routing data with the task list type "N"

● Modified records using engineering change numbers (ECN)
● Material task list assignments
● Sequences
● Operations
● Suboperations
● Global object dependencies for operations and sequences
● Component assignments
● Long texts
 Note
Routing group data you set for deletion in the source ERP system is not migrated.

 Note
If you selected production resource/tools data, ensure that the following migration objects are available in
the SAP S/4 HANA system:
● PM - Equipment
Out of Scope
● Local object dependencies

● Global object dependencies for production resources/tools
● Routing group data created with ECN
● Other task list types: "0", "2", "3", "A", "E","M", "Q", "R", "S", "T", "V"
 Note
If you have multiple steps for migration, you can simulate the initial routing group data created without
ECN.
During the migration phase, errors may occur for features that were not in scope during simulation, even
Prerequisites
For consistent migration, you have ensured that all relevant Customizing for the migration object is available in
the target SAP S/4HANA system.
● If you need standard text keys in routing data, you have configured the keys in the SAP S/4 HANA system.
● Before migrating routing data, you have set the ROUTING_N number range object to external number range
in the target system. After migration, you can choose to set the number range object back to internal
number range.

● Product
 Note
the SAP S/4 HANA system:
● PM - Equipment

Source System
Not relevant
Target System
C_ROUT (Authorizations for Routing)
Select all values for the ACTVT field except 41.
Name of this migration object: S4_PP_ROUTING_ECN
● BAPI_ROUTING_CREATE: (Creation of a Routing)

● ROUTING_MAINTAIN: (NOTRANSL: Ändern eines Arbeits-/Prüfplans)
Virtual Tables
● COM: To handle component allocations

● SUBOPR: To handle suboperations
● SEQTAB: To handle activities of sequences
● TEXT_HDR: To handle header long texts
● TEXT_ITEM: To handle item long texts
● PRT_TAB: To handle PRT items and activities
● CSLA_TAB: To handle the controlling area of operations activity types
● PLKO_TAB: To handle header ECN records
Post-Processing
Not relevant


Change CA02
Display CA03
Further Information
1.107 PP - Material BOM
Purpose
This migration object enables you to migrate material BOM data from the source ERP system to the target SAP
Related Business Object: Material BOM
Bills of Material Bill of Material Material BOM
Create
Component: PP-BD
Business Object Definition A bill of material created with reference to a material master.
The BOM can contain items of different item categories such
as stock items, non-stock items, document items, and text
items.
Available Scenarios
Selection Criteria
This migration object automatically selects material BOMs from the MAST table for the derived plants

In Scope
● Basic data
● BOM items
● BOM sub-items
● BOM long texts
● Alternative long texts
● Item long texts
● BOM local dependency
● All alternative BOM numbers (from 01 to 99)
● Change numbers
 Note
Material BOMs you set for deletion in the source ERP system are not migrated
Out of Scope
● Fashion material BOM

● Sub items with change numbers
● Document assignment for linked documents
● BOM item classification
● Deletion of BOM headers, items and dependencies
● Class item categories
● Document item categories
● Configurable material BOM
● BOM local dependencies of the type: Action
Prerequisites
● Class
● Characteristic
● Product

● Vendor
Source System
Not relevant
Target System
C_TCLA_BKA (Access to Classes Using the Class Type)
C_STUE_NOH (Create/Update/Display of BOM which has a History Requirement without using a Change
Number)
C_STUE_BER (Create/Update/Display of Bills of Material)
C_STUE_WRK (Create/Update/Display the Allocation of a BOM to a Plant)
Name of this migration object: S4_PP_MATERIAL_BOM
CSAI_BOM_MAINTAIN: API Stücklisten: Stückliste pflegen (E,T,M,K,P)
CSAP_MAT_BOM_MAINTAIN: API Stücklisten: Materialstückliste pflegen
Virtual Tables
● CSDEP_DAT: To handle the basic data of a dependency

● CSDEP_DESC: To handle object dependency descriptions
● CSDEP_ORD: To handle sort sequences of object dependencies
● CSDEP_SORC: To handle the source code of object dependencies
● CSDEP_DOC: To handle object dependency documentation
● CSDOC_LINK: To handle document assignments
● CSDMU_TMX: To handle DMU transformation matrixes
● CSLTX_LINE: To handle long texts

Post-Processing
Not relevant

Create CS01
Change CS02
Display CS03
Further Information
1.108 PP - Planned independent requirement
Purpose
This migration object enables you to migrate planned independent requirement data from the source ERP
Interfaces (BAPIs).
Related Business Object: Planned Independent Requirement
Business Object Component/Area User Menu Path: Logistics Production Production
Planning Demand Management Planned Independent
Requirements
Component: PP-MRP

Business Object Definition The required quantity of a product that is planned for a cer
tain time period independently of a specific customer order.
Available Scenarios
Selection Criteria
1. This migration object derives plants from the company codes you specified when defining the migration
scope.
2. This migration object automatically selects materials from the MARC table for the derived plants.
3. This migration object also selects planned independent requirements from the PBIM table for the derived
materials and plants.
In Scope
● Items
● Schedule lines
 Note
Independent requirements for materials you set for deletion in the source ERP system are not migrated
Out of Scope
● Configuration supporting points for schedule lines

● Withdrawal quantity of schedule lines (See SAP Note 793258 )
● Item texts
● Schedule line texts
Prerequisites

Source System
Not relevant
Target System
C_PPBD (Authorizations for Planned Independent Requirements)
Name of this migration object: S4_PP_PLANNED_IND_REQMNTS
BAPI_REQUIREMENTS_CREATE Planned Independent Requirements: Create Planned Independent

Requirements
Post-Processing
Not relevant
Create MD61
Change MD62
Display MD63
Further Information

1.109 PP - Production version
Purpose
This migration object enables you to migrate production version data from the source ERP system to the target
Related Business Object: Production Version
Master Data Production Versions
Component: PP
Business Object Definition Key determining the various production techniques accord
ing to which a material is to be manufactured. You specify
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
Available Scenarios
Selection Criteria
This migration object automatically selects the production version of the materials from the MKAL table for the
derived plants.
In Scope
● Production version general data (keys, lot-size ranges, validity periods)

● Detailed planning level
● Check status

 Note
For REM materials: If the detailed planning level data is not maintained for the production version, "rate
routing planning level" data is also migrated.
Out of Scope
Not relevant
Prerequisites
For information about planning levels for production versions, see SAP Note 2270240 . Implement the
recommendations before migrating the production version.
● PP - Routing
● Product
 Note
If your production version refers to the master recipe, you need to include master recipe data in the
relevant mapping task for data migration.
Source System
Non relevant
Target System
C_FVER_WRK (Production Version - Plant)

Name of this migration object: S4_PP_PRODUCTION_VERSION
FV_PROD_VERS_MAINTAIN_MULTI Maintain Multiple Production Versions
In SAP ERP, it is not necessary to have a production version for BOM explosion in Discrete Manufacturing. In
SAP S/4HANA, use the CS_BOM_PORDVER_MIGRATION02 report to create a production version based on
existing BOMs and routings.
Post-Processing
Not relevant
Create C223
Change C223
Display C223
Further Information
1.110 PP - Sales order BOM

Purpose
This migration object enables you to migrate bills of material data from the source ERP system to the target
Business Object Component/Area User Menu Path: Logistics Production Bill of
Materials Bill of Material Order BOM
Component: PP-BD
Business Object Definition A single-level BOM that you generate for a sales order from a
material BOM, and that you modify specific to the order. In
this way, the material BOM remains unchanged. An order
BOM is uniquely identified by the sales order number, the
sales order item, and the material number. Order BOMs can
be created for configurable and nonconfigurable materials.
Available Scenarios
Selection Criteria
This migration object automatically selects bills of material from the KDST table for the derived plants.
In Scope
● Bills of material of type "K" (material-based)

● Header data
● Sub-items
● Long texts
● Change numbers
 Note
Materials you set for deletion in the source ERP system are not migrated.

Out of Scope
● Component item C - Compatible unit

● Component item I - PM structure element
● Component item M - Intra-material
● Component item R - Variable size item
Prerequisites
● Product
Source System
Not relevant
Target System
C_STUE_NOH (Create/Update/Display of BOM which has a History Requirement Without Using a Change
Number)
Name of this migration object: S4_PP_SALES_ORDER_BOM
CNV_PE_S4_PP_SALESORDER_BOM Sales Order BOM
Virtual Tables

● ITM_TXT: To store item long texts
● BOM_TXT: To store BOM long texts
● DRAD_ITM: To store document links
Post-Processing
Not relevant
Change CS62
Display CS63
Further Information
1.111 PP - Work breakdown structure BOM
Purpose
This migration object enables you to migrate WBS BOM data from the source ERP system to the target SAP S/
transfers data to the target system using both Application Programming Interfaces (APIs) and Business
Related Business Object: WBS BOM

Bills of Material Bill of Material WBS BOM
Component: PP
Business Object Definition A BOM that is allocated to a WBS (work breakdown struc
ture) element.
Available Scenarios
Selection Criteria
This migration object automatically selects all WBS BOMs from the PRST table for the derived plants.
In Scope
● BOM headers
● BOM items
● Subitems
Out of Scope
● Fashion data
● Classification of BOM items
Prerequisites
● Document Info Record (DMS)

● Product
● PS - Project

● Supplier
Source System
Not relevant
Target System
● C_STUE_BER General Authorization Object for Processing BOMs

● C_STUE_WRK Authorization Object for BOM Plant
● C_STUE_BKA Access to Classes using the Class Type
● C_STUE_NOH Authorization to Process BOM without Change Numbers
Name of this migration object: S4_PP_WBS_BOM
CSAI_BOM_MAINTAIN API Stücklisten: Stückliste pflegen (E,T,M,K,P)
BAPI_DOCUMENT_SAVEOBJECTLINKS Objektverknüpfungen speichern
Virtual Tables
● BOM_TXT: To store BOM header long texts

● ITM_TXT: To store BOM item long texts
● DRAD_ITM: To store documents assigned to BOM
Post-Processing
Not relevant


Create WBS BOM CS71
Change WBS BOM CS72
Display WBS BOM CS73
Project Browser CSPB
Further Information
1.112 Pricing condition (purchasing and sales)
Purpose
This migration object enables you to migrate pricing condition data from the source ERP system to the target
Related Business Object: Pricing Condition
Business Object Component/Area User Menu Path:
Logistics Material Management Purchasing Master
Data Conditions
Logistics Sales and Distribution Master Data
Conditions
Components: MM-PUR and SD

Business Object Definition Sales: A data element used to define prices according to cri
teria selected by the user.
Purchasing: The terms of payment negotiated with a vendor,

such as surcharges or discounts. Pricing conditions deter
mine how the system calculates the effective price in a pur
chase order.
Available Scenarios
Selection Criteria
All pricing condition records belonging to Sales and Distribution and Purchasing are automatically selected
● Condition Usage field (KVEWE) is set as A (pricing) AND

● Application field (KAPPL) is set as M (purchasing) AND V (sales)
In Scope
● Pricing conditions for prices, surcharges and discounts

● Condition headers
● Condition items
● Quantity and value scales
 Note
Pricing condition records used in purchase contracts, purchase info records, sales contracts, and
scheduling agreements are migrated as part of the relevant migration objects.
Out of Scope
● Exclusion indicators
● Condition texts
● Additional data (payment terms, fixed value dates, additional value days, assignments)
● Pricing condition records that belong to applications not in Sales and Purchasing.

Prerequisites
● Customer
● Product
● PS - Project
● Supplier
Source System
Not relevant
Target System
● V_KONH_VKS (Condition: Authorization for Condition Types)

● V_KONH_VKO (Condition: Authorization for Sales Organizations)
● V_KONH_EKO (Purchasing Organization in Master Condition)
Name of this migration object: S4_SD_PRICING_CONDITION
COND_GEN_MIGRATION_CREATE Condition Migration: Create Condition Records
The API updates the validity periods in the condition header table (KONH) with the corresponding validity
periods in the condition tables.
Virtual Tables
● COND_KEY_FIELDS: To store information of condition key fields

● COND_SCALES: To store information of scales data

Post-Processing
Not relevant
Condition Maintenance: Display VK33
Display Condition Records MEK3
Display Condition Records VK13
Further Information
For information about key field combinations for price conditions, see SAP Note 2332748 .
1.113 Product
Purpose
This migration object enables you to migrate material master data from the source ERP system to the target
 Note
This migration object refers to products in the target SAP S/4HANA system.

Material Master Material
Component: LO-MD-MM
Business Object Definition The total of all material master records. A company man
ages the data on all its materials in the material master.
Available Scenarios
Selection Criteria
This migration object automatically selects all products from the MARC table for the derived plants.
● This migration object derives sales organizations from the company codes you specified when defining the
migration scope. This migration object automatically selects products from the MVKE table for the derived
sales organizations.
● This migration object derives valuation areas from the company codes you specified when defining the
migration scope. This migration object automatically selects products from the MBEW table for the derived
valuation areas.
 Note
If a products in the source system is extended to multiple plants: After data migration, the product in the
target system is extended to only the subset of plants assigned to the participating company codes.
In Scope
● Basic data
● Material descriptions
● Material data at the plant level
● Forecast parameters
● Storage location data
● Valuation data
● Warehouse data
● Sales data
● Storage type data
● Unit of measurement
● International article numbers
● Tax classification data

● Material change history
● Long texts
● Document links
● Replenishment data
● Material ledger prices
● Materials marked for deletion
Out of Scope
● Planning data
● Product resource/tool (PRT) data
● Joint production data
● Material MRP data
● Material classifications
● Production versions
● Inspection setup
● Internal numbers
Prerequisites
● Material types
● Material groups
● Characteristics
● Classes
Source System
Not relevant
Target System

● M_MATE_STA (Material Master: Maintenance statuses)
● M_MATE_NEU (Material Master: Create)
● M_MATE_MAN (Material Master: Data at Client Level)
● M_MATE_MAT (Material Master: Materials)
● M_MATE_MAR (Material Master: Material Types)
● M_MATE_WGR (Material Master: Material Groups)
● M_MATE_WRK (Material Master: Plants)
● M_MATE_LGN (Material Master: Warehouse Numbers)
● M_MATE_VKO (Material Master: Sales Organizations/Distribution Channel)
● M_MATE_BUK (Material Master: Company Codes)
Name of this migration object: S4_MM_MATERIAL_N
CMD_MIG_PROD_MAINTAIN Mass Maintenance for Material Master Data
 Note
If the data provided by you in the mapping already exists in the target system:
After data migration, the data in the views are overwritten with data from the source system and the
migration may end in errors. Hence, to avoid the overwriting of the target data, provide new data in the
relevant mapping tasks.
Virtual Tables
● MATERIAL_LONTEXT: To identify material long texts

● SALES_TEXT: To identify sales texts
● PLANT_TEXT: To identify plant texts
● MATERIAL_TAXCLASS: To identify material tax classification data
● MATERIAL_CHN: To identify material change numbers
Post-Processing

Create MM01
Change MM02
Display MM03
Further Information
1.114 PS - Network
Purpose
This migration object enables you to migrate network master data from the source ERP system to the target
Related Business Object: Network
Business Object Component/Area Component: PS
Business Object Definition An object containing instructions on how to perform tasks in

a specific way, in a specific order, and in a specific time pe
riod.
Available Scenarios
Selection Criteria
All networks from the AUFK table are automatically selected for the company codes that you specified when

In Scope
● Scheduling data for network headers

● Assignment data for network headers
● Control data for network headers
● All networks across all system statuses
Out of Scope
● Long texts for network headers

● Activity data
● Relationship data
● Activity element data
● Milestone data
● System statuses
● User statuses
Prerequisites
● PS - Project
Source System
Not relevant
Target System
Not relevant

Name of this migration object: S4_PS_NETWORK
BAPI_BUS2002_CREATE Create Network Header Using BAPI
Post-Processing
Not relevant

Create CJ20N
Change CJ20N
Display CJ20N
Further Information
1.115 PS - Project
Purpose
This migration object enables you to migrate projects data from the source ERP system to the target SAP S/
Related Business Object: Project

Business Object Component/Area User Menu Path: Logistics Project System Project
Component: PS
Business Object Definition A project is a summary of certain business processes within

a company. They can be defined as a plan distinguished by
the uniqueness of their conditions.
A project:
● Has a clear goal

● Is restricted by time due to a defined beginning and a
defined end
● Is characterized by its uniqueness and newness
● Is complex and cannot be carried out without a struc
tural outline
● Has defined costs and a defined budget based on the
tasks involved
● Is carried out within a project-related organization
● Requires defined resources
● Is processed interdisciplinarily
A project is structured according to two points of view:
● By structure
● By process
Available Scenarios
Selection Criteria
Relevant projects (that is, except closed and deleted projects) from the PROJ table are automatically selected
for the company codes that you specified when defining the migration scope.
In Scope
● Project definition data

● WBS elements
● WBS hierarchies
● WBS milestones
● Networks
● Activities
● Activities milestones

● Relationships
Out of Scope
● Long texts
● System statuses in the ERP system (Note that in the SAP S/4HANA system, the project is assigned the
status Created or "CRTD".)
● User statuses
● Settlement rule assignments
● Material reservation creation
● PS texts for WBS elements and activities
● PS documents
● Cost postings
● Confirmation data
● Excluded fields:
Fields Tabs Node
Forecast Start Date, Forecast End Basic Data Project

Date, and Location
Project Summarization check box Basic Data WBS
External Factorand Reduction Internal Activity

Strategy per Operation
Sort Term, Requistioner, Tracking External Activity

Number, Execution Factor,
andUnloading Point
Early/Late Dates Activity
Change Number Assignments Activity
Wage Type, No. Time Tickets, and No. Additional Data Activity
Conf Slips
Prerequisites
● PM - Equipment

● Supplier
Not relevant
Target System
C_PROJ_KOK (PS: Controlling Area for Project Definition)
C_PRPS_KOK (PS: Controlling Area Authorization for WBS elements)
C_AFKO_ACT (Activities on Network Header Level)
C_PRPS_KST (PS: Cost Center Authorization for WBS elements)
C_MLST_BGR (PS: Milestones (Authorization Group))
C_PRPS_USR (PS: Model for User Field Authorization for WBS Elements)
C_PRPS_PRC (PS: Profit Center Authorization for WBS Elements)
C_PROJ_PRC (PS: Profit Center for Project Definition)
Name of this migration object: S4_PS_PROJECT_STRUCTURE
BAPI_PROJECT_MAINTAIN Edit Project Including Networks
Mapping Task Info
This migration object does not automatically update value mapping for networks created with internal number
ranges in the target system. Hence, you need to maintain the value mapping for networks before migrating
other network-related migration objects.
Virtual Tables
● ACT_MILESTONE: To store network activity milestones

● AFVC_EXTRA: To store additional AFVC fields
● RELTN: To store network relationships
● AFKO_TECH: To store additional AFKO fields
● METHOD_PROJ: To store creation methods

Post-Processing

Project Builder CJ20N
Further Information
1.116 QM - Inspection method
Purpose
This migration object enables you to migrate inspection method data and assigned classification values from
the source ERP system to the target S/4 HANA system based on the default selection criteria set for the
Related Business Object: Inspection Method
Business Object Component/Area User Menu Path: SAP Menu Logistics Quality
Management Quality Planning Basic Data Inspection
Method
Component: QM-PT-BD

Business Object Definition Describes the procedure for inspecting a characteristic. In
spection 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.
Available Scenarios
Selection Criteria
In Scope
● Inspection method validity date for a plant (In released status)

● Input characteristics for inspections
● Inspection authorization groups
● Inspector qualification
● Header data for inspection method
● Short text and long text values in multiple languages
● Material classifications
● Information fields
● Search field values
● Long texts
 Note
Inspection methods you set for deletion in the source ERP system are also migrated.
Out of Scope
Inspection documents
Prerequisites

● Plants
● Inspector qualifications
You have migrated or defined settings in the Object classification (general template) migration object.
Source System
Not relevant
Target System
M_MATE_MAT (Material Master: Materials)
Q_TCODE (QM Transaction Authorization)
Name of this migration object: S4_QM_INSPECTION_METHOD
BAPI_QMTB_SAVEREPLICA: Replication of QM Inspection Methods
Virtual Tables
● INSPECTION_METHOD: To store header data for inspection methods

● INSP_METH_TEXT: To store descriptions in multiple languages
● INSP_METH_LONGTEXT: To store long texts in multiple languages
Post-Processing
Not relevant


Create QS31, QS32
Change QS33
Display QS34
Further Information
1.117 QM - Inspection plan
Purpose
This migration object enables you to migrate inspection plan data from the source ERP system to the target
Related Business Object: Inspection Plan
Business Object Component/Area User Menu Path: Logistics Quality Management
Inspection Planning Inspection Plan
Component: QM
Business Object Definition The quality inspection plan defines how an item is to be in
spected. The plan also establishes how the inspection is to
take place, the item characteristics to be inspected, and all
the required test equipment that is needed for the inspec
tion.
Available Scenarios
Selection Criteria

This migration object automatically selects the inspection plans from the PLKO table for the derived plants.
In Scope

● Task list type: "Q"
● Operations
● Material assignments
● Long texts
 Note
Inspection plans you set for deletion in the source ERP system are not migrated.
Out of Scope
● Dependent characteristics
● Inspection characteristics values
● Other task list types, such as "0", "2", "3", "A", "E" "M", "N", "R", "S", "T", "V"
● Engineering change numbers for inspection plans
Prerequisites
Before you can start the migration process, for example, ensure the following settings in the target system:
Standard text keys
● Product
● QM - Master inspection characteristic
● QM - Inspection method
● PM - Equipment

● PP - Production resource/tool
Source System
Not relevant
Target System
Q_ROUT (Authorizations for Routing)
C_PLKO_PLG (PS: Planner Groups for Standard Networks)
Name of this migration object: S4_QM_INSPECTION_PLAN
BAPI_INSPECTION_PLAN_CREATE Create Inspection plan
Virtual Tables
● CSLA_TAB : To store activity types for controlling areas

● PRT_TAB: To store production resources/tools
● TEXT_HDR: To store text headers with inspection plan details
● TEXT_ITEM: To store texts
● CHRD_PLKO: To store taskspecific information for work center details
Post-Processing

Change Inspection Plan QP02
Display Inspection Plan QP03
Further Information
1.118 QM - Master inspection characteristic
Purpose
This migration object enables you to migrate master inspection characteristic data from the source ERP
system to the target SAP S/4 HANA system based on the default selection criteria set for the migration object.
Interfaces (BAPIs).
Related Business Object: Inspection Characteristics
Basic Data Inspection Characteristics
Component: QM-PT-BD-ICH
Business Object Definition Inspection characteristic that can be used in several inspec
tion plans and can be evaluated independently of an inspec
tion plan. Master inspection characteristics facilitate and
standardize inspection planning. When creating an inspec
tion plan, it is possible to access the data from the inspec
tion characteristic record, as well as to create inspection
planspecific inspection characteristics.
Available Scenarios
Selection Criteria

This migration object automatically selects inspection characteristics from the QPMK table for the derived
plants.
In Scope
● Master inspection characteristics

● Inspection methods
● Short texts and long texts in the defined languages
● Sample-drawing texts
Out of Scope
Classifications
Prerequisites
● QM - Inspection method
● QM - Selected set
● QM - Selected set code
Source System
Not relevant
Target System
Q_STA_QPMK (Maintain Master Inspection Characs. Depending on Status)

Name of this migration object: S4_QM_MASTER_INSP_CHARAC
BAPI_QPMK_SAVEREPLICA Replication of QM Master Inspection Characteristics (ALE)
Virtual Tables
● AS_SHORT_TEXT: To handle short texts

● AS_SAMP_DR_TEXT: To handle sample drawing texts
● AS_INT_CHARAC: To handle internal and external formats for characteristics
Post-Processing
Not relevant
Create QS21
Change QS22
Display QS23
Further Information
1.119 QM - Material inspection setup

Purpose
This migration object enables you to migrate material inspection setup data from the source ERP system to the
Related Business Object: Material Inspection Setup
Quality Planning Logistics Master Data Material
Inspection Setup
Component: QM
Business Object Definition You can assign inspection setup data to a material. The
Quality Management view of the material master primarily
contains the control parameters you need to process quality
inspections throughout the logistics supply chain. In the ma
terial master, you define various inspection parameters
based on the inspection type (for example, triggering events
for quality inspections, inspection with or without task list).
You must edit inspection setup to be able to create inspec
tion lots for material. Inspection lots are created for all good
movement that are relevant for QM. In the material master
you define which goods movements are relevant to QM.
Available Scenarios
Selection Criteria
This migration object automatically selects the materials from the QMAT table for the derived plants.
In Scope
Inspection setup for all Inspection types
Out of Scope
Not relevant

Prerequisites
Before you can start the migration process, for example, ensure the following Customizing in both the source
and target systems:
● Sampling procedures
● Dynamic modification rules
● Plants
Source System
Not relevant
Target System
Q_TCODE (QM Transaction Authorization)
Name of this migration object: S4_QM_INSPECTION_SETUP
BAPI_MATINSPCTRL_SAVEREPLICA Data Distribution of QM Setup Data
Post-Processing
Not relevant

Create QA08
Change QA08
Display QA08
Further Information
1.120 QM - Quality info record
Purpose
This migration object enables you to migrate quality info record data from the source ERP system to the target
Related Business Object: Quality Info Record
Logistics Master Data Quality Info record:Procurement
Component: QM-PT-RP-PRC
Business Object Definition If a quality assurance agreement or a vendor release is re

quired for a material, you must create a quality information
record (quality info record). The quality info record deter
mines how the material can be processed further.
Available Scenarios

Selection Criteria
This migration object derives plant from the company codes you specified when defining the migration scope.
This migration object automatically selects the quality info records from the QINF table for the derived plant.
In Scope
Quality info records (Procurement)
Out of Scope
● Classifications
● Long texts
● Records marked for deletion
● Status profiles
● Quality agreements
Prerequisites
● Product
● Supplier
Source System
Not relevant
Target System
Q_MATERIAL (Material authorization)
Q_TCODE (QM Transaction authorization)

Name of this migration object: S4_QM_QUAL_INFO_REC
QBCK_QINF_CREATE: Creates Quality Info-Records
Post-Processing

Create QI01
Change QI02
Display QI03
Further Information
1.121 QM - Selected set
Purpose
This migration object enables you to migrate selected set data for inspection catalogs from the source ERP
system to the target S/4 HANA system based on the default selection criteria set for the migration object. This
migration technique posts data to the target system using Application Programming Interfaces (APIs).
Related Business Object: Inspection Catalog Selected Set

Business Object Component/Area User Menu Path: SAP Menu Logistics Quality
Management Quality Planning Basic Data Catalog
Selected Set
Component: QM-PT-BD-CAT
Business Object Definition A range of specific entries (code groups and codes), of a cat
alog. A selected set enables the user to choose only those
code groups and codes of a catalog that are required or al
lowed for a specific purpose.
Available Scenarios
Selection Criteria
In Scope
● Selected sets
● Master record statuses
 Note
Selected sets that you set for deletion in the source ERP system are also migrated.
Out of Scope
Classifications
Prerequisites
For a consistent migration, you have ensured that all the relevant Customizing for the migration object is
available in the target SAP S/4HANA system.


Source System
Not relevant
Target System
Q_CAT_SSET (Catalog Maintenance of Selected Sets)
Name of this migration object: S4_QM_INSP_CAT_SEL_SET
QPAM_SELSET_CODE_CREATE: NOTRANSL: Code in Auswahlmenge anlegen
Virtual Tables
● I_QPAM: To store the header details of selected sets

● I_LONG_TEXT_TAB: To store long texts in multiple languages
Post-Processing
Not relevant
Create QS51
Change QS52
Display QS53

Further Information
1.122 QM - Selected set code
Purpose
This migration object enables you to migrate selected set code data from the source ERP system to the target
Related Business Object: Selected Set
Business Object Component/Area Component: QM-PT-BD-CAT
Business Object Definition Selected set: A range of specific entries (code groups and
codes) of a catalog. A selected set enables the user to
choose only those code groups and codes of a catalog that
are required or allowed for a specific purpose.
Selected set code: Codes that are copied into a selected set
are known as set codes. You use selected sets to combine
codes from several code groups for processing that are al
lowed or useful for a particular application.
Available Scenarios
Selection Criteria
This migration object automatically picks up all selected set codes from the QPAC table for the derived plants.
In Scope
Selected set codes for the selected sets in the source system

Out of Scope
Classification data
Prerequisites

● QM - Selected set
Source System
Not relevant
Target System
Q_CAT_SSET (Catalog Maintenance of Selected Sets)
Name of this migration object: S4_QM_SEL_SET_CODE
QPAM_SELSET_CODE_CREATE Create Selected St Code
Post-Processing
Not relevant.

Create/Edit QS51
Display QS53
Further Information
1.123 RE-FX - Real estate contract
Purpose
This migration object enables you to migrate real estate contract data from the source ERP system to the
Related Business Object: Real Estate Contract
Business Object Component/Area Component: RE-FX
Business Object Definition A contract in real estate management. The real estate con
tract is used to record all contracts related to real estate.
Examples:
● Lease-out
● Lease-in
● Purchase
● Maintenance
● Service
● Security deposit agreement

Available Scenarios
Selection Criteria
All real estate contracts from the VICNCN table are automatically selected for the company codes that you
In Scope
● General data
● Partners
● Term data
● Objects
● Differing measurements
● Posting parameters
● Conditions
● Adjustment data
● Option rate methods
● Resubmission data
● Overviews
● Sales-based rent agreement data
● CO settlement rule data
Out of Scope
● Document management data
● Memos
● Profit segment data for CO settlement rules
● Settlement participation data
● Assignments of house bank accounts
Prerequisites

● FI - House bank
● PM - Equipment
● RE-FX - Building
● RE-FX - Land
● RE-FX - Rental object
Source System
Not relevant
Target System
● FI_GRU_BUK (Real Estate: property - Authorization for Company Code/Business Entity)

● FI_RE_BRGRP (Real Estate: Authorization Group)
● FI_REBD_AO (Real Estate: Architectural Object)
● K_VRGNG (CO: Business Transaction, Actual Postings and Planned/Actual Allocations)
Name of this migration object: S4_REFX_CONTRACT
● BAPI_RE_CN_CREATE Create Real Estate Contract

● BAPI_RE_CN_CHANGE Change Real Estate Contract
● BAPI_RE_CN_SALES_REP_REPORT Enter Sales Reports
Virtual Tables
● VITMPY_OBJ: To handle posting terms

● MEASCN_OBJREF: To handle contract measurements
● OBJ_REF: To handle objects
● ART_CAL_DIST_OBJ: To handle conditions

● AS_CO_SETTLE: To handle CO settlement rule allocations
● AS_SSTAT: To handle system statuses
● AS_USTAT: To handle user statuses
Post-Processing
Not relevant

Create RECN
Change RECN
Display RECN
Further Information
1.124 RE-FX - Architectural object
Purpose
This migration object enables you to migrate architectural object data from the source ERP system to the
Related Business Object: Architectural Object

Business Object Component/Area User Menu Path: Accounting Flexible Real Estate
Management Master Data Architecture Master Data
Process Architectural Object
Component: RE-FX-BD
Business Object Definition A part of an architectural view. Each architectural object

must be assigned to an architectural object type (for exam
ple, room or building). Architectural objects can be assigned
to objects of the usage view.
Available Scenarios
Selection Criteria
In Scope
● General data
● Number assignments
● Additional data
● Land data
● Building data
● Dates
● Partner data
● Measurements
● Fixtures/Fittings characters
● Assignment information
● Usage data
● Overview data
Out of Scope
● Change documents for objects

● Document management data
● Internal number range data

Prerequisites
● PM - Maintenance order
● PP - Production order
● PS - Project
Source System
Not relevant
Target System
F_REBD_AO (Real Estate: Architectural Object)
Name of this migration object: S4_REFX_ARCH_OBJECT
BAPI_RE_AO_CREATE Create Architectural Object
BAPI_RE_AO_CHANGE Change Architectural Object
Virtual Tables
● AS_OBJASS: To handle object assignments

● AS_AO_PARENT: To handle architectural object hierarchies

Post-Processing
Not relevant

Create REBDAO
Change REBDAO
Display REBDAO
RE Navigator RE80
Further Information
1.125 RE-FX - Building
Purpose
This migration object enables you to migrate building data from the source ERP system to the target SAP S/
transfers data to the target system using Business Application Programming Interfaces (BAPIs)..
Related Business Object: Building
Management Master Data REBDBU - Process
Building
Component: RE-FX-BD

Business Object Definition An object or parts of an object on the basis of which rooms
or areas (for example, apartments, warehouses, stores) are
rented. A building is part of a business entity.
Available Scenarios
Selection Criteria
This migration object automatically selects all building data from the VIBDBU table for all company codes
In Scope
● General data
● Dates
● Additional data
● Fixtures/fittings data
● Values
● Infrastructure data
● Measurements
● Option rate methods data
● Partner data
● Assignments data
● Architecture data
Out of Scope
● Document management
● Memo data
● Profit segment assignments under CO Settlement Rule

Prerequisites
● PP - Production Order
● PS - Project
● RE-FX - Business entity
Source System
Not relevant
Target System
FI_GEB_BUK Real Estate: Building - Auth. for CoCd/business entity
F_RE_BRGRP Real Estate: Authorization Group
F_REBD_AO Real Estate: Architectural Object
K_VRGNG CO Bus. Trans., Actual Postings and Plan/act. Allocations
Name of this migration object: S4_REFX_BUILDING
BAPI_RE_BU_CREATE: Create Building
BAPI_RE_BU_CHANGE: Change Building.
Virtual Tables
● AS_SYSTEM_SYSTEM: To handle system status

● AS_USER_STATUS: To handle user status
● AS_CO_SETTLE: To handle CO settlement rules
● AS_PROF_BUS: To handle status profiles
Post-Processing
Adjust number ranges to the required values in the SAP S/4HANA system. If the number range is configured as
internal, clear the values in the MAP_REBDBUNO value mapping.

Create/Change/Display Building REBDBU
RE Navigator RE80
1.126 RE-FX - Business entity
Purpose
This migration object enables you to migrate business entity data from the source ERP system to the target
Related Business Object : Business Entity
Management RE Navigator Business Entity
Component: RE-FX-BD

Business Object Definition A grouping characteristic used for a real estate object. Real
estate objects can be logically grouped depending on their
economic (business) purpose or geographical location.
Available Scenarios
Selection Criteria
All business entities from the VIBDE table are automatically selected for the company codes you specified
In Scope
● General data
● Reference factors
● Measurement data
● Partner data
● Assignment data
● Architecture information
● Overviews
Out of Scope
● Internal number ranges

● Profit segments for CO settlements rules
Prerequisites

● PM - Equipment
● PS - Project
● RE-FX - Architectural object
Source System
Not relevant
Target System
FI_GRU_BUK (Real Estate: property - Authorization for Company Code/Business Entity)
F_RE_BRGRP (Real Estate: Authorization Group)
K_VRGNG (CO: Bus. Trans., Actual Postings and Plan/Act. Allocations)
Name of this migration object: S4_REFX_BUSINESS_ENTITY
BAPI_RE_BE_CREATE Create Business Entity
REBD_BAPI_BUS_ENTITY Change Business Entity
Virtual Tables
● AS_OBJASS: To handle object assignments of business entities

● AS_CO_SETTLE: To handle CO settlements rules

Post-Processing
Not relevant
Create REBDBE
Change REBDBE
Display REBDBE
Further Information
1.127 RE-FX - Land
Purpose
This migration object enables you to migrate land data from the source ERP system to the target SAP S/
Related Business Object: Land

Management Master Data Process Land
Component: RE-FX-BD
Business Object Definition Lot or site not including the buildings erected on it. Land be
longs to the business entity.
Available Scenarios
Selection Criteria
All land data from the VIBDPR table is automatically selected for the company codes you specified when
In Scope
● General data
● Building law and usage
● Values
● Productive holdings
● Infrastructure
● Measurements
● Partners
● Assignments
● Architecture
● Resubmission
● CO settlement rules
 Note
Profit segment information from the CO Settlement Rule screen is not migrated.
Out of Scope

Prerequisites
Before you can start the migration process, ensure that you have created land register data in the target
system.
You have also migrated or defined settings in the following migration objects:
● PS - Project
● RE-FX - Architectural object
● RE-FX - Business entity
Not relevant
● FI_GRU_BUK (Real Estate: Property - Authorization for Company Code/Business Entity)

● F_RE_BRGRP (Real Estate: Authorization Group)
● F_REBD_AO (Real Estate: Architectural Object)
● K_VRGNG (CO: Business Transaction, Actual Postings and Planned/Actual Allocations)
Name of this migration object: S4_REFX_LAND
BAPI_RE_PR_CREATE: Create Land
BAPI_RE_PR_CHANGE: Change Land

Virtual Tables
● AS_SSTAT: To handle system status

● AS_USTAT: To handle user status
● AS_CO_SETTLE: To handle CO settlement rules
Post-Processing

Create REBDPR
Change REBDPR
Display REBDPR
Further Information
1.128 RE-FX - Rental object
Purpose
This migration object enables you to migrate rental object data from the source ERP system to the target SAP
Related Business Object: Rental Object

Business Object Component/Area Component: RE-FX-BD
Business Object Definition An object that is leased out as a single entity. Rental objects
can be:
● Rental units (unflexible objects that can only be leased

out as a unit such as apartments and retail stores)
● Pooled spaces (flexible objects that can be leased out
either as a whole or divided into rental spaces). They
cannot be leased out in their own right.
● Rental spaces
Available Scenarios
Selection Criteria
All rental objects from the VIBDRO table are automatically selected for the company codes that you specified
In Scope
● General data
● Dates
● Additional data
● Fixtures/fittings data
● Values
● Measurements
● Option rate methods data
● Partners data
● Assignments data
● Architecture data
Out of Scope

● Memo data
● Profit segment assignments (CO-Settlement rule)
Prerequisites
● PS - Project
● REFX - Building
● REFX - Business entity (RE-FX)
● REFX - Land
Source System
Not relevant
Target System
FI_ME1_BUK (Real Estate: Rental Unit - Authoriz.for CoCd/Busines Entity)
F_RE_BRGRP (Real Estate: Authorization Group)
K_VRGNG CO (Bus. Trans., Actual Postings and Plan/Act. Allocations )
Name of this migration object: S4_REFX_RENTAL_OBJECT

BAPI_RE_RO_CREATE: Create Rental Object
BAPI_RE_RO_CHANGE: Change Rental Object
Virtual Tables
● AS_SYSTEM_SYSTEM : To store system statuses

● AS_USER_STATUS : To store user statuses
● AS_CO_SETTLE: To store CO settlement rules
● AS_OBJASSIGN: To store object assignments
Post-Processing
Adjust number ranges to the required values in the SAP S/4HANA system. If the number range is configured as
internal, clear the values in the MAP_REBDRONO mapping task in the migration project.
Process Rental object REBDRO
RE Navigator RE80
Further Information
1.129 SD - Sales inquiry

Purpose
This migration object enables you to migrate sales inquiry data from the source ERP system to the target SAP
Related Business Object: Sales Inquiry
Sales Inquiry
Component: SD-SLS-GF
Business Object Definition A customer request to the company for a quotation or sales
information that is not binding. The request can refer to ma
terials or services, conditions, and, if necessary, delivery
deadlines. It is accepted by the sales area that is then re
sponsible for any further processing.
Available Scenarios
Selection Criteria
migration scope. This migration object automatically selects relevant sales inquiries from the VBAK table for
the derived sales organizations.
● The SD document category (VBAK-VBTYP) is "A" (inquiry) AND

● The overall processing status (VBUK-GBSTK) is "A" (not yet processed) or ' ' (not relevant).
In Scope
● Sales and distribution document numbers

● Inquiry header data
● Logical system information for the sender system
● Number of generated documents
● Item data
● Document partners
● Schedule line data
● Conditions
● Header and item texts

Out of Scope
● Internal control parameters

● Conversion of partner functions for document types
Prerequisites
● Customer
● Product
Source System
Not relevant
Target System
V_VBAK_AAT (Sales Document: Authorization for Sales Document Types)
V_VBAK_VKO (Sales Document: Authorization for Sales Areas)
Name of this migration object: S4_SD_SALES_INQUIRY
BAPI_INQUIRY_CREATEFROMDATA2: Sales Inquiry: Create Sales Inquiry
Post-Processing

Create VA11
Change VA12
Display VA13
Further Information
1.130 SD - Customer quotation
Purpose
This migration object enables you to migrate customer quotation data from the source ERP system to the
Related Business Object: Customer Quotation
Business Object Component/Area User Menu Path: SAP Menu Logistics Sales and
Distribution Sales Quotation
Component: SD-SLS
Business Object Definition An offer by a sales area to a customer for delivery of goods
or services according to fixed conditions. The offer is legally
binding for the company for a certain period of time. A cus
tomer quotation can refer to a business partner sales activ
ity or it can be used by the sales area to reply to a customer
inquiry.
Available Scenarios

Selection Criteria
migration scope. This migration object automatically selects customer quotations from the VBAK table for the
derived sales organizations if the following conditions are met:
● The SD document category (VBAK-VBTYP) is "B" (quotation) AND

● The overall processing status of the SD document (VBUK-GBSTK) is "A" (not yet processed)
In Scope
● Conditions
● Distribution document numbers
● Document partners
● Internal item number assignments
● Item data
● Logical system (source system)
● Number of generated documents
● Quotation headers
● Texts
Out of Scope
● Customer quotations that are completely processed

● Customer quotations that are not yet processed
Prerequisites
● Customer
● Product

Source System
Not relevant
Target System
Name of this migration object: S4_SD_CUSTOMER_QUOTATION
BAPI_QUOTATION_CREATEFROMDATA2: Customer Quotation: Create Customer Quotation
Virtual Tables
● QUOTATION_HEADER_IN: To store quotation header information

● QUOTATION_ITEMS_IN: To store item details
● QUOTATION_SCHEDULES_IN: To store the schedule lines of delivery items
● QUOTATION_CONDITIONS_IN: To store pricing condition types
● RETURN: To import result messages after quotation creation
● QUOTATION_PARTNERS: To store details of customers assigned to the quotation
● QUOTATION_TEXT: To store long texts of header and item data
Post-Processing
Not relevant

Create VA21

Change VA22
Display VA23
Further Information
1.131 SD - Customer material
Purpose
This migration object enables you to migrate customer material data from the source ERP system to the target
technique transfers data to the target system using Application Programming Interface (API).
Related Business Object: Customer Material Info Record
Master Data Agreements Customer Material
Information
Component: SD
Business Object Definition Customerspecific information about a sales material. The

customer material can also be used as an entry aid in sales
processing.
Available Scenarios
Selection Criteria
migration scope. This migration object automatically selects materials from the KNMT table for the derived
sales organizations.

In Scope
● Basic data
● Long texts
Out of Scope
Not relevant
Prerequisites
● Class
● Characteristic
● MM - Product
● SD - Customer master
Source System
Not relevant
Target System
● C_TCLA_BKA (Authorization for Class Types)

● C_KLAH_BKL (Authorization for Classification)
● C_TCLS_MNT (Authorization for Characteristics of Org. Area)
● V_KNA1_VKO (Customer: Authorization for Sales Organizations)
Name of this migration object: S4_SD_CUSTOMER_MATERIAL

CNV_PE_S4_SD_CUSTMAT_CREATE Create Customer Material Records
Virtual Tables
● TEXT_DATA: To identify text information

● CLASS_DATA: To identify classification data
● ALLOCVALUESNUM: To identify numeric allocation values
● ALLOCVALUESCHAR: To identify character allocation values
● ALLOCVALUESCURR: To identify currency allocation values
Please note that virtual tables do not exist in the database.
Post-Processing
Create VD51
Change VD52
Display VD53
Further Information
1.132 SD - Sales contract

Purpose
This migration object enables you to migrate sales contract data from the source ERP system to the target SAP
Related Business Object: Sales Contract
Sales Contract
Component: SD
Business Object Definition An outline agreement that contains special conditions nego
tiated between the supplier 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 or
der to release materials or services from the amount or
value agreed in the contract.
Available Scenarios
Selection Criteria
migration scope. This migration object automatically selects all sales contracts from the VBAK table for the
derived sales organizations.
 Note
The relevant sales document category (VBAK-VBTYP) for this migration object is G ("Contract").
In Scope
● Header data
● Item data
● Partner data
● Condition data
● Contract data
● Long texts
● Partner addresses
● Custom fields

 Note
For this migration object, the Custom Fields and Logic app is available. If you use the app to enhance your
business object with custom fields, these custom fields are automatically available in the Custom Fields
mapping task. For more information, see the Custom Fields and Logic documentation in the SAP S/4HANA
section of the SAP Help Portal (help.sap.com).
Ensure that there are no changes to the custom fields during migration.
Out of Scope
● Sales contract configurations

○ Reference data
○ Instances
○ Parts of specifications
○ BLOB internal data
○ Variant condition keys
○ Reference items/instances
● Sales contract keys
● Userdefined fields in the sales contract
● Industryspecific solution fields
● Document flows
● Output types
● Billing plans
Prerequisites

● Customer
● Product
Source System

Not relevant
Target System
● V_VBAK_VKO (Create/Update/Display of sales documents using the sales areas)

● V_VBAK_AAT (Create/Update/Display of sales documents using the sales document type)
● V_VBAK_CCD (Create/Update/Display of sales document payment cards)
Name of this migration object: S4_SD_SALES_CONTRACT
BAPI_CONTRACT_CREATEFROMDATA Create Customer Contract
Virtual Tables
● VBAK_TEXT: To handle long texts for sales contracts

● VBKD_ITM: To handle item business data
Post-Processing
Not relevant

Change VA42
Display VA43
Further Information

1.133 SD - Sales order (only open SO)
Purpose
This migration object enables you to migrate open sales order data from the source ERP system to the target
Related Business Object: Sales Order
Sales Order
Component: SD
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 sales
area that is then responsible for fulfilling the contract.
Available Scenarios
Selection Criteria
migration scope. This migration object automatically selects sales orders from the VBAK table for the derived
sales organizations if the following conditions are met:
● The SD document category (VBAK-VBTYP) is "C" (order) AND

● The overall processing status of the document (VBUK-GBSTK) is "A" (not yet processed) AND
● The overall delivery status for all items (VBUK-LFGSK) is "A" (not yet processed) AND
● The overall processing status of the SD document item (VBUP-GBSTA) is "A" (not yet processed) AND
● The Overall Delivery Status of the Item (VBUP-LFGSA) field is "A" (not yet processed) for all sales document
items.
In Scope
● Order header data

● Item data
● Partner data
● Conditions
● Texts
● Custom fields
 Note
For this migration object, the Custom Fields and Logic app is available. If you use the app to enhance your
business object with custom fields, these custom fields are automatically available in the Custom Fields
mapping task. For more information, see the Custom Fields and Logic documentation in the SAP S/4HANA
section of the SAP Help Portal (help.sap.com).
Ensure that there are no changes to the custom fields during migration.
Out of Scope
● Partial sales order items

● Configurable items
● Return orders
● References to other sales documents
Prerequisites
● Customer
● Product
Manual Pricing
In Customizing for Sales and Distribution, go to the V/08 transaction or go to Basic Functions Pricing
Pricing Control Define and Assign Pricing Procedures . Select the Set Pricing Procedures activity. Open the
relevant pricing procedure assigned to the sales document to be migrated. Set the condition types to be
processed manually by selecting Manual only.
Carrying out the Customizing described above enables manual pricing for price determination. As a result, this
migration object transfers the as-is conditions from the source ERP system to the target SAP S/4HANA
system.

Source System
Not relevant
Target System
● V_VBAK_VKO (Sales Document: Authorization for Sales Areas)

● V_VBAK_AAT (Sales Document: Authorization for Sales Document Types)
Name of this migration object: S4_SD_SALES_ORDER
BAPI_SALESORDER_CREATEFROMDAT2 Create Sales Order
Virtual Tables
● ORDERTEXT: To store sales order texts

● PRPS_HDR: To store WBS elements assigned to the sales order headers
● KONV_CUST: To store condition information
● VBKD_ITM: To store business data for sales document items
Post-Processing
Adjust the pricing procedures to the required settings in the SAP S/4HANA system.
Change VA02
Display VA03

Further Information
1.134 TRM - Additional flow
Purpose
This migration object enables you to migrate additional flow data for a TRM transaction from the source ERP
Interfaces (BAPIs).
Related Business Objects: Cap/Floor, Commercial Paper, Deposit at Notice, Interest Rate Swap, Foreign
Exchange Swap Contract, Foreign Exchange Collar Contract
Transaction Manager Money market Trading Edit
Business Object Definition The concept of flow types allows you to define other flows -
such as charges or commissions (absolute or proportional) -
for the individual product types. These other flows are cre
ated with each transaction.
The flow types that are assigned are displayed in the other
flows area as a default. You also still enter the payment
amount, currency with the direction and the payment date.
Available Scenarios
Selection Criteria
All active transactions with the active activity categories Contract, Rollover, and Settlement for which
additional flows exist are automatically selected for the company codes you specified when defining the
migration scope.

 Note
For a financial transaction, this migration object creates additional flows in the target system.
In Scope
Other flow data
 Note
Additional flow data is migrated for the following product types:
● Foreign exchange swap

● Interest rate swap
● Foreign exchange collar contract
● Commercial paper
● Cap/floor
● Deposit at notice
Out of Scope
Derived flows
 Note
You need to manually create the derived flows in the target system.
Prerequisites
● Flow types are assigned to the corresponding product types in the target system
● The financial transaction is present in the target system
● TRM - Cap/Floor
● TRM - Commercial paper

● TRM - Foreign exchange collar contract
● TRM - Foreign exchange swap contract
● TRM - OTC Interest rate derivative swap
Source System
Not relevant
Target System
Name of this migration object: S4_FI_TRM_ADDITIONAL_FLOW
BAPI_FTR_ADDFLOW_CREATE Create Other Flow
Virtual Tables
FLTR_ADD_FLOW_TRN: To store details of flow types for the financial transaction.
Post-Processing
Not relevant


Create FTR_EDIT
Change FTR_EDIT
Display FTR_EDIT
Further Information
1.135 TRM - Bank guarantee
Purpose
This migration object enables you to migrate bank guarantee data from the source ERP system to the target
SAP S/4HANA system. The data is migrated based on the default selection criteria set for the migration object.
Interfaces (BAPIs).
Related Business Object: Bank Guarantee
Transaction Manager Trade Finance Trading
Business Object Definition A bank guarantee is a pledge on the part of a bank to make
good someone's debt in the event that they cannot pay it.
This type of guarantee is essentially an agreement to stand
as a cosigner on a transaction. In the event that the original
party cannot follow through, the bank can be called upon to
provide the payment.
Available Scenarios

Selection Criteria
Bank guarantee contracts with the active activity categories Contract and Settlement are relevant for
migration. The relevant bank guarantee contract data from the VTBFHA table are automatically selected for the
company codes you specified when defining the migration scope.
In Scope
● Structure data
● Other flows
● Payment details
● Contracts
 Note
This migration object migrates only bank guarantee data and does not migrate main flow details. Hence,
migrate this object before you migrate the TRM - Main flow detail migration object. Please ensure that
both migration objects are included in the same TRM migration project.
Out of Scope
● Orders
● Conditions
● Collateral
 Note
Transactions with the Terminate, Give Notice, and Roll Over statuses are not migrated.
Prerequisites
must match.

● House banks
● MM - Purchase order (only open PO)
Source System

● T_DEAL_LC (Authorization for Letter of Credit)
Target System

Name of this migration object: S4_FI_TRM_BANK_GUARANTEE

● BAPI_FTR_BG_DEALCREATE Completely Create Bank Guarantee

● BAPI_FTR_SETTLE Settle Financial Transaction
Virtual Tables
LONG_TEXT: To retrieve long texts.
Post-Processing
before the migration process. Please note that the information related to flows is already included in the
balance sheet, which was migrated from the source system to the SAP S/4 HANA system. If you post these
flows again in the receiver system, the migration tool updates the general ledger twice. This means that the
corresponding financial transaction, which was created in the receiver system during migration, needs to be
excluded from further processing of flows.
How to avoid double balances: To avoid the double posting of flows, you can go to the TBB1_LC transaction and
select the Flag Flows as Posted checkbox. This transaction enables the generation of posting logs. In the FI
Create FTR_CREATE
Change FTR_EDIT
Display FTR_DISPLAY
Further Information

1.136 TRM - Business partner role
Purpose
This migration object enables you to migrate business partner role data from the source ERP system to the
Related Business Objec: Business Partner
Management Treasury and Risk Management Business
Partners
Business Object Definition An organization or a private individual in which you have a

business interest.
In Treasury, you assign roles to your business partners, such

as counter party, issuer, or borrower. These roles control the
permitted functions for that type of business relationship.
Typical partners might be banks or a central treasury depart
ment.
Available Scenarios
Selection Criteria
All business partner roles from the BUT100 table are automatically selected for the company codes you
In Scope
● Issuer role (TR0150) data

● Counter party role (TR0151) data
● Depository bank role (TR0152) data

● Beneficiary role (TR0154) data
● Guarantor role (TR0200) data
Out of Scope
Not relevant
Prerequisites
Please migrate the Business partner migration object before you migrate the Business partner role
migration object. Please ensure that both migration objects are included in the same TRM migration
project. For more information, see SAP Note 2863145 .
● Customer
If a customer is assigned to the business partner, migrate the Customer migration object before you
migrate the Business partner role migration object. Please ensure that all migration objects are included
in the same TRM migration project.
● Supplier
If a supplier is assigned to the business partner, migrate the Supplier migration object before you migrate
the Business partner role migration object. Please ensure that all migration objects are included in the
same TRM migration project.
Source System
Not relevant
Target System
B_CCARD (Payment Cards)
T_BP_DEAL (FS Business Partner: Standing Instructions)

F_LFA1_GEN (Vendor: Central Data)
F_LFA1_APP (Vendor: Application Authorization)
F_LFA1_GRP (Vendor: Account Group Authorization)
Name of this migration object: S4_FI_TRM_BP_ROLES
CNV_OT_APPL_FI_TRM_BP_ROLE Business Partner Role for TRM
Post-Processing
Not relevant
Create BP
Change BP
Display BP
Further Information

1.137 TRM - Commercial paper
Purpose
This migration object enables you to migrate commercial paper master data from the source ERP system to
(BAPIs).
Related Business Object: Commercial Paper
Transaction Manager Money Market Trading Create
Business Object Definition An agreement between an investor and a borrower whereby

the borrower issues commercial paper for the investment
and agrees to repay the amount and a certain percentage to
the investor at the end of the contract. There is no interest
payment during the term of the contract in this type of
transaction.
Available Scenarios
Selection Criteria
Commercial paper with the active activity categories Contract and Settlement are relevant for migration. The
relevant commercial paper data from the VTBFHA table is automatically selected for the company codes you
specified when defining the migration scope
In Scope
● Structure data

● Contracts
Out of Scope
● Transactions with the Terminate and Give Notice statuses

 Note
The settle commercial paper feature is out of scope for simulation.
Prerequisites
must match.
● Business partners along with necessary authorizations and relevant data.
● All cash flows until the migration cutoff date are posted to Financial Accounting.
● FI - House bank
● TRM - Condition details

Source System
● F_T_TRANSB ((Treasury: Transaction Authorization))

● T_DEAL_P (Authorization for Product/Transaction Types)
Target System

Name of this migration object: S4_FI_TRM_COMMERCIAL_PAPER
Target System
BAPI_FTR_CP_CREATE Create Commercial Paper
BAPI_FTR_CP_SETTLE Settle Financial Transaction
Source System
BAPI_FTR_CP_GETDETAIL Details of Commercial Paper
Virtual Tables
● TAB_CP: To store commercial paper details

● TAB_CONTRACT: To store contract details
Post-Processing

and select the Flag Flows as Posted check box. This transaction enables the generation of posting logs. You can
Create TM31
Change TM32
Display TM33
Further Information
1.138 TRM - Foreign exchange spot/forward contract
Purpose
This migration object enables you to migrate foreign exchange spot/forward contract data from the source
ERP system to the target SAP S/4HANA system based on the default selection criteria set for the migration
object. This migration technique transfers data to the target system using Business Application Programming
Interfaces (BAPIs).
Related Business Object: Foreign Exchange Spot/Forward Contract

Transaction Manager Foreign Exchange Trading Forex
fast entry - spot
Business Object Definition Spot transaction is a binding agreement for the immediate
exchange of currency. Forward transaction is the obligation
to exchange two currencies at a future date at a rate fixed
upon contract conclusion.
Available Scenarios
Selection Criteria
Foreign exchange spot/forward contracts with the active activity categories Contract and Settlement are
relevant for migration. The relevant foreign exchange spot/forward contract data from the VTBFHA table is
automatically selected for the company codes you specified when defining the migration scope.
In Scope
● Structure data
● Other flows
● Payment details
● Contracts
 Note
Transactions with the Terminate or Expiration statuses are not migrated.
Out of Scope
● Rollover transactions
● Expiration transactions

● Premature settlement transactions
● Order/fixing activities
● FX hedge management data
● Correspondence information
 Note
You can simulate only the Create spot/forward transaction feature.
The settlement feature for the spot/forward transaction is out of scope for simulation.
Prerequisites
must match
● Business partners along with necessary authorizations and relevant data

Source System
Not relevant
Target System

Name of this migration object: S4_FI_TRM_FX_SPOT_FWD_CONTRACT
BAPI_FTR_FXT_DEALCREATE Completely Create a Forex Transaction
BAPI_FTR_SETTLE Settle Financial Transactions
Virtual Tables
AT_FOREX: To filter forex data
Post-Processing
Create TX01
Change FTR_EDIT
Display FTR_EDIT

Further Information
1.139 TRM - Interest rate instrument
Purpose
This migration object enables you to migrate interest rate instrument data from the source ERP system to the
Related Business Object: Interest Rate Instrument
Transaction Manager Money Market Create Financial
Transaction
Business Object Definition An interest rate instrument is a money market transaction

with additional structural characteristics, such as variable in
terest and installment repayment.
Available Scenarios
Selection Criteria
Interest rate instruments with the active activity categories Contract and Settlement are relevant for
migration. The relevant interest rate instrument data from the VTBFHA table is automatically selected for the
company codes you specified when defining the migration scope

In Scope
● Structure data
● Contract data
● Contract settlement data
 Note
Out of Scope
● Concluded deals
● Replaced deals
● Reversed deals
● Terminated deals
● Simulation deals
● Deals with single dates
● Default Risk Limit
 Note
If you have multiple steps for migration, you can simulate only the contract data feature.
The settlement feature is out of scope for simulation.
Prerequisites
must match.

● Business partners are present in the target system with the necessary authorizations
● House banks
Source System
Target System
T_POSS_ASS (Assign Attributes to Positions)
Name of this migration object: S4_FI_TRM_INT_RATE_INSTR
BAPI_FTR_IRATE_DEALCREATE Completely Create an Interest Rate Instrument
Virtual Tables
● INTERESTRATE: To store header data for the interest rate

● CONDITIONS: To store conditions related to the interest rate

Post-Processing
Create TM_51
Change TM_52
Display TM_53
Further Information
1.140 TRM - Security bond

Purpose
This migration object enables you to migrate bond contract data from the source ERP system to the target SAP
Related Business Object: Bond
Business Object Definition Bonds are used by companies or the public sector to gener
ate outside capital on the domestic or foreign capital market.
Available Scenarios
Selection Criteria
Bond contracts with the active activity categories Contract and Settlement are relevant for migration. The
relevant bond contract data from the VTBFHA table is automatically selected for the company codes you
In Scope
● Structure data
● Trading description
● Other flows
● Payment details
Out of Scope


 Note
Prerequisites
and target systems

Source System
Not relevant
Target System
T_DEAL_DP (Authorization for Securities Account)

Name of this migration object: S4_FI_TRM_BONDS
BAPI_FTR_SECURITY_DEALCREATE Completely Create a Security Transaction
BAPI_FTR_SECURITY_SETTLE Settle Financial Transactions
Post-Processing
Create TS01
Change TS02
Display TS03

Further Information
1.141 TRM - Security class
Purpose
This migration object enables you to migrate security class data from the source ERP system to the target SAP
Related Business Object: Security Class
Transaction Manager Securities Master Data Class
Business Object Definition In the SAP system, a security is a security class. The security
class data includes all the structure characteristics of a se
curity. You can portray the security types using the product
categories delivered with the system, such as:
● Bonds
● Stocks
● Investment certificates
In this class, all relevant conditions such issue data, condi

tion structure, and stock exchanges are defined.
Available Scenarios
Selection Criteria

In Scope
● Security classes of stocks, investment certificates, and bonds

● Search terms
● Basic data
● Conditions
● Exchanges
● Notices
● User data
● Swap data
 Note
Additional security classes are not migrated.
Out of Scope
● Special attributes belonging to the class

● Memos
● Market prices
Prerequisites
● Business partner (issuer) is defined with relevant authorizations

● Relevant product types and condition groups are configured
● The FVVW_ANLA number range object is configured and set to external number range for this object.
Business partner role
Source System

Target System
Name of this migration object: S4_FI_TRM_CLASS
BAPI_FP_CREATEFROMDATA Create Security
Virtual Tables
● CLASS: To store class attributes for the class

● REFERENCES: To store reference attributes for the class
● CONDITIONS: To store condition attributes for the class
● FORMULARS: To store formular attributes for the class
● NOTICE: To store notice attributes for the class
● SWAP: To store security swap attributes for the class
● PARTPAID: To store partly-paid attributes for the stocks
● LISTINGS: To store exchange attributes for the class
● INDICES: To store secondary indices for the class
● SHARECAPITALS: To store stock capital attributes for the class
● RATING: To store rating attributes for the class
Post-Processing
Not relevant

Create FWZZ
Change FWZZ
Display FWZZ

Further Information
1.142 TRM - Stock
Purpose
This migration object enables you to migrate stock contract data from the source ERP system to the target
Related Business Object: Stock
Business Object Definition Security that certifies a share in a stock corporation.
Available Scenarios
Selection Criteria
Stock contracts with the active activity categories Contract and Settlement are relevant for migration. The
relevant stock contract data from the VTBFHA table is automatically selected for the company codes you
In Scope
● Structure data
● Trading description

● Other flows
● Payment details
Out of Scope
● Correspondence information
 Note
Prerequisites
Before you can start the migration process, for example, make sure that these Customizing settings have been
made in the target system:
must match.

● FI - House bank

Target System

Name of this migration object: S4_FI_TRM_STOCKS
● BAPI_FTR_SECURITY_DEALCREATE: Completely Create a Security Transaction

● BAPI_FTR_SECURITY_SETTLE: Settle Financial Transaction
Post-Processing


Create TS01
Change TS02
Display TS03
Further Information
1.143 VC - Configuration profile
Purpose
This migration object enables you to migrate configuration profile data from the source ERP system to the
Related Business Object: Configuration Profile
Configuration Configuration Profile
Component: LO-VC
Business Object Definition An object in which you enter configuration parameters for a
configurable object. Each configuration profile must be as
signed to at least one class with a class type that supports
variant configuration.
Available Scenarios
Selection Criteria

In Scope
● Attributes
● Basic data of local dependencies
● Descriptions of local dependencies
● Documentation of local dependencies
● Source code of local dependencies
● Assignment of dependencies (local and global) to the configuration profile
 Note
Action dependency types are migrated to the target system as the procedure dependency types.
Out of Scope
● Dependencies marked for deletion

● Changes made to local dependencies with change numbers
● Advanced variant configuration
 Note
● In Preparation
● Locked
Prerequisites
● Class
● Product
 Note
● If you need to create the configuration profile with change numbers, create the change number first.
You can next migrate a configuration profile using the change number.

● If you don't assign the configurable object to a class, this migration object assigns the Locked status to
the configuration profile.
Source System
Not relevant
Target System
C_TCLA_BKA (Authorization for Class Types )
Name of this migration object: S4_LO_VC_CONFIG_PROFILE
VCH_CON_PROFILE_MAINTAIN Wrapper API for configuration profile maintenance
Virtual Tables
● CPRO_ATTR: To store configuration profile attributes

● CPDEP_DAT: To store basic data of object dependencies
● CPDEP_DESC: To store object dependency descriptions
● CPDEP_ORD: To store object dependency sequences
● CPDEP_SORC: To store the source code of object dependencies
● CPDEP_DOC: To store object dependency documentation
Post-Processing
This migration object sets the processing mode on the Configuration Initial Screen tab to Classic after data
migration.


Change Configuration Profile CU42
Display Configuration Profile CU43
Variant Configuration Modeling Environment PMEVC
Further Information
1.144 VC - Object dependency and dependency net
Purpose
This migration object enables you to migrate object dependency and dependency net data from the source
ERP system to the target SAP S/4HANA system based on the default selection criteria set for the migration
object. This migration technique transfers data to the target system using Application Programming Interfaces
(APIs).
Related Business Object: Global Object Dependency
Configuration Dependency Single Dependency
User Menu Path: Logistics Central Functions Variant
Configuration Dependency Dependency Net
Component: LO-VC
Business Object Definition The mutual interdependencies between objects. Object de
pendencies can be defined between characteristics and
characteristic values such that 21-speed gears are only al
lowed for racing bicycles. They can also be defined to ensure
that the correct BOM items and operations are selected
when an object is configured. They can be described in a de

Available Scenarios
Selection Criteria
In Scope
● Basic data
● Descriptions
● Long texts
● Source code
● Change numbers
Out of Scope
● Actions
● Rules
● Deleted global dependencies and dependency net
Prerequisites
● Characteristic
● Product
Source System
Not relevant
Target System
Not relevant

Name of this migration object: S4_CA_GTF_VC_OBJ_DEPENDENCY
VCH_DEPENDENCY_MAINTAIN Wrapper API for dependency maintenance
VCH_CONSTRAINT_NET_MAINTAIN Wrapper API for constraint net maintenance
VCH_CNET_CONSTRAINT_MAINTAIN Wrapper API for constraint maintenance
Virtual Tables
● DEPENDENCY_DATA: To handle the basic data of dependencies

● DESCRIPTION: To handle dependency descriptions
● SOURCE: To handle the source code for object dependencies
● DOCUMENTATION: To handle dependency long texts
● AS_AENNR: To handle change numbers
● AS_CONS: To handle constraints
● SOURCE_REF: To handle object dependency cross-references
Post-Processing
Not relevant

Create Dependency CU01
Change Dependency CU02
Display Dependency CU03
Create Dependency Net CU21
Change Dependency Net CU22
Display Dependency Net CU23
Further Information

1.145 Supplier
Purpose
This migration object enables you to migrate vendor (supplier) data from the source ERP system to the target
Related Business Object: Vendor
Purchasing Master Data Vendor
Component: MM
Business Object Definition A business partner who supplies goods and delivers them to
consumers/customers.
Available Scenarios
Selection Criteria
defining the migration scope. This migration object automatically selects all vendors from the LFA1 table for
the company codes and derived purchasing organizations.
In Scope
● General data with standard addresses

● International address versions
● General texts
● Accounting texts
● Purchasing data
● Purchasing texts
● Contact persons

● Extensions of existing vendors with new organizational levels
● Extensions of existing customers as suppliers with the same business partner numbers
 Note
● If a vendor in the source system is extended to multiple company codes, after data migration, the
supplier in the target system is extended only to the participating company codes.
● If a vendor in the source system has multiple purchase organizations, after data migration, the supplier
in the target system contains only the selected purchase organizations.
Out of Scope
● Documents assigned to the vendor

● Classifications
● Updates of existing fields
● Extensions of withholding tax data to existing company codes
● Extensions of existing addresses
● Extensions of purchasing organizations belonging to existing company codes
Prerequisites
Source System
Before you can start the migration process, ensure that you have maintained the values for all fields defined as
mandatory in the target system. Otherwise, errors may occur after migration. Alternatively, blank values are
populated in the mandatory fields after data migration.
Target System
● Provided the vendor account group in the Vendor Account Group (MAP_KTOKK) mapping task. Doing so
enables the migration object to determine the business partner groupings and roles from the following
Customizing paths:

Business Partner Settings Settings for Vendor
Integration Define BP Role for Direction Vendor to BP

Synchronization Business Partner Settings Settings
for Vendor Integration Field Assignment for Vendor
Integration Assign Keys Define Number Assignment
for Direction Vendor to BP
● Registered the CVI_EI_INBOUND_REQ_ACTIVATE function module using the transaction code

CRMC_BUT_CALL_FU with the following entries:
Event CRM Inbound
Call Selected
● Bank
If there is a business partner linked to the vendor in the source system, please migrate the Business
partner migration object before you migrate the Supplier migration object. Please ensure that both
● Customer
○ If the customer and vendor refer to the same business entity in the source system, please migrate the
○ If the business partner is linked to both the customer and the vendor in the source system, please
migrate the Business partner migration object first, followed by the Customer migration object and
finally the Supplier migration object. Please ensure that all three migration objects are included in the
same migration project.
● FI- G/L account
Source System
Not relevant
Target System

To carry out the migration, assign the following role or roles to the user:
● F_LFA1_GEN Vendor Central Data

● F_LFA1_BUK Vendor Authorization for Company Codes
● F_LFA1_APP Vendor Application Authorization
● F_LFA1_GRP Vendor Account Group Authorization
● F_LFA1_BEK Vendor Account Authorization
● M_LFM1_EKO Purchasing Organization in Supplier Master Record
Name of this migration object: S4_MM_PUR_VEND_MAST_CRE
CMD_MIG_BP_CVI_CREATE Create New Business Partners with CVI and New Segments Insertion
This migration object derives the business partner category based on the vendor title defined in the TSAD3
Customizing table. If the vendor title in the source system is company, for example, the business partner
category is organization.
Handling Referenced Vendor Accounts
Migration Context Migration Object Behavior User Action Required
If the vendor account has referenced This migration object migrates the ven 1. Set the referenced vendor ac
vendor accounts such as goods sup counts for migration or manually
dor account, but not the referenced
plier or invoicing party in the source create the referenced vendor ac
vendor accounts. The migration ends in
system, but only the vendor account is counts in the target system.
set for migration. error.
2. Migrate the migration object again.
If the vendor account has referenced This migration object migrates all ven Not relevant
vendor accounts in the source system, dor accounts along with the references
and all relevant vendor accounts are set among the relevant vendor accounts.
for migration.
If the vendor account has referenced This migration object migrates the ven 1. Migrate the migration object again.
vendor accounts in the source system, dor account first and the referenced 2. This migration object updates ref
and all relevant vendor accounts are set vendor accounts later. The migration erences among the relevant vendor
for migration. ends in error. accounts.
Virtual Tables
● LFB1_TEXT: To store keys for accounting texts

● LFB1_TEXT_DATA: To store accounting text lines
● LFM1_TEXT: To store keys for purchasing texts
● LFM1_TEXT_DATA: To store purchasing text lines
● TAXNUMBER: To store tax number information

● ADRC_V: To store the contact person's address information
● ADR2_V: To store the contact person's telephone numbers
● ADR3_V: To store the contact person's fax numbers
● ADR4_V: To store the contact person's teletex numbers
● ADR5_V: To store the contact person's telex numbers
● ADR6_V: To store the contact person's e-mail addresses
● ADR7_V: To store the contact person's remote mail addresses
● ADR8_V: To store the contact person's X.400 addresses
● ADR9_V: To store the contact person's RFC destinations
● ADR10_V: To store the contact person's printer addresses
● ADR11_V: To store the contact person's SSF addresses
● ADR12_V: To store the contact person's FTP and URL addresses
● ADR13_V: To store the contact person's pager addresses
● ADRT_V: To store the contact person's communication data texts
● ADRU_V: To store the contact person's communication usages
● ADRCT_V: To store the contact person's address texts
● KNVK_TEXT: To store the contact person's keys for long texts
● KNVK_TEXT_DATA: To store the contact person's text lines
● LFA1_TEXT: To store keys for head office texts
● LFA1_TEXT_DATA: To store head office text lines
● LFZA_HDR: To store general information for permitted alternative payees
If the customer and the vendor refer to Customer and Customer Number (MAP_KUNNR) and
system Vendor Vendor Number (MAP_LIFNR) respec
tively
If the business partner is related to both Business partner, Business Partner (MAP_BU_PARTNER)
the customer and vendor in the source
system Customer and Customer Number (MAP_KUNNR) and
Supplier Vendor Number (MAP_LIFNR) respec

tively
If the vendor is not related to the busi Vendor Vendor Number (MAP_LIFNR)
ness partner or the customer in the
source system
If the vendor account group is assigned Vendor Vendor Number (MAP_LIFNR)

to an external number range
If the vendor account group is assigned Vendor (Enter a blank.) Vendor Number (MAP_LIFNR)
to an internal number range

Post-Processing
Not relevant
Further Information
1.146 AFS - Purchase grid condition record
Purpose
This migration object enables you to migrate purchase grid condition records from the source AFS system to
Related Business Object: Purchase Grid, Condition Record
Business Object Component/Area Component: IS-AFS-BD

Business Object Definition Purchase grid: A subset of a master grid. With the aid of pur
chase grids, you specify which of the grid values you defined
in the master grid for an AFS material are permitted in pur
chasing. Purchase grids are always uniquely derived from
master grid and contain its grid values at most.
Condition record: Data record with input and output values

for a task. The condition record is created or changed with
condition record maintenance and selected in the determi
nation process. The output values are dependent on chosen
input values (for example, customer, customer group, prod
uct) and are valid for a certain time period. A condition re
cord can, for example, contain a specific free-goods discount
for a particular product quantity, or a specific discount for a
particular business partner.
Available Scenarios
Selection Criteria
If the application type is "M", purchase grid condition records in the J_3AGRHD table are automatically selected
for all key combinations.
In Scope
● Condition maintenance groups

● Condition types
● Condition record headers for material grids
● Condition record line items for material grids
Out of Scope
BAPI Extensions for custom fields
Prerequisites

Relevant access sequence is active for the migration specific condition types.
● AFS - Article
● Supplier
Source System
Not relevant
Target System
/SAPCND/CM (Condition Technique: Condition Maintenance (Generic Part))
Name of this migration object: S4_AFS_MM_PURCH_GRID_APP_VAR
FSH_API_VAR_CONDREC_CREATE Fashion grid condition records: create FM
Virtual Tables
● APP_CONDREC_HDR: To store header data for condition records

● APP_CONDREC_ITEM: To store item data for condition records
Post-Processing
Not relevant

Create/Change/Display FSH_VAR_MM
Further Information
1.147 AFS - Sales grid condition record
Purpose
This migration object enables you to migrate sales grid condition records from the source AFS system to the
Related Business Objects: Sales Grid, Condition Record
Business Object Component/Area User Menu Path: SAP Menu Logistics Sales and
Distribution Grid Control Data
Component: IS-AFS-SD
Business Object Definition Sales grid : A subset of a master grid that contains the grid
value variants of a material for use in sales.
Condition record: Data record with input and output values

for a task. The condition record is created or changed with
condition record maintenance and selected in the determi
nation process. The output values are dependent on chosen
input values (for example, customer, customer group, prod
uct) and are valid for a certain time period. A condition re
cord can, for example, contain a specific free-goods discount
for a particular product quantity, or a specific discount for a
particular business partner.
Available Scenarios

Selection Criteria
If the application type is "V", all sales grid condition records in the J_3AGRHD table are automatically selected
for all key combinations.
In Scope
● Condition maintenance groups

● Condition types
● Condition record headers
● Condition record items
Out of Scope
BAPI extensions for custom fields
Prerequisites
Relevant access sequence is active for condition types selected for migration.
● AFS - Article
● Customer
Source System
Not relevant
Target System

/SAPCND/CO (Condition Technique: Field Catalog, Condition Table)
/SAPCND/SS (Condition Technique: System Settings)
Name of this migration object: S4_AFS_SD_SALES_GRID_VARIANTS
FSH_API_VAR_CONDREC_CREATE: Fashion Grid Condition Records - Create FM
Virtual Tables
● CONDRECHEADERS: To store header data for condition records

● CONDRECITEMS: To store item data for condition records
Post-Processing
Not relevant

Create/Change/Display FSH_VAR_SD
Further Information
1.148 AFS - Value-added service

Purpose
This migration object enables you to migrate value added service data from the source AFS system to the
Related Business Object: Value-Added Service
Business Object Component/Area User Menu Path: Logistics Sales and Distribution AFS
Master Data Value-Added Services
Component: IS-AFS-SD
Business Object Definition Services that improve the appearance, attractiveness and
processing of a product, for example, packing, ticketing and
special service.
Available Scenarios
Selection Criteria
In Scope
● Ticketing/labeling data
● Packing data
● Special services data
 Note
Value-added service records that are marked for deletion are not migrated.
Out of Scope
● Status information
● Service hanger data
● Service hang tags
● Service packaging information
● Service ironing data

Prerequisites
You have migrated or defined settings in the AFS - Article migration object.
● AFS - Season
● Customer
● Supplier
Source System
Not relevant
Target System
/SAPCND/CO (Condition Technique: Field Catalog)
/SAPCND/SS (Condition Technique: System Settings)
Name of this migration object: S4_AFS_VALUE_ADDED_SERVICES
FSH_API_VAS_CONDREC_CREATE: Create API for VAS Condition Record Maintenance
Virtual Tables
● HEADERS: To store VAS header data

● ITEMS: To store VAS item data
● TEXTS: To store texts in multiple languages
VAS Service Types in the Target System
This migration object automatically populates VAS service type values in the target system using the VAS
Service Types (MAP_AFS_VAS_SERVICE_1) mapping task. The populated values are picked up from the
service types delivered by SAP.

Data Service Type Value
Packing 40
Service 30
Ticketing/Labeling 10 if the data starts with T*
20 if the data starts with any other value
Post-Processing
Not relevant

Create/Change/Display FSH_VAS_SD
Further Information
1.149 Class
Purpose
This migration object enables you to migrate class data from the source AFS system to the target SAP S/

Classification System Master Data
Component: CA-CL

Available Scenarios
Selection Criteria
This migration object automatically selects all classes from the KLAH table in the source system.
In Scope
● Class basic data

● Class standard data
● Class keywords
● Class characteristics
● Class long texts
● Class local dependencies
● Characteristic overwritten values
● Characteristic overwritten value local dependencies
Out of Scope
● Long texts for characteristic overwritten values

● Deletion of local dependencies for classes
● Deletion of local dependencies for characteristic overwritten values
● Changes of local dependencies for classes using change numbers
● Changes of local dependencies for characteristic overwritten values using change numbers
● Linkages between class and document
● Class global dependencies
● Characteristic overwritten value global dependencies
● Simulation

Prerequisites
● AFS - Characteristics for non-dimension

Source System
Not relevant
Target System
C_TCLA_BKA (Create/Validate)
Name of this migration object: S4_AFS_CA_CLASS_ECN
BAPI_CLASS_CREATE Create Class BAPI
BAPI_CLASS_CHANGE BAPI: Change Class
BAPI_CLASS_MAINT_LOCAL_DEP BAPI Klasse lokales Beziehungswissen zuordnen / löschen
CLCM_CLASS_FEATURE_KNOWL_VAL_O Overwrite Dependencies for Characteristic Value of Class
Virtual Tables
● AS_CLS_AENNR: To handle change numbers

● AS_CLASS_ALLOC_DEP: To handle class allocation dependencies
● AS_CLASS_LCL_DEP_DESCR: To handle local dependency descriptions for classes
● AS_CLASS_LCL_DEP_LTXT: To handle local dependency long texts for classes
● AS_CLASS_LONG_TEXTS: To handle class long texts
● AS_CLASS_OVERWR: To handle characteristic overwritten values for classes

● AS_CLS_OVRWR_DSCR: To handle characteristic overwritten descriptions for classes
Post-Processing
Not relevant
Create CL01
Change CL02
Display CL03
Further Information
1.150 Document info record (DMS)
Purpose
This migration object enables you to migrate document info record data from the source AFS system to the
Related Business Object: Document Info Record

Business Object Component/Area Component: CA-DMS ( Cross-Applications: Document Man
agement )
Business Object Definition Master record containing all information necessary to man
age a document. The data is sorted according to various cri
teria. A document info record contains both descriptive data
(such as language and laboratory) and control data (such as
change number and status).Document management at SAP
has two sides: on one side are the originals, which can be in
any format, and on the other side is the document info re
cord, which makes the originals available to other SAP ob
jects by means of object links.
Available Scenarios
Selection Criteria
 Note
All document info records are automatically selected for migration. You can restrict the selection in the
LTMOM transaction.
In Scope
● Document data for document info records

● Descriptions data for document info records
● Originals data for document info records
● Content versioning data
● Additional files
● Long texts
● Status information (not including status change logs)
 Note
● Document info records you set for deletion in the source AFS system are not migrated.
● Important: Migrate document info records in the same sequence as the sequence of versions to
ensure consistency.
Migrate classification details linked to the document info record separately using the Object classification
(general template) migration object.

You can migrate object links related to the document info record separately for the following migration
objects:
● AFS - Non-dimensional characteristic

● PM - Equipment
● PP - Routing
● PP - Sales order BOM
Out of Scope
● Classifications
● Document hierarchies
● Document structures
● Object links
● Change numbers
● Change logs
● Document distribution data
● Digital signature
● Status change logs
 Note
● If you have multiple steps for migration, you can simulate only this feature: Document info record
metadata.
● The following feature is out of scope for simulation: Originals/Attachments.
● During the migration phase, errors may occur for features that were not in scope during simulation
even though simulation was successful.
Prerequisites
Target System
● The Version Assignment checkbox is deselected for the relevant document types in the IMG path: Cross-
Application Components Document Management Control Data Define Document Types .
● Important: To ensure classification assignments for those document info records that have the Locked (S-
type) status, change the status type from Locked (S) to ' ' (space) for all document types in the Define
Document Types configuration. After migraton, change the status type back from ' ' (space) to Locked (S).
● In the mapping task for the Document Number (DOKNR) field, the number range is set to external for the
DOKUMENT number range object.

● No explicit changes made to mapping tasks for document versions
● Content repository and storage category to store the originals
● MIME types in the IMG path: Cross-Application Components Document Management General Data
Define Workstation Application
 Note
Storage type: The same content repository should be used in the source and target systems. If you are
using an SAP system database as the content repository in the source system, you should configure the
same content repository as an HTTP server pointing to the source R/3 system in the target system.
Source System
system:
 Note
Documents are checked into the source system to enable them to be opened by different users in the
target system
Its recommended that, Document types have one-to-one mapping in the source and target systems with
similar configurations
 Note
Implement SAP Note 685521 in the source system. The HTTP server you are pointing to in the target
system, is the host address in the source system.
Source System
Not relevant
Target System
C_DRAW_TCD( Authorization for document activities )
C_KLAH_BKL ( Authorization for Classification )
C_TCLA_BKA ( Authorization for Class Types )
C_DRAD_OBJ ( Create/Change/Display/Delete Object Link )
C_DRAW_TCS ( Status-dependent Authorizations for documents )

Name of this migration object: S4_AFS_CA_DIR
BAPI_DOCUMENT_CREATE2 Create Document
Virtual Tables
AS_LONGTEXTS: To store long texts for DIR
Post-Processing
After migration, select the Version Assignment checkbox on the Define Document Types: Overview screen for
each document type. (Relevant transaction: DC10)
After migration, change the status type back from ' ' (space) to Locked (S) for all document types with the DIR
Released status for classification assignments.
This migration object creates:
● Document info records and document statuses with the migration date
● Originals data with the user and date information from the source system
Find Document CV04N
Change CV02N
Display CV03N
Further Information

1.151 FI - SEPA Mandate
Purpose
This migration object enables you to migrate SEPA mandate data from the source AFS system to the target
Related Business Object: SEPA Mandate
Accounts Receivable Master Records SEPA
Mandates
Component: FI
Business Object Definition Payers use SEPA mandates to grant their vendors or service
agents the authorization to debit their account with the ap
propriate payment amount as part of a SEPA direct debit.
Available Scenarios
Selection Criteria
All SEPA mandates from the SEPA_MANDATE table belonging to Financial Accounting are automatically
selected for the company codes that you specified when defining the migration scope.
● ANWND is set to "F" (Financial Accounting)

● MVERS is set to "0" (Current version)
● SND_TYPE is set to "BUS3007" (Customer payer ID)
● REF_ID is set to space (Blank contract ID)
 Note
For the selection criteria listed above, the company codes are stored in the Recipient ID field of the
SEPA_MANDATE table.

In Scope
● Basic data
● Payer information
● Payment recipients
● Use data for SEPA mandates with the Active status
 Note
After migration, the system treats a SEPA mandate with blank use data as a new (first use) mandate.
During a payment run (F110), all related fields are updated for new mandates, thereby possibly increasing
the processing time of payment instructions. To avoid an increase in processing time, this object migrates
use data for SEPA mandates with an active status from the source ERP system to the target SAP S/4HANA
system. During the migration, document numbers and dates remain unchanged. For the purpose of easy
identification, the ID number of the Payment Run of First Use field is migrated with the value
"CNV_MC_MIG".
Out of Scope
● Previous versions of SEPA mandates

● One-time SEPA mandates where the sender type (business object) is Accounting Document Line Item
(BSEG).
 Note
● Canceled
● Locked
● Obsolete
● Completed
Prerequisites
● Customer
● FI - Bank account

Source System
Not relevant
Target System
F_SEPA_MDT (Authorization for Processing a Global SEPA Lock)
Name of this migration object: S4_AFS_FI_SEPA_MANDATE
SEPA_MANDATES_API_MIG_CREATE Create Mandate (Migration Cockpit)
Virtual Tables
USE_SEPA_MANDATE:To process the SEPA mandate use data
Post-Processing
You can update use data manually using the FSEPA_M4 transaction code.

Create FSEPA_M1
Change FSEPA_M2
Display FSEPA_M3
Further Information

1.152 VC - Object dependency and dependency net
Purpose
This migration object enables you to migrate object dependency and dependency net data from the source
AFS system to the target SAP S/4HANA system based on the default selection criteria set for the migration
(APIs).
Related Business Object: Global Object Dependency
Configuration Dependency Single Dependency
User Menu Path: Logistics Central Functions Variant
Configuration Dependency Dependency Net
Component: LO-VC
Business Object Definition The mutual interdependencies between objects. Object de
pendencies can be defined between characteristics and
characteristic values such that 21-speed gears are only al
lowed for racing bicycles. They can also be defined to ensure
that the correct BOM items and operations are selected
when an object is configured. They can be described in a de
Available Scenarios
Selection Criteria
In Scope
● Basic data
● Descriptions

● Long texts
● Source code
● Change numbers
Out of Scope
● Actions
● Rules
● Deleted global dependencies and dependency net
Prerequisites
● AFS - Article
Source System
Not relevant
Target System
Not relevant
Name of this migration object: S4_AFS_CA_GTF_VC_OBJ_DEPENDENCY
VCH_DEPENDENCY_MAINTAIN Wrapper API for dependency maintenance
VCH_CONSTRAINT_NET_MAINTAIN Wrapper API for constraint net maintenance
VCH_CNET_CONSTRAINT_MAINTAIN Wrapper API for constraint maintenance
Virtual Tables

● DEPENDENCY_DATA: To handle the basic data of dependencies
● DESCRIPTION: To handle dependency descriptions
● SOURCE: To handle the source code for object dependencies
● DOCUMENTATION: To handle dependency long texts
● AS_AENNR: To handle change numbers
● AS_CONS : To handle constraints
● SOURCE_REF : To handle object dependency cross-references
Post-Processing
Not relevant
Create Dependency CU01
Change Dependency CU02
Display Dependency CU03
Create Dependency Net CU21
Change Dependency Net CU22
Display Dependency Net CU23
Further Information
1.153 VC - Assign global dependency to characteristic

Purpose
This migration object enables you to assign global object dependencies to characteristics after migration from
the source AFS system to the target SAP S/4HANA system based on the default selection criteria set for the
Interfaces (APIs)
Related Business Object: Characteristics
Business Object Definition A special allocation function that enables allocation of global
dependencies to characteristics
Object dependencies can be defined between characteris

tics and characteristic values. They can be described in a de
Available Scenarios
Selection Criteria
All characteristics that have global object dependencies assigned are automatically selected from the CABN
table.
In Scope
● Global dependencies for characteristics

● Overwritten values for characteristics
Out of Scope
Deletion of global object dependencies in characteristics

Prerequisites
● AFS - Characteristics for dimension

● VC - Global object dependency and dependency net
Source System
Not relevant
Target System
C_CABN (Create Characteristics)
Name of this migration object: S4_AFS_CA_CHARACT_ASSGN_GLOB_OBD
CUKD_API_ALLOCATIONS_MAINTAIN Dependency Maintenance
Virtual Tables
● CABN_AS: To hold characteristics

● CAWN_AS: To hold characteristic values
● VCUOB_AS: To hold characteristic value assignments to dependencies
● VCUKB_AS: To hold maintenance information for characteristic value dependencies
● TCME_AS: To hold the validity of characteristics
● CCUOB_AS: To hold characteristic assignments to dependencies
● CCUKB_AS: To hold maintenance information for characteristic dependencies
Note that virtual tables do not exist in the database

Post-Processing
Not relevant

Further Information
1.154 VC - Assign global dependency to class
Purpose
This migration object enables you to assign global object dependencies to classes after migration from the
source AFS system to the target SAP S/4HANA system based on the default selection criteria set for the
Interfaces (APIs).

Available Scenarios
Selection Criteria

All classes that have global object dependencies assigned are automatically selected from the KLAHtable.
In Scope
● Class dependencies (Global)

● Overwritten value dependencies (Global)
● Deletion of global dependencies assignments
Out of Scope
Assignments without change numbers
 Note
During migration, this migration object checks whether class characteristics have been changed with a
change number in the target system.
If the changes have taken place, the migration object uses the change number information in the source
system to assign global dependencies to the Class object and the overwritten class values.
Prerequisites
● Class
Source System
Not relevant
Target System

Name of this migration object: S4_AFS_CA_CLASS_ASSIGN_GLOBJDEP
● BAPI_CLASS_ALLOC_GLOB_DEP BAPI Klasse globales Beziehungwissen zuordnen

● CLCM_CLASS_FEATURE_KNOWL_VAL_O Overwrite Dependencies for Characteristic Value of Class
Virtual Tables
● AS_CLS_AENNR: To store engineering change number data

● AS_CLASS_ALLOC_DEP: To store assignment data of class dependencies
● AS_CLASS_OVERWR: To store assignment data of overwritten values
Post-Processing
Not relevant
Create CL01
Change CL02
Display CL03
Further Information

1.155 AFS - Article
Purpose
This migration object enables you to migrate article data from the source AFS system to the target SAP S/
Related Business Object: Article
Material Master Material
Component: IS-AFS-MM/LO-FSH
Business Object Definition An article is the smallest unit or customer pack that can be
ordered independently and that cannot be split into smaller
units.
Available Scenarios
Selection Criteria
This migration object derives plants and sales organizations from the company codes you specified when
defining the migration scope. This migration object automatically selects materials from MARA table for the
derived plants and sales organizations.
In Scope
● Basic data
● Deletion indicator at the basic data level
● Deletion indicator at the plant data level
● Long texts
● Material data at the plant level
● Material description

● POS data
● Sales data
● Seasons data
● Segmentation-dependent data for:
○ Weights and volumes
○ General MRP
○ Quantities
○ Sales statuses
○ Storage
○ Valuations
○ Warehouses
● Units of measurement
● Valuation data
● Vendorspecific EANs
● Warehouse data
 Note
The Object classification (general template) migration object migrates classification data.
Out of Scope
● Planning data
● Forecast values
● Total consumption data
● Unplanned consumption data
● Layout modules
● Material change history
● Materials set for deletion
● Tables and fields in the customer name space
● Materials with item categories ERLA and LUMF
Note that the information provided here is not exhaustive.
Prerequisites

● Material groups with reference material
● Material groups assigned to the configuration class
● Customer data
● Supplier data
● AFS - Configuration class for material grid

● AFS - Dimensional characteristic
● AFS - Season
● AFS - Segmentation default
● AFS - Segmentation strategy
Source System
Not relevant
Target System
M_MATE_LGN (Material Master: Warehouse Numbers)
M_MATE_MAF (Material Master: Material Locks)
M_MATE_MAN (Material Master: Data at Client Level)
M_MATE_MAR (Material Master: Material Types)
M_MATE_NEU (Material Master: Create)
M_MATE_VKO (Material Master: Sales Organization/Distribution Channel)
M_MATE_WGR (Material Master: Material Groups)
M_MSEG_BMB (Material Documents: Movement Type)
Name of this migration object: S4_AFS_LO_ARTICLE_MASTER

BAPI_MATERIAL_MAINTAINDATA_RT Create and Change Material Master Data (Retail)
Virtual Tables
● MARC_VAL: To store grid-based plant data for AFS materials. (This migration object creates an AFS
material as a separate article in SAP S/4HANA.)
● SEG_MRP: To store grid-based MRP data belonging to the J_3AMAD table.
● MBEW_AFS: To store AFS valuation data not based on segments.
● MBEW_SEG_AFS:To store AFS valuation data based on segments.
● MARM_VAL: To store unit of measure data that have grid variations.
● SEG_WTVOL: To store segmentationspecific weights and volumes belonging to the /AFS/MARM table.
● MVKE_VAL: To store grid-based sales data
● SEG_MVKE: To store grid-based sales data based on segments.
● MLGN_AFS: To store grid-based warehouse data
● SEG_MLGN:To store grid-based warehouse data based on segments.
● MLGT_AFS: To store grid-based storage location data belonging to the /AFS/MLGT table.
● SEG_MLGT_AFS: To store storage location data belonging to the /AFS/MLGT table. (This migration object
selects storage location data based on grids and segments.)
● KORDX_VAL: To store the explosion of AFS materials to generic articles and variants (1+n).
● CHAR_VAL: To store the characteristic values responsible for grid creation.
● SEASONS: To store season data.
● MEAN_VAL: To store "de-masked" data from the MEAN table.
● MAT_LTEXT: To store material long texts.
Post-Processing
Not relevant
Create MM41
Change MM42
Display MM43

Further Information
1.156 AFS - Distribution curve
Purpose
This migration object enables you to migrate distribution curve master data from the source AFS system to the
Related Business Object: Distribution Curve
Business Object Definition A definition of quantity distribution ratios across different

variant-creating characteristics or across valid segmentation
value combinations.
You use distribution curves to distribute the quantities

across different variants if the quantity is provided at generic
article level.
Available Scenarios
Selection Criteria
In Scope
● Distribution profiles independent of materials

● Category profiles
● Grid profiles

Out of Scope
● Plant profiles
● Period profiles
● Default versions assigned at the plant level
Prerequisites

● AFS - Segmentation default values
Source System
J_4KCATW (Authorization for Whole Category Field)
Target System
FSH_DPR (Authorization for Distribution Curve)
Name of this migration object: S4_AFS_LO_DISTRIBUTION_CURVE
FSH_DPR_MAINTAINDATA_RFC RFC to Maintain Distribution Curve
Virtual Tables
● CABN_NEW: To store characteristic names

● DIST_CURVE_AS: To store distribution curves

Source System
In SAP AFS, you can define your distributions using these distribution profile types:
● Plant
● Category
● Grid (based on a mastergrid)
● Period
 Note
● Distribution profiles based on categories are always linked to a coverage strategy.

● Distribution profiles based on grids are linked to a mastergrid.
Target System
In SAP S/4HANA, the distribution profiles are referred to as distribution curves and have these distribution
curve types:
● Segments
● Variants (based on a configuration class)
 Note
● Categories in SAP AFS are termed as segments in SAP S/4HANA and mastergrids in SAP AFS are
termed as configuration classes in SAP S/4HANA. Only category profiles and grid profiles are migrated
from SAP AFS.
● If descriptions are not available in the source system, the migration object maintains the distribution
curve ID as the description and the logon language as the migration language.
Post-Processing
During migration, this migration object clears the active status of the distribution curve since only one version
can be active in the SAP S/4HANA system. You need to manually set the distribution curve (and its version) as
active in the SAP S/4HANA system.
Create FSH_DC_MAINTAIN
Change FSH_DC_MAINTAIN
Display FSH_DC_MAINTAIN

Further Information
1.157 AFS - Configuration class for material grid
Purpose
This migration object enables you to migrate configuration class data from the source AFS system to the target
Related Business Object: Configuration Class
Business Object Component/Area Component: LO-RFM
Business Object Definition Important element of the AFS basic data that maps the char
acteristic values of an AFS material in grid values and per
mits combinations consisting of up to three dimensions (for
example color, size,length). The use of master, purchase and
sales grids facilitate the valuation, procurement and sale of
AFS materials at SKU level.
Available Scenarios
Selection Criteria
In Scope
Master grid data
 Note
Material grids you set for deletion in the source AFS system are not migrated

During migration, if the characteristics in the source system and master grid do not match, an error
message is displayed. The entry causing the error is not migrated.
Out of Scope
Application grids (purchase grids and sales grids)
Prerequisites

Source System
Not relevant
Target System
C_KLAH_BKP (Class Maintenance)
Name of this migration object: S4_AFS_LO_CONFIGCLASS
CLMA_CLASS_CREATE Create Class for SAP Retail
The API is used to create configuration classes with the following entries:
● "300" as the class type (KLAH-KLART) and

● " " (blank) as the merchandize management system class type (KLAH-WWSKZ)
Virtual Tables

CABN_NEW: To store characteristics.
Post-Processing
Not relevant

Change CL02
Display CL03
Further Information
1.158 AFS - Distribution curve condition
Purpose
This migration object enables you to migrate distribution condition data from the source AFS system to the
Related Business Object: Distribution Condition

Business Object Definition Distribution curve: A definition of quantity distribution ratios
across different variant-creating characteristics or across
valid segmentation value combinations.
You use distribution curves to distribute the quantities

across different variants if the quantity is provided at generic
article level.
Available Scenarios
Selection Criteria
In Scope
Demand management data
Only data in the condition tables listed below is migrated:
● Variant with the condition type "01DM":

○ Table SAPDR004: (Material / Plant)
○ Table SAPDR006: (Material)
● Segment with the condition type "02DM":
Table SAPDR102: (Material)
Sales and distribution data
Only data in the condition table listed below is migrated:
● Variant with the condition type " 01SD":

Table SAPDR204: (Material)
Material management data
Only data in the condition tables listed below is migrated:
● Variant with the condition type "01MM":

○ Table SAPDR302: (Material / Plant)
○ Table SAPDR304: (Material)
Out of Scope
● Customer
● Customer group

Prerequisites
● AFS - Article
● AFS - Distribution curve
Source System
Not relevant
Target System
FSH_DPR (Authorization for Distribution Curve)
Name of this migration object: S4_AFS_LO_DCOND
FSH_DPR_CONDREC_CREATE_API: Create API for distribution curve condition record maintenance
Virtual Tables
● MARA_J_3AGRPR: To store AFS grid profiles from the MARA table.

● DIST_COND: To store distribution conditions.
Functional Info - Source System
In the AFS system, you can define your distributions using these distribution profile types:
● Plant
● Category
● Grid (based on a master grid)
● Period

 Note
● Distribution profiles based on categories are always linked to a coverage strategy.

● Distribution profiles based on grids are linked to a master grid.
Functional Info - Target System
In the SAP S/4HANA system, the distribution profiles are referred to as distribution curves and have these
distribution curve types:
● Segments
● Variants (based on a configuration class)
 Note
Categories in the AFS system are termed as segments in the SAP S/4HANA system and master grids in the
AFS system are termed as configuration classes in the SAP S/4HANA system. Only category profiles and
grid profiles are migrated from the AFS system.
Post-Processing
Not relevant
Distribution Curve FSH_DC_MAINTAIN
Distribution curve: Purchase FSH_DC_MM
Distribution curve: Sales FSH_DC_SD
Distribution curve: Demand Management FSH_DC_DM
Further Information

1.159 AFS - Dimensional characteristic
Purpose
This migration object enables you to migrate characteristics for dimension data from the source AFS system to
(BAPIs).
Related Business Object: Characteristics for Dimension
Classification System Master Data Characteristics
Component: CA-CL
Business Object Definition Characteristic: An attribute used to describe and distinguish

between different objects, for example, color and size.
Dimension: A freely definable element of an AFS grid. An

AFS grid is composed of up to three dimensions. Dimensions
are, for example, length, color, size, or width. Each dimen
sion is composed of dimension values which are all valid en
tries for a particular dimension.
Available Scenarios
Selection Criteria
In Scope
● Basic data
● Descriptions
● Values
● Additional data

● Restrictions
● Long texts for characteristic levels
● Documents
This migration object migrates characteristics for dimensions belonging to the /AFS/SAP-Dcharacteristics
group. Other characteristics are migrated using the Non-dimensional characteristic migration object.
This migration object migrates long texts at the characteristics level and not the values level. (The WRFCHVAL
transaction in the target system doesn't support long texts at the values level.)
During migration, if the characteristics in the source system and the master grid do not match, a warning
message is displayed. However, this does not affect the migration process.
Out of Scope
● Characteristics with future values

● Characteristic relevance
 Note
● Characteristics values
● Long texts
● Documents
Prerequisites

● ECM - change master
Source System

Not relevant
Target System
C_CABN (Authorization for characteristics maintenance)
C_CABN_GRP (Authorization group in characteristic)
Name of this migration object: S4_AFS_CA_CHARACTERISTIC_DIM
● BAPI_CHARACT_CREATE: BAPI for Characteristics - Create

○ This BAPI creates characteristic values and stores dimensional characteristics in a new set of tables in
the target system. The BAPI uses the WRF_CHECK_CHAR_VAL check function to migrate the
dimensional characteristic data.
○ During migration, this migration object clears the value of the /AFS/SAP-D characteristic group since
the group is AFSspecific.
○ This migration object also clears the Entry Required check box from the Value Assignment section on
the Basic Data tab. This check box is cleared to enable the viewing of articles in the MM42 transaction
without any inconsistencies.
○ Documents that are attached to characteristics are migrated only if the target system has the same
document name.
○ This migration object does not modify or overwrite the existing characteristics in the target system.
○ This BAPI picks up only "allowed values" from the Values tab in the source system, because the target
system has the WRF_CHECK_CHAR_VAL check function on the Values tab.
● WRF_CHARVAL_MAINTAIN_RFC: Processing Characteristic Values from External Programs

○ This migration object assigns a fixed value "E" to the Check Options (CHECKOPT) field in the
WRF_CHARVAL_HEAD table. The value "E" indicates Check Characteristic Values in Material
Maintenance with Error.
○ Additionally, each characteristic defines the characteristic type in the CHARTYPE field. The
characteristic types available are: color characteristic, size characteristic (main size), size
characteristic (secondary size), or Not Typed.
● BAPI_CHARACT_ADDLONGTEXT: BAPI for Characteristics: Set Long Text for Characteristic or Value
This BAPI migrates long texts only for the characteristics level in this migration scenario.
Virtual Tables
CABN_TEXT: To store characteristic long texts.

Post-Processing
Not relevant

Create CT04
Change CT04
Display CT04
Further Information
1.160 AFS - Planned independent requirement at SKU level
Purpose
This migration object enables you to migrate planned independent requirement data from the source AFS
Interfaces (BAPIs).
Planning Demand Management AFS Planned
Independent Requirements
Component: IS-AFS-PP

Available Scenarios
Selection Criteria
This migration object automatically selects all planned independent requirements from the J_3AREQS table for
the derived plants.
In Scope
Items
Schedule lines
 Note
Planned independent requirements you set for deletion in the source AFS system are not migrated
Out of Scope
Withdrawal quantity
Prerequisites
● AFS - Article
● AFS - Segmentation default value

Source System
Not relevant
Target System
Name of this migration object: S4_AFS_LO_PLANNED_IND_REQMTS_SKU
BAPI_REQUIREMENTS_CREATE Create Planned Independent Requirements
BAPI_REQUIREMENTS_CHANGE Change Planned Independent Requirements
Virtual Tables
SCHD_LINE: To store schedule lines
Post-Processing
Create MD61
Change MD62
Display MD63

Further Information
1.161 AFS - Non-dimensional characteristic
Purpose
This migration object enables you to migrate characteristics for non-dimension data from the source AFS
Interfaces (BAPIs).
Related Business Object: Characteristics Group
Business Object Component/Area User Menu Path: Cross Application Classification
System Master Data Characteristics
Component: CA-CL
Business Object Definition Characteristics: An attribute used to describe and distin

guish between different objects, for example, color and size.
Characteristics group: A collection of similar characteristics.

A characteristics group can be used as a search criterion for
finding the characteristics you want to use more easily
(when maintaining a class, for example).
Available Scenarios
Selection Criteria
This migration object is not delimited by the company codes specified when defining the migration scope.
This migration object automatically selects characteristics from the CABN table if the following condition is
met:
The value of the Characteristic Group (ATKLA) field is NOT /AFS/SAP-D (AFS characteristics for dimensions).

In Scope
● Basic data
● Descriptions
● Values
● Additional data
● Restrictions
● Long texts for characteristics and characteristics values
● Documents
● Local object dependencies
● Characteristic relevance for these function types: BOM, DIM, EAN, GTS, MRP, PRC, PRI, ROU, RSC, SDS,
SEA, SRC, VAL, VAR, VAS, WM1 and WM2
● Changes relevant to change numbers
● Characteristics belonging to the /AFS/SAP-D characteristics group are migrated using the AFS -
Dimensional characteristic migration object.
● The characteristic group value for the /AFS/SAP-C characteristics group in the SAP S/4HANA system is
SGT_SAP-C.
● If the relevance settings are present in the /AFS/DIM_RELS table in the source system, this migration
object migrates the relevance data to the target system.
● You can migrate only allowed values from the value check strategy.
● If there are any dependency source code errors, dependencies with the Released status are migrated with
the Locked status.
Out of Scope
● Custom relevancy functions

● Characteristic relevance for these functions: FLC, VLC, MRM and MRQ
● Value check strategies other than allowed values
● Assignments of global dependencies
● Advanced variant configurations for dependencies
 Note
● Changes related to change numbers

● Characteristic dependencies
● Long texts

Prerequisites

Source System
Not relevant
Target System
C_CABN (Authorization for characteristics maintenance)
C_CABN_GRP (Authorization group in characteristic)
Name of this migration object: S4_AFS_CA_CHAR_NON_DIM
● BAPI_CHARACT_CREATE: BAPI for Characteristics - Create

● BAPI_CHARACT_CHANGE: BAPI for Characteristics - Change
● BAPI_CHARACT_ADDLONGTEXT: BAPI for Characteristics: Set Long Text for Characteristic or Value
● CTMV_CHARACT_CHANGE_KNOWL: API Function: Maintaining Object Dependencies for Characteristics
● CTMV_CHARACT_CHANGE_KNOWL_VAL: API Function: Maintaining Object Dependency Values for
Characteristics
Virtual Tables
● CABN_AS: To store basic data for characteristics.

● CABNT_AS: To store characteristic texts.
● CABNT_LONGTXT: To store long texts for characteristics.
● CAWN_AS: To store characteristic values.
● CAWNT_AS: To store characteristic value texts.
● CAWNT_LONGTXT: To store long texts for characteristic values.
● VCUOB_AS: To store object dependencies for characteristic values.

● VCUKB_AS: To store administration information for characteristic value dependencies.
● VCUKBT_AS: To store texts for characteristic value dependencies.
● VCUKN_AS: To store dependency source code for characteristic values.
● VDOC1_AS: To store dependency long texts for characteristic values.
● TCME_AS: To store validity data for global characteristics.
● DIM_RELS_AS: To store characteristic relevance.
● CCUOB_AS: To store characteristic object dependencies.
● CCUKB_AS: To store administration information for characteristic dependencies.
● CCUKBT_AS: To store characteristic dependency texts.
● CCUKN_AS: To store administration information for characteristics.
● CCUXREF_AS: To store cross references for source code object dependencies.
● CCABN_AS: To store internal characteristics.
● CDOC1_AS: To store dependency long texts for characteristics.
Post-Processing
Not relevant
Further Information
1.162 AFS - Quantity distribution profile

Purpose
This migration object enables you to migrate quantity distribution profile data from the source AFS system to
Related Business Object: Quantity Distribution Profile
Business Object Component/Area Component: IS-AFS-SD
Business Object Definition A tool in the sales order for saving a template for distributing
quantities among dimension values. After you have saved
the template, you can then enter a factor in the sales order
and the system multiplies the number by the quantities in
the profile. Example This function is used when items such
as shoes are already packed in large boxes according to a
certain profile and the customer agrees to buy a certain
quantity. This tool makes it easier to enter the quantities for
the individual dimension values.
Available Scenarios
Selection Criteria
In Scope
● Header data for quantity distribution profiles

● Deviation quantities for header characteristics
● Deviation quantities for component characteristics
●
Out of Scope
Not relevant

Prerequisites
You have migrated or defined settings in the AFS - Configuration class for material grid migration object:
Target System
FSH_QDP (Authorization to Maintain Quantity Distribution Profile)
Name of this migration object: S4_AFS_LO_QUANTITY_DIST_PROFILE
RFM_API_QDP_MAINTAIN_RFC Maintain QDP data via RFC
Virtual Tables
● GRID_HDR_VALUE: To store grid data

● DIM_VALUES: To store dimension data
Post-Processing
Not relevant

With the transaction code shown below, you can change the view and maintain the object. However, these
Create / Change / Display FSH_QDP

Further Information
1.163 AFS - Planned independent requirement at material

level
Purpose
Interfaces (BAPIs).
Planning Demand Management AFS Planned
Independent Requirements
Component: PP-MRP
Available Scenarios
Selection Criteria
This migration object automatically selects relevant planned independent requirements from the J_3AREQM
table for the derived plants.
Relevant selection criteria for planned independent requirements:
● Data of single materials

● Data of materials with an empty grid value
● Data of materials with no grid values

In Scope
● Items
● Schedule lines
 Note
Planned independent requirements you set for deletion in the source AFS system are not migrated
Out of Scope
Withdrawal quantity
Prerequisites
● AFS - Article
● AFS - Segmentation default value
Source System
Not relevant
Target System
Name of this migration object: S4_AFS_LO_PLANNED_IND_REQMTS_MM

BAPI_REQUIREMENTS_CHANGE Change Planned Independent Requirements
Virtual Tables
SCHD_LINE: To store schedule lines
Post-Processing

Create MD61
Change MD62
Display MD63
Further Information
1.164 AFS - Season
Purpose
This migration object enables you to migrate season data from the source AFS system to the target SAP S/

Related Business Object: Season
Business Object Component/Area Component: IS-AFS-SD
Business Object Definition A reporting period in which a special assortment limited to a

specific period is merchandised and maintained in the infor
mation system in a particular way (for example, summer
season, Christmas season, Easter season, winter season).
Available Scenarios
Selection Criteria
In Scope
● Season data
● Collections data
● Theme data
● Season condition data relevant to sales
● Season condition data relevant to purchasing
● Season condition data relevant to production
 Note
The migration object calculates validity dates for season data as described below:
● The Validity From date is set as the lower value of the Order From dates
● The Validity To date is set as the higher value of the Delivery To dates
● If you do not define the order from dates and delivery to dates for season data, the validity from date
is set to January 1 for the year previous to the current year. In addition, the validity to date is set to
December 31 for the year following the current year.
When the validation result shows the order date occurring after the delivery date in the target system, the
order date is set to a day earlier than the delivery date.
Out of Scope
Not relevant

Prerequisites
You have migrated or defined settings in the Customer migration object:
Source System
Not relevant
Target System
SWB_DISPLA (Authorization to display season workbench)
SWB_PROD_V (Authorization to display production view in season workbench)
SWB_PUR_V (Authorization to display purchasing view in season workbench)
SWB_SALE_V (Authorization to display sales view in season workbench)
SWB_TREE (Authorizations for season workbench)
Name of this migration object: S4_AFS_LO_SEASON
FSH_API_SEASON_MAINTAINDATA API for season insert/update/delete
Post-Processing
Not relevant


Create/Change/Display FSH_SWB
Further Information
1.165 AFS - Segmentation default value
Purpose
This migration object enables you to migrate category structure default data from the source AFS system to
 Note
This migration object refers to segmentation default values in the target SAP S/4HANA system.
Related Business Object: Segmentation Default Value
Business Object Definition You can use the Default Segment Value Maintenance tool to
create and modify condition records that will be used by the
applications, such as Sales Order, Purchase Order, and so
on, to determine default segment values.
Available Scenarios
Selection Criteria

In Scope
Default segmentation values for:
● Sales orders
● Planned orders
● Production orders
● Outline agreements
● Purchase order stock segments
● Purchase requisition stock segments
● Planned independent requirements
Out of Scope
Default segmentation values for:
● Requirement segments for purchase orders

● Requirement segments for purchase requisition
● Safety stock
 Note
Prerequisites
● AFS - Segmentation strategy

● AFS - Segmentation structure
Source System
Not relevant
Target System

J_4KCATW (Authorization for Whole Category Field)
Name of this migration object: S4_AFS_LO_SEG_DEFAULT
RFM_SGT_DEFAULT_VALUE_MAINTAIN Maintain Default Segmentation Values
Virtual Tables
DEFAULT_DATA: To store the default data created for each segmentation structure.
Post-Processing
Not relevant
Create/Change/Display SGT_DEFFAULT
Further Information

1.166 AFS - Segmentation strategy
Purpose
This migration object enables you to migrate coverage strategy data from the source AFS system to the target
 Note
This migration object refers to segmentation strategy in the target SAP S/4HANA system.
Related Business Object: Segmentation Strategy
Business Object Definition A collection of business rules that define which stock materi
als should satisfy which demand objects. The segmentation
strategy is based on the mapping between a stock segment
associated with a material in stock and a requirement seg
ment associated with a demand object. Segmentation strat
egies can be assigned to materials to determine the valid
stock segments and requirement segments for the materials
to define which requirements should be covered by which
stock segments.
Available Scenarios
Selection Criteria
In Scope
● MRP information
● PIR consumption data
● Requirement-to-stock conversions

● Stock-to-requirement conversions
Out of Scope
ATP information for segmentation strategy
 Note
Prerequisites
You have migrated or defined settings in the AFS - Segmentation structure migration object.
Source System
Not relevant
Target System
C_SGTSETUP (Auth. Object for Segmentation Setup)
Name of this migration object: S4_AFS_LO_SEG_STRATEGY
RFM_SGT_STRATEGY_MAINTAIN_RFC Segmentation Strategy Maintenance
Virtual Tables
STRAT_DATA: To store segmentation strategy data.

Post-Processing
Not relevant

Create/Change/Display SGTC
Further Information
1.167 AFS - Segmentation structure
Purpose
This migration object enables you to migrate category structure data from the source AFS system to the target
 Note
This migration object refers to segmentation structures in the target SAP S/4HANA system.
Related Business Object: Segmentation Structure

Business Object Definition A welldefined sequence of segmentation characteristics

that can be used to define segmentation strategies. Seg
mentation structures are defined using characteristics that
manifest themselves as requirement fields and stock fields
in the structure. The characteristics have relevance on both
the stock side and the requirement side.
Example: A segmentation structure uses the characteristics

"quality level" (Q1, Q2, Q3) and "country/region of origin" (In
dia, Germany, USA). The combination, for example, "Q1 In
dia" helps identify the relevance for a sales order.
Available Scenarios
Selection Criteria
In Scope
Category structures
 Note
Category structures are termed segmentation structures in the SAP S/4HANA system.
Out of Scope
Not relevant
Prerequisites
Characteristics for segmentation

Source System
Not relevant
Target System
SGT_SETUP (Auth. Object for Segmentation Setup)
Name of this migration object: S4_AFS_LO_SEG_STRUCTURE
RFM_SGT_STRUCTURE_MAINTAIN_RFC Maintain Segmentation Structure
Virtual Tables
STRUCTURE_DATA: To store segmentation structure data.
Post-Processing
Not relevant

Create/Change/Display SGTS
Further Information

1.168 Bank
Purpose
This object enables you to migrate bank data from the source AFS system to the target S/4HANA system
based on the default selection criteria set for the migration object. This migration process enables you to
transfer data to the target system using Business Application Programming Interfaces (BAPIs).
Related Business Object: Bank Master
Banks Master Data Bank Master Record
Component: FI
Business Object Definition A unique number or code that uniformly identifies a bank in
the system.
Available Scenarios
Selection Criteria
This migration object automatically selects all bank keys from the BNKA table in the source system.
In Scope
● Bank country/region
● Bank key
● Bank address data
● Other address data of the bank

Out of Scope
● Check digit calculation method

● File formats with bank data
● IBAN rules
● SEPA B2B direct debit
● SEPA COR1 direct debit
● SEPA returned debits (R transactions)
● Internal bank categories
Prerequisites
Source System
Not relevant
Target System
F_BNKA_MAN (Banks: General Maintenance Authorization)
Name of this migration object: S4_AFS_CA_BANKMASTER
BAPI_BANK_CREATE Create Bank
Post-Processing
Not relevant

Create FI01
Change FI02
Display FI03
Further Information
Purpose
This migration object enables you to migrate batch data unique at the plant level from the source AFS system
Management Batch
Component: LO-BM

Available Scenarios
Selection Criteria

This migration object automatically selects all batch data unique at the plant level from the MCHA table for the
derived plants.
In Scope
● Basic data
Out of Scope

Prerequisites

● AFS - Article
● Class
● Supplier
Source System
Not relevant
Target System

Name of this migration object: S4_AFS_MM_BATCHES_PLANTL
VB_CREATE_BATCH: Create Batch
Post-Processing
Not relevant
Create MSC1N
Change MSC2N
Display MSC3N
Further Information

Purpose
This migration object enables you to migrate activity type master data from the source AFS system to the
Related Business Object: Activity Type
Accounting Master Data Activity Type
Component: CO
Available Scenarios
Selection Criteria
migration scope. This migration object automatically selects all activity types from the CSLA table for the
In Scope
● Basic data
● Activity type texts
Out of Scope
Not relevant
Prerequisites

● Cost center categories
● Activity type categories
● CO - Activity type group

Source System
Not relevant
Target System
K_CSLA (CO-CCA: Activity Types Master)
Name of this migration object: S4_AFS_CO_ ACTIVITY_TYPE
BAPI_ACTTYPE_CREATEMULTIPLE Create One or More Activity Types
Post-Processing

Create KL01
Change KL02
Display KL03

Further Information
1.171 CO - Activity type group
Purpose
This migration object enables you to migrate activity type group master data from the source AFS system to
(BAPIs).
Related Business Object: Activity Type Group
Accounting Master Data Activity Type Group
Component: CO
Business Object Definition An organizational unit to combine several activity types.
Available Scenarios
Selection Criteria
migration scope. This migration object automatically selects activity type groups belonging to set classes from
the SETHEADER table for the derived controlling areas.
 Note
The migration object selects the set class with the value 0105 (Activity Type Group) for transfer.

In Scope
● Basic data
 Note
This migration object transfers activity type groups maintained in the source system to the target system
without any changes. If you want to rename an activity type during migration, you may have to manually
modify the activity type names in the groups.
Out of Scope
Not relevant
Prerequisites
Source System
Target System
Name of this migration object: S4_AFS_CO_ACTIVITY_GROUP

Target System
BAPI_ACTIVITYTYPEGRP_CREATE Object BUS1115 (Activity Type Group) - Method Create
Source System
BAPI_ACTIVITYTYPEGRP_GETDETAIL Object BUS1115 (Activity Type Group) - Method GetDetail
Virtual Tables
● TAB_NODES: Hierarchy Nodes

● TAB_VALUES: Hierarchy Values
Post-Processing
Not relevant
Create KLH1
Change KLH2
Display KLH3
Further Information
1.172 CO - Cost rate

Purpose
This migration object enables you to migrate cost rate data from the source AFS system to the target SAP S/
Related Business Object: Activity Price
Accounting Planning Activity Output/Prices
Component: CO-OM
Business Object Definition The amount charged for services performed for external or
internal receivers.
Available Scenarios
Selection Criteria
migration scope. This migration object automatically selects all cost rate data from the CSSL table for the
controlling areas.
All cost rate data from the CSSL table are automatically selected for the current fiscal year, previous fiscal year
and the upcoming fiscal year. Fiscal year data enables a comparison of planned and actual cost rates.
In Scope
● Header information
● Objects for plan activity
● Period values for plan activity
● Control values for plan activity
 Note
Cost rates for business processes in the source system are not migrated

Out of Scope
Not relevant
Prerequisites
Source System
Target System
K_CBPR_PLA (CO-ABC: Business Process Planning)
Name of this migration object: S4_AFS_CO_ACTIVITY_PRICE
BAPI_COSTACTPLN_CHECKACTOUTPUT: Activity/Price Planning: Check
Virtual Tables
FLTR_CSSL: To store cost rate data of the previous, current, and upcoming fiscal years.

The migration object transfers cost rate information to the target system with default values for the following
fields:
Field Default Value
PERIOD_FROM 001
PERIOD_TO 012
PLAN_CURRTYPE C
Post-Processing
Not relevant

Create KP26
Change KP26
Display KP27
Further Information
Purpose
This migration object enables you to migrate business process data from the source AFS system to the target

Related Business Object: Business Process
Based Costing Master Data Business Process
Component: CO-OM
Business Object Definition Process in a company that uses resources and can involve
the activities of different departments.

Available Scenarios
Selection Criteria
migration scope. This migration object automatically selects all business processes from the CBPR table for the
In Scope
● Basic data
● Organizations
● Attributes
● Allocation
● Templates
Out of Scope
Not relevant
Prerequisites

● CO - Business process group
Source System
Not relevant
Target System
K_ABC (CO-ABC: General Authorization Object, Business Processes)
K_CBPR_SET (CO-ABC: Business Process Groups)
Name of this migration object: S4_AFS_CO_BUSINESS_PROCESS
BAPI_PROCESS_CREATEMULTIPLE: Create One or More Business Processes
Post-Processing
Not relevant

Create CP01
Change CP02

Display CP03
Further Information
1.174 CO - Business process group
Purpose
This object enables you to migrate business process groups and assigned standard hierarchies from the source
AFS system to the target S/4HANA system based on the default selection criteria set for the migration object.
This migration process enables you to transfers data to the target system using Business Application
Related Business Object: Business Process Group
Based Costing Master Data Business Process Group
Component: CO-OM-ABC
Business Object Definition When you create a business process, you must assign it to a
group, which can be either the standard hierarchy itself or a
business process group that belongs to the standard hierar
chy. The standard hierarchy is the business process group
that you create before you define the first business process.
You can create additional business process groups as subor
dinate nodes under the standard hierarchy.
Available Scenarios
Selection Criteria
migration scope. This migration object automatically selects all business process groups and the standard
hierarchies from SETHEADER table for the derived controlling areas.

In Scope
● Basic data
● Standard hierarchies assigned to the controlling area
 Note
After the business process master data is migrated to the target system, the respective business process is
assigned to the corresponding hierarchy area.
Out of Scope
Values assigned to standard hierarchies
Prerequisites
● Standard hierarchies for business processes

● Assignment of standard hierarchies to controlling areas
Source System
Not relevant
Target System
● K_CBPR_SET (CO-ABC: Business Process Groups)

● K_ABC (CO-ABC: General Authorization Object, Business Processes)
Name of this migration object: S4_AFS_ CO_BUSINESS_PROCESS_GROUP

BAPI_BUSPROCESSCOGRP_CREATE Object BUS1114 (Business Process Group) - Method Create
Post-Processing
Not relevant
Create CPH1
Change CPH2
Display CPH3
Further Information
Purpose
This migration object enables you to migrate cost center data from the source AFS system to the target SAP S/
Related Business Object: Cost Center

Accounting Master Data Cost Center
Component: CO
The definition can be based on:
● Functional requirements
● Allocation criteria
● Physical location
● Responsibility for costs
Available Scenarios
Selection Criteria
migration scope. This migration object automatically selects all cost centers from the CSKS table for the
In Scope
● Basic data
● Address data
● Validity
Out of Scope
Not relevant
Prerequisites

● CO - Cost center group

Source System
Not relevant
Target System
Name of this migration object: S4_AFS_CO_COST_CENTER
BAPI_COSTCENTER_CREATEMULTIPLE Create Cost Center
Post-Processing
Not relevant

Create KS01
Change KS02

Display KS03
Further Information
1.176 CO - Cost center group
Purpose
This migration object enables you to migrate cost center groups and assigned standard hierarchies from the
migration object. This migration technique transfers data to the target system using standard Business
Related Business Object: Cost Center Group
Business Object Component/Area User Menu Path Accounting Controlling Cost Center
Accounting Master Data Cost Center Group
Component: CO
Business Object Definition A hierarchical group of cost centers defined and organized
according to selected criteria.
Available Scenarios
Selection Criteria
migration scope. This migration object automatically selects cost center groups and the assigned standard

In Scope
Cost center groups
Out of Scope

● Values assigned to related cost center groups
Prerequisites
Standard hierarchies belonging to cost center groups are assigned to the relevant controlling area.
Source System
Target System
K_CSKS(CO-CCA: Cost Center Master)

Name of this migration object: S4_AFS_CO_COST_CENTER_GROUP
BAPI_COSTCENTERGROUP_CREATE Object BUS1112 (Cost Center Group) - Method Create
Virtual Tables
TAB_NODES: To store the nodes of the standard hierarchy
Post-Processing
Not relevant
Create KSH1
Change KSH2
Display KSH3
Further Information
1.177 CO - Cost element group

Purpose
This migration object enables you to migrate cost element group data from the source AFS system to the
Related Business Object: Cost Element Group
Accounting Master Data Cost Element Group
Component: CO
Business Object Definition An organizational entity that combines cost elements of the
same type. Cost element groups can serve various purposes.
For example, they can be used to create reports or to proc
ess several cost elements in one business transaction.
Available Scenarios
Selection Criteria
This migration object derives the chart of accounts from the company codes you specified when defining the
migration scope. This migration object automatically selects the cost element groups from the SETHEADER
table for the derived charts of accounts.
In Scope
● Basic data
 Note
This migration object transfers cost element groups maintained in the source system to the target system
without any changes. If you want to rename a cost element during migration, you may have to manually
modify the cost element names in the groups.
Out of Scope
Not relevant

Prerequisites
Source System
Target System
Name of this migration object: S4_AFS_CO_COST_ELEMENT_GROUP
BAPI_COSTELEMENTGRP_CREATE: Create Cost Element Group
Virtual Tables
● TAB_NODES: To store group nodes

● TAB_VALUES: To store group ranges
Post-Processing
Not relevant


Create KAH1
Change KAH2
Display KAH3
Further Information
Purpose
This migration object enables you to migrate internal order data from the source AFS system to the target SAP
Related Business Object: Internal Order
Business Object Component/Area User Menu Path: Accounting Controlling Internal
Orders Master Data Special Functions Order
Create
Component: CO

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

● Monitoring the costs and revenues of a specific service
● Ongoing cost control
Available Scenarios
Selection Criteria

migration scope. This migration object automatically selects internal orders from the AUFK table for the
In Scope
● Basic data
● Internal order description
 Note
After migration, all internal orders are set to the "Created" status regardless of the status in the source
system.
Out of Scope
Not relevant
Prerequisites
● Plant
● Object class
● Business area
● Functional area
● SD - Customer quotation
● PS - Network
If you want to set the status of all migrated internal orders as "Released": You have set the order profile in the
KOT2_OPA transaction and selected Release Immediately before migration.

 Note
With this setting, after migration, all internal orders are set to the "Released" status regardless of the status
in the source system.
Source System
Not relevant
Target System
K_ORDER (CO-OPA General authorization object for internal orders)
B_URSERST_T (Status Management Set/Delete User Status using Transaction)
S_ADMI_FCD(System Authorizations)
Name of this migration object: S4_AFS_CO_INTORDER
BAPI_INTERNALORDER_CREATE Create Internal Order from Transferred Data
If you have set the number range object to internal, the BAPI still treats it as an external number range object.
As a result, errors might occur even though migration was successful.
Post-Processing
Not relevant


Create KO01
Change KO02
Display KO03
Further Information
Purpose
This migration object enables you to migrate profit center data from the source AFS system to the target SAP
Related Business Object: Profit Center
Accounting Master Data Profit Center
Component: CO
Business Object Definition An organizational unit in Accounting that reflects a manage

of internal control. Operating results for a profit center can
be analyzed using either the cost of sales approach or the
period accounting approach. By analyzing the fixed capital
as well, you can expand your profit center for use as an in
vestment.
Available Scenarios
Selection Criteria

migration scope. This migration object automatically selects all active profit centers from the CEPC table for
In Scope
● Basic data
● Address data
● Validity information
Out of Scope
Inactive profit centers
Prerequisites
● CO - Profit center group

Source System
Not relevant
Target System
K_PCA EC-PCA: Responsibility Area, Profit Center

Name of this migration object: S4_AFS_CO_PROFIT_CENTER
BAPI_PROFITCENTER_CREATE Create Profit Center
 Note
If the profit center is assigned to several company codes, this migration object assigns only the specified
company codes to the profit center in the target system. This migration object sets the ASSIGN_TO_PRCTR
parameter to "X" in the CEPC_BUKRS table for the BAPI BAPI_PROFITCENTER_CREATE .
Post-Processing
Not relevant
Create KE51
Change KE52
Display KE53
Further Information
1.180 CO - Profit center group

Purpose
This migration object enables you to migrate profit center groups and assigned standard hierarchies from the
Related Business Object: Profit Center Group
Accounting Master Data Profit Center Group
Component: CO
Business Object Definition A profit center group is a hierarchical structure of profit cen
ters.
Available Scenarios
Selection Criteria
migration scope. This migration object automatically selects profit center groups and the assigned standard
In Scope
Profit center groups
Out of Scope

● Values assigned to related profit center groups

Prerequisites
Standard hierarchies belonging to profit center groups are assigned to the relevant controlling area.
Source System
Target System
K_PCAP_SET (EC-PCA: Planning Hierarchy)
F_UNI_HIER (Universal Hierarchy Access)
K_PCA_MD (EC-PCA: Authorization Object for Profit Center Master Data)
Name of this migration object: S4_AFS_CO_PROFIT_CENTER_GROUP
BAPI_PROFITCENTERGRP_CREATE: Object BUS1116 (Profit Center Group) - Method Create
Virtual Tables
TAB_NODES: To store nodes of the standard hierarchy

Post-Processing
Not relevant.

Create KCH1
Change KCH2
Display KCH3
Further Information
1.181 CO - Secondary cost element
Purpose
This migration object enables you to migrate secondary cost element master data from the source AFS system
Related Business Object: Secondary Cost Element
Business Object Component/Area User Menu Path: Accounting Controlling Cost
Element Accounting Master Data Cost Element
Individual Processing Edit Cost Element
Component: CO

Business Object Definition A cost element that is used to allocate costs for internal ac
tivities.
Available Scenarios
Selection Criteria
This migration object derives the controlling area from company codes you specified when defining the
migration scope. This migration object automatically selects all secondary cost elements from the CSKB table
for the derived controlling areas.
In Scope
● Basic data
● Chart of accounts data
● General texts
Out of Scope
Default account assignments
Prerequisites
Company code assignments to the controlling area
FI - G/L account
Source System
Not relevant

Target System
Name of this migration object: S4_AFS_CO_SECONDARY_COST_ELEMENT
GL_ACCT_MASTER_SAVE G/L Account Master Record
If a group chart of accounts is assigned to a chart of accounts, use the values in the MAP_KTOPL_BILKT
mapping task.
If a countryspecific/local chart of accounts is assigned at the company code level, use the values in the
MAP_BUKRS_ALTKT mapping task.
If a group chart of accounts is assigned to a chart of accounts AND a countryspecific/local chart of account is
assigned at the company code level, use the values in both MAP_KTOPL_BILKT and MAP_BUKRS_ALTKT
mapping tasks.
Fixed values defined in this migration object for secondary elements:
● Type of general ledger account is "S"

● P&L statement account type is "X"
● G/L account group is "SECC"
● Field status group is "SECC"
● Cost element category is "21", "31", "41", "42", "43", "50", "51", "52" and "61"
Post-Processing
Not relevant

Create FS00
Change FS00

Display FS00
Further Information
1.182 CO - Statistical key figure
Purpose
This migration object enables you to migrate statistical key figure data from the source AFS system to the
Related Business Object: Statistical Key Figure
Accounting / Cost Center Accounting Master Data
Statistical Key Figures Individual Processing Create
Component: CO
Business Object Definition The statistical values describe the following
● Cost center
● Business process
● Profit center
● Fixed value: They are carried forward from the current

posting period to all subsequent posting periods.
● Total value: They are posted in the current posting pe
riod only.
Available Scenarios
Selection Criteria

migration scope. This migration object automatically selects the statistical key figures from the TKA03 table for
In Scope
● Basic data
● Statistical key figure descriptions in one of available languages
Out of Scope
LIS data for statistical key figures
Prerequisites
● Statistical key figure hierarchies
Source System
Not relevant
Target System
● S_ADMI_FCD(System Authorizations)
● K_KA03 (CO-CCA: Statistical Key Figures)

Name of this migration object: S4_AFS_CO_STAT_KEY_FIGURE
BAPI_KEYFIGURE_CREATEMULTIPLE Create One or More Statistical Key Figures
Post-Processing
Not relevant

Create KK01
Change KK02
Display KK03
Further Information
1.183 Customer
Purpose
This migration object enables you to migrate customer master data from the source AFS system to the target
Related Business Object: Customer

Master Data Business Partner Customer
Component: SD
Business Object Definition A business partner with whom a business relationship exists,
involving the issue of goods or services.
Available Scenarios
Selection Criteria
migration scope. This migration object automatically selects all customers from the KNA1 table for the
company codes and derived sales organizations.
In Scope
● Basic data
● Company data including dunning
● Contact persons
● Bank data
● Sales data including sales partner functions
● Industry assignments
● Credit management control data
● Extensions of existing customers to new organization levels
● Only the following long texts
○ Customer texts
○ Company code texts
○ Sales organization texts
○ Contact person texts
● International versions of addresses
 Note
● If a customer in the source system is extended to multiple company codes, after data migration, the
customer in the target system is extended only to the participating company codes.
● If a customer in the source system has multiple sales organizations, after data migration, the customer
in the target system contains only the selected sales organizations.

Out of Scope
● Documents assigned to the customer

● Classifications
● Updates to existing fields
● Extensions of withholding tax or dunning or texts data to the existing company codes
● Extensions of partner functions of existing sales organizations
● Extensions of existing addresses with an international address version.
● Extensions of sales organizations belonging to existing company codes
Prerequisites
Source System
Before you can start the migration process, ensure that you have defined values for all fields set as mandatory
in the target system. Otherwise, errors may occur after migration. Alternatively, blank values are populated in
the mandatory fields after data migration.
Target System
● Provided the customer account group in the Customer Account Group (MAP_KTOKD) mapping task.
Doing so enables the migration object to determine the business partner grouping and roles from the
following customizing paths:

Integration Define BP Role Direction Customer to BP

Integration Field Assignment for Customer Integration
Assign Keys Define Number Assignment for Direction
Customer to BP
● Registered the CVI_EI_INBOUND_REQ_ACTIVATE function module using the CRMC_BUT_CALL_FU

transaction code with the following entries:

Event CRM Inbound
Call Selected
● Bank
● Supplier
If the customer and vendor refer to the same business entity in the source system, please migrate the
Source System
Not relevant
Target System
F_KNA1_BED ( Customer: Account Authorization)
V_KNA1_VKO (Customer: Authorization for Sales Organizations)
Name of this migration object: S4_AFS_SD_CUSTOMER_MASTER

This migration object identifies the business partner category from the TSAD3 Customizing table belonging to
the customer title. If, for example, the customer title in the source system is "company", the business partner
category is "organization".
Virtual Tables
● ADRC_VRN: To store international address versions

● KNB1_TEXT: To store company long text headers for customers
● KNB1_TEXT_DATA: To store customer company text data
● KNVV_TEXT: To store sales long text headers for customers
● KNVV_TEXT_DATA: To store sale long text data for customers
● TAXNUMBER: To store tax numbers
● ADRC_C: To store contact person addresses
● ADR2_C: To store telephone numbers for contact persons
● ADR3_C: To store fax numbers for contact persons
● ADR4_C: To store teletex numbers for contact persons
● ADR5_C: To store telex numbers for contact persons
● ADR6_C: To store e-mail addresses for contact persons
● ADR7_C: To store remote mail addresses (SAP - SAP - Communication; BAS) for contact persons
● ADR8_C: To store X.400 numbers for contact persons
● ADR9_C: To store RFC destinations for contact persons
● ADR10_C: To store ADR10 printer information for contact persons
● ADR11_C: To store SSF information for contact persons
● ADR12_C: To store FTP and URL data for contact persons
● ADR13_C: To store pager information for contact persons
● ADRT_C: To store communication data texts for contact persons
● ADRU_C: To store the communication usages of contact persons
● ADRCT_C: To store address texts for contact persons
● ADRC_C_VRN: To store the international address versions for contact persons
● KNVK_TEXT: To store contact long text headers for customers
● KNVK_TEXT_DATA: To store contact long text data for customers
● KNA1_TEXT: To store long text header data for customers
● KNA1_TEXT_DATA: To store customer text data
● BP_ROLES: To store business partner roles
● KNZA_HDR: To store alternative payer data that is common for all company codes

If the customer and the vendor refer to Customer and Vendor Customer Number (MAP_KUNNR)
and
system
tively
For example:Customer ABC and vendor

XYZ refer to the same business entity in
the source system and when customer
ABC is migrated to the target system,
assume business partner PQR is cre
ated with customer roles. Later, when
you migrate the vendor migration ob
ject, the business partner PQR is auto
matically assigned to the supplier XYZ.
If the customer is not related to the Customer Customer Number (MAP_KUNNR)

vendor in the source system (classical
scenario)
If the customer account group is as Customer Customer Number (MAP_KUNNR)

signed to an external number range
If the customer account group is as Customer (Enter a blank.) Customer Number (MAP_KUNNR)
signed to an internal number range
Post-Processing
Not relevant
Further Information

Purpose
This migration object enables you to migrate change number data from the source AFS system to the target
Related Business Object: Engineering Change Number
Engineering Change Management Change Number
Component: LO-ECH
Business Object Definition A component that allows objects to be changed with history
(with date validity) or dependent on specific conditions (with
parameter effectivity). The different processing statuses of
the object are saved. All changes are made with reference to
a change master record. In the SAP system, object types can
be changed with reference to a change number, such as:
● Bills of material
● Task lists
● Documents
● Materials
Available Scenarios
Selection Criteria
In Scope
● Object types :

○ Bills of material
○ Documents
○ Materials
○ Characteristics
○ Class characteristics
● Alternative dates
● Change header long texts
 Note
Change numbers you set for deletion in the source AFS system are not migrated.
Out of Scope
● Object types
○ Task lists
○ Classifications
○ Object dependencies
○ Configuration profiles
○ Variant tables
● Objects
Prerequisites
Relevant internal and external number ranges for the AENNR (Change Master Record) table.
Source System
Not relevant
Target System
C_AENR_ERW (CC Eng. Chg. Mgmt. Enhanced Authorization Check)
C_AENR_BGR (CC Change Master - Authorization Group)

Name of this migration object: S4_AFS_LO_ENGG_CHANGE_NUMBERS
BAPI_ECN_CREATE BAPI ECN Create
Virtual Tables
AENR_TEXT: To store header texts
During migration, for each object type in the migration scope for Engineering Change Number, this migration
object clears the values for the GEN_NEW and GEN_DIALOG fields in the target system. The clearing is done to
ensure that there are no dependencies on other master data objects during migration.
Post-Processing
Create CC01
Change CC02
Display CC03
Further Information

1.185 Exchange rate
Purpose
This migration object enables you to migrate exchange rate data from the source AFS system to the target SAP
Related Business Object: Exchange Rate
Business Object Component/Area User Menu Path: SAP Netweaver General Settings
Currencies Enter Exchange Rates
Component: FI
Business Object Definition Exchange rates define the relationship between two curren
cies. They are used to translate an amount into another cur
rency.
Available Scenarios
Selection Criteria
Exchange rates are defined at the client level and are relevant across company codes. Hence, this migration
object migrates all exchange rates maintained in the TCURRtable in the source system to the target system.
In Scope
Exchange rates
Out of Scope
Incomplete exchange rates. For example, exchange rate information that is available in the TCURR table is
missing in the TCURF table.

Prerequisites
● Currencies
● Exchange rate types
● Translation ratios
Source System
Not relevant
Target System
To migrate exchange rates, assign table maintenance or table access authorizations and enter the relevant
Name of this migration object: S4_AFS_FI_EXCHANGE_RATE_V2
BAPI_EXCHRATE_CREATEMULTIPLE Insert One or More Exchange Rates in SAP Tables
Virtual Tables
AT_FACTORS : To create structures for the migration BAPI
Post-Processing
Not relevant


Maintain OC41
Further Information
1.186 Fixed asset (including balance)
Purpose
This migration object enables you to migrate legacy data for fixed assets from the source AFS system to the
Related Business Object: Fixed Asset
Fixed Assets
Component: FI-AA
Business Object Type Master data and transactional data


Available Scenarios
Selection Criteria
All fixed assets from the ANLA table, which do not have a deactivation date, are automatically selected for the
company codes you specified when defining the migration scope .

In Scope
● Asset classes with an internal number assignment

● Master details
● Inventory
● Posting information
● Time-dependent data
● Allocations
● Origin
● Account assignments for investment
● Net worth valuations
● Real estate and similar rights
● Depreciation areas
● Investment support keys
● Cumulative values
● Posted values
● Transactions
● Assets under Construction (AuC)
Time of Transfer
● If you transfer balances at the end of a fiscal year, this migration object transfers the accumulated
acquisition cost and the accumulated depreciation values.
● If you transfer balances during a fiscal year, this migration object transfers:
○ The accumulated acquisition cost
○ Accumulated depreciation values
○ Transactions dated from the beginning of the fiscal year until the transfer date
By default, the posted depreciation from the beginning of the fiscal year until the transfer date is
transferred.
Assets under Construction (AuC)
● AuC open items are transferred with the transaction type "900".
● Down payments for AuC are transferred with the transaction type "910".
● AuC line items and assigned documents are transferred to the target system.
● Credit memos with the transaction type "105" and containing negative values are migrated with the
transaction type "100". The BAPI does not accept negative values.
● The migration object posts cumulative values as transactions since cumulative values are not allowed for
AuC.
 Note
This migration object accumulates transaction values and transfers them as acquisition values with the
transaction type "100".

Out of Scope
● AuC that are 100% settled in the source system

● Down payments for AuC that are already cleared in the source system
● Insurance data
● Retirement data
● Investment measures
● Proportional values on transactions
● External number assignment for assets
 Note
If a depreciation is defined to take over acquisition values from other depreciation areas (Areas 15, 31, and
33, for example, take over values from Area 01 and 32), and you transfer the acquisition values, the system
ignores the acquisition values. For the depreciation areas 31 and 33, the system derives the values from the
leading depreciation area (01, 32). Therefore, you do not need to transfer cumulative values for these
depreciation areas.
Prerequisites
Source System
system:
● You have completed the Balance Carry Forward process using the FAGLGVTR transaction.
Target System
● You have made the settings for the relevant depreciation areas. These settings determine the type of data
migrated from the source system. The migration is successful only if the values are compatible with the
depreciation area settings. Depreciation area Customizing should match in the sender and target systems.
● You have defined the offsetting account for legacy data transfer (asset balance sheet account) for Asset
Accounting in the Define Offsetting Account for Legacy Data Transfer activity.
● You have specified the transfer date, the document type, and the legacy data transfer status.
● If you want to do a year-end migration, you have set the Transfer Year Information mapping task to the
value "X". If you want to do a mid-year migration, you have set the value in the mapping task as blank.
● You have set the transfer date in the target system as the last day of the month. For example, if you want to
set the transfer date in the month of November 2021, you need to set the date to November 30, 2021.
● You have ensured that the transfer date is the end date of the period.

 Example
If you set the transfer date to September 22, 2018 (22.09.2018) on the Legacy Data Transfer tab, set
the end date to September 30, 2018 (30.09.2018). If you enter any other date as the end date, the
system displays a warning during simulation and migration.
● PS - Project
● Supplier
Source System
Not relevant
Target System
A_A_VIEW (Asset: View)
A_S_ANLKL (Asset Master Data Maint: Company Code/Asset Class)
A_S_KOSTL (Asset Master Record Maintenance: Company Code/Cost Center)
A_S_GSBER (Asset Master Data Maintenance: Company Code/Business Area)
Name of this migration object: S4_AFS_FI_AA_2
BAPI_FIXEDASSET_OVRTAKE_CREATE BAPI for Legacy Data Transfer
Virtual Tables
● CUMULATEDVALUES: To store cumulative values

● POSTEDVALUES: To store posted values
● TRANSACTIONS: To store transactions values

Post-Processing
To ensure that the legacy data transfer is carried out completely, reconcile the data in the target system with
the data in your source system. Ensure that you reconcile the legacy data transfer and the corresponding lists
for documentation purposes before you release the SAP system to run operations in Asset Accounting.
Display AS03
Further Information
For more information about how to reconcile data, see SAP Note 2304473 .
For more information about Balance Carry Forward, see SAP Note 2427888 .
For more information about legacy data transfer in SAP_FIN 720 and relevant releases, see SAP Note 2208321
.
1.187 FI - Accounts receivable open item (classic GL)
Purpose
This migration object enables you to migrate accounts receivable open items from the source AFS system to
(BAPIs).
Related Business Object: Account Receivable

Accounts Receivable
Component: FI

items.
Available Scenarios
Selection Criteria
In Scope

 Note
Out of Scope
● Tax lines
 Note

Prerequisites

target systems
● Exchange rate
● Customer
● FI - House bank
● Product
Source System
Not relevant
Target System
Not relevant
Name of this migration object: S4_AFS_FI_AR_OI_CLASSIC_GL

Virtual Tables
SEPA: To store information for one-time SEPA mandates
Post-Processing

Create FB01
Change FB02
Display FB03
Further Information
1.188 FI - Accounts receivable open item (new G/L)
Purpose
(BAPIs).

Accounts Receivable
Component: FI

items.
Available Scenarios
Selection Criteria
All accounts payable open items from the BSID table are automatically selected for the company codes that
In Scope

 Note
Out of Scope
● Tax lines
 Note

Prerequisites

target systems
● Exchange rate
● FI - House bank
● Product
Source System
Not relevant
Target System
Not relevant
Name of this migration object: S4_AFS_FI_AR_OI_NEW_GL

Virtual Tables
SEPA: To store data related to one-time mandates
Post-Processing
Create FB01
Change FB02
Display FB03
Further Information
1.189 FI - Accounts payable open item (classic G/L)
Purpose
This migration object enables you to migrate accounts payable open items from the source AFS system to the

Accounts Payable
Component: FI
cleared..
Available Scenarios
Selection Criteria
In Scope

 Note
Out of Scope

● Tax lines

Prerequisites
● Migration G/L accounts to post offsetting lines

target systems

● Exchange rate
● Vendor
Source System
Not relevant
Target System
Not relevant
Name of this migration object: S4_AFS_FI_AP_OI_CLASSIC_GL
Post-Processing

Create FB01
Change FB02
Display FB03
Further Information
1.190 FI - Accounts payable open item (new G/L)
Purpose
This migration object enables you to migrate accounts payable open items from the source AFS system to the
Accounts Payable
Component: FI
cleared..
Available Scenarios

Selection Criteria
In Scope

 Note
Out of Scope

● Tax lines
Prerequisites
● Migration G/L accounts to post offsetting lines

target systems


● Vendor
● Exchange rate
● FI - House bank
 Note
Source System
Not relevant
Target System
Not relevant
Name of this migration object: S4_AFS_FI_AP_OI_NEW_GL
Post-Processing


Create FB01
Change FB02
Display FB03
Further Information
1.191 FI - Bank account
Purpose
This migration object enables you to migrate bank account data from the source AFS system to the target S/
Related Business Object: House Bank Account
Accounts
Component: FI
Business Object Definition An internal representation of a company's bank account at a

house bank. It contains all control information required for
processing payment relevant processing.
Available Scenarios
Selection Criteria
All house bank accounts from the T012K table are automatically selected for the company codes you specified

In Scope
● Master data for bank accounts

● Descriptions in master data for bank accounts
● Currencies in master data for bank accounts
● Bank records
● Linkages between bank accounts and house bank accounts
Out of Scope
● Overdraft limits in the master data of bank accounts

● Signatories
● Simulation
Prerequisites
● FI - Bank
● FI - House bank
Source System
Not relevant
Target System
F_CLM_BAM (Authorization for Bank Account Management)
Name of this migration object: S4_AFS_CA_BANK_ACCOUNTS

BAPI_FCLM_BAM_AMD_BNKANT BAM Master Replication
Post-Processing
Not relevant
Create FI12_HBANK
Change FI12_HBANK
Display FI13_HBANK
Further Information
Purpose
This migration object enables you to migrate G/L accounts and primary cost elements from the source AFS
This migration technique transfers data to the target system using Application Programming Interfaces (API).
Related Business Object: G/L Accounts

General Ledger Master Records G/L Accounts
Individual Processing Centrally
Component: FI
Business Object Definition A structure that records value movements in a company

code and represents the G/L account items in a chart of ac
counts. A G/L account has transaction figures that record
changes to the account during a posting period. These fig
ures are totals that are used for G/L reporting.
Available Scenarios
Selection Criteria
This migration object derives the charts of accounts from the company codes you specified when defining the
migration scope. This migration object automatically selects all G/L accounts from the SKA1 table for the
derived charts of accounts.
 Note
The selected G/L accounts should be present in the SKB1 table for the specified company codes.
In Scope
● Standard G/L account types

● Company code views
● Chart of accounts views
● Types/descriptions
● Control data
● Create/bank/interest data
● Keyword/translation data
● G/L accounts present in a Chart of Accounts view
Out of Scope
● Blocked G/L accounts

● Custom G/L account types

Prerequisites
● Languages assigned to the charts of accounts in the source and target systems must match.
● If a group chart of accounts is active, all group accounts are maintained or migrated.
● If an alternate group account is active, all alternate accounts are maintained or migrated.
● P/L statement account types
● Company IDs of trading partners
● House banks
You have migrated or defined settings in the FI - House bank migration object.
Source System
Not relevant
Target System
F_SKA1_BUK (G/L Account: Authorization for Company Codes)
F_FICB_FKR (Cash Budget Management/Funds Management FM Area)
F_SKA1_BES (G/L Account: Account Authorization)
F_SKA1_KTP (G/L Account: Authorization for Charts of Accounts)
F_SKA1_AEN (G/L Account: Change Authorization for Certain Fields)
Name of this migration object: S4_AFS_FI_GL_ACCOUNT_MASTER
GL_ACCT_MASTER_SAVE G/L account master: Check and save

Post-Processing
Not relevant

Create FS00
Change FS00
Display FS00
Further Information
1.193 FI - G/L account balance (classic G/L)
Purpose
Component: FI


Available Scenarios
Selection Criteria
All G/L account balances from the GLT0 table belonging to non-open item managed accounts and profit & loss
accounts.
● Open-Item Managed(XOPVW)
● Account is Reconciliation Account(MITKZ)
● Clearing Specific to Ledger Groups(XLGCLR)
In Scope
● G/L account balances belonging to the general ledger 00 and additional currency ledgers assigned to the
specified company codes
 Note
Out of Scope

Prerequisites
and target systems
Source System
Not relevant
Target System
Not relevant
Name of this migration object: S4_AFS_FI_GL_ACC_BALANCE_CLA_GL
BAPI_ACC_DOCUMENT_POST: Mass Maintenance for Material Master Data
Virtual Tables
Post-Processing
Not relevant

Display FS10N
Further Information
1.194 FI - G/L account balance (new G/L)
Purpose
Component: FI

Available Scenarios

Selection Criteria
& loss accounts

In Scope
company codes.
 Note
If additional local currencies are assigned to company codes only in the target system, and not in the
source system, the system calculates the values of the local currencies in the target system.
Out of Scope
Prerequisites
and target systems.

and target systems
Source System
Not relevant
Target System
Not relevant
Name of this migration object: S4_AFS_FI_GL_ACC_BAL_NEW_GL
Virtual Tables
Post-Processing
Not relevant


Display FAGLB03
Further Information
1.195 FI - G/L open item (classic G/L)
Purpose
This migration object enables you to migrate G/L open item data from the source AFS system to the target
Component: FI

Available Scenarios
Selection Criteria

In Scope
 Note
Out of Scope
Tax lines
Prerequisites

must match
● Exchange rate
● PS - Network
● PS - Project

Source System
Not relevant
Target System
Not Relevant
Name of this migration object: S4_AFS_FI_GL_OI_CLASSIC_GL
Post-Processing
Create FB50
Change FB02
Display FB03
Further Information

1.196 FI - G/L open item (new G/L)
Purpose
Component: FI

Available Scenarios
Selection Criteria
when defining the migration scope
In Scope


 Note
Out of Scope
● Tax lines
● Postings in non-leading ledgers (BKPF-BSTAT = "L") only
Prerequisites

must match
● Exchange rate
● PS - Network
● PS - Project
Source System

Not relevant
Target System
Not Relevant
Name of this migration object: S4_AFS_FI_GL_OI_NEW_GL
Post-Processing

Create FB50
Change FB02
Display FB03
Further Information
1.197 FI - House bank

Purpose
This migration object enables you to migrate the house bank data from the source AFS system to the target S/
Related Business Object: House Bank
Accounts
Component: FI
Business Object Definition A business partner that represents a bank through which
you can process your internal transactions.
Available Scenarios
Selection Criteria
All house banks from the T012 table are automatically selected for the company codes that you specified when
In Scope
● Transfer structure object T012: House Bank

● Foreign payment transactions
● Data medium exchange (DME) parameters
Out of Scope
● Bank record structures

● Simulation

Prerequisites
You have migrated or defined settings in the FI - Bank migration object.
Source System
Not relevant
Target System
F_BNKA_BUK (Banks: Authorization for Company Codes)
Name of this migration object: S4_AFS_CA_HOUSE_BANK
BAPI_HOUSE_BANK_REPLICATE House Bank and House Bank Account Replicate
Post-Processing
Not relevant

Create FI12_HBANK
Change FI12_HBANK
Display FI13_HBANK

Further Information
1.198 FI - Ledger group specific open item
Purpose
This migration object enables you to migrate open item data specific to ledger groups from the source AFS
Interfaces (BAPIs).
Component: FI
Available Scenarios
Selection Criteria
All ledger groupspecific postings from the FAGLBSIS table are automatically selected for the company codes

In Scope

● Header data
 Note
Out of Scope
Tax lines
Prerequisites

must match
 Note
Before migration, create and activate the ACC_DOCUMENT BAdI implementation in the target system. For
more information, see SAP Note 2717381 .

● Exchange rate
● PS - Network
● PS - Project
Source System
Not relevant
Target System
Not relevant
Name of this migration object: S4_AFS_FI_GL_OI_LEDG_SPEC_NEW_GL
Virtual Tables
● LEDGER: To retrieve the entry views of the document.

● FAGL_REP_LED: To retrieve the data of the representative ledger.
Post-Processing
Deactivate the BAdI implementation after migration and before posting any new documents in the target
system.


Create FB50L
Change FB02
Display FB03
Further Information
1.199 Object classification (general template)
Purpose
This migration object enables you to migrate object classification data from the source AFS system to the
Related Business Object: Classification
Business Object Component/Area User Menu Path: Cross Application Components
Classification System Assignment Assign Object to
Classes
Component: CA
Business Object Definition The assignment of objects to a class. When you assign ob
jects to a class, you assign values for the object to the char
acteristics in the class.
Available Scenarios
Selection Criteria

In Scope
● Material class type (001)

● Equipment class type (002)
● Vendor class type (010)
● Customer class type (011)
● Document management class type (017/201)
● Work center class type (019)
● Variant class type (300)
Out of Scope
● Change numbers
● Class types for batch classification: 022 and 023
Prerequisites

● Class
● PM - Equipment
● Supplier
Source System
Not relevant
Target System
C_KLAH_BKP (Authorization for Class Maintenance)
C_TCLS_BER (Authorization for Org. Areas in Classification System)

C_KLAH_BKL (Authorization for Classification)
C_TCLS_MNT (Authorization for Characteristics of Org. Area)
Name of this migration object: S4_AFS_CA_CLASSIFICATION_ASSIGN
BAPI_OBJCL_CREATE Classification BAPI: Create Assignment
Virtual Tables
● CLASSES: To store the list of classes assigned to object classifications

● ALLOCVALUESNUM: To store numeric characteristic values
● ALLOCVALUESCHAR: To store character characteristic values
● ALLOCVALUESCURR1: To store currency characteristic values
Post-Processing
Not relevant
Create CL20N
Change CL20N
Display CL20N
Further Information

1.200 MM - Material inventory balance
Purpose
This migration object enables you to migrate material inventory balances with season data from the source
AFS system to the target SAP S/4HANA system based on the default selection criteria set for the migration
(APIs).
Related Business Object: Inventory
Inventory Management Goods Movement
Component: MM-IM
Available Scenarios
Selection Criteria
This migration object automatically selects all materials from the MARC table for the derived plants.
In Scope
● Material document header data

● Material document Items
● Stock types:
○ Unrestricted use stock (" ")
○ Stock in quality inspection ("X")
○ Blocked stock ("S")
● Special stock indicators:
○ Parts provided to vendor ("O")

○ Customer consignment stock ("W")
○ Returnable transport packing stock to customer ("V")
○ Sales order stock ("E")
○ Project stock ("Q")
○ Vendor consignment stock ("K")
○ Returnable transport packing stock to vendor ("M")
 Note
● Material valuation: If materials have a standard price control indicator or a moving average price
control indicator, the system migrates stock values from the following tables:
○ Table MBEW - for material valuation
○ Table QBEW - for project stock
○ Table OBEW - for sales order stock
● Transaction or Event for Migration
○ GM_CODE = ‘05’ (Other Goods Receipts)
○ Movement type = '561' (Initial Entry of Stock Balances)
Out of Scope
● Extensions in
● Special stock indicators other than specified in the in-scope section
● Industry solutionspecific fields
● Serial numbers
● Transactions/events:
○ GM_Code 01: Goods receipt for purchase order.
● Material document EWM references
● Service parts for SPM
● Item data for Catch Weight Management
● Print control for material documents
● Stocks in transit
Prerequisites

● AFS - Article
● Supplier: Migrate the Supplier migration object if the special stocks are:
○ Vendor consignment (“K”)
○ Returnable transport packing stock to vendor ("M”)
○ Parts provided to the vendor (“O” )
● Customer: Migrate the Customer migration object if the special stocks are:
○ Customer consignment stock(“W”)
○ Returnable transport packing stock to customer ("V”)
● MM - Purchasing info record: Migrate the MM - Purchasing info record migration object for the
Consignment info category if the special stock is vendor consignment stock (“K”).
● SD - Sales order: Migrate the SD - Sales order migration object if the special stock is sales order
stock( “E”).
 Note
If the special stock is project stock (“Q”), you need to manually create the Project object in your target SAP
S/4HANA system.
Source System
Not relevant
Target System
M_MSEG_BWA (Goods Movements: Movement Type)
M_MSEG_WWA (Goods Movements: Plant)
M_MSEG_LGO (Goods Movements: Storage Location)
Name of this migration object: S4_AFS_MM_STOCK
FSH_API_GOODSMVT_CREATE: Post goods movements with MB_CREATE_GOODS_MOVEMENT

Virtual Tables
STKTAB: To store the inventory data for a material
Note that virtual tables do not exist in the database
System Actions
Batch-managed materials: If the target batch is set as blank in the batch mapping task, the system
automatically creates batches during migration. However, the new batch does not have other batch-relevant
information such as classification or segmentation.
Posting date mapping tasks: The system picks up the posting date from the Posting Date (YYYYMMDD)
mapping task for all inventory postings.
Post-Processing
Not relevant
Stock overview MMBE
List of Stock Values: Balances MB5L
Material Document List MB51
Further Information

Purpose
This migration object enables you to migrate purchase contract data from the source AFS system to the target
technique transfers data to the target system using Business Application Programming Interfaces (BAPI).
Related Business Object: Purchase Contract
Business Object Component/Area Component: MM-PUR (Outline Agreements)

materials or services are released (ordered, or called off), ac
cording to need, over a certain predefined period.
Available Scenarios
Selection Criteria
This migration object automatically selects all purchase contract data from the EKPO table for the derived
plants.
 Note
The relevant purchasing document category (BSTYP) for this migration object is 'K' (Purchasing Contract).
In Scope
● Purchasing document header data

● Purchasing document Item data
● Item condition validity data
● Item conditions
● Account assignment in purchasing document data
● Item condition scale value data
● Conditions (1-dimensional value scale) data
● Conditions (1-dimensional quantity scale) data
● Conditions header data
● Conditions item data
● Partner roles in purchasing data
● Item texts

● Header texts
● Plant addresses (default delivery address)
● Vendor address data
 Note
Purchasing contracts you set for deletion in the source AFS system are not migrated.
Any references to multi-level contracts are removed from the target SAP S/4HANA system.
Out of Scope
● Multi-level contracts
● AFSK-type contracts
● Account profit segment data
● VAS items
● Extensions in
● Technical data
Prerequisites
● AFS - Article
● Supplier
 Note
If the purchase contract contains project, network or WBS element data, you need to manually define the
corresponding objects in the target SAP S4HANA system:
● Project
● Network
● WBS element

Source System
Not relevant
Target System
M_RAHM_BSA (Document Type in Outline Agreement)
M_RAHM_EKO (Purchasing Organization in Outline Agreement)
M_RAHM_EKG (Purchasing Group in Outline Agreement)
M_RAHM_WRK (Plant in Outline Agreement)
V_KOND_VEA (Maintain Condition: Auth. for Use/Appl./Cond.Type/Table)
V_KONH_VKS (Condition: Authorization for Condition Types)
Name of this migration object: S4_AFS_MM_PURCHASING_CONTRACT
BAPI_CONTRACT_CREATE: BAPI to Create a Purchase Contract
Virtual Tables
● AS_EKPO: To handle purchasing contract items

● AS_EKKN: To handle account assignment data
● AS_EKPA: To handle partner roles in Purchasing
● AS_KONH: To handle header conditions
● AS_KONP: To handle item conditions
● AS_KONM: To handle 1-dimensional quantity scale conditions
● AS_KONW: To handle 1-dimensional value scale conditions
● APP_HDR_TEXT: To handle header texts
● APP_ITM_TEXT: To handle item texts
Post-Processing
Not relevant

Change ME32K
Display ME33K
Further Information
1.202 MM - Purchase order
Purpose
This migration object enables you to migrate open purchase order data from the source AFS system to the
Related Business Object: Purchase Order
Business Object Component/Area User Menu Path: Logistics Material management
Purchasing Purchase order
Component: MM-PUR

Available Scenarios
Selection Criteria

This migration object automatically selects relevant purchase orders from the EKKO table for the specified
company codes and relevant purchase order items from the EKPO table for the derived plants. Relevant
purchase orders and purchase order items are those that meet the following conditions:
● The value in the Purchasing Document Category (BSTYP) field is "F" (order) AND
● ThePurchase Order Not Yet Complete (MEMORY) field is not set for the purchasing document header AND
● The Delivery Completed Indicator (ELIKZ) field is not set for the purchasing document item.
In Scope
● Header data
● Header address data
● Header texts
● Item data
○ Standard
○ Third-party
○ Enhanced limits
○ Consignment
○ Subcontracting
○ Service and limits
● Item address data
Only the following account assignment categories:
○ Cost center
○ Asset
○ Project
○ Unknown
● Item schedule lines
● Purchase order item components for subcontracting
● Item texts
● Pricing data
● Manual service conditions
● Stock transport orders
● Export data
● Shipment data
● Partially processed orders
 Note
Purchase orders you set for deletion or cancellation in the source AFS system are not migrated.

Out of Scope
● Held (not yet complete) purchase orders

● Blocked item data
● Changes in message records (in the NAST table) and additional message data
● Documents attached to the purchase order
● Purchase orders for sales orders and non stock sales
● Release strategy data
● Planning data
● Open items for goods receipt or the invoice receipt clearing account
Prerequisites
● AFS - Article
● Supplier
If your purchase order contains network and service master data, you need to manually create the following
business objects in your target SAP S/4HANA system:
● Network
● Service Master
Checks for Partially Processed Orders in the Source AFS System

Before you migrate partially processed orders, execute the CNV_PE_PARTIAL_DELV_POORDS_ANA report in
your source AFS system for the company codes you specified when defining the migration scope.
 Note
The current scope of the report is the price impact created by the quantity scales only.

The report provides detailed information about partially processed orders such as deviation in quantity, net
price, and unit price at the condition type level.
This report displays partially processed orders and categorizes them into Consistent or Inconsistent orders.
Consistent orders are those which do not have an impact on pricing since the pricing remains the same across
all quantities. Orders that are impacted by pricing are termed as inconsistent orders.
The report provides a simulated price for partially processed orders that are in the inconsistent category. The
simulated price belongs to the remaining open quantities based on source pricing determination and quantities
scales setting.
The simulation enables you to make a decision about manually adjusting pricing in the target system for the
inconsistent orders. Some of the manual adjustments can be:
● Create new migrationspecific condition types and condition records with pricing adjustments.
● Create new condition records for each scale range with adjusted prices.
Based on your business requirement and the results of the report, you can also adopt any other approach to
manually adjust pricing.
How to Display the Simulated Pricing after Executing the Report
● After executing the report, check the Status column.

● If the status is green, there is no pricing inconsistency and you can migrate the order without making any
adjustments in the target system.
● If the status is red and if the order is migrated without any manual adjustments, there could be a price
inconsistency.
● Click the red status in the Status column to get the simulated prices. The simulated prices are updated in
the New Net Price and Difference Amount columns.
 Note
Double-click any column in the report to get the conditions and scales data if present.
Source System
Not relevant
Target System
M_BEST_BSA (Document type in PO)
M_BEST_EKG (Purchasing group in PO)
M_BEST_EKO (Purchasing organization in PO)
M_BEST_WRK (Plant in PO)

Name of this migration object: S4_AFS_LO_PO1
FSH_API_PURCHASINGORDER_CREATE Purchasing Order: Create PO
Virtual Tables
● APP_ADDR_HDR : To store addresses at the header level

● APP_POEXPIMPHEADER : To store export or import data of a foreign trade at the header level
● APP_POCONDHEADER : To store condition records at the header level
● APP_POCONTRACTLIMITS : To store contract limits of purchase orders
● APP_POTEXTHEADER : To store texts at the header level
● APP_POPARTNER : To store partner roles and partner functions
● APP_POLIMITS : To store the limits of service purchase orders
● APP_POSERVICES : To store service lines
● APP_POSRVACS : To store service access values for the assigned service lines at the purchase order item
level
● APP_ADDR_ITM : To store addresses at the item level
● APP_POITEM : To store the line items of a purchase order document
● APP_POSCHEDULE : To store schedule lines
● APP_POCOND : To store conditions records at the item level
● APP_POTEXTITEM : To store texts at the item level
● APP_FSH_ITEM : To store fashion-relevant fields at the item level
● APP_POEXPIMPITEM - To store the export or import data for a foreign trade at the item level
● APP_POCOMPONENTS : To store the components of a purchase document
● APP_POSHIPPINGEXP : To store export shipping data
● APP_POACCOUNT : To store account assignment fields at the item level
● APP_POSHIPPING : To store shipping data only for stock transport orders
Post-Processing
Not relevant


Change ME22N
Display ME23N
Further Information
1.203 MM - Purchasing info record
Purpose
This migration object enables you to migrate purchasing info record data from the source AFS system to the
Related Business Object: Purchasing Info Record
Purchasing Master Data Info Record
Component: MM-PUR
Available Scenarios
Selection Criteria
This migration object automatically selects the info records (except pipeline records) from the EINA table for
the derived plants.

In Scope
● Info records type

○ Standard
○ Consignment
○ Subcontracting
● General data
● Purchase organization data
● Conditions
● Texts
 Note
Condition records with expired valid-to dates in the source AFS system are not migrated.
Out of Scope
● Pipeline info record type

● Any document references such as quotations, purchase requisitions, purchase orders and the last
purchase order number
● Conditions with expired validity periods
● Industryspecific fields
● Info records set for deletion
● Segment-level long texts.
Prerequisites
● AFS - Article
● Supplier
Source System

Not relevant
Target System
M_EINF_EKO (Purchasing Organization in Purchasing Info Record)
M_EINF_EKG (Purchasing Group in Purchasing Info Record)
M_EINF_WRK (Plant in Purchasing Info Record)
Name of this migration object: S4_AFS_LO_PURCH_INFO_RECORD
ME_INFORECORD_MAINTAIN_MULTI RFC Function Module to Create and Change multiple Info Records
ME_DB_UPDATE_INFORECORDS Updating info records in database
Virtual Tables
● EINA_SPLIT: To store AFS material data related to grids present in purchasing info records
● EINE_SPLIT: To store PIR records split according to material grids
● COND_VALIDITY: To store PIR condition validities
● CONDITION: To store PIR conditions
● COND_SCALE_VALUE: To store value scales for PIR conditions
● COND_SCALE_QUAN: To store quantity scales for PIR condition
● PIR_TEXT: To store long texts of info records
●
Post-Processing
Not relevant


Create ME11
Change ME12
Display ME13
Further Information
Purpose
This migration object enables you to migrate purchase scheduling agreement data from the source AFS
Interfaces (BAPIs).
Related Business Object: Purchase Scheduling Agreement
Purchasing Outline Agreement Scheduling
Agreement
Component: MM-PUR (Outline Agreements)
Business Object Definition An outline agreement against which materials are procured
at a series of predefined points in time over a certain period.
Available Scenarios
Selection Criteria

This migration object automatically selects all purchase scheduling agreements from the EKKO table for the
 Note
The value in the Purchasing Document Category (BSTYP) field is "L" (Purchase Scheduling Agreement).
In Scope
● Standard purchasing scenarios

● Consignment scenarios
● Subcontracting scenarios
● Third-party scenarios
● Scheduling agreements with time-dependent conditions (EKKO-STAKO = "X")
● Scheduling agreement header data
● Scheduling agreement items data
● Header and item long texts
● Account assignment data
● Delivery schedule lines
● Shipping data for stock transport orders
● Header conditions data
● Item conditions data
● Validity period of header conditions
● Validity period of item conditions
● Value scale and quantity scale of header conditions
● Value scale and quantity scale of item conditions
● Foreign trade data
● Partner data
● Delivery addresses
 Note
Purchase scheduling agreements you set for deletion in the source AFS system are not migrated
Out of Scope
● Account profitability segment calculation data

● Shipping export data
● Stock transport scheduling agreements
● Release strategy

Prerequisites
● AFS - Article
● Supplier
 Note
In Customizing for source list requirements at the plant level, see: Materials Management Purchasing
Source List Define Source List Requirement at Plant Level .
If the source list is enabled for plants derived from company codes specified when defining the migration
scope, it is recommended to include the MM - Source list migration object in the migration project
containing the MM - Purchase scheduling agreement migration object.
Source System
Not relevant
Target System
● M_RAHM_BSA (Create/Update/Display outline agreements using the document type)

● M_RAHM_EKO (Create/Update/Display outline agreements using the purchasing organization)
● M_RAHM_EKG (Create/Update/Display outline agreements using the purchasing group)
● M_RAHM_WRK (Create/Update/Display outline agreements using the plant)

Name of this migration object: S4_AFS_MM_SCHEDULING_AGREEMENT
● BAPI_SAG_CREATE: Create a Scheduling Agreement

● BAPI_SCHEDULE_MAINTAIN: Maintenance of Scheduling Agreement Delivery Schedule Lines
Virtual Tables
● AS_ITM_TXT: To store item long texts

● AS_ITEMS: To store items
● AS_EKET: To store schedule lines information
● AS_HDR_TXT: To store header long texts
Post-Processing
Not relevant

Create ME31L
Change ME32L
Display ME33L
Further Information

Purpose
This migration object enables you to migrate source list data from the source AFS system to the target SAP S/
Related Business Object: Source List
Business Object Component/Area Component: MM-PUR (Source List )
possible. The source list lets you determine the source that
is valid (effective) at a certain time.
Available Scenarios
Selection Criteria
This migration object derives plants and materials from the company codes you specified when defining the
migration scope. This migration object automatically selects the materials from the MARC table for the derived
plants.
 Note
If the new source list you provided in the mapping already exists in the target system, after migration, the
target system data is overwritten with the source list data from the source system.
In Scope
● Material number
● Plant
● Source list usage in materials planning
● Agreement number(Purchase schedule agreement)
● Agreement item(Purchase schedule agreement item)
● Purchasing organization
● Valid To field in the source list record
● Fixed Supplier indicator
● Blocked source of supply
● Valid From field in the source list record

Out of Scope
● Logical system
● Product fields relevant for Purchasing
● Agreement number(Purchase contract)
● Agreement item(Purchase contract item)
Prerequisites
● AFS - Article
● MM - Purchasing contract
● Supplier
 Note
In Customizing for source list requirements at the plant level, see: Materials Management Purchasing
Source List Define Source List Requirement at Plant Level .
If the source list is enabled for plants derived from company codes specified when defining the migration
scope, it is recommended to include the MM - Purchase scheduling agreement migration object in the
migration project containing the MM - Source list migration object.
Source System
Not relevant
Target System
M_ORDR_EKO (Purchasing Organization in Source List)
Name of this migration object: S4_AFS_MM_SOURCE_LIST

ME_DIRECT_INPUT_SOURCE_LIST: NOTRANSL: Orderbuchpflege innerhalb der integrierten Artikelpflege
Virtual Tables
AS_EORD: To store AFS materials as variants, as target system expected
Post-Processing
Not relevant

Create ME01
Change ME02
Display ME03
Further Information
1.206 PM - Equipment
Purpose
This migration object enables you to migrate equipment data from the source AFS system to the target SAP S/
Related Business Object: Equipment

Management of Technical Objects Equipment
Component: PM

omous unit.
Available Scenarios
Selection Criteria
This migration object automatically selects the equipment from the ILOA table for the derived plants.
In Scope
● General data for technical objects

● Equipmentspecific data
● Vehiclespecific data
● Valid-from date for equipment
● Object links for document info records
● Installation date for equipment
 Note
● You can migrate only the latest time segment data (valid-from date for equipment) to the target
system.
● You can set only one language for the migration of equipment data.
● Equipment data with the DLFL system status is migrated with the AVLBsystem status.
Out of Scope

● Extensions in
● User definedstatus
● Equipment long texts
● Classification

● Equipment address
● Partners
● Historical equipment data
 Note
You can simulate only this feature:
Create equipment
The following feature is out of scope for simulation:
Document info record assignment
Prerequisites
Source System
Not relevant
Target System

Name of this migration object: S4_AFS_PM_EQUIPMENT
BAPI_EQUI_CREATE PM BAPI: Create Equipment
Virtual Tables
● ILOA_WC: To store internal work center numbers

● ILOA_WBS: To store internal WBS elements
● ILOA_FLOC: To store internal functional location names
● EQUZ_WC: To store internal main work center numbers
System Actions
In the Equipment Number mapping task, if the target equipment number is set as blank, the system creates
equipment using internal numbers defined for that equipment category.
Superordinate equipment: If superordinate equipment is assigned to an equipment, you need to migrate the
superordinate equipment before migrating the equipment. If you don't follow this migration sequence , the
system displays the Equipment could not be read error.
Post-Processing
Create IE01
Change IE02
Display IE03
Further Information

1.207 PP - Material BOM
Purpose
This migration object enables you to migrate material BOM data from the source AFS system to the target SAP
Related Business Object: Material BOM
Bills of Material Bill of Material Material BOM
Create
Component: PP-BD
Business Object Definition A bill of material created with reference to a material master.
The BOM can contain items of different item categories such
as stock items, non-stock items, document items, and text
items.
Available Scenarios
Selection Criteria
This migration object automatically selects material BOMs from the MAST table for the derived plants
In Scope
● Basic data
● BOM items
● BOM sub-items
● BOM long texts
● Alternative long texts
● Item long texts

● BOM local dependency
● All alternative BOM numbers (from 01 to 99)
● Change numbers
● Deviation quantity for the Fashion BOM variant
● BOM segmentation
Out of Scope
● Deletion of BOM headers, items and dependencies

● Configurable material BOM
Prerequisites
● AFS - Article
● Class
● Supplier
Source System
Not relevant
Target System
C_STUE_NOH (Create/Update/Display of BOM which has a History Requirement without using a Change
Number)

Name of this migration object: S4_AFS_PP_MATERIAL_BOM
● CSAI_BOM_MAINTAIN: NOTRANSL: API Stücklisten: Stückliste pflegen (E,T,M,K,P)

● CSAP_MAT_BOM_MAINTAIN: NOTRANSL: API Stücklisten: Materialstückliste pflegen
Virtual Tables
● CSDEP_DAT: To handle the basic data of a dependency

● CSDEP_DESC: To handle object dependency descriptions
● CSDEP_ORD: To handle sort sequences of object dependencies
● CSDEP_SORC: To handle the source code of object dependencies
● CSDEP_DOC: To handle object dependency documentation
● CSDOC_LINK: To handle document assignments
● CSDMU_TMX: To handle DMU transformation matrixes
● CSLTX_LINE: To handle long texts
● FSH_BOMD: To handle deviation quantities for the Fashion BOM variant
● SGT_BOMC: To handle BOM segmentation
Error during the migration of BOM records

If the migration of a BOM record ends in error, the following error message is displayed: BOM <Material
number>/<Plant>/<Usage> is locked by <Username>.
● Reasons for the error

The BAPI allows the posting of BOMs for generic articles that have a single related variant or multiple
related variants. However, when the number of variants is very large, the BAPI ends in error.
● Possible scenarios resulting from the error
○ The BOM record is partially migrated or
○ The BOM record is not migrated at all
● Scenario: Data partially migrated
If the data is partially migrated, you can process it again.
1. Go to transaction code CS02 in the target SAP S/4HANA system.
2. Manually delete the partially processed data.
3. Migrate the data again.
● Scenario: Data not migrated
If the data is not migrated at all, you cannot migrate the same record again. Contact SAP for a solution.
Post-Processing
Not relevant

Change CS02
Display CS03
Further Information
1.208 PP - Routing
Purpose
This migration object enables you to migrate routing data from the source AFS system to the target SAP S/
Related Business Object: Routing Group
Routings Routings Standard Routings
Component: PP-BD-RTG
Business Object Definition A description of the production process used to manufac

industry.
Available Scenarios
Selection Criteria

This migration object automatically selects all routing groups from the PLKO table for the derived plants.
In Scope
● Routing data with task list type "N"

● Routing groups assigned to variants
● Modified records using engineering change number (ECN)
● Material task list assignments
● Sequences
● Operations
● Suboperations
● Component assignments
● Long texts
 Note
Routing groups data you set for deletion in the source AFS system is not migrated
 Note
the S/4 HANA system:
● PM - Equipment
Out of Scope
● Routing group data created with ECN
● Other task list types: "0", "2", "3", "A", "E","M", "Q", "R", "S", "T", "V"
 Note
If you have multiple migrations steps, you can simulate the initial routing group data created without ECN.
During the migration phase, errors may occur for features that were not in scope during simulation, even

Prerequisites
● If you need standard text keys in routing data, you have configured the keys in the SAP S/4 HANA system.
● Before migrating routing data, you have set the ROUTING_N number range object to external number range
in the target system. After migration, you can choose to set the number range object back to internal
number range.
● AFS - Article
 Note
the S/4 HANA system:
● PM - Equipment
Source System
Not relevant
Target System
Select all values for the ACTVT field except 41.
Name of this migration object: S4_AFS_PP_ROUTING_ECN
● BAPI_ROUTING_CREATE: Creation of a Routing

● ROUTING_MAINTAIN: NOTRANSL: Ändern eines Arbeits-/Prüfplans
Virtual Tables

● COM: To handle component allocations
● SUBOPR: To handle suboperations
● MAPL_TAB: To handle assignments of routing groups to variants
● SEQTAB: To handle activities of sequences
● TEXT_HDR: To handle header long texts
● TEXT_ITEM: To handle item long texts
● PRT_TAB: To handle PRT items and activities
● CSLA_TAB: To handle the controlling area of operations activity types
● PLKO_TAB: To handle header ECN records
Post-Processing
Not relevant
Create CA01
Change CA02
Display CA03
Further Information
1.209 PP - Planned independent requirement

Purpose
Interfaces (BAPIs).
Planning Demand Management Planned Independent
Requirements
Component: PP-MRP
Available Scenarios
Selection Criteria
This migration object automatically selects all planned independent requirements from the PBIM table for the
derived plants.
In Scope
● Items belonging to all non-"Apparel" categories under Material Type

● Items belonging to the "Raw materials" category under Material Type
● Schedule lines belonging to all non-"Apparel" categories under Material Type
● Schedule lines belonging to the "Raw materials" category under Material Type
 Note
Independent requirements you set for deletion in the source AFS system are not migrated.
Out of Scope
● Configuration supporting points for schedule lines

● Withdrawal quantity of schedule lines (see SAP Note 793258 )
● Item texts
● Schedule line texts
Prerequisites
You have migrated or defined settings in the AFS - Article migration object
Source System
Not relevant
Target System
Name of this migration object: S4_AFS_LO_PLANNED_IND_REQMT_CORE
Post-Processing
Not relevant


Create MD61
Change MD62
Display MD63
Further Information
1.210 PP - Production version
Purpose
This migration object enables you to migrate production version data from the source AFS system to the target
Related Business Object: Production Version
Production Versions
Component: PP
ing to which a material is to be manufactured. You specify
the following in the production version:
● The BOM alternative for BOM Explosion

counter for assignment to routing
Available Scenarios

Selection Criteria
This migration object automatically selects the production versions from the MKAL table for the derived plants.
In Scope
● General data for production versions (key, lot-size range, validity period)
● Detailed planning levels
● Check statuses
 Note
If the detailed level data is not present in the source system, this migration object automatically maps rate-
based planning details to the detailed level for REM materials.
For information about migrating rate and rough-cut planning data, see SAP Note 2270240 .
Out of Scope
Not relevant
Prerequisites
● AFS - Article
● PP - Routing
Source System
Not relevant
Target System

C_FVER_WRK (PP-PI: Production Version - Plant)
Name of this migration object: S4_AFS_PP_PRODUCTION_VERSION
FV_PROD_VERS_MAINTAIN_MULTI Maintain Multiple Production Versions
Virtual Tables
MKAL_VAR: To store the production versions of materials with grid values.
Post-Processing
Production Version Mass Processing C223
Display Material MM03
In the MM03 transaction, navigate to the MRP4 tab and the

choose Prod Versions button.
Further Information

1.211 PP - Production order
Purpose
This migration object enables you to migrate production order data from the source AFS system to the target
Related Business Object: Production Order
Business Object Component/Area User Menu Path: Logistics Production Shop Floor
Control Order Create with Material
Component: PP
Business Object Definition An authorization from the production department to pro

duce a specific quantity of material within a predefined time.
The production order contains all the information required
for the execution of the production process.
Available Scenarios
Selection Criteria
This migration object automatically selects relevant production orders from the J_3ABSSI table for the derived
plants if the following conditions are met:
● The stock type (J_3ABSSI-J_3ABSKZ ) is "F" (production order) AND

● The AFS Delivery Completed Indicator at SKU Level in Production field (J_3ABSSI-J_3AELIKZ) is not
"X" (Yes) AND
● The AFS Indicator Technical Completed field (J_3ABSSIJ_3ATCKZ) is not "X" (Yes) AND
● The Delivery Completed Indicator field ( AFPO-ELIKZ) is not "X" (Yes).
In Scope
Production orders with deliveries not started

 Note
Production orders you set for deletion in the source AFS system are not migrated.
Out of Scope
● Partially-delivered production orders

● Production orders with technically complete status
● Long texts for production orders
● Production orders with sales order references
● Production orders marked for deletion
● Production orders from planned orders
● Collective conversion of planned orders
● Production orders without materials
Prerequisites
● AFS - Article
● PP - Production Version
● PP - Routing
Source System
Not relevant
Target System
● C_AFKO_ATY (CIM: Order category)

● C_AFKO_AWA (CIM: Authorization for Prod. Order/Order Type/Plant/Activity)
● C_AFKO_AWK (CIM: Plant for Order Type of Order)
● C_STUE_BER (CS BOM Authorizations)
● C_STUE_WRK (CS BOM Plant (Plant Assignments)
● C_TCLA_BKA (Authorization for Class Types)

Name of this migration object: S4_AFS_PP_PRODUCTION_ORDER
● BAPI_PRODORD_CREATE Creates Production Orders

● FSH_PP_PCW_CREATE_MASTER Create Master Planned Order or Master Production Order
● FSH_PP_PCW_MODIFY_MASTER Modify Master Order
Production Order Variants
This migration object creates multiple production orders for every production order in the AFS system that
contains generic material with multiple variants.
After migration, this migration object groups production order variants under a master production order with
the Created status.
 Example
A T-shirt with 3 variants has a production order in the source system. This migration object creates 3
production orders in the target system and groups the three orders under a master production order.
Production Order Dates
The basic dates (start date and end date) for production orders in the target system is picked up from the
configuration set in Customizing for scheduling parameters of production orders.
Post-Processing
After migration, you can release the production orders using the transaction code (FSH_PCW) for the
Production Control workbench. Ensure that the settlement profile and cost estimates are already customized
in the target system to ensure an error-free post processing.

Create Production Order CO01
Change Production Order CO02
Display Production CO03

Production Control Workbench FSH_PCW
Further Information
1.212 PP - Sales order BOM
Purpose
This migration object enables you to migrate bills of material data from the source AFS system to the target
Business Object Component/Area User Menu Path: Logistics Production Bill of
Materials Bill of Material Order BOM
Component: PP-BD
Business Object Definition A single-level BOM that you generate for a sales order from a
material BOM, and that you modify specific to the order. In
this way, the material BOM remains unchanged. An order
BOM is uniquely identified by the sales order number, the
sales order item, and the material number. Order BOMs can
be created for configurable and nonconfigurable materials.
Available Scenarios
Selection Criteria
This migration object automatically selects bills of material from the KDST table for the derived plants.

In Scope
● Bills of material of type "K" (material-based)

● Header data
● Sub-items
● Long texts
● Change numbers
● Deviation quantities for the Fashion BOM variant
● BOM segmentation
Out of Scope
● Component item C - Compatible unit

● Component item I - PM structure element
● Component item K - Class item
● Component item M - Intra-material
● Component item R - Variable size item
Prerequisites
● AFS - Article
Source System
Not relevant
Target System
C_STUE_NOH (Create/Update/Display of BOM which has a History Requirement Without Using a Change
Number)

Name of this migration object: S4_AFS_PP_SO_BOM
CSAI_BOM_MAINTAIN: NOTRANSL: API Stücklisten: Stückliste pflegen (E,T,M,K,P)
Virtual Tables
● BOM_TXT: To store BOM long texts

● ITM_TXT: To store BOM item long texts
● DRAD_ITM: To store document object links
● FSH_BOMD: To store deviation quantities for the Fashion BOM variant
● SGT_BOMC: To store BOM segmentation
Error during the migration of BOM records

If the migration of a BOM record ends in error, the following error message is displayed: BOM <Sales order>/
<Item number>/<Material number>/<Plant>/<Usage> is locked by <Username>.
● Reasons for the error

The BAPI allows the posting of BOMs for generic articles that have a single related variant or multiple
related variants. However, when the number of variants is very large, the BAPI ends in error.
● Possible scenarios resulting from the error
○ The BOM record is partially migrated or
○ The BOM record is not migrated at all
● Scenario: Data partially migrated
If the data is partially migrated, you can process it again.
1. Go to transaction code CS62 in the target SAP S/4HANA system.
2. Manually delete the partially processed data.
3. Migrate the data again.
● Scenario: Data not migrated
If the data is not migrated at all, you cannot migrate the same record again. Contact SAP for a solution.
Post-Processing
Not relevant

Change CS62
Display CS63
Further Information
1.213 PP - Work center
Purpose
This migration object enables you to migrate work center data from the source AFS system to the target SAP
Related Business Object: Work Center
Business Object Component/Area User Menu Path: Logistics Production Master data
Work centers Work center

Business Object Definition Organizational unit that defines where and by whom an oper
ation is performed. The work center has an available ca
pacity. The activities performed at or by the work center are
valuated by charge rates, which are determined by cost cen
ters and activity types. Work centers can be:
● Machines
● People
● Production lines
● Groups of craftsmen
Available Scenarios
Selection Criteria
This migration object automatically selects all work centers from the CRHD table for the derived plants.
In Scope
● Basic data
● Default values
● Capacities
● Scheduling information
● Costing information
● Technical data
Out of Scope
Work center description in languages other than the logon language
Prerequisites

Source System
Not relevant
Target System
C_ARPL_WRK (CIM: Work center - plant)
C_ARPL_ART (CIM: Work center category)
Name of this migration object: S4_AFS_LO_WORK_CENTER
CRAP_WORKCENTER_CREATE API work centers: create work center
Virtual Tables
● CRCO_RCVAPI: To handle work center assignments to cost centers.
Post-Processing
Not relevant
Create CR01
Change CR02
Display CR03

Further Information
1.214 Pricing condition (purchasing and sales)
Purpose
This migration object enables you to migrate pricing condition data from the source AFS system to the target
Related Business Object: Pricing Condition
Business Object Component/Area User Menu Path:
Logistics Material Management Purchasing Master
Data Conditions
Logistics Sales and Distribution Master Data
Conditions
Components: MM-PUR and SD
Business Object Definition Sales: A data element used to define prices according to cri
teria selected by the user.
Purchasing: The terms of payment negotiated with a vendor,

such as surcharges or discounts. Pricing conditions deter
mine how the system calculates the effective price in a pur
chase order.
Available Scenarios
Selection Criteria

All pricing condition records belonging to Sales and Distribution and Purchasing are automatically selected
● Condition Usage field (KVEWE) is set as A (pricing) AND

● Application field (KAPPL) is set as M (purchasing) AND V (sales)
In Scope
● Pricing conditions for prices, surcharges and discounts

● Condition headers
● Condition items
● Quantity and value scales
 Note
Pricing condition records used in purchase contracts, purchase info records, sales contracts, and
scheduling agreements are migrated as part of the relevant migration objects.
Out of Scope
● Exclusion indicators
● Condition texts
● Additional data (payment terms, fixed value dates, additional value days, assignments)
● Pricing condition records that belong to applications not in Sales and Purchasing.
Prerequisites
● AFS - Article
● Customer
● Supplier
Source System

Not relevant
Target System
● V_KONH_VKS (Condition: Authorization for Condition Types)

● V_KONH_VKO (Condition: Authorization for Sales Organizations)
● V_KONH_EKO (Purchasing Organization in Master Condition)
Name of this migration object: S4_AFS_LO_PRICING_COND
COND_GEN_MIGRATION_CREATE Condition Migration: Create Condition Records
Virtual Tables
● APP_COND_KEY_FIELDS: To store information of condition key fields

● APP_QUAN_SCAL_VAL: To store information of scales data
● APP_KONP: To store condition item data
Post-Processing
Not relevant
Condition Maintenance: Display VK33
Display Condition Records MEK3
Display Condition Records VK13

Further Information
For information about key field combinations for price conditions, see SAP Note 2332748 .
Purpose
This migration object enables you to migrate sales contract data from the source AFS system to the target SAP
Related Business Object: Sales Contract
Sales Contract
Component: SD
Business Object Definition An outline agreement that contains special conditions nego
tiated between the supplier and a customer, for example,
price, target value, or target quantity. A sales contract is
der to release materials or services from the amount or
value agreed in the contract.
Available Scenarios
Selection Criteria
migration scope. This migration object automatically selects relevant sales contracts from the VBAK table for
the derived sales organizations.
Relevant Selection Criteria
The relevant sales document categories (VBAK-VBTYP) for this migration object are G ("Contract") and 0
("Master Contract").

In Scope
● Header data
● Items data
● Partners data
● Conditions data
● Contract data
● Long texts
● Partner addresses
● Tax classification
 Note
This migration object also migrates partially processed contracts. If a contract has any subsequent delivery
documents, the contract is considered as a partially processed contract. Before migration, this migration
object removes the quantity already delivered to the business partner from the partially processed
contract.
Out of Scope
● Sales contract configurations

○ Reference data
○ Instances
○ Parts of specifications
○ BLOB internal data
○ Variant condition keys
○ Reference items/instances
● Sales contract keys
● Userdefined fields in the sales contract
● Industryspecific solution fields
● Document flows
● Output types
● Billing plans
● Customer enhancements for VBAK, VBAP, and VBEP tables
● Reference structure for the ExtensionIn and ExtensionOut BAPI parameters
Prerequisites

● AFS - Article
● AFS - Sales grid condition record
● Customer
Source System
Not relevant
Target System
● V_VBAK_VKO (Create/Update/Display of sales documents using the sales areas)

● V_VBAK_AAT (Create/Update/Display of sales documents using the sales document type)
● V_VBAK_CCD (Create/Update/Display of sales document payment cards)
Name of this migration object: S4_AFS_LO_SALES_CONTRACT
FSH_API_SALESDOCUMENT_CREATE Sales Order: Create Sales Order
Virtual Tables
● SORD_TEXT: To store long texts for sales contracts

● ITEM_DATA : To store the item and schedule lines of sales contracts
● COND_DATA: To store condition records of header and item levels in sales contracts
● PARTNER_DATA: To store the assigned business partners in a sales contract
● VAS_DATA: To store the value-added services
● HEADER_DATA: To store the header and business data of a sales contract
● CONTRACT_DATA: To store sales contract data
● VAS_TEXT_TL: To store the long texts of value-added services for ticketing and labeling
● VAS_TEXT_PAC: To store the long texts of value-added services for packing
● VAS_TEXT_SER: To store the long texts of value-added services for special services
● LONG_TEXT: To store long texts for sales contracts
● LONG_TEXT_VAS: To store long texts for value-added services

Post-Processing
Not relevant
Change VA42
Display VA43
Further Information
1.216 SD - Sales order
Purpose
This migration object enables you to migrate open sales order data from the source AFS system to the target
Related Business Object: Sales Order
Sales Order
Component: SD

services at a certain time. The request is received by a sales
area that is then responsible for fulfilling the contract.
Available Scenarios
Selection Criteria
migration scope. This migration object automatically selects sales orders from the VBAK table for the derived
sales organizations if the following condition is met: The SD document category (VBAK-VBTYP) is "C" (order).
In Scope
● Order header data

● Item data
● Partner data
● Conditions
● Texts
● Partially processed orders
● Third-party orders that (1) have subsequent purchase orders with the Delivery status and (2) do not have a
goods receipt assigned to the schedule lines
● References to other sales documents such as sales contracts or sales orders
Out of Scope
● Configurable items
● Return orders
Prerequisites
Target System

● AFS - Article
● Customer
Manual Pricing
In Customizing for Sales and Distribution, go to the V/08 transaction or go to Basic Functions Pricing
Define and Assign Pricing Procedures . Select the Set Pricing Procedures activity. Open the relevant pricing
procedure assigned to the sales document to be migrated. Set the condition types to be processed manually
by selecting Manual only.
Carrying out the Customizing listed above enables manual pricing for price determination. As a result, this
migration object transfers the as-is conditions from the source AFS system to the target SAP S/4HANA
system.
Source System
Checks for Partially Processed Orders in the Source AFS System
Before you migrate partially processed orders, execute the CNV_PE_PARTIAL_DELV_ORDS_ANA report in your
source AFS system for the company codes you specified when defining the migration scope.
 Note
The current scope of the report is the price impact created by the quantity scales only.
The report provides detailed information about partially processed orders such as deviation in quantity, net
price, and unit price at the condition type level.
This report displays partially processed orders and categorizes them into Consistent or Inconsistent orders.
Consistent orders are those which do not have an impact on pricing since the pricing remains the same across
all quantities. Orders that are impacted by pricing are termed as inconsistent orders.
The report provides a simulated price for partially processed orders that are in the inconsistent category. The
simulated price belongs to the remaining open quantities based on source pricing determination and quantities
scales setting.
The simulation enables you to make a decision about manually adjusting pricing in the target system for the
inconsistent orders. Some of the manual adjustments can be:
● Create new migrationspecific condition types and condition records with pricing adjustments.
● Create new condition records for each scale range with adjusted prices.
Based on your business requirement and the results of the report, you can also adopt any other approach to
manually adjust pricing.
How to Display the Simulated Pricing after Executing the Report
● After executing the report, check the Status column.

● If the status is green, there is no pricing inconsistency and you can migrate the order without making any
adjustments in the target system.
● If the status is red and if the order is migrated without any manual adjustments, there could be a price
inconsistency.

● Click the red status in the Status column to get the simulated prices. The simulated prices are updated in
the New Net Price and Difference Amount columns.
 Note
Double-click any column in the report to get the conditions and scales data if present.
Source System
Not relevant
Target System
Name of this migration object: S4_AFS_LO_SALES_ORDER
FSH_API_SALESDOCUMENT_CREATE Sales order: Create Sales Order
Virtual Tables
● SORD_TEXT: To store long texts of sales orders

● ITEM_DATA : To store the item and schedule lines of sales orders
● COND_DATA: To store condition records at the header and the item levels in sales orders
● PARTNER_DATA: To store the assigned business partners of a sales order
● VAS_DATA: To store value-added services
● HEADER_DATA: To store the header and business data of sales orders
● VAS_TEXT_TL: To store the long texts of value-added services for ticketing and labeling
● VAS_TEXT_PAC: To store long texts of value-added services for packing
● VAS_TEXT_SER: To store long texts of value-added services for special services
● LONG_TEXT: To store long texts of sales orders
● LONG_TEXT_VAS: To store long texts for value-added services

Post-Processing
Adjust the pricing procedures to the required settings in the SAP S/4HANA system.

Change VA02
Display VA03
Further Information
1.217 Supplier
Purpose
This migration object enables you to migrate vendor (supplier) data from the source AFS system to the target
Related Business Object: Vendor
Purchasing Master Data Vendor
Component: MM
Business Object Definition A business partner who supplies goods and delivers them to
consumers/customers.

Available Scenarios
Selection Criteria
defining the migration scope. This migration object automatically selects all vendors from the LFA1 table for
the company codes and derived purchasing organizations.
In Scope
● General data with standard addresses

● International address versions
● General texts
● Accounting texts
● Purchasing data
● Purchasing texts
● Contact persons
● Extensions of existing vendors with new organizational levels
● Extensions of existing customers as suppliers with the same business partner numbers
 Note
● If a vendor in the source system is extended to multiple company codes, after data migration, the
supplier in the target system is extended only to the participating company codes.
● If a vendor in the source system has multiple purchase organizations, after data migration, the supplier
in the target system contains only the selected purchase organizations.
Out of Scope
● Documents assigned to the vendor

● Classifications
● Updates of existing fields
● Extensions of withholding tax data to existing company codes
● Extensions of existing addresses
● Extensions of purchasing organizations belonging to existing company codes

Prerequisites
Source System
Before you can start the migration process, ensure that you have maintained the values for all fields defined as
mandatory in the target system. Otherwise, errors may occur after migration. Alternatively, blank values are
populated in the mandatory fields after data migration.
Target System
● Provided the vendor account group in the Vendor Account Group (MAP_KTOKK) mapping task. Doing so
enables the migration object to determine the business partner groupings and roles from the following
Customizing paths:

Business Partner Settings Settings for Vendor
Integration Define BP Role for Direction Vendor to BP

Synchronization Business Partner Settings Settings
for Vendor Integration Field Assignment for Vendor
Integration Assign Keys Define Number Assignment
for Direction Vendor to BP
● Registered the CVI_EI_INBOUND_REQ_ACTIVATE function module using the transaction code

CRMC_BUT_CALL_FU with the following entries:
Event CRM Inbound
Call Selected
● Bank
● Customer

If the customer and vendor refer to the same business entity in the source system, please migrate the
● FI-G/L account
Source System
Not relevant
Target System
● F_LFA1_GEN Vendor Central Data

● F_LFA1_BUK Vendor Authorization for Company Codes
● F_LFA1_APP Vendor Application Authorization
● F_LFA1_GRP Vendor Account Group Authorization
● F_LFA1_BEK Vendor Account Authorization
● M_LFM1_EKO Purchasing Organization in Supplier Master Record
Name of this migration object: S4_AFS_LO_PUR_VEND_MAST_CRE
CMD_MIG_BP_CVI_CREATE Create New Business Partners with CVI and New Segments Insertion
This migration object derives the business partner category based on the vendor title defined in the TSAD3
Customizing table. If the vendor title in the source system is company, for example, the business partner
category is organization.
Virtual Tables
● LFB1_TEXT: To store keys for accounting texts

● LFB1_TEXT_DATA: To store accounting text lines
● LFM1_TEXT: To store keys for purchasing texts
● LFM1_TEXT_DATA: To store purchasing text lines
● TAXNUMBER: To store tax number information
● ADRC_V: To store the contact person's address information
● ADR2_V: To store the contact person's telephone numbers
● ADR3_V: To store the contact person's fax numbers

● ADR4_V: To store the contact person's teletex numbers
● ADR5_V: To store the contact person's telex numbers
● ADR6_V: To store the contact person's e-mail addresses
● ADR7_V: To store the contact person's remote mail addresses
● ADR8_V: To store the contact person's X.400 addresses
● ADR9_V: To store the contact person's RFC destinations
● ADR10_V: To store the contact person's printer addresses
● ADR11_V: To store the contact person's SSF addresses
● ADR12_V: To store the contact person's FTP and URL addresses
● ADR13_V: To store the contact person's pager addresses
● ADRT_V: To store the contact person's communication data texts
● ADRU_V: To store the contact person's communication usages
● ADRCT_V: To store the contact person's address texts
● KNVK_TEXT: To store the contact person's keys for long texts
● KNVK_TEXT_DATA: To store the contact person's text lines
● LFA1_TEXT: To store keys for head office texts
● LFA1_TEXT_DATA: To store head office text lines
● LFZA_HDR: To store general information for permitted alternative payees
If the customer and the vendor refer to Customer and Customer Number (MAP_KUNNR) and
system Vendor Vendor Number (MAP_LIFNR) respec
tively
If the vendor is not related to the cus Vendor Vendor Number (MAP_LIFNR)
tomer in the source system
If the vendor account group is assigned Vendor Vendor Number (MAP_LIFNR)

to an external number range
If the vendor account group is assigned Vendor (Enter a blank.) Vendor Number (MAP_LIFNR)
to an internal number range
Post-Processing
Not relevant.

Further Information
1.218 CRM - Activities
Purpose
This migration object enables you to migrate CRM activity data from the source CRM system to the target SAP
S/4CM system based on the default selection criteria set for the migration object. This migration technique
transfers data to the target system using Business Application Programming Interfaces (BAPI).
Related Business Object: Activity
Business Object Component/Area CRM-BTX-ACT
Business Object Definition A transaction used to record information resulting from in
teraction between business partners during the customer
relationship life cycle.
Activities are subdivided into business activities and tasks.
They include:
● Telephone calls
● Customer visits
● Preparatory tasks
● Private reminders
Available Scenarios
Selection Criteria

This migration object derives activities from the sales organizations you specified when defining the migration
scope. This migration object automatically selects the activities from the CRMD_ORDERADM_H table for the
derived activities.
In Scope
● Activity header details

● Status
● Partner mapping
● Address
● Dates
● Organizational data
● Activity text/notes
● Transaction history
● Reference objects
● Change history
● Subject profile
Out of Scope
● Activities with item data

● Questionnaire/survey
● Attachments
Prerequisites
Activity number ranges
Source System
Not relevant
Target System

CRM_ACT: (Authorization Object CRM Order - Business Object Activity)
Name of this migration object: CRM_S4_ACTIVITY
CRM_S4_BTX_ACTIVITY_MIGRATION: Migration of Activities from CRM 7.0 to S4 CM
Virtual Tables
• BUT000_AS: To store BP: General data
• ADR2_AS: To store telephone numbers for Business Address services
• ADR3_AS: To store fax numbers for Business Address services
• ADR4_AS: To store teletex numbers for Business Address services
• ADR5_AS: To store telex numbers for Business Address services
• ADR6_AS: To store e-mail addresses for Business Address services
• ADR7_AS: To store remote mail addresses
• ADR8_AS: To store X.400 numbers for Business Address services
• ADR9_AS: To store RFC destinations for Business Address services
• ADR10_AS: To store printer for Business Address services
• ADR11_AS: To store SSF for Business Address services
• ADR12_AS: To store FTP and URL for Business Address services
• ADR13_AS: To store pager for Business Address services
• ADRT_AS: To store communication data text
• ADRU_AS: To store communication usages
• ADRCT_AS: To store address texts for Business Address services
• BINREL_AS: To store dynamic table for document flow & reference objects
• REFOBJECTS_AS: To store reference object details
• ACTIVITY_TEXT: To store activity texts.

Post-Processing
Not relevant
Create CRMD_ORDER
Change CRMD_ORDER
Display CRMD_ORDER
Further Information
1.219 Warehouse fixed bin assignments
Purpose
This migration object enables you to migrate warehouse fixed bin assignment data from the source EWM
system to the target SAP S/4HANA system, based on the default selection criteria set for the migration object.
This migration technique posts data to the target system using a function module.
Related Business Object: Warehouse Fixed Bin Assignment
Business Object Component/Area Component: SCM-EWM

Business Object Definition In a warehouse, products can be assigned to specific storage
bins.
These storage bins must have the fixed bin storage type as
signed to them. The relationship between product and fixed
storage bin is called fixed bin assignment. During the goods
receipt process, the products are put away in only the as
signed storage bins. During the goods issue process, the
products are picked from only those storage bins.
Available Scenarios
Migration from SAP EWM to Decentralized EWM based on SAP S/4HANA
 Note
The use of this scenario isn't supported for migration to Extended Warehouse Management embedded in
SAP S/4HANA.
Selection Criteria
Fixed bin assignment data is automatically selected for the fixed bin assignments assigned to the migration-
relevant warehouse number.
 Note
It is only possible to migrate data for one warehouse number in a single migration project.
In Scope
● Key fields
● Maximum and minimum quantities
● Display UoM
Out of Scope
Not relevant

Prerequisites
For a consistent migration, you've ensured that all relevant Customizing for the migration object is available in
● Material
● Warehouse storage bin
Source System
● /SCWM/MIG (EWM Migration Reports)

● /SCWM/LG (EWM Storage Bin)
Name of this migration object: S4_EWM_FIXED_BIN_ASN
Name of the function module used in this migration object:
/SCWM/MC_FIXBIN_ASN (FM for Migration of Fixed Bin Assignments)
Virtual Tables
MATMAP: This table is used to map the material ID and material number to the corresponding external material
numbers.
Post-Processing
Not relevant

With the transaction codes shown below, you can display your migrated data to verify that all of the attributes
are present.

Assign Fixed Storage Bins /SCWM/BINMAT
Warehouse Monitor /SCWM/MON
Node: Stock and Bin Storage Bin Fixed Bin
Assignment
1.220 Warehouse storage bin
Purpose
This migration object enables you to migrate warehouse storage bins from the source EWM system to the
target SAP S/4HANA system, based on the default selection criteria set for the migration object. This
migration technique posts data to the target system using a function module.
Related Business Object: Warehouse Storage Bin
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.
Available Scenarios
 Note
SAP S/4HANA.
Selection Criteria

Storage bin data is automatically selected for the storage bins assigned to the migration-relevant warehouse
number.
 Note
In Scope
● General storage bin data, such as aisle, stack, level, and coordinates
● Status data, such as putaway and stock removal block
● Data related to physical inventory, such as physical inventory type and date of last inventory
● Statistics-related data, such as date and time of last movement or date and time of last bin clearing
Out of Scope
● Maximum number of handling units on bin

● Actual number of handling units on bin
The migration of warehouse stock creates all of the above.
Prerequisites
Before you can start the migration process, for example, ensure that the following Customizing is available in
the target system:
● Warehouse number
● Storage types
● Storage section
● Storage bin types
● Bin access types
Source System

● /SCWM/LG (EWM Storage Bin)
● C_LIME_DOC (LIME Document Check)
● C_LIME_LOC (LIME Location)
● C_LIME_HU (LIME Handling Unit)
Name of this migration object: S4_EWM_STORAGE_BIN
/SCWM/MC_BIN (FM for Migration of Storage Bin)
Post-Processing
Not relevant
are present.
Display Storage Bins /SCWM/LS03
Node: Stock and Bin Storage Bin
1.221 Warehouse product

Purpose
This migration object enables you to migrate warehouse product data from the source EWM system to the
Related Business Object: Warehouse Product
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.
Available Scenarios
 Note
SAP S/4HANA.
Selection Criteria
Warehouse product data is automatically selected for the warehouse products assigned to the migration-
 Note
In Scope
The following data is set for migration to Decentralized EWM based on SAP S/4HANA:
● General warehouse product data, such as required minimum shelf life and preferred unit of measure
● Putaway-related data, such as putaway control and bulk storage
● Stock removal-related data, such as stock removal control
● Slotting-related data
● Storage typespecific data

Out of Scope
● Not relevant
Prerequisites
the target system:
● Storage type, if the warehouse products to be migrated have storage typespecific data
● Material
 Note
Materials must be transferred from your enterprise management system, for example, SAP S/4HANA or
SAP ERP, to the target decentralized EWM system via IDoc.
Source System

● C_APO_PROD (APO Authorization Object: Master Data, Products)
Name of this migration object: S4_EWM_WAREHOUSE_PRODUCT
/SCWM/MC_PRODUCT (FM for Migration of Warehouse Product)

Post-Processing
Not relevant

are present.
Display/Change/Create Warehouse Product /SCWM/MAT1
Node: Product Master Data Warehouse Attribute
1.222 Warehouse storage bin sorting
Purpose
This migration object enables you to migrate warehouse storage bin sorting data from the source EWM system
to the target SAP S/4HANA system, based on the default selection criteria set for the migration object. This
Related Business Object: Warehouse Storage Bin Sorting

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.
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.
Available Scenarios
 Note
The use of this scenario isn’t supported for migration to Extended Warehouse Management embedded in
SAP S/4HANA.
Selection Criteria
Storage bin sorting data is automatically selected for the storage bins assigned to the migration-relevant
warehouse number.
 Note
In Scope
● Storage bin sorting data, including activity area, activity, and sort sequence
Out of Scope
● Not relevant
Prerequisites
For a consistent migration, you’ve ensured that all relevant Customizing for the migration object is available in
the target system:

● Storage types
● Activity areas
● Activities
● Consolidation groups
● Warehouse storage bins
Source System

● /SCWM/ACTI (EWM Activity Area)
Name of this migration object: S4_EWM_STORAGE_BIN_SORTING
/SCWM/MC_BIN_SRT (FM for Migration of Bin Sortation)
Post-Processing
Not relevant

are present.
Node: Stock and Bin Storage Bin Sorting

1.223 Warehouse stock
Purpose
This migration object enables you to migrate warehouse stock data from the source EWM system to the target
SAP S/4HANA system, based on the default selection criteria set for the migration object. This migration
technique posts data to the target system using a function module.
Related Business Object: Warehouse Stock
Business Object Definition Warehouse stock represents goods that are stored physi
cally in a warehouse. Warehouse stock is an entity that de
scribes the goods with information such as the name of the
product, the quantity, batch information, packaging informa
tion, and storage bin.
Available Scenarios
 Note
SAP S/4HANA.
Selection Criteria
Stock data is automatically selected for the storage bins assigned to the migration-relevant warehouse
number.
 Note
In Scope
The following data is set for migration to Decentralized EWM based on SAP S/4HANA:
● The following stock types:

○ Unrestricted use stock
○ Blocked Stock
○ Stock in Production
○ Scrap Stock
● The following special stock indicators:
○ On Order Stock / Sales order stock - "E"
○ Project Stock - "Q"
○ Vendor Consignment Stock - "K"
● Stock for batch-managed materials
● Stock with serial numbers
● The serial numbers themselves for serialization in inventory management and on warehouse level
 Note
The system uses the fixed value 'BP' for the partner role of Party Entitled to Dispose.
Out of Scope
● Stock isn't posted to an enterprise management system, for example, SAP S/4HANA or SAP ERP.
If you don't have a live enterprise management system that already has the correct inventory balances for
the storage locations of your EWM system, you can use the transaction /SCWM/ERP_STOCKCHECK.
● Delta migration isn't supported. Functionality is restricted to an initial upload of the data.
● Migration of negative stock
● Migration of alternative handling unit identification numbers (corresponding database table: /SCWM/
HU_IDENT)
● Migration of individual status for handling units (corresponding database table: /SCWM/HUSSTAT)
● Stock that is involved in any of the following open processes or documents:
○ Stock with reference to a delivery
○ Stock in quality inspection
○ Stock or stock on bins with an open physical inventory document
○ There should be no open stock in the difference analyzer (transaction /SCWM/DIFF_ANALYZER)
○ Stock on resources or transportation units
 Note
If stock isn't ready for migration for one of the above reasons, stock for the whole storage bin is skipped in
the data selection. Therefore, the stock for that storage bin isn’t visible in the selected data and can’t be
simulated or migrated. After correcting the situation that prevented migration, data selection can be
repeated within the same migration project. The new entries in the list of selected data can now be
simulated and migrated.

Prerequisites
● Material (products and packaging materials for stock in handling units (HUs))
● Batch
● Vendor
Note: Vendor is relevant for the special stocks "K" - vendor consignment, as well as for the party entitled to
dispose and owner.
● WBS element
Note: WBS elements are relevant for the special stock "Q" - project stock.
● Purchasing info record with info category 'Consignment'
Note: Purchasing info record is relevant for the special stock "K" - vendor consignment stock
● Sales order
Note: Sales order is relevant for the special stock "E" - on order stock/sales order stock
The status of the internal number range for handling units in the target system must be set equal to or greater
than the number of the handling unit in the source system that was the last handling unit to be created before
migration.
Source System

● /SCWM/SLFU (EWM Special Functions per Warehouse Number)
● C_LIME_SI (LIME Stock Item)
● M_MSEG_BWA (Goods Movements: Movement Type)
● M_MSEG_WWA (Goods Movements: Plant)
Name of this migration object: S4_EWM_WAREHOUSE_STOCK
/SCWM/MC_STOCK (FM for Migration of Storage Bin)
Virtual Tables

STOCK_DATA : This table is used to select data for stock based on the storage bins assigned to the migration-
relevant warehouse numbers.
Post-Processing
Not relevant

are present.
Node: Stock and Bin Storage Bin Physical Stock
Node: Stock and Bin Serial Number On Whse Level
1.224 Warehouse application log settings
Purpose
This migration object enables you to migrate warehouse application log settings from the source EWM system

Business Object Definition Application log settings allow the user to activate or deacti
vate logs for EWM applications. The user can also control ad
ditional parameters. For example, the user can specify when
the system is to write an application log based on the se
verity of the messages that occur.
Available Scenarios
 Note
SAP S/4HANA.
Selection Criteria
Warehouse application log settings are automatically selected from the source system using the migration-
relevant warehouse number as a filter.
 Note
In Scope
Settings from the following transactions are set for migration to SAP S/4HANA:
● Activate Application Log

● Deactivate PPF Log Depending on Warehouse and User
Out of Scope
Settings from the following transactions are out of scope:
● Configure Log for ERP Messages

● Activate Trace in BRFplus
Prerequisites
the target system:

● Warehouse numbers
● Users
Source System
● S_TABU_DIS (Table Maintenance, using standard tools such as SM30)

● S_TABU_LIN (Authorization for Organizational Unit)
● S_TABU_NAM (Table Access by Generic Standard Tools)
Name of this migration object: S4_EWM_LOG_SETTINGS
/SCWM/MC_LOG_SETTINGS (FM for migration of Warehouse Log Settings)
Post-Processing
Not relevant.
are present.
Activate Application Log /SCWM/ACTLOG
Deactivate PPF Log Depending on Warehouse and User /SCWM/DLVPPFLOG

1.225 Physical inventory settings
Purpose
This migration object enables you to migrate physical inventory settings from the source EWM system to the
Business Object Definition Physical inventory is the recording of actual stock levels
(quantities) of materials by counting, weighing, or measur
ing at a given storage location at a specific time.
Physical inventory settings allow you to assign so-called tol

erance groups to users.
Available Scenarios
 Note
SAP S/4HANA.
Selection Criteria
Physical inventory settings are automatically selected from the source system using the migration-relevant
warehouse number as a filter.
 Note
In Scope
● Assign User to Tolerance Group for Difference Analyzer

● Assign User to Tolerance Group for Recount/Clearing

Out of Scope
Not relevant.
Prerequisites
the target system:
● Tolerance groups
● Activity areas
● Users
Source System

● /SCWM/VM (EWM Warehouse Specific View Maintenance)
● /SCWM/SLFU (EWM Special Functions per Warehouse Number)
Name of this migration object: S4_EWM_PI_SETTINGS
/SCWM/MC_PI_SETTINGS (FM for migration of Physical Inventory settings)
Post-Processing
Not relevant.

are present.
Assign User to Tolerance Group for Difference Analyzer /SCWM/PI_USER_DIFF
Assign User to Tolerance Group for Recount/Clearing /SCWM/PI_USER
1.226 Shipping and receiving settings
Purpose
This migration object enables you to migrate shipping and receiving settings from the source EWM system to
the target SAP S/4HANA system, based on the default selection criteria set for the migration object. This
Business Object Definition Shipping and Receiving in Extended Warehouse Manage

ment (EWM) comprises the following areas:
● Usage of vehicle and transportation units for managing

the transports to or from your warehouse
● Loading and unloading, including docking at and un
docking from a door
● Yard Management
To control these processes, the appropriate settings are
used.
Available Scenarios
 Note
SAP S/4HANA.

Selection Criteria
Shipping and receiving settings are automatically selected from the source system using the migration-
 Note
In Scope
● Assign Door Storage Bin and Supply Chain Unit

● Invoice Before Goods Issue
● Staging Area and Door Determination (Inbound)
● Staging Area and Door Determination (Outbound)
● Access Sequence to Staging Areas and Door Determination
● Determine TU Profile
Out of Scope
● Set Default Owner of Transportation Units and Vehicles

● Process Vehicle
● Process Transportation Unit
● Link Between Packaging Material (TU) and Means of Transport
● Set Up Printer and Form Determination
Prerequisites
the target system:
● Storage bins
● Supply chain unit
● Means of transport
● Packing materials

● Staging area groups
● Staging areas
● Staging bay and doors
● TU profiles
● Routes
● Users

● Warehouse product
Source System

Name of this migration object: S4_EWM_SR_SETTINGS
/SCWM/MC_SR_SETTINGS (FM for migration of Shipping&Receiving settings)
Post-Processing
Not relevant.

are present.

Assign Door Storage Bin and Supply Chain Unit /SCWM/DOOR_SCU
Invoice Before Goods Issue /SCWM/IBGI
Staging Area and Door Determination (Inbound) /SCWM/STADET_IN
Staging Area and Door Determination (Outbound) /SCWM/STADET_OUT
Access Sequence to Staging Areas and Door Determination /SCWM/STADET_ASS
Determine TU Profile /SCWM/TUPROF_DET
1.227 Production supply area
Purpose
This migration object enables you to migrate production supply areas from the source EWM system to the
Business Object Definition The production supply area (PSA) exists directly in the pro
duction area. You stage the material in the production supply
area in production storage bins so it can be removed directly
for production. The production supply area groups together
work centers near the production storage bins, taking the
material staging type into consideration.
Available Scenarios
 Note
SAP S/4HANA.
Selection Criteria

Production supply area data is automatically selected for the production supply area assigned to the migration-
 Note
In Scope
● General production supply area data

● PSA assignment to bin by entitled/product
Out of Scope
Not relevant.
Prerequisites
the target system:
● Parties entitled to dispose
● Product groups
● Process types
 Note
For this migration object, you must also ensure that products are already available in the target system.
Source System


● S_SCD0_OBJ (Change Documents of Change Document Object)
Name of this migration object: S4_EWM_PSA
/SCWM/MC_PSA (FM for migration of Product Supply Area Settings)
Virtual Tables
numbers.
Post-Processing
Not relevant.

are present.
Define PSA /SCWM/PSA
Assign Bin to PSA/Product/Entitled in Warehouse Number /SCWM/PSASTAGE
Assign Bin to Product/Entitled in PSA /SCWM/PSASTAGE2
1.228 Resource and user maintenance

Purpose
This migration object enables you to migrate resources and user settings for radio frequency (RF) from the
source EWM system to the target SAP S/4HANA system, based on the default selection criteria set for the
migration object. This migration technique posts data to the target system using a function module.
Business Object Definition A resource is an entity representing a user or equipment,

which can execute work in the warehouse. Resource master
data records contain the basic information required to man
age a resource. User RF data records contain information
about resources that can execute work via RF transactions.
Available Scenarios
 Note
SAP S/4HANA.
Selection Criteria
Data for resource and user settings for RF is automatically selected for the resources assigned to the
migration-relevant warehouse number.
 Note
In Scope
● General resource data such as resource type and group, default presentation device, and queue
● User RF settings such as data entry type, personalization profile, and automatic logon
● Standard and current storage bin of a resource
● Resource print behavior
Out of Scope
● Exception and process codes of a resource

● MFS settings of a resource
● REC settings
● Actual coordinates
Prerequisites
the target system:
● Resource groups
● Resource types
● Presentation devices
● Queues
● Users
● Personalization profiles
 Note
Presentation devices must be created beforehand in the target system.

● Resource group and queue settings
Source System

● C_LIME_DOC (LIME Document Check)
● C_LIME_LOC (LIME Location)
● /SCWM/RSRC (EWM Resource Maintenance)

Name of this migration object: S4_EWM_RESOURCE
/SCWM/MC_RESOURCE (FM for migration of Resource & User Maintenance)
Post-Processing
Not relevant.

are present.
Maintain Resource /SCWM/RSRC
Maintain Users /SCWM/USER
1.229 Resource group and queue settings
Purpose
This migration object enables you to migrate resource group and queue sequence settings from the source
EWM system to the target SAP S/4HANA system, based on the default selection criteria set for the migration
object. This migration technique posts data to the target system using a function module.

Business Object Definition A resource group is a grouping of resources for queue as
signment purposes. The master data for a resource group in
cludes basic information about the resource group, about
the queue sequences, and about the queue type sequences.
Available Scenarios
 Note
SAP S/4HANA.
Selection Criteria
Data for the resource group and queue settings is automatically selected for the resource groups assigned to
the migration-relevant warehouse number.
 Note
In Scope
● General resource group data such as resource group and descriptions

● Queue sequence for each resource group
● Queue sequence in task interleaving for each resource group
Out of Scope
Not relevant.
Prerequisites
the target system:

● Queues
● Queue types
 Note
Presentation devices must be created beforehand in the target system.
Source System

Name of this migration object: S4_EWM_RESOURCE_GROUP
/SCWM/MC_RESOURCE_GROUP (FM for migration of Resource Group and Queue Settings)
Post-Processing
Not relevant.

are present.
Maintain Resource Group /SCWM/RGRP
Maintain Queue Sequence for Resource Group /SCWM/QSEQ
Maintain Queue Type Sequence /SCWM/QTSQ

1.230 Resource execution settings
Purpose
This migration object enables you to migrate resources execution settings from the source EWM system to the
Business Object Definition Resource execution settings allow you to activate or deacti
vate resource execution controls and messages to resour
ces, and to change the execution priority for a warehouse or
der. Warehouse order prioritization ensures that the system
selects the warehouse order that is most suitable for a re
source.
Available Scenarios
 Note
SAP S/4HANA.
Selection Criteria
Data for resource execution settings is automatically selected from the source system using the migration-
 Note
In Scope
● Maintain Execution Priorities

● Deactivate Messages to Resources

● Activate Resource Execution Control for Storage Groups
Out of Scope
Not relevant.
Prerequisites
the target system:
● Storage types
● Storage groups for resource execution control (REC)
● Process types
● Process categories
● Activities
● Document and item types for internal warehouse processes
● Resource types
● Bin access types
● Handling unit type groups
Source System

Name of this migration object: S4_EWM_RESOURCE_SETT
/SCWM/MC_RESOURCE_SETT (FM for migration of Resource Execution Settings)

Post-Processing
Not relevant.
are present.
Maintain Execution Priorities /SCWM/EXECPR
Activate Resource Execution Control for Storage Groups /SCWM/REC_ACTIVATE
Deactivate Messages to Resources /SCWM/RSCMSG_DEACT
1.231 Work center determinations
Purpose
This migration object enables you to migrate work center determination settings from the source EWM system
Business Object Definition Work center determination settings allow the system to de
termine which work center to use in goods issue processing
and for cross-docking.
Available Scenarios

 Note
SAP S/4HANA.
Selection Criteria
Work center determination data is automatically selected from the source system using the migration-relevant
 Note
In Scope
● Determine Work Center in Goods Issue

● Determine Work Center for Cross-Docking
Out of Scope
Not relevant.
Prerequisites
the target system:
● Routes
● Activity areas
● Consolidation groups
● Storage types
● Storage section
● Handling unit type groups

Source System

Name of this migration object: S4_EWM_WORKST_DET
/SCWM/MC_WORKST_DET (FM for migration of Work Center Determinations)
Post-Processing
Not relevant.
are present.
Determine Work Center in Goods Issue /SCWM/PACKSTDT
Determine Work Center for Cross-Docking /SCWM/CDSTDET
1.232 Work center dependent settings

Purpose
This migration object enables you to migrate work center dependent settings from the source EWM system to
the target SAP S/4HANA system, based on the default selection criteria set for the migration object. This
Business Object Definition The work center is a physical unit in the warehouse, in which
you can perform warehouse activities such as packing, dis
tribution, or weighing.
Available Scenarios
 Note
SAP S/4HANA.
Selection Criteria
Data for work center dependent settings is automatically selected for the work centers assigned to the
migration-relevant warehouse number.
 Note
In Scope
● Define Master Data Attributes, which includes work center assignment to a storage bin, default packaging
material, terminal, and weight tolerance
● Printer Control
Out of Scope
The following settings are out of scope:
● External storage process step

● Work center layout

● Inbound/outbound sections
● Return storage type, section, and process type
● Print determination procedure
Prerequisites
the target system:
● Scales
● Output devices
 Note
Source System

Name of this migration object: S4_EWM_WORKSTATION
/SCWM/MC_WORKSTATION (FM for migration of Work Center Dependent Settings)
Virtual Tables
numbers.

Post-Processing
Not relevant.
are present.
Define Master Data Attributes /SCWM/TWORKST
Printer Control /SCWM/TWCPRINT
1.233 Material flow system
Purpose
This migration object enables you to migrate material flow system settings from the source EWM system to the
technique posts data to the target system using a function module.
Business Object Definition The material flow system (MFS) is used to control and moni
tor conveyor systems and resources. It enables you to con
nect up an automatic warehouse to Extended Warehouse
Management (EWM) without the need for an additional
warehouse control unit.
Available Scenarios

 Note
SAP S/4HANA.
Selection Criteria
Material flow system (MFS) data is automatically selected from the source system using the migration-relevant
 Note
In Scope
● Maintain Application Server Group for MFS Processes

● Maintain Programmable Logic Controller
● Maintain Communication Channel
● Maintain Communication Points
● Map EWM Objects to PLC Objects
● Maintain MFS Resource
● Define Aisles and Levels for MFS Resources
Out of Scope
● Generate PLC Objects from EWM Objects

● Generate Application Data
Prerequisites
Before you can start the migration process, for example, ensure the following Customizing is available in the
target system:
● RFC destinations
● Programmable logic controllers

● Communication points
● Communication channels
● Resources
● Queues
● Storage types
● Function modules for MFS actions
● Server groups
● Users
 Note

● Resource and user maintenance
● Resource group and queue settings
Source System

● /SCWM/RSTY (EWM Resource Type)
Name of this migration object: S4_EWM_MFS
/SCWM/MC_MFS (FM for migration of Material Flow System Settings)
Post-Processing
Not relevant.

are present.
Maintain Application Server Group for MFS Processes /SCWM/MFS_APPSRV
Maintain Programmable Logic Controller /SCWM/MFS_PLC
Maintain Communication Channel /SCWM/MFS_CCH
Maintain Communication Points /SCWM/MFS_CP
Map EWM Objects to PLC Objects /SCWM/MFS_OBJMAP
Maintain MFS Resource /SCWM/MFS_RSRC
Define Aisles and Levels for MFS Resources /SCWM/MFS_RSRC_AISLE
1.234 Route
Purpose
This migration object enables you to migrate routes from the source EWM system to the target SAP S/4HANA
system based on the default selection criteria set for the migration object. This migration technique posts data
to the target system using a class for the processing of BAPI data for routes.
Business Object Definition A route is a sequence of legs that are connected by trans
shipment locations. The route represents a framework or
corridor that comprises a multitude of trips, in other words,
possible concrete itineraries. The system uses routes to de
termine trips in route determination.
Available Scenarios

 Note
SAP S/4HANA.
Selection Criteria
Route data is automatically selected for all the routes that don’t have the deletion flag set.
 Note
In Scope
● Header data
● Legs
● Stops
● Carrier assignment, if there are carrier profiles in the target system that are already assigned to this route
according to the legacy system data
● Assignment to departure calendar
● Route validity and validity restrictions
● Cross-docking (CD) location, inbound and outbound routes if CD route
Out of Scope
● Routes that have the deletion flag set
Prerequisites
the target system:
● Request types
● Shipping conditions
● Transportation groups

● Carrier profile
● Zone
Source System
● /SCTM/RG (Master Data Maintenance in Routing Guide (General))

● /SCMB/SFUN (Special Functions SCM Basis)
● /SCTM/CD (Authorizations for Maintaining Cross-Docking Routes)
● /SCTM/SCU (Supply chain units in routes)
● /SCWM/SFUN (EWM Special Functions)
● C_APO_LOC (APO Authorization Object: Master Data, Locations)
● C_MD_SCU (Authorization Object: Supply Chain Unit)
Name of this migration object: S4_EWM_ROUTE
Name of the class used in this migration object:
/SCTM/CL_BAPI_ROUTE (Route: Processing of BAPI Data)
/SCWM/MC_ROUTE (Business API for migration Routes)
Post-Processing
Not relevant.

Maintain Route /SCTM/ROUTE

Further Information
1.235 Carrier profile
Purpose
This migration object enables you to migrate carrier profile from the source EWM system to the target SAP S/
transfers data to the target system using an adapter module for transportation service provider profiles.
Business Object Definition A carrier profile contains data for the carrier (business part
ner with the role Carrier). The system considers the carrier
profile data when determining routes in the routing guide.
Only one profile can exist for each carrier.
Available Scenarios
 Note
SAP S/4HANA.
Selection Criteria
All carrier profiles are automatically selected.
In Scope
● Header data
● Geographical data and means of transport, if there are routes in the target system that are already
assigned to this carrier profile according to the legacy system data

● Transportation groups and product freight groups
● Freight code sets
● Transportation costs
Out of Scope
Not relevant.
Prerequisites
Source System

Name of this migration object: S4_EWM_TSP
Names of the function modules used in this migration object:
/SCWM/MC_TSP (Business API for migration Carrier Profile)
/SCTM/AD_W_TSP_PROFILE (Adapter/Write: Transportation Service Provider Profiles)
Post-Processing
Not relevant.

Maintain Carrier Profile /SCWM/TSPP
Further Information
1.236 Zone
Purpose
This migration object enables you to migrate transportation zone data from the source EWM system to the
technique transfers data to the target system using a Business Application Programming Interface (BAPI) for
creating transportation zones.
Business Object Definition A transportation zone groups together several locations. The
system can partly transfer the properties that you assign to
a transportation zone to all its locations. This function re
duces the volume of master data stored in the system.
Available Scenarios
 Note
SAP S/4HANA.

Selection Criteria
Transportation zone data is automatically selected for the following types of zones:
● Direct zone
● Postal code zone
● Region zone
● Mixed zone
In Scope
● General zone data

● Assigned locations that have the exclude flag set if direct zone or mixed zone
● Ranges of postal codes by country if postal code zone or mixed zone
● Regions in countries if region zone or mixed zone
Out of Scope
● Transportation zones with the zone type leg zone

● Transportation zones that have the deletion flag set
Prerequisites
For this migration object, you must also ensure that all relevant locations are already available in the target
system.
Source System

● /SCTM/SCU (Supply chain units in routes)
● C_APO_LOC (APO Authorization Object: Master Data, Locations)

● C_MD_SCU (Authorization Object: Supply Chain Unit)
Name of this migration object: S4_EWM_ZONE
/SCTM/BAPI_ZONE_SAVEMULTI (BAPI FM for creating and changing Transportation Zones)
/SCWM/MC_ZONE (Business API for migration Zones)
Post-Processing
Not relevant.
Maintain Zone /SCWM/ZONE
Further Information
1.237 Zones hierarchy

Purpose
This migration object enables you to migrate transportation zone hierarchy data from the source EWM system
migration technique transfers data to the target system using a Business Application Programming Interface
(BAPI) for changing transportation zones.
Business Object Definition The transportation zone hierarchy is used to structure trans
portation zones hierarchically by assigning one transporta
tion zone to another. All locations included in a zone that is
assigned to another zone are automatically also part of that
other zone.
Transportation zones that are included in a transportation

zone hierarchy inherit the properties of the superordinate
zone.
Available Scenarios
 Note
SAP S/4HANA.
Selection Criteria
Transportation zone hierarchy data is automatically selected for the RELH_ZONE zone hierarchy.
In Scope
● Transportation zone hierarchy RELH_ZONE
Out of Scope
● Any other transportation zone hierarchies

Prerequisites
● Zone
Source System
C_APO_RELH (APO Authorization Object for Hierarchies (Master Data))
Name of this migration object: S4_EWM_ZONE_HIERARCHY
/SCTM/BAPI_ZONE_SAVEMULTI (BAPI FM for creating and changing Transportation Zones)
/SCWM/MC_ZONES_HIERARCHY (Business API for migration Zones Hierarchy)
Post-Processing
Not relevant.
Hierarchy Maintenance /SAPAPO/RELHSHOW

Further Information
1.238 Condition records (warehouse independent)
Purpose
This migration object enables you to migrate warehouse-independent condition records (applications: DPP,
PAK) from the source EWM system to the target SAP S/4HANA system based on the default selection criteria
set for the migration object.
Business Object Definition Condition records are data records with input and output
values for a task. The output values are dependent on
chosen input values (for example, customer, customer
group, product) and are valued for a certain time period. For
example, there are condition records in Extended Warehouse
Management (EWM) that allow you to control how the sys
tem schedules Post Processing Framework actions (PPF ac
tions) for delivery processing.
A packaging specification is a document containing informa

tion on how to package a material for storage or pack a ma
terial for shipping. It contains material quantities, combina
tions of materials, and packaging work steps.
Available Scenarios
 Note
SAP S/4HANA.
Selection Criteria
Condition records are automatically selected from the source system.

 Note
This migration object is for warehouse-independent settings. Unlike the other migration objects in the
SCM-EWM component, no warehouse number is required.
Warehouse-independent condition records can be migrated at the same time as one set of warehouse-
dependent conditions records.
In Scope
The following applications as condition techniques are set for migration to SAP S/4HANA:
● DPP (EWM - Scheduling PPF Actions of the Delivery), with usage DP

● PAK (Pack. Specification)
Out of Scope
All applications and usages that are not listed as being in scope.
Prerequisites
For a consistent migration, you have ensured that all relevant customizing for the migration object is available
the target system:
● Staging areas
● TU profiles
● Routes
● Application names
● Output devices
● Users
It is important to check the existence of tables for custom condition types in the target system, as well as to
compare the table structures in the source and target systems. They should be identical.

● Production supply area

● Route
● Work center dependent settings
 Note
This is the complete list of relevant migration objects. The actual number of predecessors depends on
which condition types are selected for migration.
Source System
● /SAPCND/CM (Condition Technique: Condition Maintenance (Generic Part))

Name of this migration object: S4_EWM_COND_REC
/SCWM/MC_COND_REC (FM for migration of Condition Records (warehouse independent))
This migration technique posts data to the target system using the standard function module for condition
tables (/SAPCND/DBA_UPDATE_FROM_FWS_DB).
Post-Processing
Not relevant.
are present.

Activity Transaction Code Application
Maintain Condition Records for PPF /SCWM/DLVPPFC DPP (usage DP)

Schedule Conditions
Condition Maintenance /SCWM/PSCT6 PAK
1.239 Condition records (warehouse dependent)
Purpose
This migration object enables you to migrate warehouse-dependent condition records (applications: CON,
DPP, PHU, PPI, PWO, TWP, WME) from the source EWM system to the target SAP S/4HANA system based on
the default selection criteria set for the migration object.
Business Object Definition Condition records are data records with input and output
values for a task. The output values are dependent on
chosen input values (for example, customer, customer
group, product) and are valued for a certain time period. For
example, there are condition records in Extended Warehouse
Management (EWM) that allow you to control how the sys
tem schedules Post Processing Framework actions (PPF ac
tions) for delivery processing.
Available Scenarios
 Note
SAP S/4HANA.
Selection Criteria
Condition records are automatically selected from the source system using migration-relevant warehouse
numbers as a filter.

 Note
Warehouse-dependent condition records can only be migrated for one warehouse at a time.
In Scope
The following applications as condition techniques are set for migration to SAP S/4HANA:
● CON (Slotting)
● DPP (EWM - Scheduling PPF Actions of the Delivery), with usage DP
● PHU (EWM - Print Handling Unit)
● PPI (EWM - PI: Find Printer)
● PWO (EWM - Print Warehouse Order)
● TWP (EWM - Transit Warehousing Putaway)
● WME (Wave Template Determination)
Out of Scope
All applications and usages that are not listed as being in scope.
Prerequisites
For a consistent migration, you have ensured that all relevant customizing for the migration object is available
the target system:
● Staging areas
● TU profiles
● Routes
● Application names
● Output devices
● Users
It is important to check the existence of tables for custom condition types in the target system, as well as to
compare the table structures in the source and target systems. They should be identical.

● Production supply area

● Route
● Work center dependent settings
 Note
This is the complete list of relevant migration objects. The actual number of predecessors depends on
which condition types are selected for migration.
Source System
● /SAPCND/CM (Condition Technique: Condition Maintenance (Generic Part))

Name of this migration object: S4_EWM_COND_REC_WH
/SCWM/MC_COND_REC_WH (FM for migration of Condition Records (warehouse dependent))
This migration technique posts data to the target system using the standard function module for condition
tables (/SAPCND/DBA_UPDATE_FROM_FWS_DB).
Post-Processing
Not relevant.
are present.

Activity Transaction Code Application
Maintain Condition Records for PPF /SCWM/DLVPPFC DPP

Schedule Conditions
Condition Maintenance for Slotting /SCWM/GCMC CON
Create Condition Records for Printing /SCWM/PRHU6 PHU

(HUs)
Create Condition Records for Printing /SCWM/PRPI_GCM PPI

(Physical Inventory)
Create Condition Records for Printing /SCWM/PRWO6 PWO

(Warehouse Orders)
Maintain Condition Records for Bin De /SCWM/PUT_TW_WT_GC TWP

termination
Maintain Conditions for Determining /SCWM/WDGCM WME

Wave Templates
1.240 FI - Accounts payable open item (tax line) (Customer-

specific)
(Deprecated)
Purpose
Accounts Payable
Component: FI

cleared.
Available Scenarios
Selection Criteria
In Scope
● Documents containing only vendor open items, which were created in the source system.
 Note
The vendor open item lines are recorded in the BSIK table.
● Complete invoices including tax lines

● The General Ledger view from the FAGLFLEXA table
 Note
 Note
Out of Scope

● Documents containing line items with the Open Item Managed Account field (XOPVW) set to "X" in the BSIS
table. (This data is migrated using the FI - G/L open item (tax line) migration object.)

● Documents containing line items with the Open Item Managed Account field (XOPVW) set to "X" in the BSID
Prerequisites

target systems
● Tax codes, tax rates, and any tax-related Customizing match in the source and target systems
● Sales/purchase tax codes and accounts match in the source and target systems
● Customizing for withholding tax codes and accounts match in the source and target systems
● Exchange rate
● FI - G/L open item (tax line)
● Supplier
Source System
Not relevant
Target System
Not relevant
Name of this migration object: S4_FI_AP_OI_NEW_GL_V2

Virtual Tables
FLTR_TAXL: To filter tax lines
Post-Processing
Not relevant

Create FB01
Change FB02
Display FB03
Further Information
1.241 FI - Accounts receivable open item (tax line)

(Customer-specific)
Purpose
(BAPIs).

Accounts Receivable
Component: FI

items.
Available Scenarios
Selection Criteria
In Scope
● Documents with customer open items

● Documents with a mix of customer and vendor open items
 Note
Out of Scope


Prerequisites

● Sale and purchase tax codes and accounts match in the source and target systems
● Withholding tax codes and accounts match in the source and target systems
should match
target systems
● Customer
● Exchange rate
Source System
Not relevant
Target System
Not relevant
Name of this migration object: S4_FI_AR_OI_NEW_GL_V2
Virtual Tables
FLTR_TAX: To store tax line data

Post-Processing
Not relevant

Create FB01
Change FB02
Display FB03
Further Information
1.242 FI - G/L Account balance (w/o tax account) (Customer-

specific)
Purpose
Component: FI


Available Scenarios
Selection Criteria
& loss accounts

In Scope
company codes.
 Note
Out of Scope
● Tax account balances


Prerequisites
and target systems.
and target systems
Source System
Not relevant
Target System
Not relevant
Name of this migration object: S4_FI_GL_ACC_BALANCE_NEW_GL_V2
Virtual Tables

Post-Processing
Not relevant
Display FAGLB03
Further Information
1.243 FI - Ledger group specific open item (tax line)

(Customer-specific)
Purpose
This migration object enables you to migrate ledger specific data from the source ERP system to the target
Component: FI

Available Scenarios
Selection Criteria
All ledger groupspecific open items from the FAGLBSIS table are automatically selected for the company
codes that you specified when defining the migration scope.
In Scope

● Tax lines
● Header data
● Splitting data
 Note
Out of Scope
Not relevant
Prerequisites

must match
 Note
Create and activate the ACC_DOCUMENT BAdI implementation in the target system. For more information,
see SAP Note 2717381 .
● Exchange rate
● PS - Project
Source System
Not relevant
Target System
Not relevant
Name of this migration object: S4_FI_GL_OI_LED_SPEC_NEW_GL_V2
Virtual Tables
LEDGER: To retrieve the entry views for the document.

Post-Processing
Deactivate the BAdI implementation after migration and before creating any new documents in the target
system.

Create FB50L
Change FB02
Display FB03
Further Information
1.244 FI - G/L open item (tax line) (Customer-specific)
Purpose
Component: FI


Available Scenarios
Selection Criteria
In Scope
● Line items of open item managed accounts including G/L open items, customer/vendor open items, or a
combination
 Note
Out of Scope

● Postings in non-leading ledgers
Prerequisites


● Sales/purchase tax codes and accounts
should match.
● Currency keys associated to currency types assigned to different organizational units should be same in
source and target system.
● Exchange rate
● PS - Network
● PS - Project
Source System
Not relevant
Target System
Not relevant
Name of this migration object: S4_FI_GL_OI_NEW_GL_V2
Virtual Tables
FLT_TAXLN: To retrieve the tax line items in the document.

Post-Processing
Not relevant

Create FB50
Change FB02
Display FB03
Further Information
1.245 FI - Accounts payable open item (tax line) (Customer-

specific) (AFS)
Purpose
This migration object enables you to migrate material master data from the source ERP system to the target
Business Object Component/Area User Menu Path: Logistics General Material Master
Component: LO-MD-MM

Business Object Definition Material master data records contain all the basic informa
tion required to manage a material. This data is sorted ac
cording to various criteria including data of a descriptive na
ture (such as size, dimension and weight) and data with a
control function (such as material type and industry sector).
In addition, some data can be maintained directly by the
user.
Available Scenarios
Selection Criteria
This migration object automatically selects the materials from the MARC table for the derived plants.
● Item 1
● Item 2
 Note
Enter text
All G/L accounts from the SKB1 table are automatically selected for the company codes that you specified
● Item 1
● Item 2
 Note
Enter text
● Item 1
● Item 2
 Note
Enter text

In Scope
● Basic data
● Material description
● Material data at plant level
● Valuation data
● Warehouse data
● Sales data
● Unit of measurement
● Forecast values
 Note
Materials you set for deletion in the source ERP system are not migrated
Out of Scope
● Planning data
● Product resource tool (PRT) data
 Note
If you have multiple steps for migration, you can simulate only these features:
● ABC
● DEF
● TUV
● XYZ
During the migration phase, error may occur for features that were not in scope during simulation even
 Note
● Canceled
● Locked

● Obsolete
● Completed
Prerequisites
● Customizing 1
● Customizing 2
system:
● Customizing 1
● Customizing 2
● Profit center
Source System
● TECHNICAL NAME (Descriptive name)

Target System
M_MATE_WRK (Material Master Plants)


Name of this migration object: S4_MM_MATERIAL_MASTER
BAPI_MATERIAL_SAVEREPLICA Mass maintenance for Material Master Data
Virtual Tables
● TECHNICAL NAME: To
● Enter item
Post-Processing
Create MM01
Change MM02
Display MM03
Further Information

1.246 FI - Accounts receivable open item (tax line)
(Customer-specific) (AFS)
Purpose
(BAPIs).
Accounts Receivable
Component: FI

items.
Available Scenarios
Selection Criteria
In Scope
● Documents with customer open items

● Documents with a mix of customer and vendor open items

 Note
Out of Scope

Prerequisites

● Sale and purchase tax codes and accounts match in the source and target systems
should match
target systems
● Customer
● Exchange rate
Source System
Not relevant
Target System

Not relevant
Name of this migration object: S4_AFS_FI_AR_OI_NEW_GL_V2
Virtual Tables
FLTR_TAX: To store tax line data
Post-Processing
Not relevant

Create FB01
Change FB02
Display FB03
Further Information
1.247 FI - G/L account balance (w/o tax account) (Customer-

specific) (AFS)

Purpose
Component: FI

Available Scenarios
Selection Criteria
& loss accounts

In Scope
company codes.

 Note
Out of Scope
● Tax account balances

Prerequisites
and target systems.
and target systems
Source System
Not relevant
Target System
Not relevant

Name of this migration object: S4_AFS_FI_GL_ACC_BAL_NEW_GL_V2
Virtual Tables
Post-Processing
Not relevant
Display FAGLB03
Further Information
1.248 FI - Ledger group specific open item (tax line)

(Customer-specific) (AFS)

Purpose
This migration object enables you to migrate ledger specific data from the source AFS system to the target
Component: FI
Available Scenarios
Selection Criteria
All ledger groupspecific open items from the FAGLBSIS table are automatically selected for the company
codes that you specified when defining the migration scope.
In Scope

● Tax lines
● Header data
● Splitting data
 Note

Out of Scope
Not relevant
Prerequisites

must match
 Note
Create and activate the ACC_DOCUMENT BAdI implementation in the target system. For more information,
see SAP Note 2717381 .
● Exchange rate
● PS - Project
Source System
Not relevant
Target System
Not relevant

Name of this migration object: S4_AFS_FI_GL_LED_SPEC_NEW_GL_V2
Virtual Tables
LEDGER: To retrieve the entry views for the document.
Post-Processing
Deactivate the BAdI implementation after migration and before creating any new documents in the target
system.
Create FB50L
Change FB02
Display FB03
Further Information
1.249 FI - G/L open item (tax line) (Customer-specific) (AFS)

Purpose
Component: FI

Available Scenarios
Selection Criteria
In Scope
● Line items of open item managed accounts including G/L open items, customer/vendor open items, or a
combination
 Note

Out of Scope

● Postings in non-leading ledgers
Prerequisites

● Sales/purchase tax codes and accounts
should match.
● Currency keys associated to currency types assigned to different organizational units should be same in
source and target system.
● Exchange rate
● PS - Network
● PS - Project
Source System
Not relevant
Target System
Not relevant

Name of this migration object: S4_AFS_FI_GL_OI_NEW_GL_V2
Virtual Tables
FLT_TAXLN: To retrieve the tax line items in the document.
Post-Processing
Not relevant
Create FB50
Change FB02
Display FB03
Further Information
1.250 eSPP - Location

Purpose
This migration object enables you to migrate the location master data from the source APO SPP to the target
eSPP within SAP S/4HANA based on the global filter parameter set in the migration project. The supported
location types are plant, distribution center and vendor. There is a separate migration object for the location
type MRP area.
In eSPP within SAP S/4HANA the APO relevant tables for the location master data remain unchanged. The ECC
data model for vendor on the other hand is replaced by a business partner in SAP S/4HANA. The purpose of
this migration is to update the location master data tables by the location data transferred from the APO
system.
Business Object Component/Area Component: SCM-BAS-MD
Business Object Definition Place or organizational unit at which quantities of products

or resources are managed. There are the following standard
location types:
● Production plant
● Distribution center
● MRP area
● Vendor
Available Scenarios
Migration to eSPP within SAP S/4HANA.
Selection Criteria
The location types plant, distribution center and vendor are considered in the selection. Vendors are selected
indirectly by considering only vendors with a valid transportation lane to the locations selected in the global
filter.
In Scope
The following data is set for migration to eSPP within SAP S/4HANA:
● General location data

● Language dependent location descriptions
Out of Scope
● Locations with location type customer

● Locations with a simulation version
Prerequisites
● For a consistent migration, you have ensured that all relevant Customizing for the migration object is
● The SAP S/4HANA migration/conversion for plants and vendors has already been performed. The
corresponding plants and vendors already exist in the target system.
Source System
Not relevant
Target System
 Note
Name of this migration object: /SCMB/ESPP_MIG_LOCATION
Post-Processing
Not relevant

Change /SAPAPO/LOC3

Display /SAPAPO/LOC3
1.251 eSPP - Product
Purpose
This migration object enables you to migrate the product master data from the source APO SPP to the target
eSPP within SAP S/4HANA based on the global filter parameter set in the migration project.
In eSPP within SAP S/4HANA the APO product master data has been unified with the ECC material master
data. The purpose of this migration is to update the missing part of the material master data by the product
master data from the APO system.
Business Object Definition Good that is the subject of business activity. A product is
used, consumed or created during the production process.
Available Scenarios
Selection Criteria
Product master data to be migrated is automatically selected using products assigned to the migration-
relevant plant(s) and its MRP area(s).
In Scope
● General product data

● Assigned material group values
● SPP specific product data

Out of Scope
● Product master data in simulation version

● Products which are not assigned to any plants or its MRP area(s) selected in the global filter
Prerequisites
● The SAP S/4HANA migration/conversion for materials has already been performed. The corresponding
materials already exist in the target system.
● The report PRD_SCM_GUID_CONVERSION must be executed for materials with initial SCM_MATID_GUID16
and SCM_MATID_GUID22 in the table MARA.
Source System
Not relevant
Target System
 Note
Name of this migration object: /SCMB/ESPP_MIG_PRODUCT
Post-Processing
Not relevant

Change MM02
Display MM03
1.252 eSPP - MRP Area
Purpose
This migration object enables you to migrate the location master data for the location type MRP area from the
source APO SPP to the target eSPP within SAP S/4HANA based on the global filter parameter set in the
migration project.
In eSPP within SAP S/4HANA the APO relevant tables for the location master data remain unchanged. The ECC
data model for vendor on the other hand is replaced by a business partner in SAP S/4HANA. The purpose of
this migration is to update the location master data tables for location type MRP area by the data transferred
from the APO system.
Business Object Definition Place or organizational unit at which quantities of products

or resources are managed. There are the following standard
location types:
● Production plant
● Distribution center
● MRP area
● Vendor
Available Scenarios
Selection Criteria

The location type MRP area is considered in the selection.
In Scope
● General location data

● Language dependent location descriptions
Out of Scope
Locations with a simulation version.
Prerequisites
● The SAP S/4HANA migration/conversion for MRP areas has already been performed. The corresponding
MRP area already exists and assigned to a plant in the target system.
● You have migrated or defined settings in the eSPP - Location [page 762] migration object.
Source System
Not relevant
Target System
 Note
Name of this migration object: /SCMB/ESPP_MIG_LOCATION

Post-Processing
Not relevant

Change /SAPAPO/LOC3
Display /SAPAPO/LOC3
1.253 eSPP - Location Product
Purpose
This migration object enables you to migrate the location product master data from the source APO SPP to the
target eSPP within SAP S/4HANA based on the global filter parameter set in the migration project.
In eSPP within SAP S/4HANA the APO product master data has been unified with the ECC material master
data. The purpose of this migration is to update the missing part of the plant relevant material master data by
the location product master data from the APO system.
Related Business Object: Location Product
Business Object Definition A product assigned to a specific location.
Available Scenarios
Selection Criteria
Location product data to be migrated is automatically selected using migration-relevant plant(s) and its MRP
area(s).

In Scope
● General location product data

● MRP location product data
● SPP specific location product data
● Location product planner assignment data
Out of Scope
● Products which are not assigned to any of the plants selected in the global filter
● Location products for location type vendor and customer
● Location products in simulation version.
Prerequisites
● The SAP S/4HANA migration/conversion for materials has already been performed. The corresponding
plant relevant material view exists and the extended SPP flag is set in the target system.
● The report PRD_SCM_GUID_CONVERSION must be executed for materials with initial SCM_MATID_GUID16
and SCM_MATID_GUID22 in the tables MARC or MDMA.
● You have migrated or defined settings in the following migration objects:
○ eSPP - Location [page 762]
○ eSPP - Product [page 765]
○ eSPP - MRP Area [page 767]
Source System
Not relevant
Target System
 Note

Name of this migration object: /SCMB/ESPP_MIG_LOC_PRODUCT
Post-Processing
Not relevant

Change MM02
Display MM03
1.254 eSPP - Transportation Lane
Purpose
This migration object enables you to migrate the transportation lane with the corresponding source of supply
master data from the source APO SPP to the target eSPP within SAP S/4HANA based on the global filter
parameter set in the migration project.
In eSPP within SAP S/4HANA the APO data model for the transportation lane, source of supply and external
procurement remains unchanged. The purpose of this migration is to update the corresponding tables with the
data transferred from the APO system.
Related Business Object: Transportation Lane

Business Object Definition A transportation route between two locations in a supply
chain model.
Available Scenarios
Selection Criteria
Transportation lane data to be migrated is automatically selected using migration-relevant plant(s).
In Scope
● Transportation lane data

● Means of transport data
● Source of supply data
● External procurement data
Out of Scope
● Transportation lanes which are not connected to any location selected by the global filter
● Means of transport which are not assigned to any selected transportation lane
● Source of supply without a corresponding transportation lane
● External procurement without a corresponding source of supply
Prerequisites
● The location and product master data must be migrated first. Transportation lanes containing locations
which are not migrated will not be migrated.
○ eSPP - Location Product [page 769]
Source System
Not relevant

Target System
 Note
Name of this migration object: /SCMB/ESPP_MIG_TRANSP_LANE
Post-Processing
Not relevant

Change /SAPAPO/SCC_TL1
Display /SAPAPO/SCC_TL1
1.255 eSPP - Bill of Distribution (BoD)
Purpose
This migration object enables you to migrate the bill of distribution (BoD) master data from the source APO
SPP to the target eSPP within SAP S/4HANA based on the global filter parameter set in the migration project.

In eSPP within SAP S/4HANA the APO data model for the bill of distribution remains unchanged. The purpose
of this migration is to update the corresponding tables with the data transferred from the APO system.
Related Business Object: Bill of Distribution
Business Object Definition Hierarchically structured network of locations predefining

the distribution routes for products within Service Parts
Planning (SPP).
Available Scenarios
Selection Criteria
Bill of distribution data to be migrated is automatically selected using migration-relevant plant(s).
In Scope
● Bill of distribution data

● BoD assignment to the active model
Out of Scope
● BoD assignment to a simulation model
Prerequisites
● The transportation lane master data must be migrated first.
○ eSPP - Transportation Lane [page 771]
Source System

Not relevant
Target System
 Note
Name of this migration object: /SCMB/ESPP_MIG_BOD
Post-Processing
Not relevant
Change /SAPAPO/BOD001
Display /SAPAPO/BOD001
1.256 eSPP - Product BoD Assignment

Purpose
This migration object enables you to migrate the product bill of distribution (BoD) assignment data data from
the source APO SPP to the target eSPP within SAP S/4HANA based on the global filter parameter set in the
migration project.
In eSPP within SAP S/4HANA the APO data model for the BoD assignment remains unchanged. The purpose
of this migration is to update the corresponding tables with the data transferred from the APO system.
Related Business Object: Product BoD Assignment
Business Object Definition Product assignment to a hierarchically structured network of

locations.
Available Scenarios
Selection Criteria
Product BoD assignment data to be migrated is automatically selected using migration-relevant plant(s).
In Scope
● Product BoD assignment data
Out of Scope
● Product BoD assignment in simulation version

● Product BoD assignment in the past
Prerequisites
● The bill of distribution master data must be migrated first.
○ eSPP - Bill of Distribution (BoD) [page 773]

Source System
Not relevant
Target System
 Note
Name of this migration object: /SCMB/ESPP_MIG_BOD_PRODUCT
Post-Processing
Not relevant
Change /SAPAPO/PROD2BOD_M
Display /SAPAPO/PROD2BODDISP
1.257 CO - Cost rate

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

● CO - Cost center [page 947]
Validity Period and Dependencies
Business objects that reference this object must be created within the correct validity period for this object.

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

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

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

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

Level Name
1 Bank master data (mandatory)
Tasks

Explorer.
Post-Processing
To validate your migrated data, you can use the FQM_FLOW table in transaction SE16N. To get results, you have
to enter the values Technical ID and Company Code. You can retrieve these from the FCLM_BAM_AMD table.
Transaction SE16N General Table Display
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 the same key can be migrated again using a new migration project.
1.259 Bank

Purpose
Business Object Definition An institution that provides financial services to individuals

and to businesses for profit, generally including taking
money deposits, issuing credit, and processing transactions.
In Scope
Supported Features
● Bank Country
● Bank Key
● Bank Address Data
Level Name
1 Bank master data (mandatory)
Tasks

Explorer.

Post-Processing
Transaction FI03 Display Bank
1.260 Batch unique at material and client 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

2. Segmentation is not supported

Supported Features
● Material Number
● Batch Number
● Plant
● Batch Attributes
● Batch Status
● Characteristic Values
● Control Parameters
Prerequisites
● Product [page 1021]

● Supplier [page 1107]
● If you want to migrate batches with classification data, the following objects need to be migrated first:
○ Characteristic [page 796]
○ Class [page 801]
○ Object classification - General template [page 807] – 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 that your material is assigned to. All 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 match 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 measurement:
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

Level Name
2 Classification CURR Values
2 Plant
New Characteristic Value (DATE) and Characteristic Value (TIME) Columns
Starting with SAP S/HANA 1802, you can enter values for Lower Boundary for Date-Interval and Upper
Boundary for Date-Interval in the Characteristic Value (DATE) columns. For Lower Boundary for Time-Interval
and Upper Boundary for Time-Interval, you can enter values in the Characteristic Value (TIME) columns on the
Classification NUM Values sheet in the migration template. Please note that values entered for Internal Floating
Point Value From and Internal Floating Point Value To in the Characteristic Value columns are always given
priority. When you enter values for these fields, values entered for Characteristic Value (DATE) and
Characteristic Value (TIME) will not be considered when migrating.
Tasks

Explorer.
Post-Processing
Transaction MSC3N Display Batch

Purpose
Sales and Distribution (SD)
Business Object Definition Batch Master Data if batch is unique at plant level
In Scope
1. Batch basic data
Out of Scope
1. Long texts for batches

Supported Features
● Material Number
● Batch Number
● Plant
● Batch Attributes
● Batch Status
● Control Parameters
Prerequisites


● If you want to migrate batches with classification data, the following objects need to be migrated first:
○ Characteristic [page 796]
○ Class [page 801]
○ Object classification - General template [page 807] – Please see the mapping instructions for this
object, paying special attention to the Material Classification for Batches section.
Level Name
1 Batch Basic Data (mandatory)
2 Classification CHAR/BOOL Values
2 Classification NUM Values
2 Classification CURR Values
Class Field on the Batch Basic Data Sheet

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

The values in the VALUE_FROM and VALUE_TO fields always relate to the unit of measurement of the
characteristic.
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 From and Internal Floating Point To values according to the Base UoM From
(ISO) defined in the Characteristic itself (in this case KGM). The Base UoM From (ISO) and Base UoM To (ISO)
fields are filled with the desired Units of Measure in ISO.

Internal Floating Point From Internal Floating Point To Base UoM From (ISO) Base UoM To (ISO)
100 1000 KGM TNE
● 1 for EQ (Equal),
Input example:
● VALUE_FROM: 20
● VALUE_TO: 28
Imported value:
● 20≤ X <28
New Characteristic Value (DATE) and Characteristic Value (TIME) Columns
Starting with SAP S/HANA release 1809, you can now enter values for Lower Boundary for Date-Interval and
Upper Boundary for Date-Interval in the new Characteristic Value (DATE) columns and for Lower Boundary for
Time-Interval and Upper Boundary for Time-Interval in the new Characteristic Value (TIME) columns on the
Classification NUM Values sheet in the migration template. Please note that values entered for Internal Floating
Point Value From and Internal Floating Point Value To in the Characteristic Value columns are always given
priority. When you enter values for these fields, values entered for Characteristic Value (DATE) and
Characteristic Value (TIME) will not be considered when migrating.
Tasks

Explorer.

Post-Processing
Transaction MSC3N Display Batch
1.262 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, quantity, and
unit of measure. These 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 process only one alternative BOM for each material number, plant, and BOM usage. This
can apply to any number from 01 to 99.
2. Material BOM
3. For object dependency, only the assignment of global dependency is supported. Selection condition and
Procedure are the only dependency types that are supported so far.
4. The following Item Categories (Bill of Material) are supported:
○ L-Stock item
○ N-Non-stock item
○ D-Document item
○ R-Variable size item
○ T-Text item
Out of Scope
1. Document structure
2. Equipment BOM
3. Functional location BOM
4. Sales order BOM
Supported Features
● BOM Header
● BOM Items
● BOM Subitems
● Global dependency
● Local dependency
● Description of local dependency
● Source code of local dependency
● Documentation of local dependency
● Document assignment

Prerequisites
To ensure that the data remains consistent, check that the decimal separator used in the file is the same as the
one used in user settings. Check the user settings first.
Business objects that reference this object must be created within the validity period that fits this object.
If a successor object is created with a validity period starting before this object, this will normally cause an error
message during the creation or migration of the successor object.
Therefore, make sure that you check such time dependencies before you create or migrate your objects. This
will help you to avoid later error messages and inconsistent data on your database.
Level Name
1 BOM Header
(mandatory)
2 BOM Items (man

datory)
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, do not copy and paste values from another Excel file into these fields,
because Excel will corrupt the data type of these fields. This in turn would cause the wrong numbers to be
migrated 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). 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.
Before uploading the XML file to the Migration Cockpit, check that the data type of these fields was not
changed from String to Number.
Tasks

Explorer.
Post-Processing
Transaction CS03 Display Material BOM

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 790]
● Document info record [page 861]
Out of Scope
Internal numbering isn’t 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
To validate your migrated data, you can use the following tables in the transaction SE16N.
● AENR - Change master

● AEOI - Object management records for change master
● AEDT - Alternative dates
● AENV - Object types for change master
Transaction CC01 Create Change Number
Transaction CC02 Change Change Master
Transaction CC03 Display Change Master

1.264 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 801]
Business objects that reference this object must be created within the correct validity period of this object.

Level Name
1 Characteristic Attributes (mandatory)
2 Characteristic Descriptions (manda

tory)
2 Type CHAR Characteristic value
2 Numerical Characteristic value
2 Type CURR Characteristic value
2 Descrip. for CHAR based values
2 Check table for References
2 Attributes' Additional data
2 Restrictions to Class Types
As of SAP S/4HANA 2008, the object supports the migration of characteristics with value descriptions only.
For each language, only one empty characteristic value is allowed.
Valid From
The value of this field can only be inherited from the change number. If the change number is empty, Valid from
will be ignored.
Build up a Value Hierarchy of Character Values

This functionality is only supported in SAP S/4HANA.
You can build up a value hierarchy for character-based values.
Here is an example for such a value hierarchy:
Level Name
1 EUROPE
2 GERMANY
3 BAVARIA
3 SAARLAND
3 SAXONIA

Level Name
2 ITALY
3 SICILIA
To build this value hierarchy for a characteristic name COUNTRY, you have to fill the fields on the Allowed
character based values sheet like this:
Characteristic Value (long) Value-High (long)
COUNTRY EUROPE
COUNTRY GERMANY EUROPE
COUNTRY BAVARIA GERMANY
COUNTRY SAARLAND GERMANY
COUNTRY ITALY EUROPE
COUNTRY SICILIA ITALY
Build up an Interval with Different Unit of Measure (UoM)
This functionality is only supported in SAP S/4HANA.
You can build up an interval based on different UoMs from the same dimension.
Here is an example of such an interval based on the numerical values:
The Characteristic Attributes field Base Unit of Measure (ISO) is filled with KGM.
On the Allowed NUMmerical values sheet, you want to have the following intervals:
● 100,00 kg to 1,00 t
● 10,00 mg to 100,00 g
To build this value interval you have to fill the fields on the Allowed NUMerical values sheet like this:
Enter the Internal Floating Point Values based on the UoM defined in the Characteristic Attribute sheet. The
Base UoM fields are filled with the wanted UoMs in ISO.
Internal Floating Point Internal Floating Point

Value From Value To Base UoM From (ISO) Base UoM To (ISO)
100 1000 KGM TNE
0.00001 0.1 MGM GRM
New Characteristic Value (DATE) and Characteristic Value (TIME) columns:
As of SAP S/HANA 1802, you can enter values for Lower Boundary for Date-Interval and Upper Boundary for
Date-Interval in the 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 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 Characteristic Value
(TIME) will not be considered when migrating.

Document Details
As of SAP S/HANA Cloud 1805, document details in the additional data are supported.
User-Defined Data Type (031)

The userdefined data type is NOT supported in SAP S/4HANA Cloud.
Tasks

Explorer.
Post-Processing
Transaction CT04 Characteristics
Further Information
● For this migration object, SAP delivers a prefilled sample XML template that helps you to fill out your data
migration template. Use this link to navigate to the Data Migration Template Samples for SAP S/4HANA
Cloud.
1.265 VC - Characteristics group
Purpose
Business Object Component/Area LO-VCH-GRP

Business Object Definition A group of classification characteristics with a defined order.
It is used for structuring the user interface, which shows

many characteristics.
It has a language-dependent description.
In Scope
● Migrate characteristic group
Out of Scope
● The "classic" Variant Configuration (LO-VC) had its own concept for grouping of characteristics. This is not
supported for Advanced Variant Configuration.
Supported Features
● Characteristics
● Description
● Configuration Profile
Prerequisites
● Characteristic [page 796]

● Class [page 801] (optional)
● Product [page 1021] (optional) – assigned with class and with class type 300
● VC - Configuration profile [page 826] (optional)
Characteristic [page 796] must be created first.

Level Name
1 General Information
2 Characteristics
2 Description
2 Configuration Profile
Tasks

Explorer.
Post-Processing
App: Manage Characteristic Groups
VC Modeling Environment (Display Configuration profile)
Business Role: Product Configuration Modeler

(SAP_BR_PRODUCT_CONFIG_MODELER)
1.266 Class

Purpose

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 class types in the system are supported.
Additional Values in the General Data

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

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

Transaction CL03 Display Class
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.
1.267 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
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 the 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 be higher than the level of its parent/superior class)
Hierarchy level
The hierarchy levels (Level) can be anything you like, but we recommend assigning level 1 to the instance, level
2 to its immediate subordinate classes, and so on. The hierarchy level of each class is higher than the level of its
superior class (the one without the Link indicator).
Description (optional)
The field has no function and will be not migrated.
You can enter some comments here to have a better overview of the class hierarchy.
General flag (Link)

When a class is assigned to a second superior class, this field must contain X in the first entry.
Example:Class5 has two superior classes, this means we have two entries which Child class name is Class5,
the link must be set to X in the first entry.
Input:
Instance class name Parent class name Child class name Level Link
Class1 Class1 Class2 1
Class1 Class3 Class5 2 X
Class1 Class5 4
Classification status (optional)

Defines whether the allocation is released for class search, or locked.
Left class name (optional)

Specifies the class name which is is on the left side of child class name.

Right class name (optional)
Specifies the class name which on the right side of child class name.
Tasks

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

● Information for classification: SAP Note 2267878
1.268 Object classification - General template
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 object classes (assign object 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 for internal key.
4. Class type Inspection Characteristics (005) is supported.
5. Class type Inspection Methods (006) is supported.
6. Class type Code Groups (007) is supported.
7. Class type Selected Sets (008) is supported.
8. Class type Vendor Class (010) is supported.
9. Class type Customer Class (011) is supported.
10. Class type Message Item Class (015) is supported.
11. Class type Document Management (017) is supported.
12. Class type Work Center Class (019) is supported.
13. Class type Batch (022 and 023) is supported.
14. Class type Engineering Change Management (025) is supported.
15. Class type Customer-material info record (052) is supported.
16. Class type Purchasing Info Record (057) is supported.
17. Class type Maintenance Plan (080) is supported.
18. Class type Material - Configurable Objects (200) is supported.
19. Class type Variants (300) is supported.
Out of Scope
● Other class types.
Supported Features
● Basic Data
● Characteristic Values (only for material classification)

● Change Number
Prerequisites
● Characteristic [page 796] (dependent on class type)

● Class [page 801] (dependent on class type)
● Product [page 1021] (dependent on class type)
● PM - Equipment [page 885] (dependent on class type)
● PM - Functional location [page 899] (dependent on class type)
● Supplier [page 1107] (dependent on class type)
● Customer [page 846] (dependent on class type)
● Document info record (manually, dependent on class type)
● Work center/Resource [page 1117] (dependent on class type)
Concatenated key Instructions
Level Name
1 Header data (mandatory)
2 Numerical value allocation
2 Currency value allocation
2 Character value allocation

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
● Valid from date: (optional) <valid from date> (system date if not filled)
● On the Value Allocation sheets, make the necessary entries.
Equipment Classification
To assign class and characteristic values to equipment, 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: 002

● Class Name: <Equipment Class Name> (Technical Name)
● Object Key: <Equipment 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 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 in 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
the characteristic values. Make the necessary entries on the Value Allocation sheets.
Inspection Characteristics Classification

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

● Class Name: <Inspection characteristics Class Name> (Technical Name)
● Object Key : concatenate < Plant & Master Inspection Characteristic> to assign the variants
related class
● Status: 1

Inspection Methods Classification
To assign class and characteristic values to inspection methods, the source file must contain the Header Data
● Class Type: 006

● Class Name: <Inspection methods Class Name> (Technical Name)
● Object Key : concatenate < Plant & Inspection Method> to assign the variants related class
● Status: 1
Code Groups Classification

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

● Class Name: <Code Groups Class Name> (Technical Name)
● Object Key : concatenate < Catalog & Code Group> to assign the variants related class
● Status: 1
Selected Sets Classification

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

● Class Name: <Selected Sets Class Name> (Technical Name)
● Object Key : concatenate < Plant & Catalog & Selected Set> to assign the variants related class
● Status: 1
Vendor Classification
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 in the following fields:
● Class Type: 010

● Class Name: <Vendor Class Name> (Technical Name)
● Object Key: <Vendor> to assign the variants related class
● Status: 1

Customer Classification
To assign class and characteristic values to customer, the source file must contain the Header Data sheet and
the Value Allocation sheets. On the Header Data sheet, fill in the following fields:
● Class Type: 011

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

To assign class and characteristic values to a message item, the source file must contain the Header Data sheet
● Class Type: 015

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

To assign class and characteristic values to document, the source file must contain the Header Data sheet and
the Value Allocation sheets. On the Header Data sheet, fill in the following fields:
● 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
● Value Allocation sheets.
Work Center Classification

To assign class and characteristic values to work center, the source file must contain the Header Data sheet
● 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

Material Classification for Batches

Batches are classified using the Batch unique at material and client level [page 783] or Batch unique at plant
level [page 786] 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. You can then fill in the
following fields:
● Class Type: 022 or 023

● Class Name: <Class Name>
● Object Key: <Material number> to assign to the batch related class
● Status: 1
● Value Allocation sheets must not be maintained in this case!
Engineering Change Management Classification

To assign class and characteristic values to engineering change management, the source file must contain the
Header Data sheet and the Value Allocation sheets. On the Header Data sheet, fill in the following fields:
● Class Type: 025

● Class Name: <Engineering Change Management Class Name> (Technical Name)
● Object Key: < Change Number> to assign the variants related class
● Status: 1
Customer-material info record Classification

To assign class and characteristic values to customer-material info record, the source file must contain the
Header Data sheet and the Value Allocation sheets. On the Header Data sheet, fill in the following fields:
● Class Type: 052

● Class Name: <Customer-material info record Class Name> (Technical Name)
● Object Key: concatenate < Sales Organization & Distribution Channel & Customer number
& Material Number> to assign the variants related class
● Status: 1
Purchasing Info Record Classification

To assign class and characteristic values to purchasing info record, the source file must contain the Header
Data sheet and the Value Allocation sheets. On the Header Data sheet, fill in the following fields:
● Class Type: 057

● Class Name: <Purchasing Info Record Class Name> (Technical Name)
● Object Key: concatenate < Number of purchasing info record & Material Number &
Supplier's Account Number> to assign the variants related class

● Status: 1
Maintenance Plan Classification
To assign class and characteristic values to maintenance plan, the source file must contain the Header Data
● Class Type: 080

● Class Name: <Maintenance Plan Class Name> (Technical Name)
● Object Key: <Maintenance Plan> to assign the variants related class
● Status: 1
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
Value From and Value To Fields
The values in the Value From and Value To fields always relate to the unit of measurement of the characteristic.
For example, if the unit of measurement of the characteristic is ISO UOM ANN (Year), 2 means two years. The
system ignores units in the Base unit of measure From (ISO Format) field and the Base unit of measure To (ISO
Format) field here. These are only displayed later.

● 1 for EQ (Equal)
Input example:
● VALUE_FROM: 20
● VALUE_TO: 28
Imported value:
● 20≤ X <28
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. Make sure that you use 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
The hierarchy definition is as follows::
Level Neutral Value
1 AB_Root_Level_1
2 A_First_Level_2

Level Neutral Value
3 A_Second_Level_3
2 B_First_Level_2
If you want to assign A_Second_Level_3, you make the following entries in the Character value allocations
structure:
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:
As of SAP S/4HANA release 1802, you can 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
Characteristic Value (TIME) will not be considered during the migration.
Tasks

Explorer.
Post-Processing
How to Validate Your Data in the System
Transaction CL24N Assigning Objects or Classes to Class
(Choose Class Class Type view)

Further Information
● For import information for classification see SAP Note 2267878 .
Purpose
Business Object Component/Area CO-OM-ABC
Business Object Type MD
Business Object Definition Business process (CO-OM-ABC): Process in a company that

uses resources and can involve the activities of different de
partments.

In Scope
1. Migration of Basic Data

2. Migration of Organization
3. Migration of Attributes
4. Migration of Allocation
5. Migration of Templates
Supported Features
● Business Process

Prerequisites
● CO - Profit center [page 1011]
Level Name
1 Business Process (Mandatory)
Tasks

Explorer.
Post-Processing
CP02 Change Business process
CP03 Display Business process

Further Information
1.270 CO - Statistical key figure
Purpose
Business Object Component/Area Statistical Key Figure (CO)
Business Object Definition The statistical values that describe::
● Cost centers
● Orders
● Business processes
● Profit centers
● Fixed value
Fixed values are carried forward from the current post
ing period to all subsequent posting periods.
● Total value
Totals values are posted in the current posting period
only.
In Scope
1. Statistical Key Figure

Supported Features
● Statistical Key Figure
Level Name
1 Statistical Key Figure (mandatory)
Tasks

Explorer.
Post-Processing
KK03 Display Statistical Key Figure
Further Information

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

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

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

Prerequisites

● Customer [page 846]
● Organizational Data such as company code, sales area, or purchasing org.
Condition Contract Header

The Condition Contract Header structure contains the business partner, the condition contract type, a validity
interval, the document status, currency information, exchange rate, terms of payment, purchasing
organization and sales area.
Header Texts
The Header Texts structure contains the different text objects which are stored on header level of the condition
contract.
Condition Structure Fields

The Condition Structure fields contain the corresponding condition-table-related information. The table
number, the condition type, the validity of the condition , the order key and the condition table key fields must
be specified. The order key, which is defined here for the condition structure, must be used consistently if you
define the item conditions and the condition scale settings.
Item Condition
The Item Condition structure contains the corresponding fields which define the condition such as the amount,
calculation type or currency. The order key must be part of the condition structure field table.
Condition Scale
The Condition Scale contains the corresponding fields which define the condition scales. The order key must
be part of the condition structure field table.
Business Volume Base

The Business Volume Base structure contains the business volume selection criteria. You must specify the
order key, the field combination, the include/exclude indicator and selection fields related to a field
combination.
Settlement Dates
The Settlement Dates structure contains the settlement dates for the different types of settlement (delta
accruals, partial, final, delta, and accruals deferral settlement). You must specify the order key, the settlement
date type, and the settlement date as a minimal data set. All other fields are optional.

Eligible Partners
The Eligible Partners structure contains the eligible partners for the condition contract. You must specify the
order key and an eligible partner as a minimal data set. All other fields are optional. You cannot pass data for
different eligible partner types at the same time.
Texts for Eligible Partners

The Eligible Partner Texts structure contains the different text objects which are stored on the level of the
eligible partner. The order key is used to link the text and the eligible partner entry.
Level Name
1 Condition Contract Header

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

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

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

(optional)
Tasks

Explorer.
Post-Processing
Transaction WCOCO Process Condition Contract

1.272 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 1057] or Condition record for pricing in purchasing (restricted) [page 989].
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
Supported Features
All structures/features are supported.

Prerequisites

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

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

Examples
Example of a Quantity-Based Scale:
Scale quantity Scale unit of measure Scale rate Scale currency
1,000 EA 100,00000 EUR
100,000 EA 90,00000 EUR
Example of a Scale-Based on Gross Weight:
1,000 KG 100,00000 EUR
100,000 KG 90,00000 EUR
Example of a Value Scale:
Scale value Scale currency Scale percentage
100,000000 EUR 5,000000
1000,000000 EUR 10,000000
1.273 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 - General template [page 807]
● Change number (optional)
Level Name
1 Attributes (mandatory)
2 Global dependencies (op

tional)
2 Basic data of local depend

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

● Attributes
Configuration profile name must be unique.

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

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

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

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

Tasks

Explorer.
Post-Processing
Transaction CM_DISPLAY_CONSENT Search and Display Consent Records
Purpose
Business Object Component/Area Purchasing (MM-PUR)

materials or services are released (ordered, or called off), ac
cording to need, over a 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
5. Delivery Addresses
6. Account Assignment
 Note
The following Account Assignment Categories are supported:

○ Cost Center
○ Asset
○ WBS Element
○ Sales Document
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 an info record is already available, 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 subitems (for example, inclusive/exclusive bonus quantity, display, and so on) are taken into account.
5. The control key for quantity management in procurement (EKPO-SSQSS), and the certificate category
(EKPO-ZGTYP) are only taken into account to a certain extent: This information is copied from the
reference contract or the material master record, but can't be changed, and no checks are carried out for
these two fields.
6. The revision level (EKPO-REVLV) is not changeable, because various quality management routines haven't
been implemented.
7. Version management (document change management) is not supported.
8. External services (planned and unplanned services) are not supported.
9. Creation of configurations is not supported.
10. The following Item Categories are not supported:
○ Third-Party
○ Enhanced Limits
○ Consignment
○ Subcontracting

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

● WBS element
● Fixed asset (incl. balances and transactions) [page 889]
● FI - G/L account [page 907] (expense account used in account assignment category)
● MM - Purchasing info record with conditions [page 1038] (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 check and ensure 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

Level Name
3 Account Assignment
3 Item Texts
Tasks

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

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 or extend already existing suppliers/contract
partners as customer with the same number.
2. General data (only fields that might become relevant when you extend a supplier/contract partner as
customer)
3. BP Roles
4. Additional addresses
5. Sales data including sales partner functions and sales data texts
6. Company data including dunning, withholding tax, and company texts
7. Bank data
8. Credit card data
9. Industry assignments
10. Tax classification
11. Tax numbers
12. Identification numbers
13. Contact persons, including address data with telephone, fax, and email.
14. VAT registration number against customer (South Korea only)*
15. TAN and exemption number (India only)*
16. Customer hierarchy for invoice summary (Japan only)*
17. Alternative name for payer (Japan only)*
18. Terms of payment with validity period (Japan only)*
19. Tax payment classification (Poland only)*
20.Tax type assignment (Romania only)*
21. VAT Cash Account. Regulation (Portugal only)*
 Note
Structures and fields/field groups marked with an asterisk (*) are visible only if the configuration of your
system covers the requirement for them at the time of the download.

Out of Scope
1. Updates of existing fields/records.

2. Sales partners can only be updated together with the related sales data. It isn’t 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.
 Note
This migration object is based on the assumption that business partner and customer are using the same
partner ID. If you’ve customized your system in a different way, you must adjust the migration object. If you
must adjust the migration object, you can use the migration object modeler or ask for consulting support.
Supported Features
All listed structures/features are supported.
Prerequisites

● If you want to extend already existing suppliers as customer with the same number:
○ Supplier [page 1107]
On the General Data sheet, we provide fields that 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) by using the Convert Values task. This ensures that the key mapping is added to the central key
mapping store of the SAP S/4HANA system. This, however, 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
isn’t necessary to switch on the key mapping for the Customer ID.
RUN ID
On the General Data sheet, you find an additional key field, RUN ID. This field is a counter that you can use to
execute several enhancements for the same instance. You can't import the same source record more than once
in the same project. The RUN ID field is an additional key field to which you can import the same customer
more than once.
For example, in the first step, import customer "A" with a new company code or sales view. In the second step,
import the same customer "A" with another company code or sales view.
You can distinguish the enhancements for the same instance by the different run IDs. In this scenario, you must
ensure that the migration for one run ID has been completed before uploading data with another run ID for the
same instance.
Sensitive Fields for Dual Control

If you’ve 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 is then considered as changes, and you must confirm them later on. For this reason, you should
consider deactivating 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 that 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 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 using 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 relevant field in the Contact person sheet. This number is required for
internal data processing. During processing, however, 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’ll 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
automatic determination of the Tax Jurisdiction Code for each record.
Dunning Data in On-Premise Version
Dunning data is included in the Company Data sheet. This dunning data doesn’t contain the Dunning Area field.
If a dunning area is needed, you need to adjust the mapping in your project with the SAP S/4HANA data
migration modeler (Transaction LTMOM), create a new structure, and maintain the field mapping for this sheet.
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 Withholding Tax Data
3 Company Texts
2 Bank Data
2 Credit Card Data
2 Industries
2 Tax Classifications
2 Tax Numbers
2 Identification Numbers

Level Name
2 Contact Person
2 VAT registration number

against customer*
2 TAN and exemption number*
2 Customer hier. f. inv. sum

mary*
2 Alternative name for payer*
2 Terms of paym. w. val. pe

riod*
2 Tax payment classification*
2 Tax type assignment*
2 VAT Cash Account. Regula

tion*
 Note
Country-Specific Extensions
 Note
Countryspecific extensions are visible only if the configuration of your system covers the requirement for
them at the time of the download.
Country-Specific Extension for South Korea

There are three countryspecific fields in the general data of the business partner: Type of Business, Type of
Industry, and Name of Representative. Note that these fields are overwritten by the latest corresponding fields
of the VAT registration number against customer data sheet. If there are multiple entries in this sheet, the three
fields will be updated by the entry with the most recent date. If there’s no entry on the VAT registration number
against customer sheet, the three fields will stay as they are.
Country-Specific Extension for India

To be able to maintain TAN-Based Exemption information on the TAN and exemption number sheet for India,
maintain Withholding Tax Type and Withholding Tax Code on the Withholding Tax Data sheet first.

Country-Specific Extension for Poland
The tax payment classification is used to maintain the VAT payment type for the customer. There are three
possible options:
1. VAT payment type 1: Split Disabled – This means that the customer can’t be used for split payment
between the given date range
2. VAT payment type 2: Split Enabled – This means that the customer can be used for split payment between
the given date range
3. VAT payment type 3: Split Mandatory – This means that the customer must be used for split payment
For a customer, the validity date ranges on the Tax payment classification sheet must not overlap between
different records of one customer and must be continuous.
Country-Specific Extension for Romania
Business partners in Romania must be classified for VAT registration.
The tax type classification describes where the customer is registered for VAT. There are four possible options:
1. Tax type 1: Registered for VAT in Romania

2. Tax type 2: Not registered for VAT in Romania
3. Tax type 3: Not established in Romania, but established in the EU
4. Tax Type 4: Not established in the EU
For a customer, the validity date ranges on the Tax type assignment sheet must not overlap between different
records of one customer and must be continuous.
Tasks

Explorer.
Post-Processing
Transaction BP Maintain Business Partner

1.277 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
● As a prerequisite, you need to migrate the customer master data with the Thailand company code
assigned.
● You can only set one branch code as the default branch code. If only one branch code is assigned, it is set
as the default automatically.
● If branch codes are already assigned to the customer, you cannot add additional branch codes with a
default indicator.
● As the standard method for communication (part of the address information), only the following values are
supported: Fax, E-Mail, and Telephone.
Level Name
1 Thailand branch code
Tasks

Explorer.
Post-Processing

1.278 Customer - extend existing record by Credit Management
data
Purpose
tionship exists whereby the customer orders goods or serv
ices from the company. This is one of the most commonly
used master data objects, used by almost all business appli
cations.

SAP SRM, and many industry solutions, the business part
ner approach is used.
In Scope
1. Credit management profile data

2. Credit management segment data
Out of Scope
1. Updating existing fields or records

2. Segment data can only be loaded together with the profile data. You cannot add profile data if segment
data is already loaded.
 Note
partner ID. If you have customized your system in a different way, you must adjust the migration object. If
you must adjust the migration object, you can use the migration object modeler or ask for consulting
support.

Supported Features
● All structures/features are supported.
Prerequisites
 Note
If you submit a credit limit amount, the amount value is 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: Changing the credit limit 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 disabling this event during migration. If the event is disabled, the
credit limit is stored directly in the target field. To disable the event, proceed as follows:
1. In Customizing, navigate to Financial Supply Chain Management Credit Management Credit Risk
Monitoring Processes .
2. Execute Define Events and Follow-On Processes.
3. In the Dialog Structure pane on the left, open Events Follow-On Processes .
4. Remove the LIMIT_REQ follow-on process for the Change to Credit Limit Requested event.
Level Name
1 Credit MD for Partner (Profile)
2 Credit MD for Partner (Segment)
Events and Follow-On Processes
If you have defined Events and Follow-On Processes in the Configure Your Solution app, you have to be aware
that migrated data records will trigger such an event immediately after creation, and migrated values might be
changed through the defined events and follow-on processes. For this reason, you should consider deactivating
this option before you start with the data migration, and activate it again afterwards

Tasks

Explorer.
Post-Processing
1.279 SD - 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 Classification
● CustMat Classif Numbers
● CustMat Classif Characteristic
● CustMat Classif Currency
Prerequisites

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

tic
3 CustMat Classif Currency
For more information, see the field description of the template file.
Tasks

Explorer.

Post-Processing
Transaction VD51 Create Customer-Material Info record
Transaction VD52 Change Customer-Material Info record
Transaction VD53 Display Customer-Material Info record
1.280 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

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.

SAP SRM and many industry solutions, the business partner
approach is used.
In Scope
1. General data with standard address data and localization fields for Brasil, India, Taiwan, South Korea, and
Philippines*
2. BP Roles
4. Sales data including sales partner functions and sales data texts
5. Company data including dunning, withholding tax, and company texts
6. Bank data
7. Credit card data
8. Industry assignments
9. Tax classification
10. Tax numbers
12. Contact persons, including address data with telephone, fax, email
13. VAT registration number against customer (South Korea only)*
15. Customer hierarchy for invoice summary (Japan only)*
16. Alternative name for payer (Japan only)*
17. Terms of payment with validity period (Japan only)*
19. Tax type assignment (Romania only)*
20.VAT Cash Account. Regulation (Portugal only)*
 Note

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 1098] object, you can create a supplier
with the same customer number. As a prerequisite, you have to create the customer first.
 Note
need to adjust the migration object, you can use the migration object modeler or ask for consulting
support.
Supported Features
● General Data
● BP Roles
● Additional Addresses
● General Texts
● Sales Data
● Sales Partner
● Sales Organization Texts
● Company Data
● Withholding Tax Data
● Company Texts
● Bank Details
● Payment Card Data
● Industries
● Tax Classifications
● Tax Numbers
● Identification Numbers
● Contact Persons
● VAT registration number against customer (South Korea only)*
● TAN and exemption number (India only)*
● Customer hierarchy for invoice summary (Japan only)*
● Alternative name for payer (Japan only)*
● Terms of payment with validity period (Japan only)*
● Tax payment classification (Poland only)*
● Tax type assignment (Romania only)*

● VAT Cash Account. Regulation (Portugal only)*
 Note
Prerequisites
 Note
The Customer Account Group field must be in sync with your customizing of the BU grouping. Otherwise,
the grouping will overwrite the account group.
● Bank [page 781]
You have to maintain all business partner roles depending on your business transactions.
All mandatory partner functions are 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’s 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 isn’t 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 based
on the settings of the BP Grouping.
Assigned contact persons 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’s possible to create customers and one-time customers.
The settings which are made together with your BP Grouping customizing will determine whether the customer
will be created with internal or external numbering.
If you need to create a business partner with both customer and supplier roles, this can be achieved in a two-
step approach. To extend a customer that has already been migrated, you can use the Supplier - extend
existing record by new org levels [page 1098] 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
integration) using the Convert Values task. This ensures that the key mapping is added to the central key
mapping store of the SAP S/4HANA system.

If you’ve 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, which you must confirm later on. For this reason, you should
consider deactivating 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 that 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 that these business partners are
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
the relations and add them later using the BP maintenance UI or BP mass maintenance app.

Customers might have contact persons assigned who act in partner capacity. During migration, contact
persons are created as separate business partners using internal numbering. As 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 833] 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 relevant field on the Contact person sheet. This number is required
for internal data processing. However, during processing, a new business partner will be created with an
internal number. This business partner is automatically assigned to the customer with the corresponding
relationship.
Dunning Data in the On-Premise Version

Dunning data is included in the Company Data sheet. This dunning data doesn’t contain the Dunning Area field.
If a dunning area is needed, you can use the Dunning Data sheet. Please note that this sheet isn’t used in the
standard shipment. You need to adjust the mapping in your project by using the SAP S/4HANA data migration
modeler (Transaction LTMOM) to create the structure and field mapping for this sheet.

If Vertex is activated (especially on US installations), the tax jurisdiction code is determined by the address.
If Vertex determines more than one tax jurisdiction code for one record, the migration of this record will fail. If
this happens, you must provide a more detailed/accurate address, for example, US postal codes with 9 digits
The more detailed and accurate an address, the more accurately Vertex can 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
the automatic determination of the Tax Jurisdiction Code for each record.
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 Credit Card Data

Level Name
2 Industries
2 Tax Classifications
2 Tax Numbers
2 Contact Person
2 VAT registration number

against customer*
2 TAN and exemption number*
2 Customer hier. f. inv. sum

mary*
2 Alternative name for payer*
2 Terms of paym. w. val. pe

riod*
2 Tax payment classification*
2 Tax type assignment*
2 VAT Cash Account. Regula

tion*
 Note
 Note

There are three countryspecific fields on the General Data sheet of the migration template: Type of Business,
Type of Industry, and Name of Representative. Note that these fields are overwritten by the latest respective
fields of the VAT registration number against customer sheet. If there are multiple entries in this sheet, the three
fields will be updated by the entry with the most recent date. If there’s no entry on the VAT registration number
against customer data sheet, the three fields will stay as they are.

maintain Permanent Account Number on the General Data sheet as well as Withholding Tax Type, and
Withholding Tax Code on the Withholding Tax Data sheet first.

The tax payment classification is used to maintain the VAT payment type for the customer. There are three
possible options:
1. VAT payment type 1: Split Disabled – This means that the customer can’t be used for split payment
between the given date range.
2. VAT payment type 2: Split Enabled – This means that the customer can be used for split payment between
the given date range.
3. VAT payment type 3: Split Mandatory – This means that the customer must be used for split payment
For a customer, the validity date ranges on the Tax payment classification sheet must not overlap between
different records of one customer and must be continuous.

The tax type classification describes where the customer is registered for VAT. There are four possible options:

For a customer, the validity date ranges on the Tax type assignment sheet must not overlap between different
records of one customer and must be continuous.
Country-Specific Extension for Philippines

You can find one optional countryspecific field, Business Style, on the General Data sheet of the business
partner (with role customer/customer (financial accounting)). This field can be used for the business name
registered with the concerned regulatory body used by the taxpayer.
Tasks

Explorer.

Post-Processing
Further Information
● SAP Knowledge Base Article 2848224 – Migration Cockpit: Collective KBA for Business Partner
(Customer, Supplier)
● 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.281 DG - Assessment for unpackaged product (content-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, segregation groups, and infor
mation 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 Content-Based.

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

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

● Basic Classification Details
● Segregation Groups
Prerequisites
● PSS - Product compliance info [page 879] (object for migrating compliance views)
Level Name
1 Regulation (mandatory)
2 Segregation Group
Tasks

Explorer.

Post Processing
Log on to your SAP S/4HANA system as Configuration Expert - Data Migration

(SAP_BR_CONFIG_EXPERT_DATA_MIG) and use the Data Migration Status app to validate your data in the
system. Alternatively, use the following SAP Fiori app:
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
Product app.
Business Role: Dangerous Goods - Product Compliance

(SAP_BR_DG_SPLST_PCL)
1.282 DG - Assessment for packaged product (text-based)
Purpose
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
with a compliance pattern of type Text-Based.
Out of Scope

Supported Features

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

tion for Documents

Level Name
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
Log on to your SAP S/4HANA 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:
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.


1.283 DG - Assessment for unpackaged product (text-based)
Purpose
Business Object Definition A dangerous goods assessment for an unpackaged product

contains classification data, dangerous goods descriptions,
and information about transport permission.
In Scope
with a compliance pattern of type Text-Based.
Out of Scope

Supported Features

● Basic Classification Details
● Basic Description

Prerequisites
● PSS - Product compliance info [page 879] (object for migrating compliance views)
Level Name
2 Basic Description
Tasks

Explorer.

Post-Processing

Log on to your SAP S/4HANA system as Configuration Expert - Data Migration
(SAP_BR_CONFIG_EXPERT_DATA_MIG) and use the Data Migration Status app to validate your data in the
system. Alternatively, use the following SAP Fiori app:
Apps: ● For not released assessments, open the My

Unpackaged Dangerous Goods app and select a product
to navigate to the Classify Unpackaged Dangerous
Product app.
● For released assessments, open the Analyze
Unpackaged Dangerous Goods app, search for a prod
uct, and navigate to the Classify Unpackaged Dangerous
Product app.

1.284 Document info record
Purpose
Business Object Component/Area Document Management (CA-DMS)

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

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

Explorer.

Post-Processing
Transaction CV03N Display document
1.285 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 isn’t supported while creating a measurement document.
You can only create measurement documents for measuring points.

Supported Features
● Measurement document
Prerequisites
● PM - Measuring point [page 866]
● Only internal numbering is supported.

● Valuation code can only be entered into a measurement document if the associated pointer/counter refers
to a category that enables this functionality.
● Measuring unit for measurement reading will be derived from entered measuring point.
● In most cases, the Reading field is mandatory since it's required for the quantitative evaluation. There’s an
instance where it's not required to enter a value for reading, for example, when the measuring point is
defined for the qualitative valuation only (then 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
To validate your migrated data, you can use the IMRG table in the transaction SE16N. To get results, you have
to enter the value in the MeasDocument (MDOCM) field.
Transaction IK11 Create Measurement Document
Transaction IK13 Display Measurement Document
1.286 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
Measurement reading transfer is not supported.
Supported Features
● Header
Prerequisites
● PM - Equipment [page 885]

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

● If the measuring point is a counter, the Counter Data group must be filled
● If the measuring point is not a counter, the Target Value group must be filled
● Keep the following rules in mind:
○ 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 qualitative measurement means that an evaluation code is sufficient for use as a measuring
point, you do not need to enter any characteristics for the measuring point. Instead, you just specify
one code group and select the ValCode sufficient field.
○ If you want, you can assign both a characteristic and a code group to a measuring point.
Level Name

Tasks

Explorer.
Post-Processing
Transaction IK03 Display Measuring Point
1.287 PM - Maintenance notification
 Tip
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 1021]
● Work center/Resource [page 1117]
Level Name
1 Notification Header (manda

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

Explorer.

Post-Processing
Transaction IW21 Create PM Notification
Transaction IW22 Change PM Notification
Transaction IW23 Display PM Notification
1.288 EFD - Reinf report
Purpose
Business Object Component/Area EFD-Reinf (FI-LOC-FI-BR)
Business Object Definition Brazilian legal report EFD-Reinf
A legal report that is used by legal entities and natural per

sons to report paid income and withheld income taxes, non-
work-related social contribution, and gross income data to
fiscal authorities in Brazil.
In Brazil, the report is known as 'EFD-Reinf'.
In Scope
1. EFD-Reinf Files

Supported Features
● EFD-Reinf Files
Level Name
1 EFD-Reinf Files
Tasks

Explorer.
Post-Processing
App: Run Compliance Reports – Brazil GL Reporting
Business Role: General Ledger Accountant for Brazil

(SAP_BR_GL_ACCOUNTANT_BR)
You can use the Run Advanced Compliance Reports – Brazil GL Reporting app to generate the EFD-Reinf Legacy
Files report in order to visualize and maintain data that was migrated to the target system. Find more
information here.
Find more information about SAP Fiori apps in the SAP Fiori apps reference library. This information covers
required business roles and includes links to the respective app documentation.

Further Information
Find background information on the Escrituração Fiscal Digital de Retenções e Outras Informações Fiscais
(EFD-Reinf) here: EFD-Reinf - Background Information.
1.289 EHS - Location hierarchy
 Note
To open the EHS - Location hierarchy migration object in the SAP S/4HANA Migration Cockpit, the
Industrial Hygienist (SAP_BR_INDUSTRIAL_HYGIENIST) or the Environmental Manager
(SAP_BR_EHS_ENV_MGMT) business role must be assigned to the relevant user without any restrictions.
Purpose
Business Object Component/Area EHS-SUS-FND
Business Object Definition The location hierarchy represents the structure of locations
and their sublocations.
In Scope
1. Migration of Location Hierarchy Revision

2. Migration of Location Hierarchy
Supported Features
● Location Hierarchy Revision

● Location Hierarchy

Prerequisites
● EHS - Location [page 874]
Level Name
1 Location Hierarchy Revision (mandatory)
2 Location Hierarchy (mandatory)
Tasks

Explorer.
Post-Processing
App: Manage Locations
Business Role: Industrial Hygienist (SAP_BR_INDUSTRIAL_HYGIENIST)
1.290 EHS - Location

 Note
To open the EHS - Location migration object in the SAP S/4HANA Migration Cockpit, the Industrial
Hygienist (SAP_BR_INDUSTRIAL_HYGIENIST) or the Environmental Manager (SAP_BR_EHS_ENV_MGMT)
business role must be assigned to the relevant user without any restrictions.
Purpose
Business Object Component/Area EHS-SUS-FND
Business Object Definition An identified real place, virtual space, or object. The location
is a central master data object that can be organized in a hi
erarchy to represent where a location exists spatially or func
tionally in a company. Examples of a location are a plant, a
piece of equipment, or a work area.
In Scope
1. Migration of Location Revision

2. Migration of Location Revision Texts
3. Migration of Persons Responsible
Out of Scope
1. Environmental Details
2. Documents
Supported Features
● Location Revision
● Location Revision Texts
● Persons Responsible

Level Name
1 Location Revision (mandatory)
2 Location Revision Texts
2 Persons Responsible
Tasks

Explorer.
Post-Processing
App: Manage Locations
Business Role: Industrial Hygienist (SAP_BR_INDUSTRIAL_HYGIENIST)
1.291 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 1070]

Level Name
1 Chemical compliance view

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

Explorer.

1.292 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 1070]
● PSS - Raw material compliance info [page 876]
Level Name
1 Chemical compliance view

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

production
3 Legal deviation and substi

tute substances
2 Application
2 Material assignment
2 Market coverage
2 Market request
2 Bulk assignment
2 Purpose assignment
Preparation Migration Details for Products

Process the migration in two steps as follows:
1. Migrate bulk product using the following data from the migration template:
○ Chemical composition
○ Chemical component (substances or raw materials)
○ 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.
1.293 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 Item

Tasks

Explorer.
Post-Processing
Transaction IB03 Display Equipment BOM
1.294 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 (incl. long text)

● Operations (incl. long text)
● Production Resource/Tools
● Material Components
● Maintenance Packages
Prerequisites

Business objects that reference this object must be created within a validity period that matches this object.
later error messages and inconsistent data on your database.
● 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.
● Enter the long text for the Task List Header level in the Long textfield (S_TASKLIST_HDR-TDLINE).
● Enter the long text for the Operations level in the Long text field ( S_OPERATIONS-TDLINE).

Level Name
1 Task List Header data (man

datory)
2 Operations (mandatory)
3 Production Resource/Tools
3 Material Components
3 Maintenance Packages
Tasks

Explorer.
Post-Processing
Transaction IA03 Display Equipment Task List
1.295 PM - Equipment
 Tip

Purpose

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

● Equipment Manufacturer Data
● Equipment Customer Warranty
● Equipment Vendor Warranty
● Equipment Location
● Equipment Organization
● Equipment Structure
● Equipment Serial Data
● Equipment Partners
Prerequisites

● Superordinate Equipment: To use the Superordinate Equipment field, make sure that this value will be
implemented in the PM - Functional location [page 899] first.

Business objects that reference this object must be created within a validity period that matches this object.
You therefore have to check such time dependencies before you create or migrate your objects. This avoids
Level Name
1 Equipment master data (mandatory)
2 Partners
Internal /External Number Range

This migration object supports both internal and external numbering. If you want to use an external number
range, choose External Numbering for the Equipment, internal or external numbering control parameter in the
Convert Values step in the SAP S/4HANA Migration Cockpit. Otherwise, choose Internal Numbering.
Warranty Fields
Warranty fields can be displayed from the Fiori app only.
Tasks

Explorer.
Post-Processing
App: Display Technical Object

Business Role: Maintenance Planner (SAP_BR_MAINTENANCE_PLANNER)
Transaction IE01 Create Equipment
Transaction IE02 Change Equipment
Transaction IE03 Display Equipment
Further Information
SAP Knowledge Base Article 2878950 – Migration Cockpit: Collective KBA for Migration PM-Object
Equipment
1.296 Exchange rate
Purpose
Business Object Definition The relationship between two currencies.
This rate is used to translate an amount into another cur

rency.
In Scope

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

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

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

Purpose
With this migration object, you perform a legacy data transfer for fixed assets.
Business Object Component/Area Asset Accounting (FI-AA)
Business Object Type Master data and transactional data (asset values)


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

You use the SAP S/4HANA Migration Cockpit to transfer legacy data for fixed assets.
● You can transfer the asset master records for legacy assets.
 Note
The legacy asset number is migrated to the Original Asset field on the Origin tab page.
The Origin tab of the migration template must not necessarily be populated by you. The legacy asset
number and subnumber are added automatically to the fields of the asset master by the Migration
Cockpit.
For any customerdefined asset class, the Original Asset fields (asset number and subnumber) must be
enabled in order to use the Migration Cockpit.
 Note
Transfer of asset subnumbers:

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

Prerequisites

● CO - Activity type [page 954]
Level Name
1 Master Details (mandatory)
2 Inventory
2 Time-Dependent Data
2 Allocations
2 Origin
2 Acct. Assignment. 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 Local - Time-Independent
2 Local - 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 don’t 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, then 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 don’t 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’ve created a legacy data transfer segment and for it you’ve specified the transfer date, the document
type, and the legacy data transfer status in Customizing for Asset Accounting under Asset Data Transfer
Parameters for Data Transfer Define Transfer Date and Additional Parameters .
● If you want to perform a transfer during the year, you must enter the Last Period Posted
(FAA_DEPR_PERIOD) field on the Posted Values sheet.
You must specify the last posted depreciation period (from the legacy system) for each asset. The system
requires this information to determine the first period for the depreciation that should be posted in the SAP
system.
Required Activities
● The previous fiscal year must be closed in Asset Accounting.

This can be checked in Customizing for Asset Accounting under Preparations for Going Live Tools
Reset Year-End Closing .

● You’ve extracted the legacy data from your legacy system.
Pretest
We recommend that you perform a pretest in the test system: First, test system settings by performing a
manual legacy data transfer.
You can use the following Customizing activities (transactions) under Asset Accounting Asset Data
Transfer Manual Data Transfer Legacy Fixed Asset .
● Create Master Data for Legacy Asset (transaction AS91)

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

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

For details about how to reconcile the data, see SAP Note. 2304473 .

Changing Transfer Values Subsequently
When uploading the migration template, the system posts the asset values. We recommend the following: If
incorrect transfer values were posted, you should reverse the journal entry and then enter the transfer values
again. You can only change transfer values by reversing the posted transfer document and making a new
posting. For the asset master data already created, you set a deactivation date and block it from receiving
postings. In the productive system, there should be no data before you start the file upload.
Further Information
Product Assistance
For more information, see the SAP Help Portal. Choose your SAP S/4HANA system, and navigate to Asset
Accounting Legacy Data Transfer .
Further Links
● Fixed Assets: Available Fields per Asset Class

● SAP Knowledge Base Article 2827574 – Migration Cockpit: Collective KBA for migration object Fixed
Asset (incl. balances and transactions)
● 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.298 PM - Functional location task list
Purpose


In Scope
Supported Features

Prerequisites


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

datory)
Tasks

Explorer.
Post-Processing
Transaction IA13 Display FunctLoc Task List
1.299 PM - Functional location BOM

Purpose
Business Object Definition Plant Maintenance (PM)
A list used to describe the structure of a functional location

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

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

Prerequisites

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

Explorer.
Post-Processing
Transaction IB13 Display Functional Location BOM
1.300 PM - Functional location

 Tip
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 - Manufacturer Data
● Functional Location - Customer Warranty
● Functional Location - Vendor Warranty
● Functional Location - Location Data
● Functional Location - Organization Data
● Functional Location - Partners

Prerequisites

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

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

The labeling system is only supported in SAP S/4HANA.
Warranty Fields
Warranty fields can be displayed from Fiori app only.

Tasks

Explorer.
Post-Processing
App: Display Technical Object
Business Role: Maintenance Planner (SAP_BR_MAINTENANCE_PLANNER)
Transaction IL01 Create Functional Location
Transaction IL02 Change Functional Location
Transaction IL03 Display Functional Location
1.301 PM - General maintenance task list
Purpose


In Scope
Supported Features

Prerequisites

Internal/External number range assignment for Group and Group Counter:
● The Group and Group Counter must be provided in source file, and joint with task list type to distinguish
different type of task list. For the scenario of one Group with several Group Counters, they must be grouped
logically in the source file.
● With control parameter CTR_TLIST_A_NUM, you have to decide if it is internal or external during each data
load.
Level Name

datory)
Tasks

Explorer.
Post-Processing
Transaction IA07 Display General Task List

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

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

2. No updates of existing fields/records are possible.
Supported Features
● Controlling Area (formerly known as Cost Element Data)

● Company Code Specific Area

● GL Account Names
● GL Account Keywords
Level Name
2 Controlling Area Data
2 Company Code Data
2 Account Names
2 Account Keywords
Tasks

Explorer.
Post-Processing
Transaction KA01 Create Cost Element
Transaction KA06 Create Secondary Cost Element
Transaction FS00 G/L acct master record maintenance
Transaction FSS0 G/L account master record in co code
Further Information
SAP Knowledge Base Article 2848568 – Migration Cockpit: Collective KBA for G/L Account Master

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

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

● Controlling Area (formerly known as Cost Element Data)
● Company Code Specific Area

● GL Account Names
● GL Account Keywords
Level Name
2 Controlling Area Data
2 Company Code Data
2 Account Names (mandatory)
2 Account Keywords
Tasks

Explorer.
Post-Processing
Transaction KA01 Create Cost Element
Transaction KA06 Create Secondary Cost Element
Transaction FS00 G/L Acct Master Record Maintenance
Transaction FSS0 G/L Account Company Code Data
Further Information
SAP Knowledge Base Article 2848568 – Migration Cockpit: Collective KBA for G/L Account Master

1.304 FI - G/L account balance and open/line item (restricted)
 Restriction
This object is restricted and only supports the data migration of the following four currency fields:
● document/transactional balance currency

● company code currency
● group currency
● freelydefined currency
 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:

G/L account open/line item: Open/line items are the items

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

the Fixed asset (incl. balances and transactions) [page 889]
migration object. You must NOT migrate these balances with
the FI - G/L account balance and open/line item (restricted)
migration object. Therefore, you must ensure that your mi
gration file for G/L account balance doesn’t contain any re
cords 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 / VAT line items
○ Open tax must be settled before data migration
○ Tax code isn’t needed for the initial load of G/L account balance and open/line item using the
migration cockpit and is therefore not supported
○ Exception: Deferred tax can be migrated with the migration activities for Open items payable and
Open items receivable
SAP Note 2911854 – SAP S/4HANA Migration Cockpit: Migration of VAT line items is not
supported
4. Calculate tax automatically
5. Migration of historical financial transactions (use the FI - Historical balance (restricted) [page 914]
migration object; see SAP Note 2587192 )
6. Cash account: The balance on the cash account should be migrated as a portion of the balance of a bank
account. It should be posted later on in the cash journal as the opening balance from this bank account to
the cash account.

 Caution
Performing postings to the cash account with the migration object FI - G/L account balance and open/
line item (restricted) has no effect on cash journal transactions and will not update the cash journal
opening balance.
Supported Features
● Header
● G/L Account Item
● Currency Item
● Assignment to a Profitability Segment (CO-PA)
● Countryspecific (IT, RU, KR, MX)
Prerequisites
Before starting with the initial data transfer, you must define an overall migration key date for each company
code. This migration key date is used for all migration objects, which are posting into financial accounting,
except for the Fixed asset (incl. balances and transactions) [page 889] object.
Use the FINS_MIG_CTRL_1 transaction (Define Settings for Legacy Data Transfer) to maintain these settings:
● Set the Migration Key Date for each required company code
● Set the Legacy Data Transfer Status:
○ In Preparation: migration key date is still unclear (migration of transactional data isn’t 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 isn’t
possible)

Only mandatory if account assignment on cost center is necessary.
Posting on tax jurisdiction will be derived automatically 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 derived automatically 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 isn’t 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 (that 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 888]
Maintain Profit Center Configuration (this setup must be completed before posting any transactions to the
system):
● For automatic document splitting, the default profit center is defined as YB900 in S/4HANA Cloud. If no
profit center is provided via the migration template, the default profit center is chosen automatically.
There are 2 approaches for using the default profit center in an active document split:
1. Create YB900 as profit center master data to use the already defined default profit center.
2. To use your own default profit center, create a new profit center or choose an existing one as your
default profit center. Use the SSC-UI 120100 Edit Constant for Nonassigned Processes to replace
YB900 with your own default profit center.
More information about using the profit center in a document split can be found in the road map
viewer: https://go.support.sap.com/roadmapviewer/#/group//roadmap/IMPS4HANACLDENMGMT/
node/901B0E6D3F501ED788F20B5936A6DF96:
● In addition, a default profit center can be defined for each company code and G/L account or G/L account
interval. Use the configuration step 102529 Assign Default Profit Center to Accounts to configure this
detailed default profit center assignment to a General Ledger Account. This configuration takes
precedence over the first described configuration for the default profit center YB900.
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’ll reduce the number 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 the balances are usually
zero (for normal VATs) when the migration takes place. We assume that the tax transfer has already been done
and therefore no tax has to be migrated. Exception: Deferred taxes can be migrated with the migration
activities for Open items payable and Open items receivable.

● Enter only one line per document post into the migration file. The offsetting entry will be automatically
generated for the offsetting G/L account.
● The combination of key fields Company Code + Ledger Group + Reference Document Number + Line Item
Number + G/L Account are used for duplicate check. Data records with this combination should be unique
in the migration template. Otherwise, the migration tool will display a duplicate error message. The Line
Item Number will just be used as an additional key field and will not be migrated.
● Please be aware you must fill and save value amounts in the migration file in number and not in string
format. Check the settings for a delimiter.
● For migration, the posting keys will be controlled by the sign in the amount fields. The sign for negative
values should be set at the beginning:
○ A negative value will use posting key 50 (Credit entry) for G/L Account and 40 (Debit entry) for
Offsetting G/L Account
○ A positive value will use posting key 40 (Debit entry) for G/L Account and 50 (Credit entry) for
Offsetting G/L Account
● The initial offsetting (transfer booking) accounts to be used in the Open items and Open balances
migration objects are described in the BH5 test script :
○ 39914000 (Initial FI-AR offset)
○ 39915000 (Initial FI-AP offset)
○ 39916000 (Initial other GL offset)
○ 39917000 (Initial other Open Item GL offset)
Two approaches for currency and amount:

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

Level Name
2 South Korea Specific
2 Mexico Specific
Tasks

Explorer.
Post-Processing
Transaction FB01 Post Document
Transaction FB02 Change Document
Transaction FB03 Display Document
Further Information
● SAP Knowledge Base Article 2853964 – Migration Cockpit: Collective KBA for G/L Open Item or G/L
Balance or FI AP Open Item or FI AR Open Item
1.305 FI - Historical balance (restricted)
 Restriction


● group currency
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:

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 be reversed automatically 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

2. External accounting document number
3. Postings on blocked or non existing G/L accounts

4. Multiple assignment of cost center, profit center, or segment for the same historical balance posting
(identical key field combination)
Supported Features

● Currency Item
Prerequisites
○ 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)
● FI - G/L account [page 907]

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): Posts the initial cumulative balance in the first period provided. The
subsequent movements are provided by the migration template and are posted at the end of each
following period. The cumulative balance is increased or reduced by the amount of the subsequent
movements. The latest cumulative balance is carried from one period to the next if no further
subsequent movements are provided by the migration template. The balance is reverted automatically
in the period of the migration key date, which is predefined via the Define Settings for Legacy Data
Transfer app.
○ Next Period Movement (NPM): Posts each uploaded balance at the end of the posting period and
reverts it in the following period.

● Enter only one line per document post for each period into the migration file. The offsetting entry will be
generated automatically to ensure that the balance is zero. You don't need to reverse any data as this
uploaded data wasn't posted.
● 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. Don’t 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 aren’t 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 don’t match the customizing
settings.
○ Recommendation: provide all currency information via the template to ensure the provided amounts
match to the related currencies. Otherwise, inconsistencies might be migrated.
● Naming convention used as internal document number (for example, DHG0000001):
○ D = Document
○ H = Historical
○ G = GL balance
○ 0000001 = automatically counted up
● Naming convention used for reversal document number (for example, DHR0000001):
○ D = Document
○ H = Historical
○ R = Reversal
○ 0000001 = automatically counted up
Level Name
1 Item (mandatory)
Tasks

Explorer.

Post-Processing
Transaction S_PL0_86000030 G/L Account - Balances
Transaction FAGLB03 G/L Account Balance Display
1.306 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
Migration to SAP S/4HANA Cloud is supported.
This migration object does only support external number ranges.
Out of Scope
This migration object doesn’t support internal number ranges.

Supported Features
● Inspection Method General Data

● Inspection Method Short Text
● Inspection Method Long Text
Prerequisites

● QM - Selected set [page 1062]
● QM - Selected set code [page 1064]
● 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 separates 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 validity period 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.
Allowed Number Range for Keys (Inspection Method)

The migration object only supports the data migration of keys using the external number range. The key you
want to migrate must be from an external number range.
If you’re migrating keys that are within the internal number range, you’ve to manually adjust the Number Range
Status (NRLEVEL) after the migration is finished. The Number Range Status contains the last assigned
number for internal number range intervals.
Level Name
1 Inspection Method General Data (man

datory)

Level Name
2 Inspection Method Short Texts (manda

tory)
2 Inspection Method Long Texts
Tasks

Explorer.
Post-Processing
Transaction QS31 Create Inspection Method
Transaction QS32 Create Inspection Method Version
Transaction QS33 Change Inspection Method Version
Transaction QS34 Display Inspection Method Version
1.307 QM - Inspection plan (deprecated)
Purpose

Business Object Definition Description of the quality inspection process for materials in
a plant
In Scope
Out of Scope
This migration object does not support internal number ranges.
Supported Features
● Task List Header

● Material Task List Assignment
● Operations
● Inspection Characteristics
Prerequisites

● QM - Inspection method [page 918]
● QM - Master inspection characteristic [page 992]
normally cause an error message during the creation or migration of the successor object. To avoid error
messages and inconsistent data on your database, make sure you check any such time dependencies before
you create or migrate your objects.

Flow Variants for Inspection Point Completion

' ' - Quantity, valuation, and confirmation (production)
1 - Quantity, valuation (production)
2 - Valuation
3 - Automatic valuation based on inspection point definition
Level Name
1 Task List Header (manda

tory)
2 Material Task List Assign

ment (mandatory)
3 Inspection Characteristics
Tasks

Explorer.
Post-Processing
Transaction QP03 Display Inspection Plan
1.308 QM - Inspection plan

Purpose
Business Object Definition Description of the quality inspection process for materials in
a plant
In Scope
Internal/external number range for task list group is supported.
Out of Scope
● Assignment of test equipments to an inspection characteristic is not supported.
Supported Features
● Task List Header

● Operations
Prerequisites

● QM - Master inspection characteristic [page 992]

normally cause an error message during the creation or migration of the successor object. To avoid error
messages and inconsistent data on your database, make sure you check any such time dependencies before
you create or migrate your objects.
Flow Variants for Inspection Point Completion. The possible values are:
Blank - Quantity, valuation and confirmation (production)
1 - Quantity, valuation (production)
2 - Valuation
3 - Automatic valuation based on insp. point definition
Number Range Control Indicator

This is an indicator field, which determines whether the number range for the task list groups is internal or
external.
Please enter X if it’s internal, leave the field empty if it’s external.
Level Name
1 Task List Group (man

datory)
2 General Data (manda

tory)
3 Material Assignment
4 Operations
5 Characteristics
Tasks

Explorer.

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

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

Explorer.
Post-Processing
Transaction MM03 Display Material
Choose Quality Management Insp.setup .

Purpose
Business Object Component/Area Controlling (CO)

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

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

9A0000000000 to 9AZZZZZZZZZZ.
In Scope
Out of Scope
● Settlement Rules: The used API can only create new settlement rules. A reuse of existing rules is not
possible.
Supported Features
● Master data
● Create new settlement rules
Prerequisites
The following objects must already have been maintained or migrated:

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

Explorer.
Post-Processing
Transaction KO03 Display Internal Order
1.311 Material inventory balance

Purpose
Business Object Component/Area Inventory Management (MM-IM)
In Scope
1. Material document header

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

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

○ ‘K’ - Vendor consignment
○ ‘W’ - Customer consignment
○ ‘V’ - Returnable packaging with customer
○ ‘O’ - Parts provided to vendor
○ ‘E’ - Orders on hand
○ ‘Q’ - Project Stock
 Note
For Vendor consignment stock, please provide special stock indicator ‘K’ and the vendor.
For Customer consignment stock, please provide special stock indicator ‘W’and the customer.
For Returnable packaging stock, please provide special stock indicator ‘V’ and the customer.
For Parts provided to vendor stock, please provide special stock indicator ‘O’ and the vendor.
For Orders on hand, please provide special stock indicator ‘E’ and the sales order with the corresponding
item
For Project stock, please provide special stock indicator ‘Q’ and the WBS element
For Materials which are serial managed, please provide for each serial number one item with quantity 1.

For Materials which are batch managed, please provide the corresponding batch. If the batch doesn't exist
the system will create it within the goods movement posting.
Out of Scope
1. The following types of transactions/events are not supported:

○ GM_Code 01: Goods receipt for purchase order.
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

○ 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)
● Product [page 1021]: 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 unique at material and client level [page 783] (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 1107]/Customer [page 846] (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)
● MM - Purchasing info record with conditions [page 1038] with info category Consignment (only relevant for
vendor consignment stock)
General Information
You can use the Technical Item Number field on the Material Document Item sheet itself to determine the
numbers of items posted according to the unique identifier entered on the Material Document Header sheet.
SAP recommends that you structure the document with a maximum of 1000 records per document.
 Note
The Technical Item Number field on the Material Document Item sheet and the Technical Document Number
on the Material Document Header sheet are not mapped to a target field.
Mapping of the Batch Number field on the Material Document Item sheet
You want to post stock for a material that is defined by its valuation category as a material valuated in single
batches. In this case you have to provide a valid batch. The valuation category must be assigned in the batch
itself.

Mapping of the External Amount in Local Currency field on the Material Document Item sheet
The valuation of the stocks to be entered depends on two factors:
● The price and type of price control defined in the accounting data of the material master record
● Whether or not you provide a value for the quantity entered:
For a material valuated at a standard price, the initial entry of inventory data is valuated on the basis of the
standard price. If you provide an alternative value in the External Amount in Local Currency field, the
system posts the difference to a price difference account.
For a material valuated at moving average price, the initial entry of inventory data is valuated as follows:
○ If you enter a value when entering initial data, the quantity entered is valuated at this price. If the
quotient of the value and the quantity of the initial data differs from the moving average price, the
moving average price changes when initial data is entered.
○ If you do not enter a value when entering initial data, the quantity entered is valuated at the moving
average price. In this case, the moving average price does not change.
Level Name
1 Material Document Header (manda

tory)
2 Material Document Item (mandatory)
Tasks

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

Further Information
● SAP Knowledge Base Article 2813720 – SAP S/4HANA Migration cockpit: Collective KBA for migration
object "Material inventory balance"
1.312 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 935]

● 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

Level Name
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
Transaction GJAA Maintain Joint Operating Agreement
1.313 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
Transaction GJ2B
1.314 JVA - Cost center suspense

Purpose
Business Object Definition If a partner, or equity group or cost object is suspended, cut
Suspense:
When you place an object in Suspense, all summary records

cutback.
Unsuspense:

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 944]
Level Name
1 JV Cost center in Suspense
Tasks

Explorer.
Post-Processing
Transaction GJ_SUS_CC Suspend Cost Centers

1.315 JVA - Venture suspense
Purpose
Suspense:

cutback.
Unsuspense:

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
Transaction GJ_SUS_VE Suspend Ventures
1.316 JVA - Project suspense
Purpose
Suspense:

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
Transaction GJ34 Suspend Projects
1.317 JVA - Joint venture master data
Purpose

accounting records in their own financial books. The opera
tor remits venture expenses, collects revenues, and distrib
utes 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
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 935]

● JVA - Joint operating agreement [page 933]

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

Purpose
Business Object Component/Area Cost center (CO)
A cost center can be defined in various time intervals.
In Scope
Out of Scope
You can only migrate cost centers if the controlling area that is assigned to the cost center is not configured to
use ALE distribution.
Supported Features
● Main Data
● Basic Data
● Control
● Organizational Units
● Budget Availability Control
● Address
● Communication
● Joint venture

Prerequisites

Parallel Processing of Cost Centers

Cost centers cannot be processed in parallel, since the hierarchy is locked when inserting a cost center. Thus,
either migrate cost centers within a single file or migrate multiple files sequentially (not in parallel).
Level Name
1 Cost center master data (mandatory)
Language in Which Text is Saved

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

If Vertex is activated (especially on US installations) the tax jurisdiction code will be determined by the address.
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
Transaction KS03 Display Cost Center
1.319 Legal transaction
Purpose
Business Object Component/Area Legal Content Management (LCM)
Business Object Definition Business object that is used to manage the lifecycle of legal
content as part of a business transaction or a business sce
nario.
A legal transaction collects the involved parties and impor

tant dates, it groups the assigned documents and organizes
the tasks.

In Scope
1. Header Data
2. Entity Data
3. Internal Contact Data
4. External Contact Data
5. Linked Objects Data
6. Renewal and Termination Data
7. Relationship Data
8. Date Data
9. Categories Data
Out of Scope
1. Task Group Templates

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

Level Name
2 Entity
2 Internal Contact
2 External Contact
2 Linked Objects
2 Renewal and Termination
2 Relationship
2 Date
2 Categories

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

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

Explorer.

Post-Processing
App: Manage Legal Transactions
Choose Legal Transaction.
Business Role: Legal Counsel (SAP_BR_LEGAL_COUNSEL)
Further Information
For information regarding the used API see SAP Note 1348099 .
1.320 Material listing and exclusion
Purpose
Business Object Component/Area Material Listing/Exclusion (SD-MD-MM-LIS)
Business Object Definition Condition record for material (that is, product) listing or ex
clusion, which controls what material a customer can or can
not buy. Each condition record stores a condition that ap
plies during listing and exclusion determination in sales
documents.

Supported Features
● This migration object supports the condition keys listed in the Supported Key Fields for Listing and
Exclusion Conditions file.
Prerequisites
The objects (for example, Product [page 1021] and Customer [page 846]) that map to the key fields in your
condition records must have been maintained or migrated.
Level Name
1 Listing/Exclusion condition header

(mandatory)
2 Listing/Exclusion condition keys (man

datory)
Tasks

Explorer.
Post-Processing
Transaction VB03 Display Listing/Exclusion

Further Information
● This migration object supports the condition keys listed in the Supported Key Fields for Listing and
Exclusion Conditions file.
Purpose
Business Object Component/Area Activity types (CO)
Example: Activity types in production cost centers are ma

chine hours or finished units
In Scope
Supported Features
● Basic Data
● Indicator
● Output

Prerequisites
If you set the TESTRUN flag, the migration will be simulated but no data will be posted to the system.
Level Name
1 Activity master data (mandatory)
Tasks

Explorer.
Post-Processing
Transaction KL03 Display Activity Type
1.322 PM - Maintenance item

Purpose
Business Object Component/Area Maintenance Item (PM)
Business Object Definition A description of the maintenance and inspection tasks re
quired at regular intervals for maintenance objects.
In Scope
Out of Scope
1. Data transfer for settlement rule of maintenance plan item

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

● Cost element
● PM - General maintenance task list [page 902]
● PM - Equipment task list [page 883]
● PM - Functional location task list [page 895]

Maintenance Item Number

The Maintenance Item Number will be generated by the system during creation. The Maintenance Item Number
will not be stored. It is only necessary for technical reasons. Every record must have a unique key.
Level Name
1 Maintenance Item (mandatory)
Tasks

Explorer.
Post-Processing
Transaction IP06 Display Maintenance Item
1.323 PM - Maintenance plan
 Tip

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 is taken from the Reference object, where it exists.
Supported Features
● Maintenance Plan
● Maintenance Item

Prerequisites

● PM - Equipment task list [page 883]
● PM - Functional location task list [page 895]
● PM - General maintenance task list [page 902]
● PM - Measuring point [page 866] (performance-based maintenance plan)
● PM - Measurement document [page 864] (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 STRAT field (blank or filled).
Level Name
1 Maintenance Plan Data (mandatory)
2 Maintenance Item Data (mandatory)
Tasks

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

1.324 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
1.325 Material - Forecast planning
 Restriction
● To migrate material consumptions, please use the new Product consumption [page 1013] migration
object.

Purpose
Business Object Component/Area Material Master (LO-MD)
In Scope
● Migration of Forecast Values
Supported Features
● Forecast values
Only values that correspond to the current validity period of the product are taken into account. Values that
are not in the validity period will be ignored.
 Note
The system sets the Fixing indicator automatically.
Prerequisites
Restrictions
You can migrate several organization levels for a specific material with one migration template belonging to a
specific project.

Tasks

Explorer.
Post-Processing
After migration execute the forecast.
Choose Forecast view Forecast values .
1.326 Material- extend exist record by new org levels (deprecated)
 Caution
This migration object is deprecated. Until its final removal, it is solely available for compatibility reasons.
Purpose
Business Object Definition Logistics Basic Data (LO-MD)
The total of all material master records.
A company manages the data for all its materials in the ma
terial master.

In Scope
 Note
With this migration object, you can extend existing materials by new organizational levels (for example,
plant, sales organization, or storage location).
A material view, such as Accounting or Costing, contains fields of different organizational levels (for
example, basic, plant, or accounting data). Therefore, we do not recommended enhancing a material by a
different material view.
1. Extend already existing materials with new organizational levels

2. Basic data (only fields that 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
928] migration object, because the system will calculate the values of the stock posting with the price
data provided in the material master (only relevant if you do not use the external amount field during
the migration of inventory balances).
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, tax category, and tax classification. If you have more than
one tax category for a country, please use theTax category 2/Tax classification 2 fields. 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. Changing existing data
Supported Features
● Basic Data
● Plant Data
● Storage Location Data
● Accounting Data
● Sales Data
● Description Data
● Unit of Measure Data
● Tax Classification Data
● Warehouse Number Data
● Storage Type Data
● Production Resource Tool (PRT)
● Forecast Parameters
Prerequisites

Basic Data
On the Basic Data sheet, we only offer fields that 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 (such as the purchasing group). In this case, it might also become necessary to fill in the Order
Unit field on the Basic Data sheet.
 Note
If a field already has a value in the related material master, you cannot add a value in the corresponding
field on the Basic Data sheet. You are not allowed to change existing values on the material master. Instead,
you can use the Manage Mass Maintenance - Products app. For more information, refer to the online
documentation of the Manage Mass Maintenance – Products app.

Batch Management Requirement Indicator
If you want to migrate a new plant that is batch managed for a material that is currently not defined for batch
management on material level, you have to set the Batch management requirement indicator on the Basic Data
sheet and the Batch management requirement indicator on the Plant Data sheet.
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. You are not allowed to change existing values for an
existing plant. If you provide other values on the Plant Data sheet, an error message is displayed.
Recommendation on how to handle cross-plant material status and plant-specific material

status
If you set the material status while loading the materials after the initial data migration, please be aware that
the status settings may mean that posting follow-on migration objects leads to an error.
For example, in the SAP standard delivery, material status 01 is configured in such a way that an error message
is triggered while posting the inventory. 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 do not run into
follow-on problems during the data migration process. You can 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 more 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 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 of each valuation type, you can choose between moving average price or standard
price.
Split Valuation
Split valuation enables you to valuate stocks of material in the same valuation area in different ways. If you use
split valuation for your material, you have to define a valuation header record with a specified valuation
category, initial valuation type, and a dependent record for each valuation type.
For example:
A001 1010 H (Origin)
A001 1010 Domestic H (Origin)
A001 1010 Foreign H (Origin)
Level Name
1 Basic Data (mandatory)
2 Plant Data
3 Storage Location Data
3 Forecast Parameters
3 Production Resource Data
2 Warehouse Number Data
3 Storage Type Data
2 Accounting Data
2 Sales Data
2 Material Descriptions
2 Alternative Units of Measure
2 Tax Classification
1 Settings Maintenance Status
Maintenance Status Settings

Just like the organization-dependent data, the material master data is also organized into views (Purchasing
view , 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 view, whereas the letter E is assigned to the Purchasing view. There are two different
methods of defining the maintenance status that should be available for the specific material that you want to
extend:
1. The system detects automatically the maintenance status of the fields that are 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 is followed for all mapped fields, after which a combined
maintenance status of all fields will be available, for example: BELV.
2. To define the views to be created, you use the Maintenance Status Settings sheet of your migration object
template. In the Material Views field, you define a name for your view definition. For example, you enter
PLANT_HAWA to define the maintenance status of the plantspecific data for materials of this type that you
want to extend. For each view that you want to create, you must enter x in the specific Material Views
column of that sheet, for example: PLANT_HAWA
○ Sales Data = X
○ Purchasing Data = X
○ MRP Data = X
○ Storage Data =X
○ Accounting Data = X
You enter PLANT_HAWA in the Material Views field on the Plant Data sheet for all trading goods materials of
type HAWA that 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 sheet. 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 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 the
view to be created.
● You want to have the Storage Location view created automatically for a material and its storage location
by migrating its inventory stock.
Solution: You need to set the maintenance status explicitly 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 971] migration object to migrate
material-related long texts.
You can use the Material - Forecast planning [page 961] migration object to migrate material consumptions and
forecast values (only supported for on premise).
App: Manage Mass Maintenance – Products (App ID F2505)
Transaction MM50 Material List
1.327 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.328 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 based on the text object, text name, text ID, and
language 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 de
fines 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
● Material long texts:

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

● MRP Long Text
● Sales Long Text
Prerequisites

RUN ID
On the Product sheet, you find an additional key field, RUN ID. This field is a counter that you can use to execute
several enhancements for the same instance. You cannot import the same source record more than once in the
same project. The RUN ID field is an additional key field to which you can import the same product more than
once.
For example, in the first import product "A" with a new product long text or sales long text, and in the second
step the same product "A" with another product long text or sales long text.
same instance.
Level Name
1 Material (mandatory)
2 Material long text
2 MRP long text
2 Sales long text
Tasks

Explorer.
Post-Processing

1.329 VC - Material variant
Purpose
Business Object Component/Area Variant Configuration (LO-VC)
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. Class type variants (300) is supported.

2. 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 - General template [page 807]
● VC - Configuration profile [page 826]
Level Name
2 Characteristic Valuation
Tasks

Explorer.
Post-Processing
Not available.
1.330 SD - 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)
For more information, see the field description in the template file.

Tasks

Explorer.
Post-Processing
Transaction VB11 Create Material Substitution
Transaction VB12 Change Material Substitution
Transaction VB13 Display Material Substitution
1.331 Material (deprecated)
 Caution
This migration object is deprecated. Until its final removal, it is solely available for compatibility reasons.
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 exist record by new org levels (deprecated) [page 963] 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. As the valuation values continue to change until the cutover,
they should be migrated shortly before going 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
928] migration object. This is because the system calculates the values of the stock posting with the
price data provided in the material master (only relevant if you don't use the external amount field
during migration of the inventory balances).
In the case of Single Batch Valuation, please follow the mapping instructions provided.
7. Sales Data
8. Description Data
In this view, you can maintain additional descriptions (for languages other than those provided on the Basic
Data sheet).
9. Units of Measure Data
In this view, you can enter Alternative Units of Measure (provide only the Base Unit of Measure on the Basic
Data sheet).
10. Tax Classifications
In this view, you can maintain the Tax data (from Sales Org Data 1) and the Tax indicator for material
(Purchasing).
For Tax Data (Sales), provide the country, the tax category, and the tax classification. If you have more than
one tax category for a country, use the Tax category 2/Tax classification 2 fields and, further on, the Tax
classification sheet to provide the additional tax data.
For Tax indicator for material (Purchasing), enter the value in the Tax indicator for material field on the Tax
classification sheet for the country relating to your plant.
11. Maintenance Status Settings (maintain the views for your materials).
For more details, see the Maintenance Status Settings section under Mapping Instructions below.
12. Warehouse Number Data
13. Storage Type Data
14. Production Resource Tool (PRT) Fields in the Material Master
15. Data Transfer for Forecast Values
16. Data for Quality Management

17. Additional EANs
Out of Scope
1. Internal numbering is not supported.

2. Material long text (therefore, use the Material - extend existing record with long text [page 971] 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 existing material, use the Material- extend exist record by new org levels
(deprecated) [page 963] migration object.
 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 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
● Production Resource Tool (PRT)

● Forecast Parameters
Prerequisites

● Supplier [page 1107] (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 that is longer than the set defined length.
● 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. This is 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.

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, on the Basic Data sheet of the migration template, under Multiple View
Data, set the Batch management requirement indicator. 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. Posting may lead to an error depending on the
status settings.

Example: In SAP standard delivery, the material status 01 is configured in such a way that you will receive an
error message during posting of inventory. Consider that by assigning this status, the use of the material can
follow-on postings. Therefore, SAP recommends that you consider this field carefully so that you do not run
into follow-on problems during the data migration process. You can set the content of these fields after the
initial data migration by 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:
 Note
For the valuation header record, only price control V - moving average price is possible. For the dependent
records for each valuation type, you can choose between moving average price or standard price.

Split Valuation
Split valuation enables you to valuate stocks of material in the same valuation area, in different ways. If you use
the split valuation for your material, you have to enter the valuation records as outlined below.
Define a valuation header record with a specified valuation category and an initial valuation type as well as a
dependent record for each valuation type.
For example:
Level Name
2 Plant Data
3 Storage Location Data
3 Forecast Parameters
3 Production Resource Data
3 Storage Type Data
2 Accounting Data
2 Sales Data
2 Additional EANs
1 Maintenance Status Settings
Maintenance Status Settings

As well as the organizational-dependent data, the material master data is also organized using 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 the letter K assigned. A
combination of letters that represents the available views for a specific material is stored in a field called
Maintenance Status. In the Administrative Data field group of the migration object template, the maintenance
status can be defined differently for the following sheets :
● 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 can define the views to be created by using the Maintenance Status Settings sheet/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 trading goods type
(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 X in the specific Material Views column of that sheet/
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
○ Then you fill the Material Views field on the Basic Data sheet/tab with BASIC_HAWA for all trading
goods materials of type HAWA. You also fill the Material Views field on the Plant Data sheet/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
Maintenance Status field (PSTAT) of the SAP ERP source table. In this case, it is not necessary to maintain
both the Maintenance Status Settings sheet/tab and the Material Views source field.
○ Material Maintenance Status field on the Basic Data sheet/tab.
○ Plant Maintenance Status on the Plant Data sheet/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 sheet/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 have the Storage Location view created automatically for a material and its storage location by
migrating its inventory stock.
Solution: You need to set the maintenance status explicitly 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 971] 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 960] migration object to migrate product
classification with commodity code.
Further Information
● SAP Knowledge Base Article 2811788 – SAP S/4HANA Migration cockpit: Collective KBA for migration
object Material
1.332 Xceptional case -Mat price chng for global curr (deprecated)
 Caution
This migration object isn’t available anymore as of release SAP S/4HANA 2020.
Be aware that the following documentation for this migration object only reflects the status of release SAP
S/4HANA 1909.
To migrate material ledger prices, use the Product [page 1021] migration object. For mass changes, use the
Upload Material Inventory Prices app.
Purpose
Business Object Component/Area Actual Costing/Material Ledger (CO-PC-ACT)

Business Object Definition During migration of material master, the system creates 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 cur
rent exchange rate defined in the system. If this isn’t 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’s 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 isn’t supported for Cloud
Supported Features
● Material
● Valuation Area
● Valuation Type
● Price Data
● Prices

Prerequisites

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

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

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

Explorer.

Post-Processing
Transaction FF65 List of Cash Management Memo Records
1.334 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 824] migration object.
 Restriction
You can use this migration object only for migration in the context of SAP Best Practices.
Purpose
Business Object Component/Area Condition record for pricing in purchasing.

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

In Scope
The following price conditions are supported:
1. Prices for application M - Purchasing (including scales)
Out of Scope
1. Sales conditions (see migration object Condition record for pricing in sales (restricted) [page 1057])
Supported Features
● This migration object supports only 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 824]
migration object.
● This migration object is used to migrate pricing conditions. If you want to migrate purchasing info records
with conditions, use the MM - Purchasing info record with conditions [page 1038] migration object.
Prerequisites

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

Tasks

Explorer.
Post-Processing
Transaction MEK3 Display Conditions (Purchasing)
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
● This migration object supports only the condition types and key combinations mentioned in the Supported

1.335 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
doesn’t necessarily have to be the case.
In Scope
This migration object does only support external number ranges.
Out of Scope
This migration object doesn’t support internal number ranges.
Supported Features
● General Data
● Characteristic Control Indicators
● Assign Inspection Methods
● Assign Inspection Catalogs
● Long Texts

Prerequisites

Allowed Number Range for Keys (Master Inspection Characteristic)
The migration object only supports the data migration of keys using the external number range. The key you
want to migrate must be from an external number range.
If you’re migrating keys that are within the internal number range, you have to manually adjust the Number
Range Status (NRLEVEL) after the migration is finished. The Number Range Status contains the last assigned
number for the internal number range intervals.
Level Name
1 Master Insp. Char. Basic Data (manda

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

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

tory)
2 Master Insp. Char. Long Texts

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

Explorer.
Post-Processing
Transaction QS21 Create master insp. characteristic
Transaction QS22 Create Master Insp. Charc Version
Transaction QS23 Change master insp. charac. version
Transaction QS24 Display master insp. charac. version
1.336 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

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

Level Name
2 Additional Reference text
Tasks

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

(SAP_BR_MD_SPECIALIST_JIT)
1.337 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 998]
Level Name
1 Package Specification Detail (manda

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

Explorer.

Post-Processing
Business Role: SAP_BR_MD_SPECIALIST_JIT
App: Manage Packing Specifications for Sequenced JIT Calls
1.338 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

2. Migration of Tolerance
3. Migration of Supply Control Description
4. Migration of Offset

Supported Features
● Basic Data
● Tolerance
● Supply Control Description
● Offset
Prerequisites
● JIT - Customer [page 994]
Level Name
2 Tolerance
2 Supply Control Description (manda

tory)
2 Offset
Tasks

Explorer.

Post-Processing
Business Role SAP_BR_MD_SPECIALIST_JIT
App Manage JIT Customer Supply Controls
1.339 FI - Accounts payable open item (restricted)
 Restriction

● group currency
 Tip
Purpose

Business Object Definition Open items are those items that aren’t yet cleared.
This document describes how to load the Accounts Payable

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

2. External accounting document number.
3. Open tax items / VAT line items (must be settled before data migration. Exception: deferred tax).
SAP Note 2911854 – SAP S/4HANA Migration Cockpit: Migration of VAT line items is not supported
4. Calculate tax automatically.
5. Bill of exchange: The mass migration of accounts payable open items with the special G/L indicator
referring to the special G/L type 'W'. This data must be posted manually in financial accounting.
6. Special G/L indicator leading to the noted item.
7. Down payment and down payment request.
8. Migration of open items with tax attributes from a country/region different from the company code
country/region.
Supported Features
● Header
● Supplier Item
● One-Time Account Data
● Tax Item (only for deferred tax)
● Withholding Tax Item
● Currency Item
● Countryspecific (IT, RU, KR, MX, SK)

Prerequisites
○ In Preparation: The migration key date is still unclear. Migration of transactional data isn’t possible.
○ Ongoing: Required for the initial data transfer. Migration of transactional data is possible.
○ Completed: After finishing the initial data transfer, migration of transactional data isn’t possible.

Note that posting on tax jurisdiction is automatically derived by profit center. Therefore, the tax jurisdiction
code must be already maintained for the profit center master.
system):
For automatic document splitting, the default profit center is defined as YB900 in S/4HANA Cloud. If no profit
center is provided via migration template, the default profit center is chosen automatically.
There are 2 approaches to use the default profit center:
1. Create YB900 as profit center master data to use the already defined default profit center
2. To use your own default profit center, create a new profit center or choose an existing one as your default
profit center. Use the SSC-UI 120100 Edit Constant for Nonassigned Processes to replace YB900 with
your own default profit center.
More information can be found in the road map viewer: https://go.support.sap.com/roadmapviewer/#/group//

roadmap/IMPS4HANACLDENMGMT/node/901B0E6D3F501ED788F20B5936A6DF96:
Dependencies
This is the recommended approach for the initial migration of financial data:
Please remember that no documents will be migrated. Only balances and open items are taken over.
accounts in the source system. By reducing these open items, you reduce the number of variables. This means
a lower chance of errors as well as reducing the amount of reconciliation needed to verify the data migration.
Only the balance needs to be migrated from the bank account.
No items and balances need to be migrated from tax accounts because its usually zero (for normal VATs) when
the migration takes place. We assume that the tax transfer has already taken place. 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 in the migration file. The offsetting entry is generated automatically
for the offsetting G/L account.
● The combination of the key fields Company Code + Reference Document Number + Line Item Number +
Supplier Number are used to check for duplicates. Data records with this combination should be unique in
the migration template. Otherwise, the migration tool displays a duplicate error message. The Line Item
Number is used as an additional key field and isn’t migrated.
● Please make sure to fill and save the value amounts in the migration file as numbers and not in a 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 G/L
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 uses posting key 31 (Invoice) for supplier and 40 (Debit entry) for Offsetting G/L
Account (only without special G/L indicator).
○ A positive value uses posting key 21 (Credit memo) for supplier and 50 (Credit entry) for Offsetting
G/L Accounts (only without the special G/L indicator).
 Note
During the migration of credit memo line items, the Invoice Reference field is automatically set to
'V' by the BAPI. This is hard-coded and can’t 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 :
○ 39916000 (Initial other G/L offset)
○ 39917000 (Initial other Open Item G/L offset)
One-Time Accounts (CPD)
To migrate data for one-time account customers/supplier (CPD), you need to maintain the data for this one-
time account in the sheet/table One-Time Account Data.
Deferred Tax
For posting of an invoice with deferred taxes, you need 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 customer item. Tax
amounts and tax base amounts must have the same sign. It's important that the sign doesn't differ.
If there is at least one deferred tax code in an invoice, then full tax information including nondeferred taxes
should be provided in the migration template. This is necessary for a correct proportion calculation.

Two approaches for currency and amount
Provide all relevant currencies and related amounts via the template. In doing this, the provided values are
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 is automatically calculated by valid exchange rates in the system.
The exchange rate is determined using the provided document or posting date. That date that is used is
defined in Customizing for each company code (in SPRO via Change Foreign Currency Translation).
Payment Term / Payment block
If a default payment block is assigned to a payment term, then the open item is blocked accordingly. This also
happens if the value for a payment block isn’t 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
To use this field, you need to predefine this Customizing activity: Financial Accounting Accounts Receivable
and Accounts Payable Business Transactions Posting with Alternative Reconciliation Account Define
Alternative Reconciliation Accounts .
Level Name
2 One-Time Account Data
2 Deferred Tax Items
2 Withholding Tax Items
2 Italy Specific
2 Russia Specific
2 Mexico Specific
2 Slovakia Specific
Tasks

Explorer.

Post-Processing
The total balance of all migration clearing accounts 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
(restricted) [page 909] migration object.
 Note
For Deferred Tax:
● Check entries in the DEFTAX_ITEM table

● Program RFUMSV50 for deferred tax transfer
Further Information
1.340 FI - Accounts receivable open item (restricted)
 Restriction

● group currency

 Tip
Purpose
Business Object Definition Open items are items that aren’t yet 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 invoices, debit memos, and credit memos are supported.
Out of Scope
1. Multiple customer line items per document post.

2. External accounting document number.
3. Open tax items / VAT line items (must be settled before data migration. Exception: Deferred tax).
SAP Note 2911854 – SAP S/4HANA Migration Cockpit: Migration of VAT line items is not supported
4. Calculate tax automatically.
5. Bill of exchange: The mass migration of accounts receivable open items with the special G/L indicator
referring to the special G/L type 'W'. This data must be posted manually in financial accounting.
6. Special G/L indicator leading to the noted item.
7. Down payment and down payment request.
8. Migration of open items with tax attributes from a country/region different from the company code
country/region.

Supported Features
● Header
● Customer Item
● One-Time Account Data
● Deferred Tax Item (only deferred taxes allowed)
● Withholding Tax Item
● Currency Item
● Countryspecific (IT, RU, KR, MX, SK)
Prerequisites
○ In Preparation: Migration key date is still unclear (Migration of transactional data isn’t possible)
○ Ongoing: Required for the initial data transfer (Migration of transactional data is possible)
○ Completed: After finishing the initial data transfer, migration of transactional data isn’t possible.

Posting on tax jurisdiction is automatically derived by the profit center. That's why the tax jurisdiction code
must already be maintained for the profit center master.
system):
For automatic document splitting, the default profit center is defined as YB900 in S/4HANA Cloud. If no profit
center is provided via migration template, the default profit center is chosen automatically.
There are 2 approaches to use the default profit center:
1. Create YB900 as profit center master data to use the already defined default profit center.
2. To use your own default profit center, create a new profit center or choose an existing one as your default
profit center. Use the SSC-UI 120100 Edit Constant for Nonassigned Processes to replace 'YB900' with
your own default profit center.

For more information, see the road map viewer: https://go.support.sap.com/roadmapviewer/#/group//
roadmap/IMPS4HANACLDENMGMT/node/901B0E6D3F501ED788F20B5936A6DF96:
Dependencies
Recommended approach for the initial migration of financial data:
Please keep in mind that no documents will be migrated. Only balances and open items are taken over.
accounts in the source system. By reducing these open items, you’ll reduce the number of variables resulting in
a lower possibility of error as well as reducing the amount of reconciliation needed to verify the data migration.
Only the balance needs to be migrated from the bank account.
No items and balances need to be migrated from the tax accounts because they’re usually at balance zero (for
normal VATs) when the migration takes place. We assume that the tax transfer has already taken place.
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 in the migration file. The offsetting entry is generated automatically
for the offsetting G/L account.
● The combination of key fields Company Code + Reference Document Number + Line Item Number +
Customer Number is used to check for duplicates. Data records with this combination should be unique in
the migration template. Otherwise, the migration tool displays a duplicate error message. The Line Item
Number is used as an additional key field and isn’t migrated.
● Make sure you fill in and save the value amounts in the migration file as numbers and not as strings. Check
the settings for a delimiter.
For migration, the posting keys are always derived based on the account type and on the special G/L
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 uses posting key 11 (Credit memo) for customer and 40 (Debit entry) for Offsetting
G/L Account (only without special GL indicator).
○ A positive value uses posting key 01 (Invoice) for customer and 50 (Credit entry) for Offsetting G/L
Account (only without the special G/L indicator).
 Note
During migration of a credit memo line item, the Invoice Reference field is set to 'V' automatically
by the BAPI. This is hard-coded and can’t 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 :

○ 39916000 (Initial other G/L offset)
○ 39917000 (Initial other Open Item G/L offset)
One-Time Accounts (CPD)
To migrate data for one-time account customers (CPD), you need to maintain the data for this one-time
account in the sheet/table One-Time Account Data.
Deferred Tax
To post an invoice with deferred taxes it’s 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 customer item. Tax
amounts and tax base amounts must have the same sign. It's important that the sign doesn't differ.
If there is at least one deferred tax code in an invoice, then full tax information—including nondeferred taxes—
should be provided in the migration template. This is necessary for a correct proportion calculation.
Two approaches for currency and amount

Provide all relevant currencies and related amounts via the template. In doing this, the provided values are
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. The amount is
automatically calculated by valid exchange rates in system.
The exchange rate is determined using the provided document or posting date. The date that is used is defined
in Customizing for each company code (in SPRO via Change Foreign Currency Translation).
Payment Term / Payment block

If a default payment block is assigned to a payment term, then the open item is blocked accordingly. This also
happens if the value for a payment block isn’t 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
To use this field, the following IMG activity must be predefined: Financial Accounting Accounts Receivable
and Accounts Payable Business Transactions Posting with Alternative Reconciliation Account Define
Alternative Reconciliation Accounts .
Level Name
2 One-Time Account Data
2 Deferred Tax Items
2 Withholding Tax Items
2 Italy Specific
2 Russia Specific

Level Name
2 Mexico Specific
2 Slovakia Specific
Tasks

Explorer.
Post-Processing
The total balance of all migration clearing accounts 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
(restricted) [page 909] migration object.
 Note
For Deferred Tax:
● Check entries in table DEFTAX_ITEM

● Program RFUMSV50 for deferred tax transfer
Further Information

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

of internal control.
In Scope
Supported Features
● Basic Data
● Indicator
● Address Data
● Communication
● Company Codes
Prerequisites
● Groups for CO - Profit center

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

Tasks

Explorer.
Post-Processing
Transaction KE53 Display Profit Center
1.342 Product consumption
 Restriction
You can migrate several organization levels for a specific material with one migration template of a specific
project. If you have already migrated material consumptions (organization level view) and you want to
extend those materials by additional consumptions for the same plant but different periods, please create a
new project and use a new template. Additionally, follow the steps in the section Mapping Instructions to
load this data.
Purpose

In Scope
1. Migration of total consumptions

2. Migration of unplanned consumptions
Supported Features
● Material
● Total Consumptions
● Unplanned Consumptions
Prerequisites
● If the product is fresh, you can maintain the consumption value in the Consumption value field.
● If the product already has a consumption value, you have to use the Corrected consumption value field to
update the consumption value.
● The Ratio corr val to orig val field is always generated automatically.
Tasks

Explorer.

Post-Processing
Consumption values can also be accessed via Go To Additional Data Consumption .
1.343 Product - extend existing record by new org levels
Purpose
Business Object Component/Area Product Master (LO-MD)
The total of all product master records.
A company manages the data for all its products in the prod
uct master.
In Scope
 Note
With this migration object, you can extend an existing product by new organizational levels (for example
plants, valuation areas, distribution chains, or storage locations). An update or enhancement of existing
organizational levels isn’t supported.
You can also maintain new descriptions, new units of measure and new GTINs.
1. Extend an existing product with new organizational levels

2. Basic data (only fields that might become relevant when you migrate new organizational units)
3. Additional Descriptions

4. Additional Units of Measure
5. Additional GTINs
6. Distribution Chains
7. Tax Classification
You can enter the sales tax data corresponding to your sales organization in the manage product master
data app under Distribution Chain Sales Tax .
For tax classification data, please provide the country, the tax category, and the tax classification. If you’ve
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 product (Purchasing), please enter the value in the Tax Indicator field on the Plant
Data sheet.
8. Plant Data
9. Forecasting Data
10. Storage Locations
11. Production Resources Tools
12. MRP Areas
15. Valuation Data (including Valuation Current Period Data and Valuation Future Price Data)
 Note
928] migration object. If you don’t use the external amount during the initial loading of stock, the
system calculates the values of the stock posting with the price data provided in the product master.
Out of Scope
You aren’t allowed to enrich existing organizational levels with new data. No updates of existing fields/records
are possible.
1. Product long text (you can use the Material - extend existing record with long text [page 971] migration
object to migrate product-related long texts)
3. Data transfer for total consumption of product
4. Change already existing data
Supported Features
● Basic Data
● Additional Descriptions
● Alternative Units of Measure

● Additional GTIN's
● Distribution Chains
● Tax Classification
● Plant Data
● Forecasting Data
● Storage Locations
● Production Resources Tools
● MRP Area
● Valuation Data
● Valuation Current Period
● Valuation Future Price
Prerequisites
Basic Data
On the Basic Data sheet, we only offer fields that 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 (such as the purchasing group). In this case, it might also become necessary to fill in the Order
Unit field on the Basic Data sheet.
 Note
If a field already has a value in the related product master, you can’t add a value in the corresponding field
on the Basic Data sheet. You are not allowed to change existing values on the product master. Instead, you
can use the Manage Mass Maintenance - Products app. For more information, refer to the online
documentation of the Manage Mass Maintenance – Products app.
RUN ID
On the Basic Data sheet, you find an additional key field, RUN ID. This field is a counter that you can use to
execute several enhancements for the same instance. You cannot import the same source record more than
once in the same project. The RUN ID field is an additional key field to which you can import the same product
more than once.
For example, in the first step, import product "A" with a new plant view or sales area. In a second step, import
the same product "A" with another plant view or sales area.

same instance.
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. You aren’t allowed to change already existing values for
an existing plant. If you provide other values on the Plant Data sheet, an error message is displayed.
New Forecasting Parameter to an Existing Plant

If you want to migrate forecasting parameter to an existing plant, please provide only the key fields on the Plant
Data sheet and leave all the other fields blank. You are not allowed to change existing values for an existing
plant. If you provide other values on the Plant Data sheet, an error message is displayed.
New Production Resources Tools Data to an Existing Plant
If you want to migrate production resource tools data to an existing plant, please provide only the key fields on
the Plant Data sheet and leave all the other fields blank. You aren’t allowed to change existing values for an
existing plant. If you provide other values on the Plant Data sheet, an error message is displayed.
New Storage Type Data to Existing Warehouse Number Data
If you want to migrate storage type data to existing warehouse number data, please provide only the key fields
on the Warehouse Number Data sheet and leave all the other fields blank. You aren’t allowed to change existing
values for existing warehouse data. If you provide other values on the Warehouse Number Data sheet, an error
message is displayed.
Recommendation on how to Handle Cross-Plant Product Status and Plant-Specific Product

Status
If you set the product status, the settings of the status may mean that posting follow-on migration objects
leads to an error.
For example, in the SAP standard delivery, product status 01 is configured in such a way that, an error message
is triggered while posting the inventory. Consider that when you assign the status, the use of the product can
follow-on postings. Therefore, we recommend that you consider this field carefully so that you do 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. You can open the app
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 more information, refer to the online documentation of the Manage Mass Maintenance – Products app.

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. Please
provide this on the Valuation Data sheet in the Valuation Category field.
 Note
You need to manage the product itself in batches. Therefore, you have to provide the Batch management
If you use the single batch valuation for your product, 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.
Product Number Valuation Area Valuation Type Valuation Category
 Note
For the valuation header record only price control 'V' - moving average price is possible. For the dependent
Split Valuation
Split valuation enables you to valuate stocks of product in the same valuation area in different ways. If you use
the split valuation for your product, you have to enter the valuation records as follows:
You have to define a valuation header record with a specified valuation category and initial valuation type and
also a dependent record for each valuation type.
For example:
Product No. Valuation Area Valuation Type Valuation Category
Level Name
2 Additional Description
2 Additional GTINs
2 Distribution Chains

Level Name
2 Plant Data
3 Forecasting Data
3 Storage Locations
3 Production Resources Tools
2 MRP Area
3 Storage Type Data
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 971] migration object to migrate product-
related long texts.
You can use the Material - Forecast planning [page 961] migration object to migrate product consumptions and
forecast values (only supported for on premise).
App: Manage Mass Maintenance – Products (App ID F2505)
Transaction MM03 Display product
Transaction MM50 Product List
Further Information

1.344 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
928] migration object. If you don't provide the External Amount for loading the stocks, the system
calculates the values of the stock posting using the price data provided in the product master.
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).
10. Tax Classifications
In this view, you can maintain the Tax Data (from the Sales Org Data 1).

For Tax Data (Sales), provide the country, tax category, and tax classification. If you’ve more than one tax
category for a country, use the Tax category 2/Tax classification 2 fields. To provide additional tax data, use
the Tax Classification sheet further on.
 Note
For the tax indicator of the product (purchasing), on the Plant Data sheet for the country relating to
your plant, enter the value in the Tax Indicator field in the Purchasing group.
11. Production Resources Tools

14. Data Transfer for Forecast Values
15. Data for Quality Management
16. Additional EANs
17. 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 971] migration
object)
4. Data transfer for total consumption of material
5. Enhance already existing data
For the Product migration object, you must currently use the Product - extend existing record by new org
levels [page 1015] migration object. But note that this migration object doesn’t support all of the
organizational units that 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 Product - extend existing record
by new org levels [page 1015] migration object. Please bear this limitation in mind when using Product -
extend existing record by new org levels [page 1015] to enhance data migrated with the Product migration
object.
6. Classification data (therefore, use the Object classification - General template [page 807] migration
object)
7. Inspection types (therefore, use the Material inspection setup [page 925] migration object)
8. Product consumption (therefore, use Product consumption [page 1013] migration object)
 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. You can do this 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
● Additional Descriptions
● Alternative Unit of Measure
● Additional GTIN's
● Distribution Chains
● Tax Classification
● Plant Data
● Forecasting Data
● Storage Locations
● Production Resources Tools
● MRP Area
● Valuation Data
● Valuation Current Period
● Valuation Future Prices
Prerequisites

● Supplier [page 1107] (Manufacturer)
● Be aware of the defined length set for the product number in the system. Don’t convert a product number
to a new number that is longer than the defined length.
● During migration, you can choose between internal or external numbering. The standard setting is external
numbering.
● In the case of external numbering the system checks whether the provided product is within the number
range for the provided product type.

● If the Product ID is to be used for integration with external systems, it can be switched on during migration.
In this connection, you also have to maintain the Business System ID of your source system (to be used for
integration) in the Convert Values step. This ensures that the key mapping is added to the central key
Indicator Product is Configurable

Consider the following: If you are dealing with the KMAT - Configurable materials type, the system always sets
this indicator. In this case, the Item category is also set by default if you don’t support this on the migration
template. For KMAT materials, the procurement type is always 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.

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 this field, the system sets 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 aren’t 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 the initial load of products, do consider that, depending on which status
you want to assign, follow-on migration objects can't be posted. The posting may lead to an error depending on
the status settings.
Example: in SAP standard delivery, the product status 01 is configured in such a way that during posting of
inventory you’ll 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 won’t run into
follow-on problems during the data migration process. After the initial data migration, you can set the content
of these fields by 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 ways to migrate your valuation data. If you only provide your data on the
Valuation Data sheet, the system creates 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 then takes over this price and does 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. Depending on the current
exchange rate defined in the system, the system automatically determines the prices for all deviant
currencies:
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
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
A002 1010 30 USD 31.02 01.04.2020
Single Batch Valuation enables you to valuate product stocks for each batch in a different way. You can use it if
you want to keep the price and value of each individual batch in inventory management on a value basis.
To work with valuation for a single batch, you must choose valuation category X - for Automat. Batch. Provide
this on the Valuation Data sheet in the Valuation Category field.
 Note
The product itself needs to be managed in batches. In this case, 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, 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)

Inventory Inventory
Price Price
Product Valuation Valuation Valuation Cur Price Moving Standard
Number Area Type Category rency... Control ... Average Price ...
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
saying that the reference product does not exist and cannot be migrated. Please ensure that you migrate these
products in the right sequence. Another possibility is to leave the reference products empty during migration
and assign them afterwards using the Manage Mass Maintenance – Products app.
Level Name
2 Additional EANs
2 Distribution Chains

Level Name
2 Plant Data
3 Forecasting Data
3 Storage Locations
3 Production Resources Tools
2 MRP Area
3 Storage Type Data
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 971] 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 960] migration object to migrate product
classification with commodity code.
Further Information

1.345 Production version
Purpose
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

counter for assignment to routings
In Scope
Supported Features
● General Data
Prerequisites
● Product [page 1021] (with ERP data)


● Routing [page 1047]
Level Name
Task List Group

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

Explorer.
Post-Processing
Transaction C223 Maintain Production Versions

In MM03, choose MRP 4 View ProdVersions .
Further Information
In Discrete Manufacturing, it was not necessary to have a production version for BOM explosion in the SAP ERP
suite. In this case use the CS_BOM_PORDVER_MIGRATION02 report to create a production version based on
existing BOMs and routings in the new system.
1.346 PS - Network
Purpose
Business Object Component/Area PS
Business Object Definition A network can represent the sequence of activities in a

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

● Assignments
● Control
● Text
Prerequisites

● PS - WBS element [page 1116]
● SD - Sales order (only open SO) [page 1050]
Level Name
1 Network data (mandatory)
Tasks

Explorer.
Post-Processing
Transaction CN23 Display Network

1.347 PS - Project
Purpose
Business Object Definition Project definition is the general description of the project
that you want to manage. It is a framework laid down for all
the objects created within a project. It contains organiza
tional data that is binding for the entire project.
In Scope
Supported Features
● Basic Data
● Control
● Text
Prerequisites

Level Name
1 Project Definition (mandatory)
Tasks

Explorer.
Post-Processing
Transaction CJ08 Display Project Definition
1.348 MM - Purchasing info record- extend existing record
Purpose

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
○ Pipeline
○ For purchasing info records to material groups - only the standard and subcontracting purchasing info
categories are supported.
2. General Data (only legacy number of purchasing info record, material number, material group, and the
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 is 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 does not exist, it is 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

● MM - Purchasing info record with conditions [page 1038]
● 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 MM - Purchasing info record with conditions [page 1038] object.
● If you use the identical Legacy Number of purchasing info record in the objects MM - Purchasing info record
with conditions [page 1038] and MM - 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 MM - Purchasing info record with conditions [page 1038] object, the info record number is stored in the
migration mapping table. The MM - 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 MM - 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.
RUN ID
execute several enhancements for the same instance. You cannot import the same info record more than once
in the same project. The RUN ID field is an additional key field to which you can import the same product more
than once.
For example, in the first import purchasing info record "PIR_001" with a new purchasing organization or
purchasing info record category, in a second step the same purchasing info record "PIR_001" with another
purchasing organization or purchasing info record category.
same instance.

Level Name

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

Explorer.
Post-Processing
App: Mass Changes to Purchasing Info Records
Transaction ME13 Display Purchase Order Info Record
Transaction ME1L Info Records per Supplier
Further Information
SAP Knowledge Base Article 2776897 – SAP S/4HANA Migration Cockpit: Collective KBA Migration object
"Purchasing info record"/ "Purchasing info record- extend existing record"

1.349 MM - Purchasing info record with conditions
Purpose
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
○ Pipeline
○ For purchasing info records to material groups, only the standard and subcontracting purchasing info
categories are supported.
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

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

Explorer.

Post-Processing
App: Mass Changes to Purchasing Info Records
Transaction ME13 Display Purchase Order Info Record
Transaction ME1L Info Records per Supplier
Further Information
● SAP Knowledge Base Article 2776897 – SAP S/4HANA Migration Cockpit: Collective KBA Migration
object "Purchasing info record"/ "Purchasing info record- extend existing record"
1.350 MM - Purchase order (only open PO)
Purpose
Business Object Component/Area Purchase Order (MM-PUR)

 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.
○ If your ordered material is a BOM, the system automatically generates the subcontracting
components. You can also provide the components manually on the Components for
subcontracting sheet.
 Note
9. Item Texts
Out of Scope
1. Creating configurations (you can only use existing ones)

2. Changing message records (NAST table) and additional message data (this data can only be determined
via the message determination facility (Customizing))
3. Attaching 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 non-stock 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

● SD - Sales order (only open SO) [page 1050]
● MM - Purchase contract [page 830]
● WBS element
● Fixed asset (incl. balances and transactions) [page 889]
● FI - G/L account [page 907] (expense account used in account assignment category)
● MM - Purchasing info record with conditions [page 1038] (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.
● Note that during migration there is no defaulting of values from existing purchasing info records. However,
purchase order items with item category Consignment are an exception.
● Net Price: Please specify the price manually on item level. Migration of conditions for example, discounts or
surcharges, is not supported.
● The net price is automatically set to 0 if the invoice receipt indicator has not been set.
● If there is a Third-Party, please note that 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.

● The Delivery Date field on Item Data sheet is not relevant for materials with the type Service. In this case,
please fill in the Start Date for Period of Performance and End Date for Period of Performance fields.
Otherwise, the Delivery Date is filled with the system date.
Level Name
1 Header Data (manda

tory)
2 Header Address
2 Header Texts
2 Item Data (mandatory)
3 Item Address
3 Account Assignment
3 Schedule Line
4 Components for Sub

contracting
3 Item Texts
Tasks

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

Monitor for Vendor)

Further Information
● SAP Knowledge Base Article 2771859 - Purchase Order Migration Net price must be greater than 0
1.351 QM/PM - Catalog code group/code
Purpose
Business Object Component/Area Quality Management (QM and PM)

Business Object Definition Code group: A key for summarizing code and structuring a
catalog according to various criteria. The assignment of
code to code groups takes place at client level.
Catalog type: Main category by which code groups and co

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

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

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

2. Supported catalog types for PM are: 0, 2, 5, A, B, C, D
Out of Scope
1. Classification is not supported.

Supported Features
● QM/PM Catalog Code Group

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

(mandatory)

text (mandatory)

long text
2 QM/PM catalog code (man

datory)
3 QM/PM catalog code short

text (mandatory)
3 QM/PM catalog code long

text

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

Explorer.

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

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 922] migration object.
● For task list of type A (General Maintenance task list), use the PM - General maintenance task list [page
902] migration object.
● For task list of type E (Equipment Task List), use the PM - Equipment task list [page 883] migration
object.
● For task list of type T (Task List for Functional Location), use the PM - Functional location task list [page
895] migration object.

Out of Scope
Task list types other than those mentioned above aren't supported by the data migration content.
Supported Features
● Task List Header Data

● Sequences
● Operations
● Sub-Operations
● Component Assignment
● Production Resources/Tools
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.
Component Allocation
The BOM components will be assigned to the first operation by default when creating production order if you
have not manually assigned to any operation in the routing. This is the standard functionality.
Level Name
1 Routing group (mandatory)

Level Name
2 Task list header (mandatory)
2 Material task list assignment

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

Explorer.
Post-Processing
It's mandatory to migrate all routing in the Q system first and run a cost simulation run in your Q system. Then,
verify the results and check for inconsistencies before starting the data migration into the productive system.
After data migration into the productive system, It's mandatory to run the cost simulation and validation steps
in that system as well.
Transaction CA03 Display Routing
1.353 SD - 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
● You have to provide the Sold-to Party and Ship-to Party on the Header level in the Partner sheet using 0000
in the Sales Document Item field.
● The total number of ordered items is 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 . Please note that item numbers (Sales Document Item) will be migrated with external
numbering (the source ID in the template will be used). Please make sure to take this into account in case
of re-numbering of the items during the processing of the data (e.g. BOM explosion).
Level Name
2 Header Conditions (optional)
2 Item (mandatory)
3 Item Conditions (optional)
3 Item Texts (optional)
2 Partner (mandatory)
2 Schedule Line Data (manda

tory)
Tasks

Explorer.

Post-Processing
Transaction VA03 Display Sales Orders
Further Information
SAP Knowledge Base Article 2818627 – Migration Cockpit: Collective KBA for migration object Sales orders
(only open SO)
Purpose
Business Object Definition An outline agreement whereby materials are procured at a

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

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

2. Creation of delivery schedule
Supported Features
Prerequisites

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

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

1.355 Service order (only open SRVO)
Purpose
Business Object Component/Area CRM-SRV-SVO
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 at the header and item level
5. Service order conditions at the item level
6. Service order reference objects at the 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
● Employee master (via SAP SuccessFactors)

● Condition record for pricing (general template) [page 824]
● Only one Employee Responsible can be maintained for 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.
Level Name
2 Item Mandatory
3 Item Pricing Elements (optional)
3 Item Texts (optional)
3 Item Reference Objects (optional)
2 Header Reference Objects (optional)
2 Person Responsible (relevant for on-

premise only)

Tasks

Explorer.
Post-Processing
For on-premise related migration, validation of data can be done using the following apps:
App: ● Search Service Orders

● CRM Web UI
Business Role: ● Customer Service Manager

(SAP_BR_CUSTOMER_SRVC_MGR)
● Service Professional (S4C_SRV_PRO)
1.356 Condition record for pricing in sales (restricted)
 Restriction
This migration object only supports the condition types and key combinations mentioned in the Supported
 Restriction
This migration object may only be used for migration in the context of SAP Best Practices.

Purpose
Business Object Component/Area Condition record for pricing in sales

data from the price conditions, for example, in Sales and Dis
tribution. Prices, surcharges, and discounts are determined
Business Object Definition The term pricing is used broadly to describe the calculation
In Scope
The following price conditions are supported (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
989])
Supported Features
● This migration object only supports the condition types and key combinations mentioned in the Supported
● For other key combinations, you must use the Condition record for pricing (general template) [page 824]
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, please refer to the Supported
Tasks

Explorer.
Post-Processing
Transaction VK13 Display Condition

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
● This migration object only supports the condition types and key combinations mentioned in the Supported
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
der to release products from the amount agreed in the con
tract. 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 aren’t supported.
Supported Features
The supported types of sales contract are value contracts and quantity contracts.
Prerequisites

● Condition record for pricing (general template) [page 824]
During migration, you can choose between internal and external number assignment for the sales contract
number. Please note that item numbers (Contract Document Item Number) will be migrated with external

numbering (the source ID in the template will be used). Please make sure to take this into account in case of re-
numbering of the items during the processing of the data (e.g. BOM explosion).
Level Name
1 Header Data (mandatory)
2 Additional Header Partners
2 Item (mandatory)
3 Item Partners
Tasks

Explorer.
Post-Processing
Transaction VA43 Display Contract
1.358 QM - Selected set
Purpose

Business Object Definition Selected Set/Select Set Code
Quality Management (QM)
A range of specific entries (code groups and codes) of a cat

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

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

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

Tasks

Explorer.
Post-Processing
Transaction QS51 Edit Selected Sets
Transaction QS52 Display selected set index
1.359 QM - Selected set code
Purpose
Business Object Definition Selected Set/ Selected Set Code
Quality Management (QM): A range of specific entries (code

groups and code) of a catalog. A selected set enables the
user to choose only those code groups and code of a catalog
that are required or allowed for a specific purpose.
In Scope

Supported Features
● Inspection Catalog Code for Selected Set
Prerequisites

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

Explorer.
Post-Processing
Transaction QS51 Edit Selected Sets
Transaction QS52 Display selected set index

1.360 FI - SEPA mandate
Purpose
Business Object Component/Area FI-AR, Financial Contract Accounting (FI-CAC)
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
Out of Scope
Applications for which mandates are relevant:
● A – CRM with ERP Contract Accounts A/R and A/P

● B – Bank Customer Accounts - Receiver Bank
● C – Bank Customer Accounts Sender Bank
● H – Payroll
● K – CRM with ERP Accounts Receivable
● P – Payment Request (Internal)

Supported Features
● SEPA Mandate Data
Prerequisites
● Bank [page 781]

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 tool tips field of the template file for further information.
Tasks

Explorer.

Post-Processing
To validate your migrated data, use the SEPA_MANDATE table in the SE16N transaction. To get results, enter the
value in the MNDID (Unique Reference to Mandate for each payee) field.
Transaction FSEPA_M1 Create SEPA Mandate
Transaction FSEPA_M2 Change SEPA Mandate
Transaction FSEPA_M3 Display SEPA Mandate
Purpose
Business Object Component/Area Source List (MM-PUR)
possible.
The source list lets you determine the source that is valid (ef
fective) at a certain time.
In Scope

Out of Scope
1. Stock transfer without a supplier account number.
Supported Features
● Purchasing Source List
Prerequisites

● Agreements
There are two types of outline purchase agreement:
○ MM - Purchase contract [page 830]
○ MM - Purchase scheduling agreement [page 1053]
If a successor object is created with a validity period starting before this object, it will normally cause an error
You therefore must check such time dependencies before you create or migrate your objects. This will avoid
Level Name
1 Purchasing Source List (mandatory)

Tasks

Explorer.
Post-Processing
Transaction ME03 Display Source List
1.362 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
1 General data (mandatory)
2 Company specific names
2 Conditions
Preparation of Migration Details for Company Substance

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

○ Internal Name
○ Listed Substance Name
○ CAS Number
○ EC Number
○ Molecular Formula
○ Responsible Unit
Tasks

Explorer.
1.363 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.364 TRM - Commercial paper
Purpose
Business Object Component/Area Transaction Manager (FIN-FSCM-TRM-TM)
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
2. Administration 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
Follow-on Activities
The function for the legacy data transfer are available in the Customizing of the Transaction Manager under
General Settings -> Tools -> Legacy Data Transfer:
● Enter Val.-Area-Dependent Data for Money Market, Forex, OTC Derivatives (transaction TPM63C)
● Execute Data Transfer (transaction TPM63)
● Reverse Data Transfer (transaction TPM64)
● Flag Flows as Posted (transaction TBB1_LC)
● Flag Flows as Reversed (transaction TBB3)
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.

1. Flag Flows as Posted (transaction TBB1_LC)
Use the Flag Flows as Posted Customizing activity to do this.
The flows are indicated as being posted but are not actually posted. A posting log is generated.
The Flag Flows as Reversed Customizing activity (transaction TBB3) is also available, if needed, to set the
flows as reversed.
2. Enter Val.-Area-Dependent Data for Money Market, Forex, OTC Derivatives
The remaining valuation-area-dependent position component values are entered in the Legacy Data table
using the Enter Val.-Area-Dependent Data for Money Market, Forex, OTC Derivatives Customizing
activity (transaction TPM63C). Alternatively, use the SAP S/4HANA Migration Cockpit app to enter the
position values (see the TRM - Position value [page 1095] 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 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 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.
3. Using the Execute Data Transfer Customizing activity (transaction TPM63), you enter the positions
component values in the Positions Management tables. Should errors occur, you can reverse the initial
load using the Reverse Data Transfer Customizing activity (transaction TPM64).
4. To check the values entered, you can display the positions component values with the Display Treasury
Position Values apps or with the Treasury Position Analysis app.
Transaction FTR_DISPLAY Transaction Display
1.365 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

2. Other flows 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
1 Structure Data (mandatory)
2 Administration Data (mandatory)
Tasks

Explorer.
Post-Processing
The Treasury Specialist – Back Office will find the apps for legacy data transfer on the launchpad under General
Settings -> Tools -> Legacy Data Transfer:
● Flag Flows as Reversed(transaction TBB3)
your scenario, you might have to post the transactions to the general ledger. Even if you do not have to post the

The flows are indicated as being posted but are not actually posted. A posting log is generated.

flows as reversed.
using the Enter Val.-Area-Dependent Data for Money Market, Forex, OTC Derivatives Customizing activity
(transaction TPM63C). Alternatively, use the SAP S/4HANA Migration Cockpit app to enter the position
values (see the TRM - Position value 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
system), the migration cockpit can derive the financial transaction number if you can fill one of the
following fields or field combinations instead:
Note
These fields are available in the financial transaction data and should have been filled during the migration
of the financial transaction.
component values in the Positions Management tables.
Should errors occur, you can reverse the initial load using the Reverse Data Transfer Customizing activity
(transaction TPM64).
1.366 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
The function for the legacy data transfer is available in the Customizing of the Transaction Manager under
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 don’t have to post the

The flows are indicated as being posted but are not posted. A posting log is generated.
flows as reversed.
position values (see the TRM - Position value migration object. If you don’t know the financial transaction

number (because this number was generated during the migration of your financial transactions to S/
4HANA system), the migration cockpit can derive the financial transaction number if you can fill one of the
 Note
1.367 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
6. Default risk limit
7. Migration of order/fixing activities
Supported Features
● Structure
Level Name
1 Structure (mandatory)
Tasks

Explorer.

Post-Processing

flows as reversed.
 Note

1.368 TRM - Foreign exchange collar - contract
Purpose
Business Object Definition Foreign exchange collar contract
In Scope
1. Structure data
3. Only the creation of financial transactions is considered. Data transfer for ongoing transactions isn’t
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


flows as reversed.
number (because this number was generated during the migration of your financial transactions to SAP S/
Note
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.
Transcation FTR_DISPLAY Transaction Display
1.369 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
1. There are two options when determining how to migrate other flows via the control parameter. 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 that 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. 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 that 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 excel template into account, and these
are not related to the configuration level.

Tasks

Explorer.
Post-Processing

flows as reversed.
 Note

1.370 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. You can
2. Control Parameter: CTR_TR_COND_C (Indicates whether entries in conditions are complete).
○ Not Complete (by default): means that 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
not related to the configuration level.
Main Flows
1. There are two options when determining how to migrate main flows via the control parameter. You can
2. Control Parameter:CTR_TR_MAINF_C (Indicates whether entries in main flows are complete).
○ Not Complete (by default): means that 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
from the configuration level.
○ 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
1. There are two options when determining how to migrate other flows via the control parameter. You can
2. Control Parameter: CTR_TR_OTHERF_C (Indicates whether entries in other flows are complete).
○ Not Complete (by default): means that 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 flows
from the 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

Payment Details
1. There are two options when determining how to migrate payment details via the control parameter. 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 that 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
details 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 the configuration level.
Tasks

Explorer.
Post-Processing

flows as reversed.
 Note
1.371 TRM - Position value
Purpose

Business Object Definition Valuation-area-dependent data for MM, FX, OTC transac
tions
In Scope
Supported Features
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 1087]

TRM - Foreign exchange swap - contract [page 1082]
TRM - Deposit at notice [page 1076]
TRM - Commercial paper [page 1074]
TRM - Interest rate instrument [page 1091]
TRM - FX option [page 1079]
Level Name
1 Position value data (mandatory)

Enter the financial transaction number to import the position value data. If the transaction number isn’t
available (because this number was generated during the migration of your financial transactions to the SAP
S/4HANA Cloud system), you can use the following fields or field combinations 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
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.
Tasks

Explorer.
Post-Processing
After the import of position value data, you can execute the initial load of position data.
Transaction TPM63C Enter Val.-Area-Dependent Data for Money Market, Forex,

OTC Derivatives

1.372 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’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. 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 that might become relevant when you extend a customer/contract partner as
supplier)
3. BP Roles
5. General texts
6. Company data and localization fields for Korea and USA*
7. Withholding tax data
8. Company texts
9. Purchasing organization data
10. Purchasing partner functions
11. Purchasing texts
12. Bank data

13. Industries
14. Tax numbers
16. Contact persons, including address data with telephone, fax, and email
17. VAT registration number against supplier (South Korea only)*
19. Storing contract details (Ireland only)*
20.Storing SIN and site address (Ireland only)*
21. Pattern of due date shift (Japan only)*
22. Individual/Corporate numbers (Japan only)*
25. Tax payment attributes (Russia only)*
26. Supplier certificates (Saudi Arabia only)*
27. VAT - Cash Account. Regulation (Spain)*
 Note
Out of Scope
1. Updates of existing fields/records.

2. Withholding tax data can only extend with related company data. It isn’t 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 isn’t possible to
extend purchasing partner functions for an already existing purchasing organization.
 Note
This migration object is based on the assumption that business partner and supplier are using the same
must adjust the migration object, you can use the migration object modeler or ask for consulting support.
Supported Features
● General Data
● BP Roles

● General Texts
● Company Data
● Company Texts
● Partner Functions
● Purchasing Texts
● Bank Details
● Industries
● Tax Numbers
● Contact Persons
● VAT registration number against supplier (South Korea only)*
● Storing contract details (Ireland only)*
● Storing SIN and site address (Ireland only)*
● Pattern of due date shift (Japan only)*
● Individual/Corporate numbers (Japan only)*
● Tax payment attributes (Russia only)*
● Supplier certificates (Saudi Arabia only)*
● VAT - Cash Account. Regulation (Spain)*
 Note
Prerequisites

● If you want to extend already existing customers as supplier with the same number:
○ Customer [page 846]

Country-Specific Prerequisites
Country-Specific Prerequisites for Russia

For Russia, make the following additional configurations:
● Financial Accounting (New) Accounts Receivable and Accounts Payable Business Transactions
Country-Specific Settings Russia Payments Maintain Budget Classification Codes
Country-Specific Settings Russia Payments Maintain Payer Statuses
● Financial Accounting (New) Asset accounting Information System Country-Specific Functions
Russia Property Tax (Advanced Compliance Reporting) Define OKTMO Codes
Country-Specific Prerequisites for Saudi Arabia

For Saudi Arabia, make the following additional configuration:
Financial Accounting (New) Accounts Receivable and Accounts Payable Vendor Accounts Master Data
Preparations for Creating Vendor Master Data Accounts Payable Master Data for Saudi Arabia
On the General Data sheet we only offer fields that might become relevant when you extend already existing
customers as supplier with the same number. If you want to extend an existing customer as supplier with the
same number, you have to fill out the customer number (reference number). You also have to fill the BP Roles
sheets. If you want to extend an already existing supplier by new org levels, you have to leave the reference
number empty.
Please consider: You can't transfer a value in one of the fields provided on the General Data sheet when the
supplier already exists.
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
integration) using the Convert Values task to ensure that the key mapping is added to the central key mapping
store of the SAP S/4HANA system. This is only relevant if you extend an existing customer or contract partner
as supplier with thesame number. If you extend an existing supplier with new org. levels, it isn’t necessary to
switch on the key mapping for the Supplier ID.
RUN ID
execute several enhancements for the same instance. You cannot import the same source record more than
once in the same project. The RUN ID field is an additional key field to which you can import the same supplier
more than once.
For example, in the first step, you can import supplier "A" with a new company code or purchasing view. In the
second step, you can import the same supplier "A" with another company code or purchasing view.
same instance.

If you’ve 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 that could be cross-references to other
business partners, for example goods supplier or invoicing party.
If you want to use these references to other business partners, make sure that these business partners have
been 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
the relations and add them later via the BP maintenance UI or BP mass maintenance app.

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
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 is created with an internal

If Vertex determines more than one tax jurisdiction code for a record, the migration of this record fails. If this
The more detailed and accurate an address, the better the tax jurisdiction code is determined by Vertex.

For some addresses, Vertex will always provide more than one tax jurisdiction code. In this case, you’ll have to
Level Name
2 BP Roles
2 General Texts
2 Company 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
2 VAT Reg. Number Against

Suppl.*
2 TAN and Exemption Num

ber*
2 Storing Contract Details*
3 Storing SIN and Site Ad

dress*
2 Pattern of Due Date Shift*
2 Individual/Corporate Num
bers*
2 Tax Payment Classification*
2 Tax Type Assignment*
2 Tax Payment Attributes*
2 Vendor Certificates*
2 VAT - Cash Account. Regula

tion*

 Note
 Note

There are three countryspecific fields in the general data of the business partner: Type of Business, Type of
Industry, and Name of Representative. Note that these fields are overwritten by the latest corresponding fields
of the VAT registration number against supplier sheet. If there are multiple entries in this sheet, the three fields
are updated by the entry with the most recent date. If there’s no entry on the VAT registration number against
supplier data sheet, the three fields stay as they are.

maintain Withholding Tax Type and Withholding Tax Code on the Withholding Tax Data sheet first.
Country-Specific Extension for Ireland

Make sure that the Address Number on the Storing SIN and site address sheet starts with ## followed by any
random number. The system then autogenerates unique numbers for each address record. Note that this
address is relevant for Ireland RCT only. It is not related to the general address of the supplier.
Country-Specific Extension for Japan

For a supplier with Supplier Type I (that is, Individual), the validity date ranges on the Individual/Corporate
Numbers sheet must not overlap between different records of one supplier.

The tax payment classification is used to maintain the VAT payment type for the supplier. There are three
possible options:
1. VAT payment type 1: Split Disabled – This means that the supplier can’t be used for split payment between
2. VAT payment type 2: Split Enabled – This means that the supplier can be used for split payment between
3. VAT payment type 3: Split Mandatory – This means that the supplier must be used for split payment
For a supplier, the validity date ranges on the Tax payment classification sheet must not overlap between
different records of one supplier and must be continuous.

The tax type classification describes where the supplier is registered for VAT. There are four possible options.

For a supplier, the validity date ranges on the Tax type assignment sheet must not overlap between different
records of one supplier and must be continuous.
Country-Specific Extension for Saudi Arabia
For supplier certificates, you need to fill information in the General Data, Company Data, and Vendor certificate
sheets.
Tasks

Explorer.
Post-Processing
1.373 Supplier - extend existing record by Thailand branch code

Purpose
Business Object Component/Area LO-MD-BP
Business Object Type Master Data
Business Object Definition Business partners may have many branches depending on
the various locations they operate from. A branch code is a
4-digit or a 5-digit code assigned by the Revenue Depart
ment in Thailand to uniquely identify each branch of a busi
ness partner. The head office branch has 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 or features are supported.
Prerequisites

● As a prerequisite, the supplier master data needs to be migrated with a Thai company code assigned to it.
● Only one branch code can be marked as the default branch code. If only one branch code is assigned, it will
automatically be marked as the default.
● If branch codes are already assigned to the supplier, additional branch codes can only be uploaded without
a default indicator.
● , Only fax, E-mail, and telephone are supported as standard methods of communication (part of the
address information).
Level Name
1 Thailand branch code
Tasks

Explorer.
Post-Processing
1.374 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.
As a master data object, the supplier is frequently 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 and localization fields for Brasil, India, South Korea, Great Britian,
Taiwan, Australia*
2. BP roles
4. General texts
5. Company data and localization fields for Korea and USA*
6. Withholding tax data
7. Company texts
8. Purchasing organization data

9. Purchasing partner functions
10. Purchasing texts
11. Bank data
12. Industries
13. Tax numbers
15. Contact persons, including address data with telephone, fax, email
16. VAT registration number against supplier (South Korea only)*
18. Storing contract details (Ireland only)*
19. Storing SIN and site address (Ireland only)*
20.Pattern of due date shift (Japan only)*
21. Individual/Corporate numbers (Japan only)*
24. Tax payment attributes (Russia only)*
25. Supplier certificates (Saudi Arabia only)*
26. VAT - Cash Account. Regulation (Spain) *
 Note
Out of Scope
1. Relationship to other business partners.

2. Supplier and customer are two separate business partners and, therefore, have two different numbers.
With the Supplier - extend existing record by new org levels [page 1098] data migration object, you're able
to create a supplier with the same customer number. As a prerequisite, you have to create the customer
first.
 Note
This migration object is based on the assumption that business partner and supplier are using the same
need to adjust the migration object, you can use the migration object modeler or ask for consulting
support.

Supported Features
● General Data
● BP Roles
● General Texts
● Company Data
● Company Texts
● Partner Functions
● Purchasing Texts
● Bank Details
● Industries
● Tax Numbers
● Contact Persons
● VAT registration number against supplier (South Korea only)*
● Storing contract details (Ireland only)*
● Storing SIN and site address (Ireland only)*
● Pattern of due date shift (Japan only)*
● Individual/Corporate numbers (Japan only)*
● Tax payment attributes (Russia only)*
● Supplier certificates (Saudi Arabia only)*
● VAT - Cash Account. Regulation (Spain)*
 Note
Prerequisites
● Bank [page 781]
 Note
The Supplier Account Group field must be in sync with your customizing of the BU grouping. Otherwise, the
grouping overwrites the account group.

Country-Specific Prerequisites
Country-Specific Prerequisites for Russia

For Russia, make the following additional configurations:
Country-Specific Settings Russia Payments Maintain Budget Classification Codes
Country-Specific Settings Russia Payments Maintain Payer Statuses
● Financial Accounting (New) Asset accounting Information System Country-Specific Functions
Russia Property Tax (Advanced Compliance Reporting) Define OKTMO Codes
Country-Specific Prerequisites for Saudi Arabia

For Saudi Arabia, make the following additional configuration:
Financial Accounting (New) Accounts Receivable and Accounts Payable Vendor Accounts Master Data
Preparations for Creating Vendor Master Data Accounts Payable Master Data for Saudi Arabia
You have to maintain all business partner roles depending on your business transactions.
All mandatory partner functions are 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
according to the settings for BP grouping.
Assigned contact persons always get an internal number for the new business partner.
With the BP Grouping field on the General Data sheet, you can 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.
The settings that are made together with your BP Grouping customization determines whether the supplier will
be created with internal or external numbering.
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 1098]
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
integration) using the Convert Values task. This ensures that the key mapping is added to the central key

If you’ve 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, which you must confirm later on. For this reason, you should consider
deactivating 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 that could be cross-references to other
business partners, for example, goods supplier or invoicing party.
If you want to use these references to other business partners, make sure that these business partners are
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
the relations and add them later via the BP maintenance UI or BP mass maintenance app.

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 1098] migration object in a second
step to assign the purchasing 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 is created with an internal

The more detailed and accurate an address, the better the tax jurisdiction code can be determined by Vertex.

For some addresses, Vertex will always provide more than one tax jurisdiction code. In this case, you must
Level Name
2 BP Roles (mandatory for OP)
2 General Texts
2 Company 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
2 VAT Reg. Number Against

Suppl.*
2 TAN and Exemption Num

ber*
2 Storing Contract Details*
3 Storing SIN and Site Ad

dress*
2 Pattern of Due Date Shift*
2 Individual/Corporate Num
bers*
2 Tax Payment Classification*
2 Tax Type Assignment*
2 Tax Payment Attributes*
2 Supplier Certificates*
2 VAT - Cash Account Regula

tion*

 Note
 Note

There are three countryspecific fields on the General Data sheet of the migration template: Type of Business,
Type of Industry, and Name of Representative. Note that these fields are overwritten by the latest
corresponding fields of the VAT registration number against supplier sheet. If there are multiple entries in this
sheet, the three fields are updated by the entry with the most recent date. If there's no entry on the VAT
registration number against supplier data sheet, the three fields will stay as they are.

maintain Permanent Account Number on the General Data sheet as well as Withholding Tax Type and
Withholding Tax Code on the Withholding Tax Data sheet first.
Country-Specific Extension for Ireland

Make sure that the Address Number on the Storing SIN and site address sheet starts with ## followed by any
random number. The system then autogenerates unique numbers for each address record. Note that this
address is relevant for Ireland RCT only. It isn't related to the general address of the supplier.
Country-Specific Extension for Japan

For a supplier with Supplier Type I (for example, Individual), the validity date ranges on the Individual/
Corporate Numbers sheet must not overlap between different records of one supplier.

The tax payment classification is used to maintain the VAT payment type for the supplier. There are three
possible options:
1. VAT payment type 1: Split Disabled – This means that the supplier can’t be used for split payment between
2. VAT payment type 2: Split Enabled – This means that the supplier can be used for split payment between
3. VAT payment type 3: Split Mandatory – This means that the supplier must be used for split payment
For a supplier, the validity date ranges on the Tax payment classification sheet must not overlap between
different records of one supplier and must be continuous.

The tax type classification describes where the supplier is registered for VAT. There are four possible options.

For a supplier, the validity date ranges on the Tax type assignment sheet must not overlap between different
records of one supplier and must be continuous.
Country-Specific Extension for Saudi Arabia
For supplier certificates, you need to fill information in the General Data, Company Data, and Vendor certificate
sheets.
Tasks

Explorer.
Post-Processing
Further Information
● SAP Knowledge Base Article 2848224 – Migration Cockpit: Collective KBA for Business Partner
(Customer, Supplier)
● SAP Note 2726010 – Migration Cockpit: Support of custom fields (in-app extensibility).

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

Level Name
1 Project Definition (mandatory)
2 WBS element data (mandatory)
WBS Element data:

To create a WBS element in a hierarchy, maintain the parent WBS element in field Parent Work Breakdown
Structure Element
Tasks

Explorer.
Post-Processing
Transaction CJ13 Display WBS Element
1.376 Work center/Resource

Purpose
Business Object Component/Area Work Center / Resource (PP/PM)
Business Object Definition 1. Work Center

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

● Work Center Default Values
● Work Center Scheduling
● Work Center Formula Constants

● Work Center Description
● Work Center Formula Constants
● Work Center Capacities, Header data
● Work Center Capacities, Description
● Work Center Capacities, Intervals of Available Capacity
● Work Center Capacities, Shift Values
● Work Center Assignment to Cost Center
Prerequisites
Work Center Description on Work Center Header

Enter a language for the Work Center Description. The default is the logon language.
On sheet the Work Center Description, you can maintain additional descriptions for languages other than those
provided on the Work Center Header sheet.
Capacity Description on Work Center Capacity

The text that describes the capacity in more detail is the logon language.
On the sheet Capacity Description, you can maintain additional descriptions for languages other than the logon
language.
Level Name
1 Work Center Header (man

datory)

Level Name
2 Work Center Capacity
3 Interval of Available Capacity
3 Capacities, shift values
3 Capacity Description
2 Work Center Cost Center
2 Work Center Description
Tasks

Explorer.
Post-Processing
Transaction CR03 Display Work Center
Transaction CRC3 Display Resource
Further Information
SAP Knowledge Base Article 2852321 – Migration Cockpit: Collective KBA for Work Center

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

Important Disclaimers and Legal Information PUBLIC 1121
www.sap.com/contactsap
© 2021 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.
SAP and other SAP products and services mentioned herein as well as
their 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

MigrationObjects OP en

Uploaded by

Document Informationclick to expand document information

Document Informationclick to expand document information

Copyright:

Available Formats

MigrationObjects OP en

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

MigrationObjects OP en

Uploaded by

Copyright:

Available Formats

Implementation Guide | PUBLIC

Document Version: SAP S/4HANA 2020 FPS02 – 2021-08-19

Migration Objects for SAP S/4HANA

THE BEST RUN

Migration Object Name Business Object Type Migration Approach Component

FI - SEPA mandate [page Master data File/Staging Table FI

ECM - Change master [page Master data File/Staging Table PLM-WUI-OBJ-ECN

PM - Measurement docu­ Master data File/Staging Table PM

QM - Inspection plan [page Master data File/Staging Table QM

Service order (only open Transactional data File/Staging Table CRM-S4-SRV

JVA - Joint operating agree­ Master data File/Staging Table CA-JVA

JVA - Joint venture partner Master data File/Staging Table CA-JVA

JVA - Cost center suspense Master data File/Staging Table CA-JVA

JVA - Venture suspense Master data File/Staging Table CA-JVA

JVA - Project suspense [page Master data File/Staging Table CA-JVA

Migration Objects for SAP S/4HANA

JVA - Joint venture master Master data File/Staging Table CA-JVA

CO - Business process [page Master data File/Staging Table CO-OM-ABC

FI - G/L account - extend ex­ Master data File/Staging Table FI

FI - G/L account [page 907] Master data File/Staging Table FI

Product - extend existing re­ Master data File/Staging Table LO

CO - Statistical key figure Master data File/Staging Table CO

Product [page 1021] Master data File/Staging Table LO

FI - Accounts payable open Transactional data File/Staging Table FI-AP

Material listing and exclusion Master data File/Staging Table SD

DG - Assessment for unpack­ Master data File/Staging Table EHS-SUS-DG

DG - Assessment for pack­ Master data File/Staging Table EHS-SUS-DG

DG - Assessment for unpack­ Master data File/Staging Table EHS-SUS-DG

FI - Accounts receivable open Transactional data File/Staging Table FI-AR

FI - G/L account balance and Transactional data File/Staging Table FI

open/line item (restricted)

CO - Cost rate [page 777] Master data File/Staging Table CO

CO - Activity type [page 954] Master data File/Staging Table CO

FI - Bank account balance Transactional data File/Staging Table FI

FI - Cash memo record [page Transactional data File/Staging Table FIN-FSCM-CLM

Migration Objects for SAP S/4HANA

Bank [page 781] Master data File/Staging Table FI

Batch unique at material and Master data File/Staging Table LO-BM

Batch unique at plant level Master data File/Staging Table LO-BM

Material BOM [page 790] Master data File/Staging Table PP-BD

PM - Equipment BOM [page Master data File/Staging Table PM

PM - Functional location Master data File/Staging Table PM

PSS - Product compliance Master data File/Staging Table EHS-SUS

VC - Material variant [page Master data File/Staging Table LO-VC

QM - Inspection plan (depre­ Master data File/Staging Table QM

PSS - Raw material compli­ Master data File/Staging Table EHS-SUS

Class hierarchy [page 804] Master data File/Staging Table CA-CL

Characteristic [page 796] Master data File/Staging Table CA-CL

Class [page 801] Master data File/Staging Table CA-CL

Object classification - Gen­ Master data File/Staging Table CA-CL

PSS - Substance [page 1070] Master data File/Staging Table EHS-SUS

Condition contract [page Master data File/Staging Table LO-AB

Consent [page 829] Transactional data File/Staging Table CA-GTF-CON

CO - Cost center [page 947] Master data File/Staging Table CO

Customer - extend existing Master data File/Staging Table SD

Migration Objects for SAP S/4HANA

Customer - extend existing Master data File/Staging Table SD

PM - Measurement docu Master data File/Staging Table PM

JVA - Joint operating agree Master data File/Staging Table CA-JVA

FI - G/L account - extend ex Master data File/Staging Table FI

Product - extend existing re Master data File/Staging Table LO

DG - Assessment for unpack Master data File/Staging Table EHS-SUS-DG

DG - Assessment for pack Master data File/Staging Table EHS-SUS-DG

DG - Assessment for unpack Master data File/Staging Table EHS-SUS-DG

QM - Inspection plan (depre Master data File/Staging Table QM

PSS - Raw material compli Master data File/Staging Table EHS-SUS

Object classification - Gen Master data File/Staging Table CA-CL

FI - Historical balance (re Transactional data File/Staging Table FI

QM - Master inspection char Master data File/Staging Table QM

PM - Maintenance notifica Transactional data File/Staging Table PM

Material - extend existing re Master data File/Staging Table MM

Product classification - Com Master data File/Staging Table SLL-ITR-CLS

Software/Hardware con Master data File/Staging Table PLM-ESD-ESC

Supplier - extend existing re Master data File/Staging Table MM

Supplier - extend existing re Master data File/Staging Table MM