You can use archiving object ICLCLAIM
to archive claims. This means:
You can archive claims in archiving files.
You can delete these claims in the database tables.
Note
The prerequisite for using SAP Information Lifecycle Management (ILM) for archiving object ICLCLAIM
is that you have activated the business functions ILM
and INS_FSCM_ILM_1
.
The ILM object ICLCLAIM
is assigned to archiving object ICLCLAIM
(technical names are the same). In the ILM object ICLCLAIM
, you enter the retention rules for claims. As the time reference, you have the date on which the claim was last changed (table ICLCLAIM
, field ACHANGETIME
). As the condition field, the combination of internal claim type, subclaim type and coverage type is used.
In Customizing for Claims Management
, you can change the settings for the condition field under and Assign Condition Field in Claim to Application Rule Variant
.
Example
A policyholder cancels his auto liability insurance effective December 31, 2013. He had submitted a collision claim on this insurance, and this claim was closed on September 17, 2013. For a certain period - the residence period - the corresponding business partner and his claim can still be accessed freely by any claim handler and can also be changed or reopened. You define the length of the residence period in ILM Customizing for the business partner. For collision insurance, for example, this is six months, meaning that the end of the residence period for this business partner is reached on March 17, 2014, and the ILM then locks the business partner. Normal claim handlers who do not have any additional authorization are then unable to display the business partner or his claims. As of this point in time it is possible to archive the business partner and his claim.
If deletion of data is not permitted for any reason, such as legal reasons, you can enter a retention period for the claim - like 7 years - in ILM Customizing. When this period ends on September 17, 2020, the business partner and his claim are deleted automatically from the database and archive.
Caution
For reasons of compatibility, you are no longer able to use the Archiving Engine (transaction AR_ENGINE
) to archive claims. You can only use the standard transaction SARA
. To enable parallel processing, there are now two application types in the Parallel Processing Framework:
ICL_PRE
(Analysis Phase of Archiving Object ICLCLAIM
)
ICLCLAIM ICL_WRI
(Writing Phase of Archiving Object ICLCLAIM
)
Before a claim can be archived, it must fufill the residency requirements (these are defined in the archiving scenario configuration for Archiving Engine). In addition, the following conditions must be fulfilled:
The claim is closed.
Note
Here, the system does not check whether the claim bundle has status 2 (Closed
), but that the indicator STHANDLER
is not set in table ICLCLAIM
(meaning that claims processing must not be active).
If other claims are assigned to the claim, they must also have been closed.
If the claim is assigned to a claim bundle, the claim bundle must have already been archived.
The claim no longer contains any active workflow tasks.
You can also define own checks by using the Archiving Factory to create and configure a check module.
The standard selection options are available for archiving object ICLCLAIM
.
You can view the archived claims in display mode (transaction ICLCDC03
). The title line contains the addition “Archived”.