DRM 11.1.2.2. What's new

Oracle Data Relationship Management, Fusion Edition V.11.1.2.2 Release Highlights

Performance Management Architect (EPMA) Integration: Oracle Hyperion EPM Architect can import hierarchies, nodes, and properties directly from 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: Oracle Hyperion Financial Management, Oracle Hyperion Planning, and Oracle Essbase. 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 Data Relationship Management EPM Architect Integration Guide.

Version Variables: 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.

Version Backup and Restore: 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 purpose

Hierarchy Group Properties: 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.

Domain Membership for Nodes: 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.

Copying Nodes and Properties Across Versions: 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.

Navigation to Hierarchy and Node via URL: 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.

Hyperlink Enabled Properties: 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.

Batch Validations for Export: 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: Hierarchy Export, Hierarchy XML Export, Generation Export, Version Export, Compare Export, EPM Architect Export (new in this release).

Record ID for Exports: 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: Hierarchy Export, Version Export, Compare Export.

Formula Based Validations and New Formula Functions: 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. See the Oracle Data Relationship Management Administrator's Guide for more information on these functions.

Property Type Modification for Saved Property Definitions: 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.

Tags: Exalytics for Hyperion Planning, Hyperion Essbase and Hyperion Profitability & Cost Management, Optimisation Hyperion Planning and Essbase Tip 6, Strategic Planning is not a military discipline anymore: welcome Adaptive Planning, The benefits of Management Information Dashboards, The Stacked Discount Case,

Meer »