Symptom
Sometimes a PR that has been created the day before another PR has a higher number.
The numbering is not sequential.
or
There is 10 numbers jump
Example:
First person created PR , then ID is 1000010
Another person create then it will be ID 1000020
Again the first person creates another PR it is ID 1000011
Environment
SAP S/4HANA Cloud Public Edition
Cause
To improve the performance of the system, most application number ranges are buffered on the application servers. Otherwise, every number would have to be fetched from the database server by the application server in sequence, via the network, which can be very detrimental to performance. In a busy system there could be many lock conflicts without buffering. In the cloud environment this is always the case and the buffering of PR and PO number ranges is delivered content.
If you use several application servers, the numerical sequence will not reflect the (chronological) insert sequence because the numbers are buffered separately on the individual hosts.
The number range object for Purchasing documents is buffered on different application servers. The number of documents in the buffer is set to 10 by default. So the buffer on each application server hold 10 numbers at any given time. If done on a different application servers, then PO numbers will be out of sync in that sense, and you will see some higher numbers were posted ahead of lower numbers.
Resolution
System is behaving as designed.
Known issue due to buffering across different application servers.
There is no legal requirement to have PR/PO number in sequential manner, thus the buffering is delivered content and cannot be changed.
Also customer requests to change the number range buffering has already been rejected for performance reasons.
See Also
Keywords
Number missing, number range not as expected , KBA , MM-FIO-PUR-REQ-SSP , Fiori UI for Self Service Procurement , Problem