---
title: "SalesOrderTypeByType (Visma.net Financials)"
description: "Sales Order Type by Type"
language: en
source_language: en
translation_state: complete
canonical: https://documentation.invantive.eu/en/datamodels/vismanet/VismaNet.SalesOrderType.SalesOrderTypeByType
original: https://documentation.invantive.eu/en/datamodels/vismanet/VismaNet.SalesOrderType.SalesOrderTypeByType
updated: 2026-11-01T17:49:50Z
license: https://documentation.invantive.eu/en/
---

# SalesOrderTypeByType: Visma.net Financials Sales Order Type by Type

`read only` `REST`

- Catalog: `VismaNet`
- Schema: `SalesOrderType`
- Label: Sales Order Type by Type

Get a specific SO OrderType

Can only retrieve data.

## API Source

- Endpoint: `/v1/salesordertype/{orderType}`
- Operation: `get /v1/salesordertype/{orderType}`

## Performance Characteristics

| Characteristic | Value |
|---|---:|
| Average access latency (ms) | 155 |
| Full scan rows per minute | 29,100 |
| Point query rows per minute | 387 |

The result can be cached on the client.

## Parameters

| Name | Data Type | Required | Default | Documentation |
|---|---|:---:|---|---|
| `orderType` | `` | [x] |  | Identifies the SO OrderType |

## Table Columns

The columns of the table `SalesOrderTypeByType` are shown below. Each column has an SQL data type. A new non-null value must be provided for every required column at all times during insert and update.

| Name | Data Type | Label | Required | Marks | Documentation |
|---|---|---|:---:|---|---|
| `COMPANY_CODE` | `varchar2(30)` | Company Code | [x] | writable | Partition code, segmenting the data. |
| `COMPANY_NAME` | `varchar2(240)` | Company Name | [x] | writable | Name of the partition. |
| `active` | `char` | Active | [ ] | filters on the platform, writable, `active` | The top part &gt; Active &gt; A check box that indicates (if selected) that the order type is active, |
| `behavior` | `varchar2` | itgen_vnet_behavior | [ ] | filters on the platform, writable, `behavior` | Template settings tab &gt; Automation behaviour &gt; An automation behaviour is a set of automation steps. The type of automation behaviour used for the template, which can be Sales order, Invoice, Quote, Credit note, or RMA order. |
| `customerDocumentType` | `varchar2` | itgen_vnet_customerdocumenttype | [ ] | filters on the platform, writable, `customerDocumentType` | Template settings tab &gt; Customer document type &gt; The type of customer ledger document to be generated on release of a document of this type. |
| `defaultOperation` | `varchar2` | itgen_vnet_defaultoperation | [ ] | filters on the platform, writable, `defaultOperation` | Template settings tab &gt; Default operation &gt; The default inventory operation for the order type, which can be Receipt or Issue. |
| `description` | `varchar2` | Description | [ ] | filters on the platform, writable, `description` | The top part &gt; Description &gt; The brief description of the order type. |
| `errorInfo` | `varchar2` | Error Message | [ ] | filters on the platform, writable, `errorInfo` |  |
| `metadata_maxPageSize` | `int64` | Metadata Max Pagesize | [ ] | filters on the platform, writable, `metadata.maxPageSize` |  |
| `metadata_totalCount` | `int64` | Total Count | [ ] | filters on the platform, writable, `metadata.totalCount` |  |
| `orderType` | `varchar2` | Order Type | [ ] | filters on the platform, writable, `orderType` | Mandatory field: The top part &gt; Order type* &gt; The ID of the order type, which is a two-character alphanumeric string. |



## Release Notes

What changed per release in the tables, columns, attributes and capabilities of the driver:

- [Visma.net Financials](/en/release-notes/drivers?driver=visma-net-financials)

