In CRQ the block size for EQUIPMENT is set as 50.
For example if you have 110 equipment to be downloaded from ERP, there would be 3 inbound queues generated in CRM, the first two will each import 50 equipment and the left 3rd queue imports the left 10 equipment. The transaction handling of each queue is isolated from each other, for example if there is some conrupt data on a given equipment in the 1st queue, the creation / update on the 1st queue ( 50 equipment ) will fail, however the left 60 equipment will still be successfully imported to CRM.
Screenshot from CRQ: the row number of internal table EQUI = block size set in R3AC1
update 2017-11-20 11:58AM
Middleware的download可以分块处理。 比如50个equipment，block size 设成5.那么就有10个queue，每个queue处理5个。每个queue的save是原子操作，queue与queue之间互不影响。我已经试过了。
R3AC1里默认的block size为50：
将其改为1，保存。
在R3AR2的request header里设置download 5个equipment:
之后能够观察到这5个equipment download 是分成5个queue分别执行的:
第一个queue里包含的equipment ID:
第二个queue里包含的equipment ID: