Hierarchy
SAP_HRRXX (Software Component) Sub component SAP_HRRXX of SAP_HR⤷
PA-PA (Application Component) Personnel Administration⤷
PBAC (Package) Customizing HR Master Data
IMG Activity
| ID | OHIX0640 | BAdI: Set Up Check for Fast Entry of Actions |
| Transaction Code | S_PH0_48000470 | (empty) |
| Created on | 20000202 | |
| Customizing Attributes | OHIX0640 | BAdI: Set Up Check for Fast Entry of Actions |
| Customizing Activity | OHIX0640 | BAdI: Set Up Check for Fast Entry of Actions |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | HR_FAST_ACTION_CHECK |
Business Add-In (BAdI) Check fields on the fast entry screen (HR_FAST_ACTION_CHECK) allows you to set default values and checks for generated fast entry screens from the Fast Entry of Actions transaction (PA42).
The BAdI contains the method Verification of Fields (CHECK_FIELDS), which can be used to set default values and to execute checks.
The program name of the generated fast entry screen (parameter FLT_VAL) is used as a filter value to differentiate between the various implementations of the BAdI.
Example
You can use the existing implementations Check Fast Entry Screen Germany (HR_FEFA_CHECK_01) and Check Fast Entry Screen USA (HR_FEFA_CHECK_10) as a basis for your own implementations.
Requirements
Standard settings
Recommendation
SAP recommends that you use the following naming convention for your implementations of this BAdI: HR_FEFA_CHECK_XX, where 'XX' indicates the relevant fast entry action. In this way, the personnel action and the MOLGA can be coded in 'XX' for example.
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:
- 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.
- Enter a short text for the implementation in the Short text for implementation field.
- 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.
- Save your entries, and assign the implementation to a development class.
- Place the cursor on the method, and double-click to enter method processing.
- Enter the code for the implementation between the statements
method <Interface name> ~ <Name of method>andendmethod. - Save and implement your code. Return to the Edit Implementation screen.
- 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.
- Choose Activate
The code you stored in the method will be run when the application program is executed.
Further notes
If no BAdI implementation exists for a fast entry screen, no checks are performed when the action is processed, and only the default values that are transferred from the initial screen are set.
For more information, refer to the BAdI interface and method documentation:
Method: Verification of Fields
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 | 2 | Optional 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 | 20000202 |
| SAP Release Created in | 46C |
