Solution : https://service.sap.com/sap/support/notes/409641 (SAP Service marketplace login required)
Summary :
This SAP Note explains how ROIDOCPRMS in the OLTP system and DataSource-specific settings in the scheduler influence packet size during data transfer. The packet size calculation involves a general formula: packet size = MAXSIZE * 1000 / transfer structure size, but it cannot exceed MAXLINES. Examples demonstrate the influence of MAXSIZE and MAXLINES variables in determining packet sizes, highlighting how different configurations and customizations impact general extraction performance. Conditions where packet sizes might vary due to extractor coding are also mentioned, indicating potential deviations from the calculated sizes.
Key words :
scheduler additional key words datasource default data transfer, packet size = maxsize 1000 \ transfer structure size, transfer structure size = 250 bytecontrol parameters, 000 maxlines - -calculated packet size = maxsize, 000calculated packet size = maxsize, data transfer influence, datasource specific settings, packet size depending, generic data extraction, bw oltp maxsize - 20
Related Notes :
| 1597364 | FAQ: BW-BCT: Extraction performance in source system |
| 549184 | FAQ: What is important for extraction |
| 482494 | Loading data from liveCache: Performance optimization |
| 417307 | Extractor package size: Collective note for applications |
| 157652 | Main memory requirement for extraction from R/3 |