There is no doubt these are geared towards AI Agents, MCP Server and in general making it easy for AI apps to interact with Oracle EPM. This will be Part 1 of the series. I will be making videos as well.

With that lets get strated with the API to get the Dimension Details.

Latest EPM REST APIs

The below are the REST APIs I want to cover in my articles and vidoes.

• Get Plan Types

• Get Dimensions for a Plan Type

• Get Dimension Details

• Get Application Summary

• Export Data

• Export Form Data

We will start with Get Dimension Details API.

Get Dimension Details API

I am particularly excited about this one becuse we can get the dimension deails - the hierarchy, parent, children, alias in json format. I don't know about you, but I haven't been this excited about an EPM REST API in a looooong time!!

Ok Lets see how we use this.

API end Point: /HyperionPlanning/rest/v3/applications/{appName}/plantypes/{planType}/dimensions/{dimension}

You need to provide the following details

• Application Name

• Plan Type / Cube Name

• Dimension Name

REST API Response

Let's examine the REST API response.

• dimType: The type of dimension this is - Custom / Standard / Attribute

• dimName: Projects

• density: Sparse

• usedIn: the cubes in which the dimension is being used. This an extremely useful information.

Let's look at another screenshot where we take a closer look at the members of the dimension:

It shows you the following information:

• Hierarchy in a few different ways: using the Path, Alias Path, parentName, and id and parentId fields

• the member level

• the alias

• cubes in which the member is being used

• generation

• dataStorage

Conclusion

The new REST API allows us to get all the members and member information of a given dimension. And the best thing is the respose is in JSON format.

I am exicted to show you the other EPM REST APIs soon.

What are your thoughts about the new REST APIs? Let me know your thoughts.

Installing the Extension

The first step, obviously, is to install the extension. And it is pretty easy. Go to Extensions tab of VS Code and search for “Oracle SQL Developer Extension for VSCode” and install it.

Press enter or click to view image in full size

Create Connection

The next step is to create the connection to a DB. You can choose between various connection options. I will be showing how to use the Cloud Wallet option.

Press enter or click to view image in full size

Click on Create Connection and you will be prompted to provide the details as shown above.

Configure Connection Settings and Cloud Wallet

Confguring the connection setting is simple and straightforward. Here are the steps involved.

• Download the wallet from OCI console

• Change the Connection type to “Cloud Wallet”

• Click on “Choose File” and select the Wallet Zip file

• Select the Service (this will be available after you select the Wallet zip file)

Press enter or click to view image in full size

Make sure to alos provide the following:

• Connection Name

• Username

• Password

• Optionally choose to save password

Press enter or click to view image in full size

Click the “Test” button to make sure you are able to connect to your database. You should see a success message in the bottom right corner of VSCode.

Once connected you will notice the Database in the left panel.

Create a new SQL Worksheet

To the right of the connection name, you will notice few options. One of them is Open the SQL Worksheet and this is where you will write and execute your SQL statements.

Press enter or click to view image in full size

You can also use the keyword Ctrl + Shift + W to create a new SQL Worksheet.

SQL Worksheet Features

Autocomplete is enabled and available. When you start typing the object name, you will notice the objects with similar names available for easy selection. This definitely speeds up the development time.

Press enter or click to view image in full size

Once you execute the statement, you will notice the restults at the bottom (just like SQL Developer). Ctrl + Enter keyboard shortcut works to execute SQL statement.

Press enter or click to view image in full size

One of the best features I like is the SQL History tab. This allows you to view SQL statements executed previously. Double clicking on one of the history record will copy that statement to the editor.

Conclusion

Oralce has made is extremely easy for you to connect to your Oracle Cloud DBs. And as many of us uses VS Code, it is now even more easier to use the same editor with Oracle DB. You get to use the same Code Editor for all your programming needs.

Another day, another experiment with the Export Data Slice REST API. I have written about the Export Data Slice rest api earlier. Do read that for an explanation for the beginners. Here is a link to the previous article. Today I wanted to show you how you can visualize data in Jupyter Notebooks.

Export data slice can be used to export data for a specified region or intersection. The exported data will be in the form of a JSON grid with pov, columns, and 0 or more data rows.

Understanding the Data Structure

To export the data using the REST API, we need to understand the intersection where we have data. The below data form will you give you a better idea of the data we are looking to export using the API. We will be focusing on the Plan scenario numbers.

Press enter or click to view image in full size

Expense By Category Data Form in EPM

Grid Definition

