Skip to Content

Daylight Savings Time 2014

As a reminder, we’ve been keeping track of any Daylight Savings Time-related knowledge under this blog post from Joshua Kuhn.  Please visit that blog for a thorough review of DST as it pertains to SAP BI products.

I’d like to highlight one addendum to that post, one potential issue that could affect users of both Enterprise XI 3.1 and Business Intelligence Platform 4.0 / 4.1.  Full details are available under Knowledge Base Article 1986781, but here is a quick summary:

When recurring instances have a run time within the 1 hour period that is skipped over in Daylight Savings Time — for example, between {2-2:59am on March 9 in the US} or {1-1:59am on March 30 in the UK} — their run times are moved up by one hour, by design.  Their run times should then be reset to the original value in subsequent runs, but this does not appear to always be the case.

For example, in the US:

– A daily instance runs at 2:30am

– On March 9, that instance will be run at 3:30am

– On March 10, that instance should run at 2:30am again, but in some cases it may not

– The same can be seen in weekly, monthly, and hourly instances (where they run every 2 or more hours apart)

Affected instances can simply be re-scheduled, and this can be done en masse with an application where needed.  Full details are available in Knowledge Base Article 1986781.

This behavior has been seen in:

SAP BusinessObjects Enterprise XI 3.1, Fix Pack 6.3

SAP Business Intelligence Platform 4.0, Support Package 08

SAP Business Intelligence Platform 4.1, Support Package 02

You must be Logged on to comment or reply to a post.
  • We run BI 4.1 SP3 Patch 5.  Searching for related Bi 4.1 DST 2015 detail on SCN and SAP Notes, but nothing exists.  We assume that similar issue will be experience this March to what we saw in March 2014.

    SAP Note #1986781 has a reference to BI 4.1.

    No reference located in BI 4.0/4.1 Product Fix site.

    Anyone have further detail on when or if this will be patched in BI 4.1?

    • Hi Monte,

      I'm sorry to say there will not be a code fix for the issue within current versions of the product, as it'd be a major fix for a minor issue.  Workaround is documented under that KBA, and please feel free to let me know if I can assist with that.