SAP ABAP IMG Activity PYIN_ESS_CLM_BADI_10 (BAdI: Determine Approver and Approver Group)
Hierarchy
☛ EA-HRCIN (Software Component) Sub component EA-HRCIN of EA-HR
   ⤷ PY-IN-PS (Application Component) INDIA PUBLIC SECTOR
     ⤷ PAOC_PAD_IN_PS (Package) HR IN: India Public Sector
IMG Activity
ID PYIN_ESS_CLM_BADI_10 BAdI: Determine Approver and Approver Group  
Transaction Code S_P7H_77000211   (empty) 
Created on 20081209    
Customizing Attributes PYIN_ESS_CLM_BADI_10   BAdI: Determine Approver and Approver Group 
Customizing Activity PYIN_ESS_CLM_BADI_10   BAdI: Determine Approver and Approver Group 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name HRPBSIN_NEXT_APPROVER    

Use

This Business Add-In (Add-In) is used in the Advanced Claims component.

This Add-In enables you to define customer specific logic to determine the approver of a request.

After the employee submits the request through Employee Self-Service (ESS), the request needs to be approved by the relevant approver(s). The system calls this BAdI to determine the approver. This BAdI returns the:

  • Approver's employee number to whom the system should send the request
  • Approver's group

Based on this data, system determines the privileges associated with the approver group.

The BAdI determines the approver based on the following cases:

  • Case 1- If you return the approver perner and the approver group

    BAdI send the request to the approver perner with the privilege associated with the approver group

  • Case 2 - If you return the approver perner and the approver group is initial

    BAdI displays an error

  • Case 3 - If the approver perner is initial and you return the approver group

    BAdI checks if you have set the Pick approvers from Approver Group checkbox for the returned approver group . If you have set this indicator then it checks if there are multiple approvers in the approver group. If it is so, it sends the request to all the approvers. If any of the above mentioned condition is not met, the BAdI displays an error message.

  • Case 4 - If you have not implement this BAdI or the approver perner and approver group is initial

    BAdI considers the request as approved.

Requirements

You should only carry out this step if both of the following points apply:

  • The SAP standard processes do not suit your needs
  • You are a competent ABAP/4 programmer

Standard settings

In the standard system, the Business Add-In is not activated.

Activities

  1. After calling up the IMG activity, a dialog box appears, in which the existing implementations are displayed. Choose Change, and proceed as follows:
  2. From the tab index, choose Interface.
  3. Save your entries, and assign the implementation to a development class.
  4. Place the cursor on the method, and double-click to enter method processing.
  5. Enter the coding for the implementation between the statements method <Interface name> ~ <Name of method> and end method.
  6. Save and implement your coding. Return to the Edit Implementation screen.
  7. Save the entries on the Edit Implementation screen.

Note

You can also change an implementation, and then activate it at a later time. In such a case, end the processing stage at this point.

  1. Choose Activate.
  2. The coding you stored in the method will be run when the application program is executed.

Example

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   Critical 
Country-Dependency I   Valid for countries specified 
Customizing Attributes Country Key Country Name
PYIN_ESS_CLM_BADI_10 IN India
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20081224 
SAP Release Created in 600