Document Number not in sequence ...

Issue:

 

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.

 

Applicable for below TCODES:

 

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:

 

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 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.

 

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:

 

1. Start Transaction SNRO and enter the affected object.

 

2. Choose 'Change'.
3. Deactivate buffering: Choose 'Edit' -> 'Set Up Buffering' -> 'No Buffering'.
4. If you want to change the buffer size only, enter the corresponding value in the field 'No. of numbers in buffer'.
5. Save the changes.

 

Number range buffering can be activated or deactivated at any time.

Number range objects that have to be continuous due to legal.

 

For the following number range objects, gaps may cause:

 

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)

 

 

For other possible solutions, refer to the following notes: 37844, 23835, 179224, 678501, 599157 and 840901.

 

IMPORTANT: Read Notes 504875 and 678501.