Hierarchy
SAP_BW (Software Component) SAP Business Warehouse⤷
BW (Application Component) SAP Business Information Warehouse⤷
RS (Package) BW: General Business Information Warehouse
IMG Activity
| ID | BW_RSADMINCV6 | Threshold Value for Data Loading |
| Transaction Code | S_BR3_49000040 | (empty) |
| Created on | 20000217 | |
| Customizing Attributes | BW_RSADMINCV6 | Threshold Value for Data Loading |
| Customizing Activity | BW_RSADMINCV6 | Threshold Value for Data Loading |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | BW_RSADMINCV6 |
1. Frequency with which Data IDocs are sent
With this frequency you can determine how many Data IDocs are to be sent to an Info Doc, or how many Data IDocs are to be described by an Info IDoc.
Dependencies
Info IDocs contain, among others, information on whether the respective Data IDocs were loaded correctly. You can use each Info IDoc in the Monitor to establish whether the loading process is running without errors. If this is the case for all Data IDocs described in an Info IDoc then the traffic light in the Monitor will be green.
Standard settings
Frequency 1 means, for example, that an Info IDoc succeeds each Data IDoc. You should generally choose a frequency between 4 and 10 but no greater than 20. Info IDocs contain, among other things, information on whether the relevant Data IDocs were loaded correctly.
Recommendation
The larger the packet size of a Data IDoc, the smaller you should set the frequency. This will help you obtain information on the respective data loading status at relative short intervals.
2. Packet size for IDocs
This option refers to the number of data records that are delivered from a flat file to an IDoc when uploading.
The basic setting should be between 5000 and 20000, depending on how many data records you want to load.
Activities
If you want to upload a large amount of transaction data using the IDoc loading method, change the 'Number of data records per IDoc' from the standard value of 1000 to a value between 10000 (Informix) to 50000 (Oracle, MS SQL Server).
Dependencies
The IDOCS can be imported in the background in parallel into BW. Through more efficient use of the system resources (uploading is divided into several processes), uploading in parallel is the most cost-efficient from a performance point of view.
Recommendation
You should not divide the data into too large a number of IDocs, as this can have a negative effect on the performance when uploading.
There should be no more than 100 IDocs in each loading process.
Business Attributes
| ASAP Roadmap ID | 899 | not to be assigned |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | BW_RSADMINCV6 | 0 | ARS0000022 | Warehouse Management |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| RSADMINCV6 | V - View | RSCUSTV6 |
History
| Last changed by/on | SAP | 20000217 |
| SAP Release Created in | 20B |
