cancel
Showing results for 
Search instead for 
Did you mean: 

PR NUMBERS ARE NOT IN SEQUENCE

former_member659143
Contributor
0 Kudos

Hi ,

We are facing an issue where Purchase requisition number created are not in sequence .

For e.g.Purchase requisition number 30087027 has been raised on 22.11.2011 and today's (23.11.2011) created purchase requisition number is 30086998 and 30086999.

So how this is happening .

My first analysis put me towards the Buffering of serial number .

Could you please guide me what will be the problem.

Thanks,

APR

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

Please check note 62077 Info: Internal number assignment is not continuous.

I hope this will help.

Regards,

Ashwini.

Answers (4)

Answers (4)

former_member182609
Active Contributor
0 Kudos

Hi Amit,

You are right,Please remove buffer in SNRO to 'ZERO' for the PR number range object then system will give continious numbers.

Thanks,

Former Member
0 Kudos

hi,

check the display number range of intervals omh7

chek the current number.

regards,

Ali

Former Member
0 Kudos

Dear,

Kindly check the PR number ranges and the number ranges assign to the document type.

Then,

This issue with the internal number range assignment occurs due to buffering in the application server.this can be adjusted using SNRO.

Just access transaction SNRO and enter the object type BANF (no ranges for pr), in change mode , in the menu bar, please follow the path Edit---> Set up buffering ---> No buffering and save changes.

Please also look at SAP NOTE 62077.

Please also take care that the following situations

- Gaps (jumps) occur when allocating internal numbers.

- The status of the number range does not match the number last

assigned.

- The number assignment does not match the insert sequence.

usually occurs due to buffering. Buffering increases the

performance of the application, since a data base access is not required

each time a posting is made, but it can cause jumps on the internal

number assignment. This is usually not a problem, since number range

buffering doesn't loose any guaranteed attributes. If your business

requirements are that the internal numeration has to be continuous, you

will have to disable buffering. In order to do this, please follow

these steps:

Menu path (or transaction SNRO):

Tools -> ABAP/4 workbench -> Development -> Other tools -> Number ranges

In the field "object" write "banf", select 'change' and deselect the

'main memory buffering' flag.

Please also see notes 62077 and the listing of related notes which may

be relevant to your situation.

According to the note

Causes for having large jumps in your system can be following:

- purchase requisitions are deleted

- several application servers (each server has buffered numbers) and

when system is stopped all buffered numbers are lost

- when running MRP in parallel, each work process gets buffered with

the number of "numbers" set up in SNRO for that number range

Another consideration for the large consumption of number is the MRP

setting for "Planning Mode". If this is set to "3" the system will

replan every non-firmed purchase requisition and give it a new number

It is recommended using planning mode 1 to minimize the impact on

system resources.

please see note 504200 that provides an explanation on

how the system behaves for purchase requisitions created by the MRP.

Hope this will solve your problem

Thnks & regards

Varun

Former Member
0 Kudos

hi,

go to snro in given number range object banf select dislay option .

see that how many numbers are in buffer place and make it as 0 in change mode and save.

Thanking you