# Infor LN PMC Solution and Patch Installation Checklist > Source: https://netray.co/tools/infor-ln-pmc-solution-patching-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A 5-stage checklist for installing Infor LN solutions and patches through PMC on an on-prem system, from reading the release notes to recording what is installed in production. ## Category infor-ln ## Erp Infor LN ## Audience - LN system administrator - LN technical consultant - LN developer ## Tool **Kind:** checklist **Groups:** #### Before download **Items:** **Text:** Read the solution or patch release notes and the linked KB article; note the symptoms fixed and any manual steps **Critical:** true **Text:** Confirm the base VRC the solution is built for matches the update VRC it will be installed in **Critical:** true **Text:** After scanning, view the dependencies from Process Solutions or Process Patches and list every prerequisite and co-requisite **Critical:** true Check whether any prerequisite is already installed, and order the missing ones Check whether the solution changes table definitions, which means table reconfiguration and longer downtime **Text:** Take a database backup and a backup of $BSE (or at least the application and dictionary directories) on the target environment **Critical:** true Freeze development in the affected package VRCs until installation and retrofit are complete Note the current list of installed solutions so the change can be reported and, if needed, reversed #### Installation in test **Items:** **Text:** Install into a test environment that is a recent copy of production, never into production first **Critical:** true Scan the delivered solution or patch file into PMC on the test environment Install solutions from Process Solutions (ttpmc2101m000) and patches from Process Patches (ttpmc2102m000) **Text:** Check that every solution shows status Installed; investigate any solution left in another status before continuing **Critical:** true Run the post-install steps the documentation asks for, such as converting to runtime or reconfiguring changed tables Review the PMC installation report and keep it with the change record #### Customization collisions **Items:** **Text:** List the objects in the solution (scripts, DLLs, forms, reports, tables) and compare them with objects present in your customer VRC **Critical:** true **Text:** For every object customized in a derived VRC, retrofit the standard change into the customized copy, because the customer copy shadows the update VRC **Critical:** true Recompile customized scripts and DLLs that include or call changed libraries Rerun tests for DAL and UE (user exit) code on tables the solution touches Check customized reports and forms whose standard version changed Record each retrofit with the solution number in the customization register #### Testing **Items:** **Text:** Test the sessions named in the release notes with the scenario the solution fixes **Critical:** true Run a short regression of related sessions in the same package Test BOD publishing and ION flows that involve changed objects Print the reports that use changed tables or scripts, on the real devices Run the Job Management jobs and AFS or DLL-based interfaces that touch the changed area **Text:** Get key-user sign-off on the test results before scheduling production **Critical:** true #### Production **Items:** Agree a change window and announce it to users and integration owners **Text:** Stop or hold Job Management jobs and inbound interfaces during installation **Critical:** true **Text:** Lock users out of the environment, then install the same solutions in the same order as in test **Critical:** true Restart bshells or the application server as the documentation requires so users load the new runtime objects Check the log files under $BSE/log for errors after installation Smoke-test the fixed scenario and two or three critical daily transactions Record installed solutions, date, installer and change number **Scoring Note:** Every critical item should be checked before production installation. If any item in Customization collisions is open, the solution is not ready for production even if it installed cleanly in test. ## Content **Intro:** This checklist covers installing Infor LN solutions and patches through PMC (Product Maintenance and Control) on an on-prem LN 10.x system. Work through it per solution or per patch, from reading release notes to recording what reached production. **Sections:** #### How to use it **Body:** Open a copy per change and tick items as they are done. Critical items block production. The groups follow the real order of work: read and check dependencies before downloading anything, install and retrofit in test, test, then repeat in production with the same solutions in the same order. Export the completed list to PDF or Excel and attach it to the change record so auditors and the next administrator can see what was checked. For a cumulative patch, treat the patch as one unit for installation but still review the solutions inside it for collisions with your own code. #### Where this lives in LN **Body:** PMC on the recipient side is in the Tools package. You scan a delivered solution or patch file into PMC, then install solutions in Process Solutions (ttpmc2101m000) or patches in Process Patches (ttpmc2102m000). From either session you can view the dependencies of a solution: the prerequisites and co-requisites that must be installed before or with it. Defining dependencies is a distributor-side task, used only when you build and deliver your own solutions, for example to transport customizations. Installed objects go into the update VRC connected in PMC; customer VRCs derived from it are not changed. **Bullets:** - Install solutions: Process Solutions (ttpmc2101m000) - Install patches: Process Patches (ttpmc2102m000) - Dependencies: viewed from either session before installing - Logs: $BSE/log on the application server #### Worked example: a solution that touches a customized script **Body:** A solution fixes rounding in a sales order line script. The release notes list two prerequisites, one already installed. You order the missing one, scan both, install the prerequisite first and then the fix in test. The object list shows the script also exists in your customer VRC because a developer changed it two years ago. Users running that session would still execute the customer copy, so the fix would appear not to work. The developer merges the standard change into the customer copy, recompiles, and the key user retests the original scenario plus normal order entry before the solution is scheduled for production. #### Gotchas **Body:** Most failed patch weekends come from three things. First, a missing co-requisite: two solutions that must be installed together were split. Second, customized objects shadowing the fix, as above. Third, table definition changes that trigger table reconfiguration on large tables and run far longer than planned. Check the release notes for table changes and time the reconfiguration in test on production-sized data. Some solutions can be uninstalled through PMC, but do not plan on it for solutions that change tables or data, so treat a backup as the real rollback. **Cta:** If you want your LN admins to ask in plain English which customized objects a pending solution touches, we can set that up on your own servers. **Faq:** #### Where do I find Infor LN release notes for a solution? **Answer:** Each solution on the Infor support portal has its own description and, where relevant, a KB article with symptoms, cause and manual steps. Release-level notes for a feature pack or update are on docs.infor.com and the support portal. Read both: the solution text tells you what changes, the KB tells you what else you must do. #### What is the difference between a solution and a patch in LN PMC? **Answer:** A solution is a single fix or change set. A patch bundles a set of solutions delivered together, often cumulatively. Solutions are installed in Process Solutions (ttpmc2101m000) and patches in Process Patches (ttpmc2102m000). Inside an opened patch you can see and handle the individual solutions it contains. #### How do I check which LN version and solutions are installed? **Answer:** Process Solutions and Process Patches show each solution with its status, so you can filter on Installed for an update VRC. The package VRCs used by your package combination show the base version. Keep your own register of installed solutions too, because it is faster for audits and comparing environments. #### Can I install a solution directly in production? **Answer:** PMC will let you, but it is a bad idea on any customized system. Customized objects in derived VRCs, missing co-requisites and table reconfiguration only show up when you install and test. Use a test environment copied from production and install the same set in the same order in both. ## Search terms infor ln release notes, infor ln administrator guide, infor ln latest version, infor ln pmc solution, infor ln process solutions, infor ln patch installation, infor ln upgrade, how to check infor ln version --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json