Hierarchy
FI-CA (Software Component) FI-CA⤷
IS-U-TO-MI (Application Component) Migration⤷
EEMI (Package) IS-U Migration
Basic Data
| Data Element | EMG_MASSRUN_SIZE |
| Short Description | File size for mass import |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | NUMC5 | |
| Data Type | NUMC | Character string with only digits |
| Length | 5 | |
| Decimal Places | 0 | |
| Output Length | 5 | |
| 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 | MI size |
| Medium | 15 | MI file size |
| Long | 21 | Mass import file size |
| Heading | 0 |
Documentation
Definition
File size in the number of data objects for distributed import.
Use
During distributed import, the import file is divided into files of this size in order to achieve maximum utilization of the system resources.
Dependencies
You should choose this number depending on the migration object. Migration objects with a high throughput should have a larger file size than objects with a low throughput. An optimal value for the individual migration objects must be determined in the project. This value is heavily dependant on the system environment and Customizing.
Example
Execute the import for migration object PREMISE with a file size that is larger than 1000 (for example 5000).
You should start the import for migration object INST_MGMT with file sizes of approximately 1000 data objects.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in | 463 |
