SAP ABAP IMG Activity SIMG_ICL_RBP_SRCH (BAdI: Automatic Performer Assignment for Role-Based Performer)
Hierarchy
☛ INSURANCE (Software Component) SAP Insurance
   ⤷ FS-CM (Application Component) Claims Management
     ⤷ ICL_RBP_AI (Package) Claims: Role-Based Performer: Application Integration
IMG Activity
ID SIMG_ICL_RBP_SRCH BAdI: Automatic Performer Assignment for Role-Based Performer  
Transaction Code S_PNI_08000848   (empty) 
Created on 20050519    
Customizing Attributes SIMG_ICL_RBP_SRCH   BAdI: Automatic Performer Assignment for Role-Based Performer 
Customizing Activity ICL_RBP_SRCH   BAdI: Automatic Performer Assignment for Role-Based Performer 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name ICL_RBP_SRCH    

Use

You can use this Business Add-In (BAdI) in role-based performer in claims processing to execute automatic performer assignment for existing roles.

There are three points in time for automatic performer assignment, and you can implement an own method for each of these:

  • Early assignment

    The performer is assigned as soon as a new claim is created. This point in time is suitable for the search for performers who can already be determined and assigned on the basis of the general claim data.

  • Later assignment

    The performer is not assigned until the claim is saved. This point in time is suitable for now searching for a suitable performer for all roles without performer assignment. Claim data added manually can now be used for this search.

  • Manual assignment

    You can manually assign the performer at any time in claims processing. In this way you have complete control over the assignment.

You can implement the BAdI methods individually or combined.

Note: You can use event RBP_CHANGED of the Business Rule Framework (BRF) to output a notification upon changes to a performer in a role. If this BAdI is used to assign a new performer in the background, the notification reminds the user to save when exiting the claim, even if the user has not made any changes.

Requirements

Standard settings

In the standard delivery this BAdI is not active.

Activation of the BAdI without implementation of the methods has no effect on the behavior of the system.

The BAdI is not filter-dependent and it does not have multiple uses.

Activities

After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.

If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:

  1. In the dialog box, enter a name for the implementation of the Add-In and choose Create.
    The system displays the initial screen for creating Business Add-In implementations.
  2. On this screen, enter a short description for your implementation in the Implementation Short Text field.
  3. If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
  4. Save your entries and assign the Add-In to a package.
  5. To edit a method, double-click its name.
  6. Enter your implementation code between the method <Interface Name>~<Name of Method>. and endmethod. statements.
  7. Save and activate your code. Navigate back to the Change Implementation screen.
    Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step:
  8. Choose Activate.
    When the application program is executed, the code you created is run through.

Example

  • You determine the standard performer or a performer who has been assigned for individual roles.
  • You execute a multi-step search for performers via Organizational Management or rules from the Workflow. Many different criteria (such as regional assignment) from the claim data can be considered here.

See also:

Methods

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  20050519 
SAP Release Created in 600