How-toInfor LNEngineering Data / Engineering Change Management

Infor LN Use-Up: Handling Old Material in Engineering Changes

Question
infor ln use up

Also searched as

  • infor ln use up old material engineering change
  • infor ln phase out item use up stock
  • infor ln engineering change order effectivity

Short answer

Use-up means consuming existing stock of an old component or item before the new version takes over when an engineering change is introduced. In Infor LN you model it through the change's effectivity (a date or an effectivity unit) so the old item stays valid in the BOM until its stock is expected to run out, and planning then switches demand to the new item. Exact session names vary by version.

Applies to: Infor LN 10.x with Engineering Data Management and Enterprise Planning; verify field names in your own release

How to set up a use-up change

  1. 1Create the engineering change (change order) that introduces the new item or revised BOM component and link the affected items and BOMs.
  2. 2Decide the change type for old material: use up existing stock, scrap it, or rework it, and record this decision on the change.
  3. 3On the old BOM line set an expiry (out) date or effectivity unit based on when you expect existing stock and open supplier orders to be consumed.
  4. 4On the new BOM line set the matching start (in) date or unit so the two lines do not overlap or leave a gap.
  5. 5Reduce or cancel open purchase orders for the old item where appropriate, so you do not buy more of what you are phasing out.
  6. 6Run planning and confirm that planned orders for the old item stop at the cut-over and the new item takes over.
  7. 7Release the change and review the exceptions list for orders that still reference the old item.

Date versus unit effectivity

A date cut-over is simple: the old component is valid until a date, the new one from the same date. The risk is that stock runs out earlier or later than the date, so you either stall production or strand parts. An effectivity-unit cut-over ties the change to a serial, lot or build number, which suits products built to a defined sequence.

Use the date when demand is steady and use units when the product is configured or serialised and the change must apply to a precise point in production.

How planning sees it

Planning explodes the BOM using the components valid on each requirement date. Before the cut-over it generates demand for the old item, which consumes stock and open orders. After it, demand shifts to the new item. Open orders for the old item beyond the cut-over appear as exceptions to reschedule or cancel.

To avoid orphaned stock, check inventory of the old item against the forecast demand up to the cut-over and set the date near the point stock covers. Anything left needs a disposition: scrap, rework or sell as a spare.

Spare parts and aftermarket

An old item that is no longer in the BOM may still be needed as a spare for installed products. Keep it active for service demand even when production stops using it, and do not delete or obsolete the item record just because manufacturing has moved on.

Document the superseded relationship so service staff know the new part replaces the old one and whether the two are interchangeable.

Try it here, free

Engineering Change Order (ECO) Template

Open full tool

An ECO and ECN document template with affected items, effectivity, stock disposition and implementation tasks, exportable as PDF or Word.

Common pitfalls

  • !Gaps or overlaps between old and new BOM line dates produce missing or double demand.
  • !Leaving open purchase orders for the old item after the decision to phase out.
  • !Marking the old item obsolete while service still needs it as a spare.
  • !Using a date cut-over for serialised products where a unit cut-over is required.

How an ERP-grounded AI assistant handles this

Netray adds a private AI layer on top of the Infor LN you already run, including on-prem installs. ERPray answers questions in plain language over LN data read-only, shows the query it ran and respects LN roles, so a consultant can ask the question instead of hunting for the session. The model runs on your own GPUs, nothing leaves your network, and any write-back needs a human approval. Cloud-hosted LN works too, but the design is tuned for on-prem and air-gapped sites. For pure navigation questions, LN's own session search and help are often enough.

Frequently asked questions

What does use-up mean in an engineering change?

It means exhausting existing stock of the old component before the replacement takes over, instead of scrapping that stock the day the change is released.

How does LN know when to stop using the old item?

Through the validity of the old BOM line, set by an expiry date or an effectivity unit. Planning only explodes components valid on the requirement date.

What happens to stock left after the cut-over?

It stays in inventory until you disposition it: scrap, rework, return to supplier, or keep as a service spare.

Can I change the use-up date later?

Yes, by adjusting the effectivity on the BOM lines, but re-run planning afterwards and review the exceptions it raises.

Related

How-to

Infor LN planning BOM: how it works, setup and use (and what people mean by SIC planning)

A planning BOM is a structure used by Enterprise Planning to plan at family or option level, rather than the production BOM used on shop orders. You maintain planning items and a planning structure with proportions, and the planning engine uses it to explode forecasts into component and capacity requirements. 'SIC planning' is not a term I can pin to a single standard LN feature, so check how your site uses it.

How-to

Infor LN Master Planning: How It Works and a Setup and Run Checklist

Master planning in Infor LN looks at demand (sales orders, forecasts, dependent demand), nets it against inventory and open supply within the planning horizon, and generates planned orders with pegging that links each supply to the demand it serves. The result is only as good as the item planning data, the plan unit, the calendars and the horizon settings, so the checklist below starts with data, not the run.

How-to

Infor LN Item Group: Setup and Maintenance

An item group in Infor LN classifies items so that defaults, accounting and reporting can be applied by group instead of item by item. You maintain them in the Item Groups session (tcmcs023m000 in common data) and assign each item to one group in the item base data. Plan the group structure before loading items, because changing it later affects accounting defaults and history.

How-to

Customer Furnished Material in Infor LN: Ownership, Cost and Receiving

Customer furnished material (CFM, also called free issue or customer supplied) is stock your customer owns but you hold and consume on their job. In Infor LN you must keep it out of your own inventory value, receive and issue it with full traceability, and be able to prove quantities on hand. The exact mechanism depends on the LN functionality you adopt, so decide the pattern first and test it end to end.

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.

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

Guides

AI on your ERP