SAP ABAP IMG Activity HRWPC_RQ_APPR_NEXT (BAdI: Modification of Rule Resolution for Next Approver)
Hierarchy
☛ SAP_HRGXX (Software Component) Sub component SAP_HRGXX of SAP_HR
   ⤷ EP-PCT-MGR-HR (Application Component) Business Package for Manager Self-Service (HR)
     ⤷ PWPC_MAN_RECR_US_46CFF (Package) PWPC_MAN_RECR_US_46CFF
IMG Activity
ID HRWPC_RQ_APPR_NEXT BAdI: Modification of Rule Resolution for Next Approver  
Transaction Code S_AXA_22000110   (empty) 
Created on 20040224    
Customizing Attributes HRWPC_RQ_APPR_NEXT   BAdI: Modification of Rule Resolution for Next Approver 
Customizing Activity HRWPC_RQ_APPR_NEXT   BAdI: Modification of Rule Resolution for Next Approver 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name HRWPC_RQ_APPR_NEXT    

This Business Add-In (BAdI) enables you to tailor the rule resolution logic of role ApproverNext (50000144) to suit customer requirements. The entire role container is available for this purpose.

Example

The role ApproverNext is used within the approval workflow of ProcessRQ (50000050), ProcessRQ_1 (21300032) and ProcessRQ_3 (21300043) for requisition requests to determine the first approver. Additionally, this role is also used in the new E-Recruiting Requisition related workflows: ProcessEREC1 (12300159) and ProcessEREC2 (12300158).

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 for example in Requisition Request - Long Form and is triggered after the form has been submitted by the Manager. On the E-Recruiting side, this role is used in both Simple and Extended Requisition Requests in the same way.

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:

  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 code for the implementation between the statements method <Interface name> ~ <Name of method> and endmethod.
  7. Save and implement your code. 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 code you stored in the method will be run when the application program is executed.

Further notes

Interface

IF_EX_HRWPC_PCR_APPR_NEXT

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_NEXT 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