# SyteLine Material Transaction and Reference Types Reference

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

## Short answer

The transaction and reference types behind SyteLine material transactions, with where each comes from and whether it counts as usage, so you can build reliable usage and aging reports.

## Category

syteline

## Erp

Infor SyteLine

## Audience

- SyteLine report writer
- Inventory analyst
- ERP administrator

## Tool

**Kind:** worksheet

**Mode:** reference

**Columns:**

#### List

**Key:** section

**Type:** select

**Options:**

- Transaction type
- Reference type

#### Type

**Key:** type

**Type:** text

#### Typically created by

**Key:** source

**Type:** text

#### Effect on on-hand

**Key:** onhand

**Type:** text

#### Reference fields

**Key:** ref

**Type:** text

#### Counts as usage

**Key:** usage

**Type:** select

**Options:**

- Yes
- No
- Depends

#### Stored code

**Key:** code

**Type:** text

**Help:** Fill in from the decode query on your own database

**Rows:**

**Section:** Transaction type

**Type:** Adjustment

**Source:** Quantity Adjustment

**Onhand:** + or - by sign of quantity

**Ref:** Usually Inventory reference

**Usage:** No

**Section:** Transaction type

**Type:** Misc Receipt

**Source:** Miscellaneous Receipt

**Onhand:** +

**Ref:** Usually Inventory reference

**Usage:** No

**Section:** Transaction type

**Type:** Misc Issue

**Source:** Miscellaneous Issue

**Onhand:** -

**Ref:** Usually Inventory reference

**Usage:** Depends

**Section:** Transaction type

**Type:** Stock Move

**Source:** Quantity Move

**Onhand:** None at warehouse level; moves between locations

**Ref:** Inventory

**Usage:** No

**Section:** Transaction type

**Type:** Other Cost

**Source:** Cost-only postings

**Onhand:** None

**Ref:** Check the reference type on the row

**Usage:** No

**Section:** Transaction type

**Type:** Receipt

**Source:** Purchase Order Receiving and other receipts

**Onhand:** + when received to stock

**Ref:** Purchase Order: PO number, line, release

**Usage:** No

**Section:** Transaction type

**Type:** Ship

**Source:** Order Shipping

**Onhand:** - (returns reverse the sign)

**Ref:** Customer Order: order, line, release

**Usage:** Yes

**Section:** Transaction type

**Type:** Transfer

**Source:** Transfer order ship and receive

**Onhand:** - at source, + at destination

**Ref:** Transfer: transfer order and line

**Usage:** Depends

**Section:** Transaction type

**Type:** Transfer Loss

**Source:** Transfer order receipt with loss

**Onhand:** Removes quantity lost in transit

**Ref:** Transfer

**Usage:** No

**Section:** Transaction type

**Type:** Cycle Count

**Source:** Cycle Count Update

**Onhand:** + or - by count variance

**Ref:** Inventory

**Usage:** No

**Section:** Transaction type

**Type:** Physical Inventory

**Source:** Physical inventory posting

**Onhand:** + or - by count variance

**Ref:** Inventory

**Usage:** No

**Section:** Transaction type

**Type:** Finish

**Source:** Job completion to stock (job receipt)

**Onhand:** + finished item

**Ref:** Job: job, suffix, operation

**Usage:** No

**Section:** Transaction type

**Type:** Labor/Next Operation

**Source:** Job labor and move transactions

**Onhand:** None; moves quantity between operations

**Ref:** Job

**Usage:** No

**Section:** Transaction type

**Type:** Issue/WIP Change

**Source:** Job Material Transactions

**Onhand:** - on issue, + on return

**Ref:** Job: job, suffix, operation

**Usage:** Yes

**Section:** Transaction type

**Type:** Withdrawal/Return

**Source:** Material withdrawals and returns against an order

**Onhand:** - on withdrawal, + on return

**Ref:** Check the reference type on the row

**Usage:** Yes

**Section:** Transaction type

**Type:** Split/Merge/Create

**Source:** Lot split, merge and create activity

**Onhand:** Net zero across lots when balanced

**Ref:** Inventory

**Usage:** No

**Section:** Transaction type

**Type:** Scrap

**Source:** Scrap reported on job operations

**Onhand:** None on stock; reduces WIP

**Ref:** Job

**Usage:** Depends

**Section:** Reference type

**Type:** Inventory

**Source:** Inventory forms not tied to an order

**Onhand:** See transaction type

**Ref:** Reference number usually blank

**Usage:** Depends

**Section:** Reference type

**Type:** Customer Order

**Source:** Order Shipping and order returns

**Onhand:** See transaction type

**Ref:** ref_num = order, ref_line_suf = line, ref_release = release

**Usage:** Yes

**Section:** Reference type

**Type:** Purchase Order

**Source:** Purchase Order Receiving and returns

**Onhand:** See transaction type

**Ref:** ref_num = PO, ref_line_suf = line, ref_release = release

**Usage:** No

**Section:** Reference type

**Type:** RMA

**Source:** RMA return processing

**Onhand:** See transaction type

**Ref:** RMA number and line

**Usage:** No

**Section:** Reference type

**Type:** Transfer

**Source:** Transfer order ship and receive

**Onhand:** See transaction type

**Ref:** Transfer order number and line

**Usage:** Depends

**Section:** Reference type

**Type:** Job

**Source:** Job material, labor and completion

