Ansicht
Dokumentation

OHAKREPEEABADI02 - Substitute standard calculation of number of weeks worked by temp.employees

rdisp/max_wprun_time - Maximum work process run time   CPI1466 during Backup  
This documentation is copyright by SAP AG.

This step describes how to set up customer-specific enhancements using the optional Business Add-In (BAdI) HRPADCA_RPLEEAK0_002, which can be used to substitute the calculation of the number of weeks worked by temporary employees that is delivered with the standard system with a calculation method of your own. The method GET_WEEKS_WORKED within this BAdI consists of the following parameters:

• PERNR

• BEGDA

• ENDDA

• EEA_BUFFER

• WEEK_COUNTER and

• CALC_WEEKS_BY_IT16

As currently delivered, Employment Equity Act (EEA) Reporting refers to the payroll information of contract employees to calculate the number of weeks they have worked. However, for contract employees, the number of weeks worked can also be derived through reference to the Contract Elements infotype (0016). Therefore, you are at liberty to instruct Employment Equity Act (EEA) Reporting (if desired) to refer to contract employees' Contract Elements infotype (0016) records, rather than payroll information, to determine the number of weeks they have worked. To do so, set the export parameter CALC_WEEKS_BY_IT16 within method GET_WEEKS_WORKED of the present Business Add-In.

You wish to substitute the calculation of the number of weeks worked that is delivered with the standard system with a calculation method of your own and understand that BAdI implementation HRPADCA_RPLEEAK0_002 is provided as an example to achieve this goal. This example is provided "as is" to illustrate how a BAdI implementation along these lines could be developed. You should not use this implementation yourself, but rather copy it to the customer name range and maintain it to meet your specific requirements.

The information explained below applies to all methods of BAdI HRPADCA_RPLEEAK0_002.

1. Execute this IMG step. On the subsequent screen, enter a name for the implementation you wish to create. (Alternatively, if you have already used this BAdI to create other implementations, a dialog box appears, displaying the implementations that have already been created.)
2. Choose Create. (Or, alternatively, Edit. The remainder of the documentation for this activity describes the steps to be performed when you create a new implementation.)
   
   Caution
   If you have already implemented this BAdI, then you must re-activate your current implementation. Otherwise, the report will issue error messages or short dumps as it processes employee data.
3. Enter a short text for the implementation in the Implementation name field, then choose Continue.
4. On the subsequent screen, specify an Implementation short text, then choose the Interface tabstrip. The name of the implemented class fields are already found in this tabstrip.
5. Save your entries and assign the implementation to a development class.
6. Place the cursor on the method, then double-click to initiate method processing.
7. Enter the code for the implementation between the statements method <Interface name> ~ and endmethod.
8. Save and implement your code.
9. Return to the Edit Implementation screen, then save your entries there.
10. If you wish to activate the implementation you have created at a later date, then exit the Edit Implementation screen without activating the implementation. Otherwise, choose Activate from this screen to activate the implementation for immediate use.

Once you have completed these activities, the source code that you stored in the method will be run when the associated application is executed.

BAL Application Log Documentation   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 4368 Date: 20240523 Time: 192535     sap01-206 ( 88 ms )