cancel
Showing results for 
Search instead for 
Did you mean: 

Deletion process on XI - what about entries with PE_Adapter entry

Former Member
0 Kudos

Hello,

we started the archiving/deletion on our development system.

As we added the interfaces to teh archive process really late there are lots of entries in SXMSPMAST most of our entries were only to be deleted.

After starting report RSXMB_DELETE_MESSAGES (_HISTORY) most netries were deleted.

But some are left:

status 014, 029, 009, 012.

The status 029 messages are from PE_Adapter (Field PID in table SXMSPMAST).

Some could be killed by using SWWL transcation (error workitems).

We started a archiving / deletion process for workitems already before we had a look at the BC_XMB objects.

Question now is:

Most of status 029 messages are processed successfully but are not deleted with the named job.

So we would expect to get a database table reaching max size only with these message entries. How can we get rid of them?

Best regards

Dirk

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

OSS 872388 question 11 together with OSS named here gave the solution!

Answers (1)

Answers (1)

dhagigeorgiou
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Dirk,

From what i have seen deleting work items via tr swwl moves messages from

029 (INI) to 003 (INI).

The delete background job will transfer them to 003 (DEL)

Dimitris

Former Member
0 Kudos

Hi Dimitris,

but when I use the standard archive/Deletion function for workitems what about the status 029 entries in SXMSPMAST?

I am afraid that there could be a mandatory sequence?

a) Archive / Delete in SXMSPMAST

b) Archive / delete in Workflow area?

Because we did the deletion for all workitems till Dec. 31st 2006, but there are 1700 entries in SXMSPMAST in status 029 for PID PE!

Possibly they all refer to the BPEs we used last year and which we deleted from the database!

I started report RSXMB_COMPARE_CENTRAL_BPE_MSG and got 129 entries lost on BPE side.

I checked some of the message IDs from the report in SXMB_MONI and found them as successfully processed.

Running the report (OSS 960240) and starting again the deletion report erased another 57 entries. But what about the other 1640 ?

Regards

Dirk

Former Member
0 Kudos

Hi Dirk,

I have faced this problem several times. Please

run report from note 894193 and then make sure that note 942651

is also implemented.

in general, the following notes have important info

964769 BPE-RUN: RSWF_XI_UNUSED_MSGS löscht verwaiste

960240 Messages mit Adapter Typ 'PE' werden nicht gelöscht

880162 BPE-RUN: Nachricht aus gelöschtem Prozess nicht

894193 BPE-RUN: Nicht mehr verwendete Nachricht finden und

but, the 894193 should help you out.

Good luck

Regards,

Jaime

Former Member
0 Kudos

Hi Jaime,

this hint was not that bad. Thank you!

I got rid of 300 Messages.

But 1400 are left for PE_ADAPTER in status 029!

So something else is missing!

What I have seen is that using TA SWWL (SP19 is our current SP) reduces the results in the report from OSS 894193. So there we have 0 results now!

Ok, solution was in the link of PE_ADAPTER entries to IDOC messages which were hanging.

In the result (OSS 872388) we are fine now!

Regards

Dirk