Oracle Hyperion EPM Architect can import hierarchies, nodes, and properties directly from Oracle Hyperion Data Relationship Management for use by EPM applications. The dimensions imported into Performance Management Architect can then be shared with and deployed to these EPM application types:

An application template is loaded into a source Data Relationship Management application to auto-configure it for managing and exporting dimensions for Oracle Hyperion EPM Architect. The application template may be optionally customized to support the specific business requirements of different organizations.

For more information, see the Oracle Hyperion Data Relationship Management EPM Architect Integration Guide.

Data Creator, Data Manager, and Application Administrator role users can utilize variables to refer to versions in a Data Relationship Management application. Version variables may be used to dynamically refer to different versions over time or provide an easy method of selecting a version from a large list of versions. Version variables can be saved with user metadata objects such as queries, compares, imports, blenders, and exports. In all areas of Data Relationship Management, a version variable may be used in the same manner as a version name. The previously available DefaultCurrentVersion and DefaultPreviousVersion system preferences are now accessible as version variables.

Data Manager role users can archive or migrate data from one Data Relationship Management application to another using version backup and restore. You can include one or more versions in a binary backup file that is written to an external connection defined by an administrator. The backup file may be later restored into the same or a different application. The Batch Client also supports version backup and restore for automation purposes.

Application Administrators can create hierarchy group properties to enable users to group hierarchies in multiple ways based on different contexts. A hierarchy can be assigned to different groups for different properties but can only be associated to a single group per property. The Hierarchy Tree toolbar has a new drop-down list called Group By for selecting a hierarchy group property. Only the hierarchy group properties that the user has access to are available in the Group By drop-down list.

Domains are available to preserve integrity and ensure consistency of node names and descriptive properties across multiple versions for nodes of a common type. Domains are created by administrators and associated with versions by Data Manager role users or version owners. Nodes may be assigned to a domain in a particular version at the time of creation or later using the Domain Membership feature. Nodes that are members of a domain cannot be renamed. Domains may be optionally configured to use a prefix or suffix to qualify node names as well as restricting the deletion of nodes or changing their limb/leaf designation. Import processes can handle the qualification of domain node names as nodes are being created in a version and blending processes allow the assignment of a node to a domain as nodes are copied to a target version.

You can copy nodes from one version to another. The Put Node and Insert Node features let you select a node from a version other than the current version. On Compare result page you can drag and drop and a node from one version to a different version. For each scenario where a node is being copied across versions, you have the option of copying properties and descendant nodes from the source to the target version. You can also copy node properties across versions from one node to another node.

You can directly access a hierarchy or local node in the Data Relationship Management Web Client from an external document or program using a context-senstive URL. The URL is accessible as a system property for a hierarchy or local node for easy reference and copy-paste to another application. If Single Sign On (SSO) or anonymous access is enabled, the user will directly navigate to the version, hierarchy, and node with which the URL is associated. If not enabled, the user is directed to the login page and upon successful log in, is navigated to the hierarchy or node.

A new Hyperlink property data type is available to manage URLs which refer to Web resources. The URLs display as navigable hyperlinks in the Data Relationship Management Web Client. The Memo and FormattedMemo data types can also support hyperlinks embedded in regular text. All of these property data types support the option of defining a label for each URL to improve on-screen display of complicated or lengthy URLs.

Assigned or selected batch validations can be run prior to executing a Data Relationship Management data export. This feature ensures that the data adheres to the appropriate business rules before further distribution. When the validation option is selected and the associated data fails to pass the specified validation, the export process is stopped. The following export types support this feature:

When exporting to a database table, a record number is auto-generated for each record being output to preserve the order of the records as they are exported. The following export types support this feature:

A new Formula validation class may be used to enforce business rules that require complex logic which can be expressed in a Data Relationship Management formula. This validation class bypasses the need for a derived property definition to be created which may greatly reduce the complexity of an application configuration. New formula functions are also available to perform advanced calculations for derived properties and validations.

The new formula functions are listed below. See the Oracle Hyperion Data Relationship Management Administrator's Guide for more information on these functions.

You can change the property type for an existing property definition to improve customization of properties loaded from application templates and to preserve any relationships to other metadata objects which depend on the property to function properly. The primary consideration when changing the property type is if the property is being changed from one that can store data to one that cannot (defined to derived or lookup). In this situation, the user is warned that data will be lost and must confirm the change.

Data Relationship Management user interface components are available in non-English languages to support globalization requirements for international organizations. The following languages are supported:

A limited set of non-Unicode multi-byte character sets are supported for text files used for action scripts, import sources, and export targets to accommodate legacy systems that are not Unicode compliant.

