Add a New row to enter data for a New Product or a Customer - Using Groovy Part 2

 In the Part -1  we saw how to add a new row for a New Product or a Customer using the Calculation Manager rule. In this post, we will see how to do the same using the Groovy rule. 

This is the data from where add a row option is enabled,

Column A is hidden and the rest of the column will be visible.

The actual form is shown below, 

Add a New row to enter data for a New Product or a Customer - Part 1

 In this blog, let's discuss how to address the requirements of entering data into a New Product or a Customer in a Data From exists in the PBCS or EPBCS application where the Suppress missing data for Rows or Suppress Missing data for Columns are enabled. Or the data does not exist for that combination but the users want a provision to enter the data for that specific combination. 

During the Budget or the Forecast, the users might want to enter data for a combination that never had any historical data. 

It is a general best practice the Data Forms will be enabled with the following,

• Suppress missing data - Rows
• Suppress missing data - Columns

Leveraging & Introduction to Oracle OCI for Oracle EPM suite components - Part 2

Continuation of my Part-1 post

Kubernetes, also known as K8s, is an open-source container orchestration platform that automates the deployment, scaling, and management of containerized applications. It provides a robust framework for managing clusters of containers across multiple hosts, allowing organizations to efficiently run and scale their applications.

Leveraging & Introduction to Oracle OCI for Oracle EPM suite components - Part 1

In this blog series i am going to talk about my fun project which is leveraging Oracle OCI to connect to Oracle EPM and invoke EPM components to perform multiple compute/analytical operation using the REST API.

Before that we see a brief introduction to Oracle OCI.

Introduction to Oracle OCI

Global Infrastructure:

 Example: An e-commerce company wants to expand its operations to the Asia Pacific region. Oracle OCI offers multiple data centers strategically located in countries like Singapore, Australia, and Japan. The company can choose to deploy its application in the Singapore data center to serve customers in that region. By doing so, they can take advantage of the low-latency network connectivity between the data center and the end-users, resulting in faster response times and an improved user experience.

Compute Services:

Example: A software development company is working on a project that requires high-performance computing capabilities. They can utilize OCI's compute services, such as the VM.Standard.E3 shape, which provides a high CPU-to-memory ratio. This instance shape is suitable for CPU-intensive workloads, such as scientific simulations, rendering, or machine learning. By leveraging this shape, the company can allocate more computing power to their application and achieve faster processing times.

Networking:

Restoring the Out of Box artifacts for the EPBCS modules!

It happened that some of the module-based artifacts were missing/accidentally deleted and we were finding a way to restore them.

As a user of Oracle Enterprise Performance Budgeting and Planning Cloud Service (EPBCS), you may want to restore the out-of-box artifacts that were delivered with your EPBCS instance.

In this blog, we will see how to systematically restore artifacts related to the EPBCS module's process of restoring the out-of-box artifacts for the EPBCS modules.

EPBCS Groovy Rule series-2, One rule for multiple Data forms do the calculation!

In this second part of the blog, let's explore how to reuse the same Calculation Manager Groovy rule by attaching the rule to multiple data forms to perform different actions in each data form.

The Groovy Calculation Manager rule is dynamic, it gets the account member from the data form, and depending on the selected account member the rule will perform a specific calculation. 

We can use the same rule and attach it to multiple Data forms. 

Let's see how the rule looks,

// Capture the edited periods and products
Set<String> editedMembers = []
operation.grid.dataCellIterator({DataCell cell -> cell.edited}, MemberNameType.ESSBASE_NAME).each { DataCell cell ->
        //editedMembers << cell.periodName << cell.getMemberName("Product")
        editedMembers << cell.periodName << cell.getMemberName("Years") << cell.getMemberName("Product") << cell.getMemberName("Customer")
    }
if(editedMembers.size() == 0){
    println("No edited cells found!")
    return;

EPBCS Groovy Rule series-1, Focused calculation based on the selected account!

This blog post will demonstrate how to carry out a targeted calculation using the accounts you've chosen from the Data Form's Page.

Product and Customers on the Rows, on the Data Form.

The Data Form allows for the selection of a single account from a group of accounts in order to perform the calculation. A specific calculation will be performed depending on the account chosen by the members on the POV and on the Page of the Data from the rule related to the Data Form.

Really neat and effective, huh?

Let's look at the Calculation rule that makes this possible.