1.1.

1 Symptom
The database of your PI or connected Proxy system is growing and you would like to
know how to remove messages from the database. You have scheduled the required
deletion and archiving jobs, but some or all messages are neither deleted nor archived
and the corresponding database tables increase.

1.1.2 Other Terms

Archiving, Deletion, SXMSPMAST, SXMSPMAST2, SXMSCLUR, SXMSCLUR2,

SXMSCLUP, SMXSLUP2, SXMSPFRAWH, SXMSPFRAWD, XI_AF_MSG,
XI_IDOC_OUT_MSG, XI_IDOC_IN_MSG, BC_MSG, BC_MSG_LOG, workitem, ccBPM,
XI, Proxy

1.1.3 Solution

If you need detailed information about deletion and archiving please

consult http://help.sap.com.
For directly accessing the respective chapters, please use:

1. For messages and history entries in the Integration

Engine: http://help.sap.com/saphelp_nw73ehp1/helpdata/en/0e/80553b4d53273d
e10000000a114084/content.htm
2. For messages in the Adapter Framework: Note 816022, question 8 (deletion)
and http://help.sap.com/saphelp_nw73ehp1/helpdata/en/cf/b2fc3f48ecc742e1000
0000a1550b0/content.htm(archiving)
3. For workitems in the Business Process Engine: Note 836092.
4. For Performance Data in the Integration Engine Note 820622
and http://help.sap.com/saphelp_nw73ehp1/helpdata/en/8b/08b140cbe49d2ae10
000000a155106/frameset.htm

Introduction:

Looking at archiving and deletion in PI the following runtime items have to be

considered:

 XML messages and history entries in the ABAP Integration Engine

 XML messages in the Java Adapter Framework
 Workitems in the Business Process Engine (BPE)
 Performance data collected in the Integration Engine

Per default only asynchronous messages (EO and EOIO) will be persisted on the ABAP
and Java side. Synchronous messages (Best Effort) will only be persisted if an error
occurs during processing or if the parameter LOGGING_SYNC (ABAP only) is set.
Setting LOGGING_SYNC is not recommended to reduce processing overhead. Note:
Also on applications systems connected to PI via ABAP proxies the messages will get
persisted and archiving/deletion has to be configured. Performance data on the other
hand are persisted for both, synchronous and asynchronous, messages
(tables SXMSPFRAWH and SXMSPFRAWD).

In general, there are for all data types in PI two ways to remove the relevant objects from
the database - Deletion or Archiving. The exceptions are history entries and
performance data which can only be deleted. Also synchronous PI messages can only
be deleted and not archived.

Per default no deletion & archiving is carried out in the Integration Engine and BPE.
Therefore manual interaction is necessary by the administrator of the PI system to setup
a suitable deletion/archiving strategy. On the AFW messages will per default be deleted
after a default time of 1 day (for 7.0x and lower the default is 30 days). Reorganization of
PI internal processing data is vital for the performance of an PI system. Since many of
the relevant flags are persisted on database during the processing time of a message
and can not be changed easily afterwards Archiving and Deletion has to be configured
prior to processing messages for the relevant interface. If you want to change the
archiving of interfaces after the message processing please consult Note 789352.

In general only messages with a final status can be deleted. Asynchronous messages in
error cannot be deleted and have to be cancelled first. While in the Integration Engine
(ABAP) asynchronous messages that were manually cancelled or changed have to be
archived they will be per default be deleted directly in the Adapter Framework.

For the archiving, different actions need to be taken, depending on the type of object you
would like to archive:

 To archive interfaces in the Integration Server, the interfaces have to be defined

for archiving via transaction SXMB_ADM -> "Define Interfaces for Archiving and
Retention Periods". These messages will only be removed from the database via
the archiving procedure. Deletion procedures will not affect them.
 To archive workitems, it is sufficient to plan archiving jobs as described in the link
above. If a deletion job is running as well, it will delete workitems, i. e. there is no
flag for workitems as for XML messages in the Integration Server.
 To archive interfaces in the Adapter Framework (AFW), the XML DAS (Data
Archiving Store) has to be set up. If no archiving has been set up XML message
will be deleted from the AFW by the standard deletion job after a default time of 1
day (releases 7.10 and higher). You can define which interfaces should be
archived via archiving rules.