Hierarchy

⤷

⤷

IMG Activity
ID | HRWPC_EREC_ADD_VALS | BAdI: Define List Field Values |
Transaction Code | S_PLN_62000411 | (empty) |
Created on | 20040311 | |
Customizing Attributes | HRWPC_EREC_ADD_VALS | BAdI: Define List Field Values |
Customizing Activity | HRWPC_EREC_ADD_VALS | BAdI: Define List Field Values |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | HRWPC_EREC_ADD_VALS |
Use
This Business Add-In (BAdI) is available if you want to adjust the entries in the dropdown lists for Requisition request forms yourself.
The input help field comprises a name (description) and a technical name. In the standard delivery, the technical names are displayed in parentheses.
Requirements
Standard settings
The BAdI is not implemented in the standard delivery. If you do not create an implementation, the system uses the standard code.
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.
Example
For specific fields (such as Recruitment Officer (EREQ_RECRUITER)), you can specify that the system should use the description instead of the technical name.
Result: The description Personnel Number is displayed as opposed to the technical name (PERNR).
If this role resolution fails, the entire workflow is terminated. If this is the case, use this Business Add-In to implement customer-specific error handling.
Workflow ProcessRQ (50000050) is used for the Requisition Request - Long Form, for example, and is sent after the first approval request has been triggered.
See also:
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 |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | HRWPC_EREC_ADD_VALS | 0 | AXA0000002 | Business Package for Manager Self-Service (HR) |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20050216 |
SAP Release Created in | 500 |