Number range skipping

Hi All,
Lately, Our billing number range has started to skip from tiem to time. So sometime ago i dug out and realised it was happening only while network trip. I was wondering if anyone has done any development on this or used some kind of validation to avoid using number range untill it is saved or anythign else to avoid such number jumps.
Any clue will be helpful. thank you in advance.

Check this thread
[Re: Number range Skip|Number range Skip;
thanks
G. Lakshmipathi

Similar Messages

Inspection lot number ranges skipping

My inspection lot number ranges are skipping, those are std number ranges like 01 origin, 04 origin etc, what could be the reason for that.
Inspn lots are getting generated and I took UD also. But certain numbers in the range got skipped.
Eg:- Incoming inspn lot 010000000041 then it comes 010000000045
Lot numbers 01/42, 01/43, 01/44 does not exist in sytem.
Please suggest a way out
Thanks
Vineeth
Edited by: vineeth varghese on Jul 18, 2008 11:31 AM

Craig,
But expert suggestion says, not to switch off buffer thru SNRO as it may affect fuctionality as you said early in this discussion.
But I believe, this is to be relooked by SAP as number range skipping is not good (My case its skipping 5-7 numbers at a time). But I am not convinced with the reply from SAP also.
Anyway thanks to you craig for your advice.
SAP Note on this matter for reference of all. Thanks
================================
Note: 62077
Summary
Symptom
Gaps (jumps) occur when allocating internal numbers.
The status of the number range interval does not match the number that was last assigned.
The number assignment does not reflect the insert sequence.
IMPORTANT: Read Notes 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:
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.
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.
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).
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:
Area CO:
- RK_BELEG   (CO Document)
CAUTION: Note that the problems described in Notes 20965 and 29030 may occur if you deactivate buffering.
- COPA_IST (Document number in actual posting)
- COPA_PLAN (Document number in planned posting)
- COPA_OBJ   (Profitability segment number)
Area FI:
- DEBITOR    (Customer master data)
- KREDITOR   (Vendor master data)
Area HR:
- RP_REINR (Trip numbers)
Area PM, PP, PS
- AUFTRAG    (Order number, production, process, maintenance order, network number)
- QMEL_NR    (Number range - message)
Area MM:
- MATBELEG   (Material documents)
- MATERIALNR (Material master)
Area QM:
- QLOSE      (Inspection lots in QM)
- QMEL_NR    (Number range - message)
- QMERK      (Confirmation number)
- QMERKMALE (Master inspection characteristics in QSS)
- QMERKRUECK (Confirmation number of an inspection characteristic in QM results processing)
- QMETHODEN (Inspection methods in QM)
- ROUTING_Q (Number ranges for inspection plans)
- QCONTROLCH (Quality control chart)
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).
Header Data
Release Status: Released for Customer
Released on: 10.07.2007 12:57:00
Priority: Recommendations/additional info
Category: Consulting
Primary Component: BC-SRV-NUM Number Range Management
Secondary Components: CA-GTF General Application Functions
BC-SRV-ASF-UOM Unit Management
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
Edited by: viny on Jul 23, 2008 9:18 AM

SAP buffer for Customer Account Group (number range skipping)

Dear Experts,
When creating new customer for Account Grp = TRDL for my company, I find out that the number range always skip and this problem continues. Someone told me to check it out if the problem might comes from buffer. In Tcode = SNRO (Object = DEBITOR) I find out that buffer setting = 5.
The Question is how can I check if this buffer rate is compatible with my SAP environment? or which rate is more compatible and help solve the problem of number range skipping?
If anybody have some suggestion please feel free to contribute it.
Thank you very much

Hi,
in SNRO, take out the flag for
"Main memory buffering".
SAP recommends:
Dependencies
When buffering number intervals, gaps may result in number assignment. Buffering is therefore not possible for applications, which require continuous number assignment.
What happens is that the system loads consecutive numbers into the buffer, in your case these are five consecutive numbers. When you create customers and do not use all the numbers already in the buffer, the numbers remain open. Example: You start XK01 for customer creation, create three customers and then logoff. You have two open numbers remaining. Numerical example: 1, 2, 3 have been used, 4 and 5 have been reserved, but are open.
When invoking XK01 again after subsequent log-on, the system pulls the next five numbers into the buffer. Since 1,2,3,4,5 were already taken (for the previous buffer), the next buffer goes from 6 to 10.
Numbers 4 and 5 will never be used, the practical consequence of that are the number gaps that you have noticed.
Hope this helps.
Rudolf

Number range skipping & getting reassigned

