The meaning of block size in middleware transaction code R3AC1

In the middleware transaction code R3AC1, the size of the block size can be maintained for a middleware adapter object.

Taking the size of 50 as an example, assuming that there are 110 devices in the ERP system (equipment) need to download, then the CRM middleware will automatically generate 3 inbound queue to perform the download task, 2 queues each download 50 devices, the other 1 queues to download the remaining 10 devices.

The transaction processing for these download queues is isolated from each other, meaning that the ERP device to be downloaded in this queue is not successfully stored in the CRM system, even if a queue has been downloaded incorrectly, but does not affect the processing of other queues.

My SAP Community Blog step by step-to-debug Product Initial Download in CRM system describes how to debug middleware on the CRM side, the function m that is processed on the CRM side inbound Odule can clearly see how this block size works: The number of rows that contain data from the ERP internal table =block size

To get more original Jerry's technical articles, please follow the public number "Wang Zixi" or scan the QR code below:

The meaning of block size in middleware transaction code R3AC1