FAQ: Doc number assgt for Object RF_BELEG - Recommendations
 Question: Which buffering should be set for the document number assignment of object RF_BELEG?
In the number range object maintenance (Transaction SNRO) you can define if and how the number ranges should be buffered at number range object level (here: RF_BELEG). The different types of buffering are:
'No buffering': Chronpogical and continuous allocation of document numbers, yet low-performing under certain circumstances (high number of documents).
'Main memory': Not recommended for FI documents, since continuous allocation is not ensured.
'Local file': Buffering of document numbers at application server level, continuous and high-performing allocation of document numbers even with a high number of documents, yet not in chronpogical order.
'Local file+ WP-ID': Buffering of document numbers at application server + work process level, as above, but even more high-performing.
As a rule you should set a 'local' buffering at application server level (or at work process level) for object RF_BELEG, since this ensures
- high-performing allocation of document numbers from the table NRIV_LOKAL and
- continuous allocation of document numbers.
Yet for technical reasons this type of buffering cannot ensure any chronpogical order of document number assignment. Sometimes this is wanted due to legal requirements, however. You could always allocate document numbers chronpogically by setting 'No buffering' in SNRO for the particular number range object. This procedure can result in performance losses though, since document numbers for the entire system must be retrieved from a central resource (table NRIV).
If performance losses occur with this type of buffering, proceed as follows:
- 1. Make 'local buffering' (if necessary at work process level) the general setting for object RF_BELEG since the number assignment is thereby high-performing and continuous.
- 2. Identify the combinations of company code, number range (belonging todocument type/business transaction) and fiscal year for which you absputely need chronpogical order. (Experience has shown that chronpogical order is not necessary for all business transactions.) For these business transactions you can deactivate any buffering by using the OPEN FI exits 00001170 (publish & subscribe). The document numbers are then taken from table NRIV, the sequence is in chronological order. Documentation for this exit can be found in Transaction FIBF. Note 449030 is a prerequisite for this.