itgendoc001X
xMsg javascript has not been loaded.
Visma.net Financials API Data ModelGet a specific employee time cards
Catalog: VismaNet
Schema: Employee
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.
Select Visma.net Financials API URL: /controller/api/v1/employee/{employeeCd}/timecards
Insert Visma.net Financials API URL: /controller/api/v1/employee/{employeeCd}/timecards
Update Visma.net Financials API URL: /controller/api/v1/employee/{employeeCd}/timecards
Delete Visma.net Financials API URL: /controller/api/v1/employee/{employeeCd}/timecards
Field Selection Method: NotRequired
Base Path: materials[*]
Select Visma.net Financials API Operation: get /controller/api/v1/employee/{employeeCd}/timecards
Table Function Parameters
The following parameters can be used to control the behaviour of the table function EmployeeTimeCardMaterialsByEmployeeCode. 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 treated using their default values.
Value specification by position is done by listing all values from the first to the last needed value. For example with `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 |
|---|---|---|---|---|
COMPANY_CODE |
string |
☐ |
|
Partition to retrieve data from. |
employeeCd |
string |
☑ |
|
Identifies the employee |
greaterThanValue |
string |
☐ |
|
Greater-than value. The item which is the object for this, varies from API to API. |
lastModifiedDateTime |
string |
☐ |
|
System-generated value for last modification of transaction/record. Use format: YYYY-MM-DD HH:MM (date and time) to filter from date to present. |
lastModifiedDateTimeCondition |
string |
☐ |
|
System-retrieved information for state/condition. |
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. |
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 |
☐ |
|
The status of the document. (Values: Hold, Open, Approved, Rejected, Released) |
type |
string |
☐ |
|
Identifies the type of the time card (Normal, Corrected, NormalCorrected) (Values: Normal, Correction, NormalCorrected) |
week |
string |
☐ |
|
Identifies the week number of the time card |
Table Function Columns
The columns of the table function EmployeeTimeCardMaterialsByEmployeeCode are shown below. Each column has an SQL data type.
Name |
Data Type |
Label |
Required |
Documentation |
|---|---|---|---|---|
approvalStatus |
string |
Approval Status |
☐ |
The top part > Approval status > The approval status of the time card |
approvalStatusText |
string |
Approval Status Text |
☐ |
|
COMPANY_CODE |
string(30) |
Company Code |
☑ |
Partition code, segmenting the data. |
COMPANY_NAME |
string(240) |
Company Name |
☑ |
Name of the partition. |
description |
string |
Description |
☐ |
Description > The description of the reported quantity. |
employee_internalId |
string |
|
☐ |
|
employee_name |
string |
|
☐ |
The name of the particular destination of the selected type. |
employee_number |
string |
|
☐ |
The identifier of the particular destination of the selected type. |
errorInfo |
string |
Error Message |
☐ |
|
fri |
double |
|
☐ |
Fri > The quantity reported for Friday. |
invoiceable |
int32 |
Invoiceable |
☐ |
The top part > Regular column: Invoicable > The invoiceable work hours spent by the employee during the week |
invoiceableOvertime |
int32 |
Invoiceable Overtime |
☐ |
The top part > Overtime column: Invoicable > The invoiceable overtime spent by the employee during the week |
invoiceableTotalTime |
int32 |
Invoiceable Total Time |
☐ |
The top part > Total column: Invoicable > The total invoiceable working time (regular and overtime) for the week |
itemId |
string |
Item ID |
☐ |
Item Id |
lastModifiedDateTime_1 |
datetime |
|
☐ |
System generated information: The last time the time card line was modified |
lastModifiedDateTime |
datetime |
Last Modified |
☐ |
|
lineNumber |
int32 |
Line Number |
☐ |
The time card line number |
metadata_maxPageSize |
int64 |
|
☐ |
|
metadata_totalCount |
int64 |
Total Count |
☐ |
|
mon |
double |
|
☐ |
Mon > The quantity reported for Monday. |
origRefNbr |
string |
|
☐ |
The top part > Orig. ref. no. > The reference number of the time card being corrected. This box is filled in only when Correction is specified in the Type box |
overtimeSpent |
int32 |
Overtime Spent |
☐ |
The top part > Overtime column: Time spent > The work hours spent by the employee during the week on activities with the Overtime earning type. |
project_description |
string |
Project Description |
☐ |
Click on the magnifier. > The description. |
project_id |
string |
Project ID |
☐ |
Click on the magnifier. > The identifier. |
projectTask_description |
string |
Project Task Description |
☐ |
Click on the magnifier. > The description. |
projectTask_id |
string |
Project Task ID |
☐ |
Click on the magnifier. > The identifier. |
refNbr |
string |
Reference Number |
☐ |
The top part > Ref. no. > The unique reference number of the time card, which Acumatica ERP automatically assigns according to the numbering sequence specified as the Time Card Numbering Sequence on the Time and Expenses Preferences (EP.10.10.00) form. |
sat |
double |
|
☐ |
Sat > The quantity reported for Saturday. |
status |
string |
Status |
☐ |
The top part > Status > The status of the time card |
sun |
double |
Sunday |
☐ |
Sun > The quantity reported for Sunday. |
thu |
double |
|
☐ |
Thu > The quantity reported for Thursday. |
timeSpent |
int32 |
Time Spent |
☐ |
The top part > Regular column: Time spent > The work hours spent by the employee during the week on activities with the Regular Hours earning type. |
totalQty |
double |
|
☐ |
Total Qty |
totalTimeSpent |
int32 |
Total Time Spent |
☐ |
The top part > Total column: Time spent > The total working time (regular and overtime) for the week |
tue |
double |
Tuesday |
☐ |
Tue > The quantity reported for Tuesday. |
type |
string |
Type |
☐ |
The top part > Type > The type of the time card. The following options are available:• Normal: Regular time card• Correction: Corrective time card, which is a time card that updates a released time card |
uoM |
string |
Unit of Measure |
☐ |
The unit of measure of item |
wed |
double |
Wednesday |
☐ |
Wed > The quantity reported for Wednesday. |
week_description |
string |
Week Description |
☐ |
Name of item/description |
week_number |
string |
Week Number |
☐ |
Number of item |
06-04-2021 14:55 Version 20.1.393-BETA+3152
