Please enable JavaScript to view this site.

Visma.net Financials Forums

Navigation: Schema: Account > Tables

AccountByCode: Visma.net Financials General Ledger Account by Code

Get a specific Account - ScreenId=GL202500

Catalog: VismaNet

Schema: Account

Label: General Ledger Account by Code

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 AccountByCode. 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

accountCd

string

 

Return the Information from Chart of account for the specified AccountCD

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.

 

Columns of Table Function

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

Name

Data Type

Label

Required

Documentation

accountCD

string

Account Code

Mandatory field: The table > Account* > The unique identifier of the general ledger account in the system.

accountClass

string

Account Class

The table > Account class > Optional. The account class to which the account is assigned.

accountGroupCD

string

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

boolean

Active

The table > Active > A check box that indicates that the account is active.

analysisCode

string

Analysis Code

The table > Analysis code > A field that can be used for sorting and inquiries. Either enter in field or predfine in GL20253S.

cashAccount

boolean

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

string(30)

Company Code

Partition code, segmenting the data.

COMPANY_NAME

string(240)

Company Name

Name of the partition.

currency

string

Currency

The table > Currency > Optional: This column appears only if support for multiple currencies has been activated for the system.

description

string

Description

The table > Description > An alphanumeric string of up to 30 characters that describes the account.

externalCode1

string

External Code 1

The table > External code 1 > A field that can be used for sorting and inquiries. Either enter in field or predfine in GL20251S.

externalCode2

string

External Code 2

The table > External code 2 > A field that can be used for sorting and inquiries. Either enter in field or predfine in GL20252S.

lastModifiedDateTime

datetime

Last Modified

This information is not visible in the window. It is collected from the system.

postOption

string

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

int32

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

string

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.

type

string

Type

The table > Type > The type of account: Asset, Liability, Income, or Expense.

useDefaultSub

boolean

 

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.

 

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

X

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.

  
Disclaimer