Archiving & Deletion XI 3.0/ PI 7.1 - Need Help

[Former Member]

Hi All,

I have configured the Archiving / Deletion settings in both Xi 3.0 & Pi 7.1. I had gone through the documentation from SAP Help & also the Step-by-Step Guides, Blogs, FAQs.

Brief Information abt my settings,

- Done the technical settings of the Archiving objects (Logical File name, Logical path.... etc)

- Done the Interface/ retention period settings etc..

I was able to do the archiving /deletion also, for many msgs. & also read them from Archive.

The main issue is, I am unable to archive/delete some msgs, which I expect to be Archived/deleted.

Cos these are exactly the interfaces I have given in the settings & these are well outside the retention period and they are successful Async msgs.

I could see them in SXMB_MONI (with similar input data as given in A/D settings).

When I run the Archiving job, it creates an empty run without archive file etc.

I am puzzled by the intermittent working of this set-up (I had been testing earlier and many msgs were archived), now I have narrowed down to couple of interfaces & trying to see the Archiving for them.

Is there any overall setting controlling this?? pls help.

Thanks

Knowledge Quest

[Former Member · Accepted solution]

Hi,

Perhaps report RSXMB_SHOW_STATUS or RSXMB_SHOW_REORG_STAT will give you more

information. Iu2019m wondering specifically about the Adapter Status at the bottom of the report RSXMB_SHOW_STATUS. You can directly take a look at the ADAPT_STAT values from table

SXMSPMAST for the messages in question.

If you see 001 or 008, then you will need to schedule report SXMS_REFRESH_ADAPTER_STATUS to run (SAP Note 872388). If you see 007, you may need to resolve the errors first.

Thanks,

-Russ

[Former Member · Accepted solution]

Hello Russell,

Thanks for the info.. I had a look at some of these reports already..

but they dont relate anything to the situation.

for ex. the RSXMB* reports give counter on the number of msgs in different status..nothing specific

however, i think I can get some info from SXMSPMAST ,since it is based on msg id..

but how to relate the issue (as like u mentioned adapter status)

abt adapter reports, I dont think that anything is strange in this area as well..

To put it simple, the transaction is an aysnc checkered flag trans in MONI...nothing different

I shall check the system tomorrow and keep you posted..

meanwhile if you can throw some more light on relating the indications of the above (or any other) reports to the issue it would be great...

Thanks again

Knowledge Quest

[Former Member · Accepted solution]

Hi,

I just wanted to point out that the Message Status can show successful (003- checkered), but the

Adapter Status can keep the messages from being archived/deleted. This may not be your issue at all,

but it was for me recently.

If you get stuck, one thing which also helped me was to see the actual SQL queries which were being

executed when I ran the jobs. Use ST05 with a Trace Filter. Look for queries against the SXMSPMAST table. You should be able to see why your messages are not being picked up. Hereu2019s an example for a delete action query from our XI system. You can see that both the message state and adapter state have to match the criteria.

11794,110 SXMSPMAST  FETCH       0   1403
                                                             
SELECT WHERE "MANDT" = '020' 
	AND "MSGSTATE" IN ( 003 , 020 , 010 , 022 , 023 , 024 , 021 , 011 ) 
	AND ( "ADAPT_STAT" = 006 OR "ADAPT_STAT" = 000 ) 
	AND "ITFACTION" = 'DEL' 
	AND "MSGTYPE" = 'A' 
	AND "EXETIMEST" <= 20080917033327 
	AND "EXETIMEST" >= 0 
	AND "REORG" = INI

Thanks,

-Russ

[Former Member · Accepted solution]

Hello Russ,

Thanks so far.. I hope that I can proceed further from here...

Regards

Knowledge Quest