Fail Archiving failed in the source system

[praveen_hannu]

Hi Friends,

There is one interface running, XI pickups the file from sender system and putting into the receiver system.

Here sender system is Synergy and Receiver is SAP R/3. But here the problem is the file is not moving

to archive once it is kept in R/3 system, the message showing that the attempt to archive the file

but get failed.

Can you please help me how to rectify this.

Thanks and Regards

Praveen

[Former Member]

Hi Praveen,

yours question is a bit confusing. Are you using XI archiving/deletion job for archiving?

Could you explain the sceanrio ?

Ranjeet Singh.

Edited by: Ranjeet Singh on Jan 25, 2008 10:25 AM

[praveen_hannu]

Hi Ranjit

We are using SAP XI archiving method. There are some files are getting archived automatically and replacing, few files are archiving and replacing automatically.

Regards

Praveen

[Former Member]

Hi,

Please confirm that you have provided enough rights to user using which file is being picked and archived from a directory. If the file is being polled successfully and not being archived then it could be caused because of insufficient rights on this directory.

Thanks,

Bhavish

Reward points of comments helpful

[Former Member]

Praveen,

To prevent overwriting of archived files try to use Archiving with timestamp. Also check read,write,execute access of the Archiving folder.

Regards,

Sudharshan N A

[Former Member]

Hi Praveen,

Please check that the whether interfaces have been marked for retention/archiving. Only interfaces for which retension period has been set will be archived otherwise not.

One more thing is that only data which have come to XI after setup of archiving procedure in XI will be archived , old message will not be archived . But this can be corrected.

Please go through the note. 866896

here is the documentation that I had prepared for myself.

Problem Description:

Old XI message cannot be archived if we have not set them for archiving before the first message was processed in integration engine. When XI messages are processed successfully in integration engine, they are flagged with status DEL (to be deleted). It means that these messages can be deleted from XI persistence layer but they cannot be archived. If we run report RSXMB_SHOW_REORG_STATUS, these messages will come under ‘Delete’ section not in ‘Archiving’. So ideally to do the archiving of XI messages, we should select the corresponding interface and set retention periods before processing any message from those interfaces.

Solution Approach:

To resolve above problem, SAP has provided a standard ABAP report ,namely, SXMB_SET_ITFACTION_TO_ARCH.This report changes the flag for delete or archive decision making at already processed message from DEL(deletion) to ARCH(archive).

Selection criteria are only the execution time and date of the message. There is a 'start date' input field and an 'end date' input field on the initial screen of the program. To assure that all messages within the given time period will be changed, don't change the 'start date' field at a repeated run after an abortion. If the Program aborts while processing, it stores the date and time of the last changed message to assure continuous following processing. This date and time appears in the 'start date' input field at the next program run. If running the program in a batch-job, create a new variant after abortion of the batch-job to get the 'start date' field automatic filled. To limit the amount of messages being changed in one run, we can give an end date. There is also a 'block size' input field with default value 1000. This means that the program commits every 1000 messages changed, so in the case of abortion there is no need to process all messages again. We can change the default value if needed (e.g. set it lower if the update repeatedly dumps or set it higher to achieve better performance).