2023-03-28 2755360

2755360 - Reconciliation prior to S/4HANA Conversion

Version 5 Type SAP Note
Language English Master Language English
Priority Recommendations / Additional Info Category Help for error analysis
Release Status Released for Customer Released On 12.05.2021
Component FIN-MIG-GL ( Data migration for General Ledger Accounting )

Please find the original document at https://launchpad.support.sap.com/#/notes/ 2755360

Symptom

You want to convert your ERP or Suite on HANA production system to S/4HANA. As part of the S/4HANA
conversion cycle the accounting data are analyzed in detail. In most cases it turnes out, that the analyzed
data aren't consistent and correct and therefore don't fullfill the pre-condition for a S/4HANA conversion.

Other Terms

Readiness check, S/4HANA conversion, preparation tasks, data consistency, reconciliation

Reason and Prerequisites

Missing Functionality.

Please make sure the notes 1680583 and 1601030 are implmented before proceeding with implementation of
this note.

Solution

Implement the assigned correction instructions in your system and run report NOTE_2755360.

If you face issues when implementing the correction instruction, please ignore these errors for the time
beeing and activate and run report NOTE_2755360. This will then create the missing objects that lead to
errors while implementing the correction instruction. Now you can reapply the correction instruction again, the
errors should be gone.

The assigned coding allows you to perform reconciliation checks for your accounting data upfront a S/4HANA
conversion project, that means in your ERP or SoH productive system. The checks identify the most critical
data inconsistencies, which should be corrected upfront a S/4 conversion project. In the case of data
inconsistencies, have a look at note 2714344.

After the installation of the coding proceed as following:

Start transaction FIN_CORR_RECONCILE in your system and select the company code and fiscal year
combination for the consistency check. Run the reconciliation in background mode. The program will
complete with an information about the executed run id.

Start the second transaction FIN_CORR_DISPLAY to analyze the result of the reconciliation run. You can
choose the last run as selection criteria to view the issues found in the last run or select the results via the
selection criterias company code and fiscal year.

In specific circumstances it might be usefull to analyze a specific document. This can be achieved by entering
the document number (and fiscal year) in the reconciliation and display transaction.

© 2023 SAP SE or an SAP affiliate company. All rights reserved 1 of 8

2023-03-28 2755360

Manual Activities

------------------------------------------------------------------------
|Manual Post-Implement. |
------------------------------------------------------------------------
|VALID FOR |
|Software Component SAP_APPL SAP Application |
| Release 600 SAPKH60001 - SAPKH60031 |
| Release 602 Until SAPKH60221 |
| Release 603 Until SAPKH60320 |
| Release 604 SAPKH60401 - SAPKH60421 |
| Release 605 Until SAPKH60518 |
| Release 606 SAPKH60601 - SAPKH60624 |
| Release 616 Until SAPKH61613 |
|Software Component SAP_FIN |
| Release 617 SAPK-61701INSAPFIN - SAPK-61718INSAPFIN |
| Release 618 Until SAPK-61812INSAPFIN |
------------------------------------------------------------------------

1. Use transaction SE38 to execute the report NOTE_2755360.

2. Choose "TESTRUN" and execute the report.
3. Check the execution log: Only information messages or warnings should occur (green/yellow
traffic lights).
4. Go back to the execution (using the "Back" arrow, F3), choose "UPDATE", and execute the
report again.
5. The system prompts you to specify a transport request: Enter a transport request (you may
have to create a new task in the transport request if the existing task does not match the
correction).
6. Confirm the message for restricted object editing if you are prompted to do so (this message
is generated for each object; confirm this message for each object).
7. Confirm the message about the object creation as a copy if you are prompted to do so (this
message is generated for each object; confirm this message for each object).
8. Confirm the proposed package assignment (this package assignment is generated for each
object; confirm this assignment for each object).
9. The system may issue a message for object maintenance in the original language. Confirm this
message (this message is generated for each object; confirm this message for each object).
10. As a last step, the system displays the list of all processed objects to be activated.
Activate all objects from this list.
11. Check the activation log; there should be only warnings and information messages.
12. Go back to the execution of the report (using the "Back" arrow, F3), choose "SHOWLOGS", and
execute the report again.
13. Select the last execution log and check that there are only information messages (green
traffic lights).

