Infor SyteLineFree referencePDF, Excel, Word exportInfor SyteLine

SyteLine Item Master Fields Reference (item_mst Columns Explained)

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.

Download:

Field (item_mst)	Meaning	Typical values	What it drives
item	Item number	Alphanumeric key, unique per site	Every join to jobs, orders, POs and inventory
description	Item description	Free text	Documents, reports and lookups
p_m_t_code	Source of supply	P purchased, M manufactured, T transferred	Whether MRP plans a PO, a job or a transfer
cost_type	Costing method	S standard, A average, F FIFO, L LIFO	How inventory is valued and relieved
abc_code	ABC classification	A, B or C	Cycle count frequency and reporting
u_m	Stocking unit of measure	EA, KG, M and other defined units	Quantity on every inventory and order transaction
stocked	Stocked item flag	1 yes, 0 no	Whether on hand balances are kept
lot_tracked	Lot tracking flag	1 yes, 0 no	Lot capture at receipt, issue and shipment
serial_tracked	Serial tracking flag	1 yes, 0 no	Serial number capture on transactions
product_code	Product code	Code defined in prodcode_mst	GL account defaults and reporting rollups
family_code	Family code	Code defined in the family code table	Grouping for planning and reporting
lead_time	Planned lead time	Days	Offset of planned orders in MRP and planning
safety_stock	Safety stock quantity	Number in stocking UoM	Net requirements in MRP
order_min	Minimum order quantity	Number in stocking UoM	Size of planned orders
order_mult	Order multiple	Number in stocking UoM	Rounding of planned order quantities
unit_cost	Total standard unit cost	Sum of the five cost elements	Standard cost valuation and variance
matl_cost	Material cost element	Currency per unit	Material part of the standard cost
lbr_cost	Labor cost element	Currency per unit	Labor part of the standard cost
fovhd_cost	Fixed overhead cost element	Currency per unit	Fixed overhead part of the standard cost
vovhd_cost	Variable overhead cost element	Currency per unit	Variable overhead part of the standard cost
out_cost	Outside (subcontract) cost element	Currency per unit	Outside processing part of the standard cost
phantom_flag	Phantom item flag	1 yes, 0 no	Whether the item is exploded through rather than stocked

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.

Want an item master quality scan?

An optional read-only scan of your item data for missing codes, cost gaps and inconsistent units, with findings you review before any change.

Optional. The tool and every export work without this. No spam.

How to use this reference

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.

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

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

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.

Frequently Asked Questions

What does p_m_t_code mean in SyteLine?

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?

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?

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?

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.

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.

Talk to an Expert Explore More Free Tools

Related Tools

Infor SyteLine

More Infor SyteLine tools

See all

Back to All Tools