Automating Multiple Data Push in Oracle Cloud EPM Using Groovy Business Rules!

In Oracle Cloud EPM, Groovy scripting has become a powerful tool for automating business processes, ensuring real-time validations, and enhancing interactivity. This blog explores a practical use case where a Groovy business rule dynamically sets substitution variables and validates Data Maps before executing Smart Push operations.

The rule also demonstrates on using runtime prompts (RTPs) to set values for Substitution Variables, validate Data Map existence, execute Smart Pushes for specific members, and log user execution details.

The objective of the Groovy script is as follows:

1. Dynamically retrieve runtime prompt (RTP) values provided by the user.
2. Update substitution variables with the RTP values for Snapshot Version, Years, and Source Version.
3. Validate the existence of specific Data Maps in the application before executing them.
4. Use Smart Push to transfer data for a specific members.
5. Log execution details, including confirmation messages and the user who executed the rule.

Script Initialization: Capturing Runtime Prompts

At the top of the script, the Runtime Prompts (RTPs) are captured and converted to strings for use in the script.

• rtps: The rtps object holds the values passed into the rule during execution.
• toString(): Ensures that RTP values are treated as strings, even if numeric.

This section makes the script dynamic and user-driven. 

Setting Substitution Variables

The script updates substitution variables (Version, Years, Version) dynamically in the application. Substitution variables allow for flexible data calculations and reporting based on these values.

setSubstitutionVariableValue(): This method updates the value of substitution variables in the application dynamically.

1. hasDataMap(): Checks whether the specified Data Map exists in the application.
2. getDataMap(): Retrieves the Data Map object for execution.
3. createSmartPush(): Creates a Smart Push object that will transfer data.
4. execute(): Executes the Smart Push operation.
• The parameters are:
• "Years": Uses the Years RTP value.
• "Version": Uses the Version RTP value.

• The execute flag indicates the Smart Push will run synchronously (wait for completion before continuing).

If the Data Map exists, the Smart Push is executed, and a confirmation message is logged. If not, the script logs an error message.

Executing a Second Data Map

The same approach is repeated for another Data Map 2

1. Dynamic Execution: Users can pass values via RTPs, making the script highly adaptable.
2. Error Handling: Validating Data Maps before execution prevents runtime failures.
3. Efficiency: Using Smart Push ensures that only relevant data for specific periods is pushed, reducing processing time.
4. Auditability: Logging user details and execution messages enhances transparency and traceability.

This rule will run one Smart push waits for its completion then triggers the other one. 

The complete Rule is here.

With Groovy's flexibility and power, we can automate complex workflows, ensuring that financial planning processes remain efficient and user-friendly.

Happy Grooving!!!!