Navigation: Schema: JournalTransactionV2 > Tables

JournalTransactionLinesByPeriodOrDateV2: Visma.net Financials Journal Transaction Line Attachments by Period or Date

Get a range of Journal Transactions - ScreenId=GL301000. On this particular endpoint, pagesize and totalcount denotes number of journaltransaction lines. When using pagination, the transactions for one specific batch can be split into several responses. Please use a page size lower or equal to the allowed max page size which is returned under metadata. If pagesize is greater than the max page size, it will be limited to max page size.

Catalog: VismaNet

Schema: JournalTransactionV2

Label: Journal Transaction Line Attachments by Period or Date

The data in this table is partitioned per value of the COMPANY_CODE column.

This is a read-only table function. The Visma.net Financials API may not support changing the data or the Invantive SQL driver for Visma.net Financials does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Visma.net Financials API.

Parameters of Table Function

The following parameters can be used to control the behaviour of the table function JournalTransactionLinesByPeriodOrDateV2. 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	Documentation
branch	string	☐	Branch to query data for.
COMPANY_CODE	string	☐	Partition to retrieve data from.
erp-api-background	string	☐	If a URL value is provided, then API endpoint will be queued and executed in background. When the execution of the background operation is finished, the system will POST the response to the specified URL. The endpoint itself responds in this case with a 202-Accepted status and a reference to a state document for the background operation.
expandAttachments	boolean	☐	If true there will be included all attachments regarding batch. Default on false
lastModifiedDateTime	string	☐	When setting this parameter there will be exported only the batches changed or created since the provided date and time. Mandatory if 'PeriodId' is not provided. Format: yyyy-MM-dd HH:mm:ss
module	string	☐	Module to query data for. Allowed values: GL, AP, AR, CM, CA, IN, DR, FA, PM
pageNumber	int32	☐	Pagination parameter. Page number.
pageSize	int32	☐	Pagination parameter. Number of items to be collected.Please use a page size lower or equal to the allowed max page size which is returned as part of the metadata information.If requested page size is greater than allowed max page size, request will be limited to max page size.
periodId	string	☐	Financial Period to query data for. Mandatory if 'LastModifiedDateTime' not provided. Format: YYYYPP
releasedBatch	boolean	☐	If true there will be exported the batches having Released flag on true. If false there will be exported the batches having Released flag on false. If not set no filtering based on Released flag is applied

Columns of Table Function

The columns of the table function JournalTransactionLinesByPeriodOrDateV2 are shown below. Each column has an SQL data type.

