SAP ABAP IMG Activity SIMG_ICL_ACT_PRIO_MA (BAdI: Conversion of Old Priorities of Tasks to New Priorities)
Hierarchy
☛ INSURANCE (Software Component) SAP Insurance
   ⤷ FS-CM (Application Component) Claims Management
     ⤷ ICL_BASIS (Package) FS-CM: General Functionality
IMG Activity
ID SIMG_ICL_ACT_PRIO_MA BAdI: Conversion of Old Priorities of Tasks to New Priorities  
Transaction Code S_KK4_08000612   (empty) 
Created on 20031002    
Customizing Attributes SIMG_ICL_ACT_PRIO_MA   BAdI: Conversion of Old Priorities of Tasks to New Priorities 
Customizing Activity SIMG_ICL_ACT_PRIO_MA   BAdI: Conversion of Old Priorities of Tasks to New Priorities 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name ICL_ACT_PRIO_MAP    

Use

Through Release 4.71, Activity Management in the Claims Management system used priorities for tasks in the claim and claim bundle, but these priorities are not compatible with the priorities of the workflow system (SAP Business Workflow). The priority in Release 4.71 and older releases of the Claims Management system (referred to as "old" priority below) is defined in a NUMC type field with length 3 (data element ICL_ACTIVITYPRIO), whereas the workflow system only knows 8 priority stages (data element ICL_TASK_PRIORITY_WF).

As tasks can be assigned to the relevant clerk in the Claims Management system and via the workflow system, it is difficult to manage two priority concepts simultaneously. For this reason, as from Release 4.72, Activity Management in the Claims Management system uses the priorities that are compatible with the workflow system (referred to a "new" priorities below) for tasks in the claim and claim bundle.

The tables that are affected should not be converted. If you need to open a claim to make changes, and the tasks in this claim are only available in the old format, then you have to convert the priorities to the new format.

You then use this Business Add-In (BAdI) to convert the old priorities to the new priorities for tasks in the claim and claim bundle.

Requirements

You have actively created tasks in the claim or claim bundle in Release 4.71 (or older releases) of the Claims Management system.

Standard settings

The standard implementation converts the "old" priorities to "new" priorities as follows:

Priority in old format    Priority in new format

SPACE     5

000 to 099     5

100 to 199     1 (highest priority)

...

900 to 999     9 (lowest priority)

Activities

If you do not have any tasks that were created in Release 4.71 or earlier releases, this BAdI is not called. You therefore do not have to do anything.

If you do have tasks from Release 4.71 or earlier releases, you can use the standard implementation if this suits your requirements.

If not, you will have to perform your own implementation that converts the priorities as you require. You have all the information that you need on a task. For your own implementation, ensure that you always get a priority that is between 1 and 9. Other values are not permitted.

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.

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