Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-SRV-NUM (Application Component) Number Range Management⤷
SZN (Package) R/3 Central Basis Development: Number Ranges
Basic Data
| Data Element | NRBUFFER_S |
| Short Description | Flag whether interval is to be saved in a local file |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR1 | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Buffer |
| Medium | 15 | Buffering |
| Long | 20 | Buffering |
| Heading | 0 |
Documentation
Definition
The indicator determines whether the number intervals for assigning numbers are buffered in a "local" file.
Use
The number (sub)intervals are managed in an additional file.
If the buffering method 'Local File' is used, the server name forms part of the key.
If the extended local buffering method 'Local File with Work Process ID' is used, the work process ID is included in the key in addition to the server name. For each work process on every server, a separate number package is buffered in the local file. This ensures that database locks are almost completely avoided.
If there are no numbers of the subinterval left in the local file, some numbers are fetched from the database. The level in the database is increased by the number of numbers that were imported into the local file.
Procedure
Examples
Dependencies
The numbers are not assigned in chronological order. The gaps (the numbers that are not assigned) cannot be shown in an analysis report.
History
| Last changed by/on | SAP | 20040312 |
| SAP Release Created in | 640 |
