Implementation Procedure:

In this document we explain the procedure to do the implementation of collective note 3053181
which incorporate about 40 SAP note needed for the good functioning of the reconciliation report for
FI_GL (FIN_CORR_RECONCILE).

By Implementing this Note 3053181, missing notes fitting configuration of your system and related to
FIN_CORR_RECONCILE will be implemented into your system.

The SAP note 3053181 covers this list of SAP Notes:

Number Title
2982279 Reconciliation prior to S/4HANA Conversion: Dump "GETWA_NOT_ASSIGNED "
occured while reconciling data for parked items
2952166 Reconciliation prior to S/4HANA Conversion: Dump "GETWA_NOT_ASSIGNED "
occured while reconciling data for noted items
2951541 Reconciliation prior to S/4HANA Conversion: Number of error message per package is
inconsistent
2937335 Correction prior to S/4HANA Conversion using tool FIN_CORR_MONITOR: Error
message FIN_FB_RECON 334,335,336,337,338 given in reconciliation check
FIN_CORR_RECONCILE
2926051 Reconciliation prior to S/4HANA Conversion: Check between document and index
gives error FIN_FB_RECON226 or FIN_FB_RECON0227
2920374 Analysis and Correction of G/L Inconsistencies in ECC prior to S/4HANA Conversion-
FIN_CORR_MONITOR extension.
2900708 Reconciliation prior to S/4HANA Conversion: Dump " DBSQL_DUPLICATE_KEY_ERROR"
occured while reconciling data with multiple company codes
2896016 FIN_CORR_MONITOR: Additional corrections
2893763 Reconciliation prior to S/4HANA Conversion: BSEG vs. NewGL line item - Amount and
XNEGP
2892011 Reconciliation prior to S/4HANA Conversion: Message Text 517...
2890142 Deactivate Program FIN_AUTO_CORR_MIG_ERROR
2888847 Reconciliation prior to S/4HANA Conversion: Check between BSEG and NewGL Line
Item giving error FIN_FB_RECON072
2885330 Reconciliation before the SAP S/4HANA migration: Change of logic to invalidate
reconciliation run in case of partial run
2884353 Reconciliation prior to S/4HANA Conversion: Compare Balances NewGL Line Item and
BSEG and Existence Check
2880162 Reconciliation prior to Conversion to S/4HANA: Determination of currencies to
reconcile
2875140 Reconciliation prior to S/4HANA conversion: Shifted Fiscal Year
2869029 Reconciliation prior to S/4HANA conversion: Missing check on KOART M for index
2866646 Reconciliation prior to S/4HANA conversion: Missing Comparison for Indices on
KOART A
2863953 Reconciliation prior to S/4HANA Conversion: Correction to Note 2860326
2860326 Reconciliation prior to S/4HANA Conversion: GL Index for AP/AR Reconciliation
Account
2858146 Reconciliation prior to S/4HANA Conversion: Wrong mismatch of fields between BSEG
and Index
2855630 Reconciliation prior to Conversion to S/4HANA: ZUONR for entries in BSIS with KOART
M
2854973 Reconciliation prior to S/4HANA Conversion: Document Key for Mismatch Between
BSEG and NewGL Line Item
 2848596 Reconciliation prior to S/4HANA conversion: Invalid Missing Index for KOART A and M
2843406 Reconciliation prior to S/4HANA conversion: Wrong message number for mismatch
between index and AA line
2840019 Reconciliation prior to S/4HANA Conversion: Short Dump
CX_SY_DYNAMIC_OSQL_SEMANTICS
2839441 Reconciliation prior to S/4HANA conversion: Correction for PSM customers in spain
2837303 Reconciliation prior to S/4HANA conversion: Mismatch BSEG_ADD wrong message
2836444 Analysis and Correction of G/L Inconsistencies in ECC prior to S/4HANA Conversion-
User Interface
2835751 Reconciliation prior to S/4HANA conversion: Unjustified issues when posting in
parallel
2835646 Reconciliation prior to S/4HANA Conversion: Correction to Note 2831943
2834278 Reconciliation prior to S/4HANA Conversion: Missing Check between BSEG and
NewGL Line Item Table
2833865 Reconciliation prior to S/4HANA conversion: Stop after customizing error of one
ledger
2833447 Reconciliation prior to S/4HANA conversion: Unjustified missing header when posting
in parallel
2833232 Reconciliation prior to S/4HANA Conversion: NewGL Error without NewGL active
2831943 Reconciliation on ECC: Compare BSEG with Index for Fields
2822400 Reconciliation before the SAP S/4HANA migration: Corrections for Spanish PSM
customers
2793849 Analysis and Correction of G/L Inconsistencies in ECC prior to S/4HANA Conversion-
Application Coding
2755360 Reconciliation prior to S/4HANA Conversion

Procedure:

1. First of all, please make sure to implement the mandatory SAP note 2755360 and follow the
instruction explained into the solution area and the post pre-manual implementation steps.
2. Secondly, please implement the collective note 3053181
a. Download SAP note 3053181

b. Implement SAP Note 3053181

I. In this step you will get a list of SAP note to be downloaded and implemented
into your system.
PLEASE NOTE:

The list of SAP notes to be implemented depends on your system configuration and the
fact that if some of these SAP notes are already implemented previously in your system.

As reference, the following screenshot displays the list of SAP notes to be implemented
in our test system (configuration SAP_APPL = 600 SP 32). It doesn’t mean that the list of
SAP notes mentioned below should be the same as you will have once you do note
implementation. This is only an implementation example.

II. During implementation process, you may be asked to do some manual

In Some SAP notes, it is mentioned that “in case you face issues when
implementing the correction instruction, please ignore these errors for the time
being and activate and run report …”. In this case, please follow the instructions
inside these notes and go further with implementation process and perform the
manual activities later.

To go further with implementation process, please select the confirmation check

In our current example, we were asked to refer to the mentioned SAP Notes from
the screenshot (2836444, 2880162, 2884353 and 2920374) and to check the
solution section and follow the instructions inside. [In the current
implementation process, and while referring to solution section of SAP note
(2836444 and 2920374) above it is mentioned to activate object despite errors
and then do the manual instruction by running the reports NOTE_2920374 and
NOTE_2836444_NEW and this will solve the issues].

III. After referring to the solutions as explained in the previous step, select the
check box to confirm the manual activities
IV. Lock the changes under a transport

V. Activate the objects

VI. Perform the manual instructions already confirmed from Step (III.)

Please execute the manual instructions from the list of notes (if you got some)
you got when you confirmed the manual steps in step III.

In our current case manual instruction are:

• Reports execution from SAP note 2836444 and SAP note 2920374
• Adding some messages text into massage class: FB_RECON for SAP note
2880162 and 2884353