I faced a serious problem with mass processing of activities using FM CRM_ORDER_MAINTAIN.
The problem is that when my program is running it takes to much memory on the server (from 20M to 100M for processing 1000 and more activities, the extended memory is increasing by blocks). From each call of CRM_ORDER_MAINTAIN I create 10-20-20 activities. The FM's calls are the following:
CRM_ORDER_READ (read and change data from template)
COMMIT WORK statement
Does anybody have such experience with mass processing with CRM_ORDER_MAINTAIN or faced the same problem?
Thank you and best regards,