How to Check the Infor LN Version and Current Package VRC
how to check infor ln version
Also searched as
- current package vrc infor ln
- infor ln feature pack version
- infor ln porting set version
- which package vrc is infor ln using
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.
Applies to: Infor LN 10.x (all feature packs) and Baan IVc / Baan 5 style package VRC administration; menu names vary slightly by version
How to find each LN version
- 1In 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.
- 2Open 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.
- 3To 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.
- 4To 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.
- 5On 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.
- 6Record 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.
- 7For 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.
- 8Write 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.
What each number actually tells you
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
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.
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
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.
Try it here, free
Infor LN and Baan ERP Table List by Package
Filterable list of commonly used Infor LN and Baan tables by package, with the naming convention, key fields and where a Baan IV table differs from LN.
Common 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.
How an ERP-grounded AI assistant handles this
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.
Frequently asked questions
Where is the Infor LN version shown in the UI?
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?
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?
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?
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.
Related
Baan IV to Infor LN migration checklist
Moving from Baan IV to Infor LN is a re-implementation, not an in-place upgrade, because the two products differ in data model, session technology and, for LN Enterprise Edition, the underlying runtime. The checklist centers on inventorying customizations, converting master data, rebuilding logic rather than porting it, and running a real parallel test before cutover.
AdvancedHow to create a custom session in Infor LN Studio
Infor LN Studio's session designer generates a new maintenance, overview or detail session from a table definition, then lets you arrange fields, attach DAL2 validation, and wire menu access, all inside a custom package so the session survives upgrades. Building on a custom table gives the lowest upgrade risk; extending a standard table needs more care and re-testing after every release.
Error fixInfor LN bshell Process Stuck at 100% CPU: How to Diagnose and Fix It
A bshell process pinned at 100% CPU on the Infor LN application server almost always means one session is stuck in a 4GL loop, scanning an unindexed table, or waiting on a database lock. End the session from the Sessions Monitor first, then kill the OS process only if that fails, and check for a blocking database transaction before assuming it is a bug.
Error fixInfor LN DAL Out of Sync After a Custom Field: Cause and Fix
Infor LN throws a DAL, or table, out of sync error, or simply drops a new custom field silently, when a table's dictionary definition is changed but the generated DAL and dependent forms are not regenerated afterward. Running the standard sequence, table compile, DAL generation, then session/form compile, in Tools > Development after every dictionary change resolves it. Skipping any one of the three steps is what causes the mismatch.
Error fixInfor LN Not Authorized to Run This Session: How to Fix It
Infor LN refuses to open a session with a not authorized message when the logged-in user's assigned role does not include that session, or when the session is blocked for the company they are logged into. Grant the session through Common > Authorization Management > Roles, or check the user's role and company context, and the session opens on retry. In most cases this is a permissions configuration issue, not a bug.
Error fixInfor LN Jobs Stuck in Active or Waiting: Fix the Job Daemon
Infor LN background jobs, reports, batch processes and print jobs, get stuck in Active or Waiting status when the job daemon on the enterprise server has stopped or lost its connection, or when a prior job crashed without releasing its status. Restart the job daemon and reset the stuck job's status through the Jobs session, and the queue resumes. A daemon that keeps stopping usually points to a memory, license or database connectivity problem on the server.
AI for ERPAI for Infor LN: Sessions, BODs, and Engineer-to-Order Work
Add grounded AI to Infor LN 10.x or CloudSuite: natural-language answers over sessions and BODs, agents for project and engineer-to-order work, on-prem options.
AI for ERPAI for Legacy Baan IV/V: Capture the Knowledge Before It Walks Out the Door
Use AI to capture knowledge from ageing Baan IV/V systems, document undocumented customisations, and de-risk a future migration to LN or CloudSuite.
Stuck on Infor LN (Baan)?
Talk to engineers who work inside Infor LN (Baan) every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- Infor LN and Baan ERP Table List by PackageFilterable list of commonly used Infor LN and Baan tables by package, with the naming convention, key fields and where a Baan IV table differs from LN.
- Infor LN and Baan Customization Inventory WorksheetEditable worksheet to list every Baan or LN customization with type, owner, effort and a retire, keep or replace decision.
- Baan to Infor LN Data Conversion Mapping WorksheetField-level mapping sheet for Baan or legacy data moving into Infor LN, with transform rules, owners and load status.
ERP fixes and how-tos
- Cannot Find Session Info in Baan and Infor LN: Causes and FixFix the cannot find session info error in Baan and Infor LN: session missing from the VRC or runtime dictionary, package mismatch, and how to reconvert.
- Infor LN Application Studio and Studio: overview and getting startedWhat Infor LN Studio and application customization tools are, what you can change with them, how VRCs separate customizations, and how to get started.
- Infor LN Report Designer: How to Build and Personalize ReportsHow reports are built and personalized in Infor LN: LN Studio's report designer, copying standard reports to a customer VRC, layouts, scripts and a safe workflow.
Guides
- Infor LN Domain Administration GuideAdminister Infor LN domains effectively. Domain architecture, user management, environment configuration, and system maintenance best practices.
- Infor LN Upgrade Path to 2026 and BeyondPlan your Infor LN upgrade path through 2026. Version comparison, feature roadmap, customization remediation, and upgrade project methodology.
- BAAN 5 to Infor LN Complete Migration GuideMigrate from BAAN 5 to Infor LN comprehensively. 4GL analysis, data transformation, business process mapping, and organizational change management.