Hierarchy

⤷

⤷

Basic Data
Data Element | /LIME/ARCHV_MAXSIZE |
Short Description | Maximum Number of Objects Allowed in an Archive File |
Data Type
Category of Dictionary Type | Direct Type Entry | |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ||
Data Type | INT4 | 4-byte integer, integer number with sign |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 11 | |
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 | Max. Size |
Medium | 15 | Maximum Size |
Long | 20 | Maximum Package Size |
Heading | 35 | Maximum Archiving Package Size |
Documentation
Definition
Controls the Maximum Number of Data Objects per Archive File
Use
Before a data object is written into an archive file, the system checks whether the maximum allowable number of data objects has been exceeded. If this the case, then the system closes the current archive file and opens a new one, which then accepts the data object.
If you do not enter a value here, the system determines a default value of 100.
Dependencies
Changes to this parameter also affect the performance of the archiving procedure. When the write program completes an archive file, this automatically starts the delete program - if specified in Customizing - which reads this file and deletes the data in the database.
The smaller the maximum number of data objects in a file, the more likely it is that several delete jobs are active parallel to the Several background processes are required for this. The parallel processing of the delete operation can to a certain extent prove to be beneficial.
Example
History
Last changed by/on | SAP | 20050131 |
SAP Release Created in | 400 |