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

Converting Base Objects to Entity Base Objects

Converting Base Objects to Entity Base Objects

You must convert base objects to entity base objects before you can use them in the
Hierarchy Manager
. The base objects must have state management enabled before you can convert them to entity base objects.
Base objects do not have the metadata required by the Hierarchy Manager. To use base objects with the Hierarchy Manager, you must add this metadata using a conversion process. You can use entity base objects with both the MDM Hub and the Hierarchy Manager.
  1. In the Hierarchies tool, acquire a write lock.
  2. Right-click anywhere in the navigation pane and choose
    Convert BO to Entity/Relationship Object
    .
    The same options you see on the right-click menu are also available on the Hierarchies menu.
  3. In the Modify Existing Base Object dialog, select
    Convert to Entity Base Object
    and click
    OK
    .
    If you do not see any choices in the Modify Base Object field, then there are no non-hierarchy base objects available. You must create one in the Schema tool.
  4. Click
    OK
    .
    If the base object already has Hierarchy Manager metadata, the Hierarchies tool will display a message indicating the Hierarchy Manager metadata that exists.
  5. In the Foreign Key Column for Entity Types field, select the column to be added: RowId Object or BO Class 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 MDM Hub-generated ROWID.
  6. In the Existing BO Column to use, select an existing column or select the Create New Column option.
    If no BO columns exist, only the Create New Column option is available.
  7. In the Display Name and Physical Name fields, create display and physical names for the column, and click
    OK
    .
The base object will now have the columns that Hierarchy Manager requires. To add additional columns, use the Schema Manager.
When you modify the base object using the Schema Manager tool, do not change any of the columns added using the Hierarchies tool. Modifying any of these columns will result in unpredictable behavior and possible data loss.

0 COMMENTS

We’d like to hear from you!