SAP ABAP Data Element P05_ZKMKT_EN (Status of Sickness Notification)
Hierarchy
☛ SAP_HRCNL (Software Component) Sub component SAP_HRCNL of SAP_HR
   ⤷ PA-PA-NL (Application Component) Netherlands
     ⤷ PB05 (Package) HR Master Data: Netherlands
Basic Data
Data Element P05_ZKMKT_EN
Short Description Status of Sickness Notification  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type P05_ZKMKT    
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 StsSickNtf 
Medium 15 Sts SicknNofif. 
Long 24 Status of Sickn. Notif. 
Heading 7 StsSckN 
Documentation

Definition

Status of the sickness record for the notifications of sickness and recovery.

This field determines which forms are printed by the Notifications of Sickness and Recovery (RPTZKMN2) report. The following statuses are possible:

  • 1 - Notification of Sickness created
  • 2 - Notification of Sickness sent
  • 3 - Notification of Long Term Sickness in "Poortwachter" sent
  • 4 - Notification of Recovery sent
  • 5 - Case Will Be Followed Up
  • 6 - Case Will Be Followed Up, Work Incap. Pct Will Change
  • 7 - Case Will Be Followed Up, Work Incap. Pct Will Change/ LngTrm Sickness Notif. sent
  • A - Arbodienst Notification of Sickness sent
  • B - Arbodienst Notification Full Recovery sent
  • C - UWV Notification of Sickness sent
  • D - UWV Full Recovery sent
  • E - UWV Long Term Sickness Notification sent
  • F - UWV Long Term Full Recovery sent
  • G - Arbodienst Notification of Sickness & UWV Notification of Sickness sent
  • H - Arbodienst Notification of Sickness & UWV Full Recovery sent
  • I - Arbodienst Notification Sickn. & UWV Long Term Sickness Notification sent
  • J - Arbodienst Notification Sickn. & UWV Long Term Full Recovery sent
  • K - Arbodienst Full Recovery & UWV Notification of Sickness sent
  • L - Arbodienst Full Recovery & UWV Full Recovery sent
  • M - Arbodienst Full Recovery & UWV Long Term Sickness Notification sent
  • N - Arbodienst Full Recovery & UWV Long Term Full Recovery sent
  • O - Continuation Sickness Record present
  • P - Continuation Sickness Record present & Arbodienst Modif. WI% sent
  • Q - Continuation Sickness Record present & UWV Modif. WI% sent
  • R - Continuation Sickn. Rec. present & Arbodienst & UWV Modif. WI% sent

Use

When creating a record, the status is automatically set to 1 - Notification of Sickness created.

In most cases, the status of a sickness record is maintained by a batch input session, which is created by the Notifications of Sickness and Recovery (RPTZKMN2) report. The batch input session automatically enters the new status of the processed records in the Absences (2001) infotype.

The following examples describe record maintenance using a batch input session.

  • Status 1 - Notification of Sickness created has been assigned to a record. When a sickness notification is sent to the Labor Conditions and Absenteeism Monitoring Board (Arbodienst) for approval, the status of the record must then be changed to 2 - Sickness Notification sent. The batch input session is used to maintain the new status of the record. If you do not use the batch input session, the status remains unchanged and the sickness notification has to be reprocessed using the Notifications of Sickness and Recovery (RPTZKMN2) report.
  • Status 6 - Case Will Be Followed Up, Work Incapacity Percentage Will Change has been assigned to a record. This special status is applicable to records relating to a current sickness period. For example, the employee goes home sick and does not return to work the next day. A percentage is assigned to the first day that does not correspond to the work capacity percentage (Fit for Work field in the Absences (2001) infotype) of the next day. The first percentage is used to create two records, the first with status 6 for the first day, the second with status 1 for the current sickness period and a different percentage. Subsequently, two separate sickness notifications are created (one for each record), as well as at least one notification of recovery for the first day of sickness. This is only applicable to records with a status of 6.

In some cases, you will need to change the status manually. The following examples describe record maintenance which must be conducted by the user.

  • An employee has gone home sick during the course of a workday and does not return to work the following day. The user must set the status of the record to 5 - Case Will Be Followed Up. The two sickness records created are looked upon as one, whereby the first day of sickness printed on the notification of sickness is derived from the first record. The user is requested to let the second sickness record follow on from the first one, even if the workdays do not follow on. For example, if the employee goes home sick on Friday and stays home on Monday then the first date of the second sickness record should start on Saturday.
  • If after reviewing the notifications, the user concludes that some information has been incorrectly recorded in the system or is incomplete after the report has been run, a selection of notifications can be reprinted. To reprint a notification, the user must reset the status of the record to the corresponding notification.
  • If the work capacity percentage changes, a new sickness record is created. The user must set the status of the old sickness record to 5 - Case Will Be Followed Up. In this case, the authorities do not receive a notification of recovery from the old record but a new notification of sickness with a different work incapacity percentage.
  • If a long term sickness notification has been sent and the work incapacity percentage changes, the user must change the status of the first long term sickness record to 7 - Case Will Be Followed Up/ WI Percentage Will Change/LngTrm Sickness Notif. Sent. The user must also change the status of the second record to 1 - Notification of Sickness Created. In this case, a new sickness notification with the different work incapacity percentage must be sent.

Dependencies

Example

History
Last changed by/on SAP  20091125 
SAP Release Created in