There are 100 invoice proposals need to be generated. 10 Threads are available. Current code in standard allocates 10 invoice proposals to each thread, based on the pure number of invoice proposals, equally spread. Our issue: The proposals do have significant deviations in their size, because of our business is dealing with few very big customers and lots of smaller customers. What we saw multiple times now is a scenario where we ended up with one of the thread being loaded with multiple “big” proposals, while all other threads only got the little ones. So all but one thread will finish in time, while this one thread basically runs with the full load of data. So long story short, the system ends up in a semi-single thread situation. Repro steps: Pre-requisite to create the Project invoice proposal •Our invoice preparations are created for related Project nodes Use function Create project invoice proposal from Project management and accounting>Periodic>Project Invoices •Use late selection •Select "Invoice grouping setup ID" In "records to include" filter on one or a combination of the following •Project Contract ID (range) •Classification code •Project invoice interval pattern

Under Review
Ideas Administrator

Thank you for the suggestion! This has been added to our roadmap and will be considered for a future release.


Kim Nelson

Program Manager, Project management and accounting