------------------------------------------------------------------------
|Manual Post-Implement. |
------------------------------------------------------------------------
|VALID FOR |
|Software Component SAP_FIN |
| Release 700 Until SAPK-70016INSAPFIN |
| Release 720 Until SAPK-72011INSAPFIN |
| Release 730 SAPK-73003INSAPFIN - SAPK-73013INSAPFIN |
|Software Component S4CORE |
| Release 100 Until SAPK-10008INS4CORE |
| Release 101 Until SAPK-10106INS4CORE |
| Release 102 Until SAPK-10204INS4CORE |
| Release 103 Until SAPK-10302INS4CORE |
------------------------------------------------------------------------

1. Use transaction SE38 to execute the report NOTE_2755360.

2. Choose "TESTRUN" and execute the report.
3. Check the execution log: Only information messages or warnings should occur (green/yellow
traffic lights).
4. Go back to the execution (using the "Back" arrow, F3), choose "UPDATE", and execute the

© 2023 SAP SE or an SAP affiliate company. All rights reserved 2 of 8

2023-03-28 2755360
report again.
5. The system prompts you to specify a transport request: Enter a transport request (you may
have to create a new task in the transport request if the existing task does not match the
correction).
6. Confirm the message for restricted object editing if you are prompted to do so (this message
is generated for each object; confirm this message for each object).
7. Confirm the message about the object creation as a copy if you are prompted to do so (this
message is generated for each object; confirm this message for each object).
8. Confirm the proposed package assignment (this package assignment is generated for each
object; confirm this assignment for each object).
9. The system may issue a message for object maintenance in the original language. Confirm this
message (this message is generated for each object; confirm this message for each object).
10. As a last step, the system displays the list of all processed objects to be activated.
Activate all objects from this list.
11. Check the activation log; there should be only warnings and information messages.
12. Go back to the execution of the report (using the "Back" arrow, F3), choose "SHOWLOGS", and
execute the report again.
13. Select the last execution log and check that there are only information messages (green
traffic lights).

Software Components

Software Component Release

SAP_APPL 600 - 600

SAP_APPL 602 - 602

SAP_APPL 603 - 603

SAP_APPL 604 - 604

SAP_APPL 605 - 605

SAP_APPL 606 - 606

SAP_APPL 616 - 616

SAP_FIN 617 - 617

SAP_FIN 618 - 618

SAP_FIN 700 - 700

SAP_FIN 720 - 720

SAP_FIN 730 - 730

S4CORE 100 - 100

S4CORE 101 - 101

S4CORE 102 - 102

S4CORE 103 - 103

© 2023 SAP SE or an SAP affiliate company. All rights reserved 3 of 8

2023-03-28 2755360
S4CORE 104 - 104

Correction Instructions

Software Component From To Version Changed on ID

SAP_FIN 700 700 1 29.08.2019 20:41:49 0000575415

SAP_FIN 700 700 1 29.08.2019 20:41:28 0000575416

S4CORE 104 104 1 22.07.2019 21:21:09 0000608267

S4CORE 104 104 1 22.07.2019 21:20:53 0000608268

S4CORE 103 103 1 22.07.2019 21:21:33 0000604149

S4CORE 103 103 1 17.07.2019 20:52:18 0000604150

S4CORE 102 102 1 22.07.2019 21:21:43 0000604143

S4CORE 102 102 1 17.07.2019 20:53:10 0000604144

S4CORE 101 101 1 22.07.2019 21:21:54 0000604121

S4CORE 101 101 1 17.07.2019 20:53:41 0000604142

S4CORE 100 100 1 22.07.2019 21:22:20 0000604119

S4CORE 100 100 1 17.07.2019 20:53:49 0000604120

SAP_APPL 616 616 1 22.07.2019 21:27:09 0000604201