We need to provide the grid definition as part of the JSON Payload. It will be easier to understand the grid definition by looking at the existing Form design. As you can see the POV (Point of View) has the following Dimensions and corresponding members:

• HSP_View: BaseData

• Version: Working

• Product: P_000

• Period: YearTotal

Press enter or click to view image in full size

POV Members in Form Definition

Now let’s look at the rows. You will notice we have two Dimensions.

• Entity: Descendants(TD)

• Account: 6000, Children(7001), 7300

Rows in the Form Definition

Finally, let’s check the column. We are going to look at the Plan scenario column. The column has two dimensions:

• Year: FY22

• Scenario: Plan

Columns in the Form Definition

JSON Payload

Based on the Form design, let’s now create the Grid Definition in the JSON Payload. I have broken down the Grid definition into three separate sections for easy explanation. Below is the Point of View.

• provide the dimensions

• provide the members

Press enter or click to view image in full size

Define Point of View in the JSON Payload

I have modified the POV to include HSP_View, Scenario, Year, Product and Version dimensions.

The below section is the columns definition. I am only providing the “Period” dimension.

Press enter or click to view image in full size

Column definition in JSON Payload

The rows section remains the same as the form design. We are providing the Entity and Account dimensions along with the values.

Press enter or click to view image in full size

Row Definition in JSON Payload

Oracle recommends specifying the Dimensions in the grid definition section of the JSON Payload for efficiency.

Jupyter Notebook

Let’s start coding. First things first, lets import the necessary Python libraries.

Press enter or click to view image in full size

Python Libraries

Let’s set the URL and the headers. Make sure to provide the correct URL. To read more about the end point, head over to the Oracle Documentation.

Press enter or click to view image in full size

URL and Headers

Let’s invoke the RESP API. Make sure to use the POST method. You have to pass the user name and password as well.

Press enter or click to view image in full size

Invoke REST API

Once you get the JSON response, you can create a Pandas Data Frame as shown below. There may be a better way of creating the data frame from the JSON response. I am converting the JSON response into a list.

Press enter or click to view image in full size

Create a Pandas Data Frame

The below code will create a bar chart based on the data frame.

Press enter or click to view image in full size

Create a bar Chart

And here is the final visualization created from the data exported from Oracle EPM Planning instance.

Press enter or click to view image in full size

Conclusion

As you can see it is pretty easy to export a data slice using REST API from Oracle EPM. The one draw back that I have seen with this approach is that the “alias” or “description” of the members are not exported.

I will further add data labels and possibly make the chart more interactive. Watch out for another post of Export Data Slice and Import Data Slice coming soon.

Let me know if you have questions on this. Share your comments and feedback. You can view the complete python code here.

There are some much needed updates to the out of the box planning modules; especially the integration between Projects and Capital Module, and Projects and Financials modules. A much needed feature on enabling custom dimensions is also coming as part of this update.

Account Reconciliation

Audit History for Match Types in Transaction Matching

As part of the October updates, there will be a new Transaction Matching tab in Audit page. The tab provides audit information for match types. You can find information about

• match processes

• match rules

• match rule conditions

• alert rules

• data sources

• and more!!

Groovy Engine Update

The Groovy engine will be update to a newer version as part of the December 2025 updates. As part of the August update, the Groovy Script Validator was made available to check your existing Groovy rules.

The new Groovy engine has stricter validation rules that may cause previously valid rules to fail validation. So make sure to test the Groovy Rules using the Groovy Script validator.

Check this link to read more about how to test the Groovy Scripts. Additionally, make sure to read the below articles by Patrick :

• Oracle EPM - Gettin' Groovy with the Upcoming Groovy Engine Update

• Oracle EPM - Gettin' Groovy with the Upcoming Groovy Engine Update Part 2

I would also recommend reading this Oracle Documentation that explains about Resolving Groovy Businesss Ruel Validation Issues.

REST APIs

I love the updates that are coming to REST APIs. More and more I see Oracle moving to using JSON for POST and GET requests. I hope majority of the REST APIs adop this approach rather than using a csv file for various operations. That is for another discussion.

As part of the October updates, there are a few new REST APIs being included. There will now be an opton to create and delete user variables using REST APIs. Here are the APIs that are being introduced:

APIs for User Variables

• Create User Variables

• Udpate User Variables

• Get All User Variables

• Get a User Variable Using Its ID (I am intrigued what this is!!)

• Delete One User Variable

• Delete User Variable Definitions (interested to know more about this one)

