Table of Contents

Search

  1. Preface
  2. Part 1: Introduction
  3. Part 2: Configuring Hub Console Tools
  4. Part 3: Building the Data Model
  5. Part 4: Configuring the Data Flow
  6. Part 5: Executing Informatica MDM Hub Processes
  7. Part 6: Configuring Application Access
  8. Appendix A: MDM Hub Properties
  9. Appendix B: Viewing Configuration Details
  10. Appendix C: Row-level Locking
  11. Appendix D: MDM Hub Logging
  12. Appendix E: Table Partitioning
  13. Appendix F: Collecting MDM Environment Information with the Product Usage Toolkit
  14. Appendix G: Informatica Platform Staging
  15. Appendix H: Informatica Platform Mapping Examples
  16. Appendix I: Glossary

Example Base Objects for Inter-Table Paths

Example Base Objects for Inter-Table Paths

Consider the following example in which a
Informatica MDM Hub
implementation has two base objects:
Base Object
Description
Person
Contains any type of person, such as employees for your organization, employees for some other organizations (prospects, customers, vendors, or partners), contractors, and so on.
Address
Contains any type of address—mailing, shipping, home, work, and so on.
In this example, there is the potential for many-to-many relationships:
  • A person could have multiple addresses, such as a home and work address.
  • A single address could have multiple persons, such as a workplace or home.
In order to configure match rules for this kind of relationship between records in different base objects, you would create a separate base object (such as PersAddrRel) that describes to
Informatica MDM Hub
the relationships between records in the two base objects.

0 COMMENTS

We’d like to hear from you!