How-toInfor LNCommon Data / Item Base Data / Units

Conversion Factor Session in Infor LN: Setup and Common Errors

Question
conversion factor session in infor ln

Also searched as

  • infor ln unit conversion factor
  • infor ln no conversion factor defined
  • infor ln purchase unit to inventory unit

Short answer

Infor LN converts between units using conversion factors, either general factors between units of the same physical dimension or item-specific factors that override them. When an item is bought in one unit and stocked in another, LN needs a factor for that pair. A missing factor is the usual cause of a conversion error on purchase orders, receipts or sales lines.

Applies to: Infor LN 10.x. Session names for units and conversion factors sit in Common Data and Item Base Data; search the session list for 'conversion factors' in your version.

Fix a missing or wrong conversion factor

  1. 1Read the error and note the item and the two units LN is trying to convert, for example the purchase unit and the inventory unit.
  2. 2Open the item's data and confirm its inventory unit, purchase unit, sales unit and any other units used.
  3. 3Search the session list for the conversion factors session and check whether a general factor exists for the unit pair.
  4. 4If units are of the same dimension, such as length, define the general factor. If not, such as converting a count to weight, define an item-specific factor.
  5. 5Enter the factor in the correct direction. Confirm which unit the factor converts from and to, then test with a simple quantity.
  6. 6Retry the transaction that failed, and check the quantity in the resulting order line and in inventory.
  7. 7Review recently changed factors for open orders, since a change does not always revalue lines already created.

General versus item-specific factors

A general factor says, for instance, that a metre is a hundred centimetres, and applies to any item using those units. It only makes sense between units of the same physical dimension, because it relies on a fixed ratio.

An item-specific factor describes a ratio that exists only for that item, such as a roll of material that weighs a known amount, or a pack of fifty pieces. These are the factors you must maintain item by item, and the source of most data-quality issues.

Where factors are used

Purchasing converts the order unit to the inventory unit at receipt. Sales converts the sales unit to the inventory unit when reserving and shipping. Production may use another unit for bill of material quantities. Each of those boundaries needs a defined factor, or the transaction stops.

Pricing can sit in yet another unit, so a mismatch may show as a wrong price per unit rather than an error. Check both quantity and price unit when totals look off.

Preventing errors at scale

Create a standard unit set and conversion rules before item load. Use a data-load validation that, for every item, tests that each assigned unit pair has a factor, and flags rounding that loses precision, for example a factor that produces fractional inventory.

Lock edits to factors for items with open orders unless a data owner approves, since a change affects receipts and valuation.

Item unit validation checklist
For each item:
  inventory unit set?
  purchase unit -> inventory factor exists?
  sales unit -> inventory factor exists?
  BOM unit -> inventory factor exists?
  fractional quantity risk reviewed?

Try it here, free

Baan to Infor LN Data Conversion Mapping Worksheet

Open full tool

Field-level mapping sheet for Baan or legacy data moving into Infor LN, with transform rules, owners and load status.

Common pitfalls

  • !Entering a factor in the inverse direction and receiving a hundred times too many or too few.
  • !Using a general factor for units from different dimensions.
  • !Changing a factor while orders are open and assuming existing lines update.
  • !Rounding that creates fractional quantities in a unit that must be whole.
  • !Loading items with units in bulk without validating every unit pair.

How an ERP-grounded AI assistant handles this

A data-quality sweep for missing or suspicious factors is a pattern-matching job. Netray's private assistant can scan item and unit data in read-only mode, list items with unit pairs lacking a factor or with implausible ratios, and draft the corrections for a data owner to approve and load. It runs on-prem, so item master data stays in your environment.

Frequently asked questions

Which session maintains conversion factors in Infor LN?

There are sessions in Common Data for general unit conversion factors and in Item Base Data for item-specific ones. Names and codes vary by version, so search the session list for conversion factors in your environment.

What does 'no conversion factor defined' mean in LN?

It means LN was asked to convert between two units and found no general or item-specific factor for that pair. Define the factor for the item or units involved and retry the transaction.

When do I need an item-specific conversion factor?

When the ratio between units is true only for that item, or when units belong to different dimensions, such as pieces to kilograms. General factors cover units of the same dimension.

Will a changed factor update open orders?

Do not assume so. Order lines already created may keep converted quantities. Review open orders after changing a factor and correct them deliberately, with a data owner's approval.

Related

Error fix

Infor 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.

How-to

How to process inbound and outbound warehousing orders in Infor LN

Infor LN Warehousing splits every physical movement into inbound (goods arriving, mainly from purchase orders) and outbound (goods leaving, mainly for sales orders), each driven by its own warehouse order type. Inbound runs through intake, inspection if required, and put-away; outbound runs through order release, picking, packing and shipment confirmation, with each stage updating the order status other modules watch.

How-to

How to calculate item cost prices in Infor LN

Infor LN calculates an item's cost price by rolling up material, labor, machine, subcontract and overhead costs defined against cost components, using the item's bill of material and routing as the calculation base for manufactured items and purchase price for bought items. The calculation can run in simulation mode to preview the result or in update mode to actually change the item's standard cost, which then drives inventory valuation and variance reporting going forward.

Error fix

Infor 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 fix

Infor 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 fix

Infor 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 ERP

AI 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 ERP

AI 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?

Talk to engineers who work inside Infor LN every week, and who build private AI that answers these questions from your own ERP data.

Keep exploring

Free tools

ERP fixes and how-tos

Guides

AI on your ERP

Integrations

Comparisons

Software