Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Multidomain MDM 10.5 HotFix 2
  • All Products

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: Glossary

Configuration Guide

Configuration Guide

Back Next

Converting Base Objects to Relationship Base Objects

Converting Base Objects to Relationship Base Objects

Relationship base objects are tables that contain information about two entity base objects.
Base objects do not have the metadata required by the
Hierarchy Manager
 for relationship information. To use base objects, first convert the base objects to entity objects, and then select the entity objects you want to relate in a relationship object.
  1. In the Hierarchies tool, acquire a write lock.
  2. Right-click in the navigation pane and choose
    Convert BO to Entity/Relationship Object
    .
  3. Click
    OK
    .
    The Convert to Relationship Base Object screen is displayed.
  4. Specify the following properties for this base object.
    Field
    Description
    Entity Base Object 1
    Entity base object to be linked via this relationship base object.
    Display name
    Name of the column that is a FK to the entity base object 1.
    Physical name
    Actual name of the column in the database. Informatica MDM Hub will suggest a physical name for the column based on the display name that you enter.
    Entity Base Object 2
    Entity base object to be linked via this relationship base object.
    Display name
    Name of the column that is a FK to the entity base object 2.
    Physical name
    Actual name of the column in the database. Informatica MDM Hub will suggest a physical name for the column based on the display name that you enter.
    Hierarchy FK Column
    Column used as the foreign key for the hierarchy; can be either ROWID or CODE.
    The ability to choose a BO Class CODE column reduces the complexity by allowing you to define the foreign key relationship based on a predefined code, rather than the Informatica MDM Hub-generated ROWID.
    Existing BO Column to Use
    Actual column in the existing BO to use.
    Hierarchy FK Display Name
    Name of this FK column as it will be displayed in the Hub Console
    Hierarchy FK Physical Name
    Actual name of the hierarchy foreign key column in the table. Informatica MDM Hub will suggest a physical name for the column based on the display name that you enter.
    Rel Type FK Column
    Column used as the foreign key for the relationship; can be either ROWID or CODE.
    Existing BO Column to Use
    Actual column in the existing BO to use.
    Rel Type FK Display Name
    Name of the FK column that is used to store the Rel Type CODE or ROWID.
    Rel Type FK Physical Name
    Actual name of the relationship type FK column in the table. Informatica MDM Hub will suggest a physical name for the column based on the display name that you enter.
  5. Click
    OK
    .
When you modify the base object using the Schema Manager tool, do not change any of the columns added by the
Hierarchy Manager
. Modifying these columns will result in unpredictable behavior and possible data loss.
0 COMMENTS
We’d like to hear from you!