cancel
Showing results for 
Search instead for 
Did you mean: 

Deleting XI messages (cleaning the system).

Former Member
0 Kudos

Hi folks,

I’ve found a lot of threads and some documentation regarding this issue, but no ones cleared enough for me… Since one month ago we are exchanging messages between our XI PRD and CONS Business Systems Landscape. We are going to go-live in one week and we want delete, not archive, all the test messages in both stacks, I mean ABAP and Java.

I’ve tried the report RSXMB_DELETE_MESSAGES and check it with RSXMB_SHOW_REORG_STATUS report, but only some messages were deleted from DB. I’m not sure about the meaning of this report and SAP help didn’t help too much.

Anyone could provide me the steps to do such task?

Thanks in advance,

Ricardo.

Accepted Solutions (1)

Accepted Solutions (1)

justin_santhanam
Active Contributor
0 Kudos

Ricardo,

I don't know if it helps you or not, just have a look on the below SAP Note.

Note 872388 - Troubleshooting Archiving and Deletion in XI 3.0 / PI 7.0

raj.

Answers (2)

Answers (2)

aashish_sinha
Active Contributor
0 Kudos

Hi,

you can use RSXMB_MARK_DELETABLE_MESSAGES and

RSXMB_DELETE_MESSAGES will delete all successfully processed asynchronous messages but not error messages.

if you are looking for T Tables

Look into

1. SXMSPEMAS

2. SXMSPERROR

3. SXMSPMAST

4. SXMSPVERS

refer links http://help.sap.com/saphelp_nw04/helpdata/en/0e/80553b4d53273de10000000a114084/frameset.htm

Regards

Aashish Sinha

PS : reward points if helpful

Former Member
0 Kudos

Ricardo,

>Only some messages are deleted?

Could be various reasons ..

Do you have asynchronous messages which are in error status? If so those messages will not be deleted till you cancell them.

Did you check the retention period of the messages?

Why dont you post the content of the report in this thread. We would see if we can help you analyze that.

Regards,

Sumit

Former Member
0 Kudos

Hi,

Yes I've async in error status.

Maybe I should run RSXMB_CANCEL_MESSAGES before RSXMB_DELETE_MESSAGES.

I don't have any retention periods, should I need it for messages deleting?

Anyway, the report is the standard RSXMB_DELETE_MESSAGES mentioned above.

Regards,

Ricardo.

Former Member
0 Kudos

Just to add,

I tried the RSXMB_CANCEL_MESSAGES and it canceled 1000 mesages from 3000. It have chaged the message status from 014(error - restart posible) to 21(canceled manually). I don't know why it didn't calceled the other 2000...

I could check this using report RSXMB_SHOW_STATUS

Any ideas guys?

Regards,

Ricardo.

Former Member
0 Kudos

Ricardo,

>Maybe I should run RSXMB_CANCEL_MESSAGES before RSXMB_DELETE_MESSAGES.

That report would indeed cancell the messages but i woudnt recommend you to schedule the report in production. You woudnt want to cancell all the messages. Suppose a message goes into error because of some mapping problem. We can correct the mapping get it transported in production and restart the message.

>I don't have any retention periods, should I need it for messages deleting?

Offcourse you need to define. In your case you/someone else must have defined the same without actually knowing that you did the same. Go to SXMB_ADM->Integration Engine Config- Specific Configuration and check the value of the following parameters :

DELETION PERSIST_DURATION ASYNC

DELETION PERSIST_DURATION HISTORY

DELETION PERSIST_DURATION SYNC

DELETION PERSIST_DURATION_ERROR SYNC

> I don't know why it didn't calceled the other 2000...

Might be those other 2000 messages are synchronous msg which can not be cancelled.

See if you can find one message out of those 2000 and find out what is the status of that message.

Regards,

Sumit

Former Member
0 Kudos

Hi Sumit,

