My Oracle Support Banner

Enforcing Case Sensitivity of Hierarchy Nodes in DRM (Doc ID 1983891.1)

Last updated on MARCH 08, 2017

Applies to:

Hyperion Data Relationship Management - Version and later
Information in this document applies to any platform.


You have a requirement to enforce case sensitivity of hierarchy nodes (members) that are stored and managed in DRM so you would like to be able to create nodes named node_a as well as a node named node_A.

The only problem is that DRM has been designed from the ground up to not be case sensitive as many customers do not want to deal with case sensitivity in their financial reports. A result of this is that if you add a node named node_a and then subsequently try to add another node named node_A you will get an error like this if shared nodes are not enabled due to a name collision:

Node node_A already exists in hierarchy Hier for version Ver.

Multiple instances of a node are not enabled for this hierarchy.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.