Archival/Deletion of messages in XI 3.0 SP23

Dear All,
We need to carry out a data deletion/purging activity at our XI box, where no archival/deletion policy has been incorporated ever. As a preparatory measure, I need to have some guidelines for the activities as under,
1. While defining an Archival policy, is there any recomendation from SAP or others that message archival exercise has to be carried out first, before proceeding with message deletion? To be more precise, can we directly delete/purge the messages without archiving them? What will be the impact of such an exercise on the XI system?
This point may sound confusing but the reality is that we do not have enough H/W to carry out an activity of Archival and Deletion.
2. What is the SAP recomendation/best practice in this regard?
3. Although we are defining the Archival/Deletion policy now, we need to purge data that is 3 years old and we do not require them any more. What would be the best practice to carryout this activity?
Thanks and regards,
Sugata Basu

Hi Sugatada,
is there any recomendation from SAP or others that message archival exercise has to be carried out first, before proceeding with message deletion?
No as per my knowledge..
can we directly delete/purge the messages without archiving them? What will be the impact of such an exercise on the XI system?
This wholly depends on requirement...if the data is too old...you can directly delete it..no need to archieve..
What is the SAP recomendation/best practice in this regard?
you can set these values which close to best practice...
Retention period for both synch and asynch
msgs without error awaiting deletion : 180 days
msgs without error awaiting archieving : 45 days
retention period for history entris for deleted msgs : 30 days
in XI we have 2 types of action:
(1) deletion of XML messages (without prior archiving)
(2) archiving of XML messages with subsequent deletion
SAP_BC_XMB_DELETE* for type (1)
SAP_BC_XMB_ARCHIVE* for type (2)
Regds,
Pinangshuk.

Similar Messages

Issue with Archiving & Deletion of messages in PI ,SXMB_MONI messages

Hello experts
I am working on Archiving & Deletion of messages in PI ,SXMB_MONI, i have fallowed all the steps which are avialable in /people/deepak.shah/blog/2010/04/22/archiving-deletion-of-messages-in-pi--part-2, but the messages still there in SXMB_MONI.
please help me to resolve this issue.
regards
chandra

Hi Krish
i have fallowed steps like....
in SXMB_ADM
>>>step 1: Define the interface for archivng and retnetion period
>>>step2):Schedule Archive Jobs,
after this i have checked the in SM37 the jobs got sheduled and released after that it showing finished.
>>>step3):ARV_BC_XMB_WRP<date> (archiving, step 1)
ARV_BC_XMB_DEL<date> (archiving, step 2)
here i am getting message like "0 XML messages got archived".
"0 XML message for deleated".
I have doubt in SXMBPMAST table here when i check the status of interface , ITFACTION field is containing the value INIT and if I understood correctly it job deletes only those messages where ITFACTION is set to DEL.
We are actually trying to delete the messages avoiding archiving but what I am seeing is we cannot delete error messages and for them we must have to go through archiving. Please correct me if I am wrong.
Thanks
Chandra

Archiving/Deleting Test Messages in SAP Solution manager

Hi,
We have configured Service Desk in our solution manager 7.0 with EHP1 system.
We have created test messages to test the configuration.
We need to delete these test messages which are appearing in T Code CRM_DNO_MONITOR.
We run the report "CRM_ORDER_DELETE" but the output is
Deletion of CRM Documents
The following document could not be deleted:                 8000000259
Not possible to delete, a reference exists to a subsequent document
Number of documents deleted:                                          0
Number of documents not deleted:                                      1
So
We have followed the "Note 1329247 - Archiving Solution Manager Service Desk messages".
1)
a)Call transaction DNOTIFWL and set the deletion flag for the Service Desk message. The deletion flag corresponds to the system status I1076 (deletion flag).
b) Execute the report Z_DELETE_BASIC_NOTIFICATIONS
The above step we have executed successfully.
2)
In CRM
You cannot delete a service process in CRM. The service process must be archived.
Call transaction SARA and select the archiving object CRM_SERORD. Archiving involves three steps:
a) Initial run     Report CRM_ARC_SERORD_CHECK
b) Write run       Report CRM_ARC_SERORD_SAVE
c) Delete run     Report CRM_ARC_SERORD_DELETE
in SARA T Code we have typed archiving object CRM_SERORD.
After this what to do??? How to proceed further.
Can any body suggest us the step by step procedure to archive these test messages.
Regards,
Raj

