SAP ABAP Data Element P05_ZKMKT (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
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 |
| 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. The field status from infotype Absences (2001) determines which forms are printed by the Notifications of Sickness and Recovery report (RPTZKMN1). The following statuses are possible:
- 1 Notification of Sickness Created
- 2 Notification of Sickness Sent
- 3 13th Week or 8th Month Notification 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/ y13th Week or 8th Month Sent
Procedure
When creating a case, the status is automatically set to 1 - Notification of Sickness Created.
In normal cases, the status of a sickness record is maintained by the Notifications of Sickness and Recovery report (RPTZKMN0) by means of a batch input session. The report enters the new status of the processed records in infotype Absences (2001) by means of a batch input session automatically created by the report.
Examples:
- 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 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 by the Notifications of Sickness and Recovery report (RPTZKMN0).
- 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 fit for work percentage (Fit for Work field in the above-mentioned 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 applicable to notifications with status '6'. For futher information, please refer to the examples below.
Sometimes, the user has to maintain the status of a case himself:
Examples
- An employee has gone home sick during the course of a workday and does not return to work the following day. The status of the first case must be set to 5 - Case Will Be Followed Up by the user. 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. Example: the employee goes home sick on Friday and stays home on Monday: the first date of the second sickness record should start on Saturday.
- If, after studying the forms, you draw the conclusion that some information has been incorrectly recorded in the system or is incomplete after the batch input session has been run and you would like to print a number of forms again, this can be done by resetting the status to the corresponding value of the form you wish to print.
- If the Fit for Work Percentage changes, a new sickness record is created. The status of the old sickness record should be set 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 13th week or 8th month notification has been sent and the work incapacity percentage changes, the status of the first sickness record of 3 - 13th Week or 8th Month/Preliminary Reintegration Plan Sent must be changed to 7 - Case Will Be Followed Up/WI Percentage Will Change/13th Week or 8th Month Sent. The status of the second record must be set to 1 - Notification of Sickness Created. In this case, a new sickness notification with the different work incapacity percentage must be sent.
History
| Last changed by/on | SAP | 20040819 |
| SAP Release Created in |
