Unleash the Power: EDM to EPM Dimension Loads Just Got a Turbo Boost! (No More Shared Member Nightmares!)

For years, the dance between Oracle Enterprise Data Management (EDM) and Enterprise Performance Management (EPM) administrators has been a delicate, sometimes awkward, tango. The culprit? Shared members and the dreaded 'CLEAR' versus 'MERGE' dilemma during dimension loads. We've all been there: the fear of locking up stored members, the heart-stopping moment when a crucial member vanishes, and the constant headache of managing alternate hierarchies.

But hold onto your hats, folks, because Oracle has just dropped a game-changing feature that's about to revolutionize how we handle dimension loads. Buried in the March 2025 EPM release notes (yes, you might have missed it!), lies a gem: the 'Clear Shared Members' option in metadata import files. (See the official docs here: https://docs.oracle.com/en/cloud/saas/readiness/epm/2025/epm-mar25/25mar-epm-wn-f37479.htm)

Why This Matters (and Why You Should Be Excited):

Historically, 'CLEAR' was the necessary evil for dealing with shared member movements and alternate hierarchies. 'MERGE' simply couldn't handle the dynamic shifts, leading to duplicate shares and a messy outline. But 'CLEAR' came with its own set of risks:

• Locked Members: Stored members tied to forms and business rules? Ouch.
• Data Loss: Accidentally wiping out members and the data they held. Double ouch.
• The Shared Member Shuffle: Moving shared members was a recipe for chaos.

The Game Changer:

This new 'Clear Shared Members' option changes everything. It's like having a surgical tool instead of a sledgehammer. Now, you can:

• Precisely Target Shared Members: Clear only the shared instances, leaving your stored members and critical data untouched.
• Effortlessly Manage Alternate Hierarchies: Move shared members without creating duplicates or causing outline inconsistencies.
• Say Goodbye to Anxiety: No more sweating over locked members or accidental deletions.

Imagine: A world where EDM and EPM administrators collaborate seamlessly, where dimension loads are smooth and predictable, and where shared member management is a breeze. That's the power of this new feature.

This isn't just an incremental improvement; it's a paradigm shift. We can finally embrace the 'CLEAR' functionality without the fear of collateral damage.

What are your thoughts? Are you as excited as I am about this game-changing update? Let's discuss in the comments below!"

Ability to sort Requests based on columns in the Request view - DELIVERED

 Oracle EDM Idea Lab post - DELIVERED

 

Ability to sort Requests based on columns in the Request view

 

Description (Required): 

We would like the ability to sort Requests by the columns provided in the request view. 

 

Use Case and Business Need (Required):

The business would like to be able to sort on the requests that return from a request filter by the request Title and Description (and other available columns) to better allow the review of in process, in flight and completed requests.

 

 

 

Delivered: https://docs.oracle.com/en/cloud/saas/readiness/epm/2024/edm-dec24/24dec-edmcs-wn-f36314.htm

 

Sort Listing Pages By Selected Column

Several pages in the Enterprise Data Management user interface now support sorting displayed items by a selected column. The table content can be sorted in ascending or descending order. The following pages can be custom sorted by a particular column:

• Views
• Request Activity
• Applications
• Node Types
• Hierarchy Sets
• Node Sets
• Properties
• Lookup Sets

Business Benefit: Listing pages in Enterprise Data Management can be custom sorted by a selected column to find particular items of interest.

 

Allow Blank Download of Lookup / Legacy GL Viewpoints - DELIVERED

 Oracle EDM Idea Lab post - DELIVERED

 

Allow Blank Download of Lookup / Legacy GL Viewpoints

 

 

Description (Required):

 

Need the ability to download viewpoints that are based on Lookup or Legacy GL Node types.

 

Use Case and Business Need (Required):

For users to easily have a format for running a LOAD to a Lookup or Legacy GL node type, we would like to have the ability to download the viewpoint with no data, just the column headers.

 

 

Delivered: https://docs.oracle.com/en/cloud/saas/readiness/epm/2024/edm-dec24/24dec-edmcs-wn-f36295.htm

 

Download Viewpoint Column Headers Only to File

When downloading a viewpoint to a file, you have the option to download only column headers for the viewpoint rather than all nodes, property values, and relationships in the viewpoint. The resulting output file provides a template for loading data into the viewpoint from a file.

Business Benefit: Users who need to load data into a viewpoint from an external file can easily download a template providing the appropriate file format.

 

Need Extract Package to combine files without placing them in zipped folder - DELIVERED

Oracle EDM Idea Lab post - DELIVERED

