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_E01 | Business Add-In: Determine Compensation Area |
| Transaction Code | S_ALN_01002084 | (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_E01 | BAdI HRECM00_CARGP |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | HRECM00_CARGP |
Implement this Business Add-In to define a customer-specific algorithm that determines the default compensation area on creation of infotype Compensation Program (0758). By doing so, you no longer need to evaluate feature Compensation Area (CARGP).
The Business Add-In consists of the method READ_FEATURE_CARGP, in which you can implement the algorithm that determines the default compensation area (CAREA).
The following import parameters are provided:
- PERNR
Personnel number. - KEYDT
Key date that determines the compensation area. - MESSAGE_HANDLER
Reference to interface IF_HRPA_MESSAGE_HANDLER. If the evaluation of the default compensation area encounters 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:
- CAREA
Default compensation area. - IS_OK
Indicator to be set to SPACE if errors have prevented your routine from retrieving the default compensation area successfully. - 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 default compensation area should be provided by the standard feature CARGP. However, if infotype 0758 already contains a record, the compensation area of the additional record should be 'Worldwide'.
Requirements
Standard settings
Recommendation
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.
Example
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 |
