MIRO document Number range buffering problem

Dear all,
My MIRO document number is not following the sequence. if my first 5 numbers come in a sequence, then the next 5 numbers are not coming in between. Instead, the next 5 numbers are coming. It might be due to number range buffering problem. How to find the number range object for MIRO document number range?
How to solve this?
Please suggest.
I will award full points.
Thanks & Regards,
AR

Hii,
You can search the Number Range object in T-Code: SNRO
The Number Range object for Invoice document is RE_BELEG
Go the Change Mode of the Number Range Object in SNRO, remove the No of Numbers of Buffers (by default it will be 10).
This will resolve your issue.
Regards,
Kumar

Similar Messages

MIRO document number range

Hello all,
We have different company codes in single client and we want each company code have diffrent set of Invoice document number. and seprate number range assignment i.e internal or external
But SAP standard support Invoice document number assignment based on financial year..
We want similar assignment as how number range has been assigned to accounting document based on Company code in FBN1..
Please help me, how I can customize this in my system?
Regards,
PAVAN

Hi
Hope this helps.
Re: how to assign INVOICE NUMBER RANGE TO ONLY ONE PLANT
Regards,
Maniraj

Document Number Range problem

Dear All,
Previously Document number range(FBN1) for Invoice was External, then i have changed to Internal number, now the problem is that in Counter it shows 1800000126 but system is showing document number 1800000136. Pls help on this & when i am changing from Internal to External system is showing error as "Lower limit can only be changed during Initial Entry".
Pls pls help on this.

Dear ranjith,
If you want to change number ranges from external to internal no ranges,
from T-code FBN1 you can for the changes first go to ,<change status button> and make you counter no as 0 and save the intervals,
and come to change intervals button and change the no ranges according to ur requirement.
Assign points.
SU

Best practice for Number range buffering in SAP BI for FI Cubes

Hello Experts,
I have a question regarding Number range buffering. What i have observed is if we use more number of background processes while loading data, it for sure creaets locks with NRIV table bcoz of more calls for bufffered numbers with multiple processes.
But there is a clause in SNRO while we buffer 'Main Memory' that it should not be used for Financial documents. I understand that this is for serial assignment of numbers for Documents and acoounts on the backend ECC, but does this even stand true for DIM ID's which we are buffering while loading data into a FI Cube?
I have looked up a SAP note 1398444, which talks about NRIVSHADOW and parallel buffering and different use case scenarios.
Which one of those should be used if I need to buffer my Dimension while loading a FI Cube in BI with maximun background processes?
Please help me understand the difference?

hi,
well the message is just like a warning to signify that incase you load more number of new records then your existing limit of buffer then you will have to increase accordingly if no then you can ignore
if you want to understand the reason it like this....
if there is not sufficent buffers space available and then process would be rollback and the existing numbers will get lost resulting gaps between the document numbers and for applications like finance this is not desirable .
see doc more details
http://help.sap.com/saphelp_nw04/helpdata/en/95/3d5540b8cdcd01e10000000a155106/frameset.htm
Also if you are not sure you ask your basis team for Early watch alert report in their you can easily see whether number range buffering is really required or not, if yes then for which object/dimensions
Also check below SAP Note:449030 and 62077
hope it helps
regards
laksh

Define document number ranges

Hi ,
i have problem with document number ranges .we have more company codes and each we specify the same ranges. e.g 19...for KR document for each company but there is a mistake with one of them.
i customise no 12 year 2010 from number 1900000 but
it should be no 19 year 2010 from number 190000
it effects our reports because it doesn't give 19000 for KR documents,i customised no 19 from number 26000 it gives 26000..for KR documents
may i change the ranges if we had an accounting entry?thanks your advices

You can change he number range, and it will not generate any posting.
But also it will not affect any existing entry, (Also take care to keep the current number status of the document number range correct, as no document can have same number.)
Regards,
SDNer

Document Number range autmatically getting updated

Hi,
I m in SAP ECC 6.0 and new GL concept is activated. I am posting a document. Document number is generated. But the update error is given. When i saw the document number range status in document number in general ledger view, the document number is updated to further 100 numbers.
For example:
Before document was psoted, current document status was 1800000100.
But after the document was posted, current document status was 1800000200.
Let me know why SAP is behaving in such a way. The above error is seen only in "Define Document Number Ranges for General Ledger View" and not in "Define Document Number Ranges for Entry View"

