Recent Posts


Oracle Data Relationship Management Version Release Highlights
Posted on March 12, 2015
Author: Jason Sawicki, Performance Architects

Oracle recently released Oracle Data Relationship Management (DRM) Version with some exciting enhancements. One great aspect of this release is that the DRM architecture was reworked to improve overall performance for users.  In addition to anticipated updates to the Oracle Data Relationship Governance (DRG) module and a number of native enhancements, another notable change is that DRM is more tightly integrated with Oracle’s EPM (Hyperion) software-as-a-service (SaaS) offerings.

DRM Cloud Integration with Oracle Planning and Budgeting Cloud Service (PBCS)

DRM now integrates with both Oracle Planning and Budgeting Cloud Service (PBCS) and Oracle Hyperion Planning to allow for either the export or import of dimensions out of or into DRM. This should be considered a positive for organizations that maintain a combination of on premise and cloud-based applications (for example, planning in PBCS but using Oracle Hyperion Financial Management (HFM) for financial close and consolidation on premise). This particular integration leverages the outline load utility (OLU) file format that we are all familiar with for managing dimensions and member properties in Hyperion Planning applications.

Data Relationship Governance (DRG)

Data Relationship Governance (DRG) is the change management and workflow module native to DRM as of release Some of the enhancements in this release include:

  • Conditional Workflow Stages. You can assign a conditional action for a stage in the workflow, or follow a separate workflow mid-stream if a particular condition is met. If the condition is not met, you can continue following the primary workflow.
  • Request Items from a File. You can now include a flat file within a request. For example, for a remediation request, the output from a validation could be included within the request as a flat file.
  • Request Auditing. You can now view the final approver of a workflow within the transaction history of DRM. This was not possible prior to this release. To view DRG history in the initial release the work list would have to be accessed and searched for the specific request ID. This is now an easier way to identify the responsible user, as you can query workflow tasks to see the users, stage, time, and/or type of task for requests. This is similar to the native DRM audit functionality.
  • Request Attachments. You can now add attachments to a workflow request (explain actions and justify changes). Attachments are accessible to all workflow participants.
  • Improved Handling of Request Submissions.
    • Submitter can withdraw a request.
    • Commit Users may access escalation requests from prior stages.
    • Escalation Users can advance requests up the chain for any stage.
    • The Data Manager role can now take control of inflight requests and “unclaim” a request if need be or can delete a request if required to do so.
  • Workflow Page Layout Improvements.
    • The workflow is now laid out in tabs.
    • Inclusion of labels and instructions is now possible and these can either be displayed or hidden.
    • Hierarchies can be filtered by task.

Native DRM Enhancements

Getting back to native DRM, there are a number of enhancements to both the import and export functionalities that I will summarize without going into too much detail.

  • Export Enhancements.
    • Substitution Parameters. This allows for dynamic control of an exported column via a substitution parameter and provides a constant value that generates a column resulting from the combination.
    • Hierarchy Groups. Uses already-defined hierarchy groups to auto-select hierarchies for export.
    • Dynamic Columns. As mentioned above, dynamic columns can be generated within exports in this release.
  • Import Enhancements.
    • Create Hierarchies from Orphans. Hierarchies can be created from a list of orphans (nodes in DRM not assigned to any existing hierarchies).
    • Substitution Parameters. Can be used for setting defaults and run-times.
    • Node Ignoring. You can specify nodes to ignore during an import process and you can also specify to skip header records.
    • Import single section. Per the import file format: a single block section can be imported without the header section.
    • Validations and Node Types. These can now be assigned during an import.
    • String Handling and Memos. Can be loaded via an import; handling of these has been improved.

DRM Improved Infrastructure and Architecture

In this release, how the engines run as associated with server processors has been reworked to improve overall performance. Basically, DRM can now better leverage multi-processor servers to run operations more efficiently. This means that calculation and read operations have more power – making DRM faster and more scalable!

Stay tuned for further updates from our team on the release.

Author: Jason Sawicki, Performance Architects


© Performance Architects, Inc. and Performance Architects Blog, 2006 - present. Unauthorized use and/or duplication of this material without express and written permission from this blog's author and/or owner is strictly prohibited. Excerpts and links may be used, provided that full and clear credit is given to Performance Architects, Inc. and Performance Architects Blog with appropriate and specific direction to the original content.

Leave a Reply

Your email address will not be published. Required fields are marked *