|
|
Release 11.1.2.1
Table of Contents:
Oracle Hyperion Data Relationship Management, Fusion Edition 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:
The fully qualified name of an object includes its namespace and uses dot notation to delimit the namespace from the name of the object.
System-defined objects always use the Core namespace.
User-defined objects always use the Custom namespace.
Properties that are generated by the system for assigning validations are created with the Val namespace.
Properties that are generated by the system for assigning node access groups are created with the namespaces Nag.Limb and Nag.Leaf.
Properties, validations, and node access groups are displayed by label in the property editor, with the ability to separately view the namespace.
Objects are displayed by label and namespace in other areas of the web client where selection from a list is required.
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:
New property definitions labeled Added On, Added By, Last Changed On, Last Changed By, and Node Changed are now available in the Stats property category. These core properties replace the custom properties that were referred to by system preferences to enable change tracking functionality in previous releases.
DateTime, a new data type for properties, is available and is used by the NodeAddedOn and NodeLastChangedOn change tracking properties. The DateTime data type combines the functionality of the Date data type and the Time data type, which remain and are not otherwise affected. The format in which DateTime data type property values are displayed is controlled by the regional settings of each user's session.
The formula functions AddedOn, AddedBy, ChangedOn, and ChangedBy are mapped to the new properties. A new formula function labeled Changed is mapped to the new Node Changed property.
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:
URLs, namespaces, and types
Method signatures
Policy management and message protection are now available using Oracle Web Services Manager
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.
With this release, many Oracle Hyperion Enterprise Performance Management System products support hostnames that resolve to IPv6 addresses. See the Oracle Hyperion Enterprise Performance Management System Certification Matrix. IPv4 support (both hostname and IP address) remains unchanged from earlier releases.
Oracle Hyperion Enterprise Performance Management System supports the following types of SSL configurations:
Full SSL Deployment (including data access)
SSL Terminating at the Web Server
SSL Accelerators (Off-loading)
Two-way SSL
For more information on the SSL configurations, see the Oracle Hyperion Enterprise Performance Management System Security Administration 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:
Authenticated users have personalized service based on their roles and granular security
Anonymous users can access public views of data via a URL for easy reference
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:
Anonymous User
Workflow User
Interactive User
Data Creator
Data Manager
Access Manager
Application Administrator
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:
View multiple properties as columns in a tree
Show or hide inactive nodes in a hierarchy
Identify shared nodes using icons
Configure the number of nodes to be displayed in a tree on each page
Use the pager to navigate through node pages
Search for specific descendant nodes under a hierarchy node
Find a node in the Node Selector dialog box
Download trees and grids to an external file format such as PDF, RTF, or XLS
Create your own versions and hierarchies using the Data Creator role
Define new hierarchy groups during hierarchy creation
Assign controlled properties after hierarchy creation
Add or insert a node as a sibling
Add multiple nodes to the clipboard at the same time by using the Take option
Insert or move nodes from different parents at the same time by using the Put option
Copy and paste properties from the clipboard
Order children by using drag-and-drop functionality
View and edit properties directly from node lists such as find, query, compare, or validation results.
Create validations to run in real time, batch, or both modes
Define the validation mode at the time of assignment to data
View validation reasons for multiple nodes at the same time
Copy nodes from validation results to the clipboard
Work with multiple queries and compares at the same time
Define return properties during query or compare creation
Run queries or compares for selected nodes by using shortcuts
Copy nodes from results to the clipboard
Restrict access to queries and compares used for system purposes
Select a character encoding for a source file
Edit action parameters in loaded scripts
Download loaded scripts to additional external file formats such as PDF, RTF, or XLS
Imports, Blenders, and Exports
Work with multiple objects at the same time
Import from or export to network resources by using external connections
Select a character encoding for an import or export file
Download import and blender results to an external file format such as PDF, RTF, or XLS
Restrict access to imports, blenders, and exports used for system purposes
View From and To details for administrator transactions side by side
Download transactions or requests to external file formats such as PDF, RTF, or XLS
The following rules apply for querying transactions:
Interactive Users can query only their own transactions
Data Creator or Manager users can query all data transactions
Access Manager or App Administrator users can query system transactions
The following rules apply for request queries:
Users can query only requests that they own
Data Manager users can query all requests
Browse and select administrative tasks from a tree
Work on multiple objects at the same time
Define function parameters before you insert functions into formulas
Provide glyphs in PNG format
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, Fusion Edition 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.
To access online help: