SyteLine Item Import Worksheet (Excel Template)
Item master data is the first thing to go wrong in a SyteLine migration or cleanup. Duplicates, wrong units of measure and missing lead times show up months later as planning errors. This worksheet gives you a clean place to stage and check items before loading.
| Item | Description | UoM | Source (P/M/T) | Product code | Cost method | Unit cost | Lead time (days) | Reorder qty | First buy value | |
|---|---|---|---|---|---|---|---|---|---|---|
$1,600 | ||||||||||
$4,740 | ||||||||||
$600 | ||||||||||
$2,565 | ||||||||||
$1,480 |
Use this as a staging sheet, then map columns to the fields in your own item load process (the Excel add-in, an import utility or an IDO-based load). Required fields, valid codes and cost methods differ by version and site settings, so test a small batch in a non-production configuration before the full load.
Item master cleanup support
Optional: have your legacy item data profiled for duplicates and unit conflicts before a SyteLine load.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
Replace the sample rows with your own items, add rows as needed and let the sheet compute first buy value for each line. Sort or search to spot duplicates, then export to Excel or CSV and map the columns to the fields your loader expects. Treat it as a staging area: the goal is to find problems while they are still cheap to fix, before anything is written to the live item table.
- One row per item, one unit of measure per row.
- Decide source code (P, M or T) before costing.
- Review the longest lead time and the largest first buy values first.
Fields that cause the most trouble
The unit of measure is the first source of errors, because changing it after transactions exist is difficult. Source code controls how planning treats the item, so a manufactured part flagged as purchased will never generate a job suggestion. Cost method must match your costing policy for the product code, since mixing methods without intent confuses variance reports. Lead time of zero is legal but almost always wrong, and it makes MRP plan every order for today. Reorder quantity and unit cost together define the first purchase exposure, which is why the sheet computes it.
Common mistakes in item loads
Loading the whole list in one go with no pilot is the biggest mistake. Load fifty items, check them in the item form and in a planning run, then load the rest. Other repeat offenders are inconsistent descriptions that make search useless, product codes created on the fly, and costs loaded in the wrong currency or per-thousand instead of per-each. Keep a mapping column for the legacy item number so that bills of material, open orders and history can be reconciled after the load.
- Pilot a small batch before the full load.
- Keep the legacy item number for reconciliation.
- Confirm cost per each, not per hundred or thousand.
Frequently Asked Questions
How do I load items into SyteLine from Excel?
Common routes are the Excel add-in, an import utility or an IDO-based load. Which is available depends on your version and configuration. Whatever method you use, stage and clean the data first and test a small batch in a non-production configuration.
What do the P, M and T source codes mean?
P marks purchased items, M marks manufactured items and T marks items supplied by transfer from another site or warehouse. The code tells planning whether to suggest purchase orders, jobs or transfers, so it must match how the item is really supplied.
Which cost method should I use?
That is a finance policy decision. Standard cost is common in manufacturing because it enables variance analysis, while average and FIFO follow actual purchases. Pick the method per product group with your controller and keep it consistent for similar items.
Why is lead time zero a problem?
With zero lead time MRP assumes the item is available immediately, so it recommends orders for the need date and then reports them as late. Set realistic purchase or manufacturing lead times, and review them at least once a year.
Netray can profile your legacy item data for duplicates, unit conflicts and missing lead times, and prepare load files for SyteLine with a human review step before anything is written.
Related Tools
SyteLine SQL Query Generator for Item, Job and Order Tables
Fill in site, item prefix, job status and date to produce read-only SQL for item master, jobs and open customer order lines.
Costing & FinanceSyteLine Cost Rollup Variance Calculator
Compare actual job cost to the rolled standard by material, labor and overhead, and see the inventory revaluation caused by a standard cost change.
Developer ToolsSyteLine IDO REST Request Generator
Fill in host, configuration, IDO, properties and filter to get ready-to-use REST calls for loading, updating and invoking methods on SyteLine IDOs.
Infor SyteLineSyteLine MRP vs APS Assessment
Answer ten questions about capacity, routing complexity and planning cadence to see whether SyteLine MRP is enough or an APS tool is worth evaluating.
More Infor SyteLine tools
See all- SyteLine Job and Order Status Codes Reference
- SyteLine Implementation Cost Calculator
- SyteLine to CloudSuite Upgrade Cost Estimator
- SyteLine Version End-of-Life Risk Assessment
- SyteLine MRP Health Check
- SyteLine Customization Technical Debt Scorer
- SyteLine Downtime Cost Calculator
- SyteLine License Optimization Calculator
- SyteLine Go-Live Readiness Checklist