As organizations grow through acquisition and the development of new products and services, the task of keeping master data synchronized across multiple systems is often met using Oracle Data Relationship Management. However, managing the process of requesting, approving and documenting changes to this master data requires something more – Oracle Data Relationship Governance. Paul Ritner, a Principal Solutions Architect with Advanced EPM joined me for a podcast to discuss what data relationship governance is, and why people want and need it.
So what is data relationship governance? Paul indicated that to understand data relationship governance, you first need to understand data relationship management.
Data relationship management is a solution used to manage the structure and alignment of master data such as, account numbers, department codes, product codes, and any other similar values or reference data across multiple systems. The real value of data relationship management is that organizations can build their business rules and other complex business logic into the repository to ensure only valid values get created and are correctly positioned in the multiplicity of hierarchical structures organizations require for both aggregations and reporting. Oracle’s solution, Oracle Data Relationship Management (or DRM), is just such a management solution that is highly configurable and is agnostic when it comes to connecting to align data in multiple systems.
Data relationship governance is the solution that helps to monitor and manage workflow activities related to data relationship management. Oracle’s solution, Oracle Data Relationship Governance (or DRG) is fully integrated with DRM. DRG handles all the workflow activities, and relies on existing Oracle DRM configured rules and property formulas. It is also a natural extension to Oracle’s DRM solution.
Paul said that prior to Oracle introducing their DRG solution, discussions about workflow in relation to data relationship management was usually met with a rolling of the eyes due to the complexity of typical data governance processes. At the time, it was a difficult conversation as it required significant customer development. With DRG it turns into a simple configuration exercise.
So why do people now want Oracle’s DRG solution?
Paul said that there were several reasons, including:
• Oracle DRG is an easily configurable workflow tool that is fully integrated with, Oracle Data Relationship Management.
• Oracle DRG enables you to easily build web-based workflows to manage requests for new values & changes, which ultimately end up in your existing data relationship management repository.
• Oracle DRG includes task lists and email alerts!
• All the key configurations that organizations already have in their Oracle DRM repository can be readily leveraged by Oracle DRG workflows. Configurations such as:
• Linking workflows with hierarchies
• Linking existing data relationship management validations (or Business Rules) with particular data relationship governance workflow steps
• As well as including any of your derived property values, which can contain some very complex logic
Basically, all the hard work that went into an organization’s DRM application can be readily included in their DRG workflow, and that’s a huge value! Paul provided a great 4 step workflow example, however he indicated that workflows can have as many steps as needed by an organization. He also talked about the fact that a single workflow request could be made for multiple accounts.
So who, exactly, would initiate a workflow request? A financial analyst? Paul indicated that it could be one of several people. However, in general, it is often an analyst or accountant. A request could be made by other business people as well and, if the workflow was for a Department Code or Cost Center, requests could come from all over a company.