Need Extract Package to combine files without placing them in zipped folder

 

 

Description (Required):

We need to combine 2 or more extracts into a single file. Not in a zipped folder.

 

Use Case and Business Need (Required):

To support related value sets for the GL, we need to combine multiple extracts into a single text file and place it the default UCM folder.

 

Enhancement Request / Service Request: 

Currently extract packages force the combined files into a zip file. This is not an acceptable load format for the related value set import within Fusion GL. We need the option to run the package with a combined file and NOT embed it in a zipped file.

 

 

Delivered: https://docs.oracle.com/en/cloud/saas/readiness/epm/2024/edm-dec24/24dec-edmcs-wn-f36301.htm

 

Extract Package Option to Output Individual Files to Global Connection

An extract package which extracts data to a global connection can write individual extract files to the connection target rather than having the files bundled within a zip file. This capability prevents the need to unzip the extract files after writing them to the global connection. The Zip Package option can be disabled in the extract package to output individual files when extracting to a global connection.

Business Benefit: An extract package consisting of many extracts can be run in a single operation and the data files produced by the package can be individually written to a global connection target such as Oracle Cloud ERP, Oracle Cloud EPM, or Oracle Object Storage.

 

Flag Policies that are invalid in the Policy Listing Report Download - DELIVERED

Oracle EDM Idea Lab post - DELIVERED

Flag Policies that are invalid in the Policy Listing Report Download

 

Description (Required):

We would like to have the Policy Listing report download updated to show a warning or indicator when a policy has become invalid due to users being removed from the groups assigned.

Use Case and Business Need (Required):

Currently this is only viewable when inspecting a single policy and is typically only identified once a policy has failed. If we can get this in the report, we can see if this were to occur in a single location verses having to inspect every policy.

 

Enhancement Request / Service Request: 

Update Policy report download to show same warning you see when inspecting an individual policy.

 

 

Delivered: https://docs.oracle.com/en/cloud/saas/readiness/epm/2024/edm-dec24/24dec-edmcs-wn-f36289.htm

 

Column in Policy Listing Report Download to Indicate Validity 

When downloading the Policy Listing report to a file, an additional column is included to identify whether each policy is valid or not. The Valid column provides a True value for valid policies and a False value for invalid policies. An invalid policy may have resulted from a deletion of an assigned user or group, or a metadata object which the policy depended on.

Business Benefit: The Valid column in the Policy Listing report download can be used to determine if there are any invalid policies which need to be modified or disabled to ensure proper request workflow behavior

 

More of my Idea Lab posts realized in EDM 24.03 release

Just wanted to share some of my Idea Lab posts for EDM that Oracle has made available in the 24.03 release. Please take a few minutes to see what Oracle has done and as always, remember to vote and comment on idea lab posts you like as Oracle is listening and responding to the community.

Allow for exclusion of archived objects when creating a template

Ask: We need the ability to exclude archived or draft objects when creating templates.

Use Case and Business Need: When migrating to production, we need to ensure there is no left over work in progress or "dead" objects that cannot be deleted but have been archived. These archived objects will not have been tested and cannot be migrated to production. They must be excluded from the template.

In addition, this feature would allow for the clean up of unwanted archived objects in lower environments as well. By exporting the template without the archived objects and the associated data via exports, the application can be archived and deleted. Then it can be re-created with the template and data exports where the old archived objects will no longer exist.

Oracle Delivered: EXCLUDE ARCHIVED OBJECTS DURING TEMPLATE IMPORT

When importing a template file, you can prevent archived objects in the template from being imported into a target Enterprise Data Management environment if the objects are not already present. An Exclude Archived Objects option is available for template preview and import to control whether archived objects in the template will be created in the target environment. For objects which are depend on an archived object, those dependent objects will also be excluded from the template import if they do not exist in the target environment. In cases where a dependent object would be partially excluded, the object will appear in the template preview and import with a warning message indicating it cannot be imported.

Business Benefit: Archived objects that were created for an application or dimension in a source environment but are not needed in a target environment can be excluded during a template import process to ensure those objects are not migrated.

Need multi-select option for subscription top node selection

Ask: When selecting Included Top Nodes on a subscription filter, we would like the option to be able to select multiple items at once from the hierarchy instead of one at a time.

Use Case and Business Need: The user experience is very clumsy when multiple top nodes have to be configured in a subscription filter. need the ability to display all top nodes defined.

Oracle Delivered: SELECT MULTIPLE TOP NODES FOR A VIEWPOINT SUBSCRIPTION FILTER

