Deleting entries in SXMS* tables in PI and ECC

[Former Member]

Hi Experts,

Can you help me understanding the below tables. These tables contains data from Integration Engine(SXMB_MONI). The pipeline informations are stored here. The retention period of messages in PI is 7 days. We have deletion and archival jobs running in PI every 7 days.

SXMSCLUP

SXMSCLUP2

SXMSCLUR

SXMSCLUR2

SXMSPMAST

SXMSPMAST2

SXMSPHIST

SXMSPHIST2

From all these tables, every 8th days entries are deleted and new entries comes in. So i want to understand how it is working.

Is it like when a message is deleted from integration engine, the entry is also deleted from these tables?

Or any back ground activities takes place implicitely?

Please let me know if any other job needs to be run to delete the entries from these tables explicitely.

We have the same tables in ECC also but the deletion and archival jobs are not resetting the entries from the table.

Thanks in Advance,

Regards,

[vadimklimov · Accepted solution]

Hello Vicky,

Please check the SAP Note 872388 that is discussing archiving and deletion of message in various engines of PI and that contains extensive answers to your questions.

Program for archiving of messages in Integration Engine: RSXMB_ARCHIVE_PLAN.

Programs for deletion of messages in Integration Engine: RSXMB_DELETE_MESSAGES (messages deletion), RSXMB_TABLE_SWITCH (used for tables switch in case switch procedure is active). Deletion of messages cleans up tables SXMSPMAST / SXMSPMAST2, SXMSPEMAS / SXMSPEMAS2, SXMSPVERS / SXMSPVERS2, SXMSCLUP / SXMSCLUP2, SXMSCLUR / SXMSCLUR2, SXMSPERROR / SXMSPERRO2.

Program for deletion of history entries for messages: RSXMB_DELETE_HISTORY. Deletion of history entries for messages cleans up tables SXMSPHIST / SXMSPHIST2.

All mentioned programs above as well as general concept of messages archiving/deletion in Integration Engine that is described in the mentioned SAP Note, is relevant for both central Integration Engine (of the PI system) and local Integration Engines (of SAP business/application systems where ABAP proxies are used).

Regards,

Vadim

[Former Member · Accepted solution]

Thanks everyone. But i have already read all the notes you have mentioned.

There is a field REORG. Based on different values in this table, the deletion of the entries takes place. Can you help in understanding the meaning of the value or point me to some notes or blogs.

MFA     Selected for Archiving

MFD     Selected for Deletion

DEL      Deleted

ARC     Archived

INI        Initial

COP     Copied

[vadimklimov · Accepted solution]

Hi Vicky,

Here is a brief description of meaning of various possible message reorganization statuses:

• INI (Initial) - initial reorganization status
• MFA (Selected for Archiving) - used to mark message as relevant for archiving (this status is checked during messages archiving program run)
• MFD (Selected for Deletion)- used to mark message as relevant for deletion (this status is checked during messages deletion program run)
• ARC (Archived) - used to indicate the message has been archived (set during messages archiving program run  after the message was placed in the archive store and indicates the message can be deleted from online database)
• DEL (Deleted) - used to flag message as logically deleted (used during switch procedure)
• COP (Copied) - used to indicate the message has been copied (used during switch procedure when moving message from current container to new container)

Regards,

Vadim

[Eoin_Kierans · Accepted solution]

Hi Vicky,

The entries in these tables are removed by the deletion and archiving jobs. You can schedule these within the transaction SXMB_ADMIN -> Schedule Archiving Job/Schedule Delete Job.

Messages are removed from the tables depending on a number of criteria. If a message is flagged for archiving it will be archived before it is removed, this is indicated with the field ITFACTION which will show a value of ARCH. Messages which are not flagged for archiving are removed by the standard deletion job.

Messages are considered for archiving and deletion depending on the retention period, i.e how long messages are to be persisted, along with their message and adapter status. Messages must have a final message status and adapter status before they are removed.

You can check the meaning of each message status in the table SXMSMSTATT. If a message has a final message status such as 003, processed successfully, it may still not be removed if it is has a non final adapter status such as 001 or 007. How to deal with messages with none final message or adapter status is detailed within section 1.k of the note #872388

Useful reports to run to check on the reorg status of messages in your system are the following:
RSXMB_SHOW_REORG_STATUS

RSXMB_SHOW_STATUS

Hope this helps

Regards

Eoin

[Former Member · Accepted solution]

Hi,

What i can see, in sxmb_adm the retention period is mentioned as 90 days. But all the program and jobs related to those are running daily/weekly and also they are not deleting or archiving any messages within 90 days.

Is it like, based on the retention period, this program will work even though you run the deletion or archival programs daily.

regards,

Pinaki

[Eoin_Kierans · Accepted solution]

Hi Pinaki,

As you're retention period is set to 90 days, any messages older than 90 days should be removed archived or deleted. Each day more and more messages will cross this threashold, therefore it is necessary to run these jobs on a daily or weekly basis depending on the message throughput in your system.

Regards

Eoin

[Harish]

Hi Vicky,

Please have a look on below discussions

Tables SXMSCLUP and SXMSCLUR Archiving | SCN

regards,

Harish