How To Fix FGL_SFIN_NGLM065 - Master data check is different between tables &1 and &2 (s. table T800D)

FGL_SFIN_NGLM065 - Overview

• Message type: E = Error

• Message class: FGL_SFIN_NGLM - SAP AC on HANA : New G/L Migration

• Message number: 065

• Message text: Master data check is different between tables &1 and &2 (s. table T800D)

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message FGL_SFIN_NGLM065 - Master data check is different between tables &1 and &2 (s. table T800D) ?

  The SAP error message FGL_SFIN_NGLM065 indicates that there is a discrepancy in the master data between two tables, specifically referencing table T800D. This error typically arises during financial processes, particularly when dealing with General Ledger (G/L) accounts and their associated master data.
  
  Cause:
  The error occurs when there is a mismatch in the master data for G/L accounts between two tables. This can happen due to several reasons:
  
  Data Inconsistency: Changes made to master data in one table may not have been reflected in the other table.
  
  Configuration Issues: Incorrect configuration settings in the system can lead to discrepancies.
  Data Migration Issues: If data was migrated from another system or during an upgrade, inconsistencies may arise.
  User Errors: Manual entry errors or incorrect updates to master data can lead to mismatches.
  
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Identify the Tables: Determine which two tables are being compared (the error message will indicate them as &1