Solution : https://service.sap.com/sap/support/notes/399207 (SAP Service marketplace login required)
Summary :
For SAP system optimization, local buffering of number ranges, vital for enhanced performance, is analyzed within specific legal and operational constraints (e.g., RF_BELEG). The introduction of correction within SAP Note addresses not only the technical requirements for implementing additional number buffering strategies (e.g., adjustments to NUMBER_GET_NEXT for Note 359907 implementation) but also mitigates potential 'STOPPED NUM' or 'WAITING NUM' errors (refer to Note 142237 for further details). The resolution involves modifying the 'nobuf/max_no_buffer_entries' parameter—increasing it effectively from 100 to 1000 to bypass buffer maxing constraints, monitored through transaction SM56. This adjustment necessitates increased buffer capacity to 280000 bytes from 28000 bytes, with necessary server restarts and potential adjustments in DEFAULT.PFL.
Key words :
buffered number range objects, diagnosisthe number range buffer, buffer required approximately 28000 bytes, number range objects, number range buffer, system administrationthe buffer, potential error arising, terms nr 031 reason, related long text, current buffer entries
Related Notes :
| 359907 | Buffering RF_BELEG/number assignment in FI |
| 179224 | Doc.no.assignment for unbuffered number ranges |