Hello All,
I am getting a situation where the number ranges are getting skipped & then later the skipped number ranges are getting assigned again to new documents. This is happening for excise documents, customer master & material number. When i checked the number range objects in SNRO, there is no buffer assigned. What is confusing to me is that the number ranges once skipped should not get re-assigned to new documents.
request you to please give your expert comments on this issue. Thanks in advance.

You may need to refer OSS 1817764 - Number range skip in Customer / Vendor Master Data
and 1646025 - Material number skipping while creating material in transaction MM01
Regards,

Problem in Purchase Requisition Number Range (Skipping)

Hi,
While creating the Purchase Requisition, the PR Number is skipping by 10, for example, first PR is 10000000, send is 10000010 and so on.. on the Quality Server
The same is OK in Development Server. Pls. note that I have used the Standard Number Range.
Pls. guide.
Regards,

Hi,
To add on Arun's answer. The setting in trs SNRO is client independent. You should press the "display" button there (the glasses) and check the field "No. of numbers in buffer". The standard SAP setting is 10 and changing this setting is a modification to standard.
The scenario is as follows. Each time your application server needs to allocate new number to a PReq it contacts the database server, which keeps track of the number range. Even if your system (Q) is a single server system, the principle is still the same.
The point is that the application server doesn't take one next number from the database server, but 10 numbers. Next time it needs to allocate new number to a PReq, it doesn't have to call the DB server again - it merely takes the next number from the "bundle" it already got. The reason is to save time.
This works fine as long as the application server is up and running all the time - no "holes" are generated. It can however happen that the application server "forgets" the buffer, e.g. when the server is taken down (this is however not the only way). In this case, all the numbers it got from the DB server get lost and the application server takes out new ten.
As I mentioned above, this function is impossible to change without modification to SAP standard. Please consider well your business need to have the consequent numbers. Most of the companies manage with this setting.
BR
Raf

Number range Skip

Hi Guys,
Sometimes I have found that serial number is not getting followed correctly. One or two number get skipped. Can someone suggest what could be the reason behind that and is there any way to find out the missing numbers?
Regards
Pushpa

Hi Pushpa,
In SD module, the gaps in invoice numbering may be caused normally due
to two reasons:
- update interruptions - the number is set in to the invoice at the
beginning of the program . If an interruption of the process happens
after the assignation of this number, the number has run in the range
and cannot be recovered. Update terminations in transaction VF01 and
VF04. The billing document number is reserved prior to the update.
After a possible update termination, it cannot be used again.
Update terminations are displayed in transaction SM13. At present,
there is no possible solution to this.
- Object RV_BELEG is buffered. In this case the performance is improved
but these gaps are produced.
Note 19050 provides details on why gaps occur, please also refer to the
other attached notes for more info.
I am sorry to tell you that there is no way to solve the gaps or to
'refill' missing invoice numbers.
We know that in different countries you have to explain document gaps
to Legal Authorities, for example Italy. For this reason there is report
RFVBER00 to document gaps occuring due to an update termination.
Report RFVBER00 only lists update terminations that are not older than
50 days (or according to what time is maintained in your system).
So it could be that this log has already been cleared.
It is necessary that these update terminations are documented before
the 50 days expiration period.
A second possibility is that the gaps occur, but NOT due to an update
termination other resons, incorrect customising & user exits etc.
Gaps without update terminations cannot be (easily) explained.
They can be (only) detected via report RFBNUM00. Report RFBNUM00 display
s these document number gaps for the number range object RF_BELEG.
I hope this information helps explain the system behaviour and is
sufficient for your auditing. If you really cannot have gaps in billing
documents you will have to switch off buffering of RV_BELEG.
Thanks & Regards
Roop

Sales order number range skipping..anyone faced this ????

Hi all ,
We have perculiar problem where Sales order document numbers are
skipping/ jumping inbetween around 200- 250. And it is recurring.
Anyone faced this problem ? Does any one has any clue on this ?
we are in ECC 5.0
Thanks in advance.
Kb

This is happening due to buffering in number range. If you write the same to SAP OSS, they will let tou know the note no to be refered to, which will resolve the problem.
Regards,
Rajesh Banka

Number range skip problem during material creation

Hi MM expert,
When we are creating material, its number is skipping by interval of 10.
kindly tell the solution.
Regards,
Santosh

Hi,
Please check which number range assigned to the Materiial type you are creating at sprologistics generalmaterial masterbasic settings-material type .and for the number range at the transaction code MMNR .
Regards,

Vendor number ranges - skip

Hi,
In our organization, we have defined the number range for vendors from 1000 to 2000 but the number of vendor codes created are 1999 but in XKN1, the current status is 1500 onlly. But when we try to create a vendor, it is stopping saying that the vendor code 1501 already exists and so on. Please help...
Thanks a lot...