> In CRM
> You cannot delete a service process in CRM. The service process must be archived.
> Call transaction SARA and select the archiving object CRM_SERORD. Archiving involves three steps:
> a) Initial run     Report CRM_ARC_SERORD_CHECK
> b) Write run       Report CRM_ARC_SERORD_SAVE
> c) Delete run     Report CRM_ARC_SERORD_DELETE
>
> in SARA T Code we have typed archiving object CRM_SERORD.
> After this what to do??? How to proceed further.
You need to schedule a BGD job to execute this. You can do this from the SARA screen itself, clicking on the 'Job' button. Please refer:
http://help.sap.com/saphelp_crm50/helpdata/en/e6/c66f3b6c980c3be10000000a11402f/content.htm
Rajeev

Message archiving/deletion in PI 7.1

Hi All,
I'm new to SAP PI. We have newly implemented PI 7.1 in our landscape. We have installed PI in HP UX 23 with oracle as the database.
We have configured the messge archival/deletion in our PI production server. We have allocated a dedicated file system to store the archived messages. Eventhough we have maintained the path of the archival_interface, no messages are archived in this drectory.
We are using synchronous interfaces and while executing the report ( RSXMB_SHOW_REORG_STATUS ) as per the note 872388, the report says that there are more than 1700 messages to be archived. But no messages are getting archived in the path mention as of now.
I think we have missed out some steps while configuring the archiving process. Can somebody help me with the steps involved in PI integration engine message archival/deletion.
Your timely help will be much appreciated.
Thanks in advance.
Regards,
Varadhu

Hi,
Go to transaction "SXMB_ADM" on the ABAP stack of your XI installation. Go to "Integration Engine Configuration" and click on tab "Specific configuration". Check if you have the parameter "LOGGING_SYNC" enabled (It should have a value 1). In case it is not present, please create this entry and have the default value as "1". This will enable you to view all sync messages on sxmb_moni.
Thanks,
Sidhartha

Seeburger message tracking archiving / deleting question

Hello,
We are using Seeburger 1.7 with XI 7.0 for our EDI translations..We store information in Seeburger Message Tracking for our business requirements.I would like to know how these entries could be archived(Compressed) and stored or deleted after certain days so that we wont max up our storage..?
Any suggestions are appreciated.
Thanks in advance!
Larry

Prateek,
Thanks for your response.Yes,I could find the "Archive Configuration" option..when I click that it shows me a screen saying show master data with two items with check boxes (Document Types & Archiving Systems)..On clicking the details of them I see set of parameters which shows the profile and the document type..not sure how to proceed from here to set up any archiving / deletion..any help is appreciated..
Regards,
Larry.

XI Messages Archive & Delete

Please help regarding messages archive & del. our xi production disk is almost full. i went through many threads regarding this , also OSS note: Note 872388. but nothing is working for me. would somebody please tell me the steps in simple & clear to do the acrh & del. I am posting the reports RSXMB_SHOW_STATUS & RSXMB_SHOW_REORG_STATUS in the next post.
Thanks