Data Relationship Management can be used to manage chart of accounts segment values, their properties, and hierarchies for independent value sets in Oracle E-Business Suite General Ledger or Oracle Fusion Accounting Hub. Segment values can be created, organized into hierarchies, and marked for distribution in Data Relationship Management. This chart of accounts information can be distributed to one or multiple Oracle General Ledger instances. Segment values and hierarchies are retrieved from Data Relationship Management and loaded using a concurrent request program. For more information, refer to the Oracle Hyperion Data Relationship Management Oracle General Ledger Integration Guide.

Namespaces are used in the names of property definitions, validations, and node access groups to distinguish metadata objects with similar names and to prevent naming conflicts when application templates are loaded into the same Data Relationship Management application. These metadata object types are organized by namespace for user selection and administration purposes within the web client. Labels can now be duplicated for convenience purposes, whereas previously they had to be unique. Tasks such as action scripts may require a fully qualified object name if the label of a referenced object cannot be resolved to a unique name. The following namespace considerations apply to property definitions, validations, and node access groups:

With the 11.1.2.1 release, change tracking functionality for nodes is now always enabled and is no longer controlled by system preferences. Several enhancements improve change tracking for nodes in Data Relationship Management:

Data Relationship Management can now identify forward dependencies with an object that was selected for deletion during metadata administration. This capability enables users to preview which other objects would be negatively affected as a result of the deletion and enables cancellation of the deletion operation.

Administrators can now modify a selected set of system preferences for a Data Relationship Management application that will take immediate effect once saved. This immediate effect capability is particularly beneficial for frequently changed system preferences such as Default Current Version and Default Previous Version, which you can now set using the Make Default menu option available while managing versions.

In this release, Data Relationship Management supports single sign-on using Oracle Access Manager. Single sign-on is available through the Data Relationship Management web client. For more information on enabling single sign-on, see the Oracle Hyperion Enterprise Performance Management System Security Administration Guide.

You can use Oracle HTTP Server to load balance Data Relationship Management IIS Web applications. For more information, see the Oracle Hyperion Enterprise Performance Management System High Availability and Disaster Recovery Guide.

Unless otherwise indicated, you can find more information on the new features outlined in this guide in the Oracle Hyperion Data Relationship Management User's Guide and the Oracle Hyperion Data Relationship Management Administrator's Guide.

The Data Relationship Management web service API was enhanced to conform to Oracle Fusion Middleware web service standards, including:

Detailed information about the web service API is available in the Oracle Hyperion Data Relationship Management Web Service API Reference. For more information on the Data Relationship Management API, see the Oracle Hyperion Data Relationship Management Application Programming Interface Guide.

A new Web client provides access to the complete feature set of a Data Relationship Management application through a Web browser. It combines the functionality previously available in the Windows client and the Web Publishing client in a single user interface. Presentation of data and access to features is simplified, improving ease of use.

The Web client provides two types of access:

Online help is now available from the Data Relationship Management user interface.

User roles enable control of high-level access to data and Data Relationship Management features. Several system-defined roles are available, enabling permissions to be assigned at a granular level to allow users to perform higher-level functions without giving them complete higher-level access. Security administration is now segregated from metadata administration to align with corporate policies that require this level of separation of duties.

The following system-defined roles are available:

Administrators can set up common connections to file systems and databases that can be shared by all users. Imports and exports run on the application server and directly access external connections instead of requiring a manual upload/download by a user. Administrators are also able to restrict certain connections to only profiles used for system integration purposes. Centralized maintenance of external connections helps minimize maintenance of connectivity to network resources, particularly for migration scenarios across environments.

Many existing features have been enhanced to provide a more informative and streamlined user experience. The improvements for each product function are:

Browsing and Searching Data

Managing Data

Validations

Queries and Compares

Scripts

Imports, Blenders, and Exports

Audits

The following rules apply for querying transactions:

The following rules apply for request queries:

Administration

Data Relationship Management provides Unicode support for user-defined metadata and data. Unicode support allows the use of multi-byte character sets to handle multiple languages at the same time. Internationalization of date and float data types based on a user’s locale is also included.

Separate Data Relationship Management applications can be configured and run on the same server to enable customers to physically segregate and independently manage different instances without requiring additional hardware or virtualization software. Different business groups are able administer the metadata and data within their own applications without any impact to any other application. The Data Relationship Management Console is now used to create and manage all applications for a single installation.

A coarse-grained Java web service for Data Relationship Management provides easier interoperability with other Oracle Middleware and third-party Service-Oriented Architecture (SOA) applications. API methods are now stateless and include operations that perform a combined set of actions on the server. Asynchronous operations such as imports and exports that use saved profiles can be executed using a small set of runtime parameters instead of requiring the entire profile to be supplied. Security improvements have also been incorporated to comply with web service standards.

64-bit support is available for the web and application servers for Data Relationship Management. This includes certification for 64-bit Windows operating systems as well as increased memory addressability for Oracle Hyperion Data Relationship Management engines on the application server.

For more information on these new features, see the Oracle Hyperion Data Relationship Management User's Guide and the Oracle Hyperion Data Relationship Management Administrator's Guide.