Hi Sridevi,
Make sure,
1. Number is not external.
2. Check whether other company codes have created vendors under this group.
Regards,
Chintan Joshi.

Number ranges skipping for travel expenses

Hi,
What could be the reason for missing numbers in the expense notes document range?
Sometimes the gap between 2 numbers is 10.
Thank you fro giving your feedback.
Kind regards,
Linda

Hi,
I have the solution:
SAP reserves a buffer for the document numbers.
Tcode SNRO - object RP_REINR.
If the application server shuts down, the numbers which are in the buffer (not assigned numbers) are lost.
This explains gaps in the number range.
The buffer can be removed, but this could influence the performance.
Kind regards,
Linda

PR Number Range skipping

Hello,
When I create the PR the number is 4000000001 instead of 4000000000. also for next PR the number generated was 4000000010 instead of 4000000002. When I check the current number is 4000000019.
Whereas in Quality server the PRs are having the sequential number. I have also checked the SNRO setting for buffering which is same in both Quality & Production server. Is there something I have missed while configuring.
Pls help me to rectify the same.
Thanks & Regards
Abhijit

you do not have any inconsistency.
the buffer is set to 10.
SAP takes 10 numbers into memory e.g. 40000010 to 40000019
when you save a PR, SAP takes the first number from the memory and saves your PO with that number.
you will see 40000010 in table EBAN, but 40000019 as last number in the number range.
if you create the next PR, then SAP uses the next number from memory.
you will see 40000011 in table EBAN, but still 40000019 as last number in the number range.
if you logoff, then SAP will loose the memory.
next time you start ME51N, it reads the number range and takes next 10 numbers into memory.
then you will see 40000020 in table EBAN after having saved, but 40000029 as last number in the number range.

Number range is skipping in MIGO

umber range is skipping in MIGO

dear bala,
This number range skipping may happen some time, the reason is bassed on buffer setting. check your buffer number range with help of basis consultant. and gothrough the buffer setting conecpt also.
reg
mrs

Vendor number range issue

Hi,
In testing server when i created a vendor it skipped number series sequence. Lastly vendor was created with xxxx50 but upon creation it created vendor with xxxx67, i have heard there is some problem with buffering settings in SNRO but when i look there i find it to be set as 5 then why system is skipping so numbers. Anyone can help me on it.

Hi,
Please ensure that none is using the system during the copy, this can generate this gaps
Also check note 175047:
In note 175047 you can find a summary about situations, where missing
document numbers (gaps) could occur. See also the referred notes at the
bottom of the note.
The possible and usual causes for the number range gaps are as follows-
   1. User exit USEREXIT_NUMBER_RANGE in program RV60AFZZ.
      Please check the user exit.
   2. Number buffering (which might not be applicable to your case)
      Please check transaction SNRO for object RV_BELEG to verify
      if buffering is switched on. Please refer to the attached
      note 62077, 23835 and 363901.
   3. Update termination
      This is the most likely cause of number range skipping.
      Please review trxn SM13 for update terminates during the run. If
      so, copy them in this message. Please also use trxn st22 to check
      whether shortdump occurred. If yes, upload the first 15 pages of
      the dump into this message.
BR,
Raquel

Number Range object skipping numbers SAP

Hi All,
Number Range object skipping numbers SAP "EINKBELEG" . While creating Purchase order with transaction code me21n, the purchase order is skipping odd numbers. I have checked the transaction code "SNRO" there is no buferring set on the object.
Please help

Are multiple users creating Purchase Orders at the same time?
If yes then this is possible. Because Number Range (unique Number) is assigned to Purchase Order at the start of the Transaction (ME21N).
Thus if multiple users are creating Purchase Orders at the same time & some of these users may have not saved the Purchase Order after partially creating it... This may lead to particular Number Range to be skipped as the following number is already assigned to some other Purchase Order.
Hope this helps,
Thanks,
Jignesh Mehta

How can prevent the number range of document skip

Dear friend,
     I want to preverify the cancel billing document process via VF11. If the FI period is closed, the cancel billing document (which refers to closed period) process is not permitted.
     I found the user exit: SDVFX001 (User exit header line in delivery to accounting) and implemented / activated it already.
     My user exit is work, the cancel process of old billing document is denied, but !!! I found that the number range of cancel document is reserved already (but the document is not create). So the number range of cancel document is skip in the next time when I cancel other billing document....
     Are there any exit or BTE to prevent this case?
Thank you in advances,
Sam.

Hi,
In your user exit itself, try finding out any FM available for closed period.
Thanks,
Sriram Ponna.

Number range skipping

Similar Messages

Maybe you are looking for