Hierarchy
SAP_HRCGB (Software Component) Sub component SAP_HRCGB of SAP_HR⤷
PY-GB-PS (Application Component) Öffentlicher Dienst⤷
P08P_HER (Package) HR Public Sector Great Britain (Higher Education)
Basic Data
| Data Element | P08P_HESA_STAFF_CATEGORY |
| Short Description | HESA Staff return category for NISR |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | P08P_HESA_STAFF_CATEGORY | |
| 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 | 10 | Category |
| Medium | 20 | NISR Category |
| Long | 30 | NISR Staff category |
| Heading | 5 | Cat. |
Documentation
Definition
Five categories of staff are defined by HESA for NISR:
- Clinical (C)
- Academic (A)
- Professional (P)
- Non-academic (N)
- Atypical (A)
The range of data required for HESA NISR about an individual and the contract(s) that they hold depends on the nature of those contracts and also the classification of the activity for which the contract exists.
For those individuals with contracts of employment and/or for whom the institution is liable to pay Class 1 National Insurance contributions but whose relationship for all contracts held with the institution during the reporting period would be defined as 'atypical' there is a requirement to return only a minimum data set. The definition of 'atypical' is set out by the DTI:
The term 'atypical' is used to describe working arrangements that are not permanent, involve complex employment relationships and/or involve work away from the supervision of the normal work provider. These may be characterised by a high degree of flexibility for both the work provider and the working person, and may involve a triangular relationship that includes an agent. They can be contrasted with the model of a permanent, full-time employment contract between two parties, where one works standard hours under the control of the other and termination can only take place if there is grave fault or by giving notice. Atypical arrangements may involve an absence of mutual obligation between the work provider and working person beyond or within a given period of work or assignment and may also involve complex relationships between the working person, an agent paying and/or supplying the working person and the principal, under whose supervision the working person may work. It is important to recognise, however, that atypical workers may often be employees.
For those individuals whose relationship with the institution, for one or more of the contracts held during the reporting period, cannot be defined as 'atypical' there is a requirement to return a wider range of data. For many staff, those who have contracts to undertake activities classified in SOC groups 4-9, this additional requirement relates mainly to grade and salary information and start and end dates of employment and contracts (all staff except atypical).
Where individuals have contracts to undertake activities classified in SOC groups 1- 3 there is a requirement for an additional range of data for example about qualifications and previous employment/destination on leaving information. This information is required for those who have contracts in administrative and professional posts, for example in planning, libraries and registraries, whose activities are likely to be coded in SOC groups 1, 2B and 3 - areas that mean that they are likely to have careers within the HE sector that involve them moving between institutions. There is also a requirement for institutions to track the use of staff identifiers when SOC 1, 2B and 3 staff move between institutions.
For all other staff with contracts where any of the activity code fields (24, 27, 30) are coded 2A, there is a requirement for a further additional range of data. There is also a requirement for institutions to track the use of staff identifiers when SOC 2A staff move between institutions.
Amongst the SOC 2A group of staff some information is only needed for Health and Social Care professions, i.e. where any of the cost centres fields (25, 28, 31) are coded 1 to 9 or 29.
Finally, only in the case of those staff who hold NHS contracts are field 19, NHS contract grade and field, 20 Healthcare professional specialty in the Contract Table additionally required.
History
| Last changed by/on | SAP | 20040114 |
| SAP Release Created in | 470 |
