Early Watch Alert Archiving in SOLMAN


In this article, we will discuss how to delete/archive Early watch alert documents and sessions in solution manager system.

Why we need archiving?

To reduce the data footprint and perform the housekeeping tasks for fastest growing tables.


First discuss with your stack-holders if we need to permanently delete old Early watch alert reports or we just need to Archive them and use as on when required.

We need to setup the retention time for EWA reports using transaction code: SOLMAN_EWA_ADMIN

If retention time =0, EWA will have unlimited retention time i.e no EWA reports are deleted forever.

Let us discuss both the approaches in detail:

  1. Archive the EWA reports
  2. Delete EWA reports permanently.

A) Archiving

We need to setup the weekly job: SM:ARCHIVE SESSIONS AND DOCS which runs report: RDARCH_ARCHIVE_DATA_SOLMAN.
This report will not free up space.
However if executed with default parameters, it will archive all closed sessions which are in archive queue, older than 90 days.

let us discuss each field in this report.


Useful to archive sessions older than “Days”.

If we enter few “Days”, together with “From Original” or “From Original and Repository” and “Delete From DataBase” checkmarked, we could archive and delete recent sessions.

Sessions and Documents

Here we have a option to choose to choose both or one of them i.e wither EWA sessions or documents.

From which Aspect View is Data to be Archived

  • Only From Original
    Only from”Original” means sessions which are not yet closed can be archived.
    For this option the parameter “Days” permits to archive recent not closed session.
  • Only From Repository
    ‘Repository’ denotes the archive queues in which closed sessions can be retrieved.
    As a result, this option processes only the closed sessions.
    For this option ‘Days’ parameter is irrelevant as session closure depends on ‘Retention Time’ set by both transaction SOLMAN_EWA_ADMIN and report RDSWP_SSA_MOVE_2_ARCHIVE_QUEUE.
  • From Original and Repository
    ‘Original’ indicates sessions not yet closed while
    ‘Repository’ indicates archive queue in which closed sessions can be retrieved.
    i.e. This option will archive both closed & not closed sessions.

Table Entries After Archiving

  • Delete From Database

    SAP do not recommend to select this option instead use report RDSMOPREDUCEDATA to serve the purpose.
    If we select option ‘delete from database’ , sessions will be removed from solution manager system and will be kept in the attached archive system.

    We do this as we rarely need archived sessions & our purpose of Database space is release is fulfilled.
    In case we need to retrieve the this sessions, we can only do this by running old transaction DSA with proper time period for all the closed and deleted sessions.

    If we don’t select check mark ‘Delete from Database’, all the service sessions in SOLMAN system keep on storing data & only sessions are stored to archived system.
  • Adjust Archive to DB
    This will keep in synchronization sessions between Solution Manager and archive systems.

DON’T USER DELETE FROM DATABASE OPTION in this report as SAP recommends doing it using report RDSMOPREDUCEDATA.


The report RDSMOPREDUCEDATA which is SAP recommended report will delete service sessions, attached download data, documents and reporting documents.