SAP ABAP IMG Activity SIMG_IGN_VC_TICL320 (Configure Policy Products)
Hierarchy
☛ INSURANCE (Software Component) SAP Insurance
   ⤷ FS-CM (Application Component) Claims Management
     ⤷ IGN (Package) IS-IS: Insurance General
IMG Activity
ID SIMG_IGN_VC_TICL320 Configure Policy Products  
Transaction Code S_KK4_08000097   IMG Activity: 
Created on 19991122    
Customizing Attributes SIMG_IGN_VC_TICL320   Define Policy Products 
Customizing Activity SIMG_IGN_VC_TICL320   Define Policy Products 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name _IGN_VC_TICL320    

Use

In this IMG activity you configure policy products .

Make the following settings for each policy product:

  • Key of policy product
  • Name of policy product
  • Period in which a version of the policy product is valid
  • Payment settings that apply to this policy product:
  • If the benefit types of a benefit type tree are to be valid across coverage types, enter the benefit type tree in the detailed view of the version of the policy product in the Benefit Type Tree field.

    Note:

    You can find detailed information on the assignment of benefit type trees in the documentation for IMG activity Configure Benefit Type Trees in the Activities section.

  • Assign the permitted coverage types to a version of the policy product.

    At the level of the permitted coverage types you can make the following additional settings:

    • You can specify the country and the region for which the relevant coverage type should be valid in connection with this policy product.
    • You can specify whether the coverage type should be Always Covered.
    • You can define a basic coverage type for a coverage type.
    • You can define the display mode of the coverage type in the policy snapshot.
    • If the benefit types of a benefit type tree should only be valid for a certain coverage type, assign the benefit type tree to the required coverage type on this level.
  • Assign the permitted incident types to a version of the policy product (at the level of Determination of Internal Claim Type).

    When you create a claim in the application, the input help of the Incident Type field only contains those incident types that you assigned to the relevant version of the policy product.

    Note:

    In this IMG activity you cannot assign any internal claim type to the combination of policy product and permitted incident type, since no internal claim types have yet been defined. You assign the internal claim type in IMG activity Assign Internal Claim Type to a Combination of Policy Product and Incident Type.

Generations and Versions

Note: The following describes the behavior of generations and versions for policy products. All these details also apply to internal claim types and benefit type trees.

Navigation to Generations and Versions

From the initial screen you can navigate to all previous generations and versions of the policy product.

  1. In the initial screen, select the policy product
  2. Select menu path Goto -> Details. This takes you to the level of the previous generations.
  3. Mark the relevant generation
  4. Select menu path Goto -> Details. This takes you to the level of the previous versions.

Notes on Generations Level and Versions Level:

  • To display inactive generations and/or versions as well, select menu path Policy Product -> Active <-> All.
  • At the relevant level you can change the validity period for the generation and/or version.

You can also create a new version of the policy product based on an older version. Select the desired older version and then press the Change button. The system creates a new suspense entry on the basis of the older version.

General Information on Versioning

All attributes of a policy product are time-dependent.

If the policy product that you want to change already has a suspense entry, this entry will always be changed.

If there is no suspense entry, the system inquires about the type of change, and a new suspense entry is created. Changes to claims assigned to this version during claim creation on the basis of the specific date (renewal of contract, date of loss, or period of services provided) do not become effective until you activate these suspense entries.

Suspense entries have no effect whatsoever on claim processing, meaning that you can delete suspense entries. Before suspense entries are activated, the system performs numerous consistency checks and displays them in the form of a log.

Generations and Versions of a Policy Product

You can change a contract renewal date in the following ways:

  • Changes that are to apply to all claims that occurred after a certain date lead to new versions of the policy product. The old version applies to claims before this date, and the new version to all claims after this date.
  • Changes that are to apply to all claims whose contract was renewed after a certain date lead to new generations of the policy product. The old generation applies to claims whose contract renewal date was before this date, and the new generation applies to claims whose contract renewal date was after this date.

Details on Versioning

Version and generation numbers are assigned automatically by the system. Version numbers with every new generation begin with the number one. The generation and version numbers of the policy product are not related to those of the assigned internal claim types.

If a contract is never renewed, the generation produced when the contract was created applies. The renewal date generally differs from contract to contract. In the event of a claim, the generation that is valid is determined on the basis of the last renewal date before the date of loss. The policy system must transfer the last renewal date before the date of loss to the claims system.

The user making the change and the time of the change are recorded.

You define the time period in which a version or generation is effective in the valid-from date and the valid-to date fields. When you activate simple changes, the old version is automatically given a valid-to date that corresponds to the valid-from date of the new version. For tracking reasons, the time stamp records when the valid-to date was set (= point in time at which the new version was activated).

  • Simple changes are:
    • Changes without specifying a valid-from date
    • Changes with a valid-from date after the system date (future changes)
  • Complex changes are:
    • Deletions
    • Changes with a specified valid-to date (temporary changes)
    • Changes with a valid-from date before the system date (retroactive changes)
    • Changes with a valid-from date before the oldest valid-from date set to date (reset of future changes)

Complex changes can lead to inactive versions or generations.

Requirements

Standard settings

Activities

Once you have made all the required settings for the policy product, you have to activate the policy product. To do so, select menu path Policy Product -> Activate. The policy product is now given the status of Active.

Note: Consider that after every transport of customizing to a downstream system all objects of time-dependent customizing (policy products, internal claim types, benefit type trees) have status T (for Transport). You must therefore explicitly activate each policy product, each internal claim type, and each benefit type tree in the downstream system.

Example

  • Product A: Auto Germany for private customers with the possible coverages
    • Liability - standard
    • Liability - compact
    • Liability - optimal
    • Fully comprehensive - standard
    • Fully comprehensive - compact
    • Fully comprehensive - optimal
    • Part comprehensive - standard
    • Part comprehensive - compact
    • Partially comprehensive - optimal
    • Passenger accident
    • Roadside assistance

      The highlighted coverage types (all, in this case) are basic coverages. They have all been assigned as a permitted coverage type to a policy product in IMG activity Configure Policy Products.

      A contract contains Liability Optimal, Fully Comprehensive Standard and Roadside Assistance, for example. However, a contract never contains liability standard and liability optimal simultaneously.

  • Product B: Auto Germany for private customers&#x
Business Attributes
ASAP Roadmap ID 203   Establish Master Data 
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
ICLCVERM320 T - Individual transaction object ICLCVERM320  
History
Last changed by/on SAP  19991217 
SAP Release Created in