How To Fix FGL_SFIN_NGLM030 - FBCB documents exist in FI-GL (new); cannot reset document transfer

FGL_SFIN_NGLM030 - Overview

• Message type: E = Error

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

• Message number: 030

• Message text: FBCB documents exist in FI-GL (new); cannot reset document transfer

What causes this issue?

You want to reset the document transfer from <LS>General Ledger
Accounting</> to <LS>General Ledger Accounting (new)</>. However, you
have already performed manual adjustments to the opening balance sheet
by posting FBCB documents. Resetting and restarting the document
transfer might cause inconsistencies in the database.

System Response

The system cannot reset the document transfer.

How to fix this error?

Reverse all FBCB documents, then reset and restart the document
transfer to <LS>General Ledger Accounting (new)</>.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FGL_SFIN_NGLM030 - FBCB documents exist in FI-GL (new); cannot reset document transfer ?

  The SAP error message FGL_SFIN_NGLM030 indicates that there are FBCB (Financial Accounting) documents that exist in the FI-GL (General Ledger) and that the system cannot reset the document transfer. This typically occurs in the context of the New General Ledger (New GL) functionality in SAP.
  
  Cause:
  The error usually arises due to one of the following reasons:
  
  Existing Documents: There are already posted documents in the system that are linked to the document transfer process, which prevents the reset.
  Inconsistent Data: There may be inconsistencies in the data between the FI-GL and the New GL, which can lead to issues when trying to reset document transfers.
  
  Configuration Issues: There may be configuration settings in the New GL that are not aligned with the current document postings.
  
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check Existing Documents:
  
  Use transaction codes like FB03 to review the existing FBCB documents in the FI-GL. Identify any documents that are causing