Академический Документы
Профессиональный Документы
Культура Документы
Help
continuous
SAP Note Number
Print
Text
62077
Note Language
Display Versions
SSCR
Header Data
Release
Correction Instructions
Support Packages
>>
Symptom
The status of the number range does not match the number last assigned.
If an application server is shut down, the numbers that were 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 was not yet transferred to an
application server for intermediate buffering. The current number level does not therefore display the number of
the "next" object.
The current number level (per server) can be displayed with Transaction SM56. Start Transaction SM56 and
branch into 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 several application servers are used, the chronological insert sequence is not determined by the numerical
sequence on the individual hosts, due to the separate buffering on the various servers.
Buffering the number range objects has a positive effect on the performance as no database access (on the number
range table NRIV) is required for every posting. Furthermore, a serialization of this table (database blocking) is prevented
to a large extent so that posting procedures can be carried out in parallel.
Solution
As the number range buffering does not lose any guaranteed attributes, a correction is not required.
If you still require a continuous allocation, you can deactivate the number range buffering deliberately for individual
objects.
Proceed as follows:
-
Please note that this change is a modification. The modification is overwritten as soon as the affected
number range object is redelivered - that is, you must check the change manually after every import of a
maintenance level.
For the the following number range objects, gaps may cause user insecurity as a sequential numbering is 'expected':
Area CO:
- RK_BELEG (CO Document)
Caution: Note that the problems described in notes 20965 and 29030 can occur if you deactivate the buffering.
- COPA_IST (Document number during actual posting)
- COPA_PLAN (Document number with planned posting)
- COPA_OBJ (Business segment number)
Area FI:
- DEBITOR (Customer master data)
- KREDITOR (Vendor master record data)
Area HR:
- RP_REINR (Trip numbers)
Area PM, PP, PS
- AUFTRAG (Order number, Production, Process, Maintenance order
number, network number.)
- QMEL_NR (Number range message)
Area MM:
- MATBELEG (Material documents)
- MATERIALNR (Material master)
Area QM: