Siebel Data Quality Administration Guide > Configuring Data Quality >

Configuring a New Field for Real-Time Data Matching


When using the Oracle Data Quality Matching Server for data matching, there are a number of steps involved in configuring a new field for real-time data matching. Use the following procedure to configure a new field for data matching. This procedure shows how to add a new field called Position when matching Contacts.

To configure a new field for real-time data matching  

  1. In your Siebel application, navigate to the Administration - Data Quality screen, then the Third Party Administration view, and add the vendor field mappings for the new business components. For example:
    1. Select the Vendor shown in the following table:
      Vendor Name
      DLL Name

      ISS

      ssadqsea

    2. Select the business component operation shown in the following table:
      Business Component Name
      Operation

      Contact

      DeDuplication

    3. Add the field mapping shown in the following table:
      Business Component Field
      Mapped Field

      Position

      MyPosition

  2. Configure the integration object.
    1. If using the old synchronizer, modify the Identity Search Server synchronization Integration Object by adding the new fields to it. In this example, you must modify the ISS_Contact to add the new Integration Component Field as shown in the following table:
      Name
      Data Type
      Length
      External Name
      XML Tag

      Position

      DTYPE_TEXT

      50

      Position

      MyPosition

      NOTE:  For a Contact, you must modify the ISS_Contact integration object. For an Account, you must modify the ISS_Account integration object. For a Prospect, you must modify the ISS_List_Mgmt_Prospective_Contact integration object.

    2. If using the new synchronizer, then do the following:
      • Add the new field to the Synchronize Integration Object. In this case, 'SyncContact' IO. For the contact address field, add it to the 'Contact_INS Personal Address' Integration Component.
      • Add the new field to the 'DQ Sync Services' user property. In this case, 'Contact_DeDupFlds'. For the contact address field, add it to the 'Contact_INS Personal Address_DeDupFlds' user property.
      • Add the new field length to one or both of the following 'DQ Sync Services' user properties:

    'Contact_ExtLen'

    'Contact_INS Personal Address_ExtLen'

    NOTE:  It is mandatory that you maintain the same sequence that is detailed in the sdf file. Also make sure that the address fields are grouped together at the end of the sdf file.

    • Enter the new record length into the 'Contact Record Length' user property. This user property holds a total of all the field lengths in 'Contact_ExtLen' and 'Contact_INS Personal Address_ExtLen'.

      NOTE:  ISSDataSrc must be added to the OM - Named Data Source component parameter for the UCM object manager and EAI object manager components.

  3. Modify the SDF file (SiebelDQ.sdf):
    1. Add the new fields to the IDT table in IIR:

      In the following example for the old synchronizer, you must add the new Position field to the IDT_Contact. For example:

    create_idt
              IDT_CONTACT
    SOURCED_FROM      FLAT_FILE
                        BirthDate                    w(60),
                        CellularPhone                w(60),
                        EmailAddress                 w(60),
                        NAME                         w(100),
                        HomePhone                    w(60),
                        MiddleName                   w(100),
                        Account                      w(100),
                        City                         w(60),
                        Country                      w(20),
                        PrimaryPostalCode            w(20),
                        State                        w(20),
                        StreetAddress                w(100),
                        RowId                        w(30)
                        SocialSecurityNumber         w(60)
                        MyPosition                   w(60)
                        WorkPhone                    w(60)
    SYNC_REPLACE_DUPLICATE_PK
    TXN-SOURCE NSA
    ;

    In the following example for the new synchronizer, you must add the new Position field to the IDT_Contact.

    create_idt IDT_CONTACT
    sourced_from odb:15:ssa_src/ssa_src@ISS_DSN
    INIT_LOAD_ALL_CONTACTS.BIRTHDATE            BirthDate             V(60),
    INIT_LOAD_ALL_CONTACTS.CELLULARPHONE        CellularPhone         V(60),
    INIT_LOAD_ALL_CONTACTS.EMAILADDRESS         EmailAddress          V(60),
    INIT_LOAD_ALL_CONTACTS.NAME                 NAME                  V(100),
    INIT_LOAD_ALL_CONTACTS.HOMEPHONE            HomePhone             V(60),
    INIT_LOAD_ALL_CONTACTS.MIDDLE_NAME          MiddleName            V(100),
    INIT_LOAD_ALL_CONTACTS.ACCOUNT              Account               V(100),
    INIT_LOAD_ALL_CONTACTS.CONTACT_ID  (pk1)    RowId                 C(30),
    INIT_LOAD_ALL_CONTACTS.SOCIALSECURITYNUMBER SocialSecurityNumber  V(60),
    INIT_LOAD_ALL_CONTACTS.MYPOSITION           MyPosition            V(60),
    INIT_LOAD_ALL_CONTACTS.WORKPHONE            WorkPhone             V(60),
    INIT_LOAD_ALL_CONTACTS.CITY                 City                  V(60),
    INIT_LOAD_ALL_CONTACTS.COUNTRY              Country               V(20),
    INIT_LOAD_ALL_CONTACTS.POSTAL_CODE          PrimaryPostalCode     V(20),
    INIT_LOAD_ALL_CONTACTS.STATE                State                 V(20),
    INIT_LOAD_ALL_CONTACTS.STREETADDRESS        StreetAddress         V(100),
    INIT_LOAD_ALL_CONTACTS.ADDRESS_ID  (pk2)    ContactAddressID      C(60)
    SYNC REPLACE_DUPLICATE_PK
    TXN-SOURCE NSA
    ;

    1. Modify SCORE-LOGIC in the IIR search definition:

      A set of field types are provided that are supported by Match Purpose. For Contact Match Purpose, the required and optional field types are shown in the following table:

      Field
      Required

      Person_Name

      Yes

      Organization_Name

      Yes

      Address_Part1

      Yes

      Address_Part2

      No

      Posal_Area

      No

      Telephone_Number

      No

      ID

      No

      Date

      No

      Attribute1

      No

      Attribute2

      No

      If you want the new field to contribute to the match score, add it to the SCORE-LOGIC section in IIR search definition. For example:

    search-definition
    ==================
    NAME=           "search-person-name"
    IDX=            IDX_CONTACT_NAME
    COMMENT=        "Use this to search and score on person"
    KEY-LOGIC=      SSA,
                    System(default),
                    Population(usa),
                    Controls("FIELD=Person_Name
                              SEARCH_LEVEL=Typical UNICODE_ENCODING=6",
                    Field(Name)
    SCORE-LOGIC=    SSA,
                    System(default),
                    Population(usa),
                    Controls("Purpose=Person_Name
                              MATCH_LEVEL=Typical UNICODE_ENCODING=6",
                    Matching-Fields
    ("Name:Person_Name,StreetAddress:Address_Part1,City:Address_part2,State:Attribute1,PrimaryPostalCode:Postal_area,MyPosition:Attribute2")

  4. Delete the existing system in IIR, and then create a new system using the new SiebelDQ.sdf file.

    For more information about creating a new system in IIR (which will hold all the IDT and IDX database tables), see the relevant documentation included in Siebel Business Applications Third-Party Bookshelf in the product media pack on Oracle Software Delivery Cloud.

  5. Reload the IIR system as described in Initial Loading of Siebel Data into Oracle Data Quality Matching Server Tables.
Siebel Data Quality Administration Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.