SAP ABAP IMG Activity SIMGH_M_TICL950 (Claim Bundle: Define Tasks and Log Entries)
Hierarchy
☛ INSURANCE (Software Component) SAP Insurance
   ⤷ FS-CM (Application Component) Claims Management
     ⤷ ICL_EVENT (Package) FS-CM: Claim Bundle
IMG Activity
ID SIMGH_M_TICL950 Claim Bundle: Define Tasks and Log Entries  
Transaction Code S_KK4_08000577   (empty) 
Created on 20030411    
Customizing Attributes SIMGH_M_TICL950   Claim Bundle: Define Tasks and Log Entries 
Customizing Activity SIMGH_M_TICL950   Claim Bundle: Define Tasks and Log Entries 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name _M_TICL950    

Use

In this IMG activity you define tasks and log entries for the claim bundle (application class ICLE).

You use the Entry Is a Task indicator to define whether an entry is a task or a log entry.

  • Task

    You can use tasks in the Business Rule Framework (BRF). In a control predicate in the BRF you can define a task for a certain anomaly. If the BRF recognizes the anomaly during processing of a claim or claim bundle, the system creates the task defined here.

    The task then appears in the following places:

    • In the list of pending tasks in Claims Management
    • In the Business Workplace
    • An executed task appears as a log entry on the Log screen in the list of executed process steps.

      You can use certain tasks (such as Check Receipt of Appraisal) as resubmission tasks for appraisals, for example. You do this in IMG activity Appraisal: Define Resubmission Task.

  • Log Entry

    A log entry is displayed on the log screen in the list of executed process steps. Log entries displayed there can be tasks that have already been executed, or entries created automatically by the system.

Make the following settings for a task and/or a log entry:

  • Key of task and/or log entry
  • Indicate whether the entry is a task or a log entry.
  • Name of task and/or log entry
  • Text of task and/or log entry

    This text is displayed to users on the interface

  • Text of the task or log entry that is displayed after completion of the task
  • You can assign a task to a task category
  • Define a navigation target for an task.

    When users click on the list of pending tasks, or on this task in the Business Workplace, the system navigates to the specified navigation target. Depending on the task concerned, the user can now clarify or eliminate the anomaly that was the cause of the task.

    Note: Read the documentation on the data element navigation target for more information on the various options for storing a navigation target in Activity Management.

    The possible navigation targets are defined in the following IMG activities:

  • Specify whether the task should be flagged as completed after navigation.
  • You can specify a priority for the task.

    Note: In the Priority Obsolete field the system displays the "old" priority used through Release 4.71, which is no longer compatible with the priority concept of SAP Business Workflow. This "old" priority is displayed for information purposes only and is not considered by the system. You cannot change it.

    Enter the required priority in the Priority field. This "new" priority is compatible with SAP Business Workflow. If you do not define a priority, the system automatically assigns a priority of 5.

  • You can define the following deadlines for a task:
    • Deadline up to first submission of task (in days and hours)
    • Deadline up to start of task (in days and hours)
    • Deadline up to end of task (in days and hours)

      The due date is determined on the basis of the deadlines defined here, and displayed in the list of pending tasks.

      For more information on the individual deadlines, see the documentation of data element Deadline up to first submission of task in days.

  • You can define a validity for a task in days.
  • You can indicate whether users can change the text of the task in the list of pending tasks.

    This setting is only relevant for tasks that can be created manually by users. Users cannot change the text of tasks that have been created automatically.

  • You can indicate whether the task should be exported using the Business Add-In (BAdI) Enable Messages from Activity Management.

    Whenever any changes are made to the task, this change is exported to an external system, such as a CRM system.

  • You can indicate whether the task and/or log entry should be visible to the policyholder or customer via the Internet.
  • You can indicate whether the task and/or the log entry should also be displayed in notification mode.
  • You can indicate whether the task definition can be changed using a BAdI.
  • You can make the setting that a task may not be completed manually. For more information, see the documentation of data element IAM_NO_SET_AS_DONE.

The following settings are only possible for tasks in the claim, and not for tasks in the claim bundle:

In IMG activity Claim Bundle: Assign Activities to a Task, you can assign 0 to n activities to a task.

Requirements

Standard settings

Activities

Example

Business Attributes
ASAP Roadmap ID 203   Establish Master Data 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
M_TICL950 V - View SM30  
History
Last changed by/on SAP  20030925 
SAP Release Created in 472