Navigation: Catalog: VismaNet > Schemas > Schema: Account > Tables

Accounts: Visma.net Financials General Ledger Accounts

Get a range of General ledger accounts - ScreenId=GL202500Data for Account

Catalog: VismaNet

Schema: Account

Primary Keys: accountCd

Label: General Ledger Accounts

Retrieve: true

Insert: true

Update: true

Delete: false

Parameters of Table Function

The following parameters can be used to control the behaviour of the table function Accounts. 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	Required	Documentation
active	☐	Set to True to select active accounts.
analysisCode	☐	Filter by Analysis code (field used for sorting and inquiries.)
externalCode1	☐	Filter by External code 1 (field used for sorting and inquiries.)
externalCode2	☐	Filter by External code 2 (field used for sorting and inquiries.)
greaterThanValue	☐	Enter the from-value for Account no.
includeAccountClassDescription	☐	Set to True to include AccountClass description.
lastModifiedDateTime	☐	This value, generated by the system, indicates the last time the record was modified. Use it to retrieve all records that have been modified since that time, up to the present.Accepted format:* ```yyyy-MM-dd```* ```yyyy-MM-dd HH:mm:ss```* ```yyyy-MM-dd HH:mm:ss.FFF```* ```yyyy-MM-ddTHH:mm:ss```* ```yyyy-MM-ddTHH:mm:ss.FFF```_Note:_ __LastModifiedDateTime__ and __LastModifiedDateTimeCondition__ are __mutually inclusive__.
lastModifiedDateTimeCondition	☐	This value represents the condition to be applied when retrieving records.Accepted values (without the single quotes):* '>' for greater than* '<' for less than* '>=' for greater than or equal* '<=' for less than or equal_Note:_ __LastModifiedDateTime__ and __LastModifiedDateTimeCondition__ are __mutually inclusive__.
publicCode	☐	Filter by the Public code 1, authorities mapped code to the account.

Columns of Table Function

The columns of the table function Accounts 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	Documentation
accountCD	varchar2	Account Code	☐	Mandatory field: The table > Account* > The unique identifier of the general ledger account in the system.
accountClass	varchar2	Account Class	☐	The table > Account class > Optional. The account class to which the account is assigned.
accountClassDescription	varchar2		☐	The table > Desc > An alphanumeric string of up to 30 characters that describes the AccountClass.
accountGroupCD	varchar2	Account Group Code	☐	The table > Account group > The account group (used in project management if the Projects module has been activated) that includes this account.
accountID	int32	Account ID	☐	The table > AccountID > The Account ID is the actual ID that the account have in the database and are used in other tables as the relation between the Chart of accounts table and other tables.
active	char	Active	☐	The table > Active > A check box that indicates that the account is active.
allowManualEntry	char		☐
analisysCodeInfo_description	varchar2		☐	Name of item/description
analisysCodeInfo_number	varchar2		☐	Number of item
cashAccount	char	Cash Account	☐	The table > Cash account > A check box that indicates (if selected) that the account has a cash account or multiple cash accounts linked to it.
COMPANY_CODE	varchar2(30)	Company Code	☑	Partition code, segmenting the data.
COMPANY_NAME	varchar2(240)	Company Name	☑	Name of the partition.
controlAccountModule	varchar2		☐
currency	varchar2	Currency	☐	The table > Currency > Optional: This column appears only if support for multiple currencies has been activated for the system.
description	varchar2	Description	☐	The table > Description > An alphanumeric string of up to 30 characters that describes the account.
errorInfo	varchar2	Error Message	☐
externalCode1Info_description	varchar2		☐	Name of item/description
externalCode1Info_number	varchar2		☐	Number of item
externalCode2Info_description	varchar2		☐	Name of item/description
externalCode2Info_number	varchar2		☐	Number of item
lastModifiedDateTime	datetime	Last Modified	☐	This information is not visible in the window. It is collected from the system.
metadata_maxPageSize	int64	Metadata Max Pagesize	☐
metadata_totalCount	int64	Total Count	☐
postOption	varchar2	Post Option	☐	The table > Post option > An option that defines how transactions created in other workspaces are posted to this account. Summary (default) or Detail.
publicCode1	varchar2	Public Code 1	☐	The table > Public code 1 > The authorities valid code mapped to the account. Used for example in SAF-T and in some nationals reporting to the authorities.
taxCategory	varchar2	Tax Category	☐	The table > VAT category > A tax category that you define for the selected account. When you create a journal transaction manually in the GL301000 window, based on this VAT category, the taxable amount will be calculated for the journal entry.
timeStamp	blob	Timestamp	☐
type	varchar2	Type	☐	The table > Type > The type of account: Asset, Liability, Income, or Expense.
useDefaultSub	char		☐	The table > Use default sub > A check box that causes the system (if selected) to set the default subaccount as the Subaccount if the account is selected.

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

Accounts: Visma.net Financials General Ledger Accounts

Parameters of Table Function

Columns of Table Function

Important Safety and Usage Information