DRG – The Key to Effective Master Data Management in DRM

Steve Davis

August 3rd, 2017

Data Governance continues to be a big topic. To understand Data Relationship Governance, you need to understand what the need is. When new accounts, cost centers, entities, or other master data needs to be added or modified, typically it will need to be added to multiple systems. Regardless of the company size, at some point, the growing organization decides to implement workflow in order to capture the changes that you need to make to the master data. This could be as simple as an email chain that is initiated by filling out a form and sent to various departments for their fortification and approval.  Once approved, the individual administrators can make these changes to the multiple applications, or these changes could be made in DRM and then sent downstream to the subscribing applications. This is where Data Relationship Governance (DRG) comes in.

Previously, companies have integrated their workflow tools into DRM using the Application Programming Interface (API). By writing code to integrate with DRM, the customers could capture additions and changes in one system and track and log these changes.  Emails could be sent from the workflow tool to indicate to users that they have a new request, or to remind users that the deadline was coming up.

Data Relationship Governance is native to Data Relationship Management with versions later than It is a tool that allows you to do workflow in order to manage master data in DRM. It uses a web interface that allows users to submit a request to make additions, deletions, or changes to the current structures in DRM.PRE-DRG it would take months to create workflow processes for DRM.  With DRG, you can have a workflow for DRM within a couple of hours.  The configuration of DRG is relatively simple, and DRG should be able to accomplish the majority of your workflow needs.

  • Workflow models in DRG are used to control user tasks, stages of workflow, and types of data involved to govern a set of changes to data.
  • Workflow requests in DRG are used to initiate changes or corrections to be completed, approved, enriched, and committed by other users using workflows.
  • Worklists are a central location for interacting with the requests. From the worklist, governance users may submit change requests or review and participate in requests assigned to their user group.
  • Alerts and email notifications have been added to DRM in order to notify the governance users and data managers about requests that they are associated with.
  • Workflow paths in DRG identify the stages of workflow to be completed for a request, the active stage for the request, the completion status of previous stages, and the approval count for the active stage. The workflow path enables participating users to understand how long a request may take, how many approvals may be involved, and where a request is positioned in the overall approval process.
  • Workflow tags allow governance users to assign a due date for completion of a request and to mark the request as urgent.

Find out more about DRG in my webcast, DRG – Creating Workflows in DRM.

We’ll look at workflow models, requests, paths, tags, and worklists, tasks, models, filters and users. You will learn how to create models and tasks, build workflow objects, auto number your new accounts and create validations on the workflow, assign security to the users and to the hierarchies, separate duties and do conditional workflows, filter nodes, and more…

Next, we’ll take what you’ve learned and apply it to real-world scenarios. Then I’ll leave you with tips, tricks, and best practices for working collaboratively with DRG to make sure all users have the necessary change management and data quality remediation workflows to do effectively do their jobs.

NOTE: Attendees should have a good understanding of DRM. You should understand what workflow is and how it is used.



Steve Davis

About Steve Davis

Steve Davis is a Principal Architect with over 18 years experience in all phases of design, development, and implementation of computer applications. His work with DRM and EDMCS includes integration with HFM, FDM, Planning, Essbase, EPM Cloud apps (e.g., PBCS, EPBCS, FCCS, etc.) EBS, PeopleSoft, SAP, OBIEE, and Data Warehouse. Steven has developed and delivered end-user training and designed MDM solutions around specific company requirements, leading the upgrade of multiple technical infrastructure projects. Steven frequently presents on data governance, most recently at OAUG Collaborate, the Altamont Group Business Forecasting Summit, and Kscope.

Leave a Reply

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