SAP ABAP Data Element KLETFILESIZE (Maximum File Size in MB)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ FREP (Package) RF reporting
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ FREP (Package) RF reporting
Basic Data
Data Element | KLETFILESIZE |
Short Description | Maximum File Size in MB |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | U_INT_4 | |
Data Type | INT4 | 4-byte integer, integer number with sign |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 10 | |
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 | Size/dim. |
Medium | 15 | Size in MB |
Long | 20 | File Size in MB |
Heading | 0 |
Documentation
Depending on the installation, the files created may not exceed a certain limit, for example, 2 gigabytes.
By specifying the required maximum size, the balance audit trail generates a new file once the limit has been reached.
Prerequisite: The last character of the physical file name must be a number.
Example: Physical name RFKLET00_01_A0, then RFKLET00_01_A1
is created.
When reading the physical file, you must start with RFKLET00_01_A0 again. The following files will then be opened automatically.
History
Last changed by/on | SAP | 20110901 |
SAP Release Created in |