# SyteLine Item Import Worksheet (Excel Template)

> Source: https://netray.co/tools/syteline-item-import-worksheet
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A staging sheet for item master data with computed first-buy value, ready to clean in the browser and export to Excel or CSV for loading.

## Category

syteline

## Erp

Infor SyteLine

## Industry

Discrete Manufacturing

## Audience

- Data migration lead
- SyteLine administrator
- Master data steward

## Tool

**Kind:** worksheet

**Mode:** editable

**Currency:** $

**Columns:**

#### Item

**Key:** item

**Type:** text

**Help:** Unique item number, keep within your item length setting.

#### Description

**Key:** description

**Type:** text

#### UoM

**Key:** um

**Type:** select

**Options:**

- EA
- KG
- M
- L
- BOX
- HR

#### Source (P/M/T)

**Key:** source

**Type:** select

**Options:**

- P
- M
- T

**Help:** P purchased, M manufactured, T transferred.

#### Product code

**Key:** product_code

**Type:** text

#### Cost method

**Key:** cost_method

**Type:** select

**Options:**

- Standard
- Average
- FIFO
- LIFO

#### Unit cost

**Key:** unit_cost

**Type:** number

**Format:** currency

#### Lead time (days)

**Key:** lead_days

**Type:** number

**Format:** integer

#### Reorder qty

**Key:** reorder_qty

**Type:** number

**Format:** integer

#### First buy value

**Key:** first_buy

**Type:** number

**Expr:** reorder_qty * unit_cost

**Format:** currency

**Rows:**

**Item:** PN-48213

**Description:** Bracket, mounting, 3mm steel

**Um:** EA

**Source:** M

**Product code:** FAB

**Cost method:** Standard

**Unit cost:** 6.4

**Lead days:** 12

**Reorder qty:** 250

**Item:** RM-ST-3MM

**Description:** Steel sheet 3mm, 1250 x 2500

**Um:** EA

**Source:** P

**Product code:** RAW

**Cost method:** Average

**Unit cost:** 118.5

**Lead days:** 21

**Reorder qty:** 40

**Item:** FS-M8X25

**Description:** Bolt hex M8 x 25 zinc plated

**Um:** EA

**Source:** P

**Product code:** HDW

**Cost method:** Average

**Unit cost:** 0.12

**Lead days:** 7

**Reorder qty:** 5000

**Item:** PN-50177

**Description:** Housing assembly, anodized

**Um:** EA

**Source:** M

**Product code:** ASM

**Cost method:** Standard

**Unit cost:** 42.75

**Lead days:** 18

**Reorder qty:** 60

**Item:** PK-BOX-L

**Description:** Carton, large, double wall

**Um:** EA

**Source:** P

**Product code:** PKG

**Cost method:** FIFO

**Unit cost:** 1.85

**Lead days:** 5

**Reorder qty:** 800

**Totals:**

#### Total first buy value

**Key:** first_buy

**Agg:** sum

**Format:** currency

#### Items staged

**Key:** item

**Agg:** count

**Format:** integer

**Summary:**

#### Average first buy per item

**Key:** avg_cost

**Expr:** sum_first_buy / count

**Format:** currency

#### Longest lead time

**Key:** max_lead

**Expr:** max_lead_days

**Format:** days

**Notes:** 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.

## Content

**Intro:** 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.

**Sections:**

#### How to use the worksheet

**Body:** 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.

**Bullets:**

- 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

**Body:** 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

**Body:** 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.

**Bullets:**

- Pilot a small batch before the full load.
- Keep the legacy item number for reconciliation.
- Confirm cost per each, not per hundred or thousand.

**Cta:** 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.

**Faq:**

#### How do I load items into SyteLine from Excel?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

syteline item import, syteline item master template, syteline item load excel, syteline data migration item master, syteline item master fields, syteline excel add-in item, syteline import template, item master data cleansing worksheet

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json