Governing Master Data – A Data Steward’s Experience

Governing Master Data

As organizations grow, the need to govern master data grows. The growth of an organization often creates the need for additional downstream applications that need to consume master data. Manually maintaining master data in an ERP, as well as multiple downstream applications, can become cumbersome very quickly. This is when organizations will inevitably begin to consider the use of a single source master data management tool, such as Data Relationship Management (DRM). As a former data steward, I have seen this roadmap on multiple occasions. It just makes sense to find a central location to maintain your master data.

The next big challenge is how to address the process to change master data. In my previous roles, the process often included uploading requests to SharePoint or submitting Excel spreadsheets via email. The data steward would then combine the various requests and vet any unanswered questions prior to reviewing the proposed changes in a governance board meeting. Following the board meeting, final approvals were sent to the data steward for documentation. The spreadsheets and email approvals would be retained by the data steward for audit purposes. This manual process was ultimately time consuming and error prone.

DRG (Data Relationship Governance) is a component of DRM that is quite effective at automating the manual master data change process. This tool allows organizations to build custom workflows unique to their business needs and rules.

Below are some of the key features included in DRG:

  • Master data additions, deletions, moves, inserts, and updates
  • The ability to build complex workflows including multiple approvals and conditional routing based on a property or validation
  • Customizable tasks that can be tailored to each user group such as a requestor, a mid-level approver, and a final approver
  • The ability to apply validations to each individual stage of a workflow, ensuring each request conforms to business rules
  • Various approval types, review, enrich, or commit
    Alerts and email notifications
  • The ability to audit the requests from submit to commit

DRG has proven to significantly improve the master data change process. This tool allows businesses to efficiently submit, approve, and update DRM with master data changes while eliminating the need to maintain offline spreadsheets and approvals. A more streamlined master data change process removes unnecessary administrative tasks from employee responsibilities, providing an immediate return on investment.

Leave a Reply

  • Oracle EPM Cloud Update – Jan’22 (22.01)

    These Oracle EPM updates are scheduled to take place during the first nightly maintenance period on or after 2AM ET on Saturday Jan 8, 2022 (test environments) and on or after 2AM ET on Saturday, Jan 22, 2022 (production environments)

    January 7, 2022
  • Oracle EPM Cloud Update – Dec’21 (21.12)

    These Oracle EPM updates are scheduled to take place during the first nightly maintenance period on or after 2AM ET on Saturday Dec 3, 2021 (test environments) and on or after 2AM ET on Saturday, Dec 17, 2021 (production environments).

    December 2, 2021
  • Oracle EPM Cloud Update – Nov’21 (21.11)

    These Oracle EPM updates are scheduled to take place during the first nightly maintenance period on or after 2AM ET on Saturday Nov 5, 2021 (test environments) and on or after 2AM ET on Saturday, Nov 19, 2021 (production environments).

    November 3, 2021
  • Block Creation in Essbase – Part 2

    The previous post ended with a discussion on using DATACOPY to create blocks. I stated that it was my preferred method of making sure the right blocks were created for use. However, we may run into a situation requiring an “IF” test to determine when we create the blocks. In this situation, we cannot use DATACOPY as it is not syntactically valid inside an IF test.

    October 22, 2021