Inaport Training Introduction to Matching

Matching The purpose of Inaport is to: Extract data from a source Transform that data Load into a target Loading may require Insert new record if not there Update an existing record Update or insert All require Matching Identifying records in target that are same as source © Copyright 2010 InaPlex Inc

Matching Process of deciding which record or set of records in the target table(s) should be updated Alternatively, decide if record already exists and take appropriate action

© Copyright 2010 InaPlex Inc Table Operations Create new Create a new record always – no match required Update Means must be able to match Update single match –Make sure only *ONE* record matches Update all matches Update or create Try to match, if fail then create Match only No mapping

© Copyright 2010 InaPlex Inc Table Operations Address any table or combination of tables Can have same table multiple times E.g. Importing an ACT contact record with multiple contacts in same record New set of operations on each table

© Copyright 2010 InaPlex Inc Table Operations Account Contact ContactExtra Source Data Tables in target system Address

© Copyright 2010 InaPlex Inc Table Operations Operations are applied to tables starting from top of tree and working down Decision on top table may cause child tables to not be touched Consider effect: Create not exist on top means only sensible op on child is create always

© Copyright 2010 InaPlex Inc Matching Two parts Table relationships Specify primary/foreign keys using data dictionary, expression editor Primary key from parent used to find related records in child Match expressions Further refine matches on tables AFTER relationships have been used

© Copyright 2010 InaPlex Inc Match Example Suppose our database has company and people like this: Company table: comp1, Acme Corp comp2, Beta LLC Person table: pers1, comp1, John Smith pers2, comp1, Fred Jones pers3, comp2, John Smith Pers1 and pers2 are members of Acme Corp Pers3 is a member of Beta LLC Notice pers1 and pers3 have the same name

© Copyright 2010 InaPlex Inc Match Example The incoming data is: Acme Corp, John Smith Inaport will first match on company Acme Corp and get the primary key: comp1

© Copyright 2010 InaPlex Inc Match Example The Company primary key is then used to find the correct person records: pers1, comp1, John Smith pers2, comp1, Fred Jones Note – the John Smith belonging to Beta LLC is skipped Then the person John Smith is matched. Correct record is pers1

© Copyright 2010 InaPlex Inc Matching Techniques Inaport supports different ways to match Standard build expressions on source and target Fuzzy Refine Standard to allow for bad data SQL Use SQL SELECT instead of expressions

© Copyright 2010 InaPlex Inc Matching Techniques Each technique has strengths and weaknesses Standard Powerful, flexible In memory index can take time to build Fuzzy Even more powerful than standard More performance intensive, may require user review SQL No upfront cost of building indexes Less flexible, requires SQL knowledge, cost per source record

© Copyright 2010 InaPlex Inc Matching Techniques You can use the same technique for all tables, OR Choose different techniques for each table, based on requirements: Account - Fuzzy Match Contact - Standard Match

© Copyright 2007 InaPlex Limited See the tutorial movies for details and demonstration of each of these matching techniques

© Copyright 2010 InaPlex Inc THANK YOU