RF barcode data collectionInfor LNRuns on-prem

Infor Warehouse Mobility (Factory Track) and Infor LN: RF scanning

Infor Warehouse Mobility is a native Infor add-on where handheld RF scanners capture barcoded warehouse and shop-floor transactions, which are formatted and posted to LN. Infor's documentation says it is enabled through the Factory Track Implemented parameter in LN Warehouse Mobility general parameters. It also applies to Baan.

How Infor Warehouse Mobility (Factory Track for LN) connects to Infor LN

Native add-on enabled by a parameter

The Factory Track Implemented setting in the Warehouse Mobility general parameters turns on the Factory Track behaviour in LN. Transactions captured on the scanner are formatted by the add-on and posted to LN.

Scanner and label side

Scanners, terminal emulation or mobile clients, and the barcode labels they read sit outside LN. Their configuration and label content are what most go-live problems come from.

What data moves

FromToDataWhen
RF scannerInfor LNReceipts, issues, moves, counts and shop-floor reportingOperator scans and confirms
Infor LNRF scannerValid orders, locations, items, lots and promptsScan or screen entry
Infor LNLabel printersBarcode label data for items, locations and containersReceipt or setup
Infor LNSupervisorRejected or unposted transactionsValidation failure

Setting it up

  1. 1Enable Factory TrackSet Factory Track Implemented in Warehouse Mobility general parameters in a test environment first.
  2. 2List the transactionsChoose which receipts, issues, moves, counts and production reports go on the scanner first.
  3. 3Set up master data for scanningConfirm warehouses, locations, items, lots and units have the data scanning needs.
  4. 4Design barcode labelsDefine label content so a scan identifies item, lot or location unambiguously.
  5. 5Configure the terminalsSet up devices, wireless coverage and the screens operators will use.
  6. 6Pilot in one areaRun one warehouse or cell for several weeks and collect rejected scans.
  7. 7Train and roll outTrain by role, and keep a manual fallback for outages.

What usually breaks

  • !Wireless dead zones causing partial or repeated scans.
  • !Barcodes that identify the item but not the lot, leading to wrong-lot picks.
  • !Locations not set up in LN, so scans are rejected and operators work around the system.
  • !Units of measure differing between purchase, stock and the scan prompt.
  • !Operators posting production quantities late, distorting inventory and backflush.
  • !Customizations made to scanner screens that must be retested on every LN upgrade.

A private AI layer across both systems

Rejected scan triage

A private assistant reads rejected transactions, groups them by cause and suggests the master data fix for the supervisor to approve.

Count variance review

It compares cycle count results with recent movements to propose likely causes for each variance.

Plain-language inventory questions

Operators and planners ask where an item or lot is and what moved last, answered read-only from LN.

Label and location audit

It spots locations or items whose labels do not match LN master data.

Try it here, free

Infor Factory Track AI Assistant Sizing and Value Calculator

Open full tool

Size the GPUs and estimate the monthly value and payback of an on-prem AI assistant for Infor Factory Track users.

When something else fits better

  • Use a third-party RF and WMS product if your processes are more complex than the add-on covers.
  • Use paper with keyed entry if volumes are small and the area is simple.
  • Use the warehouse functions in LN directly with fixed terminals instead of handhelds.

Frequently asked questions

What is Factory Track in LN?

It is the data collection behaviour of Infor Warehouse Mobility, where RF scanners capture barcoded transactions and post them to LN. Infor's docs say it is enabled with the Factory Track Implemented parameter in the general parameters.

Does it work with Baan?

Infor's documentation lists it for both LN and Baan. Check the version-specific documentation for the parameters and session names in your release.

Is it on-prem?

It is an add-on to LN, so it runs wherever your LN runs, including on-prem. The scanners and wireless network are your responsibility and should be designed with the plant IT team.

What usually goes wrong?

Master data gaps, label content and wireless coverage cause most problems. Pilot in one area, collect rejected scans, and fix data before you scale.

Pairing documented at docs.infor.com/ln/2024.x/en-us/lnolh/brolh/tcomtcbr.html . Infor Warehouse Mobility (Factory Track for LN) is a product of Infor; Netray is independent and not affiliated with either vendor.

Keep exploring

Free tools

ERP fixes and how-tos

Runs with your ERP

Guides

Integrations

Software