Please enable JavaScript to view this site.

Made in EU
Visma.net Financials Forums

Visma.net Financials API Data Model

Navigation: Package: vnt_inventory > Procedures

vnt_inventory.inventory_putbyinventoryid: Visma.net Financials Package for Inventory operations that could not be mapped to a table.

Response Message has StatusCode NoContent if PUT operation succeed

Parameters of Procedure

The following parameters can be used to control the behaviour of the procedure vnt_inventory.inventory_putbyinventoryid. 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 `begin package.procedure(value1, value2, value3); end` on a procedure 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 `begin package.procedure(name1 => value1, name3 => value3); end` on the same procedure 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

p_inventoryID

int32

☑

 

Identifies the inventory item to update

p_inventoryNumber

string

☐

 

Mandatory for POST, not applicable for PUT. The unique alphanumeric identifier of the item that is used in UI.

p_status

string

☐

 

 

p_type

string

☐

 

 

p_description

string

☐

 

 

p_body

string

☐

 

 

p_itemClass

string

☐

 

Mandatory, the item class to which the item is assigned. Selecting a class provides default settings for the item.

p_postingClass

string

☐

 

The posting class of the item, which by default is the posting class assigned to the item class.

p_vatCode

string

☐

 

The vat category of the item, which by default is the vat category associated with the item class.

p_defaultPrice

string

☐

 

The price of the item. This price is used as the default price, if there are no other prices set.

p_baseUnit

string

☐

 

 

p_salesUnit

string

☐

 

 

p_purchaseUnit

string

☐

 

 

p_expenseAccrualAccount

string

☐

 

Only used for Non-stock items

p_inventoryAccount

string

☐

 

Only used for Stock items

p_expenseAccount

string

☐

 

Only used for Non-stock items

p_cogsAccount

string

☐

 

Only used for Stock items

p_expenseNonTaxableAccount

string

☐

 

 

p_expenseEuAccount

string

☐

 

 

p_expenseImportAccount

string

☐

 

 

p_salesAccount

string

☐

 

 

p_salesNonTaxableAccount

string

☐

 

 

p_salesEuAccount

string

☐

 

 

p_salesExportAccount

string

☐

 

 

p_packaging

string

☐

 

This class represents a Packaging part of InventoryItem in InventoryItemController. Used for insert/update data.

p_intrastat

string

☐

 

This class represents a Intrastat part of InventoryItem in InventoryItemController. Used for insert/update data.

p_defaultWarehouse

string

☐

 

General information tab > Warehouse defaults section > Default warehouse > The default warehouse used to store the stock item with the specified item ID.

p_defaultIssueFrom

string

☐

 

General information tab > Warehouse defaults section > Default issue from > The location of the warehouse to be used by default to issue quantities of the selected stock item.

p_defaultReceiptTo

string

☐

 

General information tab > Warehouse defaults section > Default receipt to > The location of warehouse to be used by default to receive certain quantities of the specified stock item.

p_kitItem

string

☐

 

 

p_note

string

☐

 

 

 

23-06-2025 19:16 Version 24.1.116-BETA+5455

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