How To Fix GK835 - Document no. &1 already exists in number range &2, dimension &3, year &4

GK835 - Overview

• Message type: E = Error

• Message class: GK - Messages for SAP Consolidation

• Message number: 835

• Message text: Document no. &1 already exists in number range &2, dimension &3, year &4

What causes this issue?

The document database already contains journal entries with document
number &V1& in dimension &V3& and fiscal year &V4&.

System Response

Document number &V1& cannot be posted.

How to fix this error?

When the assignment is external, assign a document number that does not
yet exist. When the assignment is internal, go to number range
maintenance and increase the current number for number range &V2& in
fiscal year &V4& to a number that exceeds the maximum number already
assigned.

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 GK835 - Document no. &1 already exists in number range &2, dimension &3, year &4 ?

  The SAP error message GK835 indicates that there is an attempt to create or post a document that already exists in the specified number range, dimension, and year. This typically occurs in the context of financial documents, such as journal entries or other accounting documents, where unique document numbers are required.
  
  Cause:
  
  Duplicate Document Number: The document number you are trying to use is already assigned to another document within the same number range and year.
  Incorrect Number Range Configuration: The number range configuration may not be set up correctly, leading to overlaps or incorrect assignments.
  Manual Entry Error: A user may have manually entered a document number that is already in use.
  Data Migration Issues: If data was migrated from another system, there may be conflicts with existing document numbers.
  
  
  Solution:
  
  Check Existing Documents: Verify if the document number you are trying to use already exists in the system. You can do this by searching for