Ansicht
Dokumentation

SIMG_ICL_TICL068 - Internal Claim Type:Specify Claim Handler Group+Scrn Sequences f.ExpertMode

CPI1466 during Backup   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

In this IMG activity you define the screen sequences for expert mode, depending on the internal claim type.

You would normally define screen sequences for a combination of internal claim type and claim handler group. 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.

For each internal claim type (or combination of internal claim type and claim handler group), you define screen sequences for the following areas prescribed by SAP:

• Claim header

Here you define the screen sequences for the claim header in the prescribed node categories of the navigation tree.

• Subclaim

Depending on the permitted subclaim types that you defined for the relevant internal claim type in IMG activity Configure Internal Claim Types, you specify the screen sequences at subclaim level for the prescribed node categories.

• Damaged object

You specify the screen sequences for the damage categories that you assigned to a permitted subclaim type in IMG activity Configure Internal Claim Types.

• Participant

Here you specify the screen sequence for the relevant participant role.

• You can also specify which data sets are hidden for this combination.

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

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

1. 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. Hide has the highest priority here, followed by display, required entry, optional entry, and the non-specified entry.

Examples of linking:

Criterion 1         Hide        Op.Entry    Op.Entry

Criterion 2         Op.Entry    Display     Req.Entry


Interim Result      Hide    Display    Req.Entry

1. 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 displaymeans 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

BAL Application Log Documentation   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 6179 Date: 20240524 Time: 011256     sap01-206 ( 81 ms )