Demo prep acceleration · GenAI + ERP

AI-driven BOM creation for Infor LN

Start from a client name, a sentence, or a spreadsheet. The tool parses it into a multi-level bill of material, lets you edit the structure in place, then creates the items and BOM lines live in LN through the PLM OData API.

Describe→ Review tree→ Send to LN

LN defaults

Applied to every item created

Company

Revision

PLM project

Code prefix

Item prefix ★ before parsing

Include in item code

Codes are created as 01- + item prefix + code · item prefix also goes to SearchKey2.

Item defaults by level

Item group can still be changed per row in the tree

Level

Item group

Item character

PLM template

Finished good

Subassembly

Component

Re-check serial / lot / country after each create and fix what PLM's template changed

Serial and lot control come from LN's Item Defaults for each item group. PLM template is optional — leave it blank to let PLM choose, or click the field to browse the templates on this tenant.

1 Describe the assembly in plain language

1 Upload a BOM file — any column layout

Drop in an Excel or CSV export in whatever shape you have it. Claude maps your columns to the required structure automatically.

1 Who is the client?

Claude researches what this company manufactures and suggests products worth building a demo BOM around.

How it posts. Items go first, one POST /LN/plmapi/odata/pdpdm.plmdataservice/Items per row, then each parent→child relationship via POST …/AddBOMLine with a follow-up PATCH for quantity — sequential, so parents always exist before their BOM lines. Every call carries X-Infor-LnCompany from the company field. Authentication is handled by the proxy; nothing sensitive is stored in the browser.