Data Copy using DataGridBuilder in Groovy!

 

 

In this blog, we will see how to perform an intercompany data translation with ease,  

 

This rule ensures intercompany data is clean, aligned, and instantly processed when users save a form. It applies standard naming and business logic automatically—no manual cleanup needed. Data flows straight into the target  cube or POV, reducing cycle time and reconciliation effort. It improves auditability and consistency across entities, accounts, and products. The result? Faster closes, fewer errors, and more trust in your numbers

EPCM - Copy Data by Point of View operation via Groovy

If you’ve been working with Oracle EPM Cloud, particularly Profitability and Cost Management (PCM), you might need to copy data between different POVs (Point of View) in your application.

In Oracle's Enterprise Profitability and Cost Management (EPCM), efficiently managing data across different Points of View (POVs) is crucial for accurate financial analysis and reporting. A POV typically represents a specific combination of dimensions such as year, period, scenario, and version. Copying data from one POV to another allows organizations to replicate datasets across different scenarios or time periods, facilitating comparative analysis and forecasting. Oracle provides a REST API endpoint specifically designed for this purpose: the "Copy Data by Point of View" operation.

Running EPCM Calculation Manager rules in sequential and Data Management rules as a child job using Groovy!

In this blog we will see how to run the EPCM (Enterprise Performance Management Cloud)  Calculation Manager rules using groovy in a sequential manner also invoking Data Management rules as child jobs using the jobFactory.

Groovy script is fetching substitution variable values from an operation's application and printing them. Here's a detailed explanation along with the provided script: 

subVarValue is defined to fetch the value of a substitution variable from the application.

Also Sets the connection name, which is already predefined for the REST API to work. 

def connectionName = 'Localhost'

Closure subVarValue = { String subVar -> operation.application.getSubstitutionVariable(subVar).value }

String CurYr = subVarValue('CurYr')

String CurMth = subVarValue('CurMth')

println "The Rule is using the Sub Var Current Year : " +CurYr +" " + "Current Month : " +CurMth

Multiple Rules of Enterprise Profitability and Cost Management (EPCM) using Groovy in Sequential Manner!

In this blog we will see how to run multiple Rules of Enterprise Profitability and Cost Management (EPCM) using Groovy in Sequential and proceed with the next rule only after completion the previous rule.

 

/**************************************************************************************/

/*                  Run IC Calcs All Region                                                                     */

/*                  Creation Date       : 10th Apr 2024                                                  */

/*                  Version                   : 1.0                                                                    */

/*                  Modifications         :                                                                        */

/*       The Rule uses the Sub Var &CurMth, &CurYr.                                          */

/*  The Rule will be executing the following,                                                     */

/*       1. Clear for EMEA                                                                                          */

/*        2. Clear for APAC                                                                                         */

/*        3. Clear for Americas                                                                                   */

/*       4. Merge Slices                                                                                         */

/*       5. Run Ruleset Ranges:                                                                            */

/*                  Start   End                                                                                      */

/*                  1            999                                                                                   */

/**************************************************************************************/

connectionName is a variable that stores the name of the connection to the server. In this case, it's set to 'Localhost'. This variable is later used to specify which server to connect to when making HTTP requests. 

def connectionName = 'Localhost'

Closure subVarValue = { String subVar -> operation.application.getSubstitutionVariable(subVar).value }

String CurYr = subVarValue('CurYr')

String CurMth = subVarValue('CurMth')

println "The Rule is using the Sub Var Current Year : " +CurYr +" " + "Current Month : " +CurMth

Groovy Rules Calling Enterprise Profitability and Cost Management Rules using REST API!

Using the Groovy script we can invoke the following REST API provided by an Enterprise Profitability and Cost Management system.

• Calculate Model - Runs the calculation on a given point of view in a selected cube.
• Clear Data By Point of View - Clears the data for a given point of view in a selected cube.
• Copy Data by Point of View - Copies data from a source to a destination point of view in a selected cube.
• Delete Point of View - Deletes the data associated with a point of view from the calculation cube.
• Generate Model Documentation Report - Generates an Enterprise Profitability and Cost Management Model Documentation report. Any validation failures are written to file with file name provided in the parameters and can be accessed from Inbox/Outbox Explorer.
• Validate Model - Automates the calculation process for validating a model. Any validation failures are written to file with file name provided in the parameters and can be accessed from Inbox/Outbox Explorer.
• All this are asynchronous call, so use the job status URI to determine whether the operation is complete. For running all the above REST API Required Roles is Service Administrators.