# SYSPRO Common Table Name Reference

> Source: https://netray.co/tools/syspro-table-name-reference
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Searchable list of frequently used SYSPRO tables with module, purpose and key columns, for report writers and integrators.

## Category

other-erp

## Erp

SYSPRO

## Region

South Africa

## Audience

- SYSPRO consultant
- Report developer
- Business analyst

## Tool

**Kind:** worksheet

**Mode:** reference

**Columns:**

#### Table

**Key:** table

**Type:** text

#### Module

**Key:** module

**Type:** text

#### Purpose

**Key:** purpose

**Type:** text

#### Typical key columns

**Key:** keys

**Type:** text

**Rows:**

**Table:** InvMaster

**Module:** Inventory

**Purpose:** Stock code master record

**Keys:** StockCode

**Table:** InvWarehouse

**Module:** Inventory

**Purpose:** Stock quantities by warehouse

**Keys:** StockCode, Warehouse

**Table:** InvMovements

**Module:** Inventory

**Purpose:** Inventory movement history

**Keys:** StockCode, Warehouse

**Table:** ArCustomer

**Module:** Accounts Receivable

**Purpose:** Customer master

**Keys:** Customer

**Table:** ArInvoice

**Module:** Accounts Receivable

**Purpose:** Open receivable invoices

**Keys:** Customer, Invoice

**Table:** ApSupplier

**Module:** Accounts Payable

**Purpose:** Supplier master

**Keys:** Supplier

**Table:** ApInvoice

**Module:** Accounts Payable

**Purpose:** Payable invoices

**Keys:** Supplier, Invoice

**Table:** SorMaster

**Module:** Sales Orders

**Purpose:** Sales order header

**Keys:** SalesOrder

**Table:** SorDetail

**Module:** Sales Orders

**Purpose:** Sales order lines

**Keys:** SalesOrder, SalesOrderLine

**Table:** PorMasterHdr

**Module:** Purchase Orders

**Purpose:** Purchase order header

**Keys:** PurchaseOrder

**Table:** PorMasterDetail

**Module:** Purchase Orders

**Purpose:** Purchase order lines

**Keys:** PurchaseOrder, Line

**Table:** WipMaster

**Module:** Work in Progress

**Purpose:** Job header

**Keys:** Job

**Table:** BomStructure

**Module:** Bill of Materials

**Purpose:** Bill of material components

**Keys:** ParentPart, Component

**Table:** GenMaster

**Module:** General Ledger

**Purpose:** General ledger account master

**Keys:** GlCode

**Table:** GenJournalDetail

**Module:** General Ledger

**Purpose:** General ledger journal lines

**Keys:** GlCode, Journal

**Table:** SalBranch

**Module:** Sales Analysis

**Purpose:** Customer delivery branches

**Keys:** Customer, Branch

**Notes:** 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.

## Content

**Intro:** 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.

**Sections:**

#### How to use the reference

**Body:** 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

**Body:** 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.

**Bullets:**

- 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

**Body:** 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

**Body:** 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.

**Cta:** 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.

**Faq:**

#### Does SYSPRO use SQL Server?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

syspro table names, syspro database tables, syspro invmaster, syspro sorMaster table, syspro sql server tables, syspro reporting tables, syspro crystal reports tables

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