Hierarchy

⤷

⤷

IMG Activity
ID | HRWPC_RQ_APPR_FORM | BAdI: Modification of Rule Resolution for Approver Form |
Transaction Code | S_AXA_22000111 | (empty) |
Created on | 20040224 | |
Customizing Attributes | HRWPC_RQ_APPR_FORM | BAdI: Modification of Rule Resolution for Approver Form |
Customizing Activity | HRWPC_RQ_APPR_FORM | BAdI: Modification of Rule Resolution for Approver Form |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | HRWPC_RQ_APPR_FORM |
This Business Add-In (BAdI) enables you to tailor the rule resolution logic of role ApproverForm (50000145) to suit customer requirements. The entire role container is available for this purpose.
Example
The role ApproverForm is used within the approval workflow of ProcessRQ (50000050) for requisition requests to determine the second approver.
If this role resolution fails, the entire workflow is terminated. You can use this Business Add-In to implement customer-specific error handling in the event of the standard role resolution failure.
Workflow ProcessRQ (50000050) is used in Requisition Request - Long Form, for example, and is triggered after the first approval request form has been submitted.
Requirements
Standard settings
This BAdI is not implemented in the standard SAP System. If you do not create an implementation, the system runs through the standard coding.
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:
- 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
Interface
Method
MANIPULATE_ACTOR_TAB (Change the Actor Table for Role Resolution)
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_RQ_APPR_FORM | 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 | 20040224 |
SAP Release Created in | 2004_1_470 |