# SyteLine Customer Order Tables Columns Reference

> Source: https://netray.co/tools/syteline-customer-order-tables-columns-reference
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

The key columns in SyteLine 9/10 customer order tables, what they mean, how they join and how to use them in custom reports.

## Category

syteline

## Erp

Infor SyteLine

## Audience

- SyteLine report writer
- SQL developer
- ERP administrator

## Tool

**Kind:** worksheet

**Mode:** reference

**Columns:**

#### Table

**Key:** table

**Type:** text

#### Column

**Key:** column

**Type:** text

#### Meaning

**Key:** meaning

**Type:** text

#### Typical values or type

**Key:** values

**Type:** text

#### Join to

**Key:** join

**Type:** text

#### Report tip

**Key:** tip

**Type:** text

**Rows:**

**Table:** co_mst

**Column:** co_num

**Meaning:** Customer order number

**Values:** Text, key

**Join:** coitem_mst.co_num

**Tip:** Always join on co_num plus site_ref in multi-site databases

**Table:** co_mst

**Column:** cust_num

**Meaning:** Customer number

**Values:** Text

**Join:** custaddr_mst.cust_num

**Tip:** Use with cust_seq to reach the right address

**Table:** co_mst

**Column:** cust_seq

**Meaning:** Customer address sequence

**Values:** 0 for the bill-to, higher for ship-tos

**Join:** custaddr_mst.cust_seq

**Tip:** cust_seq 0 gives the main customer name

**Table:** co_mst

**Column:** order_date

**Meaning:** Order date

**Values:** Date

**Tip:** Use for bookings by period

**Table:** co_mst

**Column:** type

**Meaning:** Order type

**Values:** R regular, B blanket

**Tip:** Blanket orders carry lines in co_bln_mst with releases in coitem_mst

**Table:** co_mst

**Column:** stat

**Meaning:** Order status

**Values:** Status code

**Tip:** See the job and order status codes reference for meanings

**Table:** co_mst

**Column:** cust_po

**Meaning:** Customer PO number

**Values:** Text

**Tip:** Common search field for customer service reports

**Table:** co_mst

**Column:** slsman

**Meaning:** Salesperson

**Values:** Text

**Tip:** Group bookings by salesperson

**Table:** co_mst

**Column:** terms_code

**Meaning:** Payment terms code

**Values:** Text

**Tip:** Useful in credit and AR reports

**Table:** coitem_mst

**Column:** co_num

**Meaning:** Order number

**Values:** Text

**Join:** co_mst.co_num

**Tip:** Part of the line key

**Table:** coitem_mst

**Column:** co_line

**Meaning:** Order line

**Values:** Integer

**Join:** co_ship_mst.co_line

**Tip:** Part of the line key

**Table:** coitem_mst

**Column:** co_release

**Meaning:** Line release

**Values:** Integer, 0 for regular lines

**Join:** co_ship_mst.co_release

**Tip:** Blanket releases use values above 0

**Table:** coitem_mst

**Column:** item

**Meaning:** Item ordered

**Values:** Text

**Join:** item_mst.item

**Tip:** Join item_mst for description and product code

**Table:** coitem_mst

**Column:** cust_item

**Meaning:** Customer's item number

**Values:** Text

**Tip:** Show it on customer-facing reports

**Table:** coitem_mst

**Column:** qty_ordered

**Meaning:** Quantity ordered

**Values:** Decimal, in base unit of measure

**Tip:** Open qty is commonly qty_ordered minus qty_shipped

**Table:** coitem_mst

**Column:** qty_shipped

**Meaning:** Quantity shipped

**Values:** Decimal

**Tip:** Compare with co_ship_mst totals when auditing

**Table:** coitem_mst

**Column:** qty_invoiced

**Meaning:** Quantity invoiced

**Values:** Decimal

**Tip:** Shipped not invoiced = qty_shipped minus qty_invoiced

**Table:** coitem_mst

**Column:** qty_returned

**Meaning:** Quantity returned

**Values:** Decimal

**Tip:** Net it out of shipped quantities for true shipments

