SAP ABAP IMG Activity PAY_AT_GERF_01 (BAdI: Define Exceptions for Minimum Income Workers)
Hierarchy
☛ SAP_HRCAT (Software Component) Sub component SAP_HRCAT of SAP_HR
   ⤷ PY-AT (Application Component) Austria
     ⤷ P03C (Package) HR Customizing: Austria
IMG Activity
ID PAY_AT_GERF_01 BAdI: Define Exceptions for Minimum Income Workers  
Transaction Code S_L7D_24000736   (empty) 
Created on 20070511    
Customizing Attributes PAY_AT_GERF_01   Edit Warning Messages for Minimum Income Workers 
Customizing Activity PAY_AT_GERF_01   Edit Warning Messages for Minimum Income Workers 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name HRAT_PAY_EXITS_RA    

Use

This Business Add-In (BAdI) enables you to define additional exceptions when checking payroll data to determine whether the income of marginally employed workers is above or below the minimum income threshold. The customer exit enables the warnings to be activated or deactivated accordingly.

In the master data, the monthly salary specified and the assignment between personnel number and technical contribution group determine which employees are to be considered as minimum income workers in the payroll run. For the public sector, the system also evaluates the data entered in the AVKAT feature (HR-PS AT: Feature for Insurance Category).

If an employee is identified as marginally employed and receives, in a period, an income that is above the minimum income threshold, a warning is output in the payroll run to indicate that the master data has to be checked for the payroll period.

The reverse case also applies: If an employee receives, in a payroll period, an income that is below the minimum income threshold, but this employee is not identified as marginally employed, a warning is to be displayed. This warning is not implemented with the existing customer exit since the warning is useful only in combination with the definition of exceptions.

The warning is not displayed in the following exceptions:

  • If the employee is ill and a related reduction in salary has resulted in the income falling below the minimum income threshold.
  • For apprentices
  • For company pensioners

Even though these employees have a low salary, they are not considered as marginally employed.

Standard settings

Interface IF_EX_HRAT_PAY_EXISTS_RA contains an active default implementation that issues a warning if the salary for an employee identified as marginally employed exceeds the minimum income threshold. If you want to make customer-specific adjustments, you can use the implementation as a template for a custom implementation.

If the default implementation meets your requirements, no further settings need to be made.

To define additional exceptions for minimum income workers for whom no warnings are to be output, you can use the sample implementation CL_EXM_IM_HRAT_PAY_EXITS_RA. This shows you how to activate warnings when the minimum income threshold is not reached and how to model exception rules, including those described above.

Activities

After calling up the IMG activity, a dialog box appears, in which you can enter a name for the implementation.

If you have already made other implementations for this BAdI, another dialog box appears, in which the existing implementations are displayed. In this case, choose Create, and proceed 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 <Interface name> ~ <Name of 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.

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency I   Valid for countries specified 
Customizing Attributes Country Key Country Name
PAY_AT_GERF_01 AT Austria
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20070511 
SAP Release Created in