SAP ABAP Data Element ICL_PER_CHG (Delayed Change per Date of Claim/Loss)
Hierarchy
☛ INSURANCE (Software Component) SAP Insurance
   ⤷ FS-CM (Application Component) Claims Management
     ⤷ ICL_CDC (Package) FS-CM: Data Capture
Basic Data
Data Element ICL_PER_CHG
Short Description Delayed Change per Date of Claim/Loss  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type XFELD    
Data Type CHAR   Character String 
Length 1    
Decimal Places 0    
Output Length 1    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 0   
Medium 0   
Long 40 Delayed Change per Date of Claim/Loss 
Heading 50 Delayed Change per Date of Claim/Loss 
Documentation

Definition

With this option you can change the policy product (or the internal claim type) for new claims after a certain claim date (claim event). The system interprets the time entered as matching the time zone entered in your user defaults, and converts this to UTC.

Changes made using this option are independent of any possible renewals of the contract.

If the time entered is in the past when activation in the production system takes place, only those claims created after activation are automatically handled in accordance with the changes.

Claims created beforehand are handled in accordance with the old version. This avoids any conceivable inconsistency. You also have the option of assigning the active version to these claims. Choose menu path Edit -> Further Processing -> Product Setting. You should avoid doing this with large changes, because great inconsistencies could occur.

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.

Use

You would use this option, for example, if a statutory regulation stipulates improvements in the policyholder's position with claims after a certain date. This improvement is only dependent on the claim date, and not on the date on which the relevant contract is renewed annually (or in any other period). You should activate the change in the production system before the selected point in time.

If you use this option to implement a change that is to the disadvantage of a policyholder, the policyholder usually has the option of terminating the contract.

If you have several active generations, only versions for one generation are changed. The system selects the generation that was valid at the effective-from time entered. If you want to execute the change for the other generations as well, you have to navigate to the generation screen by double-clicking. On this screen you see all active generations for the selected internal claim type, and you can explicitly select one that you want to change.

History
Last changed by/on SAP  20050224 
SAP Release Created in 462