SYSPRO Common Table Name Reference
SYSPRO stores its data in SQL Server tables whose names follow a module prefix, such as Inv, Sor, Por and Ar. This reference helps report writers find the right table fast.
| Table | Module | Purpose | Typical key columns |
|---|---|---|---|
InvMaster | Inventory | Stock code master record | StockCode |
InvWarehouse | Inventory | Stock quantities by warehouse | StockCode, Warehouse |
InvMovements | Inventory | Inventory movement history | StockCode, Warehouse |
ArCustomer | Accounts Receivable | Customer master | Customer |
ArInvoice | Accounts Receivable | Open receivable invoices | Customer, Invoice |
ApSupplier | Accounts Payable | Supplier master | Supplier |
ApInvoice | Accounts Payable | Payable invoices | Supplier, Invoice |
SorMaster | Sales Orders | Sales order header | SalesOrder |
SorDetail | Sales Orders | Sales order lines | SalesOrder, SalesOrderLine |
PorMasterHdr | Purchase Orders | Purchase order header | PurchaseOrder |
PorMasterDetail | Purchase Orders | Purchase order lines | PurchaseOrder, Line |
WipMaster | Work in Progress | Job header | Job |
BomStructure | Bill of Materials | Bill of material components | ParentPart, Component |
GenMaster | General Ledger | General ledger account master | GlCode |
GenJournalDetail | General Ledger | General ledger journal lines | GlCode, Journal |
SalBranch | Sales Analysis | Customer delivery branches | Customer, Branch |
Table and column names can differ between SYSPRO versions and customised installs. Confirm against your own database with the SYSPRO data dictionary or by querying INFORMATION_SCHEMA before writing production reports.
SYSPRO reporting help
Optional: talk to an expert about read-only AI access to your SYSPRO data.
Optional. The tool and every export work without this. No spam.
How to use the reference
Search for a module name, a business object or a table name to filter the list. The key columns show how rows are usually joined, for example SorMaster to SorDetail on SalesOrder. Use it as a map before opening the database, and verify column names on your own system with INFORMATION_SCHEMA.COLUMNS.
Naming pattern
Most tables start with a module prefix: Inv for inventory, Sor for sales orders, Por for purchase orders, Ar for receivables, Ap for payables, Wip for jobs, Bom for bills of materials and Gen for the general ledger. Header and detail tables usually split into a Master table and a Detail table sharing the document key.
- Join headers to lines on the document number
- Add the Warehouse key when reading stock by location
- Expect extra columns on customised installs
Reading versus writing
Reading tables for reporting is fine, but never update SYSPRO tables directly. Business logic, audit trails and multi-table consistency live in the application, so use the SYSPRO e.net business objects or the supported import tools to post data. Direct updates can break integrity and support agreements.
Common mistakes
Common report errors include joining on the wrong key, reporting stock without warehouse, and ignoring company-specific databases. SYSPRO keeps a separate database per company, so make sure your query points at the right one.
Frequently Asked Questions
Does SYSPRO use SQL Server?
Yes, current SYSPRO versions run on Microsoft SQL Server. Each company normally has its own database named SysproCompanyX style, plus a system-wide database. Always confirm the database names in your installation before pointing reports at them.
Can I write directly to these tables?
You should not. Direct writes bypass SYSPRO business rules and audit trails. Use the e.net business objects, import tools or supported APIs to change data, and keep direct SQL for read-only reporting.
Why do column names differ on my system?
Versions, service packs and customisations can add, rename or change columns. Check INFORMATION_SCHEMA or the SYSPRO data dictionary for your exact build, and avoid copying queries between versions without testing.
Where can I find every table?
This page lists only common tables. For a complete list, query sys.tables on your SQL Server database or use the data dictionary supplied by SYSPRO for your release.
If your reports and dashboards depend on deep knowledge of SYSPRO tables, Netray can help set up read-only natural-language access over your ERP data.
Related Tools
Sage Evolution SQL Query Generator for Stock and Debtors
Builds read-only SQL queries for stock items and customer accounts in a Sage Evolution company database.
Other ERPsSYSPRO Month-End Close Checklist
Tick-off checklist for closing a period in SYSPRO across inventory, purchase orders, WIP, receivables, payables and the general ledger.
ERP Migration & SelectionAfrica ERP Implementation Readiness Assessment
Ten questions that score data quality, infrastructure, tax compliance, skills and sponsorship before you commit to an ERP project.
Country & TaxAfrica and Middle East VAT Rates Reference
Standard VAT rates, currency codes and tax authorities for 22 African and Gulf countries, built for ERP tax code and multi-country setup.
More Other ERPs tools
See all- SYSPRO BOM Material Cost Rollup Worksheet
- Infor VISUAL Work Order Status and Structure Reference
- Infor VISUAL Manufacturing Scheduling Checklist
- Infor XA (MAPICS) Period End Close Checklist
- Infor VISUAL Database Table Reference
- Infor XA (MAPICS) Application Module Reference
- IBM i Commands for Infor XA Administrators Reference
- Acumatica Generic Inquiry Design Template
- Acumatica Manufacturing Edition Setup Checklist
New to SYSPRO? Start with the SYSPRO guide and toolkit, or plan with Training Path Builder, Upgrade Path Planner, ERP Table and Field Explorer.
Keep exploring
Free tools
- SYSPRO SQL Query GeneratorGenerate read-only SQL Server queries against common SYSPRO tables. Fill in database and filters, then copy the code.
- SYSPRO Private AI Layer Blueprint GeneratorGenerate a shareable architecture plan for adding a private, on-prem AI assistant to SYSPRO: read replica, e.net business objects, retrieval index, local model serving, permissions and audit.
- SYSPRO AI Assistant Sizing and Value CalculatorEstimate GPUs, index size and monthly value for a private AI assistant on SYSPRO. Enter your named users, usage pattern and cost assumptions to see peak concurrency, daily token volume and payback.
ERP fixes and how-tos
- SYSPRO tables list: core database tables by module and safe queriesSYSPRO database naming, the core tables by module for inventory, sales orders and WIP, and safe read-only SQL patterns for reporting without risking data.
- How to Add AI to SYSPRO On-Prem Without Moving Your DataReference architecture for adding a private AI assistant to on-prem SYSPRO: SQL Server read replica, e.net business objects, retrieval, local GPU and audit.
- SYSPRO API integration: e.net business objects, REST, EDI and OfficeHow to integrate with SYSPRO 8: e.net business objects, web service and REST options, EDI and Office integration, with a table of which route fits which job.
AI on your ERP
- AI for SYSPRO production and job costingHow AI reads SYSPRO WIP jobs, labor and material postings to explain job cost variances and late work orders, with read-only access and on-prem hosting.
- AI for SYSPRO, Grounded in Your Own Manufacturing DataAdd AI to SYSPRO without moving your manufacturing data to a public model. On-premise and private-cloud LLMs for SYSPRO in Australia, NA, and beyond.
Integrations
- How to use ChatGPT with SYSPROHow to use ChatGPT with SYSPRO: exporting data vs live access, custom GPT actions over a SYSPRO API, enterprise data controls, and when a private model is better.
- How to use Claude with SYSPROHow to use Claude with SYSPRO: MCP connectors, Anthropic API, AWS Bedrock or Google Vertex, enterprise data handling, and the on-prem alternative for sensitive data.