- Oracle has moved the Essbase development work out of EPM and into the Oracle Database development team. Essbase will remain an OLAP database rather than relational – Oracle just shuffled some deck chairs.
- When EPM 11.2 comes out, Essbase will initially remain 188.8.131.52 technology under the covers: we won’t be getting the new Sandbox features introduced with Essbase 12 in on-premises OBI12 / cloud OAC.
- On-premises CapEx, Workforce and Project planning modules will be deprecated and not available in EPM 11.2. (We knew for some time that Project Planning will be going away; nobody seems to use it). But losing CapEx and Workforce was a bit of a shock. This means those cubes would need to be re-implemented as custom cubes in 11.2 Planning; no more pre-built content for them.
- Disclosure Management, Interactive Reporting, WebAnalysis (deprecated when 184.108.40.206.900 came out), and SQR Reporting are also sunset and will not be available post-220.127.116.11.0/18.104.22.168.7xx.
- It is clear Oracle wants to push CapEx, Workforce and HSF customers to the cloud.
- At some point, we’re not sure when, EPMA will be gone in 11.2 and will be replaced by a limited-use version of Enterprise DRM. This DRM will be bundled with 11.2. This is a complete reversal from previous Safe Harbor statements made by Oracle
- Out-of-place / lift-and-shift migration from 22.214.171.124 to 11.2 will apparently be certified. Some kind of migration tool will be provided for this.
- OAC will no longer have Essbase bundled with it, effective immediately for all new customer-managed OAC implementations. Essbase “12c” will have to be installed separately as a standalone instance, and then Essbase cubes would need to be migrated from the old Essbase instance into a new standalone Essbase 12c instance. The jury is out on this. Unsure if Oracle will soften their position and bend to the collective will of their customers.
- A new Essbase, Essbase 19c, is under development for 11.2. It is expected to come out sometime next year. Essbase 19c will be for on-premises only. So the confusion: 126.96.36.199 Essbase is for 11.2 in the short term and also EPM Cloud. Customer-managed OAC will remain on Essbase 12. Oracle-managed OAC might eventually get Essbase 19c.
- 188.8.131.52 on-premises Essbase patch development has apparently stopped and will not continue. This makes no sense as there are still unsolved bugs lingering out there, and EPM Cloud uses 184.108.40.206 technology behind the scenes. No word yet if EPM Cloud will be bumped up to 11.2. My gut feeling is EPM Cloud will get 11.2 first, as the cloud’s servers run Linux. Plan on opening SRs galore if Oracle plans on doing this within the first 6 months of 11.2’s release. They’ve pushed out 11.2’s release multiple times now, so they must be fighting bugs.
Dedicated to Oracle EPM (Hyperion) on-premises infrastructure topics, such as upgrading, patching and troubleshooting.
Sunday, July 7, 2019
KScope 2019 - Candid Thoughts
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!
The way 19c was explained to me by folks from Oracle is as follows: 19c is the most current code line for Essbase. It will be released in the Cloud sometime later this year (hopefully September). 19c would then be released for on-prem approximately three months later. Future releases of Essbase should be expected every year and will follow the same pattern. So 20c would be released in the cloud at some point in 2020 and would be released to on-prem three months later.ReplyDelete
Tim, good comment! The documentation I was given tells a different story, but I will wait to see what actually happens. I hope the scenario you described actually plays out. The Essbase community would be better served by a single version of Essbase being maintained, vs. 3 different versions.ReplyDelete
Correction: The Oracle release 11.2 slides specifically say Windows deployment will be first release, and Linux will follow in a PSU.ReplyDelete
I will make this correction. Thanks!Delete
Any comments on customers with Workforce planning in use in 220.127.116.11, will we get some migration path to move all Artifacts/Metadata/Data to 11.2 ?
Hi Azmat, Oracle has not revealed any details in the meetings I've attended. I attended a webcast yesterday and Oracle said "most people customize their WrkForce and CapEx cubes anyway". In theory, it out to be possible to LCM migrate everything. The LCM artifacts may need to be edited to replace "Wrkforce" with Plan2 or Plan3. The trick is whether or not their are Custom Defined Functions in Essbase that might not migrate. This smells like it would become a small development project to figure out how to bring it into 11.2.Delete
Thanks Dave....hope Oracle can come up with a good strategy for migration from 18.104.22.168 to 11.2ReplyDelete
Hello, if Workforce Planning is not supported on 11.2, What about PSPB (Public Sector Planning & Budgeting) applications? is it going to be supported in 11.2 version? Also, what are the alternatives to CAPEX and PFP modules?ReplyDelete