How-toInfor LNCommon / Item Base Data / Purchase Control

MPN in Infor LN: Manufacturer Part Numbers, Items and Suppliers

Question
mpn in infor ln

Also searched as

  • infor ln manufacturer part number
  • infor ln supplier item code
  • infor ln item code system
  • infor ln link manufacturer part to item

Short answer

Infor LN does not treat the manufacturer part number as a single magic field. You normally hold the MPN through the item code system (alternative codes tied to your own item code) and through supplier-specific item data on the buy-from business partner, so purchase orders can print the supplier or manufacturer number while stock stays under your own item.

Applies to: Infor LN 10.x (Common, Item Base Data and Purchase Control packages). Session codes and field names differ slightly between releases, so confirm them in your own session search.

How to hold and use an MPN in Infor LN

  1. 1Decide the rule first: your own item code is the identity, the MPN is an attribute or cross reference. Do not create a new item per manufacturer number unless the parts are genuinely not interchangeable.
  2. 2Open the Items - General data in Item Base Data and confirm the item exists with the correct purchase and warehousing flags.
  3. 3Open the item code system sessions (search the Web UI for Item Code System or Item Codes) and define a code system for manufacturer numbers, then attach the MPN as an alternative code on the item.
  4. 4In Purchase Control, maintain the item data per buy-from business partner so the supplier's own item number and description are stored against your item.
  5. 5Check that your purchase order and request for quotation reports print the supplier item code, not only your internal code.
  6. 6Test with one real item: create a purchase order, confirm the supplier code prints, then search by the MPN in the Web UI to confirm you can find the item from it.

Why LN has no single MPN field

LN is built around one internal item code per stocked thing, and external identifiers hang off it. The same item may have a customer number, a supplier number and a manufacturer number. Each lives in a cross reference rather than in the item master itself, which keeps stock, costing and planning on one record.

The consequence is that the MPN is rarely on the item screen. If you need it on a screen, a report or in a search box, you have to design where it is stored and who maintains it. That design decision matters more than the clicks.

Choosing between item code system and supplier item data

Use the item code system when the MPN is the same regardless of who you buy from, for example a catalogue number from one manufacturer. This lets any user find the item by typing the MPN.

Use supplier-specific item data when the number depends on the distributor, because a distributor may reprint a manufacturer number as its own stock code. Many electronics and machinery buyers need both: the manufacturer number for engineering and approved manufacturer control, and the distributor number for ordering.

If approved manufacturer lists matter for quality or defense work, keep that in a controlled structure owned by engineering, and use the LN cross reference only as the lookup.

Cleaning up MPNs that are already messy

Most sites inherit MPNs typed into item descriptions or in free text. Export the item descriptions, separate the number from the text, and load them as alternative codes in a controlled import. Run duplicate checks first: the same MPN on two internal items is a real data problem, not a formatting one.

Keep the manufacturer name next to the number. Two manufacturers can legitimately use the same string.

-- Concept: find the same MPN pointing at more than one item
-- (run on a copy or via a read-only reporting view; table and field names depend on your release)
SELECT mpn, COUNT(DISTINCT item) FROM item_cross_reference GROUP BY mpn HAVING COUNT(DISTINCT item) > 1;

Try it here, free

Infor LN Session and Module Code Reference

Open full tool

Searchable list of the Infor LN / Baan package and module codes (tisfc, tdsls, whinh and others) with what each one covers.

Common pitfalls

  • !Creating a separate LN item for every manufacturer number, which splits stock and breaks MRP.
  • !Storing the MPN only in the item description, which is not searchable as a code.
  • !Forgetting to add the manufacturer name beside the number, so two vendors with the same string collide.
  • !Assuming reports will print the supplier code without changing the report layout.

How an ERP-grounded AI assistant handles this

An AI assistant grounded in the LN item and purchase data can answer which item an MPN maps to, flag the same MPN on two items, and draft the cleanup list for a data steward. ERPray runs read-only over LN data and shows the query it used, so the buyer or engineer can check it. Any bulk change to cross references should still go through your normal approval and import process.

Frequently asked questions

Is there a standard manufacturer part number field on the LN item?

Not as a single universal field in most setups. LN usually holds the MPN through the item code system or supplier item data. Check your release in the item and purchase sessions, because customization and newer versions can add fields.

Should every manufacturer number be a separate item?

No, only when the parts are not interchangeable. If they are form, fit and function equivalents, keep one item and record the manufacturer numbers as alternatives so stock and planning stay combined.

Can I search LN by MPN?

Yes if the MPN is stored as an alternative item code, because you can then find the item from that code. If it lives only in a description you are limited to text search in reports or an external query.

How do I get the supplier item number on the purchase order?

Maintain it in the supplier-specific item data and make sure the purchase order report layout includes that field. If it still does not print, the report is the next place to look.

Related

How-to

Infor LN item sales session, item purchase session and site data: where each lives

In Infor LN the item master is split by business function. General data sits in the Items - General table (tcibd001), sales data in Item - Sales (tdisa001) and purchase data in Item - Purchase (tdipu001). Site-dependent data such as ordering and planning parameters is held per item and site, so one item can behave differently in each site.

How-to

Conversion Factor Session in Infor LN: Setup and Common Errors

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.

How-to

Infor LN Report Designer: How to Build and Personalize Reports

Infor LN reports are designed in LN Studio's report designer, where a report is defined by its input fields, data selection through the session's tables and a layout of sections. To personalize a standard report, copy it into your customer VRC and edit the copy, never the standard object, so upgrades do not overwrite your work.

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

AI for ERP

AI for Infor LN Purchasing: Faster Exception Handling on Orders, Schedules and Suppliers

AI for Infor LN purchasing: triage late orders and schedules, answer supplier performance questions, and draft POs with buyer approval. On-prem option.

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.

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

Runs with your ERP

Guides

AI on your ERP

Integrations

Comparisons

Software