Hierarchy
EA-HRRXX (Software Component) Sub component EA-HRRXX of EA-HR⤷
PA-GE (Application Component) Management of Global Employees⤷
PAOC_PAD_MGE (Package) Management Of Global Employees
IMG Activity
| ID | MGE_00_PO_BADI_GEOG | Business Add-In for Geographical Areas |
| Transaction Code | S_ALN_01001393 | (empty) |
| Created on | 20030108 | |
| Customizing Attributes | MGE_00_PO_BADI_GEOG | Business Add-In for Geographical Areas |
| Customizing Activity | MGE_00_PO_BADI_GEOG | Business Add-In for Geographical Areas |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | HRMGE00REGION |
Use
This Business Add-In enables you to determine the geographical area for a specific personnel assignment.
The implementation of the Business Add-In method DETERMINE_REGION is required if you have opted for a more specific approach to determine the cost-of-living index in the activity Define Cost of Living Providers, since a COLI index on a country-to-country basis does not necessarily reflect the cost of living in a specific area. For example, the Bay Area in the US and Munich in Germany are far more expensive than North Dakota and Hannover, respectively.
Requirements
No preliminary steps required.
Standard settings
SAP delivers the implementation DETERMINE_REGION, which contains the following input and output parameters:
- Import parameters
- PERNR
Number of the employee's assignment - WERKS
Personnel area - BTRTL
Personnel subarea - PLANS
Position - Export parameters
- IS_OK
Indicates whether the region was found. - REGION
Region
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 | 20030108 |
| SAP Release Created in | 200 |