User and Role Management REST APIs

• Import User Group Assignments as CSV

• Update Application Roles for Groups

• Update Application Roles for Users

• Update Groups : I am imagining this to be a useful API. Imagine employees leaving organization or moving from one department to another. With this new API, you may be able to automate management of Groups. Let's see!!

• Update Users (v2): Similar to the previous API, this could also be useful tool. Imagine updates to your employee's name etc.

Data Integration

I dont know if you have noticed the Action Menu updates in Data Exchange. As of now, the Action Menu looks like this.

Maximize image

Edit image

Delete image

So, I am not sure what is changing in October 2025 updates. As per the update announcements, it reads that "Actions menu options on the Data Integration home page are now grouped in Setup and Configure action dropdowns."

De-support of Legacy Features

Starting with this October 2025, Oracle will de-supported the following legacy features:

• Forms 1.0

• Dashboard 1.0

• Legacy List Pages application setting

• Infolets

Make sure to read this in detail here. Few additional items to keep in mind:

• Effective October 2025, all environments will default to the 2.0 setting for Forms and Dashboards

• Existing environments will have the option to switch back to 1.0, however there will be no no support for 1.0

• All new environments deployed effective October (25.10) will be deployed with Forms 2.0 and Dashboard 2.0 only; the option to switch to Forms 1.0 will no longer be available.

EPM Planning Updates

Now comes the biggest set of updates. I was honestly surprised to see so many updates.

Predictive Cash Forecasting

Predictive Cash Forecasting now supports up to 100 forecast days in a daily rolling forecast. Previously, the number of forecast days was limited to 45. When you configure Predictive Cash Forecasting, in Forecast Range Setup, you can now select up to 100 in Number of Forecast Days.

Automated Seeding of Key Members in Planning Modules

When a custom dimension is enabled for multiple Planning modules, the Total<Member\> and No<Member\> members are now enabled for all modules where the dimension is enabled.

I think this is a good feature. Rather than us creating these members, these members will now be automatically enabled.

Support Business Expansion By Incrementally Enabling Custom Dimensions in Financials

At the moment, you have to enable all dimensions the first time you enabled features and could not incrementally enable additional custom dimensions later. This is changing as part of the October updates.

You can now incrementally enable custom dimensions in Financials. The new dimensions are available only in the OEP_FS cube even if you have other modules enabled.

Tips and Considerations for this:

• The new custom dimensions you enable are only available in OEP_FS cube

• In an existing application, if you have not previously enabled some of the custom dimensions, you now have the option to expand your business by incrementally enabling the custom dimensions, up to the total of 5 custom dimensions

• All out-of-box artifacts are updated for the newly enabled dimensions

Any additional custom artifacts you’ve added or modified are not updated for the newly enabled dimensions

I suggest you read this documentation. Oracle has provided recommendations to follow to avoid potential data loss when you incrementally enable additional custom dimensions.

Enhanced Projects Integration with Capital for Common Custom Dimensions

The integration between Projects and Capital is enhanced. Previously, if there was a common dimension in both Projects and Capital, such as Vendor, only aggregated values were pushed from Projects to Capital. Now, data for all members is pushed from Projects to Capital for common dimensions.

Tips And Considerations

• This enhancement is available only for new implementations, the first time you enable.

• If you’ve already enabled only Capital, but have not yet enabled Projects, this enhancement is available when you enable Projects

Enhanced Projects Integration with Financials for Common Custom Dimensions

The integration between Projects and Financials is enhanced. Previously, if there was a common dimension in both Projects and Financials, such as Cost Center, only aggregated values were pushed from Projects to Financials. Now, data for all members is pushed from Projects to Financials for common dimensions.

After enabling Financials and Projects, configuring Projects Financials Mapping, and creating a project and loading data, when you are ready to push data from Projects to Financials:

1. Run the Calculate Project or Calculate Expense rule.

2. Run the data map Project - FinStmt Reporting.

3. Run the Rollup rule in the Financials cube

This enhancement is available only for Projects modules that are enabled in 25.10 or later.

There are a few other enhancements coming to Planning modules.

Conclusion

There are a few noteable enhancements in Planning modules. And I like all of them. Make sure to read the documentation to understand what updates are coming to the EPM instances.

I have been creating articles and videos about Data Pipleine in Account Reconcliation. You can read those here:

• https://tinyurl.com/dyesrb5v or Creating your first data Pipeline in Oracle EPM Account Reconciliation

