How To Fix G3608 - Several Cons documents were found for some FI documents

SAP Error Message - Details

• Message type: E = Error

• Message class: G3 - Messages for SAP Consolidation: Integration

• Message number: 608

• Message text: Several Cons documents were found for some FI documents

What causes this issue?

Normally exactly one documnet is updated in Consolidation for every
document in Financial Accounting. However, for some FI documents
several follow-on documents exist in Consolidation. These could result
from subsequent posting of FI documents in Consolidation with the
option "Preliminary check" deactivated. These additional documents
produce differences between the general ledger and the Consolidation
ledger.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message G3608 - Several Cons documents were found for some FI documents ?

  The SAP error message G3608, which states "Several Cons documents were found for some FI documents," typically occurs in the context of financial accounting (FI) when there are inconsistencies or multiple entries related to a particular financial document. This can happen during processes such as document clearing, reconciliation, or when trying to post a new document that references existing ones.
  Causes:
  
  
  Multiple Consignment Documents: The error often arises when there are multiple consignment documents linked to a single financial document. This can happen if there are multiple postings or transactions that have not been properly cleared or reconciled.
  
  
  Data Inconsistencies: There may be inconsistencies in the database, such as orphaned records or incorrect references between financial and consignment documents.
  
  
  Incorrect Configuration: Configuration settings in the SAP system related to consignment processing may not be set up correctly, leading to issues in document handling.
  
  
  User Errors: Manual entries or incorrect postings by users can lead to multiple consignment documents being created for the same financial transaction.
  
  
  Solutions:
  
  
  Review Consignment Documents: Check the consignment documents associated with the financial documents in question. Identify if there are indeed multiple consignment documents and determine which ones are valid.
  
  
  Clear or Reconcile Documents: If there are multiple consignment documents that should not exist, you may need to clear or reconcile them. This can involve reversing incorrect postings or clearing open items.
  
  
  Check Configuration: Review the configuration settings related to consignment processing in the SAP system. Ensure that they are set up correctly to prevent such issues in the future.
  
  
  Use Transaction Codes: Utilize relevant transaction codes (like MB1A, MB1B, or MB1C) to analyze and manage inventory and consignment documents. You can also use transaction codes like FBL1N or FBL3N to review financial documents.
  
  
  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 underlying issues.
  
  
  Engage Technical Support: If the issue persists and cannot be resolved through standard procedures, consider engaging your SAP technical support team or a consultant who specializes in SAP FI to investigate further.
  
  
  Related Information:
  
  
  Transaction Codes: Familiarize yourself with transaction codes related to consignment and financial accounting, such as:
  
  MB51: Material Document List
  FBL1N: Vendor Line Item Display
  FBL3N: G/L Account Line Item Display
  
  
  
  Documentation: Review SAP documentation and user manuals related to consignment processing and financial accounting for best practices and troubleshooting steps.
  
  
  Training: Consider training sessions for users involved in financial postings to minimize user errors and improve understanding of the consignment process.
  
  
  By following these steps, you should be able to identify the cause of the G3608 error and implement a solution to resolve it.