Here is SAP help text on buffering field.
Buffer flag
This ID determines whether the number intervals are buffered for assignements and checks.
Use
The number interval buffer is in the Shared Memory of the application server. Each buffer is used to store the external number intervals and a certain number (subinterval) of the internal number intervals. If the numbers of an internal number interval are used up, numbers are taken from the database via the number range server. The status of the number interval in the database is increased by the number of numbers fetched to the buffer.
Dependencies
When buffering number intervals, gaps may result in number assignment. Buffering is therefore not possible for applications, which require continuous number assignment.
Try removing the buffer, reset all transaction data (OBR1) and retest postings. If transaction data cannot be deleted, you should set the current number in SNRO to the most recent document number in BKPF/FAGLFLEXA and retest the postings.

Must I open the system to setup number range buffering ?

Hello community,
Number range buffering is disabled for DIM IDs on most of our InfoCubes, but we would like to experiment with turning it on according to the recommendations in this SDN blog :
/people/vikash.agrawal/blog/2006/04/05/load-lots-of-data-147faster148-with-buffering-number-range
I have imported a test cube into the production system and would like to test load the same quantity of data that is normally loaded into our production cubes.
But the problem when turning on Number Range Buffering for the test cube is that the production has status 'not modifiable'
Is it necessary to open the production system for modifications each time you want to make a change to the number range buffering settings ?
If so, then this will be difficult because we transport new cubes very frequently in order to separate the data by time period.
Is there a way to change the number range buffering settings via transport, or other customization without opening the production system for modifications ?

NRIV is the table that has the number range buffering info it.
http://help.sap.com/saphelp_nw04/helpdata/EN/7b/6eb2aa7aed44ea92ebb969e03081fb/frameset.htm
There appear to be a couple related tables.
Table Name      Short text
NRIV            Number Range Intervals
NRIVSHADOW      Local NRIV for multiprocessor machines
NRIV_LOKAL      Local NRIV for multiprocessor machines
NRIV_RESTE      Internal numbers not assigned in conn. wit
According to the doc on one of the linked help pages, you may want to look at Tran SM56. It says it will tell you how often a load had to wait because it had to wait to get the next available number. You might find that you are not waiting in any of your loads, in which case, this effort won't bear any fruit.
Personally, absent a specific set of instructions from SAP that indicate that yes you can transport this stuff and how to do it, I don't think I would pursue it.
Not to be negtive about this idea, but from what I have seen, the nbr range buffer objects don't share the same BID####### across systems. This seems like it would be a very large obstacle to overcome. I think will end up throwing lots of hours down a rat hole trying to do this.
But, who knows, if you get it to work, you ought to blog about it.
Good luck.

RV_BELEG - Number Range Buffering

Hi All: I implemented parallel number range buffering for my client via transaction SNUM for object RV_BELEG which includes orders, deliveries, invoices, contracts, etc. We did this because with the amount of users they have, when entering orders, they were getting short dumps upon saving orders and losing data. Changing to parallel buffering was suggested from SAP. It assigns a buffer of numbers to users as they log on or open sessions. The user groups entering orders, deliveries and invoices had no issues with these documents being out of sequence.
After we implemented this, the user group that enters contracts started to noticed that their document numbers were no longer sequencial and this is causing issues for them.
I have searched OSS and the web to find a solution so that you can stop a single number range, in our case, for the contracts, from buffering. All I have found is instructions on how to set up another number range for the same document type for certain sales orgs and then add the logic for this new number range and a custom talble in USEREXIT_NUMBER_RANGE. This does not apply where you have all contracts types being entered by multiple users accross multple sales orgs.
If anyone has any ideas, suggestions, solutions, please contact me.
Thanks,
Pam

Hi Pam,
As a suggestion, can you not make the buffer zero? I have made the buffer zero since the client was not particular on the buffer but they were very particular on the number range being sequential. They were ok with having the buffer as zero.
So perhaps you can try talking to your client on the same lines and convince them to have a zero buffer if possible.
Regards,
Rohan Gudavalli

External Document Number Range