SAP_APPL 616 616 1 17.07.2019 21:18:24 0000604212

SAP_APPL 606 606 1 22.07.2019 21:27:30 0000604876

SAP_APPL 606 606 1 18.07.2019 15:33:33 0000604877

SAP_APPL 605 605 1 17.07.2019 21:18:35 0000604200

SAP_APPL 616 616 1 30.07.2019 19:21:26 0000617130

SAP_APPL 606 606 1 30.07.2019 19:22:10 0000617129

SAP_APPL 605 605 1 30.07.2019 19:22:21 0000617128

SAP_APPL 604 604 1 30.07.2019 19:22:33 0000617127

SAP_APPL 603 603 1 30.07.2019 19:22:48 0000617125

SAP_APPL 602 602 1 30.07.2019 19:23:00 0000617124

SAP_APPL 600 600 1 30.07.2019 19:23:16 0000617123

© 2023 SAP SE or an SAP affiliate company. All rights reserved 4 of 8

2023-03-28 2755360
SAP_FIN 730 730 1 22.07.2019 21:24:50 0000604117

SAP_FIN 730 730 1 17.07.2019 20:53:56 0000604118

SAP_FIN 720 720 1 22.07.2019 21:25:05 0000604115

SAP_FIN 720 720 1 17.07.2019 20:54:02 0000604116

SAP_FIN 618 618 1 22.07.2019 21:25:49 0000604215

SAP_FIN 618 618 1 17.07.2019 21:17:03 0000604216

SAP_FIN 617 617 1 22.07.2019 21:26:54 0000604213

SAP_FIN 617 617 1 17.07.2019 21:18:08 0000604214

SAP_FIN 618 618 1 30.07.2019 19:20:49 0000617182

SAP_FIN 617 617 1 30.07.2019 19:21:14 0000617131

SAP_APPL 605 605 2 23.07.2019 14:58:21 0000604199

SAP_APPL 603 603 3 23.07.2019 14:59:32 0000604197

SAP_APPL 602 602 3 23.07.2019 15:00:03 0000604196

SAP_APPL 600 600 3 23.07.2019 15:00:37 0000604195

SAP_APPL 604 604 3 23.07.2019 14:58:57 0000604198

Prerequisites

Software SAP
From To Title Component
Component Note/KBA

Reconciliation prior to S/4HANA

S4CORE 100 100 2755360 FIN-MIG-GL
Conversion

Reconciliation prior to S/4HANA

S4CORE 101 101 2755360 FIN-MIG-GL
Conversion

Reconciliation prior to S/4HANA

S4CORE 102 102 2755360 FIN-MIG-GL
Conversion

Reconciliation prior to S/4HANA

S4CORE 103 103 2755360 FIN-MIG-GL
Conversion

Reconciliation prior to S/4HANA

S4CORE 104 104 2755360 FIN-MIG-GL
Conversion

Reconciliation prior to S/4HANA

SAP_APPL 600 600 2755360 FIN-MIG-GL
Conversion

SAP_APPL 602 602 2755360 Reconciliation prior to S/4HANA FIN-MIG-GL

© 2023 SAP SE or an SAP affiliate company. All rights reserved 5 of 8

2023-03-28 2755360
Conversion

Reconciliation prior to S/4HANA

SAP_APPL 603 603 2755360 FIN-MIG-GL
Conversion

Reconciliation prior to S/4HANA

SAP_APPL 604 604 2755360 FIN-MIG-GL
Conversion

Reconciliation prior to S/4HANA

SAP_APPL 605 605 2755360 FIN-MIG-GL
Conversion

Reconciliation prior to S/4HANA

SAP_APPL 606 606 2755360 FIN-MIG-GL
Conversion

Reconciliation prior to S/4HANA

SAP_APPL 616 616 2755360 FIN-MIG-GL
Conversion

Reconciliation prior to S/4HANA

SAP_FIN 617 617 2755360 FIN-MIG-GL
Conversion

Reconciliation prior to S/4HANA