**Table:** coitem_mst

**Column:** price

**Meaning:** Unit price

**Values:** Decimal, order currency

**Tip:** Check the order currency before summing across orders

**Table:** coitem_mst

**Column:** disc

**Meaning:** Line discount percent

**Values:** Decimal

**Tip:** Net value = qty * price * (1 - disc / 100)

**Table:** coitem_mst

**Column:** due_date

**Meaning:** Line due date

**Values:** Date

**Tip:** Basis for late-line reports

**Table:** coitem_mst

**Column:** promise_date

**Meaning:** Promised date

**Values:** Date

**Tip:** Compare with due_date for on-time to promise

**Table:** coitem_mst

**Column:** stat

**Meaning:** Line status

**Values:** Status code

**Tip:** Filter open lines by status, not only by quantity

**Table:** coitem_mst

**Column:** whse

**Meaning:** Shipping warehouse

**Values:** Text

**Join:** itemwhse_mst.whse

**Tip:** Join itemwhse_mst on item and whse for on-hand

**Table:** coitem_mst

**Column:** u_m

**Meaning:** Unit of measure

**Values:** Text

**Tip:** Quantities are stored in the item's base unit

**Table:** coitem_mst

**Column:** ref_type, ref_num, ref_line_suf, ref_release

**Meaning:** Supply linked to the line

**Values:** Reference type plus document keys

**Join:** job_mst or poitem_mst depending on ref_type

**Tip:** Shows the job or PO supplying a make-to-order line

**Table:** co_ship_mst

**Column:** co_num, co_line, co_release

**Meaning:** Line the shipment belongs to

**Values:** Keys

**Join:** coitem_mst

**Tip:** Join on all three columns

**Table:** co_ship_mst

**Column:** date_seq

**Meaning:** Shipment sequence for the line

**Values:** Integer

**Tip:** Several shipments per line are normal

**Table:** co_ship_mst

**Column:** ship_date

**Meaning:** Shipment date

**Values:** Date

**Tip:** Use for shipments by period and on-time delivery

**Table:** co_ship_mst

**Column:** qty_shipped

**Meaning:** Quantity on this shipment

**Values:** Decimal

**Tip:** Sum per line to reconcile with coitem_mst.qty_shipped

**Table:** co_bln_mst

**Column:** co_num, co_line

**Meaning:** Blanket order line

**Values:** Keys

**Join:** coitem_mst on co_num and co_line

**Tip:** Releases for the blanket line sit in coitem_mst

**Table:** co_bln_mst

**Column:** item

**Meaning:** Item on the blanket line

**Values:** Text

**Join:** item_mst.item

**Tip:** Use for blanket coverage reports

**Table:** custaddr_mst

**Column:** cust_num, cust_seq

**Meaning:** Customer address key

**Values:** Keys

**Join:** co_mst on cust_num and cust_seq

**Tip:** Join on both columns

**Table:** custaddr_mst

**Column:** name

**Meaning:** Customer or ship-to name

**Values:** Text

**Tip:** Use cust_seq 0 for the customer name

**Table:** join

**Column:** co_mst to coitem_mst

**Meaning:** Order header to lines

**Values:** ON co.co_num = ci.co_num

**Join:** Add site_ref in multi-site databases

**Tip:** Header filters such as order date go on co_mst

**Table:** join

**Column:** coitem_mst to co_ship_mst

**Meaning:** Lines to shipments

**Values:** ON s.co_num = ci.co_num AND s.co_line = ci.co_line AND s.co_release = ci.co_release

**Tip:** Use LEFT JOIN to keep unshipped lines

**Table:** join

**Column:** co_mst to custaddr_mst

**Meaning:** Order to customer address

**Values:** ON ca.cust_num = co.cust_num AND ca.cust_seq = co.cust_seq

**Tip:** Use cust_seq 0 instead for the bill-to name

**Notes:** Every _mst table also carries system columns: site_ref, RowPointer, RecordDate, CreateDate and audit columns such as CreatedBy and UpdatedBy. Status code meanings are in the job and order status codes reference. Confirm columns in SSMS or in the SLCos and SLCoitems IDO property lists for your version before relying on them in production reports.

