Incident/Accident number range

[Former Member]

Hi

Facing one issue specific to incident/accident number range. After creating incident, system is giving autogenerated internal no. with gap of 10 ( eg 0000000000011, 00000000000021, 0000000000031). Then after creating 1-2 incidents, it start giving counitnution series of 3-10 progressing 1 every time (Eg. 00000000000000013, 00000000000000014 and so on till 0000000000000020). After 000000000000020 next number with gap of 10 and then after creating 1-2 incidents, countiution series of 3-10 again. Not able to understand this phenomena, where few numbers are missed by system and then taking back again.

if any body has idea, please revert back.

Regards

Vikram

[nirajsikligar]

Hello Vikram,

This phenomenon is because of the buffering of the No. ranges.

number range buffering is one way of SAP to make a quick access to the next sequential number for a particular document(in your case it is Incident / Accident no. range document object).

The mechanism(when number range buffering is activt) is as follows:

· During startup of the SAP system, a block of sequential numbers are picked up from the relevant customizing table and the transactional data table and these numbers are buffered in the main memory for quicker access.

· During the course of the system operation, these numbers are consumed during the relevant transactions. As soon as all the numbers are consumed during normal transactional operation, another sequence of numbers are picked up into main memory.

· If for any reason, only a few numbers from this block are consumed during transactional processing before a system shutdown, the system assumes that all the numbers have been used up and hence you miss out the intermittent numbers(They are no more usable).

You can disable the buffering by using Tcode SNRO and enter CBIHN_IAID and disable the buffering for this no. range with a very nominal hit on the performance. The performance hit happens because every time you create a new document, the system goes down to the relevant customizing table and the transactional data table to find the next number available. The performance hit is very miniscule and you wouldnu2019t even notice it.

Please take help of your Basis person for the same.

Hope this information i sueful to you.

For No. range object in EHS please visit IMG activity : Number Range Objects in EH&S Under EHS node.

Thanks and Regards,

Niraj

Edited by: Niraj Sikligar on Jun 7, 2010 9:25 AM