ProjectTransactionByReferenceNumber: Visma.net Financials Project Transaction by Reference Number
read only REST
- Catalog:
VismaNet - Schema:
ProjectTransaction - Label: Project Transaction by Reference Number
Get a specific Project transaction document
Data for project transaction
The response headers include an ETag after a successful GET operation.
Can only retrieve data.
Summary
Data for project transaction
The response headers include an ETag after a successful GET operation.
API Source
- Endpoint:
/v1/projecttransaction/{refNbr} - Operation:
get /v1/projecttransaction/{refNbr}
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 |
|---|---|---|---|---|
refNbr |
`` | Identifies the project transaction document |
Table Columns
The columns of the table ProjectTransactionByReferenceNumber 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_ |
varchar2 |
Company Code | writable | Partition code, segmenting the data. | |
COMPANY_ |
varchar2 |
Company Name | writable | Name of the partition. | |
description |
varchar2 |
Description | filters on the platform, writable, description |
The top part > Description > The description provided for the transaction. | |
error |
varchar2 |
Error Message | filters on the platform, writable, error |
||
metadata_ |
int64 |
Metadata Max Pagesize | filters on the platform, writable, metadata. |
||
metadata_ |
int64 |
Total Count | filters on the platform, writable, metadata. |
||
module |
varchar2 |
Module | filters on the platform, writable, module |
The top part > Module > The module you create the transactions in. | |
note |
varchar2 |
Note | filters on the platform, writable, note |
||
orig |
varchar2 |
Original Document Number | filters on the platform, writable, orig |
The top part > Orig. doc. no. > The reference number of the underlying document for the transaction. | |
orig |
varchar2 |
Original Document Type | filters on the platform, writable, orig |
The top part > Orig. doc. no. > The type of the document the transaction is based on. It has one of the following values: Allocation, Time card, Case, Expense claim, Allocation reversal, Reversal, Credit note. | |
refNbr |
varchar2 |
Reference Number | filters on the platform, writable, refNbr |
The top part > Ref. no. > The reference number of the transaction. | |
status |
varchar2 |
Status | filters on the platform, writable, status |
The top part > Status > The status of the transaction. The following statuses are possible: Balanced, Released. | |
time |
blob |
Timestamp | filters on the platform, writable, time |
Identifier that represents a specific version of the resource. It helps to prevent simultaneous updates of the resource from overwriting each other (by using ETags and If-Match headers) |
Release Notes
What changed per release in the tables, columns, attributes and capabilities of the driver: