NOTE 2714344

2021-08-27
2714344
2714344 - Financial data migration to SAP S/4HANA:
Most frequent Error Messages – Information and
Recommendations
Version
9
Type
SAP Knowledge Base
Article
Language
Английский
Master
Language
Английский
Release
Status
Released to Customer
Category
How To
Component
FIN-MIG (SAP Simple Finance data
migration)
Released On
17.10.2020
Please find the original document at https://launchpad.support.sap.com/#/notes/2714344
Symptom
Important! The recommendations in this note are based on practical project experience and should be
verified by the project team during the planning, testing and execution of the project. The content of this note
may be updated at anytime.
You are performing the conversion of your ERP solution to SAP S/4HANA and encounter errors
• during financial data migration steps (transaction FINS_MIG_STATUS). Typically, you are observing
the error messages for the first time when you run your first test conversion and you need to analyze,
understand and then take action for the errors before you run the next SAP S/4HANA conversion
iteration (see KBA 2741967 as well).
• during reconciliation test report run in your SAP ECC solution (see the note 2887318)
You need more information about the error messages:
• What kind of checks are carried out by the system leading to the error message and how to check the
reason for the error message yourself?
• What are typical root causes of the error messages?
• What is the possible business impact?
• What are the recommendations and best practices to handle the error messages?
Environment
•
•
•
•
SAP S/4HANA
ERP
Conversion to SAP S/4HANA
Financial data migration
Cause
A number of checks are introduced in the tools for financial data migration to ensure the consistency of the
data migrated to SAP S/4HANA. Errors are reported in the various check tools while processing the financial
data migration.
© 2021 SAP SE or an SAP affiliate company. All rights reserved
1 of 30
2021-08-27
2714344
Resolution
This Note covers the most frequently seen error messages only. It does not cover all error messages that
could potentially come up during the Financial data migration.
There are some typical reasons for the errors presented however the particular situation in the project may be
different. You should verify the situation with experienced SAP consultant before applying suggested fixes.
Remarks:
• For more information about planning and executing the financial data migration during conversion of
your SAP ERP solution to SAP S/4HANA please refer to SAP Note 2741967
• New! The new reconciliation test, analysis and correction reports (reports FIN_CORR_RECONCILE,
FIN_CORR_DISPLAY, FIN_CORR_MONITOR) have been released in the note 2887318, 2755360
that allow checking and automated correction of most typical inconsistencies in your data in SAP ERP
system before the SAP S/4HANA conversion project start.
• The latest information about the reconciliation test and correction tools is available in the note
2887318
• The checks use the message class FIN_FB_RECON in SAP ERP to report potential data
inconsistencies. The error messages of this class correspond where possible to the messages
with the same number from the class FINS_RECON.
• The Pre-Checks help you identify the steps you need to take to ensure your system is compatible with
the conversion process. These Pre-Checks run in the ERP system before the S/4HANA technical
conversion. Please refer to the following Notes that list error messages and possible solutions for the
pre-checks in ERP:
For Finance: SAP Note 2245333; For Asset Accounting: SAP Note 2618023; For Material Ledger: SAP
Note 2389581
• Post migration phases: please be aware of the note 2390871 for the balance enrichment
Migration
phase
All phases
Application
Error message Performed checks
component
Root cause
examples
There have been
many
potential
inconsistencie
s of a particular type
identified
per
package
(a
combination
of
all
FINS_RECON
company code and
components 899
fiscal year). After
identifying
1000
errors the tools do
not perform the
given check further
and throw this error
message.
© 2021 SAP SE or an SAP affiliate company. All rights reserved
Potential impact
Not all potential
inconsistencie
s may have been
identified in the
particular package
(company
code
and fiscal year).
Further
similar
errors
as
mentioned in the
short text of the
message may be
identified
during
the next test run.
2 of 30
Recomm
Note that
will
no
further re
per error
package
company
fiscal
combinat
limit
is
Ensure
identify, a
address
relevant
during the
conversio
solution
more FIN
899
appear in
you want
and dis
errors pe
2021-08-27
2714344
and
e
please
note 2815
R20: Analyze
Transactional
Data and/or
R21:
FI-GL
Reconciliation
of
Transactional
Data
R20: Analyze
Transactional
Data and/or
R21:
FI-GL
Reconciliation
of
Transactional
Data
R20: Analyze
Transactional
Data and/or
R21:
FI-GL
Reconciliation
of
Transactional
Data
Error
text:
BALANCE IN BSEG
IS NOT ZERO IN
SECOND
LOCAL
CURRENCY
&2
Functional
check:
Check
for
Zero
Balance for a BSEG
document
(Field
BSEG-DMBE2) The
errors
FINS_RECON 001,
002, 003 and 004
are all similar but
they
check
the
BSEG
fields:
WRBTR, DMBTR,
and DMBE3 Errors
FINS_RECON 201,
202, 203 and 204
are related to the
same fields, but for
table BSEG_ADD
Data inconsistency
exists in the source
system already due
to
e.g.
software
errors in the past or
manual update of
BSEG table
ACDOCA will be
filled from BSEG
(in case of classic
GL in the source).
That means the
data inconsistency
in the Universal
Journal will remain
as is This could
also
lead
to
balance
adjustment
line
items in ACDOCA
table if there are
issues
between
balance and line
items in the source
system
In
ca
correction
in
the
system, c
(compone
MIG-GL)
Error
text:
&1
(STATUS
&2):TABLE BSEG
DOES
NOT
FINS_RECON
CONTAIN
ANY
021
ITEMS
Functional
check: BKPF entry
exists, but no BSEG
entry.
Inconsistency
between BKPF and
BSEG in the source
system
already.
Most probably due
to program errors or
wrong handling in
the past Problem
could be due to
incorrect
archiving
as well
Since BSEG is the
main source for
SAP
S/4HANA
migration,
the
particular
document will not
be migrated to
ACDOCA
Check if
items,
missing
exist
in
Otherwise
SAP
FIN-MIG-
Error text: (STATUS
&2): TABLE BSEG
CONTAINS ITEMS
Functional
check:
Check for existence:
FINS_RECON
For an entry in table
023
BKBF
with
field
BSTAT ='A', 'L', 'V',
'W', 'Z', ‘C’ check
that there is no entry
in table BSEG.
Data inconsistency
exists in the source
system already due
to
e.g.
software
errors in the past
etc. There are BSEG
entries found where
this is not expected
due to the document
status
(BKPFBSTAT).
For
instance,
parked
documents
with
document
lines
supposed to be in
Depends
situation
cannot
anticipated
FINS_RECON
003
FINS_RECON
001
FINS_RECON
002
FINS_RECON
004
FINS_RECON
201
FINS_RECON
202
FINS_RECON
203
FINS_RECON
204
© 2021 SAP SE or an SAP affiliate company. All rights reserved
3 of 30
on
Contact
and
(compone
be
MIG-GL)
2021-08-27
2714344
VBSEG*,
nonleading
ledger
documents
with
document lines in
BSEG_ADD, etc. It
needs to checked if
the BSEG entries
wrongly exist or
whether
the
document status in
BKPF is wrong
R24: Check
Migration of
Balances
R24: Check
Migration of
Balances
FI-GL
FI-GL
Error text: FI-GL
TRANSACTION
FIGURES FOR &1
ARE
INCONSISTENT
FINS_RECON Functional
check:
041
Check classic GL
transactions
(original data in
backup
table
GLT0_BCK)
vs.
View GLT0.
Empty
conversion
control
table
FINS_CURTP_MAP
causing
wrong
conversion in phase
MUJ In the original
table GLT0 there
might
be
data
posted on a specific
ledger (check the
ledger definition in
table T881) that has
not or not completely
been converted for
some reason. There
might be a wrong
customizing
for
these ledgers or the
data posted in those
ledgers is not in
synch
with
the
ledger customizing
any more
The
migrated
balances
are
wrong,
which
means the balance
sheet
in
SAP
S/4HANA system
will be wrong, Do
not accept these
errors, especially
in
productive
migration.
Check
recomme
s given
2695313.
that
FINS_CU
is not em
running
errors are
data of
ledger
having
amounts,
the
SA
2700828
implemen
Otherwise
SAP
FIN-MIG-
Error text: FI-GL
(NEW)TRANSACTI
ON FIGURES FOR
&1
ARE
INCONSISTENT
Functional
check:
FINS_RECON Check
NewGL
042
transactions
(original data in
backup
table
FAGLFLEXT_BCK)
vs.
view
FAGLFLEXT
(ACDOCA)
In case classic GL is
used in the source,
the error message
might be due to
wrong customizing
in the step ‘Define
Source ledger for
Migration
of
Balances’.
Check
IMG help for this
step Use transaction
SE16
with
view
FGLV_REC_N_SUM
in order to analyze
inconsistencie
s
between
view
FAGLFLEXT
(ACDOCA)
and
The
migrated
balances
are
wrong,
which
means the balance
sheet
in
SAP
S/4HANA system
will be wrong, Do
not accept these
errors
in
productive
migration
Make sur
Note 26
implemen
corrects
reconcilia
logic with
case cla
used in
check
2695261
contact
(compone
MIG-GL)
© 2021 SAP SE or an SAP affiliate company. All rights reserved
4 of 30
2021-08-27
2714344
table
FAGLFLEXT_BCK.
Check the balance
per group by fields in
view
FGLV_REC_N_SUM
R21:
Reconciliation
of
FI-GL
Transactional
Data
Error
text:
NO
ENTRY IN BSEG
FOR THIS LINE
ITEM
OF
FAGLFLEXA
(LEDGER
&3)
FINS_RECON Functional
check:
070
Check that for all
FAGLFLEXA entries
(
V_FAGLFLEXA_OR
I)
there
is
an
equivalent entry in
table BSEG
R21:
Reconciliation
of
FI-GL
Transactional
Data
Error
text:
NO
ENTRY
IN
FAGLFLEXA FOR
THIS LINE ITEM OF
BSEG (Ledger &3)
FINS_RECON Functional
check:
072
BSEG
entries
without equivalent
entry
in
FAGLFLEXA
(V_FAGLFLEXA_O
RI)
R21:
Reconciliation
of
FI-GL
Transactional
Data
Error
text:
INCONSISTENT
AMOUNT
FOR
UPDATING IN G/L
FOR THIS LINE
ITEM
(LDG
**)
FINS_RECON
Functional
check:
074
Check
table
FAGLFLEXA
(V_FAGLFLEXA_O
RI)
values
in
TSL/HSLKSL/OSL
vs. table BSEG
This inconsistency
exists in the source
system already for
various
possible
reasons This error is
often coupled with
error
message
FINS_RECON 021/
022
The document will
not be migrated if Contact
the
completed (compone
document
is MIG-GL)
missing
This inconsistency
exists in the source
system already for
various
possible
reasons
System
will
migrate
the
document without
FAGLFLEXA,
however
if
document splitting
is active then the
ACODCA records
could be wrong. If
the balance was
not updated then
the migration will
write a correction
item per period to
offset
new
balances created
by the migrated
line items
Check
2425426
explains
find/locali
inconsiste
s (found
SAP S/4
system
automatic
source E
The incon
s can
found/ana
in the sou
with
TFC_COM
Contact
(compone
MIG-GL)
This inconsistency
exists in the source
system already for
various
possible
reasons
(e.g.
program error)
Amounts
will
migrated as per
table BSEG and in
some cases, like
document splitting,
as
per
FAGLFLEXA
which leads to
further inconsistent
data in ACDOCA
The incon
s can
found/ana
in the sou
with
TFC_COM
Contact
(compone
MIG-GL)
© 2021 SAP SE or an SAP affiliate company. All rights reserved
5 of 30
2021-08-27
2714344
PSWBT/
DMBTR/
DMBE2/DMBE3
Amounts
are
checked
between
entry
view
and
general ledger view
R21:
Reconciliation
of
FI-GL
Transactional
Data
Error text: ENTRY
OF
TABLE
BSIS_BCK DOES
NOT
EXIST
IN
VIEW
BSIS
FINS_RECON Functional
check:
081
Check
for
all
existing entries in
the original table
BSIS (BSIS_BCK)
that an entry exists
in the view BSIS.
R21:
Reconciliation
of
FI-GL
Transactional
Data
Error text: ENTRY
OF
TABLE
BSAS_BCK DOES
NOT
EXIST
IN
VIEW
BSAS
Functional
check:
FINS_RECON Check
for
all
083
existing entries in
the original table
BSAS (BSAS_BCK)
that
an
corresponding entry
exists in the view
BSAS.
R21:
Reconciliation
of
FI-GL
Transactional
Data
Error
text:
NO
ENTRIES
FOR
COMPANY CODE
&3 WERE FOUND
IN TABLE GLT0
Functional
check:
Check if there are
FINS_RECON
entries in total table
115
GLT0 (GLT0_BCK )
for documents found
in the source ledger
(according to IMG
section
‘Define
Source Ledger for
Migration.’)
Data inconsistency
in the source system
because.
e.g.
inconsistent/m
issing
archiving
information (BSISXARCH)
in
the
original BSIS entry
BSIS entry without
BSEG/BKPF entry
Etc.
View BSIS will not
be created in SAP
S/4HANA system.
This might cause
follow on issues
like clearing. This
might cause also
follow on issues
like
in
reports
reading from view
BSIS. Those might
show other results
compared to ERP
Data inconsistency
in the source system
because. e.g. BSAS
entry
without
BSEG/BKPF entry
View BSAS will not
be created in SAP
S/4HANA system.
This might cause
follow on issues Contact
like
in
reports (compone
reading from view MIG-GL)
BSAS.
Those
might show other
results compared
to ERP
Wrong customizing
in
IMG
section
‘Define
Source
Ledger for Migration’
in the SAP S/4HANA
system
In
rare
cases,
error
message can be due
to
data
inconsistency in the
source
system
between documents
(BKPF, BSEG) and
totals (GLT0) when
no GLT0 entry exists
Make sur
2515228
implemen
avoid tha
message
incorrectl
customizi
Source
Migration
made. C
Notes 24
2475904.
NOTE_24
allows ch
customizi
correctly
Check i
data
FAGLFLE
© 2021 SAP SE or an SAP affiliate company. All rights reserved
If the error is due
to
wrong
customizing in IMG
section
‘Define
Source Ledger for
Migration’, ignoring
that error message
without correcting
the Customizing,
will
cause
inconsistencie
s in the migration
of balances
6 of 30
If the err
is
rel
documen
original
without
flag, that
in BKPF
(because
archived)
could b
Otherwise
SAP
FIN-MIG-
2021-08-27
2714344
or any oth
totals tab
change
ledger to
NewG/L
‘0’ ledger
contact
(compone
MIG-GL)
R20: Analyze
Transactional FI-GL
Data
Error text: FIELD &3
OF BSEG DOES
HAVE
A
NON
INITIAL
AMOUNT
(&2)
Functional
check:
Check
Currency
Customizing
vs.
Entry View: Check if
FINS_RECON amount field BSEG168
PSWBT,
BSEGDMBTR,
BSEGDMBE2,
BSEGDMBE3 is filled,
whereas
the
currency
customizing (table
T001A)
is
not
maintained
accordingly.
Data inconsistency
exists in the source
system already due
to
e.g.
wrong
handling/curre
ncy
customizing
There might be other
error messages e.g.
FINS_RECON398,
FINS_RECON588
for the relevant data
packages
Table
BSEG
remains untouched
during
data
migration.
Inconsistency
could cause issues
in clearing etc
In
ca
correction
in
the
system, c
(compone
MIG-GL)
Clearing
of
documents might
be
a
problem.
However mismatch
existed in source
system already If
the data in index
table is incorrect
then there is no
issue at all, the
errors
can
be
accepted.
However if the
data in BSEG is
wrong, then there
is the need to
update BSEG from
index tables
If data n
corrected
source
contact S
requires
investigat
In
tha
Customer
know/tell
the cor
(BSIS
BKPF/BS
Clearing
of
documents might
not be a problem,
since
the
inconsistency
is
If the
correct a
incorrect,
repair of
might
R21:
Reconciliation
of
FI-GL
Transactional
Data
Error text: FIELDS
IN BSIS DO NOT
MATCH Functional
FINS_RECON
check:
Mismatch
220
between view BSIS
and the backup
table (BSIS_BCK).
Inconsistency
in
source
system
between secondary
index BSIS and
document
header/line
items
(BKPF/BSEG) The
differences can be in
different fields. (e.g.
BSIS_BCK-ZUONR
<> BSEG-HZUON)
Check Long-text of
the error message
and check the data
accordingly
R21:
Reconciliation
of
FI-GL
Transactional
Data
Error text: FIELDS
IN BSAS DO NOT
FINS_RECON
MATCH Functional
221
check:
Mismatch
between view BSAS
Inconsistency
in
source
system
between secondary
index BSAS and
document
© 2021 SAP SE or an SAP affiliate company. All rights reserved
7 of 30
2021-08-27
2714344
and the backup header/line
items with the cleared
table (BSAS_BCK). (BKPF/BSEG) The items (BSAS)
differences can be in
different fields. (e.g.
BSAS_BCK-ZUONR
<> BSEG-HZUON)
Check Long-text of
the error message
and check the data
accordingly
Open
Item
Reporting in SAP
S/4HANA
might
show
different
results compared
to ERP (where the
secondary
index
tables are read).
Therefore, the data
in source system
should
be
corrected
necessar
migration
BSEG e
discards
in the
S/4HANA
Therefore
will be co
SAP
system
migration
needs
corrected
source
avoid t
contact S
requires
investigat
In
tha
Customer
know/tell
the cor
(BSAS
BKPF/BS
R20: Analyze
Transactional FI-GL
Data
Error text: ITEM IN
BSEG
BUT
MISSING IN INDEX
TABLES BSIS_BCK
AND
BSAS_BCK
FINS_RECON
Functional
check:
339
Check for existing
secondary
index
data
(BSEG
vs
BSIS_BCK / BSEG
vs BSAS_BCK)
Inconsistency
between BSEG and
secondary
index
BSIS/BSAS exists in
the source system
already for various
possible reasons
R20: Analyze
Transactional FI-GL
Data
Error text: LOCAL
CURRENCY &2 IN
BKPF
INCONSISTENT
(SHOULD BE &3)
Functional
check:
FINS_RECON Check
BKPF397
HWAER against the
SAP
S/4HANA
currency settings for
the local currency
for the company
code
(transaction
FINSC_LEDGER)
Inconsistent BKPF
entries (wrong local
currency)
in
the
source system. Most
probably due to
Depends
program errors or
situation
wrong handling of
currency
changes
(e.g. changing local
currency
subsequently) etc.
R20: Analyze
FI-GL
Transactional
FINS_RECON Error text: SHIFTED Data inconsistency Inconsistency
Contact
391
BUZEI BETWEEN exists in the source (shifted line items) (compone
© 2021 SAP SE or an SAP affiliate company. All rights reserved
8 of 30
on
Make s
Note 25
implemen
avoid
documen
status O
contact
(compone
MIG-GL)
Contact
(compone
MIG-GL)
2021-08-27
Data
2714344
BSEG AND NEWGL
LINE
ITEM
Functional
check:
Check
whether
Entry View (BSEG)
and
GL
View
(FAGLFLEXA,
V_FAGLFLEXA_OR
I) have shifted Line
Items (field BUZEI)
system
already.
Typically the issues
are due to a sort
issue in the field
BSEG-BUZEI
and
this is caused by the
bug described in
SAP Note 1988463
There
might
be
additional
error
messages for the
relevant
data
packages
e.g.
FINS_RECON392 or
FINS_RECON394
between
Table MIG-GL)
BSEG
and
ACDOCA
could
cause issues in
clearing etc. It
could also impact
the
migrated
documents
with
incorrect
amounts/accoun
ts between BSEG
ACDOCA
Error text: SECOND
LOCAL CURRENCY
&2
IN
BKPF
INCONSISTENT
(SHOULD BE &3)
Functional
check:
FINS_RECON Check
BKPF398
HWAE2 against the
SAP
S/4HANA
currency settings for
the
2nd
the
company
code
(transaction
FINSC_LEDGER.
Inconsistent BKPF
entries in the source
system, mainly due
to program errors,
wrong handling of
currency
changes
(e.g. adding second
local currency in
trans. OB22) etc.
Depends
on
situation. It need to
be checked with
business whether
Contact
the
wrong
or
(compone
missing value in
MIG-GL)
the
additional
currency
for
previous postings
is needed
R23: Check
Migration of FI-GL
Journal Entry
Error
text:
BALANCE
IN
ACDOCA IS NOT
ZERO
FOR
DOCUMENT
CURRENCY
&2
FINS_RECON
Functional
check:
501
Check that all the
document lines in
each
ACDOCA
document balance
to Zero in document
currency
The data migration
in phase MUJ did
not work correctly
due to e.g. an
program error The
inconsistency
did
exist for the journal
entry in the source
system already. In
that
case,
often
there is a related
error message in an
earlier
phase
pointing
to
an
inconsistency in the
source system (e.g.
error
message
FINS_RECON074 in
phase R21)
Depends on the
root cause and
error
situation
Incorrect data in
migrated
documents
Make sur
2640057
Note 27
implemen
(re-)runni
MUJ
C
related
phases R
R21
contact
(compone
MIG-GL)
R23: Check
Migration of FI-GL
Journal Entry
Error
text:
FINS_RECON BALANCE
IN
504
ACDOCA IS NOT
ZERO FOR 3 RD
The
inconsistency
did most likely exist
for the journal entry
in the source system
Depends on the
root cause and
error
situation
Incorrect data in
Check f
errors in
and/or
Otherwise
R20: Analyze
Transactional FI-GL
Data
© 2021 SAP SE or an SAP affiliate company. All rights reserved
9 of 30
2021-08-27
2714344
LOCAL CURRENCY
&2
Functional
check: Check that
all the document
lines
in
each
ACDOCA document
balance to Zero in
3rd local currency
already. In that case, migrated
typically there is a documents
related
error
message
in
an
earlier
phase
pointing
to
an
inconsistency in the
source system (e.g.
error
message
FINS_RECON534 in
phase R21) Often,
the error is due to
introduction of any
new
currency
settings
for
the
company
code
subsequently in the
source system
SAP
FIN-MIG-
Check
2647203
possible
case
o
custom
ACDOCA
SAP Note
and
Otherwise
SAP
FIN-MIG-
R23: Check
Migration of FI-GL
Journal Entry
Error
text:
MISMATCH
OF
FIELD BETWEEN
NEWGL LINE ITEM
FINS_RECON AND
ACDOCA
515
Functional
check:
Check NewGL line
item
FAGLFLEXA
(V_FAGLFLEXA_O
RI) vs ACDOCA.
Not all GL relevant
fields from source
have been migrated
to
ACDOCA
in
phase MUJ. Very
often
because
Custom fields where
used in source that
were not correctly
migrated etc.
R21:
Reconciliation
of
FI-GL
Transactional
Data
Error
text:
MISMATCH
OF
FIELD
&2
BETWEEN NEWGL
LINE ITEM (&3)
AND BKPF/BSEG
(&4)
Functional
FINS_RECON check: Check Fields
517
of
Entry
View
BKPF/BSEG/BSEG
_ADD
vs
FAGLFLEXA
(V_FAGLFLEXA_O
RI) Fields checked
are BUDAT, HKONT
and WAERS.
Inconsistency exists
In case
in
source
ERP
related t
system
already
BUDAT b
between
in FAGLF
BSEG/BKPF/BSEG
can be c
_ADD
and
the Depends on error program
NewGL
Journal situation
FAGL_CO
table FAGLFLEXA.
(refer to
Often the error is
862523)
due to missing or
contact
wrong field BUDAT
(compone
in table FAGLFLEXA
MIG-GL)
R23: Check
Migration of FI-GL
Journal Entry
Error text: ENTRY
IN BSEG WITHOUT
ENTRY IN ACDOCA
FINS_RECON
Functional
check:
521
Check
that
all
entries in BSEG
have an entry in
BSEG Entry could
not be created in
ACDOCA
during
phase MUJ because
of various possible
reasons:
Inconsistent
© 2021 SAP SE or an SAP affiliate company. All rights reserved
Depends
on
situation
There
might be a loss of
NewG/L
information
in
ACDOCA
Depends
on
situation Missing
documents
in
ACDOCA, hence
in reporting tools.
Possible impact on
balances
10 of 30
Make sur
2714660
implemen
running p
Otherwise
SAP
FIN-MIG-
2021-08-27
2714344
ACDOCA
R23: Check
Migration of FI-GL
Journal Entry
R23: Check
Migration of FI-GL
Journal Entry
Error
text:
DOCUMENT HAS
AMOUNTS &2, &3
(ACDOCA)
IN
TRANSACTION
CURRENCY (TSL)
FINS_RECON Functional
check:
536
Check
BSEG
/
BSEG_ADD
vs.
ACDOCA
Amount
(in
Transaction
Currency). Refer to
the long-text of the
error-message.
Error text: AMOUNT
IN
FAGLFLEXA
AND
ACDOCA
DIFFERS BY &2
(3RD
LOCAL
CURRENCY
&3)
FINS_RECON
Functional
check:
544
Check
that
the
amounts in journal
table FAGLFLEXA
(V_FAGLFLEXA_O
RI) are the same in
ACDOCA.
configuration
Program error etc.
The error might be
closely related to an
error message in an
earlier
phase,
pointing to a data
inconsistency in the
source data (e.g.
FINS_RECON023 in
phase R20/R21)
Inconsistent
ACDOCA
Value
compared to Entry
View
in
BSEG/
BSEG_ADD
Very
often there is a
related
error Depends
message
in
an situation
earlier
phase
pointing
to
an
inconsistency in the
source system (e.g.
FINS_RECON074 in
phase R21)
Typically this error
message is related
to
another
error
message
in
an
earlier
phase
(FINS_RECON588
in
phase
R20).
During
the
data
migration ACDOCA
was filled according
to current currency
settings (transaction
FINSC_LEDGER)
© 2021 SAP SE or an SAP affiliate company. All rights reserved
In case
inconsiste
source (
in phase
error
FINS_RE
check S
2425426
on
explains
find/locali
inconsiste
s (found
SAP S/4
system
automatic
source E
Contact S
See explanation in
error
message
FINS_RECON588:
Error
FINS_RECON544
is a follow-up of
FINS_RECON588.
Documents will be
migrated correctly
to ACDOCA table
in phase MUJ as
per
the
configuration of the
company
code
currencies
(transaction
FINSC_LEDGER).
But
the
table
BSEG
is
not
touched
during
migration
which
can cause issues
in clearing, views
of the index tables
11 of 30
Check f
errors in
and/or
Otherwise
SAP
FIN-MIG-
2021-08-27
2714344
( BSIS, BSAS etc.)
R20: Analyze
Transactional
Data and/or
R21:
FI-GL
Reconciliation
of
Transactional
Data
Error text: OPEN
ITEM
FLAG
IN
SKB1
DIFFERS
FROM OPEN ITEM
FLAG IN BSEG
Functional
check:
Missing Open Item
FINS_RECON
Flag in the line item:
577
In Account Master
Table SKB1 the
open
item
management
indicator is set, in
table BSEG/BSIS it
is not.
The
open
item
management
flag
(XOPVW)
was
changed/set
somewhen in the
past in the account
master data without
changing
the
corresponding line
items
Those line items
cannot be cleared
There might be
problems
in
archiving line items
on these accounts
There might be an
impact on the the
post
migration
activity
‘Enrichment
of
balance
carryforward’, as
well
Check w
SAP Not
is releva
relating
documen
reference
transactio
If releva
sure
implemen
Otherwise
SAP
FIN-MIG-
Check w
SAP Not
is releva
relating
documen
reference
transactio
If releva
sure
implemen
the expl
KBA 25
the corre
inconsiste
OIM flag
removed
line item
by
ZF_SWIT
XOPVW
explained
Note
Otherwise
SAP
FIN-MIG-
R20: Analyze
Transactional
Data and/or
R21:
FI-GL
Reconciliation
of
Transactional
Data
Error text: OPEN
ITEM
FLAG
IN
BSEG
DIFFERS
FROM OPEN ITEM
FLAG
IN
SKB1
Functional
check:
Missing Open Item
FINS_RECON Flag in the Account
578
master
data:
In
Account
Master
Table SKB1 the
open
item
management
indicator is not set,
in table BSEG/BSIS
it is.
The
open
item
management
flag
(XOPVW)
was
changed/switch
ed-off somewhen in
the past in the
account master data
without changing the
corresponding line
items
If the data is not
required as OIM
before
the
upgrade, for any
possible
subsequent
process of this
data,
reconsider
the case after the
upgrade
and
confirm that the
data as OIM is still
not required The
relevant line items
cannot
be
archived, because
they are marked
as OIM
R20: Analyze
Transactional
Data and/or
R21:
FI-GL
Reconciliation
of
Transactional
Data
Error text: OPEN
ITEM
FLAG
IN
SKB1
DIFFERS
FROM OPEN ITEM
FLAG
IN
FINS_RECON
BSEG_ADD
579
Functional
check:
Missing Open Item
Flag in the line item:
In Account Master
Table SKB1 the
The
open
item
management
flag
(XOPVW)
was
changed/set
somewhen in the
past in the account
master data without
changing
the
corresponding line
items
Those line items
cannot be cleared
Contact
There might be
(compone
problems
in
MIG-GL)
archiving line items
on these accounts
© 2021 SAP SE or an SAP affiliate company. All rights reserved
12 of 30
2021-08-27
2714344
open
item
management
indicator is set, in
table
BSEG_ADD
item it is not.
BSEG_ADD is the
Entry
view
for
ledger-group
specific postings to
a
non
leading
ledger.
R20: Analyze
Transactional FI-GL
Data
R20: Analyze
Transactional
Data and/or
R21:
FI-GL
Reconciliation
of
Transactional
Data
Documents will be
migrated correctly
to ACDOCA table
as
per
the
configuration of the
company
code
currencies
(transaction
FINSC_LEDGER)
But
the
table
BSEG
is
not
touched
during Contact
migration
which (compone
can cause issues MIG-GL)
in clearing, views
of the index tables
( BSIS, BSAS etc..
) Data in SPLINFO
and
SPLINFO_VAL
tables is incorrect
which will create
further issues in
follow
on
processes
Error text: FIELD &3
OF
FAGLFLEXA
DOES
HAVE
A
NON
INITIAL
AMOUNT (LEDGER
&4)
Functional
check:
Check
if
there are entries in
journal
table
FINS_RECON FAGLFLEXA
588
(V_FAGLFLEXA_O
RI)
with
filled
amount field (e.g.
OSL) although this
amount
is
not
maintained
in
customizing
(transaction
FINSC_LEDGER)
for this ledger
Inconsistency exists
in source system
already.
An
additional
local
currency might have
existed in the past
and was removed
incorrectly.
The
existing
FAGLFLEXA
records are not in
synch
with
the
current
currency
settings
for
the
company code
Error
text:
CLEARING
SPECIFIC
TO
LEDGER GROUPS
DIFFERS IN BSEG,
SKB1
&2
&3
FINS_RECON
Functional
check:
593
Field
Clearing
specific to ledger
groups
(XLGCLR)
differs in entry view
BSEG and account
master SKB1.
Very often the error
message is due to a
data inconsistency in
table BSEG. The
field
BSEGXLGCLR
contains
the unexpected/not
There could be
allowed value ‘/’. In
issues with follow
that case, the error
on processes
message is related
to error message
FINS_RECON584 in
phase R20. Refer to
refer to SAP Note
1323960 and SAP
Note 1437341 for
© 2021 SAP SE or an SAP affiliate company. All rights reserved
13 of 30
In
cas
XLGCLR
check S
1437341
correct
Check th
of error
FINS_RE
as well.
to
FIN_COR
RROR_S
Note
Otherwise
SAP
FIN-MIG-
2021-08-27
2714344
the
reason/root
cause of the issue
DLT: Data
Migration into
Unified
FI-GL
Journal Entry:
Aggregate
Deltas
Check th
2424125.
recomme
s
In
company
productiv
can be
Error text: NO FI-GL
Customiz
AGGREGATES
The company code
incorrect
FOR LEDGER &1, is not productive In
ledger m
COMPANY CODE Customizing,
an
been def
&2
EXIST incorrect
source
balance
Functional
check: ledger has been
The
relevant Correct
FINS_FI_MIG Check
for defined
for
the
balances are not ledger fo
002
existingG/L
balance migration: A
migrated
that co
balances(GLT0_
non-G/L application
balances
BCK
/ wants to migrate a
be migra
FAGLFLEXT_BCK) company code for
G/L
for
a
ledger/ which no G/L data
wants to
company
code exists
company
combination
which no
exists.
occur
f
codes tha
been use
time: Me
be ignore
R23: Check
Migration of FI-AA
Journal Entry
Error
text:
NO
ENTRY
in
COMPATIBILTY
VIEW ITEM FOR
ENTRY
IN
ORIGINAL TABLE
FINS_RECON (ANEP) Functional
741
check:
Check
existence of entry in
original view for
ANEP
(FAAV_ANEP_ORI
) v. compatibility
view (FAAV_ANEP)
R23: Check
Migration of FI-AA
Journal Entry
Error
FINS_RECON
MIMATCHED
744
AMOUNT
Data not completely
migrated in phase
MUJ because of
e.g.:
FI-AA
customizing in SAP
S/4HANA is not
complete
(e.g.
missing
account
determinations
) Program error etc.
Very often there are
other
error
messages for the
same
assets
in
earlier phases (e.g.
FINS_RECON793 in
phase R21) because
the
data
is
inconsistent in the
source system
Check th
Note 25
implemen
analysis
FINS_MIG
Mismatch between ECK_RC
ANEP values (in analyze t
ERP and SAP the error
S/4HANA)
in detail.
message
fiscal yea
archiving
data
conversio
text: Error message can Mismatch between In case
happen in context of ANEP values (in assets,
&2 migration of group ERP
and
S/4) SAP Not
© 2021 SAP SE or an SAP affiliate company. All rights reserved
14 of 30
2021-08-27
2714344
(ANEP) Functional
check: Checks for
mismatch
in
amounts
between
compatibility
view
(FAAV_ANEP) and
original view for
ANEP
(FAAV_ANEP_ORI
)
assets before the
SAP
S/4HANA
Conversion. Refer to
SAP Note 2508546.
Indicator, that error
is for group asset, is
the existence of
error
FINS_RECON772
for same assets.
Data inconsistency
in source system FIAA customizing in
SAP S/4HANA is not
complete
(e.g.
missing
account
determinations
)
There might be
related
error
message
FINS_RECON781
in phase R24
If the err
is for old
consider
that old
conversio
analysis
FINS_MIG
ECK_RC
analyze t
the error
in detail.
R24: Check
Migration of
Balances
R25: Check FI-AA
Initial
Depreciation
Calculation
Error
text:
MISMATCHED
BALANCE
FOR
ANLC
Functional
check: Compare the
balance
of
the
original table ANLC
(can be checked in
SAP
S/4HANA
system via view
FINS_RECON
FAA_ANLC_ORI )
761
and
compatibility
view (FAAV_ANLC)
In phase R25, the
check from R24 is
repeated after the
initial depreciation
calculation has been
made
in
the
predecessor phase
AFA
If the error comes up
in phase R25 and
the difference is very
small for the field
NAFAP in tables
FAAV_ANLC_ORI
and FAAV_ANLC, it
is due to rounding
and can be ignored.
Very often, the error
is closely related to
error
message
FINS_RECON795 in
phase R21, when
there is a mismatch
between line Items
ANEP/ ANEA and
Totals ANLC for
certain assets. In
this
case,
the
inconsistency
existed in the source
ERP, already and
can be due to
different
reasons
(wrong
handling,
software bugs etc.)
Typically
the
inconsistency
existed
in
the
source
ERP
system,
already.
Refer to the longtext
of
error
message
FINS_RECON795
The FI-AA
be check
detailed
program
FINS_MIG
ECK_RC
is in p
check
2328351
relevance
rounding
in NAFAP
in phase
SAP Not
2532471,
and 27
relevance
years ar
archiving
considere
option,
opening
years is
times no
customer
Otherwise
SAP
FIN-MIG-
R24: Check
Migration of
Balances
Error
text:
RECONCILIATION
FINS_RECON ACCOUNT
&2:
763
TOTAL WITHOUT
ASSET
ASSIGNMENT
Inconsistency
between FI-GL and
FI-AA in the source
system e.g. because
of manual posting to
Asset reconciliation
Inconsistency
between
FI-GL
and FI-AA If the
inconsistency
exists
in
the
source system is
Check
Note 24
implemen
the steps
in
th
Conversio
FI-AA
© 2021 SAP SE or an SAP affiliate company. All rights reserved
15 of 30
2021-08-27
2714344
Functional
check:
Check that the total
of all non-asset lines
posted
on
the
reconciliation
account is 0,-
R24: Check
Migration of
Balances
FI-AA
Error text: ANLC
VALUES WITHOUT
GENERAL LEDGER
ASSIGNMENT
IN
THE OPEN YEAR
FINS_RECON Functional
check:
764
Check,
that
all
annual values in
ANLC are covered
by
the
balance
carryforward year of
the general ledger.
R24: Check
FI-AA
FINS_RECON Error
account Before the
SAP
S/4HANA
Conversion, run the
reconciliation
between FI-GL and
FI-AA in the source
system. Follow the
steps explained in
the FIN Conversion
guide attached to
SAP Note 2332030
and
run
reconciliation
reports in ERP as
explained in SAP
Note 2390881
The general ledger
balance
carryforward was not
processed to the
same year as the
asset management
A fiscal year change
for
fixed
assets
which was already
carried out for two
years in the future
and
closing
operations
have
been
reversed
Typically for the
same assets there
are related error
messages in phase
R21
(e.g.
FINS_RECON795 )
pointing
to
inconsistencie
s in the Source
system
not corrected there
and is accepted in
FINS_MIG_STATU
S, this cannot be
corrected
any
longer
in
the
migrated
system
afterwards
Mismatch between
GL and FI-AA.
Reconciliation
has to be made
before conversion
text: Data not completely Differences
© 2021 SAP SE or an SAP affiliate company. All rights reserved
16 of 30
attached
Note 23
make su
period e
activities
reconcilia
tasks are
in the sou
before
S/4HANA
conversio
message
FINS_RE
might be
if the mig
legacy d
was carr
the cur
Refer to
2346879
details in
Otherwise
SAP
FIN-MIG-
Make sur
2670612
implemen
a long-te
error mes
original
make su
balance c
to the ide
has been
consisten
accountin
the gene
for all led
the SAP
Conversio
reconcilia
between
FI-AA in
system.
steps in
Conversio
attached
Note
Otherwise
SAP
FIN-MIG-
in The FI-AA
2021-08-27
Migration of
Balances
2714344
766
MISMATCHED
BALANCE
FOR
ANLP
Functional
check:
Compare
balance of original
tableANLP
(view
FAAV_ANLP_ORI)
and
compatibility
view (FAAV_ANLP)
migrated in phase
MUJ because of
e.g.:
FI-AA
customizing in SAP
S/4HANA is not
complete
(e.g.
missing
account
determinations
) Program error etc.
Very often there are
other
error
messages for the
same
assets
in
earlier phase R21,
pointing
to
an
inconsistency in the
source system (e.g.
FINS_RECON793)
Periodic
Asset be check
Values
between detailed
ERP
and program
S/4HANA
FINS_MIG
ECK_RC
error mes
old
fisc
consider
that old
conversio
error are
closed fi
check
aggregate
per
fis
between
ANLP an
view are
In this
would o
difference
posting
this case
message
ignored/a
ed Chec
SAP Not
is
im
Otherwise
SAP
FIN-MIG-
R21:
Reconciliation
of
FI-AA
Transactional
Data
Error
text:
MISMATCH
BETWEEN
TRANSACTION
TYPE IN ANEP
FINS_RECON AND
PROVIDED
769
ANEA
FILEDS
Functional
check:
See long-text of
error message-and
explanation in SAP
Note 2424657
Data inconsistency
in the source system
because of wrong
posting.
(Transactions
are
posted to the fixed
asset that use a
current-year
acquisition
transaction type, but
proportional values
for
prior-year
acquisitions
have
also been posted in
the document.)
Potential runtime
errors after the
migration
in
subsequent
processes such as
intracompany
transfers
or
reversals
If the err
is for old
consider
that old
conversio
relevant
been
meanwhil
errors
ignored O
the error
open ye
before, c
(compone
MIG-AA)
R23: Check
Migration of FI-AA
Journal Entry
Error
text:
NO
ENTRY
IN
FINS_RECON COMPATIBILITY
771
VIEW ITEM FOR
ENTRY
IN
ORIGINAL TABLE
Data not completely
migrated in phase
MUJ because of
e.g.:
FI-AA
customizing in SAP
S/4HANA is not
Mismatch between
ANEK values (in
ERP and SAP
S/4HANA)
Check th
Note 25
implemen
that
t
2785894
implemen
© 2021 SAP SE or an SAP affiliate company. All rights reserved
17 of 30
2021-08-27
2714344
ANEK
Functional
check:
Check
existence of entry in
original view for
ANEK
(FAAV_ANEK_ORI
) v. compatibility
view (FAAV_ANEK)
R24: Check
Migration of
Balances
FI-AA
Error
text:
MISMATCHED
BALANCE
FOR
ANEA
Functional
FINS_RECON check:
Compare
781
balance of original
tableANEA
(FAAV_ANEA_ORI
) and compatibility
view (FAAV_ANEA)
complete
(e.g.
missing
account
determinations
) Program error etc.
Very often there are
other
error
messages for the
same
assets
in
earlier phases (e.g.
FINS_RECON793 in
phase R21) because
the
data
is
inconsistent in the
source system
the
MU
execution
message
fiscal yea
archiving
data
conversio
Error message can
Use
happen
in
the
program
context of migration
FINS_MIG
of
group
assets
ECK_RC
before
the
SAP
analyze t
S/4HANA
the error
Conversion. Refer to
in detail
SAP Note 2508546.
occurs i
These
are
false
Depends
on group as
positives
FI-AA
situation and root the
SA
customizing in SAP
cause
2508546
S/4HANA is not
message
complete
(e.g.
fiscal yea
missing
account
archiving
determinations
data
) There might be
conversio
related
error
Otherwise
messages
SAP
FINS_RECON744 /
FIN-MIG772 in phase R23
R21:
Reconciliation
of
FI-AA
Transactional
Data
Error
text:
NO
ENTRY
IN
ORIGINAL TABLE
ANEP
FOR
LEADING
DEPR.AREA
Functional
check:
Inconsistency exists
FINS_RECON The system checks
in
source
ERP
793
whether at least one
system already
data record of the
leading depreciation
area
exists
for
parallel depreciation
areas in table ANEP
(FAAV_ANEP_ORI
)
R21:
FI-AA
Reconciliation
FINS_RECON Error text: LINE Refer
to
error Refer
to
error Use
795
ITEMS ANEP/ANEA message long-text
message long-text program
© 2021 SAP SE or an SAP affiliate company. All rights reserved
Depends on error
situation If not
corrected,
there
might be a followup error message
FINS_RECON 766
in the phase R24
18 of 30
Check th
of the err
and
fo
recomme
s given t
the
SA
2144919
the erro
Otherwise
SAP
FIN-MIG-
2021-08-27
of
Transactional
Data
2714344
DIFFERS
FROM
TOTALS
ANLC
Functional
check:
Aggregated values
of line items in
ANEP and ANEA do
not match the totals
in table ANLC
In migration step
R24
(Check
Migration
of
Balances),
the
total
of
these
migrated line items
is compared with
the former totals
tables. If there was
already
a
difference between
the line item and
the totals table in
phase
R21
(FINS_RECON795
),
this
usually
causes
a
mismatch.
Error
message
FINS_RECON 761
is issued for the
fixed asset and
fiscal year in R24
then
FINS_MIG
ECK_RC
analyze
message
Refer
message
MUJ: Data
Migration into
Unified
Journal: Line
Items and/or
DLT: Data
FI-AA
Migration into
Unified
Journal Entry:
Aggregate
Deltas
Error
text:
GL
ACCOUNT
NOT
MAINTAINED FOR
KTOPL & KTOGR &
FINS_FI_MIG AFABE & TYPE
081
Functional
check:
Check for missing
account
assignments in FIAA customizing
Account allocation in
SAP S/4HANA FIAA customizing not
complete
for
specified
depreciation area
The relevant line
items (in phase
MUJ) or balances
(in phase DLT)
balances
cannot
not
migrated
correctly
Make sur
2581270
implemen
more inf
the erro
Check th
2678925
solutions.
FI-AA
assignme
transactio
Running
report
RASFIN_
ECHECK
S/4HANA
can also
identifying
missing/w
customizi
Otherwise
SAP
FIN-MIG-
MUJ: Data
Migration into
Unified
FI-AA
Journal: Line
Items
Error
text:
BALANCE SHEET
FINS_FI_MIG
ACCOUNT
082
DETERMINATION
MISSING FOR &1,
Account allocation in
SAP S/4HANA FI- The relevant line
AA customizing not items cannot not
complete
for migrated correctly
specified
Check
2678925
solutions.
is relate
FINS_FI_
© 2021 SAP SE or an SAP affiliate company. All rights reserved
19 of 30
2021-08-27
2714344
&2, &3 AREA &4 depreciation area
Functional
check:
Check for missing
balance
sheet
account
assignments in FIAA customizing
R21:
Reconciliation
of
FI-AA
Transactional
Data
R23: Check
Migration of CO
Journal Entry
Error text: COCD
&1: DATA FOR
ASSET
ACCOUNTING
IS
NOT
ARCHIVED
Functional
check:
Check if deactivated
company
codes
have data: as they
will not be migrated,
data will be lost if
not archived.
Company code is
de-actived from an
Asset
Accounting
point of view but
data
(transaction
data or master data)
still exists
Error
text:
BALANCE IN CO
LINE
ITEM
DIFFERS BY &2
(TRANSACT.
CURRENCY
&3)
FINS_RECON
Functional
check:
701
Check balances in
CO between original
table
COEP
(V_COEP_ORI) and
ACDOCA / V_COEP
(transact. Currency)
Data not completely
migrated in phase
MUJ because of
e.g.:
Customizing
and /or Master data
in SAP S/4HANA is
not complete/consi
stent with COEP
data Program error
etc. Typically, for the
affected
data
records, there were
other
error
messages in earlier
phases R21, R22 or
MUJ, giving more
information
about
the root cause (e.g.
FINS_RECON723)
ACC_AA 213
© 2021 SAP SE or an SAP affiliate company. All rights reserved
, but the
steps to
in that No
for
FIN
errors as
the FI-A
assignme
transactio
Running
report
RASFIN_
ECHECK
S/4HANA
can also
identifying
missing/w
customizi
Otherwise
SAP
FIN-MIG-
If the data is
neither
archived
nor the documents
are migrated, it will
be
no
longer
possible to display
documents in the
future
Check th
of the err
and the
2406313
possible o
Controlling
relevant
data
existing in original
table COEP could
not be posted into
ACDOCA
Make sur
2493971
implemen
running
errors are
no mor
org.units,
is
pos
remove
inconsiste
from
t
system
data co
the error
for old f
consider
that old
conversio
Otherwise
SAP
20 of 30
2021-08-27
2714344
FIN-MIG-
R23: Check
Migration of CO
Journal Entry
Error
text:
BALANCE IN CO
LINE
ITEM
DIFFERS BY &2
(OBJECT
CURRENCY
&3)
FINS_RECON
Functional
check:
702
Check balances in
CO between original
COEP
(V_COEP_ORI) and
ACDOCA / V_COEP
(object Currency)
Data not completely
migrated in phase
MUJ because of
e.g.:
Customizing
and /or Master data
in SAP S/4HANA is
not complete/consi
stent with COEP
data Program error
etc. Typically, for the
affected
data
records, there were
other
error
messages in earlier
phases R21, R22 or
MUJ, giving more
information
about
the root cause
Controlling
relevant
data
existing in original
table COEP could
not be posted into
ACDOCA
Make sur
2567727
2731092
is
im
before ru
If the err
to e.g.
existing
check if i
to
rem
inconsiste
from
t
system
data co
the error
for old f
consider
that old
conversio
Otherwise
SAP
FIN-MIG-
R23: Check
Migration of CO
Journal Entry
Error
text:
BALANCE IN CO
LINE
ITEM
DIFFERS BY &2
(CONTROLLING
AREA CURRENCY
&3)
Functional
FINS_RECON
check:
Check
703
balances in CO
between
original
COEP
(V_COEP_ORI) and
ACDOCA / V_COEP
(Controlling
area
Currency)
Data not completely
migrated in phase
MUJ because of
e.g.:
Customizing
and /or Master data
in SAP S/4HANA is
not complete/consi
stent with COEP
data Program error
etc. Typically, for the
affected
data
records, there were
other
error
messages in earlier
phases R21, R22 or
MUJ, giving more
information
about
the root cause (e.g.
FINS_RECON723)
Controlling
relevant
data
existing in original
table COEP could
not be posted into
ACDOCA
Make sur
2493971
implemen
running
errors are
no mor
org.units,
is
pos
remove
inconsiste
from
t
system
data co
the error
for old f
consider
that old
conversio
Otherwise
SAP
FIN-MIG-
R23: Check
Migration of CO
Journal Entry
Error text: ENTRY
IN COEP WITHOUT
ACDOCA Functional
FINS_RECON check:
Check
if
704
original
COEP
entries exist (via
view V_COEP_ORI)
without
COEP record not
migrated in phase
MUJ because of
Depends on the
e.g.:
Customizing
root cause Missing
and /or Master data
CO data
in SAP S/4HANA is
not complete/consi
stent with COEP
Make sur
2714660
implemen
running p
If the err
to e.g.
existing
check if i
© 2021 SAP SE or an SAP affiliate company. All rights reserved
21 of 30
2021-08-27
2714344
corresponding
ACDOCA entry
data
Data
inconsistency
in
source
Program
error etc. Typically,
for the affected data
records, there were
other
error
messages in earlier
phases R21, R22 or
MUJ, giving more
information
about
the root cause.
to
rem
inconsiste
from
t
system
data co
the error
for old f
consider
that old
conversio
Otherwise
SAP
FIN-MIG-
R22:
Enrichment of
CO
Transactional
Data
Error text: EMPTY
FIELD
COEPBUKRS,
OBJECT
&2, VALUE TYPE
FINS_RECON &3
Functional
712
check: Check for
missing
company
code in originally
table
COEP
(V_COEP_ORI)
The
migration
activity
'Enrich
Transactional Data'
tries to determine
the company code
from the object to
which the item is
posted
to
(field
COEP-OBJNR) The
inconsistency exists
in the source system
already
The ENR phase
cannot derive the
relevant company
code from existing
master
data,
hence
these
records are not
migrated
to
ACDOCA
SAP Not
lists the
options
these er
SAP Not
in case
raised for
value typ
error mes
old
fisc
consider
that old
conversio
Otherwise
SAP
FIN-MIG-
R22:
Enrichment of
CO
Transactional
Data
Error text: WRONG
VALUE IN FIELDS
(AWTYP, -SYS, KEY, OWAER or
KWAER) in COEP
FINS_RECON Functional
check:
713
Check for missing or
wrong
fields
in
COEP
(V_COEP_ORI)
versus settings in
COBK, T001,TKA01
Data inconsistency
in the source system
because of program
error in the past
Wrong
handling,
configuration
(e.g.
change of controlling
currency area) etc.
Depends on the
root cause and
situation
Incorrect/miss
ing data migration
with respect to
current
customizing
If the err
is for old
consider
that old
conversio
Otherwise
SAP
FIN-MIG-
R22:
Enrichment of
CO
Transactional
Data
Error text: EMPTY
FIELD COSS_BAKBUKRS
Functional
check:
FINS_RECON
Check for missing
717
company code in
COSS_BAK
(backup table for
COSS)
For the erroneous
records, the phase
ENR
could
not
derive the company
code
information
from the CO object
(COEP-OBJNR).
Check SAP Note
2331897
The relevant items
will
not
be
migrated into the
Universal Journal
(ACDOCA),
because
they
cannot
be
assigned
to
a
company-code
SAP Not
lists the
options
these er
error mes
old
fisc
consider
that old
conversio
Otherwise
SAP
© 2021 SAP SE or an SAP affiliate company. All rights reserved
22 of 30
2021-08-27
2714344
FIN-MIG-
R22: Check
Enrichment of
CO
Transactional
Data
Error text: EMPTY
FIELD COSP_BAKBUKRS
Functional
check:
FINS_RECON
Check for missing
718
company code in
COSP_BAK
(backup table for
COSP)
For the erroneous
records, the phase
ENR
could
not
derive the company
code
information
from the CO object
(COEP-OBJNR).
Check SAP Note
2331897
The
relevant
Controlling items
will
not
be
migrated into the
Universal Journal
(ACDOCA),
because
they
cannot
be
assigned
to
a
company-code
SAP Not
lists the
options
these er
error mes
old
fisc
consider
that old
conversio
Otherwise
SAP
FIN-MIG-
R21:
Reconciliation
of
CO
Transactional
Data
Error
text:
NO
ENTRY IN COBK
FOR COEP FOR
DOCUMENT
FINS_RECON Functional
check:
721
Check that a COBK
entry exists for each
COEP
(V_COEP_ORI)
document
Data inconsistency
exists in the source
ERP system already
because
of
e.g.
wrong
handling/usage
of
customer
programs
These inconsistent
COEP-Entries will
not be migrated to
ACDOCA. So they
will be missing
afterwards
when
checking
CompatibilityView COEP
If the err
is for old
consider
that old
conversio
Otherwise
SAP
FIN-MIG-
R21:
Reconciliation
of
CO
Transactional
Data
Error text: MISSING
TARGET LEDGER
SETTING
FOR
COCD
&1
VERSION
&2
Functional
check:
FINS_RECON
Identify target ledger
723
information for a
combination
of
company code and
CO
version)
for
existing
CO
transactional data
Program error, in
case the version is
used for plan data
only Wrong/missing
customizing in IMG
step ‘Define Ledger
for
CO
Version’
There
might
be
cases were COEP
records exist, but the
related
company
code does not exist
(any more). This is
an
inconsistency
that might be due to
wrong handling
Transactional CO
data
for
this
combination
of
company code and
version will not be
migrated into the
Universal journal
Make sur
2692684
implemen
avoid tha
message
versions
used for
only
C
complete
customizi
step ‘De
for
CO
before (r
phase R
error mes
old
fisc
consider
that old
conversio
Otherwise
SAP
FIN-MIG-
R24: Check
Migration of
Balances
Error
text:
COSP_BAK differs
from
COSP
in
FINS_RECON
values - &1 &2 &3
733
Functional
check:
Compare
view
COSP
and
the
Check long-text of
error message One
possible reason is
missing
companycode information in
source tables. In
those cases the
The
relevant
Controlling items
will
not
be
migrated into the
Universal Journal
(ACDOCA),
because
they
Analyze
difference
help of
FCO_MIG
PLAIN (re
Note 21
case
o
CO
© 2021 SAP SE or an SAP affiliate company. All rights reserved
23 of 30
2021-08-27
2714344
former totals table, errors are related to cannot
be company
stored
in the
errors assigned
to
a informatio
COSP_BAK.
FINS_RECON712
company-code
tables, re
/718 from phase
Note 23
R22
lists the
options
these er
error mes
old
fisc
consider
that old
conversio
Otherwise
SAP
FIN-MIG-
CO
Error
text:
COSS_BAK differs
from
COSS
in
values - &1 &2 &3
FINS_RECON Functional
check:
737
Compare
view
COSS
and
the
former totals table,
stored
in
COSS_BAK.
MUJ: Data
Migration into
Unified
CO
Journal: Line
Items
Error
text:
CO
DOCUMENT &1 &2
&4: MORE THAN 3
COEP
ITEMS
ASSIGNED
TO
ACDOCA
ITEM
Functional
check:
FINS_FI_MIG
Checks
whether
123
there are more than
3 line items in a
COEP
(V_COEP_ORI)
document,
having
the same value for
field BW_REFBZ.
R24: Check
Migration of
Balances
Check long-text of
error message One
possible reason is
missing
companycode information in
source tables. In
those cases the
errors are related to
the
errors
FINS_RECON712
/717 from phase
R22
The
relevant
Controlling items
will
not
be
migrated into the
Universal Journal
(ACDOCA),
because
they
cannot
be
assigned
to
a
company-code
Analyze
difference
help of
FCO_MIG
PLAIN (re
Note 21
case
o
company
informatio
tables, re
Note 23
lists the
options
these er
error mes
old
fisc
consider
that old
conversio
Otherwise
SAP
FIN-MIG-
Wrong configuration
- more than 3 CO
versions
are
assigned to ledger
Corrupt data in the
old COEP table due
to various possible
reasons:
e.g.
Software error that
was fixed by SAP
Note 2202973
The relevant CO
document
line
items have been
corrupt
in
the
source
system
already and will
not be migrated
into
table
ACDOCA.
However,
CO
totals
will
be
corrected
by
migration
of
balances
(step
DLT), so there
Check th
of the err
and the e
in
SA
2657286
message
fiscal yea
archiving
data
conversio
the erro
migration
accepting
case ther
number
© 2021 SAP SE or an SAP affiliate company. All rights reserved
24 of 30
2021-08-27
2714344
R21:
Reconciliation
of
ML
Transactional
Data
M20: Check
Material
Ledger
Master Data
ML
Error
text:
KALN1/MATERIAL
/PLANT/VALUATI
ON
TYPE:
&4/&1/&2/&3
–
FINS_RECON ACCOUNT
NOT
752
DERIVED
Functional
check:
Check if account
can be derived for
the
inventory
balance
Error text: & TABLE
ENTRY,IDENTIFIED
VIA FIELD KALN1:
& Functional check:
Compare
original
table data in table
MBV<Table_Name
>OLD
(e.g.
MBVMBEWOLD for
FINS_ML_MIG
original
data
of
011
MBEW) and its CDS
redirect
MBEW
(View on ACDOCA).
See also long-text of
error
message
FINS_ML_MIG013
, that is shown for
the
same
data
package, as well.
should not be an
impact
on
reporting
and
operations by the
missing items
message
zero val
might be
correct th
source
Contact
ask for b
as Pilot C
SAP Note
The
migration
simulates a goods
receipt.
Errors
happen e.g.: For the
relevant material in
the specific plant/
valuation type (DBfield KALN1= ) no The migration of
account
can
be inventory balance
determined So the is not possible
migration
of
inventory
balance
fails This error is
often coupled with
error
message
FINS_ML_MIG 016/
201 in phase M20.
Check th
of the err
and ma
settings
account
determina
inventorie
goods rec
posted Th
missing
assignme
OBYC is
the pre
Simplifica
item
(/SDF/RC
_CHECK
Typically
the
problem is due to an
inconsistency
existing in source
ECC/ERP
system
already.
During
phase M10, system
tries to simulate a
goods
receipt
posting E.g. for the
relevant material in
the specific plant/
valuation type the
system could not
create an entry e.g.
due
to
missing
account
allocation
entry
(e.g.
field
MBEW-BKLAS not
maintained)
© 2021 SAP SE or an SAP affiliate company. All rights reserved
Check th
of
SA
2532117
long-text
message
FINS_ML
to
ide
relevant t
causing t
In case t
allocation
maintain
Depends on the
allocation
affected data not
goods rec
being posted
posted a
phases
M20. In
error is re
historical
consider
the data
SAP
conversio
Otherwise
SAP
FIN-MIG-
25 of 30
2021-08-27
M20: Check
Material
Ledger
Master Data
2714344
ML
M10: Migrate
Material
Ledger
Master Data
and/or M20: ML
Check
Material
Ledger
Master Data
Check th
of the err
FINS_ML
and
FINS_ML
. First,
relevant d
history ta
tables)
KALN1
error
FINS_ML
. With th
table ke
then th
history
Depends on the
(*BEWH)
affected data not
account a
being posted
missing,
the
determina
that a go
can be
repeat p
and M20
error is re
historical
consider
the data
SAP
conversio
Otherwise
SAP
FIN-MIG-
Error
text:
&
(IDENTIFY
VIA
NON-HISTORY
TABLE
FIELD
KALN1:
&
),
LFMON: & , LFGJA:
& Functional check:
Compare
original
table data in history
data
table
MBV<Table_Name
>OLD
(e.g.
MBVMBEWHWOLD
FINS_ML_MIG for original data of
016
MBEWH) and its
CDS
redirect
MBEWH (View on
ACDOCA). See also
long-text of error
message
FINS_ML_MIG013
, that is shown for
the
same
data
package. The error
message
FINS_ML_MIG017
is shown in this
context as well.
Typically
the
problem is due to an
inconsistency
existing in source
ECC/ERP
system
already.
During
phase M10, system
tries to simulate a
goods
receipt
posting for history
data (from *BEWH
tables)
For
the
relevant material in
the specific plant/
valuation type the
system could not
create an entry e.g.
due
to
missing
account
allocation
entry
(e.g.
field
MBEW-BKLAS not
maintained for the
material in table
MBEW for the given
KALN1)
Error text: NO &
ENTRY
EXISTS
FOR VALUATION
AREA & Functional
check: Check a
FINS_ML_MIG
number of relevant
020
customizing tables
that
consistent
customizing entries
for the valuation
area exists.
Typically
the
problem is due to an
inconsistency
existing in source
ECC/ERP
system
already. E.g.: For a
valuation area no
entries
in
table
CKMLV
(Material
Depends
Ledger
Control
situation
Records), In table
T001K
for
the
Valuation
Area
(BWKEY)
a
company
code
(BUKRS)
is
assigned, but the
assigned Company
Code does not exist
© 2021 SAP SE or an SAP affiliate company. All rights reserved
on
26 of 30
Check an
KBA 273
sure, all
valid for
the
from coll
Note 23
implemen
(re-)runni
migration
2021-08-27
2714344
(any more) in table
T001 Missing entry
in table T001W for a
valuation area
See Also
• KBA 2741967 - How to plan and execute the financial data migration during conversion of SAP ERP
solution to SAP S/4HANA
• SAP Note 2332030 - Conversion of accounting to SAP S/4HANA
• SAP Note 2270333 - S4TWL - Data Model Changes in FIN
• SAP Note 2643232 - SAP S/4HANA migration: Accepting FINS_RECON ** errors
• SAP Note 2352383 - S4TWL - Conversion to SAP S/4HANA Material Ledger and Actual Costing
• SAP Note 2345739 - SAP S/4HANA Material Ledger Migration: Relevant notes and frequently asked
questions
• KBA 2681584 - Dump in ENR / MUJ / DLT step during SAP S/4HANA migration
• KBA 2781513 - High number of inmaterial differences identified during conversion to SAP S/4HANA
Keywords
SAP S/4HANA 1709 1809 Conversion Financial data migration, FINS_RECON, FINS_FI_MIG, ACC_AA,
FINS_ML_MIG, FINS_MIG_STATUS, FINS_MIG_MONITOR_RC0, FINS_MIG_MONITOR_RC1,
FINS_RECON003 FINS_RECON001 FINS_RECON002 FINS_RECON004 FINS_RECON201
FINS_RECON202 FINS_RECON203 FINS_RECON204 FINS_RECON021 FINS_RECON023
FINS_RECON041 FINS_RECON042 FINS_RECON070 FINS_RECON072 FINS_RECON074
FINS_RECON081 FINS_RECON083 FINS_RECON115 FINS_RECON168 FINS_RECON220
FINS_RECON221 FINS_RECON339 FINS_RECON397 FINS_RECON391 FINS_RECON398
FINS_RECON501 FINS_RECON504 FINS_RECON515 FINS_RECON517 FINS_RECON521
FINS_RECON536 FINS_RECON544 FINS_RECON577 FINS_RECON578 FINS_RECON579
FINS_RECON588 FINS_RECON593 FINS_FI_MIG002 FINS_RECON741 FINS_RECON744
FINS_RECON761 FINS_RECON763 FINS_RECON764 FINS_RECON766 FINS_RECON769
FINS_RECON771 FINS_RECON781 FINS_RECON793 FINS_RECON795 FINS_FI_MIG081
FINS_FI_MIG082 ACC_AA213 FINS_RECON701 FINS_RECON702 FINS_RECON703 FINS_RECON704
FINS_RECON712 FINS_RECON713 FINS_RECON717 FINS_RECON718 FINS_RECON721
FINS_RECON723 FINS_RECON733 FINS_RECON737 FINS_FI_MIG123 FINS_RECON752
FINS_ML_MIG011 FINS_ML_MIG016 FINS_ML_MIG020 FINS_RECON899 FIN_FB_RECON
Products
SAP S/4HANA 1610
SAP S/4HANA 1709
SAP S/4HANA 1809
SAP S/4HANA 1909
SAP S/4HANA 2020
SAP S/4HANA, on-premise edition 1511
© 2021 SAP SE or an SAP affiliate company. All rights reserved
27 of 30
2021-08-27
2714344
Other Components
Component
Описание
CO-PC-ACT
Actual Costing/Material Ledger
FI-AA
Asset Accounting
FIN-MIG-AA
Data migration for Asset Accounting
FIN-MIG-GL
Data migration for General Ledger Accounting
XX-SER-MCC
Mission Control Center - Knowledge Management
FIN-MIG-CO
Data migration for Controlling
FIN-MIG-ML
Data migration for Material Ledger
FI-GL
General Ledger Accounting
This document refers to
SAP
Note/KBA
Title
2741967
How to plan and execute the financial data migration during conversion of SAP ERP solution to SAP
S/4HANA
2739717
FINS_ML_MIG020: No CKMLCT entry exists for valuation area
2695313
FINS_RECON41 error message appears in FINS_MIG_STATUS transaction in R24 step
2695261
FINS_RECON042 error message appears in FINS_MIG_STATUS in R24 step
2681584
Dump in ENR / MUJ / DLT step during S/4HANA migration
2678925
FINS_FI_MIG 081 during asset accounting migration
2518759
FINS_RECON 578 - Open item flag in BSEG differs from open item flag in SKB1
2328351
FINS_RECON 761 for small NAFAP differences
862523
mySAP ERP New General Ledger: New functions as of SP 10
2815746
S/4 HANA Financial Data Migration: Error message FINS_RECON 899 given at the end of log.
2767354
Error message FINS_RECON 761 ("Mismatched balance for ANLC") in migration step R24
2754748
S/4 HANA Financial Data Migration:Restrict value type 60 during company code derivation
© 2021 SAP SE or an SAP affiliate company. All rights reserved
28 of 30
2021-08-27
2714344
2731416
S/4 HANA Financial Data Migration : FINS_RECON501 in R23 step due to missing MIG_SOURCE
'R' record
2731092
S/4HANA Finance Migration: Error FINS_RECON 702 for COGM items with zero amounts in version
000
2714660
Line Item migration: Missing packages for reference type AMDP
2700828
S/4 HANA Financial Data Migration R24: FINS_RECON 41 given for a curency ledger in GLT0
2693779
2692684
S/4 HANA migration: Reconciliation error FINS_RECON723 given in R21 step
2670612
FINS_RECON764 - Enhancement of the error message in step R24
2658089
S/4 HANA migration: Reconciliation error FINS_RECON042 given in R24 step
2657286
S/4HANA Finance Migration: Error message FINS_FI_MIG123
2647203
S/4 HANA migration: Reconciliation error due to ZZAUFNR
2643232
S/4 HANA migration: Accepting FINS_RECON ** errors
2640057
S/4HANA Finance Migration: Error FINS_RECON501 for NewG/L Document Split and Transfer
Prices
2581270
Message FINS_FI_MIG 081 is not described clearly enough
2577625
GLYEC / BSTAT O / year end postings to be excluded from migration reconciliations
2577469
S/4HANA Finance Migration: Missing package for AIBU in Migration of Line Items
2572077
R20 reconciliation: Exclusion of BSTAT O documents from index reconciliation
2567727
S/4HANA Finance Migration: Error message FINS_RECON702 for COGM versions
2532471
No updates in migration process step DLT_AA or during Balancy Carry Forward
2532117
S/4HANA Material Ledger Migration Errors with HANA 2.0 SPS02 Rev020
2526882
FINS_RECON 761 in step R24 for fiscal years with archived depreciation (ANLP)
2515228
SFIN reconciliation: Restriction of check to missing GLT0 entries for ledger 00
2514510
Data Migration: FINS_RECON 761 in step R24
2508546
Error messages in context of migration of group assets
2493971
S/4HANA Finance Migration: Error message FINS_RECON701 for split COEP items
2480922
Migration posts asset transaction to incorrect accounts - error FINS_RECON 763
2475904
SFIN reconciliation: Additional check as to whether GLT0 entries exist 2 (source code change)
2475903
SFIN reconciliation: Additional check as to whether GLT0 entries exist 1 (ABAP Dictionary
prerequisites)
© 2021 SAP SE or an SAP affiliate company. All rights reserved
29 of 30
2021-08-27
2714344
2453614
FAQ: Universal Journal Extensibility
2431747
General Ledger: Incompatible changes in S/4HANA compared to classic ERP releases
2425426
FINS_RECON: Technical preparation for corrections in non-migrated source system (here,
messages 184 and 530)
2424125
Migration to S/4 HANA: No GL Balances
2390871
Additional information for balance enrichment
2352383
S4TWL - Conversion to S/4HANA Material Ledger and Actual Costing
2346879
Migration - unjustified error message FINS_RECON763 in the balance check
2345739
S/4HANA Material Ledger Migration: Relevant notes and frequently asked questions
2332030
Conversion of accounting to SAP S/4HANA
2331897
Error FINS_RECON 712, 717 and 718 in data migration - empty field 'company code'
2270333
S4TWL - Data Model Changes in FIN
2225322
Automatic corrections for certain inconsistencies during technical check of transaction data 2
2153336
Explain Error Messages in SAP Simple Finance CO Balance Migration
2144919
Correction report for error FINS_RECON-793
175960
Activation of open item management using RFSEPA02/03
1437341
Correction of BSEG/Index tables after note 1323960
Terms of use | Copyright | Trademark | Legal Disclosure | Privacy
© 2021 SAP SE or an SAP affiliate company. All rights reserved
30 of 30