Skip to Content

Archiving Days Before Archiving issue

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

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    Posted on Dec 01, 2014 at 09:38 AM

    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

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Nov 28, 2014 at 06:10 PM

    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.

    Add a comment
    10|10000 characters needed characters exceeded

    • 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

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.