RSXMB_SHOW_STATUS
====================
Table Container:                                   SXMSPMAST
Overview
========
Time Stamp Not Included
Number of Messages in Database:                                           1,890,176
Number of Messages in Client:                                             1,890,176
Number of Messages for Reorganization in Client:                          1,890,176
Number of Messages to Be Archived in Client:                                    834
Number of Logically Deleted Messages in Client:                                   0
Number of Archived and Logically Deleted Messages in Client:                      0
Message Status
==============
Message Status:      001 Number:                  0
Message Status:      002 Number:                  0
Message Status:      003 Number:          1,888,648
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:                  0
Message Status:      010 Number:                  0
Message Status:      011 Number:                  0
Message Status:      012 Number:                  0
Message Status:      013 Number:                  0
Message Status:      014 Number:                950
Message Status:      015 Number:                  0
Message Status:      016 Number:                  0
Message Status:      017 Number:                  0
Message Status:      018 Number:                 11
Message Status:      019 Number:                  0
Message Status:      020 Number:                  0
Message Status:      021 Number:                567
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:                  0
Message Status:      030 Number:                  0
Message Status:      030 Number:                  0
Adapter Status
==============
Adapter Status of Messages with Message Status:              003
Adapter Status:      001 Number:                 49
Adapter Status:      002 Number:                  0
Adapter Status:      003 Number:                  0
Adapter Status:      004 Number:                  0
Adapter Status:      005 Number:                  0
Adapter Status:      006 Number:          1,888,105
Adapter Status:      007 Number:                271
Adapter Status:      008 Number:                  0
Adapter Status:      009 Number:                  0
Adapter Status:      010 Number:                  0
Adapter Status >     010 Number:                  0
RSXMB_SHOW_REORG_STATUS
===========================
Overview
=========
Retention periods and message and adapter status ignored in the following
Number of messages in DB:       1,890,024
Number of messages in client:    1,890,024
Number of messages in client still to be reorganized:      1,890,024
Archiving
============
Number of messages to be flagged for archiving
Message and adapter status is ignored in the following
- Msgs not in retention period (can be archived):            0
- Msgs in retention period (cannot be archived):           688
Message and adapter status is considered in the following
- Messages to be flagged for archiving:          0
Number of messages already flagged for archiving
- Messages to be archived:            0
Number of archived messages that can now be deleted
- Messages to be deleted:          0
Delete
=======
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):   1,888,303
- Asynchr. msgs in retention period (cannot be deleted):        1,033
Message and adapter status is considered in the following
- Asynchronous messages without errors to be flagged:              0
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

XI Message Archiving & Deletion

I'm looking to archive and delete old messages in XI 3.0 that are dated before we started running our archiving jobs. Does anyone know how to flag these old messages for archival?
Thanks in advance!

Courtney,
if the respective interfaces are configured for archiving and the messages have reached a final state, they will be picked up by your archiving job as soon as they fulfill the retention period criteria. If they are not configured for archiving and you have scheduled the delete job, they will again be picked up as soon as they fulfill the retention period criteria.
You do not need to do anything special here, as the criteria for deletion and archiving is always the retention period and not the time or date the first archiving job was running.
Regards
Christine

(Crucial)iOS 8 message app conversation archive/delete order

I upgraded to iOS8 from 7 and the message app is different when I delete messages.
in iOS 7 when you delete a message, the conversation order goes back to the last existing text. for example if you delete some text in an existing conversation, this conversation will be fall behind newer text you sent after the last existing text you have.
for iOS8 however, after I deleted texts from a recent conversation and the last existing text in that convo was something i sent two weeks ago, the convo is still all the way on top when i have other convo from minutes ago.
I don't know if I explained this clear enough, it is supposed to be like this, it doesn't make any sense.
in iOS8 the text conversation order isn't based on the last existing text time stamp, but instead is using the actual order convo order even if the text doesnt exist anymore. Maybe this explains it better.
This is a crucial issue and I have not seen anyone address it. I hope it gets fixed soon.

No, there is no way to change back to the way things were under the previous version.
Submit your feedback directly to Apple using the appropriate link on the Feedback page:
http://www.apple.com/feedback

How to delete / cancel messages in PI adapter engine