**Onhand:** See transaction type

**Ref:** ref_num = job, ref_line_suf = suffix, ref_release = operation

**Usage:** Yes

**Section:** Reference type

**Type:** SRO

**Source:** Service order material

**Onhand:** See transaction type

**Ref:** SRO number and its line or operation

**Usage:** Yes

**Section:** Reference type

**Type:** Project JIT Production

**Source:** Project just-in-time production

**Onhand:** See transaction type

**Ref:** Project identifiers

**Usage:** Depends

**Section:** Reference type

**Type:** Production Schedule

**Source:** Production schedule (repetitive) transactions

**Onhand:** See transaction type

**Ref:** Production schedule identifiers

**Usage:** Depends

**Section:** Reference type

**Type:** Work Center

**Source:** Work Center Material Transactions

**Onhand:** See transaction type

**Ref:** Work center

**Usage:** Yes

**Notes:** Type and reference lists follow the SyteLine Material Transactions report and Reference Type help. Single-letter stored codes are left blank on purpose: map them in your own database with SELECT trans_type, ref_type, COUNT(*), MIN(trans_date), MAX(trans_date) FROM matltran_mst GROUP BY trans_type, ref_type and compare a few rows with the Material Transactions form. Confirm column names in SSMS for your version.

## Content

**Intro:** This reference decodes Infor SyteLine 8, 9 and 10 material transactions: the 17 transaction types and 10 reference types, where each comes from, how it moves on-hand and whether it belongs in an item usage report. A decode query lets you map the stored codes in your own matltran_mst table.

**Sections:**

#### How to use it

**Body:** Every inventory movement in SyteLine writes a row to the material transaction table, matltran_mst, shown on the Material Transactions form. Two fields tell you what happened: the transaction type (what kind of movement) and the reference type (what document it belongs to). Use the Transaction type rows to decide which movements to include in a report and the Reference type rows to know how to read ref_num, ref_line_suf and ref_release. Then run the decode query from the notes and fill the Stored code column for your database, since that is what your SQL will filter on.

#### Worked example: an item usage report

**Body:** Usage normally means consumption: material issued to jobs, shipped to customers, issued to service orders and consumed at work centers. Start from matltran_mst, keep the Ship and Issue/WIP Change transaction types, and add Withdrawal/Return and Misc Issue only if your site uses them for consumption rather than corrections. Exclude Stock Move, Cycle Count, Physical Inventory and Adjustment, which correct quantities rather than consume them. Group by item and month on trans_date, and sum quantity with its sign so returns net against issues instead of inflating usage.

**Bullets:**

- Include: Ship, Issue/WIP Change, work center and SRO issues
- Decide per site: Misc Issue, Withdrawal/Return, Scrap, Transfer
- Exclude: Stock Move, Cycle Count, Physical Inventory, Adjustment

#### Inventory aging from transactions

**Body:** An aging report needs the date each unit on hand arrived. For lot-tracked items, use the lot creation or receipt date. For untracked items, a common method is first-in-first-out back-allocation: take current on-hand, walk receipt-type rows (Receipt, Finish, Misc Receipt and positive adjustments) from newest to oldest until the quantity is covered, and age each slice by its trans_date. Leave Stock Move rows out, since they change location, not age. State the method on the report so readers know it is an estimate built from transactions.

#### Gotchas

**Body:** Do not hard-code letters you found in a forum: map trans_type and ref_type from your own data with the decode query, because a wrong letter silently drops a whole class of rows. The sign of the quantity carries the direction, so a customer return through Order Shipping can appear as a Ship row with negative quantity. Reference fields change meaning by reference type: for jobs ref_line_suf is the job suffix, for orders it is the line. Large sites have millions of rows, so filter on trans_date and item in reports and run them on a reporting copy.

**Cta:** If you want planners to ask 'what did we use of this item last quarter' in plain English against SyteLine on your own servers, we can set that up.

**Faq:**

#### Which SyteLine table holds material transactions?

**Answer:** matltran_mst holds the material transaction history shown on the Material Transactions form, one row per movement with item, warehouse, location, transaction type, reference type, reference number fields, date and quantity. Related cost detail is stored with the transaction. Use it for usage, movement and aging reports.

#### What are the trans_type codes in matltran?

**Answer:** The stored values are single-letter codes mapped to the 17 transaction types in this table. We do not list letters because they must be confirmed for your version. Run SELECT trans_type, ref_type, COUNT(*) FROM matltran_mst GROUP BY trans_type, ref_type and compare sample rows with the Material Transactions form to map them.

#### How do I build an item usage report in SyteLine?

**Answer:** Filter matltran_mst to consumption transaction types (shipments and job issues, plus any site-specific issue types), sum signed quantity by item and period on trans_date, and exclude moves, counts and adjustments. Returns then net against issues. Check totals against the Material Transactions form for one item before trusting the report.

#### Why does my SyteLine inventory aging not match on-hand?

**Answer:** Usually because moves or counts were treated as receipts, or because the back-allocation started from the wrong on-hand figure. Age only receipt-type rows, start from current on-hand per item and warehouse, and treat counts and adjustments consistently. Lot-tracked items are better aged from lot dates than from transactions.

## Search terms

syteline item usage report, syteline inventory aging report, syteline reporting, sightline reporting, syteline matltran, syteline material transactions, matltran_mst trans_type, syteline transaction types

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