# SyteLine Item Master Fields Reference (item_mst Columns Explained)

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

## Short answer

Searchable list of important item_mst fields with typical values and what each one drives in planning, costing and inventory.

## Category

syteline

## Erp

Infor SyteLine

## Audience

- SyteLine admin
- Inventory planner
- Cost accountant

## Tool

**Kind:** worksheet

**Mode:** reference

**Columns:**

#### Field (item_mst)

**Key:** field

**Type:** text

#### Meaning

**Key:** meaning

**Type:** text

#### Typical values

**Key:** values

**Type:** text

#### What it drives

**Key:** drives

**Type:** text

**Rows:**

**Field:** item

**Meaning:** Item number

**Values:** Alphanumeric key, unique per site

**Drives:** Every join to jobs, orders, POs and inventory

**Field:** description

**Meaning:** Item description

**Values:** Free text

**Drives:** Documents, reports and lookups

**Field:** p_m_t_code

**Meaning:** Source of supply

**Values:** P purchased, M manufactured, T transferred

**Drives:** Whether MRP plans a PO, a job or a transfer

**Field:** cost_type

**Meaning:** Costing method

**Values:** S standard, A average, F FIFO, L LIFO

**Drives:** How inventory is valued and relieved

**Field:** abc_code

**Meaning:** ABC classification

**Values:** A, B or C

**Drives:** Cycle count frequency and reporting

**Field:** u_m

**Meaning:** Stocking unit of measure

**Values:** EA, KG, M and other defined units

**Drives:** Quantity on every inventory and order transaction

**Field:** stocked

**Meaning:** Stocked item flag

**Values:** 1 yes, 0 no

**Drives:** Whether on hand balances are kept

**Field:** lot_tracked

**Meaning:** Lot tracking flag

**Values:** 1 yes, 0 no

**Drives:** Lot capture at receipt, issue and shipment

**Field:** serial_tracked

**Meaning:** Serial tracking flag

**Values:** 1 yes, 0 no

**Drives:** Serial number capture on transactions

**Field:** product_code

**Meaning:** Product code

**Values:** Code defined in prodcode_mst

**Drives:** GL account defaults and reporting rollups

**Field:** family_code

**Meaning:** Family code

**Values:** Code defined in the family code table

**Drives:** Grouping for planning and reporting

**Field:** lead_time

**Meaning:** Planned lead time

**Values:** Days

**Drives:** Offset of planned orders in MRP and planning

**Field:** safety_stock

**Meaning:** Safety stock quantity

**Values:** Number in stocking UoM

**Drives:** Net requirements in MRP

**Field:** order_min

**Meaning:** Minimum order quantity

**Values:** Number in stocking UoM

**Drives:** Size of planned orders

**Field:** order_mult

**Meaning:** Order multiple

**Values:** Number in stocking UoM

**Drives:** Rounding of planned order quantities

**Field:** unit_cost

**Meaning:** Total standard unit cost

**Values:** Sum of the five cost elements

**Drives:** Standard cost valuation and variance

**Field:** matl_cost

**Meaning:** Material cost element

**Values:** Currency per unit

**Drives:** Material part of the standard cost

**Field:** lbr_cost

**Meaning:** Labor cost element

**Values:** Currency per unit

**Drives:** Labor part of the standard cost

**Field:** fovhd_cost

**Meaning:** Fixed overhead cost element

**Values:** Currency per unit

**Drives:** Fixed overhead part of the standard cost

**Field:** vovhd_cost

**Meaning:** Variable overhead cost element

**Values:** Currency per unit

**Drives:** Variable overhead part of the standard cost

**Field:** out_cost

**Meaning:** Outside (subcontract) cost element

**Values:** Currency per unit

**Drives:** Outside processing part of the standard cost

**Field:** phantom_flag

**Meaning:** Phantom item flag

**Values:** 1 yes, 0 no

**Drives:** Whether the item is exploded through rather than stocked

**Notes:** Field names reflect common releases. Current cost fields carry a cur_ prefix and may differ from standard. Check the item form and your database for custom and version specific columns before building reports on them.

## Content

**Intro:** The item master is the most joined table in SyteLine, and a handful of its fields decide how an item is planned, costed and tracked. This reference explains those fields in plain language so you can set up items correctly and write queries that interpret the codes.

**Sections:**

#### How to use this reference

**Body:** Search for a field name from a query, or a concept such as lot or cost, to see the meaning, the typical stored values and the processes it drives. The last column is the important one: it tells you what breaks when a value is wrong. Export the table to Excel if you want a data conversion checklist that lists which fields every imported item must populate.

**Bullets:**

- Source of supply and cost type are required decisions for every item
- Tracking flags should be set before any stock exists
- Check product code, because it controls GL account defaults

#### Fields that cause the most support tickets

**Body:** Changing cost_type after transactions exist is restricted for good reason, because inventory valuation and relief depend on it. Lot and serial flags work the same way: switching them on later requires the on hand to be converted. The p_m_t_code field is another frequent cause of confusion, since an item set to manufactured with no active routing or BOM will plan jobs that cannot be released properly.

#### Reading the cost fields

**Body:** The standard cost is built from five elements: material, labor, fixed overhead, variable overhead and outside. unit_cost is their total. When you compare standard to actual, break the variance back to these five elements instead of looking at the total, because a labor rate problem and a purchase price problem need different owners. A cost roll updates the standard elements from routings and BOMs, so check both before rolling.

**Cta:** If your item master has years of inconsistent codes, Netray can help profile it and propose clean up rules for human review before anything is written back.

**Faq:**

#### What does p_m_t_code mean in SyteLine?

**Answer:** It is the item's source of supply: P for purchased, M for manufactured and T for transferred. Planning uses it to decide whether a requirement becomes a purchase order, a job or a transfer order.

#### Can I change the cost type of an existing item?

**Answer:** Only under restrictions, usually when there is no on hand and no open transactions, or through a controlled conversion. Plan the choice carefully before go live and involve the cost accountant.

#### Where are item quantities stored?

**Answer:** Not in item_mst. On hand quantities live in itemwhse_mst by warehouse, and in itemloc_mst and lot_loc_mst by location and lot. Summing item_mst fields will not give you stock.

#### Why do custom fields on items disappear after an upgrade?

**Answer:** Custom columns need to be carried through the upgrade process and maintained in the right extension mechanism. Document them before an upgrade and test them in the regression pass.

## Search terms

syteline item master fields, p_m_t_code syteline, syteline cost type, syteline item table, syteline item setup, syteline abc code, syteline lot tracked item, syteline unit cost fields

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