Ansicht
Dokumentation

OHARUBP_PY_FSSAPP_10 - BAdI: Processing of Absence Modifier

RFUMSV00 - Advance Return for Tax on Sales/Purchases   ABAP Short Reference  
This documentation is copyright by SAP AG.

The BAdI HRPADRU_B_FSS_ABSENCE_MODIFIER can be used to define special processing for the field Modifier ID for Subtype Mapping, if required.

Modifier ID for Subtype Mapping is defined in Customizing activity Define Absences Suggestions based on Data from Sickness Certificate. The field can be used to combine proposals of subtypes related to different events that have similar meaning. For example, you can use one modifier ID for proposals related to events of a sick leave for caring for a child younger than 5 years, and another modifier ID for proposals related to events of a sick leave for an older child.

These modifiers are then activated and processed 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 Customizing activity Define Absences Suggestions based on Data from Sickness Certificate. In ambiguous cases, when different events with different time periods would produce the same absence type, the modifier with the lowest number will have the highest priority (empty modifier first, then 00, then 01, and so on.)

After you call the Customizing activity, the system displays a dialog box where you enter a name for the implementation.

If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:

1. In the dialog box, enter a name for the BAdI implementation in the Implementation field, and choose Create.
   
   The screen for creating BAdI implementations is now displayed.
2. Enter a short text for the implementation in the Short text for implementation field.
3. From the tab index, choose Interface.
   
   The Name of implemented class field is already filled on the tab page, as a class name was automatically assigned to the implementation when you named it.
4. Save your entries, and assign the implementation to a development class.
5. Place the cursor on the method, and double-click to enter method processing.
6. Enter the code for the implementation between the statements method ~ and endmethod.
7. Save and implement your code. Return to the Edit Implementation screen.
8. Save the entries on the Edit Implementation screen.
   
   Note: You can also create an implementation, and then activate it at a later time. In such a case, end the processing stage at this point.
9. Choose Activate.

The code you stored in the method will be run when the application program is executed.

BAL Application Log Documentation   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 3584 Date: 20240607 Time: 032309     sap01-206 ( 70 ms )