Hierarchy
⤷ PY-GB (Application Component) United Kingdom
⤷ PC08 (Package) HR accounting: GB
Basic Data
Data Element | P08_MSAX_SSPP |
Short Description | SSP payment mandatory |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFELD | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 4 | SSPP |
Medium | 4 | SSPP |
Long | 4 | SSPP |
Heading | 4 | SSPP |
Documentation
Definition
This field contains Statutory Sick Pay (SSP) payments brought forward across a tax year that were paid to comply with legislative rules governing statutory minimum payments. It does not contain any payments made as part of an employer's Occupational Sick Pay (OSP) scheme.
Use
Set this field to 'X' to create the wage type SSPP.
Set this field to ' ' (space) to create the wage type SSPO.
Dependencies
Example
- An employee is on Full Pay OSP and has an additional day of absence entered belonging to the previous tax year.
The additional SSP due for that day is treated notionally because the employer's OSP scheme more than covers the legislative minimum payable to the employee. This means the wage type SSPO will be created in the current payroll period.
- An employee is on Nil Pay OSP and has an additional day of absence entered belonging to the previous tax year.
The additional SSP due for that day is treated as an actual payment because the employer's OSP scheme does not cover the legislative minimum payable to the employee. This means the wage type SSPP is created in the current payroll period.
History
Last changed by/on | SAP | 20050705 |
SAP Release Created in |