When defining an Included Top Nodes filter for a viewpoint subscription, multiple nodes can be selected at the same time rather than having to select each top node separately. In cases where several nodes need to be selected, this can significantly reduce the effort required to configure the filter for the subscription.

Business Benefit: For viewpoint subscriptions which are filtered using many top nodes, the ability to multi-select those top nodes provides an efficient way to configure the subscription filter.

Allow INSERT Orphans from Node Set to associated Hierarchy Set via UX (not request upload)

Ask: Need the ability to INSERT, using the UX node selector, an orphan node in the node set not in the hierarchy set.

Use Case and Business Need: When a node has become an orphan, the ADD function in the UX does not work as it returns the error: A node with the name '****' already exists in node type '****'.

If you select 'INSERT HERE' instead of ADD, the Select a Node prompt will not find the orphan member from the node set.

We would like to have the Node Selector have an option to select from orphan nodes to insert to the hierarchy set without having to create custom list views for every node set.

Oracle Delivered: QUERY ORPHAN NODES FOR HIERARCHY VIEWPOINTS

Viewpoint queries can be used to identify nodes of particular node types that have not been included in the hierarchy set for a viewpoint. An Orphan Nodes query scope is available to determine which nodes have been excluded and may potentially need to be inserted into the viewpoint. Additional filters can be specified for an orphan nodes query to reduce the results to particular orphans of interest. Nodes from orphan query results can be inserted into the hierarchy viewpoint using drag-and-drop or the node selector dialog when in the context of a request.

Business Benefit: Orphan node queries can be used to ensure nodes of specific node types are included in a hierarchy viewpoint for reconciliation purposes. They also provide a way to identify nodes which may have been indirectly removed from a hierarchy and need to be re-inserted for completeness reasons.

Oracle Idea Lab really does work!!

I wanted to share some recent idea lab posts I had made in the Oracle Cloud Customer connect ideas lab for EDM and show that getting these ideas into the forum, voted on and community comments provided really does help get new features and functionality for us to use.

 

First and foremost, I want to put out a big THANKS to the EDM product management and development teams for allowing us to provide this important input and even more important fact that you are listening and delivering.

 

In the recent test release of EDM (23.12) these ideas I had submitted came to life (note there are many others that the community submitted that also come to life).

 

·      Need to be able to evaluate (test) an expression in the Expression Build

o   Description

§  We need the ability to test out the results of an expression while still in the expression builder.

o   Use Case and Business Need

§  The process of writing an expression (formula) in EDM can be very complex and iterative. In the current user experience, it requires defining the expression, saving it, closing the object the expression is in (validation, property, NT converter, etc) then going to a view/viewpoint and trying it out. 

§  This cycle of setting up the expression, saving and testing it out can recycle as many as 2 dozen times (or more) before the expression is setup correctly.

§  If we had the ability to select a view/viewpoint and node to evaluate the expression against to see the result while still in the Expression Builder, this would make the process extremely efficient and ensure the expression is correct before actually saving it into EDM. 

 

 

·      Add Lineage to Transaction Audit report

o   Description

§  We would like to have the request lineage information available for download with the Transaction and Workflow audit reports.

o   Use Case and Business Need

§  Having the lineage in the downloads would allow the report to show how each of the transactions are associated via subscription. This is needed to be able to visualize the metadata movement within the application in EDM prior to publishing to the target ERP and EPM applications. 

 

·      Need to have audit filter that will include related requests

o   Description

§  Need to have audit filter that will include related requests.

o   Use Case and Business Need

§  As part of normal business we will filter specific requests in the audit using the given filters EDM has. Once we have the set of requests filtered down, we also need to see any request that is related to what has been filtered. 

§  Two use cases:

·      To see the specific requests that generated the items we have filtered to (up stream requests)

·      To see the specific requests that generated from the requests we have filtered (down stream requests)

 

 

·      Need to be able to run selected validation on a given viewpoint

o   Description

§  Need to be able to run a selected set of assigned validations on a given viewpoint. 

o   Use Case and Business Need

§  When running validations on a viewpoint we have different data stewards that are responsible for clearing different validations. We need a method to run a single or group of validations associated to a viewpoint so the results only show items for the selected validation(s) and not all.

 

·      Hide Tiles not used by 'Users'

o   Description

§  There are several tiles exposed to users that could be hidden when their access does not allow them to manage the related objects. 

o   Use Case and Business Need

§  For Non-Owner/Non-Data Manager users, the Applications, Node Types, Hierarchy Sets, Node Sets, Properties, Lookup Sets & Connections tiles should not be exposed.

§  For Data Managers the same applies with the exception of adding back the Applications tile.