Keeping up with EPM Cloud

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...

Custom calculation scripts contain sections of code which can then be referenced several times within a Business Rule, or in multiple different Business Rules. They are created within Calculation Manager, in much the same way as Business Rules, and are listed below the relevant PBCS Plan Type, under the ‘Scripts’ heading, as below: Custom scripts are useful for times when a certain section of code is repeated throughout a Business Rule, or is contained in multiple Business Rules. Using scripts in this situation means that if the script needs to be altered, it only needs to be updated in one place, rather than having to be updated in multiple locations or Business Rules. This saves time and ensures all your Business Rules which contain this section of code are consistent. The syntax used to reference a script from within a Business Rule is: %Script(name:=" ScriptName ",application:=" AppName ",plantype:=" PlanType ") Where:   ScriptName...