Hierarchy
EA-HRGXX (Software Component) Sub component EA-HRGXX of EA-HR⤷
PA-EC-LT (Application Component) Long-Term Incentives⤷
PAOC_ECM_LTI_BL (Package) Long Term Incentive Plans - Business Logic
IMG Activity
| ID | HR_ECM_00_LT_E02 | Business Add-In: Extract LTI Grant Information for Outbound IDOC |
| Transaction Code | S_PLN_06000119 | (empty) |
| Created on | 20030514 | |
| Customizing Attributes | HR_ECM_00_LT_3_2_E | LTI - Not required - Not critical - User Exits |
| Customizing Activity | HR_ECM_00_LT_E02 | BAdI HRECM00_GRANT_INFO |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | HRECM00_GRANT_INFO |
Use this Business Add-In to extract the grant data of an employee using a method other than the standard one.
The Business Add-In contains the method described below.
GET_LTI_GRANT_INFO
This method replaces the complete data extraction routine related to the employee's grant data.
The following import parameters are provided:
- PERNR
Personnel number. - BEGDA
Begin date of the data extraction. - ENDDA
End date of the data extraction. - CPLAN
LTI plan (optional). - MESSAGE_HANDLER
Reference to interface IF_HRPA_MESSAGE_HANDLER. If any messages 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:
- IS_OK
Indicator to be set to SPACE if errors have prevented your routine from retrieving the data successfully.
The following change parameters must be provided by your coding:
- IDOC_TAB
This table contains all relevant information about the LTI grant of an individual employee such as the grant date, expiry date, number of shares of the grant, vesting information, blackout period and life event.
Example
The customer has special requirements concerning the data extraction of a blackout period.
Example
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.
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 |