• https://tinyurl.com/28deez7v or Create Reconciliations in Oracle Account Reconciliation using Data Pipeline

• https://youtu.be/bVEEGnH1HPo

Are you attending Oracle AI World? If you would like to catch up and talk about any of the following, message me on Linkedin.

• Fusion ERP Reporting (OTBI, BIP)

• Fusion AI Agent Studio

• Oracle EPM Account Reconcliation

• Oracle EPM Narrative Reporting

• Oracle EPM Predictive Cash Forecasting

• Oracle EPM Data Pipeline

• Oracle ACE program

• or just to meet and grab a coffee

Lookout out for our podcast episode with Partrick . Coming soon!! If you would like to be part of the podcast, reach out to me.

Let me know what you think of these updates. What is your favorite one?

Last but not least, I would appreciate your support for the below Idea posted in Oracle Cloud Customer Connect Forums.

https://community.oracle.com/customerconnect/discussion/907871/show-job-types-based-on-the-local-or-remote-application-connected

That is it for this update. Look forward to hearing your thoughts!!

Let’s now explore how to create a pipeline that will create reconciliations in Account Reconciliation.

Reconciliation Creation Process Overview

Before we configure the pipeline to create the reconciliations, let’s review the general process to create a reconciliation from the profile.

• Navigate to Application > Profiles

• Actions > Create Reconciliations

• Select the Period

• Click on the Apply button

• Select whether you want to create the reconciliation for the selected profile or all the profiles based on the filters currently applied

• Click on the Apply Button

The key take away from this overview is that we create the reconciliations from the profiles.

Creating the Pipeline

Alright, let’s go ahead and create the pipeline. Navigate to Application > Data Exchange > Create Pipeline

Give the Pipeline Name and Pipeline Code

• Pipeline Name : create recon

• Pipeline Code : CREATERECON

Press enter or click to view image in full size

Click on Save and Continue

Let’s go ahead and define a variabe to provide the Period Name as a dynamic value.

• Variable Name: periodName

• Display Name: Period Name

• Display Sequence: 1

• Required: Yes

• Validation Type: Text

Make sure to delete any default variables that you are not planning to use.

Press enter or click to view image in full size

Let’s create a new stage. Provide the Stage Name and State Title as shown in the screenshot.

Press enter or click to view image in full size

Once you create the stage, go ahead and create a new job in the Stage. Provide the following information.

• Type: Create Reconciliations

• Tile: create recon

Press enter or click to view image in full size

You will notice that we need to provide values for “Period” and “Filter”.

For period, we will use the variable we defined (periodName). For Filter, we need to create a filter in the application. Let’s do that and then come back and edit the pipeline. Go ahead and click the “Save” button.

Creating a Filter

To select the filter in pipeline, we need to first create a filter. Follow the steps below:

• Navigate to Application > Configuration > Filters

• Create a new filter and provide a name

• Select the type as Profile

• Create new Condition

• Set the condition as shown below

• Once finished, click on OK button

The above condition filters the profiles based on the method and specifically looks at Profiles that has a method of “Balance Comparison”.

The next step is to publish the filter and make it public.

Press enter or click to view image in full size

That is it for creating the filters.

Complete the Data Pipeline Configuration

Let’s edit our data pipeline and profile the filter that we published.

• Edit the pipeline

• Navigate to the job

• Select the filter “BC Profiles” from the available list of filters

• Click on Save

Testing the Pipeline

Now that we have configured the pipeline, let’s go ahead and test the pipeline.

👉 Navigate to Data Exchange and run the pipeline

Provie the period name and other parameter values as necessary.

Click the “Run” button to execute the pipeline.

The pipeline has executed successfully.

Let’s check the reconciliations and make sure the reconciliations were created successfully.

Navigate to Recoconcliations and select the period as “Jun-24” and Method as “Balance Comparison”.

All the Balance Comparison reconciliations are created successfully for the period. Great job!!!

Conclusion and Next Steps

The pipeline allows you to create the reconciliations based on the filter. You can invoke the pipeline from another application like Planning or FCC.

📽️📽️ I will be making a video explaining the process as well. So make sure to subscribe to my YT channel.

If you like the articles and want to support me, you can join my YT channel as a member or Buy Me a Coffee 🍵.

Creating your Pipeline

Navigate to Application > Data Exchange

Press enter or click to view image in full size

Once you are in the Data Exchange page, click on Create New > Pipeline

Give the Pipeline Name and Pipeline Code

