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

Adding Match Path Components

Adding Match Path Components

Match paths define the connection between parent and child base objects. To configure match rules that include parent and child records, add match path components to the root base object. Also, add filters to include or exclude data during the match process.
  1. In the
    Match/Merge Setup Details
    page for the Party base object, click the
    Paths
    tab.
  2. Add the Party Address Rel relationship base object as a match path component.
    1. From the Path Components section, select the
      Root for C_Party
      match path component.
      The following image shows the
      Paths
      tab of the
      Match/Merge Setup Details
      page:
      The Paths tab of the Match/Merge Setup Details page shows the Root for C_Party match path component.
    2. In the
      Path Components
      section, click
      Add
      .
      The following image shows the
      Add Path Component
      dialog box:
      The
      Add Path Component
      dialog box appears.
      The Add Path Component dialog box shows the Display Name and Physical Name fields, and the check for missing children option. The Party cross-reference table appears in the Constraints section of the Add Path Component dialog box.
    3. In the
      Display Name
      field, enter Party Address Rel as the name for the match path component that you want to display in the Hub Console.
      The
      Physical Name
      field is populated based on the display name for the match path component that you enter. Physical name is the name of the path component in the database.
      The following image shows the
      Add Path Component
      dialog box:
      The
      Add Path Component
      dialog box appears with the name fields populated.
      The Add Path Component dialog box shows the Display Name field with the value Party Address Rel and the Physical Name field with the value, C_MT_PARTY_ADDRESS_REL.
    4. Ensure that the
      Check for missing children
      option is enabled.
      The option is enabled by default. When enabled, matching occurs between the parent base object records and their associated child base object records. Matching occurs even if the parent base object records do not have child records in the child base object for which the option is enabled.
      Match key generation depends on the configuration of the
      Check for missing children
      option. If the
      Check for missing children
      option is disabled, and if the parent record has no child records, match keys are not generated for the parent record.
    5. From the Constraints section, select a constraint, and click
      OK
      .
      The Party Address Rel path component appears in the Path Components section.
      The following image shows the
      Paths
      tab of the
      Match/Merge Setup Details
      page:
      The Paths tab of the Match/Merge Setup Details page shows the Root for C_Party match path component and the Party Address Rel match path component.
  3. Add the Address base object to the match path as a child of the Party Address Rel match path component.
    1. From the Path Components section on the
      Paths
      tab, select the
      Party Address Rel
      match path component.
    2. Click
      Add
      .
      The
      Add Path Component
      dialog box appears.
    3. In the
      Display Name
      field, enter the name that you want to display in the Hub Console for the Address base object.
    4. From the Constraints section, select a constraint, and click
      OK
      .
      The Address path component appears in the Path Components section as a child of the Party Address Rel match path component. The direction of the relationship appears as Child-to-Parent.
      The following image shows the
      Paths
      tab of the
      Match/Merge Setup Details
      page with path components:
      The Paths tab of the Match/Merge Setup Details page shows the Root for C_Party, Party Address Rel, and Address match path components.
  4. To include individuals and exclude organizations for matching, configure a filter for the Party base object that has the Party Type column.
    1. From the Path Components section, select the
      Root for C_Party
      match path component.
    2. In the Filters section, click
      Add
      .
      The
      Add Filter
      dialog box appears.
    3. From the
      Column
      list, select
      Party Type
      .
    4. From the
      Operator
      list, select
      IN
      .
    5. Beside the
      Values
      field, click
      Edit
      .
      The
      Edit Values
      dialog box appears.
    6. Click
      Add
      .
      The
      Add Value
      dialog box appears.
    7. In the Value field, enter
      Individual
      , and click
      OK
      .
    8. Click
      OK
      .
      The filter for the Party Type column appears in the Filters section. The filter for the Party Type column ensures that records such as Ryerson Area Med Ctr that belong to the party type Organization are excluded for match key generation. Only records such as Rachel Arsen and Ahmed Rauf that belong to the Person party type are included for match key generation.

0 COMMENTS

We’d like to hear from you!