Thanks for the advice, but I was not intended to schedule RSXMB_CANCEL_MESSAGES relating to the same reasons that you have mentioned. I’m just using it manually to cancel all error messages, because when the go-live day arrives we will have to point this XI to another R/3 client and I don’t want to resend (RSXMB_RESTART_MESSAGES) all the old error test messages to the productive environment. I also know this report has a selection screen and we can choose the start date, but it will be another colleague that will do that and I’m just trying to avoid test data in a productive environment…

Regarding my 2000 messages that still remaining in error (not canceled), such messages have the status 014 and I’m not sure if I have 2000 sync messages in error, I only have one sync interface and it’s all about few messages. Anyway, when I try to search it at sxi_monitor I got 1000 messages, the same number that I’ve canceled and all are in status 021 (manually canceled), seams correct! But, now I’m wondering where are the other 2000 messages showed via RSXMB_SHOW_STATUS, do you know?

About deleting all messages; do you know if after I set the retention periods I’ll be able to delete all messages, like cleaning all messages at ABAP stack? And for the messages at Java stack do you have an idea how to delete it?

Thanks a lot for your help, regards,

Ricardo.

Former Member
0 Kudos

Ricardo,

Can you copy and paste the content of report(RSXMB_SHOW_REORG_STATUS) over here .

When you execute the report select the option Check Messages to be deleted. Those 2000 messages are not synch for sure because of status 014.

>About deleting all messages; do you know if after I set the retention periods I’ll be able to delete all messages, like cleaning all messages at ABAP stack?

Yes you would be able to do if you have scheduled the report provided the messages are in final status. Also see the note mentioned by Raj.

>And for the messages at Java stack do you have an idea how to delete it?

Deletion of messages for AF.. See Note 816022 Question 8.

Regards,

Sumit

Former Member
0 Kudos

Hi Sumit,

Here follows the content of both reports:

RSXMB_SHOW_STATUS

Message Status

==============

Message Status: 001 Number: 0

Message Status: 002 Number: 0

Message Status: 003 Number: 2.147

Message Status: 004 Number: 0

Message Status: 005 Number: 0

Message Status: 006 Number: 0

Message Status: 007 Number: 0

Message Status: 008 Number: 0

Message Status: 009 Number: 11

Message Status: 010 Number: 0

Message Status: 011 Number: 0

Message Status: 012 Number: 13.361

Message Status: 013 Number: 0

Message Status: 014 Number: 3.778

Message Status: 015 Number: 0

Message Status: 016 Number: 0

Message Status: 017 Number: 0

Message Status: 018 Number: 0

Message Status: 019 Number: 0

Message Status: 020 Number: 0

Message Status: 021 Number: 1.731

Message Status: 022 Number: 0

Message Status: 023 Number: 0

Message Status: 024 Number: 0

Message Status: 025 Number: 0

Message Status: 026 Number: 0

Message Status: 027 Number: 0

Message Status: 028 Number: 0

Message Status: 029 Number: 143

Message Status: 030 Number: 0

RSXMB_SHOW_REORG_STATUS

Number of messages to be flagged for deletion

Message and adapter status is ignored in the following

- Asynchr. msgs not in retention period (can be deleted): 17.629

- Asynchr. msgs in retention period (cannot be deleted): 1.766

Message and adapter status is considered in the following

- Asynchronous messages without errors to be flagged: 1

Message and adapter status is ignored in the following

- Synchr. msgs not in retention period (can be deleted): 0

- Synchr. msgs in retention period (cannot be deleted): 0

Message and adapter status is considered in the following

- Synchronous messages without errors to be flagged: 0

- Synchronous messages with errors to be flagged: 0

Number of messages already flagged for deletion

- Messages to be deleted: 0

Regards,

Ricardo.

Former Member
0 Kudos

Ricardo,

Also paste the OverView section of both the reports.

If you dont understand execute the report again and see the result.

Regards,

Sumit

Former Member
0 Kudos

Ricardo,

Check if any entries are stuck in SMQ2.

Regards,

Sumit