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

EmployeeExpenseClaimDetailAttachmentsByEmployeeCode: Visma.net Financials Employee Expense Claim Detail Attachments by Employee Code

Get expense claims for a specific employee

Catalog: VismaNet

Schema: Employee

Label: Employee Expense Claim Detail Attachments by Employee Code

This is a read-only table function. The Visma.net Financials API may not support changing the data or the Invantive UniversalSQL 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 EmployeeExpenseClaimDetailAttachmentsByEmployeeCode. 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
customer	☐	The customer from the document
date	☐	The date of the document
departmentId	☐	Identifies the department
employeeCd	☑	Identifies the employee
greaterThanValue	☐	Greater-than value. The item which is the object for this, varies from API to API.
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__.
orderBy	☐	This field has been deprecated and will be removed in future versions. The OrderBy parameter has no effect on the result.
status	☐	The status of the document. (Values: Hold, PendingApproval, Approved, Rejected, Released)

Columns of Table Function

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

Name	Data Type	Label	Required	Documentation
amountInClaimCurr	double		☐	Amount in claim currency > The amount claimed by the employee, which is expressed in the currency of the expense claim.
approvalDate	datetime	Approval Date	☐	The top part > Approval date > The date when the claim was approved.
approvalStatus_2	varchar2		☐	The top part > Approval status > The status of the claim in Approval.
approvalStatus	varchar2	Approval Status	☐	Approval status > The approval status, which indicates whether the detail row requires approval and, if it does, what the current state of approval is.
approvalStatusText_2	varchar2		☐	The top part > Approval status > A text field.
approvalStatusText	varchar2	Approval Status Text	☐	Last approval comment > The approval status text suitable for display
approver	varchar2	Approver	☐	Pending approver > The identifier of the person authorized to approve the activity, if approval is required. This is either the approver of the project task or, if no approver is assigned to the project task, the project manager.
arReferenceNbr	varchar2		☐	REef.no. customer > The reference number of the customer ledger document.
branch_name	varchar2	Branch Name	☐	Click the magnifier. > The name.
branch_number	varchar2	Branch Number	☐	Click the magnifier. > The identifier.
claimAmount	double	Claim Amount	☐	Claim amount > The amount claimed by the employee, which is calculated as the total claim amount minus the employee part.
claimDetailId	int32	Claim Detail ID	☐	Identifies the expense claim detail id, necessary when updating detail information
claimedBy_internalId	varchar2	Claimed by - Internal ID	☐
claimedBy_name	varchar2	Claimed by - Name	☐	The name of the particular destination of the selected type.
claimedBy_number	varchar2	Claimed by - Number	☐	The identifier of the particular destination of the selected type.
claimTotal	double	Claim Total	☐	The top part > Claim total > The total amount of the claim.
COMPANY_CODE	varchar2(30)	Company Code	☑	Partition code, segmenting the data.
COMPANY_NAME	varchar2(240)	Company Name	☑	Name of the partition.
currency_2	varchar2		☐	The top part > Currency > The currency of the claim.
currency	varchar2	Currency	☐	Currency > The currency of the expense receipt. However, if you enter a claim line directly, the currency value is read-only and matching the claim currency.
customer_name_2	varchar2		☐	Click the magnifier. > The name.
customer_name	varchar2	Customer Name	☐	Click the magnifier. > The name.
customer_number_2	varchar2		☐
customer_number	varchar2	Customer Number	☐
date_2	datetime		☐	Mandatory field: The top part > Date* > The date when the claim was entered.
date	datetime	Date	☐	Mandatory field: Date > The date when the expense was incurred.
department_description	varchar2	Department Description	☐	Click on the magnifier. > The description.
department_id	varchar2	Department ID	☐	Click on the magnifier. > The identifier.
description_2	varchar2	Description 2	☐	Mandatory field: The top part > Description > A description of the claim.
description	varchar2	Description	☐	Mandatory field: Description* > A description of the transaction.
employeePart	double		☐	Employee part > The part of the total amount that will not be paid back to the employee. The percentage depends on the company policy.
errorInfo	varchar2	Error Message	☐
expenseAccount_active	char		☐
expenseAccount_description	varchar2	Expense Account Description	☐	Name of item/description
expenseAccount_externalCode1	varchar2		☐	Account class > The identifier of the account class.
expenseAccount_externalCode2	varchar2		☐	Account class > The name of the account class.
expenseAccount_number	varchar2	Expense Account Number	☐	Number of item
expenseAccount_type	varchar2	Expense Account Type	☐	Account > The account number.
expenseItem_description	varchar2		☐	Name of item/description
expenseItem_number	varchar2		☐	Number of item
expenseSubaccount_active	char		☐
expenseSubaccount_description	varchar2		☐	Click on the magnifier. > The description.
expenseSubaccount_id	varchar2		☐	Click on the magnifier. > The identifier.
id	guid	ID	☐	The ID of the attachment
invoiceable	char	Invoiceable	☐	Invoicable > A check box that, if selected, indicates that the claim amount is invoiceable to the customer (the total amount minus the employee's part).
lastModifiedDateTime	datetime	Last Modified	☐	System generated information: The lastest time the expense claim was modified
lineId	guid		☐	The expense claim line id
location_description_2	varchar2		☐	Click on the magnifier. > The description.
location_description	varchar2	Location Description	☐	Click on the magnifier. > The description.
location_id_2	varchar2	Location ID 2	☐	Click on the magnifier. > The identifier.
location_id	varchar2	Location ID	☐	Click on the magnifier. > The identifier.
metadata_maxPageSize	int64	Metadata Max Pagesize	☐
metadata_totalCount	int64	Total Count	☐
name	varchar2	Name	☐	The name of the attachment.
project_description	varchar2	Project Description	☐	Click on the magnifier. > The description.
project_id	varchar2	Project ID	☐	Click on the magnifier. > The identifier.
project_internalId	int32		☐	The internal identifier.
projectTask_description	varchar2	Project Task Description	☐	Click on the magnifier. > The description.
projectTask_id	varchar2	Project Task ID	☐	Click on the magnifier. > The identifier.
projectTask_internalId	int32		☐	The internal identifier.
quantity	double	Quantity	☐	Quantity > The quantity of this expense item.
refNbr_2	varchar2		☐	The top part > Ref. no. > The unique reference number of the expense claim document.
refNbr	varchar2	Reference Number	☐	Ref. no. > The identifier of the transaction.
revision	int32	Revision	☐	The version of the attachment.
salesAccount_active	char		☐
salesAccount_description	varchar2	Sales Account Description	☐	Name of item/description
salesAccount_externalCode1	varchar2		☐	Account class > The identifier of the account class.
salesAccount_externalCode2	varchar2		☐	Account class > The name of the account class.
salesAccount_number	varchar2	Sales Account Number	☐	Number of item
salesAccount_type	varchar2	Sales Account Type	☐	Account > The account number.
salesSubaccount_active	char		☐
salesSubaccount_description	varchar2		☐	Click on the magnifier. > The description.
salesSubaccount_id	varchar2		☐	Click on the magnifier. > The identifier.
status	varchar2	Status	☐	The top part > Status > The current status of the expense claim: On Hold/Pending Approval/Approved/Rejected/Released.
taxCategory_description	varchar2		☐	Name of item/description
taxCategory_number	varchar2		☐	Number of item
timeStamp	blob	Timestamp	☐	Identifier that represents a specific version of the resource.It helps to prevent simultaneous updates of the resource from overwriting each other (by using ETags and If-Match headers)
totalAmount	double	Total Amount	☐	Amount > The total amount paid for the expense item in the specified quantity.
unitCost	double	Unit Cost	☐	Unit cost > The cost of a unit of the item.
uom	varchar2	Unit of Measure	☐	Mandatory field: UoM > The unit of measure in which the quantity is shown.
vatExemptTotal	double	VAT Exempt Total	☐	The top part > VAT exempt total > The document total that is exempt from VAT.
vatTaxableTotal	double	VAT Taxable Total	☐	The top part > VAT taxable total > The document total that is subjected to VAT.

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

EmployeeExpenseClaimDetailAttachmentsByEmployeeCode: Visma.net Financials Employee Expense Claim Detail Attachments by Employee Code

Parameters of Table Function

Columns of Table Function

Important Safety and Usage Information