Name	Data Type	Label	Required	Documentation
accountNumber	string	General Ledger Account Number	☐	Mandatory field: The table > Account* > The account (associated with the specified branch) whose balance will be updated by the journal entry.
autoReversing	boolean		☐	The top part > Automatic reversing > A check box that indicates (if selected) that the batch is auto-reversing.
batchNumber	string	Batch Number	☐	The top part > Batch number > The unique ID of the batch, which is generated by the numbering sequence assigned to batches in the GL102000 window.
branch_1	string		☐	The top part > Branch > The branch to which this batch is related. This field is available if your company is set up with branches.
branch	string	Branch	☐	The table > Branch > The branch associated with this journal entry.
COMPANY_CODE	string(30)	Company Code	☑	Partition code, segmenting the data.
COMPANY_NAME	string(240)	Company Name	☑	Name of the partition.
controlTotal	double	Total for Control	☐	The top part > Control total > The control total of the batch, which is used for batch status validation.
controlTotalInCurrency	double		☐	Background calculation giving you the Control total in your default currency. This field is applicable if the amount is given in another currency than your default.
createVatTransaction	boolean		☐	The top part > Create VAT transactions > A check box that indicates (if selected) that a VAT-related transaction can be created manually; select this check box when you begin to create the transaction.
creditAmount	double	Credit Amount	☐	The table > Credit amount > The credit amount of the journal entry.
creditAmountInCurrency	double		☐	Background calculation giving you the Credit amount in your default currency. This field is applicable if the amount is given in another currency than your default.
creditTotal	double		☐	The top part > Credit total > The total of transaction credit amounts for the batch; the value is calculated automatically.
creditTotalInCurrency	double		☐	Background calculation giving you the Credit total in your default currency. This field is applicable if the amount is given in a another currency than your default.
currencyId	string	Currency ID	☐	The top part > Currency > The currency used for all the journal transactions in the selected batch.
customerSupplier	string		☐	The table > Customer/Supplier > The customer or supplier associated with the entry.
debitAmount	double	Debit Amount	☐	The table > Debit amount > The debit amount of the journal entry.
debitAmountInCurrency	double		☐	Background calculation giving you the debit amount in your default currency. This field is applicable if the amount is given in another currency than your default.
debitTotal	double	Debit Total	☐	The top part > Debit total > The total of transaction debit amounts for the batch; the value is calculated automatically.
debitTotalInCurrency	double		☐	Background calculation giving you the Debit total in your default currency. This field is applicable if the amount is given in another currency than your default.
description_1	string		☐	The top part > Description > A description of the batch.
description	string	Description	☐	The table > Description > A detailed description provided by a user or generated by the system.
errorInfo	string	Error Message	☐
exchangeRate	double	Exchange Rate	☐	Ingformation collected from the system to calculate currency amount.
financialPeriod	string	Financial Period	☐	Mandatory field: The top part Post period* > The financial period to which the transactions should be posted. Format YYYYMM.
hold	boolean	Hold	☐	The top part > Hold > A check box that indicates (if selected) that the batch has the On hold status and cannot be released or posted. You can clear the check box only if the batch has total debits equal to total credits.
inventoryNumber	string	Inventory Number	☐	Item ID > The item ID of the line item, if applicable.
lastModifiedDateTime	datetime	Last Modified	☐	System generated information.
ledger	string	Ledger	☐	Mandatory field: The top part > Ledger* > The unique ID of the ledger to which batch transactions are posted. By default, it is the default posting ledger specified for the branch in the GL101010 window, but another posting ledger can be selected.
ledgerDescription	string	Ledger Description	☐	Mandatory field: The top part > Ledger* > Click the magnifier > The description of the ledger to which batch transactions are posted. By default, it is the default posting ledger specified for the branch in the GL101010 window, but another posting ledger can be selected.
lineNumber	int32	Line Number	☐	The table > Number at the left indicating the line number of the table.
metadata_maxPageSize	int64		☐
metadata_totalCount	int64	Total Count	☐
module_1	string		☐	The top part > Workspace > The workspace where the batch originates. New batches can be created only for General ledger.
module	string	Module	☐	The workspace where the batch originates. See module in the Top part > Workspace
note	string	Note	☐
originalBatchNumber	string		☐	The top part > Orig. batch number > For a scheduled or auto-reversing batch, the reference number of the batch used as a template.
postPeriod	string	Post Period	☐	Mandatory field: The top part > Post period* > The financial period to which the transactions recorded in the document should be posted. Format MMYYYY.
project_description	string	Project Description	☐	Click on the magnifier. > The description.
project_id	string	Project ID	☐	Click on the magnifier. > The identifier.
projectTask_description	string	Project Task Description	☐	Click on the magnifier. > The description.
projectTask_id	string	Project Task ID	☐	Click on the magnifier. > The identifier.
quantity	double	Quantity	☐	The table > Quantity > The quantity of items associated with the transaction, if relevant.
referenceNumber	string	Reference Number	☐	The table > Ref. no. > The reference number of the external or internal document associated with the journal transaction.
reversingEntry	boolean		☐	The top part > Reversing entry > A check box that indicates (if selected) that the batch is a reversing batch. The Orig.batch number field displays the ID of the batch that was reversed by this batch.
skipVatAmountValidation	boolean		☐	The top part > Skip VAT amount validation > A check box that (if selected) causes automatic validation of a VAT-related transaction that you create manually to be skipped.
status	string	Status	☐	The top part > Status > The current status of the batch. The status defines what processing can be applied to the batch. The following options are available: On hold, Balanced, Scheduled, Unposted, Posted, Void.
subaccount_active	boolean		☐	Active > The status of the identifier.
subaccount_description	string	Subaccount Description	☐	Description > The description of the identifier.
subaccount_errorInfo	string	Sub Account Error Message	☐
subaccount_lastModifiedDateTime	datetime	Sub Account Last Modified	☐	System generated information.
subaccount_metadata_maxPageSize	int64		☐
subaccount_metadata_totalCount	int64		☐
subaccount_subaccountId	int32	Sub Account ID	☐	SubID > The identifier of the subaccount.
subaccount_subaccountNumber	string	Sub Account Number	☐	Mandatory field: Subaccount* > The subaccount number. Format 9-XX.
transactionCode	string		☐
transactionCodeDescription	string		☐	The Table part > Transaction description > A description of the transaction or any comments relevant to the transaction.
transactionDate	datetime		☐	Mandatory field: The top part > Transaction date* > The date when the batch was created, which relates to the transaction dates of the journal entries.
transactionDescription	string		☐	The table > Transaction Description > A description of the transaction or any comments relevant to the transaction.
transactionType	string		☐	The top part > Type > The type of this general ledger batch, which is specified by the system automatically.
uom	string	Unit of Measure	☐	The table > UoM > The quantity of items associated with the transaction, if relevant.
vat_description	string		☐	Click on the magnifier. > The description.
vat_id	string	VAT ID	☐	Click on the magnifier. > The identifier.
vatCode_description	string	VAT Code Description	☐	Click on the magnifier. > The description.
vatCode_id	string	VAT Code ID	☐	Click on the magnifier. > The identifier.

22-12-2022 21:03 Version 22.1.101-BETA+3681

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.

Please enable JavaScript to view this site.

Visma.net Financials API Data Model Visma.net Financials Forums

JournalTransactionLinesByPeriodOrDateV2: Visma.net Financials Journal Transaction Line Attachments by Period or Date

Parameters of Table Function

Columns of Table Function

Important Safety and Usage Information