Ansicht
Dokumentation
OHARUBP_PY_FSSAPP_08 - Define Absences Suggestions based on Data from Sickness Certificate
BAL_S_LOG - Application Log: Log header data Addresses (Business Address Services)This documentation is copyright by SAP AG.
In this Customizing activity, you define the absence types which are suggested when certain data in the Sickness Certificate (3330) infotype is filled.
You use this activity to customize the absences that are created when a user performs personnel action FSS Application for SI Payment if the personnel action includes infotypes Sickness Certificate (3330) and Absences (2001). Depending on the data entered in the sickness certificate, the system can automatically suggest absences.
In standard delivery, four types of events corresponding to the data of the Sickness Certificate (3330) infotype are available:
- Regime breach – Field Regime Breach Date (HSBRD) is filled.
- Stationary treatment – Fields From (HSDT1) and To (HSDT2) in section Stay in the Hospital are filled.
- Spa treatment – Fields Date1 (DATE1), Date2 (DATE2) and Ref.Doc.No. (VONUM) are filled.
- Ambulatory treatment – Covers the whole period of the sickness certificate. Intended to have lower priority than the types above to cover the part not filled by those types.
These events correspond to Operation IDs in this Customizing activity. Operation IDs are defined in Customizing activity Define Special Operation ID for Mapping Subtypes.
If you need to use different absence types for the same sickness certificate events based on additional information, use field Mod ID (Modifier ID for Subtype Mapping). These modifiers are activated using BAdI HRPADRU_B_FSS_ABSENCE_MODIFIER. SAP recommends to use this BAdI in a way that ensures that for each sickness certificate only one modifier is active. If several modifiers are active, the system shows a search help for subtypes of the infotype Absences (2001), with the list of subtypes derived from this Customizing activity. In ambiguous cases, when events customized with different modifiers have different time periods but the same absence type, and the user selects this absence type from the value help, the system will propose the creation of an entry for infotype Absences (2001) that corresponds to the event that has been customized with the modifier with the lowest number (empty modifier is the first priority, then 00, 01, and so on.)
The priority field is used to prioritize the time period of events inside one modifier ID value.
To provide different types of absences for children of different ages, you create three implementations of BAdI HRPADRU_B_FSS_ABSENCE_MODIFIER to determine the correct age of children. You use this activity to customize the Child Care subtype of the Sickness Certificate (3330) infotype as follows:
| Mod ID | Oper | Name of Operation | A/AType | Start Date | End Date | Prio |
|---|---|---|---|---|---|---|
| 01 | 1 | Regime breach | MROT absence type | 01.01.1800 | 31.12.9999 | 1 |
| 01 | 2 | Stationary treatment | Stationary child <3 years old | 01.01.1800 | 31.12.9999 | 10 |
| 01 | 3 | Spa treatment | Spa absence type | 01.01.1800 | 31.12.9999 | 20 |
| 01 | 4 | Ambulatory treatment | Ambulatory child <3 years old | 01.01.1800 | 31.12.9999 | 50 |
| 02 | 1 | Regime breach | MROT absence type | 01.01.1800 | 31.12.9999 | 1 |
| 02 | 2 | Stationary treatment | Stationary child 3 to 7 years old | 01.01.1800 | 31.12.9999 | 10 |
| 02 | 3 | Spa treatment | Spa absence type | 01.01.1800 | 31.12.9999 | 20 |
| 02 | 4 | Ambulatory treatment | Ambulatory child 3 to 7 years old | 01.01.1800 | 31.12.9999 | 50 |
| 03 | 1 | Regime breach | MROT absence type | 01.01.1800 | 31.12.9999 | 1 |
| 03 | 2 | Stationary treatment | Stationary child 7 to 14 years old | 01.01.1800 | 31.12.9999 | 10 |
| 03 | 3 | Spa treatment | Spa absence type | 01.01.1800 | 31.12.9999 | 20 |
| 03 | 4 | Ambulatory treatment | Ambulatory child 7 to 14 years old | 01.01.1800 | 31.12.9999 | 50 |
The user entered data in the Sickness Certificate (3330) infotype for a child care sickness certificate with dates of the stay in hospital and the regime breach filled. For example, the dates of the sickness certificate are 01.01.2018 to 31.01.2018, the dates of the stay in hospital are 01.01.2018 to 10.01.2018, the dates of spa treatment are 21.01.2018 to 31.01.2018, and the regime breach date is 25.01.2018.
After the user saves the Sickness Certificate (3330) infotype record, the system checks the modifiers with the BAdI and selects the correct modifier ID for this specific case. If the BAdI implementations return more than one positive answer, the system prompts the user to choose one of three stationary child absence types. In both cases, the correct absence type for this case is proposed for an entry of the Absences (2001) infotype with period 01.01.2018 to 10.01.2018. After that, the system proposes an entry of the Absences (2001) infotype with period 11.01.2018 to 20.01.2018 with the absence type with the same modifier ID. The next proposed entry of Absences (2001) infotype will have period 21.01.2018 to 24.01.2018 and will have subtype Spa absence type. After that, the system will provide the last entry of Absences (2001) infotype with period 25.01.2018 to 31.01.2018 and with subtype MROT absence type.
ABAP Short Reference ABAP Short Reference
This documentation is copyright by SAP AG.
Length: 9034 Date: 20240523 Time: 191058 sap01-206 ( 124 ms )
