How To Fix F5695 - Number range &2 in year &3 has been used up for company code &1

F5695 - Overview

• Message type: E = Error

• Message class: F5 - Document Editing

• Message number: 695

• Message text: Number range &2 in year &3 has been used up for company code &1

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message F5695 - Number range &2 in year &3 has been used up for company code &1 ?

  The SAP error message F5695 indicates that the number range for a specific company code has been exhausted. This typically occurs when all the available numbers in a defined number range have been used up for a particular year.
  
  Cause:
  
  Exhausted Number Range: The number range defined for the company code has been completely utilized. This can happen if a large number of documents (like invoices, payments, etc.) have been created within that number range.
  
  Configuration Issues: The number range might not have been properly configured to allow for sufficient numbers, or the range might be too narrow for the volume of transactions.
  Yearly Reset: If the number range is set to reset annually, it may not have been properly configured for the new year.
  
  
  Solution:
  
  
  Extend the Number Range:
  
  Go to the transaction code SNRO (Number Range Objects).
  Find the relevant number range object (for example, for financial documents, it might be FBNR).
  Check the current number range