The EPBCS REST API provides the option to export all the job details to csv files. This is more helpful for consultants who support the application or for service admins who would like to see the summary of failed jobs in a csv file. I wanted to give it a try and explore this feature. We…
We have to deal with long-running rules when dealing with larger datasets, especially when it comes to data aggregation, data maps, and so on. The idea is to provide business rule executors the option of receiving or not receiving an email notification regarding the status of a business rule. Oracle includes a dedicated REST API…
I’ve been wanting to check out the new MDX custom calculation capability, which allows us to write MDX calculations directly in ASO cubes. Although the Groovy documentation only provides an example of a constant value assignment, it is possible to write more complex MDX calculations. Before constructing the MDX formula, there are a few factors to keep in mind. Writing Inventory Calculation MDX Interdependent values are heavily used in inventory calculations. This may be accomplished in BSO by forcing the calc to run in Cell mode (@CalcMode(Cell)). Let’s look at how we can use Groovy to convert the BSO calculation below into MDX code. Setting up the POV Pov, Source RegionPov, Source Region, and Script are the three mandatory fields to be specified for any MDX calculations written in ASO cubes with the CustomCalcParameters class. As usual, crossjoin is used to fix multiple dimension members in the POV. Since we have Groovy, I…
The Groovy API provides a privileged function to update metadata properties using business rules. Since it’s a privileged function, only administrators are allowed to execute the same. Of late, I have been using the function to rename the members, change the parents, etc. This helps in many ways, as UDAs get a little better since…
This sounds more like controlling a specific product or entity read only from the planning unit hierarchy. This post is for those who don’t use planning unit hierarchy but use a webform to control whether planners are supposed to edit a certain product or entity during the planning cycle. Below is how groovy can help…
I am sure most of us are familiar with the conventional data export from Essbase using the DATAEXPORT option. However, we cannot perform a precondition to export only the required data. But this doesn’t allow us to perform a conditional check to see whether we are exporting valid data or not. In short, we cannot…
Although input at higher level intersections in ASO is not possible, the combination of groovy and EPM APIs helps us to achieve the same. Let us make use of instant aggregation in ASO along with groovy grids. Here is the link to the article I published on LinkedIn.- Click Here for full post.
For the existing grid spread functionality to work, a webform needs to meet certain conditions, such as the entire hierarchy of YearTotal (IDescendants) must be available on the form; otherwise, the natural spread doesn’t work. The ability to input at the YearTotal and hide the Q1..Q4, H1..H2 members from the form are general requests. The article was…