MDM and business rules management
What is the role of master data management (MDM) in business rules?

    Requires Free Membership to View

    When you register, you'll begin receiving targeted emails from my team of award-winning writers. Our goal is to keep you informed on the hottest data and information management trends today.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchDataManagement.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchDataManagement.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

Business rules aren't system-centric, they're business-centric. As such, they should leverage master data when they need to. For instance, take a simple business rule, like "all branches should have a branch code." The branch code would then be able to roll up to branches within a certain region. If you look at the new crop of business rules management systems currently available on the market, they ensure that business rules are consistent across systems, deployed as a centralized enterprise service for consistency's sake. A real-life example is with volume purchase agreements (VPAs). In order to apply the correct pricing, a business rules management system might need to call product master data on a PIM hub to get the most current list price for a product in order to calculate an accurate VPA. This scenario combines workflow, master data, and authoritative business rule calculation to ensure the integrity of potentially high-impact discounts.

This was first published in April 2007