Infor SyteLineFree referencePDF, Excel, Word exportInfor SyteLine

SyteLine Database Tables Reference: Core _mst Tables and Keys

SyteLine stores business data in SQL Server tables whose names end in _mst. This lookup lists the core tables for inventory, production, sales, purchasing and finance with the business key you normally join on. Use it when you are writing a report, an IDO or a quick diagnostic query.

Download:

Table	Area	What it holds	Typical business key (with site_ref)
item_mst	Inventory	Item master, one row per item per site	item
itemwhse_mst	Inventory	Item quantities and planning data by warehouse	item, whse
itemloc_mst	Inventory	Item quantity by warehouse location	whse, item, loc
loc_mst	Inventory	Warehouse location master	loc
lot_mst	Inventory	Lot master for lot tracked items	item, lot
lot_loc_mst	Inventory	Lot quantity by warehouse location	whse, item, loc, lot
whse_mst	Inventory	Warehouse master	whse
matltran_mst	Inventory	Inventory transaction history (receipts, issues, moves)	trans_num
prodcode_mst	Inventory	Product code master used for GL and reporting	product_code
job_mst	Production	Job header	job, suffix
jobroute_mst	Production	Job operations (routing copy on the job)	job, suffix, oper_num
jobmatl_mst	Production	Job material requirements	job, suffix, oper_num, sequence
jobtran_mst	Production	Job labor, machine and move transactions	trans_num
wc_mst	Production	Work center master	wc
co_mst	Sales	Customer order header	co_num
coitem_mst	Sales	Customer order lines and releases	co_num, co_line, co_release
customer_mst	Sales	Customer master (sequence 0 is the bill-to record)	cust_num, cust_seq
custaddr_mst	Sales	Customer name and address data	cust_num
po_mst	Purchasing	Purchase order header	po_num
poitem_mst	Purchasing	Purchase order lines and releases	po_num, po_line, po_release
vendor_mst	Purchasing	Vendor master	vend_num
vendaddr_mst	Purchasing	Vendor name and address data	vend_num
arinv_mst	Finance	Accounts receivable invoices	inv_num
chart_mst	Finance	Chart of accounts	acct
ledger_mst	Finance	General ledger postings	trans_num
parms_mst	System	Site level parameters	parm_key

Every _mst table is multi-site and carries site_ref plus system columns such as RowPointer, NoteExistsFlag, CreatedBy, UpdatedBy, CreateDate, RecordDate and InWorkflow. Names and keys reflect common releases. Confirm against your own database before relying on them in production code.

Want a read-only SyteLine data map for your own database?

Ask for an optional review of your SyteLine schema, including custom tables, with notes on which queries are safe to automate.

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

How to use this reference

Type a table name, an area such as Production, or a word from the description into the search box to filter the list. Each row gives the usual business key. In SyteLine every key is effectively prefixed with site_ref, so joins between multi-site tables need site_ref on both sides or you will multiply rows across sites. Export the filtered list to Excel to keep a cheat sheet next to your query tool.

Search by area to see all tables for one module
Always join on site_ref as well as the business key
Use the view without the _mst suffix when your tool offers it

Tables versus views and IDOs

Most SyteLine forms do not read the _mst tables directly. They go through IDOs, which sit on views that filter by the current site. If you query the raw table you see every site in the database, which is useful for audits and misleading for reports meant for one site. Reporting tools that connect to the application database should usually read the site aware views, while diagnostic work such as blocking analysis or data fixes happens at the table level with care.

Common mistakes

The most frequent errors are joining job_mst to jobroute_mst without suffix, which mixes a job with its sub jobs, forgetting that customer_mst uses a sequence number for ship-to records, and updating _mst tables directly. Direct updates bypass SyteLine business logic, triggers and the audit trail, and Infor support will not stand behind data created that way.

Join job tables on job and suffix together
Use cust_seq 0 for the bill-to customer record
Prefer IDO methods or supported utilities over direct UPDATE statements

Frequently Asked Questions

Why do SyteLine tables end in _mst?

The suffix marks the multi-site base table. The application normally reads a view with the same name minus the suffix, which restricts rows to the current site. Custom code that needs one site's data should usually filter on site_ref or use the view.

Is there an official SyteLine data dictionary?

Infor documents tables and IDO properties inside the product through the IDO and form tooling, and your database itself is the final authority. This list is a quick orientation, not a replacement for checking your own release.

Can I write directly to these tables?

It is risky. Direct writes skip validation, event handlers, triggers and the audit trail. Use IDO methods, import utilities or supported APIs for any change, and use SQL mainly for reading and diagnosis.

How do I find a table that is not listed?

Search the SQL Server catalog with a query on INFORMATION_SCHEMA.COLUMNS for a known column name, or check the IDO definition of the form you are looking at. The IDO property maps back to a table and column.

If you maintain many SyteLine reports and queries, Netray can walk through your database and show which ones an AI assistant could draft and explain safely, with read-only access.

Talk to an Expert Explore More Free Tools

Related Tools

Infor SyteLine

More Infor SyteLine tools

See all

Back to All Tools