# TransactionByNumber: Twinfield Transaction by number ## Documentation The head of one financial transaction, of whichever daybook. Carries what a browse does not: where the transaction came from, who entered it and when it was last changed. Its lines are answered by TransactionLinesByNumber. - Catalog: `Twinfield` - Schema: `Settings` - Label: Transaction by number The data in this table is partitioned per value of the `COMPANY_CODE` column. This is a read-only table function. The Twinfield API may not support changing the data or the Invantive UniversalSQL driver for Twinfield does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Twinfield API. ## Parameters of Table Function The following parameters can be used to control the behaviour of the table function `TransactionByNumber`. A value must be provided at all times for required parameters, but optional parameters in general do not need to have a value and the execution will default to a pre-defined behaviour. Values can be specified by position and by name. In both cases, all parameters not specified will be evaluated using their default values. Value specification by position is done by listing all values from the first to the last needed value. For example: a `select * from table(value1, value2, value3)` on a table with four parameters will use the default value for the fourth parameter and the specified values for the first three. Value specification by name is done by listing all values that require a value. For example with `select * from table(name1 => value1, name3 => value3)` on the same table will use the default values for the second and fourth parameters and the specified values for the first and third. | Name | Data Type | Required | Default Value | Documentation | |---|:---:|:---:|:---:|---| | `code` | `` | ☑ | | Code of the daybook, such as VRK for sales. | | `COMPANY_CODE` | `` | ☑ | | Code of company. | | `number` | `` | ☑ | | Number of the transaction within the daybook. | ## Columns of Table Function The columns of the table function `TransactionByNumber` are shown below. Each column has an SQL data type. | Name | Data Type | Label | Required | Documentation | |---|:---:|---|:---:|---| | `CODE_NAME` | `varchar2` | Daybook name | ☐ | | | `CODE` | `varchar2` | Code | ☐ | Code of the daybook. | | `COMPANY_CODE` | `varchar2` | Company ID | ☑ | | | `COMPANY_NAME` | `varchar2` | Company Name | ☑ | | | `CURRENCY` | `varchar2` | Currency | ☐ | | | `DATE` | `datetime` | Date | ☐ | | | `DUEDATE` | `datetime` | Due date | ☐ | | | `FREETEXT1` | `varchar2` | Free text 1 | ☐ | | | `FREETEXT2` | `varchar2` | Free text 2 | ☐ | | | `FREETEXT3` | `varchar2` | Free text 3 | ☐ | | | `INPUTDATE` | `datetime` | Input date | ☐ | | | `INVOICENUMBER` | `varchar2` | Invoice number | ☐ | | | `MODIFICATIONDATE` | `datetime` | Modified | ☐ | | | `NUMBER` | `varchar2` | Number | ☐ | | | `OFFICE` | `varchar2` | Office | ☐ | | | `ORIGIN` | `varchar2` | Origin | ☐ | How the transaction came about, such as by hand or from a bank statement. | | `ORIGINREFERENCE` | `varchar2` | Origin reference | ☐ | | | `PAYMENTREFERENCE` | `varchar2` | Payment reference | ☐ | | | `PERIOD` | `varchar2` | Period | ☐ | Financial period, as year and period separated by a solidus. | | `USER_NAME` | `varchar2` | User name | ☐ | | | `USER` | `varchar2` | User | ☐ | User who entered the transaction. |