## Content

**Intro:** This is a column-level reference for the customer order tables in Infor SyteLine 9 and 10: co_mst, coitem_mst, co_ship_mst, co_bln_mst and the custaddr_mst join. Each row gives the meaning, typical values, join and a report tip, and three standard joins are included as rows.

**Sections:**

#### How to use it

**Body:** Filter by table to see the columns you need, or search for a business term such as 'due' or 'invoiced'. Build reports on a reporting copy or read-only login, starting from coitem_mst for anything line based (open orders, late lines, backlog) and from co_mst for header facts (order date, customer, salesperson). Add co_ship_mst when you need shipment dates rather than totals. If you prefer an IDO or REST route, the same data comes through SLCos and SLCoitems, with property names in mixed case such as CoNum and CoLine.

#### Worked example: open order backlog

**Body:** For a backlog report, select from coitem_mst joined to co_mst on co_num and to custaddr_mst on cust_num and cust_seq. Keep lines whose status is open, calculate open quantity as qty_ordered minus qty_shipped, and value it as open quantity times price times (1 - disc / 100), converting currency where orders are not in your domestic currency. Group by customer and due_date month, and flag lines where due_date is earlier than today. Export to Excel from SSMS, Report Builder or your BI tool.

**Bullets:**

- Open qty = qty_ordered - qty_shipped
- Open value = open qty * price * (1 - disc / 100)
- Late = due_date earlier than today with open qty above zero

#### Multi-site and system columns

**Body:** Every _mst table includes site_ref, and in a multi-site database the same order number can exist for more than one site, so include site_ref in every join and filter. RowPointer is a unique GUID per row, useful for change tracking and for linking notes and attachments. RecordDate is updated on change, which makes it the practical column for incremental extracts to a data warehouse. CreateDate and the audit columns record who created and changed rows. Views without the _mst suffix filter by the current site context and are often not what a reporting login expects.

#### Common mistakes

**Body:** The most frequent error is joining coitem_mst to co_ship_mst on co_num and co_line only, which multiplies rows for blanket releases; include co_release. The second is summing price across orders in different currencies. Third, filtering open lines by quantity alone includes lines that were closed short; use status as well, with meanings from the job and order status codes reference. Finally, remember that blanket orders keep their line definition in co_bln_mst and their releases in coitem_mst.

**Cta:** If you want sales and planning to ask SyteLine about orders, backlog and shipments in plain English on your own servers, we can set that up.

**Faq:**

#### Which tables hold customer orders in SyteLine?

**Answer:** co_mst holds the order header, coitem_mst the lines and releases, co_ship_mst the shipments per line, and co_bln_mst the blanket order lines. Customer names and addresses come from custaddr_mst, joined on cust_num and cust_seq. The SLCos and SLCoitems IDOs expose the same data through Mongoose.

#### How do I export SyteLine reports to Excel?

**Answer:** Most standard reports can be output to Excel formats from the report options, and grid views on forms can be exported from the client. For custom reports, run the SQL against a reporting copy and export from SSMS, or use the IDO REST API or your BI tool to load data straight into Excel or Power BI.

#### What does cust_seq mean on a customer order?

**Answer:** cust_seq is the customer address sequence. Sequence 0 is the main customer, used as the bill-to, and higher sequences are ship-to addresses. Join co_mst to custaddr_mst on both cust_num and cust_seq to get the ship-to on the order, or force cust_seq 0 to get the customer name.

#### How do I find the job supplying a customer order line?

**Answer:** Read ref_type, ref_num, ref_line_suf and ref_release on coitem_mst. When the reference type points to a job, ref_num and ref_line_suf give the job and suffix to join to job_mst; when it points to a PO, they give the PO and line. Map the stored ref_type values in your own database first.

## Search terms

syteline custom reports, syteline reporting, tables and views for erp, export syteline reports to excel, syteline coitem table, syteline co_mst columns, syteline customer order sql, coitem_mst

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