Show TOC

Background documentationConfigure Matching for Business Partner

 

Within the process step matching, the data records to be consolidated are checked for possible duplicates. According to a configured threshold records are considered to be duplicates and are displayed as match groups in the attached match review.

Activities

To configure the matching for MDG, consolidation, run the Customizing activities under Start of the navigation path Master Data Governance Next navigation step Consolidation and Mass Processing Next navigation step Configure Matching End of the navigation path:

  1. To create the match configurations for the fuzzy matching run the Customizing activity Create Match Configurations for Fuzzy Matching.

    In this Customizing activity, you define and generate a match configuration that SAP HANA uses to match master data records when using fuzzy matching. This activity is only possible within a client allowing cross-client changes. Configurations created here are used during configuration of process templates when assigning step type matching and adapter fuzzy matching.

    Note Note

    SAP provides the standard match configuration BPMATCH1 that can act as template to help you to define and generate your own match configurations.

    End of the note.

    This Customizing activity calls the Web Dynpro application Match Configuration MDC_HDB_MATCH. You can use this screen to create, change, copy, and delete a match configuration.

    • Create match configuration

      1. To create a match configuration, choose New.

      2. On the General Data screen, enter a name in the Match Configuration field.

      3. Enter a description in the Description field.

      4. Enter the business object type in the Business Object Type field.

      5. Enter a name for the SAP HANA package in the HANA Package field.

        The SAP HANA Package is generated with this name in the SAP HANA database when the match configuration is created. After the generation of the package its name cannot be changed anymore.

      6. Enter an ABAP package in the ABAP Package field.

        Note Note

        Do not use a package from standard delivery but create a package using transaction SE80.

        End of the note.

      • On the Select Attributes screen, the attributes in the tables from the process model are presented in tree form. You can select the attributes that are relevant for matching in your match configuration.

      • On the Review and Generate screen, you can review your choices from the previous screens, and if necessary, you can go back to the previous screens to make changes.

      • The Generate button generates the match configuration. Before generation you must save the configuration.

      Note Note

      After generating the configuration you may maintain the rule set in the SAP HANA studio to meet your requirements.

      • The rule set can be found in the package used for creating the match configuration. The rule set naming convention is: <MatchConfigurationName>RULESET.searchruleset.

      • By default one rule is generated with all the selected match attributes with minimum fuzziness of 0.8. All attributes are equally weighted.

      • To update the Rule Set, edit the rule set in the repositories view. Editing in the repositories view is possible since SAP HANA Studio SPS09. Authorizations should be the same as for the project explorer view.

        1. Create a repository work space.

        2. Open the rule set in the package folder

        3. Edit the rule set to change rule property or column property and conditions, such as the minimum fuzziness value or weight of an attribute.

        4. Save and Activate your changes.

      • For more information see the documentation on the SAP Help Portal:

      End of the note.

      Note Note

      When the match configuration is transported to the target system, the HANA package name is not transported and the field will be blank. In Edit mode the configuration must be updated with the appropriate HANA package name, saved and generated in the target system.

      End of the note.

    • Edit match configuration

      To edit a match configuration, select the entry and choose Edit.

      Note Note

      If you change the Select Attributes section by adding or removing attributes you have to set the Re-generate Rule Setindicator. Any manual adjustment done on the ruleset has to be done on the regenerated rule set if intended.

      End of the note.

    • Copy match configuration

      To copy a match configuration, select the entry and choose Copy.

      In the Copy Match Configuration dialog box, enter the name of the target Match Configuration.

      Note Note

      After copying the configuration you may maintain the rule set in the SAP HANA studio to meet your requirements. To do so, proceed as described under Create match configuration.

      End of the note.

    • Delete match configuration

      To delete a match configuration, select the entry and choose Delete and OK.

      Note Note

      The match configuration is marked for deletion. To finally delete the match configuration run transaction MDC_HDB_MTC_DEL.

      End of the note.

  2. To configure the number of parallel processes and to specify an upper threshold run the Customizing activity Configure SAP HANA Fuzzy Search for Direct Matching. Adapting the number of parallel processes can improve the performance of the consolidation process.

    Note Note

    To use parallelization in SAP MDG, consolidation you have to set up an RFC destination:

    • To create the bgRFC inbound destination manually, the authorization object S_BGRFC with activity 02 and type 07 has to be assigned to you.

      1. Run transaction SBGRFCCONF.

      2. On the Define Inbound Dest. tab choose Create.

      3. Enter a name in the Destination field.

      4. Enter MDC_QUEUE_ in the Prefixes field.

        If you use a queue prefix other than MDC_QUEUE_ this has to be entered in the corresponding field as described below.

      5. On the Scheduler: Destination tab select the destination by double clicking on it.

        If the destination does not exists, proceed as described:

        1. Choose Create and on the bgRFC Configuration dialog box select Inbound.

        2. Enter the destination name into the Destination field and leave all other values as defaulted.

      6. In the Open Connections field enter the number of allowed parallel processes or queues you wish to be managed by this destination. This number also specifies the maximum of parallel processes to be configured during the step configuration.

    • If you do not create the bgRFC inbound destination manually the very first consolidation process will trigger the automatic creation of the inbound destination under prerequisite that the authorization object S_BGRFC with full authorization is assigned to workflow system user.

    For more information see http://help.sap.com/saphelp_nw70ehp2/helpdata/de/f0/225c3c60065627e10000000a114084/content.htmInformation published on SAP site

    End of the note.

    Note Note

    The upper threshold for matching is the value as of which two records are rated automatically as a match without having to be checked in the match review process.

    End of the note.

    1. Select New Entries.

    2. Choose a Match Configuration ID.

    3. In the Number of Processes field, enter the number of processes you want to be processed in parallel.

    4. If required enter the Prefix for Queue Name.

      Note Note

      If you use queue prefixes other than MDC_QUEUE_ these have to be entered in the Prefix for Queue Name field.

      End of the note.

    5. Enter the upper threshold in the Up.Thrsld field.

  3. To configure the Business Objects Data Services for BAS Adapter and to specify an upper threshold run the Customizing activity Configure Business Objects Data Services for BAS Adapter.

    • Business Objects Data Services

      See the documentation of Customizing activity Configure Business Objects Data Services for BAS Adapter and follow the link to check the Customizing settings under SAP BusinessObjects Data Quality Management and adapt if required.

    • Upper Threshold

      Note Note

      The upper threshold for matching is the value as of which two records are rated automatically as a match without having to be checked in the match review process.

      End of the note.

      To specify an upper threshold proceed as follows:

      1. Enter a Config. ID and an Adapter Config Description.

      2. Enter the upper threshold in the Up.Thrsld field.

  4. To import the predefined settings for SAP HANA smart data quality run the Customizing activity Import Predefined Settings for SAP HANA Smart Data Quality.

    In this Customizing activity, you can activate the BC Set CA-MDG-EE-BP_IMHANA_C01 MDG-BP Consolidation: IM in HANAcontaining predefined sets of table entries, that are required to run the process steps standardization and matching with the adapters for the SAP HANA smart data quality.

    The BC Set contains settings for the tables listed below. You can use transaction SM30 to configure some of these tables to fulfill your requirements. Be aware, that some settings are not to be changed. For details, see the description for each table.

    Standardization and Matching

    • SIMDQ_INP_FILTER IM in HANA Filter for input

      Settings to specify filters for standardization and matching. Records can be filtered out and do not take part in the corresponding process step.

      Note Note

      To ensure the correct processing of the consolidation process, the settings delivered by SAP are not to be changed.

      End of the note.

    Standardization

    • SIMDQ_ADDR_STG IM in HANA address related settings

      Settings to specify the address standardization, for example address formats such as Woodstr. versus Wood Street.

    • SIMDQ_OTHR_STG IM in HANA non-address settings

      Note Note

      The settings delivered by SAP are required for technical reasons. Changing these settings does not have any impact.

      End of the note.

    Matching

    • SIMDQ_CMPRSRC IM in HANA compare source settings for Match Policy

      Settings to specify the data sources to be considered for matching. The delivered settings compare process data with process and active data and do not compare active data with each other.

      Note Note

      To ensure the correct processing of the consolidation process, the settings delivered by SAP are not to be changed.

      End of the note.

    • SIMDQ_MTCADDRSTG IM in HANA address settings for the Match Policy

      Settings to specify the matching for addresses, such as the threshold.

    • SIMDQ_MTCFIRMSTG IM in HANA firm settings for the Match Policy

      Settings to specify the matching for firms, such as the threshold.

    • SIMDQ_MTCPERSTG IM in HANA person settings for the Match Policy

      Settings to specify the matching for persons, such as the threshold.

    • SIMDQ_MTCCSTMSTG IM in HANA custom component settings for Custom Match Policy

      Settings to specify the matching for ID numbers.

    1. To adapt the predefined settings, run transaction SM30.

    2. Enter the table in the Table/View field and choose Edit.