SAP ABAP Data Element ARCH_PACSZ (Package Size)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-CCM-ADK (Application Component) Archive Development Kit
⤷ SARC (Package) Archive Development Kit
⤷ BC-CCM-ADK (Application Component) Archive Development Kit
⤷ SARC (Package) Archive Development Kit
Basic Data
Data Element | ARCH_PACSZ |
Short Description | Package Size |
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 | 15 | Pack. Size |
Medium | 15 | Package Size |
Long | 20 | Package Size |
Heading | 10 | Pack. Size |
Documentation
Definition
A unit, which determines how many resources are to be processed in one block by the delete program (between methods PICK_RESOURCES and CONFIRM_DELETION).
Use
The package size influences the runtime of a delete job. There is no such thing as an "optimal" package size; the smaller the resource, the larger should be the value for package size. Also, the overall duration of the delete phase depends on the number of delete jobs that were started in parallel. As a general rule one can say that with fewer data objects to be archived, a smaller package size would result in a more equal distribution of files between the delete jobs.
Dependencies
Example
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in | 640 |