Page tree
Skip to end of metadata
Go to start of metadata


The purpose of this article is to explain in detail how to correctly use the Financial Accounting General Ledger comparative analysis report SAPF190_NACC. It is important to note that this report SAPF190_NACC is the exact same as the report SAPF190 which is used in older versions of ERP, with the exception that the output is designed specifically for new releases. SAPF190_NACC should be used for checking for inconsistencies at year end to ensure there are no inconsistencies in the FI data prior to year end closing.


SAPF190_NACC is a powerful tool used to compare values from different tables in FI to check for any inconsistencies in the system. It compares values from the BKPF/BSEG table with the transaction figures totals tables in GLT0/KNC1/LFC1. It also compares the Secondary Indexes (BSIS/BSAS/BSID/BSAD/BSIK/BSAK) table entries with the same transaction figures totals tables to ensure all totals match. If there are any mismatches or discrepancies then the output of the report will highlight them.

Step 1 - When to use this report

This section is very important as the report SAPF190_NACC should only be used under the correct circumstances in the system.

  • The report SAPF190_NACC should only be used if you are using classic General Ledger (GLT0 update). If you have the New General Ledger active then SAPF190_NACC should not be used generally. You can check if you have the New General Ledger active by checking the transaction code FAGL_ACTIVATION:

  • If you are on release ECC5 or greater (SAP_APPL 500+) then you will need to use the report SAPF190_NACC for analysis. If you are any release before ECC5, you will need to use the old version of the report SAPF190. The functionality is exactly the same for both reports.
  • If there is FI archiving done in any specific year, you cannot use the report SAPF190_NACC for analysis in that same year.  
  • You should not use the report for analysis in the current fiscal period while there are postings taking place. In fact it would be best to run the report SAPF190_NACC for analysis when there are no users working in the system at all; like overnight or at the weekend. For example, if the current period is 10 2012, then you should schedule the job for periods 01 to 09 in 2012 if you want to check all data in 2012.

Step 2 - Running the report

Once you establish that it is appropriate to run this analysis report in your system based on the criteria in Step 1, you can execute the report in transaction SE38. On the selection screen enter the company code(s), fiscal year and period (optional but remember not to run if there are postings taking place in the period being analysed):

After that you can execute the report immediately in background mode (F9) or schedule it for later in background. It really depends on the volume of data in your system but generally it is best to run it in background mode as it tends usually to have a long runtime (20minutes or more is typical).

The flag 'Display History' should not be checked when running the report in analysis mode.

Step 3 - Output

When the report is finished running it will produce an output indicating if there are differences or not. It will look something like this in the case where differences are found:

Please note also that you can check all previous SAPF190_NACC analysis runs by going back to the selection screen, checking the 'Display history' checkbox and executing the report with F8. This will provide a list of previous jobs.


So in conclusion, before running the report SAPF190_NACC in your system you need to first make a few checks to ensure that it is appropriate to run it. Please remember that it cannot be run for a fiscal period where there are currently postings taking place. If you do find that there are inconsistencies in the system then you will need to contact your system administrator or consultant to review the situation further.

Related Content

Related Documents: 

How to correctly use the FI New General Ledger comparative analysis report TFC_COMPARE_VZ (aka transaction FAGLF03)

Related SAP Notes/KBAs:

SAP Note 86067: SAPF190: Differences INDIZES - BALANCES

SAP KBA 1640869: SAPF190 throws Dump LIST_ILLEGAL_PAGE Internal Error Invalid page number