SAP_FIN 618 618 2755360 FIN-MIG-GL
Conversion

Reconciliation prior to S/4HANA

SAP_FIN 700 700 2755360 FIN-MIG-GL
Conversion

Reconciliation prior to S/4HANA

SAP_FIN 720 720 2755360 FIN-MIG-GL
Conversion

Reconciliation prior to S/4HANA

SAP_FIN 730 730 2755360 FIN-MIG-GL
Conversion

Support Package

Software Component Release Support Package

S4CORE 100 SAPK-10009INS4CORE

S4CORE 101 SAPK-10107INS4CORE

S4CORE 102 SAPK-10205INS4CORE

S4CORE 103 SAPK-10303INS4CORE

S4CORE 104 SAPK-10401INS4CORE

SAP_APPL 600 SAPKH60032

SAP_APPL 602 SAPKH60222

SAP_APPL 603 SAPKH60321

SAP_APPL 604 SAPKH60422

© 2023 SAP SE or an SAP affiliate company. All rights reserved 6 of 8

2023-03-28 2755360
SAP_APPL 605 SAPKH60519

SAP_APPL 606 SAPKH60625

SAP_APPL 616 SAPKH61614

SAP_FIN 617 SAPK-61719INSAPFIN

SAP_FIN 618 SAPK-61813INSAPFIN

SAP_FIN 700 SAPK-70016INSAPFIN

SAP_FIN 700 SAPK-70017INSAPFIN

SAP_FIN 720 SAPK-72012INSAPFIN

SAP_FIN 730 SAPK-73014INSAPFIN

This document is causing side effects

SAP
Title
Note/KBA

Reconciliation prior to S/4HANA Conversion: Document Key for Mismatch Between BSEG and
2854973
NewGL Line Item

Reconciliation prior to S/4HANA conversion: Wrong message number for mismatch between index
2843406
and AA line

2848596 Reconciliation prior to S/4HANA conversion: Invalid Missing Index for KOART A and M

2835751 Reconciliation prior to S/4HANA conversion: Unjustified issues when posting in parallel

2831943 Reconciliation on ECC: Compare BSEG with Index for Fields

2855630 Reconciliation prior to Conversion to S/4HANA: ZUONR for entries in BSIS with KOART M

2860326 Reconciliation prior to S/4HANA Conversion: GL Index for AP/AR Reconciliation Account

2866646 Reconciliation prior to S/4HANA conversion: Missing Comparison for Indices on KOART A

2869029 Reconciliation prior to S/4HANA conversion: Missing check on KOART M for index

2822400 Reconciliation before the SAP S/4HANA migration: Corrections for Spanish PSM customers

2833232 Reconciliation prior to S/4HANA Conversion: NewGL Error without NewGL active

2835646 Reconciliation prior to S/4HANA Conversion: Correction to Note 2831943

Reconciliation prior to S/4HANA Conversion: Missing Check between BSEG and NewGL Line Item
2834278
Table

2863953 Reconciliation prior to S/4HANA Conversion: Correction to Note 2860326

© 2023 SAP SE or an SAP affiliate company. All rights reserved 7 of 8

2023-03-28 2755360
2858146 Reconciliation prior to S/4HANA Conversion: Wrong mismatch of fields between BSEG and Index

This document refers to

SAP
Title
Note/KBA

Analysis and Correction of G/L Inconsistencies in ECC prior to S/4HANA Conversion- Application
2793849
Coding

This document is referenced by

SAP
Title
Note/KBA

3045170 FIN_CORR_RECONCILE and/or FIN_CORR_DISPLAY is missing after 2755360 note

2887971 Transaction FIN_CORR_RECONCILE is missing in your S/4HANA system

How to plan and execute the financial data migration during conversion of SAP ERP solution to SAP
2741967
S/4HANA

2906603 Financial Data Quality: Central Preparation Note

Terms of use | Copyright | Trademark | Legal Disclosure | Privacy

© 2023 SAP SE or an SAP affiliate company. All rights reserved 8 of 8