Oracle Data Relationship Management


 drm-screenshot

Oracle Data Relationship Management (DRM) is an enterprise change management solution for building and retaining consistency within master data assets despite endless changes necessary to support underlying transactional and analytical systems.

As companies grow and evolve, it becomes essential to manage master data across information silos that result from mergers and acquisitions, departmental initiatives, or legacy system proliferation. Data consistency, integrity, quality and accuracy suffer and no one trusts the information and insight that ensues. Oracle DRM provides the industry's first data model-agnostic master data management solution built to enable financial and analytical master data management in dynamic, fast-changing business environments.

Financial MDM
Create an enterprise view of financial chart of accounts, cost centers and legal entities with a view to govern on-going financial management and consolidation based on consistent definitions of financial and reporting structures across general ledger systems, financial consolidation, planning and budgeting systems.

Analytical MDM
Create an enterprise view of analytical dimensions, reporting structures, performance measures and their related attributes and hierarchies using Oracle DRM's data model-agnostic foundation. Construct departmental perspectives that bear referential integrity and consistency with master data constructs based on validations and business rules that enforce enterprise governance policies. Synchronize master data with downstream systems including BI/EPM systems, data warehouses and data marts to gain trustworthy insight.

Data Governance
Through data governance, organizations can exercise business process control and automation over the processes and methods used by their data custodians to handle change management and remediation of enterprise information assets such as master data, enterprise dimensions, hierarchies, relationships, associated attributes and mappings.
Oracle Data Relationship Governance (DRG) is a fully configurable, collaborative business application that automates change request approval and data remediation workflows between front-line business users, subject matter experts, signing authorities and data stewards using automated, repeatable business processes to enable data quality, policy compliance, user collaboration, and change awareness across the business community.
 

What's New

 

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

  • Dynamic scripting: enables Data Relationship Management administrators to develop business logic for derived properties and validations using JavaScript. Dynamic scripts provide a more robust and better-performing alternative to formulas, using a standard scripting language. Scripts allow for better organization and less complexity of logic through the use of multiple statements, variables, and in-line comments. Dynamic scripts also provide support for advanced concepts such as looping and regular expressions.
  • Import from Database Tables: External connections to relational databases can be used to import data from database tables into Data Relationship Management. An import profile can source data from tables in a single database. Each section of an import profile can be mapped to a single database table. A query filter can be configured to import a subset of data from the source database tables.
  • Object Access Groups: Object access groups enable metadata objects to be organized, accessed, and managed collectively by a custom group of users. The previously available object access levels (User, Standard, and System) are now available as core object access groups. Custom object access groups can be created and provisioned by access managers. Users can be assigned Run or Manage permission to each custom object access group.
  • Hierarchy Constraints for Node Properties: Hierarchy constraints can limit the hierarchies and nodes available for viewing and selection when updating a node data type property value. A hierarchy constraint is an optional configuration for property definitions that use a node data type. The hierarchy constraint feature uses hierarchy groups and hierarchy group properties, which must be configured before you can assign hierarchy constraints.
  • Job Management: Job management enables greater control and visibility over long running operations (jobs) and the results they produce. Running an operation as a job enables users to perform a different task while the process is running and have access to the status and any results of the operation when they return.
  • Localized Documentation: To support globalization requirements for international organizations, the Data Relationship Management users guide, implementation guide and installation guide for this release have been translated into Simplified Chinese, Japanese, Korean, French and German.

Oracle Data Relationship Governance, Fusion Edition V.11.1.2.3 Release Highlights

  • New Product in 11.1.2.3: Fully configurable governance workflow oriented business application targeted at front-line business users. Shares metadata with Oracle Data Relationship Management and extends it through the configuration of workflow models, stages, and tasks.  Configurable and extensible by DRM administrators. Native workflow engine, only requires DRM as pre-requisite.
  • Workflow Models: Used to control user tasks, stages of workflow, and types of data involved to govern a set of changes to data in Oracle Data Relationship Management.
  • Workflow Requests: Used to initiate changes or corrections to be completed, approved, enriched, and committed by other users using governance workflows.
  • Governance Work List: A central location for interacting with change and remediation requests. From the work list, governance users may submit change requests or review and participate in requests assigned to their user group.
  • Alerts and notifications: Provides Data Relationship Management alerts and email notifications to governance users and data managers for requests to which they are associated. The configuration of stages for the workflow model for a request controls whether users are notified of activities taking place in a particular stage and which users get notified.
  • Policy Management: High level enterprise data policies articulated by data governance committees may be broken down into business rules, data validations, and data access privilege assignments. Metadata artifacts familiar to Oracle Data Relationship Management administrators may be reused or extended to enforce governance against these data policies as business users request and respond to changes executed as governance workflows.
  • Workflow Automation: Workflow automation is dynamic, data-driven and exception-based.  Requests are routed dynamically from one stage to the next based upon how both the data requested as well as how access to it is configured.   Requests are routed dynamically based upon request items, workflow data access groups, and user privilege assignments associated with a given workflow model. 


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.