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

Process Overview for Defining Base Objects

Process Overview for Defining Base Objects

Use the Schema Manager to define base objects.
  1. Using the Schema Manager, create a base object table.
    The Schema Manager automatically adds system columns.
  2. Add the user-defined columns that will contain business data.
    Column names cannot be longer than 26 characters.
  3. While configuring column properties, specify the columns that will use trust to determine the most reliable value when different source systems provide different values for the same cell.
  4. For the base object, create one staging table for each source system. For each staging table, select the base object columns that you need to include.
  5. Create landing tables that you need to store data from source systems.
  6. Map the landing tables to the staging tables.
    If any column needs data cleansing, specify the cleanse function in the mapping.
    Each staging table must get its data from one landing table (with any intervening cleanse functions), but the same landing table can provide data to more than one staging table. Map the primary key column of the landing table to the PKEY_SRC_OBJECT column in the staging table.
  7. Populate each landing table with data using an ETL tool or some other process.

0 COMMENTS

We’d like to hear from you!