Archiving Days Before Archiving issue

[Former Member]

Hi,

I am currently trying to catch up archiving in one of our sites. Archiving has not been run since
production started in 2013.

My work procedure has been to step by step decreasing the Days Before Archiving system rule for the site
(Not the global * site) and then running the Archive batch file.

I started using a value of 600 and then gradually decreasing it by 20 days.

This worked perfectly all the way, but now even though the system rule is changed to 480, the Archive is
still using the old value of 500.

I made a trace of the archive that shows amongst other the following line:

#2.0 #2014 11 28 04:59:47:547#+0800#Info#com.sap.me.trace#

##sap.com/me~ear#C000AC118E370DB3000000010000270C#3973750000000002#sap.com/me~ear#com.sap.me.trace.VM#Guest#0##93D3E25418F710088E06A6F1FBC239BD#93d3e25418f710088e06a6f1fbc239bd#93d3e25418f710088e06a6f1fbc239bd#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##

*** ARCHIVE BATCH! daysRule = 500 sql=

WHERE SITE = 'CNBE1'  AND ACTUAL_END_DATE < '2013-07-15T20:59:47.000Z'  AND STATUS = 'CLOSED' #

So the daysrule is still 500 and the date it is using for the select is 500 days back from now.

This is the system rule settings regarding Archiving:

Miscellaneous
Allow Multiple Data Collection	True False Use Global Setting		FALSE
Archive Component When Parent Archived	True False Use Global Setting		TRUE
Archive SFCs When Shop Order Is Closed or Done	True False Use Global Setting		FALSE
Days Before Archiving SFC/SO			365

Any idea what might be causing this?

Best regards,

Johan

[sergiy_katerinich · Accepted solution]

Hi Johan,

It is because of caching. System Rules, in particular, are cached, especially if NW instance is running several server processes or it is a NW cluster. For the case of a single node, sometimes it happens that something gets broken at NW layer, and as result caching fails to pick up a new value right after the change.

If it is not about the failure at NW layer, then cache refresh can be triggered by NotificationService.NotifyCacheUpdate webservice. You need to use the following cache name for System Rules:

<cacheName xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">SystemRuleBOCache</cacheName>

Otherwise, you need to restart NW.

Regards,

Sergiy

[Former Member · Accepted solution]

Hi Sergiy,

Thank you for the caching information.

I switched to another application server and ran the archiving there and then it worked.
After this I have been altering between two application servers and doing the archiving.

Best regards,

Johan

[alexander_teslyuk]

Hi Johan,

It is a good approach.

The System Rule stiings above show 365 days isntead of 480.

Anyway, I would suggest trying to switch the archiving from the script to the background job and back 1 time. Is a new value (decreased) taken after this?

Br, Alex.

[Former Member]

Hi Alex,

I noticed now that the information in my post did not show this very good.
In the Text box for Archiving days in my system it was the value 480 overriding the default 365.

I did not get the switching between background and command file to work.

Best regards,

Johan