We have an OnPrem customer with 200,000 items and many price changes (import via interfaces). Also with splitting into several price list headers the price list lines overflow in the quarter.

This is the first project where we have these problems. But we have many existing customers (old CAL World) that have huge price lists. So we will have this problem again and again in the future.

The proposed reorganization runs, are yes rather a stopgap, as we use them in the projects.

Already during the data migration of the V15 pricing to the new V16 pricing, we had a problem with the standard field “Line No.” in the table “Price List Line”. This is an integer and by counting up with 10000 in the function SetNextLineNo there was an error after 214748 new lines (Integer -2,147,483,647 to 2,147,483,647). For this we have requested a Handled Pattern event in the function SetNextLineNo.

Therefore we propose to change the field "Line No." to a BigInteger. We are aware that this has far-reaching consequences, but in view of the AutoSplitKey in the pages we have no better idea.