Skip to Content

A ‘Single Customer View’ or ‘Single Citizen View’ is the linking of customer data to provide an accurate and holistic view of any one customer across different channels and lines of business. One of the common ways to achieve this is to compare addresses of different customers and group them based on the common address.

The Address_MatchBatch Transform can be used to group together similar addresses. While comparing the address we want to compare “similar” addresses instead of going for “Exact” match. Each “Similar” address is given a score indicating the degree of Match.  An Exact match will yield a score of 100.

There is a specific option to cater to transposed letters like “ABCD” and “ABDC”.

/wp-content/uploads/2012/09/screen1_140564.jpg

If we select Check for transposed letters=Yes then the transform deducts half as many points for transposed characters as it deducts for other non-matching characters. This can be explained better with an example:

The input data has values “MATHURA” and MATHUAR” in the column mapped to Address Primary Name. The address Match score differs when we run the transform with Check for transposed letters=Yes and Check for transposed letters=No

/wp-content/uploads/2012/09/screen2_140565.jpg

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

  1. sapkrisboedge mac

    Hi Priya,

    Thanks for replay. I am Working on Buisness Objects Data Inegrator 11.7 Version. Can you please  solve below error..

    we need to update records in DB2 database table on AS/400 using Business Objects Data Integrator 11.7. Data integrator Designer version is 11.7.3 Drivers installed are iSeries ACCESS ODBC Driver 11.0.2,CLIENT ACCESS ODBC DRIVER 11.0.2.

    We are able to do the update for a single record, but while doing Bulk Update, we are getting below error message, Can anyone help on this.

    DBS-070401: ODBC DATA SOURCE Error Message for Operation : <[IBM][iSeries Access ODBC Driver]Driver not capable.> RUN-051005: Execution of for target failed. Possible causes: (1) Error in the SQL syntax; (2) Database connection is broken; (3) Database related errors such as transaction log is full, etc.; (4) The user defined in the datastore has insufficient privileges to execute the SQL. If the error is for preload or postload operation, or if it is for regular load operation and load triggers are defined, please check the SQL. Otherwise, for (3) and (4), please contact your local DBA.

    (0) 

Leave a Reply