# How to Check the Infor LN Version and Current Package VRC > Source: https://netray.co/erp-help/how-to-check-infor-ln-version-package-vrc > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer An Infor LN installation has four separate version facts: the application release and feature pack, the porting set that carries the bshell and database drivers, the package VRC that each user or company runs, and the installed solutions. The release is shown in the Help > About dialog of the client, the package VRC in the Tools package administration sessions, and the porting set on the server through the installation tooling. ## Kind how-to ## System infor-ln ## Erp Infor LN (Baan) ## Module Tools / Application Administration / Software environment ## Query how to check infor ln version ## Alternate Queries - current package vrc infor ln - infor ln feature pack version - infor ln porting set version - which package vrc is infor ln using ## Applies To Infor LN 10.x (all feature packs) and Baan IVc / Baan 5 style package VRC administration; menu names vary slightly by version ## Steps ### How to find each LN version **Items:** In the LN UI (Web UI or Worktop) open Help > About. It shows the product release and feature pack level, for example Infor LN 10.7 with its feature pack, and the build of the client you are connected to. Open the Tools module and look for the package administration sessions (Package VRCs, Package Combinations, and the user data session that links users to a package combination). Search by description with the session search because session codes are easy to misremember. To see the package VRC a specific user runs, check the user data in Tools and the package combination attached to that user's company or user template. The package combination decides which VRC the user's sessions come from. To see which VRCs exist in the software library, list the Package VRCs session and read the VRC names. Standard VRCs follow a release-letter pattern such as B61 or B61U for the standard layer, with customer VRCs derived from them via the derived-from field. On the server, locate BSE (the environment variable that points to the Baan software environment) and read the installation records kept under it, or run the installation or porting-set information tool delivered with your install. Ask your Infor partner for the exact utility name on your platform. Record the porting set version separately. It determines the bshell and database driver behavior and is patched independently from the application, so a support case needs both numbers. For solutions, open the Infor LN installation or solution administration session and list the installed solutions and their numbers. Support will ask for these when matching a defect. Write all of it in one change record: release, feature pack, porting set, package VRC chain, installed solutions, and date. It is the first thing any upgrade or support case needs. ## Sections ### What each number actually tells you **Body:** The release (for example 10.5, 10.6 or 10.7) and feature pack tell you which functionality and which published documentation applies. If a forum post says a session behaves a certain way, check it against your release first, because LN changed warehousing, project and tax functionality across the 10.x line. The porting set is the technical layer. It carries the bshell, the database drivers and the operating-system interface. Two sites on the same application release can run different porting sets, and many hang, locking or character-set problems trace to the porting set rather than the application. The package VRC is the customization layer. VRC stands for version, release and customer. An LN site normally has a standard VRC delivered by Infor and one or more derived VRCs where customer-specific sessions, reports and DAL extensions live. A user runs the combination of those, not one VRC alone. ### Reading the package VRC chain **Body:** A package combination lists which VRC supplies each package (tc, td, ti, tf, tt and so on). When you ask what VRC am I running you really ask what the package combination for this user and company resolves to. Two users in different companies can legitimately run different VRC chains. The derived-from relation matters. When a session is not found in your customer VRC, LN looks in the VRC it is derived from, and so on up to the standard VRC. That is how one customized report coexists with thousands of standard sessions, and it is also why upgrading means re-checking every object stored in the customer VRC. **Code:** Typical VRC chain (names are examples): B61_a standard VRC from Infor B61U_a update/solution VRC derived from B61_a B61O_a_custom customer VRC derived from B61U_a User -> package combination -> maps each package to one VRC in the chain ### Why the answer matters before an upgrade or a support case **Body:** An upgrade plan starts with the inventory: how many objects sit in customer VRCs, which standard sessions they override, and which porting set the target release needs. See the Baan IV to LN upgrade checklist for the follow-on steps. Without the VRC chain you cannot scope how many customizations must be re-applied. Support cases also move faster with exact numbers. Include the release and feature pack, the porting set, the VRC chain for the affected user, and the solution list. A report like it fails on our LN gets no useful answer; a report with those four facts usually does. ## Pitfalls - Reporting only the release number and omitting the porting set, which is usually what separates two behaviors on the same release. - Checking the VRC of your own login and assuming every user runs it; package combinations are per company or user template. - Confusing the standard VRC with the customer VRC and deleting objects from the wrong layer. - Reading documentation for a newer feature pack than the one you run. - Not recording the version after a patch, so the next upgrade starts from guesswork. ## Ai Angle An assistant grounded in your LN data can answer which VRC does this user run by reading the package combination and user data tables read-only, and list every object in the customer VRC that overrides a standard session. ERPray shows the query it ran and leaves any change to an administrator. ## Faq ### Where is the Infor LN version shown in the UI? **Answer:** Open Help > About in the Web UI or Worktop. It lists the product release and feature pack. It does not show the porting set or your package VRC chain, which come from the Tools administration sessions and the server installation records. ### What does VRC mean in Infor LN? **Answer:** VRC stands for version, release and customer. It identifies a layer of the application software. The standard VRC comes from Infor, and customer VRCs derived from it hold your own sessions, reports and extensions without touching the standard layer. ### How do I know which package VRC a user is running? **Answer:** Look at the user data and the package combination assigned to that user or company in Tools. The combination maps each package to a VRC. Different companies in the same environment can use different combinations, so check the specific user and company. ### Is the porting set the same as the LN version? **Answer:** No. The porting set is the technical runtime layer containing the bshell and database drivers, and it is versioned and patched separately from the application release. Support often needs both the porting set and the application version to diagnose a problem. ## Search terms how to check infor ln version, infor ln package vrc, current package vrc infor ln, infor ln porting set, infor ln feature pack, baan vrc, infor ln package combination, infor ln about version --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json