Solution : https://service.sap.com/sap/support/notes/639754 (SAP Service marketplace login required)
Summary :
The SAP Note discusses the final assignment timing of a number after calling NUMBER_GET_NEXT, which depends on the configured buffering method. For main memory buffering, the number is immediately assigned once generated, independent of COMMIT or ROLLBACK actions. For other buffering types or unbuffered scenarios, database updates, and the assigned number's confirmation hinges on COMMIT_WORK or ROLLBACK_WORK statements. The note also explains behaviors in case of rollbacks, especially in parallel buffering systems. Additionally, it details occurrences of implicit COMMIT and ROLLBACK within the SAP environment, impacting the status of number assignments. It links to further SAP Notes for deeper insights on specific buffering behaviors.
Key words :
frequently asked questions reason, free work processes exist, application program- cancel message, number_get_next function module generates, implicit database rollback occurs, dynamic program loading, finally assigned due, called function module, work processes trigger, main storage buffer
Related Notes :
| 1536257 | Duplicate, buffered number assignment |
| 1522367 | Document number gap reason and analysing method |
| 1398444 | Buffering the document number assignment for RF_BELEG |
| 700841 | Duplicate numbers after INTERVAL_NOT_FOUND |