Table of Contents

Search

  1. Introduction
  2. Configuring Hub Console Tools
  3. Building the Data Model
  4. Configuring the Data Flow
  5. Executing Informatica MDM Hub Processes
  6. Configuring Application Access
  7. MDM Hub Properties
  8. Viewing Configuration Details
  9. Search with Solr
  10. Row-level Locking
  11. MDM Hub Logging
  12. Table Partitioning
  13. Collecting MDM Environment Information with the Product Usage Toolkit
  14. Glossary

Columns in the Example Base Objects

Columns in the Example Base Objects

Suppose the Person base object had the following columns:
Column
Type
Description
ROWID_OBJECT
CHAR(14)
Primary key. Uniquely identifies this person in the base object.
TYPE
CHAR(14)
Type of person, such as an employee or customer contact.
NAME
VARCHAR(50)
Person’s name (simplified for this example).
EMPLOYER
VARCHAR(50)
Person’s employer.
...
...
...
Suppose the Address base object had the following columns:
Column
Type
Description
ROWID_OBJECT
CHAR(14)
Primary key. Uniquely identifies this employee.
TYPE
CHAR(14)
Type of address, such as their home, work, mailing, or shipping address.
NAME
VARCHAR(50)
Name of the individual or organization residing at this address.
ADDRESS_1
VARCHAR(50)
First address line.
ADDRESS_2
VARCHAR(50)
Second address line.
CITY
VARCHAR(50)
City
STATE_PROV
VARCHAR(50)
State or province
POSTAL_CODE
VARCHAR(50)
Postal code
...
...
...
To define the relationship between records in the two base objects, the PersonAddrRel base object could have the following columns:
Column
Type
Description
ROWID_OBJECT
CHAR(14)
Primary key. Uniquely identifies this person in the base object.
PERS_FK
CHAR(14)
Foreign key to the ROWID_OBJECT column in the Person base object.
ADDR_FK
CHAR(14)
Foreign key to the ROWID_OBJECT column in the Address base object.
Note that the column type of the foreign key columns—CHAR(14)—matches the primary key to which they point.

0 COMMENTS

We’d like to hear from you!