Using Data archiving once residence time reached data will be deleted from database and store to

the external system

Using ILM Archiving have additional feuture that is Blocking and deletion process which means we
will block archived data and delete archived data.
BCILM 3.0 should be certified for external storage if we want to store from ILM storage to External
Storage

Preparation:

ILM Step by Step Creation:

1.SFW5 - ILM business functionality activated for below by clicking activate changes

Need to activate ILM, ILM_STOR, ILM_BLOCKING

SFW5:

2.1 Create RFC connecting to the Store from SAP through RFC connection using this RFC connection
we will create ILM Store using TCODE: ILMSTORADM
2.2 ILMSOTRADM-> Create New, while creating this we need to queue a RFC destination

TCODE: ILMSTOREADM

3. SRS(Software and Retention Services) Connection:

SRS Configuration using SARA-> Customizing -> Technical Settings -> ILM Services -> 1. Local (SRS
service)
Configuration:
Audit Area:

TCODE: IRMPOL

Click -> New

Then EditRule

After create rule save it and policy status should be Live

If ILM enable object we can see IRM instead of content repository

TCODE: IRM_CUST

If archiving object is not enabled then we add manually archiving object as enable using this tcode
IRM_CUST
If we want add any condition field for object:
Legal Hold:

Tcode: ILM_LHM
Data Destruction:

TCode: ILM_DESTRUCTION

URI: Uniform Resource Identify:

It determines when the file is eligible for destruction

TimeBase:
ILM rule set based on creation or change date will be defined already in archiving object

Time Offset:

Any document created in start or mid-year will be consider end of year even when maintain Time
Offset “End of Year”.

Data Destruction 2 categories

1. Data destruction directly from DB

2. Data Destruction will be done based on applied Rules and Policies, we can do directly if there
are no legal holds applied

Retention where house Scenario: