# PutPayrollPeriodDataByPayrollPeriodDataId Edit the details of an payroll period data __Activity name :__ PutPayrollPeriodDataByPayrollPeriodDataId Edit the details for payroll period data __Metadata :__ Possible values for fields of the type 'metadata' can be acquired (GET) by adding `/metadata` to the PUT URL Possible values for fields of the type 'metadata' that are PERIOD-specific can be acquired (GET) by adding `/metadata/year/{year}/period/{periodNumber}` to the PUT URL Select loket.nl (REST) API URL: /providers/employers/employees/employments/payrollperioddata/{payrollperioddataId} Insert loket.nl (REST) API URL: /providers/employers/employees/employments/payrollperioddata/{payrollperioddataId} Update loket.nl (REST) API URL: /providers/employers/employees/employments/payrollperioddata/{payrollperioddataId} Delete loket.nl (REST) API URL: /providers/employers/employees/employments/payrollperioddata/{payrollperioddataId} Select loket.nl (REST) API Operation: put /providers/employers/employees/employments/payrollperioddata/{payrollperioddataId} - Catalog: `LoketNlRest` - Schema: `PayrollPeriodData` - Field Selection Method: NotRequired - Base Path: `content` 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. ## Parameters of Table Function | Name | Data Type | Required | Default Value | Documentation | |---|:---:|:---:|:---:|---| | `body` | `string` | ☑ | | Payroll period data to edit. | | `If-Match` | `string` | ☐ | | Input the value acquired in the ETag header for concurrency control. Please note this is optional (and not recommended for most types of integrations). | | `payrollperioddataId` | `guid` | ☑ | | The unique identifier of the payroll period data | ## Columns of Table Function The columns of the table function `PutPayrollPeriodDataByPayrollPeriodDataId` are shown below. Each column has an SQL data type. | Name | Data Type | Label | Required | Documentation | |---|:---:|---|:---:|---| | `costCenter_code` | `string` | | ☐ | | | `costCenter_description` | `string` | | ☐ | | | `costCenter_key` | `int32` | | ☐ | | | `costUnit_code` | `string` | | ☐ | | | `costUnit_description` | `string` | | ☐ | | | `costUnit_key` | `int32` | | ☐ | | | `distributionUnit_code` | `int32` | | ☐ | | | `distributionUnit_description` | `string` | | ☐ | | | `distributionUnit_key` | `guid` | | ☐ | The unique identifier of an object (GUID/UUID) | | `id` | `guid` | | ☐ | The unique identifier of an object (GUID/UUID) | | `payrollPeriod_periodEndDate` | `datetime` | | ☐ | The last day of the period to which the payroll period data applies | | `payrollPeriod_periodNumber` | `int32` | | ☐ | The period (month [1 to 12] , 4 weeks [1 to 13] or week [1 to 53]) of the payroll period in which the payroll data is to be processed. | | `payrollPeriod_periodStartDate` | `datetime` | | ☐ | The first day of the period to which the payroll period data applies | | `payrollPeriod_year` | `int32` | | ☐ | The year of the payroll period in which the payroll data is to be processed | | `payslipText` | `string(25)` | | ☐ | A custom text to be displayed on the payslip. | | `payslipType_key` | `int32` | | ☐ | | | `payslipType_value` | `string` | | ☐ | | | `shift_bonusPercentage` | `decimal` | | ☐ | The bonus percentage used in wage calculations for the hours made in this shift. | | `shift_fullTimeHoursPerWeek` | `decimal` | | ☐ | The full time hours for an employment that is linked to this shift. | | `shift_shiftNumber` | `int32` | | ☐ | The number for the shift. Loket.nl supports a maximum of 5 shifts per payroll administration. |