# Infor LN Use-Up: Handling Old Material in Engineering Changes > Source: https://netray.co/erp-help/infor-ln-use-up-engineering-change-old-material > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## 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. ## Kind how-to ## System infor-ln ## Erp Infor LN ## Module Engineering Data / Engineering Change Management ## Query infor ln use up ## Alternate Queries - infor ln use up old material engineering change - infor ln phase out item use up stock - infor ln engineering change order effectivity ## Applies To Infor LN 10.x with Engineering Data Management and Enterprise Planning; verify field names in your own release ## Steps ### How to set up a use-up change **Items:** - Create the engineering change (change order) that introduces the new item or revised BOM component and link the affected items and BOMs. - Decide the change type for old material: use up existing stock, scrap it, or rework it, and record this decision on the change. - On 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. - On the new BOM line set the matching start (in) date or unit so the two lines do not overlap or leave a gap. - Reduce or cancel open purchase orders for the old item where appropriate, so you do not buy more of what you are phasing out. - Run planning and confirm that planned orders for the old item stop at the cut-over and the new item takes over. - Release the change and review the exceptions list for orders that still reference the old item. ## Sections ### Date versus unit effectivity **Body:** 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 **Body:** 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 **Body:** 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. ## 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. ## Ai Angle 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. ## Faq ### What does use-up mean in an engineering change? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** Yes, by adjusting the effectivity on the BOM lines, but re-run planning afterwards and review the exceptions it raises. ## Search terms infor ln use up, use up old material, infor ln engineering change order, infor ln eco, infor ln effectivity, infor ln phase out, infor ln bom change, infor ln engineering data management --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json