Hello expert,
we have a scenario File (EOIO) --> PI --> ABAP. Today the file we received is big (>100mb), apparently PI can't handle it, and we got error
Transmitting the message to endpoint http://host:port/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException:
Error transmitting the message over HTTP. Reason: java.io.IOException: Error writing to server.
seems like PI adapter engine got problem while delivering the huge message to ABAP integration engine. In RWB message monitoring, the message is set to Error. Unfortunately the file has been picked up many times, thus the huge message is stuck in adpater engine. In RWB message monitoring, I can see the message listed many times and status is HOLDING because the previous message can not be delivered to Intergration engine. I want to delete/cancel all the messages, I tried in RWB message monitoring to cancell the messages, however after cancelling one message, it crashed the PI system and cause a reboot.
My question is; Is there some place in NWA (net weaver admin) to force all the messages to be deleted? (Because deleting/cancel in RWB message monitoring does not work because it causes system crash).
Thanks
Jayson

Hi Team,
I couldn't able to delete old message's from one of Q system, Persistence layer is 584 % filled, after triggering delete job(RSXMB_DELETE_MESSAGES) and Persistence layer has come to 384% and further I couldn't able to delete old messages.I executed program "
                                                                                                      RSXMB_CHECK_MSG_QUEUE" and manage to delete few entries.Could you please suggest how to reduce fill level to below 100%
Switch Procedure (for Persistence Tables) Deactivated
Number of Table Entries
3.185.992
Maximum Number of Table Entries
830.000
Current Fill Level in %
384
Threshold value for fill level for executing a switch run in %
60
Number of Logically Deleted Table Entries
0
Decline of Fill Level in % Following Deletion
384
Delete or archive processed XML messages
Job log overview for job:    SAP_BC_XMB_DELETE_001 / 06302000
Date       Time     Message text                                                                               Message class Message no. Message
13.03.2013 06:39:55 Job started                                                                                     00           516          S
13.03.2013 06:39:55 Step 001 started (program RSXMB_DELETE_MESSAGES, variant &0000000000034, user ID SAPBATCH)      00           550          S
13.03.2013 06:39:55 Value for parameters DELETION-RELATED_OBJECTS-ASYNC: 1                                        XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-RELATED_OBJECTS-ROWS: 100                                       XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-RELATED_OBJECTS-IDX5_DELAYED: 0                                 XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-ROWS_PER_LOOP-DELETE: 100                                       XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION-ASYNC: 007                                     XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION-SYNC: 007                                      XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION_ERROR-SYNC: 007                                XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION-IDX5: 007                                      XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION_UNIT-ASYNC: D                                  XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION_UNIT-SYNC: D                                   XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION_ERROR_UNIT-SYNC: D                             XMS_ADM        375          S
13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION_UNIT-IDX5: D                                   XMS_ADM        375          S
13.03.2013 07:27:58 0 XML messages deleted                                                                        XMS_ADM        351          I
13.03.2013 07:27:59 Step 002 started (program RSXMB_TABLE_SWITCH, variant &0000000000034, user ID SAPBATCH)         00           550          S
13.03.2013 07:28:00 Job finished                                                                                    00           517          S

How to delete the messages from SXMB_MONI which are already cancelled .

Hi All,
The messages were earlier in System error(Red flag) state so i cancelled it manually.
I want to know how to delete the messages from sxmb_moni which are already cancelled manually using ctrl+f8.
if not possible , then i want to see them in earlier state i.e.., in System error(Red flag).
can any tell me the procedure of doing it.
thanks
Sai.

Hi AmitSri,
Thanks for u r reply,
What is retention period, where can i find this option.
And i don't have authorizations to sxmb_adm --> configure delete procedure
--> Define interfaces for archiving and retention period.
and to RSXMB_DELETE_MESSAGES in se38 , i don't have authorizations to run
Is there any way to delete the messages or make them to System error( Red flag) which are manually cancelled.
Thanks
Sai.
Edited by: sai_SHA on Aug 17, 2011 12:29 AM

How to delete gmail messages in Mail for Mac

