This SAP note discusses gaps in the allocation of internal numbers. Number range objects are buffered in main memory for performance reasons, which can cause gaps if an application server is shut down before assigning all buffered numbers. The note provides recommendations for certain number range objects where continuous numbering is expected and explains how to deactivate buffering for specific objects if needed. It also references several other related SAP notes for additional information.
This SAP note discusses gaps in the allocation of internal numbers. Number range objects are buffered in main memory for performance reasons, which can cause gaps if an application server is shut down before assigning all buffered numbers. The note provides recommendations for certain number range objects where continuous numbering is expected and explains how to deactivate buffering for specific objects if needed. It also references several other related SAP notes for additional information.
This SAP note discusses gaps in the allocation of internal numbers. Number range objects are buffered in main memory for performance reasons, which can cause gaps if an application server is shut down before assigning all buffered numbers. The note provides recommendations for certain number range objects where continuous numbering is expected and explains how to deactivate buffering for specific objects if needed. It also references several other related SAP notes for additional information.
This SAP note discusses gaps in the allocation of internal numbers. Number range objects are buffered in main memory for performance reasons, which can cause gaps if an application server is shut down before assigning all buffered numbers. The note provides recommendations for certain number range objects where continuous numbering is expected and explains how to deactivate buffering for specific objects if needed. It also references several other related SAP notes for additional information.
Version 17 Validity: 11.06.2015 - active Language English
Header Data Released On 11.06.2015 15:36:48 Release Status Released for Customer Component BC-SRV-NUM Number Range Management Other Components BC-SRV-ASF-UOM Unit Management CA-GTF General Application Functions CO Controlling CO-OM-CCA Cost Center Accounting CO-OM-CCA-A Master Data CO-PA Profitability Analysis FI Financial Accounting FI-AP Accounts Payable FI-AR Accounts Receivable FI-GL General Ledger Accounting FI-TV Business Trip Management LO-MD-MM Material Master MM Materials Management MM-IM Inventory Management MM-IM-PI Physical Inventory PM Plant Maintenance PP Production Planning and Control QM Quality Management QM-PT Quality Planning QM-QN Quality Notifications Priority Recommendations / Additional Info Category Consulting
Symptom l There are gaps in the allocation of internal numbers.
l The status of the number range interval does not match the number that was last assigned.
l The number assignment does not reflect the insert sequence.
IMPORTANT: Please read SAP Notes 1843002, 504875, and 678501.
Other Terms Document number, number range, number range object, buffering, current number level, trip number assignment, number interval, CO document, CO actual posting, inspection lot, material document, physical inventory document, production order number, planned order number, process order number, maintenance order number FB01, VF01, KO88, KE21, KE11, FD01, FK01, XK01, XDN1, MB01, MB0A, MB11, MB1A, MB1B, MB1C, MB31, KANK, KB11, KB13, KB14, KB41, KB43, KB44, KB21, KB23, KB24, KB31, KB33, KB34, KB51, KB53, KB54, PR01, PR02, PR03, PR04, PR05, XD01, VD01, MK01, SNUM, SM56, SNRO, VL01, VL02, CO01, CO40, CO41, VA01, MR1M, MIRO
Reason and Prerequisites
A large number of number range objects are buffered. When the system buffers a number range object, it does not update numbers individually in the database but reserves a preset group of numbers (depending on the number range object) in the database the first time a number is requested, and makes these numbers available to the application server in question. The following numbers can then be taken directly from the application server buffer. New numbers are not used in the database until the application server buffer has been used up.
The effects described under "Symptom" are a direct consequence of this:
l If an application server is shut down, the numbers that are left in the buffer (that is, that are not yet assigned) are lost. As a result, there are gaps in the number assignment.
l The status of the number range interval reflects the next free number that has not yet been transferred to an application server for intermediate buffering. The current number level therefore does not display the number of the "next" object.
l The current number level (for each server) can be displayed using Transaction SM56. Call transaction SM56 and choose the menu 'Goto' -> 'Entries'. In the dialog box, enter the client, the affected number range object (for example, RK_BELEG) and possibly the required subobject (corresponds to the controlling area for the object RK_BELEG).
l 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.
Buffering the number range objects has a positive effect on performance, because the system no longer has to access the database (number range table NRIV) for each posting. Furthermore, a serialization of this table (database locking) is prevented to a large extent so that posting procedures can be carried out in parallel.
Solution Since number range buffering does not cause any expressly assured qualities to be lost, no correction is required. If you still require continuous allocation, you can deactivate the number range buffering specifically for individual objects. Proceed as follows: - Start Transaction SNRO and enter the affected object.
- Choose 'Change'. - Deactivate buffering: Choose 'Edit' -> 'Set Up Buffering' -> 'No Buffering'. - If you want to change the buffer size only, enter the corresponding value in the field 'No. of numbers in buffer'. - Save the changes. Please note that this change is a modification. The modification is overwritten as soon as the affected number range object is redelivered - in other words, you must check the change manually each time you import a release. In particular, read Note 678501, bearing in mind that changing the buffering type - if not explicitly recommended by SAP - constitutes a modification. For other possible solutions, refer to the following notes: 179224, 599157 and 840901.
For the the following number range objects, gaps may cause users to have doubts since they are 'expecting' a sequential numbering: CO area: - RK_BELEG (CO document) Caution: Note that when you deactivate buffering, the problems described in SAP Notes 20965 and 29030 can occur. - COPA_IST (document numbers for actual posting) - COPA_PLAN (document numbers for plan posting) - COPA_OBJ (profitability object numbers) FI area: - DEBITOR (customer master data) - KREDITOR (vendor master data) HR area: - RP_REINR (trip numbers) PM, PP, PS area - AUFTRAG (order numbers, product/process/maintenance orders, network numbers) - QMEL_NR (notification number range) MM area: - MATBELEG (material documents) - MATERIALNR (material masters) QM area: - QLOSE (inspection lots in QM) - QMEL_NR (notification number range) - QMERK (confirmation numbers) - QMERKMALE (master inspection characteristics in QSS) - QMERKRUECK (confirmation numbers of inspection characteristics in QM results processing) - QMETHODEN (inspection methods in QM) - ROUTING_Q (number ranges for inspection plans) - QCONTROLCH (control charts) Area Workflow: - EDIDOC (IDocs) Number range buffering can be activated or deactivated at any time. Number range objects that have to be continuous due to legal specifications (for example, RF_BELEG, RV_BELEG), or due to a corresponding application logic must not be buffered using the buffering type 'Main memory buffering'. See also Notes 37844 (for RF_BELEG) and 23835 (for RV_BELEG).
Validity This document is not restricted to a software component or software component version
References This document refers to: SAP Knowledge Base Articles 1843002 Gaps and Jumps in Numbering SAP Notes 746609 INFO: => LE-TRA-FC-MD (Master data) 678501 System stoppage, locks on table NRIV 456777 Order numbers for internal number assignment 391305 INFORMATION: CO-OM (Customizing & master data) 333356 Internal order: order nmbrs nt assignd continuously 175047 Causes for FI document number gaps (RF_BELEG) 141497 Consulting: Buffering of number ranges 37844 Performance: document number assignment RF_BELEG 29030 Update Terminates in CO After Resetting Transaction Data 23835 Buffering RV_BELEG/number assignment in SD
This document is referenced by:
SAP Notes (12) 175047 Causes for FI document number gaps (RF_BELEG) 37844 Performance: document number assignment RF_BELEG 141497 Consulting: Buffering of number ranges 29030 Update Terminates in CO After Resetting Transaction Data 23835 Buffering RV_BELEG/number assignment in SD 391305 INFORMATION: CO-OM (Customizing & master data) 333356 Internal order: order nmbrs nt assignd continuously 456777 Order numbers for internal number assignment 1679514 Material, customer, vendor numbers not assigned continuously 746609 INFO: => LE-TRA-FC-MD (Master data) 678501 System stoppage, locks on table NRIV 2042606 IP and DMP numbers not assigned continuously
