SAP ABAP IMG Activity SIMG_ICL_TICL068_A (Internal Claim Type: Specify CH Group+Screen Sequences for Other Proc.Modes)
Hierarchy
☛ INSURANCE (Software Component) SAP Insurance
   ⤷ FS-CM (Application Component) Claims Management
     ⤷ ICL_CDC (Package) FS-CM: Data Capture
IMG Activity
ID SIMG_ICL_TICL068_A Internal Claim Type: Specify CH Group+Screen Sequences for Other Proc.Modes  
Transaction Code S_KK4_08000185   IMG Activity: 
Created on 20000615    
Customizing Attributes SIMG_ICL_TICL068_A   Define Screen Sequences for all Other Processing Modes 
Customizing Activity SIMG_ICL_TICL068_A   Define Screen Sequences for all Other Processing Modes 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name _ICL_TICL068_A    

Use

In this IMG activity you define the screen sequences for the following processing modes:

  • Notification mode
  • Web
  • Overview

First of all you assign the relevant processing mode and a claim handler group to the internal claim type. For each combination of internal claim type, relevant processing mode, and claim handler group, you define screen sequences for the node categories of the navigation tree.

You would normally define screen sequences for such a combination. However, you can also define screen sequences without specifying the claim handler group. The system assumes that these screen sequences are standard screen sequences. You can also define different screen sequences for special claim handler groups.

Any changes that you make here have an immediate effect. If all screen sequences for an internal claim type are deleted, no claim with this internal claim type can be created, changed or displayed by any claim handler.

On the basis of the screen sequences provided by SAP in the Business Data Toolset (BDT) you can also define own screen sequences and store them here. (You can find further information on the BDT in the Application Help for the Claims Management system. Path: Claim -> Basic Functions -> Business Data Toolset (BDT) in Claims Management System).

Depending on the screen sequence defined here, damage descriptors are displayed either as a graphic or as a table.

In the following screen sequences the damage descriptors are displayed as a graphic:

  • Expert mode, no theft,
    View ICLO13, Section ICLO25, Screen ICLC59, Screen sequence CL48
  • Expert mode, theft,
    View ICLO13, Section ICLO25, Screen ICLC60, Screen sequence CL49
  • Notification mode, no theft,
    View ICLO13, Section ICLO25, Screen ICLQ11, Screen sequence ICNO
  • Notification mode, theft,
    View ICLO13, Section ICLO25, Screen ICLZ95, Screen sequence ICNL

In the following screen sequences the damage descriptors are displayed as a table:

  • Expert mode, no theft,
    View ICLO19, Section ICLO24, Screen ICLC57, Screen sequence CL50
  • Expert mode, theft,
    View ICLO19, Section ICLO24, Screen ICLC58, Screen sequence CL54
  • Notification mode, no theft,
    View ICLO19, Section ICLO24, Screen ICLQ01, Screen sequence ICNM
  • Notification mode, theft,
    View ICLO19, Section ICLO24, Screen ICLZ94, Screen sequence ICNK

Specify Field Attributes:

In addition, in this IMG activity you can define the field attributes for each combination of internal claim type, processing mode, and permitted claim handler group in master data maintenance.

For each dataset for the relevant field groups you define whether all fields of the field group

  • are hidden (Hide)
  • require an entry (Required entry)
  • are ready for input (Optional entry)
  • are displayed (Display)
  • If you do not want to specify the behavior, select Not Spec.

Proceed as follows:

  1. Mark the relevant entry on the initial screen
  2. Select the Field Modification button
  3. On the next screen, double-click on the dataset for whose field groups you want to set the field attributes
  4. Make the required settings for the field groups

For each field group, this definition is linked with the field group status of other criteria. This link is responsible for the status assumed by the fields of the field group in the input screen for master data.

Link Rules

  1. Linking the same criteria

    The same criteria can be two or more roles, for example, that a business partner can have, or several roles that can be grouped together into a role grouping.

    The field statuses for two identical criteria are linked, and then the result is linked with the third criterion and so on. Required entry has the highest priority here, followed by optional entry, display, hide and the non-specified entry.

    In this way the field status is reduced to a single status.

    Examples of linking:

    Criterion 1 Hide Op.Entry Op.Entry

    Criterion 2 Op.Entry Display Req.Entry


    Interim Result Op.Entry Op.Entry Req.Entry

  2. Linking all remaining different criteria (apart from the activity)

    Different criteria can be, for example, role(s) and BP type (application object business partner) or relationship category and client (application object relationships).

    The field statuses for two different criteria are linked, and then the result is linked with the third criterion and so on. Required entry has the highest priority here, followed by optional entry, display, hide and the non-specified entry.

    Examples of linking:

    Criterion 1 Hide Op.Entry Op.Entry

    Criterion 2 Op.Entry Display Req.Entry


    Interim Result Op.Entry Op.Entry Req.Entry

  3. Linking the result with the activity

    The result from above is linked with the field status for the activity. In principle, the same rules apply as above. In addition, the activity display means that all the fields are no longer ready for input.

    Examples of linking:

    Interim Result Req.Entry Req.Entry Op.Entry

    Field Status Act. Op.Entry Non-spec. Display

    Data Maint. Act. Create Display Change


    Result Req.Entry Display Display

In the Claims Management system the following namespaces apply for field groups:

SAP namespace    Customer namespace    Partner namespace

001-599    600-749    1400-2249

750-1399       

2500-2999       

Requirements

Standard settings

Activities

Example

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   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
VC_TICL068_A C - View cluster SM34  
History
Last changed by/on SAP  20050405 
SAP Release Created in 462