I am using Mail 7.3 on my Macbook Pro with Mavericks 10.9.5.
I use Gmail for my email.
When I DELETE a message in Gmail it goes into the Gmail Archive (and stays in the All Mail folder)- it does NOT get Deleted.
Gmail help says I need to drag each message to the Trash when using Mail as Delete will not work.
Really?
This is a drag to do, besides there is no Trash folder.
I have a 'Bin' folder and a 'Deleted Messages' folder so I'm trying to use them.
Still for Mail and Gmail not to be compatible for Delete seems crazy.
I have tried changing the Mailbox Behaviours in Preferences but it seems to make no difference.

I Wonder if your sitting there laughing at us as if there is some big conspiracy about selecti all and deleting all from our iPhones and iPads.
The conspiracy.
Why can we not just not select all in the mail inbox and then delete all, if we do not want to delete every single one of them then deselect the few that we do not want to delete instead of having to select the thousands we do want delete individually.
And if you do make a mistake and delete the wrong emails by selecting all, then go to your trash and reinstate the ones you did not want to delete
I think 99% of us know how to DELETE emails individually, as you put it.
That's just sarcasm and if not then then your not fully understanding the question asked.
I would also say that probably 99% of us want to be able to select all and delete all if that's what we desire.
I would just like a honest answer of why we cannot select all delete all rather than giving me a load of rubbish about encase we delete something we didn't want to delete.

Deleting error messages in PI 7.1

Hi ALL,
I cancelled system error messages from Message monitoring of RWB I need to know what happens to that message is that completely removed from the tables if yes how does it happen.
Is there any other method of removing messages which are error and successfully processed...I am told there is a method of archiving and deletion of messages can you send some document for that we are using PI 7.1.
What will be the retention period of messages ideally.?
Thanks
Souz

The archiving and deletion of messages happens from the DB and the configuration is the same as it happened for lower versions.
So the document for PI7.0 should hold good for PI7.1 also.
Regards,
Abhishek.

Deleting error messages in ABAP stack and JAVA stack

Hello,
found some useful answers here about deleting messages
which are successfully delivered!
What I miss is an answer about:
a) Error messages in RWB
In Component monitoring -> Archiving you can plan a job to delete messages in status "successful" or "Cancelled with errors".
To cancel jobs you have to do this one by one. With reaction time from page manual cancellation needs hours for 100 messages (Ok, there is a multiple selection button you can use to tag per list screen!).
Now I have lots of message here
- System error
- to be delivered
- cancelled with errors (from system, special case, see next question)
ready to be erased (yes, sure about that!)
Is this the only way here to proceed?
Other question: looks like there is a default time frame for the job which looks like it is more than two months for "successful". "Cancelled with errors" is only deleted from list when reaching this status with the available button "Cancel" but not for messages with status "Cancelled with errors" set by the system.
Any chance to change that time frame.
And what about the messages "Cancelled...." by the system?
b) ABAP stack
OK, delete job is running. But looks like there is a default time frame "delete older than 2 months" (different from a! where it is more than 2 months)
I tried to delete some error messages with function "Cancel message with errors".
Now these messages are cancelled in SXMB_MONI (displayed with different status sign "Pencil").
Starting deletion job has no effect on them. Why? Because they are cancelled today and are not considered by the time frame of the deletion job?
Any help is appreciated!
(This tool is confusing me more and more! )
Hm, looks like nobody knows about this issue?
Regards
Dirk

Hi Dirk,
I am also facing the issue for deleting the messages with errors or if i have cancelled them.
Did you find any solution for these issues. Kindly let me know if you have find out any solution.
thanks
Gopesh

PI 7.1 Archiving - Delete