• Pipeline Name : Set Period Status

• Pipeline Code : SETPERIOD

Click on Save and Continue

Press enter or click to view image in full size

Let’s go ahead and define a variabe to provide the Period Name as a dynamic value.

• Variable Name: periodName

• Display Name: Period Name

• Display Sequence: 1

• Required: Yes

• Validation Type: Text

Make sure to delete any default variables that you are not planning to use.

Let’s create a new stage. Provide the Stage Name and State Title as shown in the screenshot.

Press enter or click to view image in full size

Once you create the stage, go ahead and create a new job in the Stage. Provide the following information.

• Type: Set Preiod Status

• Tile: Open Period

• Period: $periodName (this is the ariable defined earlier)

• Status: Open

We can also create another variable to provide the status dynamically. I will show that in the YouTube Video.

Press enter or click to view image in full size

Click on the Save button to save the Pipeline definition.

Before executing the pipeline, lets review the status of the periods. As you can see “Jan 2025” is in Pending Status.

Press enter or click to view image in full size

Navigate to Data Exchange and Click on the “Play / Run” icon to execute the Pipeline

Press enter or click to view image in full size

In the next screen, provide values to parameters. We will be setting the status of “Jan 2025” to Open. Pass the value “Jan 2025” to the Period Name variable.

Press enter or click to view image in full size

Click on “Run” button to execute the Pipeline.

After a few seconds, you will notice the status of the Pipeline show as Success.

Let;s go ahead and check the Period Status. Navigate to “Application > Periods”

Press enter or click to view image in full size

The period status has been set correctly. You can now invoke this Pipeline from EPM Automate or using REST APIs to automate this.

If you configured the Pipeline to receive emails, you will receive an email with the details of the pipeline execution.

Press enter or click to view image in full size

What’s Next

In the next article and video, I will show you how to invoke this Pipeline from Planning application. This is useful so that you can schedule the Pipeline in Planning so that this runs on a schedule. I will also cover how to invoke the pipeline from epm automate and using REST APIs.

Let me know if you have any questions on this. Make sure to subscribe to the articles and my YouTube Channel for updated content.

While Pipeline was introduced way back (its been that looong that I dont event remeber when), it was never available in Account Reconciliation. It was a long wait. However, as part of the August 2025 updates, Pipeline was introduced in Account Reconciliation.

In the next few articles, I will cover data pipeline specifically for Oracle EPM Account Reconciliation. In the first article, we will look at what job types are available as of September 2025. Without any further delay, let’s look into what is available for Account Reconciliation.

Pipeline jobs in Oracle Account Reconciliation

Here is a quick look at what job types are available as of September 2025. Some jobs are specific to either the Reconciliation Compliance module or the Transaction Matching module.

Press enter or click to view image in full size

You can read more about these jobs here.

Invoking the Pipeline

You have a few different ways to invoke a data pipeline.

• Manually exeucting the pipeline

• Scheduling the pipeline using the Job Scheduler

• Using EPM Automate

• Using REST API

Use the runPipeline command to execute or invoke the Data Pipeline using EPM Atuomate. You can read more about it here.

If you want to use REST API, use the Data Integration REST API to invoke the pipeline. Here is a sample code snippet.

{
    "jobName": "DAILYLOAD",
    "jobType": "pipeline",
    "variables": {
                    "STARTPERIOD": "Jan-23",
                    "ENDPERIOD": "Jan-23",
                    "IMPORTMODE": "Replace",
                    "EXPORTMODE": "Merge",
                    "ATTACH_LOGS": "N",
                    "SEND_MAIL": "ALWAYS",
                    "SEND_TO": "user@company.com"
                }
}

• jobName is Short name of the Pipeline

• jobType should be pipeline

You can read more about the REST API usage here.

What’s Next

In the next few articles, I will dive deeper into individual job types and how you can configure them. I will also be making accompanying videos so can follow along.

You can also read this article on Linkedin.

Integrations

Smart Split Data Load

A new Smart Split feature is available in Data Integration when importing a large volume of data that exceeds Essbase governor limits. This feature enables you to split a data load into multiple smaller loads by enabling you to define smaller data slices without having to create multiple integrations.

Steps to use the Smart Split feature:

1. create a base integration definition with the data to be loaded from the source application

2. Create a pipeline and use the new Integration with Smart Split job type in the Pipeline

3. Specify the integration name, Split dimension, Import and Export modes, Start and End periods, and Split method

