Navigation: Schema: InventoryTransfer > Tables

InventoryTransferLineAllocations: Visma.net Financials Inventor Transfer Line Allocations

Get a range of Inventory Transfers - ScreenId=IN304000Request page size must be 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

Catalog: VismaNet

Schema: InventoryTransfer

Label: Inventor Transfer Line Allocations

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 InventoryTransferLineAllocations. 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
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.
greaterThanValue	string	☐
lastModifiedDateTime	string	☐
lastModifiedDateTimeCondition	string	☐
numberToRead	int32	☐	This field has been deprecated and will be removed in future versions. Use pagenumber and pagesize for pagination purposes. Pagenumber and pagesize does not work with NumberToRead and SkipRecords.
orderBy	string	☐	This field has been deprecated and will be removed in future versions. The OrderBy parameter has no effect on the result.
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.
skipRecords	int32	☐	This field has been deprecated and will be removed in future versions. Use pagenumber and pagesize for pagination purposes. Pagenumber and pagesize does not work with NumberToRead and SkipRecords.
status	string	☐	Waarden: Hold, Balanced, Released.

Columns of Table Function

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

Name	Data Type	Label	Required	Documentation
batchNumber	string	Batch Number	☐	The reference number of the batch generated for the receipt. Click the number to open the Journal Transactions (GL.30.10.00) form and view the details of the transactions.
branchNumber_name_1	string		☐	Click the magnifier. > The name.
branchNumber_name	string	Branch Name	☐	Click the magnifier. > The name.
branchNumber_number_1	string		☐	Click the magnifier. > The identifier.
branchNumber_number	string	Branch Number	☐	Click the magnifier. > The identifier.
COMPANY_CODE	string(30)	Company Code	☑	Partition code, segmenting the data.
COMPANY_NAME	string(240)	Company Name	☑	Name of the partition.
controlQuantity	double	Control Quantity	☐	The manually entered quantity of inventory items. Control Qty. is available only if the Validate Document Totals on Entry option is selected on the Inventory Preferences form. If the Control Qty. and Total Qty.values do not match, the system generates a warning message and the issue cannot be saved.
date	datetime	Date	☐	The date when the receipt was created. All transactions included in this document will have this transaction date.
description_1	string		☐	A brief description of the inventory issue or its transactions.
description	string	Description	☐	Description > A brief description of the goods transfer transaction.
errorInfo	string	Error Message	☐
expirationDate	datetime	Expiration Date	☐
externalReference	string	External Reference	☐	The external reference number of the inventory issue document (for example, the vendor’s reference code).
hold	boolean	Hold	☐	A check box that you select to give the receipt the On Hold status. Clear the check box to save the receipt with the Balanced status.
inventoryItem_description	string		☐	Name of item/description
inventoryItem_number	string		☐	Number of item
lastModifiedDateTime	datetime	Last Modified	☐	The date when the document was last modified.
lineNbr	int32		☐
lineNumber	int32	Line Number	☐
location_countryId_1	string		☐	Location*.
location_countryId	string	Location Country ID	☐	Location*.
location_id_1	string		☐	Click the magnifier > The identifier
location_id	string	Location ID	☐	Click the magnifier > The identifier
location_name_1	string		☐	Click the magnifier > The displayed name
location_name	string	Location Name	☐	Click the magnifier > The displayed name
lotSerialNumber_1	string		☐
lotSerialNumber	string		☐
metadata_maxPageSize	int64		☐
metadata_totalCount	int64	Total Count	☐
postPeriod	string	Post Period	☐	The financial period to which the transactions recorded in the document should be posted. Format MMYYYY.
quantity_1	double		☐	Quantity > The quantity of the transferred goods (in the units indicated below).
quantity	double	Quantity	☐
reasonCode_description	string	Reason Code Description	☐	Click on the magnifier. > The description.
reasonCode_id	string	Reason Code ID	☐	Click on the magnifier. > The identifier.
referenceNumber	string	Reference Number	☐	The unique reference number of the receipt, which the system automatically assigns according to the numbering sequence selected for receipts on the Inventory Preferences IN.10.10.00) form.
status	string	Status	☐	The current status of the receipt. The following options are available: On Hold:The receipt/issue is a draft and can be edited. Receipts with this status cannot be released.Balanced: The receipt/issue data has been validated by the system and the receipt can be released. It also can be modified or deleted, but changes can be saved only if the receipt is balanced.Released: The receipt/issue has been released and cannot be edited or deleted.
toLocation_countryId	string		☐	Location*.
toLocation_id	string		☐	Click the magnifier > The identifier
toLocation_name	string		☐	Click the magnifier > The displayed name
totalQuantity	double	Total Quantity	☐	The total quantity of inventory items, which the system calculates automatically, for the document.
toWarehouse_description	string	To Warehouse Description	☐	Click on the magnifier. > The description.
toWarehouse_id	string	To Warehouse ID	☐	Click on the magnifier. > The identifier.
uom	string	Unit of Measure	☐	Mandatory field: UoM* > The unit of measure (UoM) used for the goods to be transferred.
warehouse_description	string	Warehouse Description	☐	Click on the magnifier. > The description.
warehouse_id	string	Warehouse 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

InventoryTransferLineAllocations: Visma.net Financials Inventor Transfer Line Allocations

Parameters of Table Function

Columns of Table Function

Important Safety and Usage Information