Sunday, September 29, 2019

SOX and On-Premises EPM 11.1.2.4 and prior


Let's talk about one of our favorite subjects: Sarbanes-Oxley compliance combined with on-premises Oracle EPM / Hyperion.

Auditors and IT Risk Management departments tend to frown on running SOX-relevant financial applications on systems where a vendor's Extended Support has expired.  Plain English: no ongoing defect remediation via patches, and no new security vulnerability patches.

As I wrote in a prior post, this ship has already sailed for:
  • Oracle EPM 11.1.2.3 and prior versions
  • Microsoft Windows Server 2008 R2
  • Microsoft SQL Server 2008 (all Service Packs)
  • Java 6 and prior versions
  • JRockit 6
The next Extended Support expiration dates looming are:
  • Oracle EPM 11.1.2.4
  • Microsoft Windows Server 2012 R2
  • Microsoft SQL Server 2012 SP3
  • Java 7
Of the above, the first deadline we'll hit is December 2021, or December 2020, and that's for Oracle EPM / Hyperion 11.1.2.4.  ("Safe Harbor" - I do not speak on behalf of Oracle Corporation, and their dates may change).  Standard Support is set to expire Dec 2020, and Extended Support is set to expire Dec 2021.  Check your Oracle Support contract to see which option you're on.

What readers need to consider is their timeline to either upgrade to EPM 11.2 (once released), or migrate to the Oracle EPM Cloud.

December 2021 seems like a long time away, but let's again re-visit SOX.

Let's say your fiscal year aligns with the calendar year: Jan:Dec.  In this scenario, SOX-relevant applications only get 2 windows per year to complete upgrades and do a go-live cutover to a new system:  May and September.  Shoot for May, and use September as your fall-back position.  Going live during either your fiscal 1st Quarter or 4th Quarter will trigger a red flag in your SOX audit.

So keep these dates in mind and then start counting backward.  Don't wait until late in 2021 to either upgrade or move to the cloud.  By then most EPM consulting partners, such as the firm I work for, will likely be slammed trying to hit that Sept 2021 SOX deadline.  I'm reminded of when Microsoft revoked support for browsers older than IE11... we were insanely busy because many customers were still on EPM 11.1.2.1 or older, and IT Risk Management departments forced Finance to upgrade to remain compliant.

One final thought: I've recently been contacted by a competitor promising cheaper support rates than Oracle's.  I want to discourage people from considering this, unless you intend to completely retire Hyperion and switch to a different platform on or before Q3 2021.  A 3rd party partner/consultant will face legal problems if they are discovered installing patches or upgrades a former Oracle customer is no longer entitled to receive.

1 comment:

  1. Essbase 19 (12.2) on-premise is planned for 07/2020 (https://static.rainfocus.com/oracle/oow19/sess/1553766371547001MF6k/PF/CON4713-Essbase19c_RoadmapOnTheCloudV2_1568900288755001REfe.pdf)

    ReplyDelete

Thank you very much for your interest in this blog! I hope you're finding it helpful.

Please keep comments relevant to the topic in the post, as this blog is not a free-for-all substitute for Oracle Support or traditional consulting. If you have many questions unrelated to the specific topic at hand, consider contacting me on LinkedIn (https://www.linkedin.com/in/daveshay) so we may discuss the possibility of consulting.

Commenting on posts older than 90 days unfortunately goes into moderation, thanks to spammers who've been hitting this blog. Please have patience, and thanks for your understanding!

Comments including URLs linking back to gambling or other things unrelated to Oracle EPM will be deleted on sight. If you're an EPM consultant and are offering me constructive criticism or a tip, go ahead and DO link back to your blog or firm's website if you so desire.

Thanks again for reading!