Here is an example of how it would look like. Pay key attention to the additional parameters: Split Dimension, Split Method, Number of Groups etc.

Image Courtsey : Oracle

I will be creating a separate detailed blog and video about this feature in the coming days. Increasingly, Oracle is pushing new features in Pipeline. If you are not yet utilizing Pipeline, please do. If you organization is looking to learn more, please free to connect with me.

New Application Role - Data Integration - Administrator

The Data Integration - Administrator application role can now be assigned to any user, regardless of their predefined role. Users with this role are able to:

• Create and manage integrations between source and target systems

• Execute and monitor pipeline activities

• Perform data and metadata extraction and transformation from on-premises sources using the EPM Integration Agent

FCC (Financial Consolidation and Close)

Here are the updates that are coming to FCC instance. It is great to see the option to add additional BSO Cubes and the support for IPM insights.

Ability to Create Additional Block Storage Cubes

You can now create four additional block storage cubes to store metadata and data. The cubes can be enabled by the Service Administrator on an as-needed basis. Note that when a cube is enabled, it cannot be disabled.

This feature is only for Dense/Sparse Optimized (DSO) applications.

This feature is only available on a restricted basis. Adding additional cubes results in more maintenance required for the application, so it is recommended only for specific use cases. To enable this feature, you must submit a technical Service Request (SR).

Support for IPM Insights

Financial Consolidation and Close now supports IPM Insights. To get started with IPM Insights, administrators configure insights and then run them. They can also schedule them to run on a regular basis. Users can then review and analyze insights on the Insights dashboard, and take appropriate action to improve the close process.

Considerations

• IPM Insights requires an EPM Enterprise Cloud service subscription.

• IPM Insights works with applications with Hybrid Essbase enabled.

• IPM Insights only works with Dense/Sparse Optimized (DSO) applications.

Consolidation Job Analytics

It was intersting to see this one. I will have to see this in action to understand how useful of a feature this is.

A new Consolidation Setting called “Consolidation Job Analytics” is available. When this setting is enabled, a GenAI-based job summary will be generated for Consolidation jobs when the jobs have completed. You can view the analytics from the Job Details for the completed jobs in the Jobs console.

To use this setting, you must also enable the GenAI option application setting. From the Home page, click Application > Settings > Enable AI section > Generative AI.

Account Reconciliation

Bank Text Column Increased to 1200 Characters

When loading transactions using BAI Format Bank files, the Bank Text can now be up to 1200 characters long. Three new columns, Bank Text2, Bank Text3, and Bank Text4, are added.

If the Bank Text exceeds 300 characters, one or more of these new columns are used to store the Bank Text.

REST APIs

There are a few new REST APIs that will be introduced as part of the July updates. And enhancements to existing REST APIs.

REST APIs for Managing Users and Groups

• List Users : generates a list of available users in the environment. This API identifies the userlogin, firstname, lastname, and email. Additionally, it can provide information about the EPM groups the users belong to and the application roles assigned to the users.

• List Groups : generates a list of available groups in the environment. The API identifies the group name, description, type, and identity. Additionally, it can provide information about the groups/user members belonging to the groups and the application roles assigned to the groups.

• User Login Report : generates a report for all the users logged into the environment. The report can be created for a specific user login and/or within a valid date range.

I am hoping we get JSON data back while using these REST APIs. I will be trying this out.

Get Available Roles REST API

The optional type query parameter has been added to the Get Available Roles REST API. This parameter can take the following values:

• application: returns all application and predefined roles. This is the default.

• predefined: returns predefined roles only

Enhancements to Role Assignment Report REST API

The Role Assignment Report Synchronous API has been enhanced to search for users across all user attributes (userlogin, firstname, lastname*,* and email). Previously, this API limited the search to the userlogin attribute.

Enhancements to the User Group Report REST API

The User Group Report synchronous API, which lists the direct or indirect membership of users assigned to groups, has been enhanced to search for users across all user attributes (userlogin, firstname, lastname*,* and email). Previously, this API limited the search to the userlogin attribute.

Those are major updates. There is a new version of SmartView, so make sure to update your SmartView.

What is your favorite feature form July updates? I am hoping to see more Gen AI and Pipeline features coming soon. Additionally, I am looking forward to seeing Advanced Prediction capabilities and Operational Modeling coming to EPM.

Here is a quick tip to all Oracle EPM consultants. Start learning Oracle Apex. I know it is one more new item to our ever growing list. However, you start learning now and you will thank me later. :)