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

SAP Error Message - Details

• 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 the document number in the relevant transaction (e.g., FB03 for displaying financial documents).
  Use a Different Document Number: If the document number is indeed in use, you will need to use a different, unique document number that is not already assigned.
  Review Number Range Configuration: Check the configuration of the number ranges in the SAP system (transaction code OBA7 for financial documents) to ensure that they are set up correctly and that there are no overlaps.
  Adjust Document Numbering: If necessary, adjust the number range settings to allow for new document numbers to be generated without conflict.
  Consult with SAP Basis or Functional Team: If you suspect that the issue is related to system configuration or data migration, consult with your SAP Basis or functional team for further investigation and resolution.
  
  Related Information:
  
  Transaction Codes: 
  
  FB03: Display Document
  OBA7: Maintain Number Ranges for Document Types
  
  
  Documentation: Refer to SAP Help documentation for detailed information on number ranges and document management.
  User Exits or BAdIs: If custom logic is involved in document number assignment, check for any user exits or BAdIs that may affect the document creation process.
  
  By following these steps, you should be able to resolve the GK835 error and successfully create or post your document in SAP.