SAP ABAP IMG Activity HRPAYAT_RPCEKSA0_01 (BAdI: Calculate Statistical Monthly Values per Remuneration Type)
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 HRPAYAT_RPCEKSA0_01 BAdI: Calculate Statistical Monthly Values per Remuneration Type  
Transaction Code S_L4H_49002276   (empty) 
Created on 20110616    
Customizing Attributes HRPAYAT_RPCEKSA0_01   BAdI: Calculate Statistical Monthly Values per Remuneration Type 
Customizing Activity HRPAYAT_RPCEKSA0_01   BAdI: Calculate Statistical Monthly Values per Remuneration Type 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name HRPAYAT_RPCEKSA0_01    

Use

This Business Add-In (BAdI) is used in the Payroll Austria (PY-AT) component. You can use this BAdI to override the calculation of the amounts shown in the income report in accordance with the Equal treatment Act (report RPCEKSA0). For each

remuneration element and usage group, you can calculate the statistic monthly amounts (#pools#) and the annual amount. The total of the annual amounts of all remuneration elements is then used in the statistics for the income report. For monitoring purposes, you can also display the individual pool amounts in this report.

The implementation of this BAdI is filter dependent, that is, you need to specify at least one specific filter type for each implementation. The filter type corresponds to the type of remuneration, for example: SAPM (monthly salary) or SAPS (special payment).

Remuneration types for which implementations already exist are stored in entity table T5AS2. When you create an implementation for a new remuneration type, the system automatically adds this new remuneration type to the table. The values in this table are used as domains for data element PC03_ENTG_TYP. The filter value is always specified as an import parameter when methods are called.

Standard settings

The default implementation supports the following remuneration types:

  • SAPL: Regular salary (from payroll or simulation result, projection for 12 months in the year)
  • SAPM: Monthly salary (from Basic Pay infotype (0008), projection for 12 months in the year)
  • SAPS: Special payment (projection for 2 payments in the year in specific months)
  • SAPZ: Non-recurring payment (no projection)

You can also use the default implementation as a template for your own implementations.

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.

Example

  • In your company, you have more than 2 special payments per year.

See also

BAdI method documentation:

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
HRPAYAT_RPCEKSA0_01 AT Austria
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG HRPAYAT_RPCEKSA0_01 0 HLA0003822 Further Reporting 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20110616 
SAP Release Created in