Object &: Buffer is too small (see long text)

What causes this issue?

Number range buffer is full.
The prerequisite for this is that the number of current buffer
entries is close to the value for the maximum number of puffer entries.
Both values can be seen by using transaction SM56.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

How to fix this error?

Procedure for System Administrators

The buffer must be enlarged so that no overflow occurs. This is
necessary. The nobuf/max_no_buffer_entries parameter must be changed.
As the number of buffered number range objects is very
customer-specific, no generally applicable recommendation can be given
for the value of this parameter. The first step is to set the
parameter to 1000 (the standard value is 100). You must note the
following when changing parameters:
- Until now, the puffer needed ca. 28000 bytes. After the parameter
change, it will be 280000 bytes. As the number range puffer is in pool
40, it is possible that you have to increase its size by 260000 bytes.
- The parameter change is not valid until the server is started.
- It is likely that this parameter change makes sense for all
servers and should therefore be performed in DEFAULT.PFL.
- As we do not know exactly how many number range objects should be
buffered, you should check the utilization of the puffer after the
parameter change and possibly adapt the parameters again.

Error message extract from SAP system. Copyright SAP SE.