As an update to CheckPoint’s Blog on May 10th on the subject of Oracle’s EPM 220.127.116.11.900 release, we are posting our latest findings. The testing, and subsequent results are from our lab environment using simple test applications. The results may or may not be indicative of what we would expect to find in a “real-world” example. Your mileage may vary!
Oracle quietly released a new installer for 18.104.22.168.x labeled 22.214.171.124.900 May 1st on edelivery. I’ve not seen any announcements from Oracle about it and it was not included in the “EPM Patch Set Updates - April 2018” blog announcement which came out on 5/4/18.
Oracle Data Integrator (ODI) offers many benefits to users extracting, loading, and transforming data in their data intelligence systems. It offers a practical GUI to the user so that they can effectively manage this data. A small setback, however, appears during troubleshooting: mismatched timestamps.
Financial Management server clusters are an efficient way to push specific job types (such as consolidations or reports) to servers best suited to handle them. Clusters can also be used to separate user groups, like standard users and administrators. An issue arises when HFM clusters are mixed with task flows.
A key functionality of HFM allows several consolidations, data loads, extracts, emails, etc. to be scheduled and automated via a highly customizable operation called a task flow. These task flows allow for jobs to be completed without manual input between each step which can be a serious time saver, but they also present the opportunity for unforeseen HFM failures which can set you back further than if you simply did it manually.
A challenge that is commonly overlooked when upgrading EPM is keeping your upgraded application in sync with your Legacy application after the initial upgrade, prior to go-live. The challenge comes from the requirement to continue day-to-day operations in the Legacy environment during the upgrade project time line. At some point, the Legacy application must be "upgraded." The upgraded application then becomes a snapshot, or a "Point in Time" of the Legacy application; any changes made in the Legacy environment beyond that point must be accounted for in some form or fashion in the new, or upgraded environment and application.
Happy New Year – 2018!
Over the years we have featured numerous posts on technical how-tos, tips & tricks and insights from our consultants out in the field. Going into 2018 we are looking forward to expanding on our topics and will include more business-process articles, client successes, event presentations and more! And in case you missed some of these, we thought you might like to see what the most popular technical posts have been to date:
With the latest Oracle Cloud Updates the EPM Automate utility now supports proxy authentication. The EPM Automate utility is the tool used for automating many of the maintenance activities in the EPM cloud. With the 17.10 Oracle Cloud updates released in October the utility has been updated to allow for additional login functionality that support Internet Proxies which require authentication. For more information administrators should check out the latest documentation available from Oracle. New login command information for EPM Automate can be found here EPM Automate Login Commands.
A frequent issue With FDMEE processing is the time it takes to load data into a target system. One issue that significantly slows FDMEE processing is the use of LIKE mapping. If the number of LIKE Mappings gets large then the response time can be overly burdensome and may lead the user to wonder if there is an issue and the system has stopped processing.