Loket.nl REST API Data Model
JournalAllocationAllocationBasedOnFixedWeightsByEmploymentId |
List of journal allocations for an employment__Activity name:__ GetJournalAllocationsByEmploymentIdGet the list of financial journal allocations (journaliseren module) for an employment.
Catalog: LoketNlRest
Schema: JournalAllocation
This is a read-only table function. The loket.nl (REST) API may not support changing the data or the Invantive SQL driver for loket.nl (REST) does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the loket.nl (REST) API.
Select loket.nl (REST) API URL: /providers/employers/employees/employments/{employmentId}/journalallocations
Insert loket.nl (REST) API URL: /providers/employers/employees/employments/{employmentId}/journalallocations
Update loket.nl (REST) API URL: /providers/employers/employees/employments/{employmentId}/journalallocations
Delete loket.nl (REST) API URL: /providers/employers/employees/employments/{employmentId}/journalallocations
Field Selection Method: NotRequired
Base Path: _embedded[*].allocationBasedOnFixedWeights[*]
Select loket.nl (REST) API Operation: get /providers/employers/employees/employments/{employmentId}/journalallocations
Table Function Parameters
The following parameters can be used to control the behaviour of the table function JournalAllocationAllocationBasedOnFixedWeightsByEmploymentId. 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 |
|---|---|---|---|---|
employmentId |
guid |
☑ |
|
The unique identifier of the employment |
Table Function Columns
The columns of the table function JournalAllocationAllocationBasedOnFixedWeightsByEmploymentId are shown below. Each column has an SQL data type.
Name |
Data Type |
Label |
Required |
Documentation |
|---|---|---|---|---|
allocationBasedOnActualHours_costCenter_code |
string |
|
☐ |
|
allocationBasedOnActualHours_costCenter_description |
string |
|
☐ |
|
allocationBasedOnActualHours_costCenter_key |
int32 |
|
☐ |
|
allocationBasedOnActualHours_costUnit_code |
string |
|
☐ |
|
allocationBasedOnActualHours_costUnit_description |
string |
|
☐ |
|
allocationBasedOnActualHours_costUnit_key |
int32 |
|
☐ |
|
costCenter_code |
string |
|
☐ |
|
costCenter_description |
string |
|
☐ |
|
costCenter_key |
int32 |
|
☐ |
|
costUnit_code |
string |
|
☐ |
|
costUnit_description |
string |
|
☐ |
|
costUnit_key |
int32 |
|
☐ |
|
endPeriod_periodEndDate |
datetime |
|
☐ |
The last day of the payroll period. |
endPeriod_periodNumber |
int32 |
|
☐ |
The period (month [1 to 12] , 4 weeks [1 to 13] or week [1 to 53]) of the last payroll period for which the journal allocation is applicable. |
endPeriod_periodStartDate |
datetime |
|
☐ |
The first day of the payroll period. |
endPeriod_year |
int32 |
|
☐ |
The year of the last payroll period for which the journal allocation is applicable. |
id |
guid |
|
☐ |
The unique identifier of an object (GUID/UUID) |
journalProfileConfiguration_endPeriod_periodEndDate |
datetime |
|
☐ |
The last day of the payroll period. |
journalProfileConfiguration_endPeriod_periodNumber |
int32 |
|
☐ |
The period (month [1 to 12] , 4 weeks [1 to 13] or week [1 to 53]) of the last payroll period for which the journal allocation is applicable. |
journalProfileConfiguration_endPeriod_periodStartDate |
datetime |
|
☐ |
The first day of the payroll period. |
journalProfileConfiguration_endPeriod_year |
int32 |
|
☐ |
The year of the first payroll period for which the journal allocation is applicable. |
journalProfileConfiguration_id |
guid |
|
☐ |
The unique identifier of an object (GUID/UUID) |
journalProfileConfiguration_journalProfile_key |
int32 |
|
☐ |
|
journalProfileConfiguration_journalProfile_value |
string |
|
☐ |
|
journalProfileConfiguration_startPeriod_periodEndDate |
datetime |
|
☐ |
The last day of the payroll period. |
journalProfileConfiguration_startPeriod_periodNumber |
int32 |
|
☐ |
The period (month [1 to 12] , 4 weeks [1 to 13] or week [1 to 53]) of the last payroll period for which the journal allocation is applicable. |
journalProfileConfiguration_startPeriod_periodStartDate |
datetime |
|
☐ |
The first day of the payroll period. |
journalProfileConfiguration_startPeriod_year |
int32 |
|
☐ |
The year of the first payroll period for which the journal allocation is applicable. |
startPeriod_periodEndDate |
datetime |
|
☐ |
The last day of the payroll period. |
startPeriod_periodNumber |
int32 |
|
☐ |
The period (month [1 to 12] , 4 weeks [1 to 13] or week [1 to 53]) of the last payroll period for which the journal allocation is applicable. |
startPeriod_periodStartDate |
datetime |
|
☐ |
The first day of the payroll period. |
startPeriod_year |
int32 |
|
☐ |
The year of the first payroll period for which the journal allocation is applicable. |
weight |
int32 |
|
☐ |
The weight (factor) determines the relative weight when allocating the costs for this specific combination of costCenter and costUnit. |
13-05-2022 15:37 Version 22.1.40-BETA+3374
