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

SAP Error Message - Details

• 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 the issue.
  If necessary, reverse or delete these documents if they are not needed.
  
  
  
  Analyze Document Flow:
  
  Use transaction FBL3N to analyze the document flow and see if there are any inconsistencies or issues with the postings.
  
  
  
  Reset Document Transfer:
  
  If you have confirmed that there are no existing documents that should prevent the reset, you can attempt to reset the document transfer using transaction SFIN_NGLM or the appropriate transaction for your version of SAP.
  
  
  
  Check Configuration:
  
  Review the configuration settings for the New GL in transaction OBY6 and ensure that they are set up correctly.
  Ensure that the settings for document splitting and other related configurations are consistent with your business processes.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates that can resolve the issue.
  
  
  
  Contact SAP Support:
  
  If the issue persists after trying the above steps, consider reaching out to SAP Support for further assistance. Provide them with the error message and any relevant details about your system configuration.
  
  
  
  Related Information:
  
  New General Ledger (New GL): This is an enhanced version of the traditional General Ledger in SAP that allows for more flexible reporting and better integration with other modules.
  FBCB Documents: These are specific types of documents in the Financial Accounting module that may relate to various financial transactions.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FB03 (Display Document), FBL3N (G/L Account Line Item Display), and SFIN_NGLM (New GL Migration).
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.