Hierarchy
⤷ FS-CM (Application Component) Claims Management
⤷ ICL_CUST (Package) Customizing Claims Management
IMG Activity
ID | SIMG_ICL_TICL060 | Define Incident Types |
Transaction Code | S_KK4_08000002 | (empty) |
Created on | 19990827 | |
Customizing Attributes | SIMG_ICL_TICL060 | Define Loss Incident Type |
Customizing Activity | SIMG_ICL_TICL060 | Define Loss Incident Type |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | _ICL_TICL060 |
Use
In this IMG activity you define the incident types available in the Claims Management system.
Make the following settings for each incident type:
- Key of incident type
- Name of incident type
Meaning of the incident type for the "Claim with Product Customizing" scenario
The internal claim type is determined from the combination of incident type and policy product. This is done via the following IMG activities:
- Configure Policy Products
Here you assign the incident type to a policy product.
- Assign Internal Claim Type to Combination of Policy Prod + Loss Incident Type.
Here you assign an internal claim type to a combination of policy product and incident type.
Example:
You assign internal claim type C to the combination of policy product A and incident type B. When you create a claim with policy product A and incident type B, the system applies the rules that you defined for internal claim type C to this claim.
You can use the internal claim type to control which subclaim types should apply for an incident type.
Example:
For incident type Theft you can use the internal claim type to specify that only own-damage subclaims can be displayed and opened.
With incident type Accident, on the other hand, you can use another internal claim type to specify that liability subclaims as well as own-damage subclaims may be displayed and opened, even though the claim refers to the same contract (and so to the same policy product).
If you use the "Claim with Product Customizing" scenario in the application, you must specify an incident type when you create a claim.
Meaning of the incident type for the "Claim Without Product Customizing" scenario
In this scenario, the claim type is not determined from the combination of incident type and policy product, but entered manually when the claim is created. When you create a claim with this scenario, this means that the incident type is not actually required. However, later on, at claim header level, on the Claim Overview screen, you can store an incident type in the Claim Notification Data section.
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 |
M_TICL060 | V - View | SM30 |
History
Last changed by/on | SAP | 20050405 |
SAP Release Created in |