# Infor M3 LCM Fix and Cumulative Update Checklist > Source: https://netray.co/tools/infor-m3-lcm-fix-and-cumulative-update-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Checklist for applying M3 Business Engine fixes and cumulative updates on an on-prem M3 13.x system through Lifecycle Manager, including MAK retrofit and regression checks. ## Category infor-cloudsuite ## Erp Infor M3 ## Audience - M3 system administrator - M3 technical consultant - M3 developer ## Tool **Kind:** checklist **Groups:** #### Prepare **Items:** Download the fixes or cumulative update from the Infor support portal and store them with the change record **Text:** Read the fix documentation for prerequisites, manual steps and affected programs **Critical:** true **Text:** Check the current fix level of each environment in LCM and confirm the fix applies to it **Critical:** true List MAK modifications that touch programs or objects changed by the fix **Text:** Back up the database and the M3 installation (LCM-managed files) of the target environment **Critical:** true Freeze MAK development until the fix is applied and retrofitted Plan the order if several fixes or a cumulative update plus individual fixes are involved #### Apply in test **Items:** **Text:** Apply in a test environment refreshed from production, never in production first **Critical:** true Install the fix through LCM and keep the LCM log **Text:** Merge the fix into affected MAK modifications, rebuild and redeploy them **Critical:** true Restart the M3 BE grid applications or subsystems the fix documentation names Refresh H5 caches as the documentation describes and ask testers to clear browser caches Run any manual steps from the fix documentation, such as data conversion jobs #### Verify **Items:** **Text:** Retest the scenario the fix addresses **Critical:** true Run MI regression for the MI transactions your integrations use, comparing outputs before and after Run H5 scripts on the programs and panels changed by the fix Run MEC maps for the affected message types with saved test files Smoke-test key programs: MMS001 item, OIS100 customer order, PPS200 purchase order, PMS100 manufacturing order Run the scheduled batch jobs that touch changed areas **Text:** Get key-user sign-off **Critical:** true #### Production **Items:** Agree a maintenance window and notify users and integration owners **Text:** Stop or hold inbound integrations and scheduled jobs **Critical:** true **Text:** Apply the same fixes in the same order as in test, with the same MAK builds **Critical:** true Restart the grid applications and check they start cleanly Smoke-test the key programs and one inbound and one outbound integration Monitor the grid logs and job results for the first business day #### Close **Items:** Record the new fix level per environment Update the modification register with any MAK merges Update documentation and test scripts with what changed Note lessons for the next fix window, including actual downtime **Scoring Note:** Critical items protect against the two common failures: a fix that overwrites a MAK modification's behaviour, and production differing from what was tested. Do not start the production window until every critical item in Prepare, Apply in test and Verify is checked. ## Content **Intro:** This checklist covers applying M3 Business Engine fixes and cumulative updates on an on-prem Infor M3 13.x system through Lifecycle Manager. It adds the MAK retrofit and regression steps that keep modifications and integrations working after the fix. **Sections:** #### How to use it **Body:** Open a copy per fix window. Group the fixes you plan to apply, read their documentation and list the affected programs before anything is installed. Work through Apply in test and Verify fully, then repeat the exact same fixes and MAK builds in production. Critical items block the production window. Export the result to PDF and attach it to the change, together with the LCM logs. The Close group is what makes the next window faster: a known fix level per environment and an updated modification register. #### Where this lives in M3 13.x **Body:** On-prem M3 13.x is installed and maintained through Lifecycle Manager (LCM), which manages the M3 Business Engine and other grid applications per environment and is where you see installed fix levels. Java modifications are developed and deployed with the M3 Adaptation Kit (MAK); when a fix changes an object you have modified, the change has to be merged into the modification and the modification rebuilt. The H5 client, MI programs and MEC all sit on top of the Business Engine, which is why the Verify group tests all three, not just the screens. #### Worked example **Body:** A cumulative update corrects pricing in customer order lines. The fix documentation lists changed objects used by OIS100. Your register shows a MAK modification on one of them that adds a discount check. In test, the administrator applies the update through LCM, the developer merges the standard change into the modification and redeploys it, and the grid applications are restarted. Testers run order entry with and without discounts, an EDI order through MEC and the order-line MI transactions used by the web shop. All pass, so production gets the same update and the same MAK build in the next window. #### Gotchas **Body:** The most common problem is a modification built against the old object that silently undoes the fix, so the fix appears not to work. The second is browser and client caching after panel changes, which makes testers report errors that are not there. The third is applying a slightly different set of fixes in production than in test because a new fix was released in between. Freeze the list at the start of testing and move new fixes to the next window unless they are urgent. **Cta:** If you want your M3 team to ask in plain English which modifications and integrations a fix touches, we can set that up on your own servers. **Faq:** #### What does an Infor M3 technical consultant check before applying a fix? **Answer:** Prerequisites and manual steps in the fix documentation, the current fix level per environment in LCM, and which MAK modifications touch the changed objects. They also confirm backups exist and that the same fix list will be applied in test and production, in the same order. #### Do MAK modifications need to be redone after an M3 update? **Answer:** Only those that modify objects the update changes, but those must be merged and rebuilt. If you skip it, either the fix is lost because your modified version runs, or the modification breaks. A modification register listing changed objects makes this check quick. #### How often should on-prem M3 be updated? **Answer:** Many sites apply cumulative fixes on a regular cycle, for example quarterly, plus urgent individual fixes as needed. A regular cycle keeps each window small and testable. Long gaps mean larger fix sets, more MAK merges and bigger test scope each time. #### What should be tested after an M3 BE fix? **Answer:** The scenario the fix addresses, the MI transactions your integrations use, H5 scripts on changed panels, MEC maps for affected message types, key programs such as OIS100, PPS200, PMS100 and MMS001, and the batch jobs touching changed areas. ## Search terms infor m3 technical consultant, infor m3 update, infor m3 on premise, infor m3 on prem, infor m3 support, infor m3 lifecycle manager, infor m3 mak, infor m3 fix --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json