# SyteLine Database Tables Reference: Core _mst Tables and Keys > Source: https://netray.co/tools/syteline-database-tables-reference > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Searchable lookup of the main SyteLine SQL tables, what each holds and its usual business key, for writing queries and reports. ## Category syteline ## Erp Infor SyteLine ## Audience - SyteLine admin - ERP developer - Report writer ## Tool **Kind:** worksheet **Mode:** reference **Columns:** #### Table **Key:** table **Type:** text #### Area **Key:** area **Type:** text #### What it holds **Key:** holds **Type:** text #### Typical business key (with site_ref) **Key:** key **Type:** text **Rows:** **Table:** item_mst **Area:** Inventory **Holds:** Item master, one row per item per site **Key:** item **Table:** itemwhse_mst **Area:** Inventory **Holds:** Item quantities and planning data by warehouse **Key:** item, whse **Table:** itemloc_mst **Area:** Inventory **Holds:** Item quantity by warehouse location **Key:** whse, item, loc **Table:** loc_mst **Area:** Inventory **Holds:** Warehouse location master **Key:** loc **Table:** lot_mst **Area:** Inventory **Holds:** Lot master for lot tracked items **Key:** item, lot **Table:** lot_loc_mst **Area:** Inventory **Holds:** Lot quantity by warehouse location **Key:** whse, item, loc, lot **Table:** whse_mst **Area:** Inventory **Holds:** Warehouse master **Key:** whse **Table:** matltran_mst **Area:** Inventory **Holds:** Inventory transaction history (receipts, issues, moves) **Key:** trans_num **Table:** prodcode_mst **Area:** Inventory **Holds:** Product code master used for GL and reporting **Key:** product_code **Table:** job_mst **Area:** Production **Holds:** Job header **Key:** job, suffix **Table:** jobroute_mst **Area:** Production **Holds:** Job operations (routing copy on the job) **Key:** job, suffix, oper_num **Table:** jobmatl_mst **Area:** Production **Holds:** Job material requirements **Key:** job, suffix, oper_num, sequence **Table:** jobtran_mst **Area:** Production **Holds:** Job labor, machine and move transactions **Key:** trans_num **Table:** wc_mst **Area:** Production **Holds:** Work center master **Key:** wc **Table:** co_mst **Area:** Sales **Holds:** Customer order header **Key:** co_num **Table:** coitem_mst **Area:** Sales **Holds:** Customer order lines and releases **Key:** co_num, co_line, co_release **Table:** customer_mst **Area:** Sales **Holds:** Customer master (sequence 0 is the bill-to record) **Key:** cust_num, cust_seq **Table:** custaddr_mst **Area:** Sales **Holds:** Customer name and address data **Key:** cust_num **Table:** po_mst **Area:** Purchasing **Holds:** Purchase order header **Key:** po_num **Table:** poitem_mst **Area:** Purchasing **Holds:** Purchase order lines and releases **Key:** po_num, po_line, po_release **Table:** vendor_mst **Area:** Purchasing **Holds:** Vendor master **Key:** vend_num **Table:** vendaddr_mst **Area:** Purchasing **Holds:** Vendor name and address data **Key:** vend_num **Table:** arinv_mst **Area:** Finance **Holds:** Accounts receivable invoices **Key:** inv_num **Table:** chart_mst **Area:** Finance **Holds:** Chart of accounts **Key:** acct **Table:** ledger_mst **Area:** Finance **Holds:** General ledger postings **Key:** trans_num **Table:** parms_mst **Area:** System **Holds:** Site level parameters **Key:** parm_key **Notes:** 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. ## Content **Intro:** 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. **Sections:** #### How to use this reference **Body:** 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. **Bullets:** - 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 **Body:** 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 **Body:** 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. **Bullets:** - 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 **Cta:** 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. **Faq:** #### Why do SyteLine tables end in _mst? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms syteline database tables, syteline table list, item_mst, job_mst table, coitem_mst, syteline data dictionary, syteline sql tables, cloudsuite industrial database schema --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json