Hierarchy
EA-HRGXX (Software Component) Sub component EA-HRGXX of EA-HR⤷
PA-EC-AD (Application Component) Compensation Administration⤷
PAOC_ECM_ADM_BL (Package) Compensation Administration - Business Logic
IMG Activity
| ID | HR_ECM_00_AD_E08 | Business Add-In: Determine Calculation Base |
| Transaction Code | S_ALN_01002091 | (empty) |
| Created on | 20030331 | |
| Customizing Attributes | HR_ECM_00_AD_3_2_E | Compensation Administration - Not required - Not critical - User Exits |
| Customizing Activity | HR_ECM_00_AD_E08 | BAdI HRECM00_CALCBASE |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | HRECM00_CALCBASE |
Implement this Business Add-In HRECM00_CALCBASE to determine the calculation base salary used for calculating the compensation amount on the basis of a percentage and vice versa.
The Business Add-In consists of the method described below, which can be used instead of the standard algorithm.
GET_CALCULATION_BASE
The following import parameters are provided:
- PERNR
Personnel number. - CPLAN
Compensation plan for which you want to determine the calculation base salary. - CITEM
Compensation process item (enables you to retrieve the compensation review). - CAREA
Compensation area under which the plan is processed. - EFFDT
Current effective date. - DESIRED_CURRE
Currency used for the result of the calculation. - DESIRED_FREQU
Reference frequency used for the result. - MESSAGE_HANDLER
Reference to interface IF_HRPA_MESSAGE_HANDLER. If the evaluation of the calculation base triggers any messages that should be sent to the frontend, you can add them to the message list using method ADD_MESSAGE of this interface or function module HR_ECM_ADD_MESSAGE.
The following export parameters must be provided by your coding:
- BSEDT
Key date used for evaluating the calculation base salary. The date is stored in the work memory of the system in order to decide if in case of a manager's action the calculation base needs to be recalculated. For this purpose, the system calls routine HR_ECM_GET_CALC_BASE_KEYDATE and compares the result with the value stored in BSEDT from the last evaluation. Only if these dates differ, the calculation base salary module is called again (see the Recommendation section). - BSSAL
Calculation base salary used to convert the compensation amount to a percentage and vice versa. - IS_OK
Indicator set to SPACE if any error has prevented your routine from retrieving the calculation base salary. - PROCESS_STANDARD
Indicator to be set to 'X' if you want the system to ignore the result of your implementation and perform the standard routine.
Example
The calculation base salary is stored on a customer-specific infotype and has to be read from it.
Requirements
Standard settings
Recommendation
Since the result of parameter BSEDT is compared to the result of function module HR_ECM_GET_CALC_BASE_KEYDATE (see explanation for parameter BSEDT), which itself has no BAdI exit, it is recommended to fill parameter BSEDT only if also within your routing the key date is determined using HR_ECM_GET_CALC_BASE_KEYDATE. If you use a different method to determine the key date, it is recommended that you keep this date only internally in your module and that you do not to send it to the export parameter BSEDT, which should be left blank in this case.
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 coding for the implementation between the statements method <Interface name> ~ <Name of method> and endmethod.
7. Save and implement your coding. 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 coding you stored in the methods will be run when the application program is executed.
Further notes
For more information on using Business Add-Ins, refer to the SAP Library under Basis Components ->ABAP Workbench (BC-DWB) ->Changing the SAP Standard (BC)->Business Add-Ins.
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 3 | Nonrequired activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20031028 |
| SAP Release Created in | 200 |