hi Team,
We have PI 7.1 production environment and planning to implement ARCHIVING & DELETE for Integration Engine, Adapter Engine and Business Process Engine based messages.
I had referred to 'How to arhive & delete' doc that highly available in SDN but few question after going through the doc.
1. If a interface flagged for ARCHIVING then all messages in complete message status gets automatically Archived
2. And if interface not flagged for ARCHIVING then all messages of those interfaces gets automatically Deleted
Ofcourse on these both the cases, the corresponding action takes place only provided the retention period candition meets.
1. But Wondering, How about the messages that NOT successfully processed? Somewhere in SDN i red the NOT completetly proccessed messages require to be first 'Cancelled' and then they get marked for ARCH so that it gets archived! So in this case, both 'Synchronous" and "Asynchronous" not completely proccessed messages have to be marked for 'Cancel' before they get Archived?
2. Keeping this aside how the not completely processed archving, Why we need to archive the messages that are not completely proccessed in PRODUCTION environment?
3. In regards to 'NOT Completely processed' messages, I agree to certain extend that "All these have to be removed" from Database so that we gain disk space that helps improve the performance also? Please share your knowledge.
4. Either Archiving or Delete mechanism has any dependance or functional variations on Synchronous and Asysnchronous?
I highly appriciate all those add their knowledge here to clarify
Regards
Sekhar

Dear Sekhar,
let me go through your questions step by step...
1. But Wondering, How about the messages that NOT successfully processed? Somewhere in SDN i red the NOT completetly proccessed messages require to be first 'Cancelled' and then they get marked for ARCH so that it gets archived! So in this case, both 'Synchronous" and "Asynchronous" not completely proccessed messages have to be marked for 'Cancel' before they get Archived?
This is almost correct. Canceling is required for asynchonous messages in error state only. By canceling a message its state changes from error to final and this it is allowed to be archived. In contrast synchronous messages are final right when processing fails.
Please note: archiving applies to asynchronous messages only. It is a general decision by SAP to not archive synchronous messages.
2. Keeping this aside how the not completely processed archving, Why we need to archive the messages that are not completely proccessed in PRODUCTION environment?
Once an asynchronous message enters the central Intergation Server(IS) or the local Integration Engine(IE) XI/PI takes over responsibility for this message. Canceling a message means a serious violation of the EO/EOIO protocol. This violation needs to be documented in productive environments for the purpose of tracebility.
3. In regards to 'NOT Completely processed' messages, I agree to certain extend that "All these have to be removed" from Database so that we gain disk space that helps improve the performance also? Please share your knowledge.
I am not quite sure that I got the point. For each message entering the IS/IE SAP has to provide a guided procedure to reorganize this message. For successfully processed messages this is done by standard house-keeping jobs for archivng and deletion. For messages in error state there are basically two ooptions:
(1) restert message after error has been fixed;
- if message processing is sucessful this time, we are back to normal
- if message processing fails again, we are in the very same siutation as before
(2) cancel messages; this males the message 'final' and then it is treated like sucessfully processed messages.
Thus, this is all about defining an end point in the lifecycle of each message.

Archiving Adapter Engine Messages

For AE we have implemented the Archiving:
The steps for AE we took are as follows:
1. Created archive store, and after that done home path synch and assigned it to an archive path.
2. created the archiving background job in RWB with rules and have default delete job in place.
Archiving job is running once in a day. But Default persistance duration of messages in AE is 30days.
Here I have some confusions in understanding the core logic.
1. Whether messages which have completed their 30 days of life will be archived ?
2. or messages which have completed 1 day of life will be archived(Since archive job runs every day) ?
3. I have seen Archive and delete jobs have different run times, even though delete job didn't completed yet, archive job
is deleting the messages from database. Why it is happending like that ?
4. Does we need both the archive and delete jobs or archive job alone is fine ?
Thanks
kumar

Kumar,
Here are my thoughts.
1. Whether messages which have completed their 30 days of life will be archived ? - NO
2. or messages which have completed 1 day of life will be archived(Since archive job runs every day) ? - YES
3. I have seen Archive and delete jobs have different run times, even though delete job didn't completed yet, archive job
is deleting the messages from database. Why it is happending like that ? -
Archive jobs will archive the files to the directory mentioned. you might not have access to the archive directories. i don't think the files will be deleted if you have specified Archive parameter.
4. Does we need both the archive and delete jobs or archive job alone is fine ?
Archive jobs alone is fine, if you have a specific directory to hold archive msgs.

Archival/Deletion of messages in XI 3.0 SP23

Similar Messages

Maybe you are looking for