Sage 200 MRP BoM costing out of memory error

Hi,

We have about 8000 BoM's in our MRP system and we have been trying to get them costed for quite a while. But every time we try and do a full cost roll up, it errors with an out of memory exception error. 

Now I know you can do them by product group, or even by BoM groups, but we have some product groups that have a lot of BoM's in and will probably find this difficult. In terms of BoM groups, I know they can be created, but I have to add them one at a time. Is there no way to mass group an amount of BoMs together rather than having to add one at a time. 

We have been talking to our Sage consultants and they are not sure why its happening, which is why I am posting here. 

We are running Sage 200 12.00.0041 which was installed about a month ago and the database server and the application server has loads of resources. We have tried to run this on the server when we were running the previous version of Sage and it still failed. 

Any idea? 

Cheers.....Derrick

  • 0

    Hi Derrick,

    There's a known issue which sounds similar to yours:

    ID 6430 Issue Details

    Costing finished items when there are a lot of finished items being processed results in an Exception of type 'System.OutofMemoryException' was thrown.

    To Replicate
    1. Using data with a large number of finished items (8,000 +)
    2. Go to Bill of Materials > Processing > Cost
    3. Click on the down arrow next to Add and choose to Add all Bill of Materials
    4. Once the finished items are all listed click Cost

    Observed Behaviour
    Processing begins with the Preparing stage. The system then processes between 8000 and 9000 finished items and then displays the error:

    Exception of type 'System.OutofMemoryException' was thrown.

    Expected Behaviour
    For you to be able to cost all finished items in one go.

    Workaround
    To cost finished items in smaller batches - based on testing here 5000 - 6000 per run should be a safer number.


    The issue was first reported in Sage 200 2013 (it may have been present prior to that) and it is still outstanding as an issue.