Dear Forum,
We have an issue with the Document Number Range that has been defined in the system, according to which the document numbering is automatic. When the users post the entries for audit adjustments in the back date, the numbers jump, which becomes an audit issue. However, to resolve this the users want the externally controlled document number range, so that they have the option to chose the manual numbers. Another problem is that we are using the ledgers 0L as well as 1L, while the entries are posted in the leading ledger 0L, the same get replicated in the non leading ledger 1L and we want the external document number range in the non leading ledger 1L also.
Your prompt help would be highly appreciated as to how can we resolve the same.
Regards

Hi Dianne,
Your advice is quite helpful. I have one more confusion. The fiscal year for the leading ledger 0L is calender year and for the non leading ledger 1L is the year from April to March. Thus period 03 for 0L corresponds to period 12 of 1L. Therefore, to keep the 'external document numbers' same in 0L and 1L, would the following be corect way, say for year 2010 -
0L Year 2010 (Calender Year Jan to Dec) - External Doc nos. From 01 to 1000
1L Year 2009 (April'09 to Mar'10) - External Document nos. From 01 to 1000
Thus if the audit adjustmnets are posted on 31 March, 2010 with document no with 001 in 0L, it would appear with same document no. 001 in 1L on 31 March, 2010. In ledger 0L it will be in period 3, but in ledger 1L it will be in period 12.
Would really appreciate your help.
Regards,

Error in purchase document number range

good wishes sapgurus,
while creating PO via requisition assignment using t.co.me58.
I am getting this error
   *Document number range (i.e PR no.)is not within the defined number ranges*.
I have followed all the steps in this method of creating PO.
I have verified number ranges(which is defined as internal number ranges by default) defined in IMG PR Define number ranges as well as Document type   number ranges.
I seen that the PR number which i created falls within the defined number ranges.
I have tried by defining different number ranges with creating different PR's whose number range is
    within the defined number range.
     But my problem is that The error message is recurring and i stuck up there
      hence pls gurus help me in overcoming this error message
        thank u

Hi Rishi,
   Are you able to create PR then u can go ahead for PO creation
1.) Hope you might be given number range as external so that system is looking for that pattern of number range, plz check thoroughly.
2.) At the node of the define document type for PR use standard document type NB and use the same number range so this error will not get repeat.
Please let me know for futher details
Thanks...
Srini Rao

Number Range buffering size increase.

Hi All,
How to analyze whether to increase number range buffering size for the simple infobject. For dimensions and masterdata we can check number of data records loaded. But to analyze for infoobject if it is not master data, whether to increase the buffering size or not. And what is the maximum limit of increasing the size.
Regards,
Asim.

Hi,
Yes I have gone through the documents it is discussing about dimension and master data object.My doubt is how to analyze whether to increase the buffering size of simple infobject.
Thanks,
Asim

Number Range Buffering - SNRO

Hi Gurus,
             Can any one Plzz tell me why do v go for Number Range Buffering?
It's use?? And the procedure to do it? I searched it in forum but didn't got what I needed.
Cheers,
Sultan.

hi,
Tip on Number Range Buffering :
When you load large quantities of data in an InfoCube, the number range buffer should be increased for the dimensions that are likely to have a high number of data sets.
To do this, proceed as follows. Use function module RSD_CUBE_GET to find the object name of the dimension that is likely to have a high number of data sets.
Function module settings:
I_INFOCUBE = 'Infocube name'
I_OBJVERS = 'A'
I_BYPASS_BUFFER = 'X'
The numbers for the dimensions are then contained in table 'E_T_DIME', column 'NUMBRANR'. If you enter 'BID' before this number, you get the relevant number range (for example BID0000053).
You can use Transaction SNRO (-> ABAP/4 Workbench -> Development --> Other tools --> Number ranges) to display all number ranges for the dimensions used in BW if you enter BID*. You can use the object name that was determined beforehand to find the required number range.
By double-clicking this line, you get to the number range maintenance. Choose Edit -> Set-up buffering -> Main memory, to define the 'No. of numbers in buffer'.
Set this value to 500, for example. The size depends on the expected data quantity in the initial and in future (delta) uploads.
!! Never buffer the number range for the package dimension !!
Also heres the content of the note : 857998
The number range buffering for DIMid's and SID's
a) the DIM table increases by a large number of data records for each request
b) the size of the DIM table levels out but at the beginning you expected or observed a significant increase
c) there are many accesses to the NRIV table with reference to the number range object of the dimension table
d) the InfoCube or the dimension table is deleted regularly and, therefore, the DIM table increases significantly in each period.
The number range object for the SIDs of an InfoObject should be buffered if
e) you regularly add many new data records to the SID table
f) you know before the initial load that there is a lot of master data to be loaded for this InfoObject
g) you delete the master data periodically and you always load many new records (this should be an exception).
How do you find number range objects of the dimensions and SIDs whose number range should be buffered?
h) You know in advance that the dimension table or the SID table will increase significantly per request.
i) You observe accesses to the NRIV table and you can determine the number range object directly in the current SQL statement.
j) A high number range level may indicate that there is a significant increase for these two BW objects (valid only for BID* and BIM* objects)
                       SE16 'NRIV'
