If a user tries to expand MRP tags, where the parent tag is for multiple recommendations, the system can become unresponsive and run out of memory.

From testing Sage have found that this is more apparent when there are large quantities of tagged demand, which have generated thousands of recommendations. Sage 200 does not attempt to cache any data fetched for a particular tag and so if it meets the same tag in the tree hierarchy elsewhere it will attempt to explode it again.

This is known issue 4618. A hotfix has now been released and should only be applied to Manufacturing sites that have Sage 200 2011 SP3.