SAPNote 17665 - Performance in sales (e.g. VA01)

Symptom:

Wait times occur on the database when you enter sales documents and customer orders, resulting in poor response times.

Cause and prerequisites

When many users are working at the same time, bottlenecks occur in number assignment because the number range in the database remains locked between the assignment of the number and the COMMIT.

Solution
The number range objects can also be buffered; no lock is then used,
e.g. buffering 10 numbers .
Object KONV for the internal condition number.
This number is only used internally, no possible consequences. Object
RV_BELEG for all sales documents, deliveries, and billing documents.
You must consider here that buffering may cause gaps in the number
assignment. This is often not satisfactory, especially for billing
documents. An alternative to buffering is to use several order types
to split the number ranges of the orders, as the database lock is placed
at number range level.
Please refer to Note 23835 for information on avoiding the buffering of
invoices.
Use transaction SNRO to maintain the number range objects mentioned above.