-> OBJECT = 'BID' or OBJECT = 'BIM'
                       displays all number range objects with number level (NRLEVEL).
                       Export this output to an Excel document and sort NRLEVEL in descending order. Most candidates usually have a high number range level.
                       You can determine the corresponding dimension tables by using the table RSDDIMELOC. You can find the InfoObject for SIDs using the table RSDCHABASLOC (the field NUMBRANR contains the last seven digits of the number range object). The procedure is even more effective if you read the table NRIV periodically and you determine the changes using NRLEVEL.
k) Another indicator is if a dimension table or an SID table significantly increases on a regular basis.
                       How many instances should be buffered?
In the past, a value between 100 and 500 has proved to be efficient. If there is still a high load for these number range objects on the table NRIV, you can increase the value.
Caution:
- Never buffer the number range object of the package dimension table of a data target.
- In addition, never buffer the number range object of the request ID (RSDCHABASLOC-CHABASNM = 0REQUID), generally BIM9999998.
- Ensure that not all dialog processes are occupied permanently
hope this helps
Regards

Number range buffering for SES

Hi,
My client has problem of missing SES numbers. This could be because of number range buffering configuration.
I want to avoid missing SES numberings in future. How can I establish ?
Is it through SNRO, if yes please explain what setting to be done

Gentlemen,
Please advise.
regards
NB

AFAB:AA776 "Create document number range ## using internal number assignmen

Good afternoon
I ask for your guidance to see if anyone knows me that is generating errors in the transaction AFAB AA776 "Create document number range ## using internal number assignment", the peculiarity of this is that I'm in an environment that is proving to migrate V5 to V6 ranges in environment QAS is marked as external and no problems to run on v6 change in SAP itself. Test by removing the flag marking for external control and run, causing an alarm is that it does not work as in my QAS v 5 and that I should remove this flag is removed and remove it in all the years this range of numbers is that it can hurt if you make this change.
Can anyone guide me please.
Thanks for the support.
good day

Hello ,
Kindly have a look at the below notes that will help you resolve the
issue :
890976 - Converting closing report to internal doc number assgnmnt
If note 890976 has been applied in your system already (package
level is = or > SAPKH60005), so what you need to check is the
following :
In transaction FBN1, in your company code you should see that the
period and number range in question is ticked as external.
Please untick the indicator for "External" and press enter. If this
box happens to be uneditable then untick the number range for the
previous year and press enter. All other entries will update
automatically.
Here is a brief explaination to why this change has been made:
Before ERP2005(RAPOST2000 exists as of release 4.70)the number usage
was external, because RAPOST2000 internally managed the document number
handling. As this was not possible any more with the New General Ledger
functionality, and as the usage of internal number ranges is much
simpler and more efficient, we changed the number range management
inside RAPOST2000 (and by the way also the new periodic posting report
RAPERB2000).
Please kindly check the attached notes 683313 for your reference.
I hope this provides some clarification.
regards
Ray

Document number range not creating in Ecc 6.0

Hi
I have tried creating document number range in 6.0, but the change interval buttion is in display mode and not in the change mode, so not able to cretae number range. Any input.
Urgent please help.

Hi Sidhu,
It could be the limit of the authorization.
So try to check whether you have an authorizatin to change the interval or not.
Hope it helps.

MIRO document Number range buffering problem

Similar Messages

Maybe you are looking for