Most if not all of the organizations I've been involved with apply them only as "needed". Here are some points you also may want to take note of:

1) Test any and all patches before they are applied to Production. Get approval and sign off on the patches (if needed) before moving them to production. I think this applies to most organizations but no one has the manpower to keep up with the daily/weekly patches. Many patches you may not need or use.

2) Any critical environment patches, you need to be aware of. Sign up for emailing of the notice of those critical patches from mylawson.com. All critical notices are also within mylawson.com.

3) Also become involved with your Lawson user groups so you can connect with other organizations which use Lawson.

Roger

I strongly recommend applying patches only as "needed". The bundled patches are breaking things left and right. I wish lawson would put more people in QA before releasing patches. For example, I applied a patch to address an issue with laser print output recently and it broke AC activity validation. I am still working with lawson on this with an open case...

I resisted to put this particular "bundled" patch in because it's just a small laser print issue. I argued to no end and I was assured by 2 lawson support that this patch will not cause problem. I waited month(s) until I could not delay any further to fix the laser print issue. Then guess what? The patch caused problem. On top of that, each payroll run now, with the bundle patch, it creates additional laser print PMTOUTI files for the iseries. We are not even on the iseries platform. Fun!