Data Archiving in SAP Claims Management (FS-CM)
When you no longer require data for your operational business, you can move this data to an external storage area to free up space on the database. However, you must first ensure that you do not need to process the data in the future. The archived data can still be read.
The following archiving objects are available in SAP Claims Management:
Claim
Subclaim
Claim bundle
Reserve lot
Benefits/services catalog items
Work packages of IMP Manager
Integration
Archive Development Kit
The ILM-enabled archiving objects are archived using the Archive Development Kit (ADK). The ADK forms the technical basis for the archiving transaction SARA
. The following archiving objects in SAP Claims Management are ILM-enabled:
Claim
Claim bundle
Note
ILM stands for SAP Information Lifecycle Management
Archiving Engine
The other archiving objects in SAP Claims Management are archived using the Archiving Engine (transaction AR_ENGINE
).
Prerequisites
You must use a customer-specific preprocessing program to mark an object that you want to archive. In detail, this means the following:
For every archiving object, the relevant master table (e.g. ICLCLAIM
for claims, ICLSERVCAT
for benefits catalog items) contains the field ARCHIVE_STATUS
. Ensure that your preprocessing program sets this field from initial to 1 (for Not Archivable
). This status is required as the starting status. Only then can you decide if you really do want to archive the archiving object.
Note
SAP provides the program ICL_ARCHCLAIM_PRESTEP
as an example.
More Information
For more information about the management and destruction of archived data, see under the key word Information Lifecycle Management (ILM) or Using ILM Retention Management in the Application System in the documentation of SAP NetWeaver
under http://help.sap.com/nw
.