Keeping up with EPM Cloud

We landed on a sunny Friday afternoon, after a long but thankfully smooth trip over from London, to a heat like no other under the Texas sun. By the time we had a look around the Texas sized Gaylord Hotel, it was time to relax and get ready for the week ahead. Saturday was our only free day, so we used it wisely by heading over to the Fort Worth Stockyards. This national historic district is an immersive experience of western traditions and even has a twice daily long horn cattle drive. Later in the day we visited the Original Roy Hutchins BBQ joint and shared a BBQ feast of ribs, burnt ends and of course the famous Texas Twinkie!   The conference kicked off on Sunday with the EPM Symposiums, led by the Oracle Product Management team. The theme was ‘AI everywhere’, indicating how Oracle are working on introducing AI components into each of the EPM applications. On Monday, Brovanture’s own Sarah Dow hosted an expert panel on all things Oracle Cloud EPM Financial Close, along wit...

Recently, while implementing Oracle Planning Cloud for a new client, we experienced an issue where attribute dimensions were not being deployed successfully to the underlying Essbase cube – which was definitely not ideal! As we had never experienced this issue before, we opened an SR with Oracle, and (long story short) the issue was occurring because we had unknowingly used a restricted word as a member name and also had trailing spaces in a couple of aliases. Once we removed the restricted member names/aliases, the attribute dimensions were successfully deployed during the refresh. Unfortunately, these restricted members do not show as an error when refreshing the database, even if used in the outline, so hopefully this is something Oracle can add either as an error or as a warning on the Activity Report. In the meantime, it’s worth double checking the naming restrictions, especially if you seem to be experiencing some strange behaviour with Essbase. Some of the main restrictio...

For this blog we will be covering a common use case of exporting data from an EPM application to a file, for upload to a third-party system. While it is possible to export data from EPM Planning using the “Data Export to File” functionality in Data Integration, the formatting options available are quite limited and typically would require some manual file manipulation before it can be uploaded. This is where groovy comes in! In fact, to get the best of both worlds, we will be using a combination of both Data Integration AND groovy scripting , to produce a highly customised file format. This allows us to utilise the powerful mapping capabilities of Data Integration, as well as the file manipulation of groovy rules. Step 1 – Export to File in Data Integration For the first step, we will use the built in functionality to export data to a file. For details of how to do this, please refer to my previous blog here: https://lydia-maksoud-epm.blogspot.com/2025/01/exporting-epm-plan...