SAP ABAP IMG Activity SIMG_ICL_ACTIVITY_MG (BAdI: Enable Messages in Activity Management)
Hierarchy
☛ INSURANCE (Software Component) SAP Insurance
   ⤷ FS-CM (Application Component) Claims Management
     ⤷ ICL_BASIS (Package) FS-CM: General Functionality
IMG Activity
ID SIMG_ICL_ACTIVITY_MG BAdI: Enable Messages in Activity Management  
Transaction Code S_KK4_08000613   (empty) 
Created on 20031002    
Customizing Attributes SIMG_ICL_ACTIVITY_MG   BAdI: Enable Messages in Activity Management 
Customizing Activity SIMG_ICL_ACTIVITY_MG   BAdI: Enable Messages in Activity Management 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name ICL_ACTIVITY_MGMNT    

Use

You can use this Business Add- In (BAdI) to influence changes to functions in Activity Management.

For example:

  • Forwarding changes in status of a task

    You can forward transactions that take place in Activity Management to other systems. These might be other SAP systems or external systems. In particular, changes in the status of tasks (Create, Change, Edit, End, and so on) are made known to the other systems.

  • Overwrite task definition at runtime

    When you access table TICL044 (task definition in the claim) or TICL950 (task definition in the claim bundle), you have the option of overwriting the task definition at runtime. In particular, you can overwrite the relative deadlines (periods).

  • Overwrite absolute deadlines of a task at runtime

    You can change the default calculation of deadlines of a task that are stored in the task definition in table TICL044 to suit customer requirements. In contrast to the use described above in " Overwrite task definition at runtime", you can overwrite the absolute deadlines (actual points in time) here.

Requirements

Read the documentation on the individual methods.

Standard settings

None of the methods of this BAdI need to be implemented for Activity Management.

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

  • For Forwarding changes in status of a task

    You want to forward certain tasks from the Claims Management system to a CRM system for information purposes. This information on the status of a task that is forwarded to the CRM system provides a person working in CRM with information on the processing stage of a claim. The CRM worker does not have to open the claim.

  • For Overwrite task definition at runtime

    You do not want to specify the relative deadlines of a task definition until runtime, as the reaction times of a claim handler to a notice of loss may depend on the contract, for example.

  • For Overwrite absolute deadlines of a task at runtime

    You want to dynamically define the absolute point in time of the next deadline at runtime, as you cannot store a relative deadline statically in TICL044, nor are you able to easily overwrite the relative deadline at runtime.

See also:

Methods for Forwarding Changes in Status of a Task

Methods for Overwrite task definition at runtime

Methods for Overwrite absolute deadlines at runtime

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  20031002 
SAP Release Created in 472