Executing Matching Strategies

Hi.
Im learning the matching mode in datamanager and trying to execute a matching strategy.
1. I have created a transformation to convert X value to Y of description.
2. I have created a rule based on my transformation.
3. I created a strategy and assigned the rule to it.
Now while trying to execute the strategy from the menu Records->Matching->Execute-> I find many options in it.
I couldn' get what are all those options.
Selected vs. Selected
Selected vs. Results
Selected vs. All
Results vs. Results
Results vs. All
All vs. All
Can anyone explain me with an example?
Regards
Bala
Edited by: Balachandar P on May 5, 2010 2:10 PM

Hi Balachandar,
How is Transformation and Rules effectively used in this case?
See it depends on your requirement, you can use Rules without use of transformation.
Without Transformation:
e.g. if you are finding duplicates for Material No, you can select property Fields = Material No directly while defining Rule and then include this rule into your Strategy which will find duplicates if there are two records with same Material No. Since Material No is usually Integer as such i think we don't need Transformation here.
With Transformation:
e.g. if you are finding duplicates for Company Description, you will need here Transformation if required.
I mean if in my Repository there are Company Description for 1 record is ABC Pvt. Ltd. , for 2nd record it is ABC Private Limited and for 3rd record say it is ABC Pvt. Limited. If i don't make use of transformation and make use of Rule only where i define Fields = Company Description and then include this Rule into Strategy. So when i execute Strategy these 3 records will not considered as duplicates but considered as unique records which is not correct.
So in order to recognize that these three records are duplicates but not unique records we have to make use of Transformation where i create a transformation say XYZ and in Substitutions pane will write:
From To
ABC Pvt. Ltd ABC Private Limited
ABC Private Limited ABC Private Limited
ABC Pvt. Limited ABC Private Limited
which means for all these three records Company Description are same. Then while defining Rule select this transformation as Fields = XYZ   and then include rule into Strategy. So on execution Strategy i will come to know that these 3 records are nothing but are duplicates.
Regards,
Mandeep Saini

Similar Messages

  • Control core dump behavior for executables matching a pattern

    Systemd directs me to coredump.conf(5) for the gory details on configuring core dumps but even after reading that it's not clear to me if there's a way to have core dumps only generated for certain executables. Ideally, I'd like to pattern match the full path to an executable to determine whether or not a core dump should be generated.
    Can this be done? How?

    Which database version are you working with....????
    Some alternatives might work for example, xdbUriType
    begin
    DBMS_XMLSCHEMA.registerSchema(
       schemaURL  => 'http://www.myserver.com/myapp/1.0/xsd/xmlschema.xsd',
       schemaDoc  =>  xdbURIType('/home/myapp/1.0/xsd/xmlschema.xsd').getClob(),
       local      => FALSE,  -- local
       genTypes   => TRUE,   -- generate object types
       genBean    => FALSE,  -- no java beans
       genTables  => TRUE    -- generate object tables
    end;
    / or bfilename
    create or replace directory XMLDIR as '&XMLDIR/xsd'
    -- alter session SET events = '31098 trace name context forever';
    declare
      V_FILENAME  VARCHAR2(700) := 'xmlschema.xsd';
      V_XMLSCHEMA XMLTYPE := xmltype(bfilename('XMLDIR',V_FILENAME),nls_charset_id('AL32UTF8'));
    begin
      dbms_xmlschema.registerSchema
        schemaurl       => V_FILENAME,
        schemadoc       => V_XMLSCHEMA.getClobVal(),
        local           => TRUE,
        genTypes        => TRUE,
        genBean         => FALSE,
        genTables       => TRUE,
        enablehierarchy => DBMS_XMLSCHEMA.ENABLE_HIERARCHY_NONE,
        owner           => user
    end;
    /

  • Issue in getting score while executing the matching strategy

    Hi,
    On executing the matching strategy, even if there is a duplicate count of zero in the record pane, some score is calculated. I want to know how does the system get that score even if there is no potential duplicate in the matches pane. 
    Also we are facing an issue - whenever the matching strategy is executed, some score is calculated which does not match with any one of the individual score in the match pane.
    Can anyone guide me what might be the reason?
    Regards,
    Indraveer

    Hi Indraveer,
    On executing the matching strategy, even if there is a duplicate count of zero in the record pane,
    some score is calculated. I want to know how does the system get that score even if there is no
    potential duplicate in the matches pane.
    First i want to clarify how this score getting calculated.
    In the record pane the three extra coloumn tell about the result about matching strategy
    Count : this represent the no of record matches with the selected record based on the matching strategy executed
    Class : This defines
    Score : this contains the sum of score of all rules that contain in strategy i.e. You know in rules tab we define the value for
    SUCCESS
    FALIURE
    UNDEFINED
    So in  the score section it calcilates the score of each rules that you included in executed strategy.
    For Example
    Your 1st rules contain values like
    SUCCESS :2
    FALIURE  :1
    UNDEFINED:0
    Your 2nd rules contain values like
    SUCCESS :3
    FALIURE  :1
    UNDEFINED:0 (this score if contain NULL values and data manger unable to execute the matching)
    Now ypu included these two rules in strategy and define
    High threshhold : 5
    Low threshhold :4
    Now you execute the strategy
    I will consider yr case that no one record matches .In this case  score section will contain value 2 because it fails in matching
    any rules so it get  1 for rule1  and 1 from Rule2.
    Hope it clarifies yr doubt.
    Also we are facing an issue - whenever the matching strategy is executed, some score is calculated which does not match with any one of the individual score in the match pane.
    After Whatever i understand from yr statement,this will be the case when you have multiple rules  ans some record  succeed in all rules while some are succeed in one and fail in second rule.
    For example :
    we have 3 record in table in which first one matches with both record for all rules where as second  record matches with some record for first rule and some for second rule  so their total score  calaculate accordingly
    and third record matches with some reord  for second rule  and some record with first rule so their score will calculate automatical;ly.
    so in this case when u select  first record  in record pane and  open match pane you will see other two record with different score as this score shows there personal score after executing matching strategies.
    Hope this will help you to clarify yr doubt .
    For further reading please check the data manager reference guide  on page 500.
    Thanks,
    Sudhanshu

  • API for Matching Strategy

    Hi All,
    Does the MDM Sp04 has API to execute a Matching Rules/Strategy in MDM and get back the result set.
    I found following classes in MDM in API but there is no documentation what they are and how to use them:
    CMChangeNormalizationInfos  
    CMChangeRuleInfos  
    CMChangeStrategyInfos
    Abhay

    ExecuteMatchingStrategyCommand
    A command to execute a matching strategy for internal source records. 
    ExecutetMatchingStrategyForNewRecordValuesCommand
    A command to execute a matching strategy for external source records. 
    RetrieveMatchedRecordsCommand
    A command to retrieve the records that matched the source record for a matching strategy. 
    RetrieveMatchingResultCommand
    A command to retrieve the matching results for a matching strategy. 
    RetrieveMatchingStrategiesCommand
    A command to retrieve the list of matching strategies. 
    TerminateMatchingStrategyCommand
    A command to terminate a running matching strategy. 
    Use RetrieveMatchingStrategiesCommand to get the stretagies available in MDM
    RetrieveMatchedRecordsCommand get the records that match the stretagies.
    and then loop through all to work.
    I have also started working on same. I believe this is the way to do it.
    Will update once i am done. and if you have finished, let me know how you did:-)

  • Match code : value #

    Hello all,
    I wish to delete value '#', when I execute match code of master data on query.
    This value is display, even if this value never exist in my infoprovider.
    Someone have a solution ?
    Regards,
    Sebastien

    Hi Sebastien,
    If i have understood your question right, then you want to remove the "#" from your query/report output?
    What you can do is edit your master data text with blank spaces, where ever you do not have any entries. Or you will have to write a VBA Macro code.
    Check this thread, its something similar.
    replacing '#'-sign for 'not assigned' in queries
    If i have understood it wrongly, please let me know what you are looking for.

  • Matching New records - Without Record ID

    Hi,
    Can you help me with this?
    I am trying to get a list of matching/duplicate records for a new record which is not added to MDM yet. (ie., no Record ID for the new record)
    The RetrieveMatchedRecordsCommand cmd is expecting the source record id.
    The RetrieveMatchingResultCommand cmd getmatchingresults returns null (as specified in the java doc). But this command gives me the number of duplicates by getMatchCount() class. If I can get the duplicate records (existing in MDM) also, it solves the purpose.
    Have you worked on similar scenario?
    Cheers,
    Prabhu

    Hi Prabhu,
    Thanks for the feedback, I am happy to help !
    RetrieveMatchingResultCommand is used when you run matching for multiple source records (already exist in MDM), for iterating through match results of each source record.
    Please see farther info at
    Re: MDM Repository gets hanged while executing Matching Strategy
    Regards
    Orit

  • Question of Data Matching

    Dear All:
    In MDM, Data Manager -> Matching Mode, there are different ways to execute Matching Strategy, but we can't tell the differences between
    1, Selected VS Results
    2, Selected VS All
    because both the two ways return the same result.
    Such as total 1000 data, via search parameter we get 100 results, in the result set we select 10 records, the we choose both above two ways, the matching results are both 10 vs 100. But we expect via "selected vs All" should get 10 vs 1000.
    Anyone know the difference or met the issue?
    Any info will be highly appreciated!
    Thanks in advance!
    BR,
    DH

    Hi David,
    As per your question on Matching Stratergy:
    1. Selected Vs Selected - Selected records will be matched with each other.
    2. Selected VS result - Matches the selected records with the records set derived from the search criteria.
    3. Selected VS All - Matches the selected records with all records in the repository.
    4. Result VS Result - Matches all records that result from the search criteria
    5. Results VS All - matches all records that result from the search criteria with the records in the repository.
    Selected VS Result  - should give you 10 VS 100
    Selected VS All should give you  - 10 VS 1000.
    The 2nd one is not working fine may be because, you are selecting records(10) out of the Searched Records( 100). And it is understanding All as 100 as the record set is already been searched and the selection of records is made out of the seacrhed records.
    But it should not be like this.
    Hope it helps..
    Thanks and Regards
    Nitin jain

  • Matching Scenarios

    Hi guys,
    I like to know the features and improvement holes in SAP MDM regarding data quality management. For example, If we have Customer name like George and other record is also the same Customer but written differently like Gorge. I think here SAP MDM fails to find duplication records by their Soundex.
    Second improvement hole is like if I have a repository where I have maintained 100 of users and user roles. Is it not like awful I have to repeat them again in one other repository.
    Questions.
    1. Any recommended reading where I can find such improvement holes in SAP MDM 5.5
    2. User management problem for several repositories.
    3. Matching with Soundex feature like we find normally in RDBMS "Oracle"
    Regards,
    Naeem

    Hi Naeem,
    The Problem of Soundex can be solved within MDM by using the Transformation feature.
    - In the MDM data manger under the matching mode,you have a tab for Transformation.
    - Here you can create Transformations which will identify George and Gorge as identical duplicates.
    - You need to transform Geoge To George,This will make the transformation only virtual and not in reality,but however MDM will recognize them in the Data manager and select them as possible dupliacates.
    - By given a high score.
    - The only disadvantage in using this feature is that if you have many records with this kind of transformations,you will have to manually do it for each,before running the Strategy.
    Kindly refer the below Link,to understand how this works.
    MDM Matching Strategies for Master Data Consolidation
    Regarding reusing the created Roles and Users in one rep into another.
    - There are 3 different ways to transport your Roles and Users from one rep to another.
    - Archieve/Unarchieve, Duplicate Rep, and Export/Import Schema.
    - The Export/Import schema option is less preferred as the roles and the users will get transported however their pwd if set any may get resetted.
    - However with the Archieve and Duplicate option you will get all the Roles and users replicated.
    - The drawback being ,there is no option in MDM to transport just the Role and Users,you entire Repository structure will get transported.
    - So if you want to reuse the same roles on to a differnt rep,then manul work will involve.
    Regarding Data Quality, MDM's latest release 7.1 has additional facilities to handle data quality aspects in MDM.
    Have a look at the Presentation which explains all the new upcoming features to be included in MDM 7.1:
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/101fdef1-7776-2b10-0ab9-8d67c1f3e1d7
    Hope It Helped
    Thanks & Regards
    Simona Pinto

  • Lack of restriction on Matching Mode Pane

    Hi,
    is there any standard (or non-standard) functionality to restrict the different Tabs in the Matching Mode Pane in the MDM Data Manager?
    I couldn't find any functionality in the MDM Console to restrict that pane.
    e.g even a user with only read rights to all tables and no execution rights is able to delete and change matching strategies. This is very delicate information. So how can you forbid this for certain users?
    Thank you for the answers
    Best regards
    Nicolas

    Hi,
    is this going to be an enhancement in the standard in SP05?

  • Defaut XML file  for matching strategy

    Where is the default xml file loacted for loading the varibles (attributes and score) into the matching strategy algrithim..  Can any one send me a copy of the xml file as a template.  We have looked for the delivered xml template and cannot find it.

    Hi Ted,
    Please check SAP note 779619. This note describes how to customize the standard matching strategies. The customizing XML files you are looking for are attached to this note, too.
    Regards,
    Wolfgang Dittrich

  • Error in Release procedure for PO

    Hi
    I have created a release procedure for Purchase groups and plants. But now I want to add a new Purchasing group to the same strategy. How to do this.

    Hi Garapati,
    Release strategy is configuration in customisation screen. Do not merely do assignment of object via CL20N or CL24N. Though assigning the object would work, but is better to do it in customisation.
    Go to this path: -
    SPRO>IMG>Materials Management>Purchasing>Purchase Order>Release Procedure for Purchase Orders>Define Release Procedure for Purchase Order (Execute)-->Release Strategies
    Go to: Position>Identify the Group> Identify the Release Strategy code
    (How to know what is the release strategy code? In the PO where a release strategy for this value and characteristic is triggered, you can go to the Header-->Release Strategy tab, you would be able to see that the release strategy is triggered. Simply remember the release strategy code. If you already know the code, ignore this step)
    When the search is complete and located the right release strategy that you want to amend, select it and click on Details.
    Inside, go to Classification. Check that this release strategy contain the characteristic that you want to amend. You would be able to see the Characteristic "Purchasing Group" already maintained. Click on Purchasing Group line and click on "Add rows" icon below, then key in the the Purchasing Group value that you want to add.
    Hit Back, and then Save this customisation.
    Now, the PO release strategy will trigger the Purchasing Group you just added if the PO details entered matched the Purchasing Group, Plant and Document Type value that you maintained for this release strategy.
    Hope this helps.
    Rgds.

  • MDM Data Manager step-by-step process with an example

    Hi All,
    I recently started reading MDM. I am clear with MDM-Console concepts. But I have problem with MDM Data Manager. I am confused with data entries in qualified tables, work flows(using microsoft studio), Matching mode- rules(High treshold, low threshold) etc.. I read material posted in forums- but still I am not clear.
    I need a step-by-step process for data entries with *examples*. A good example which covers all Data Manager concepts. PDF's with screen shots, videos any thing would help.
    Please help me......It would be of great help.
    Thanks in Advance.
    Suchir

    Hi Suchir ,
    MDM 5.5 has 4 MDM clients to perform 4 main functionality on the MDM master records.
    - Console- This is where all the Administrative work is performed
    - Data Manager- This is where the actual maintainence work is done on the master data like consolidation deduplication etc.
    - Import manager- Thsi is from where the source matser records are taken into MDM repoistory
    - Syndicator- This is from where teh consolidated master data is send back to the target systems.
    MDM Data Manager is the heart of MDM
    The activities that can be performed in the MDM Data manager are:
    - Data Consolidation
    - Data Validation
    - Data Deduplication
    - Data Assignment
    - Data Governanace
    etc......
    Qualified Table:
    - Qulaified tables are used to store relational records where one field value is determining the other field or fields value.
    - Qualified tables are maintained in Console and can be viewed in Data Manager
    - Qualified Table are viewed under a separate section in Data Manager in the right hand side.
    - Qualified table has Non qualifiers and Qualifiers.
    - Non qualifiers can be seen in the  Qualified table and in the linking Qualified field
    - Qualifiers can be seen separately under the Qualified section in the data manager
    Kindly refer the below link to know more on this:
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00a15239-684e-2b10-b8ae-b936b7d1c1fe
    Workflows
    - Workflows are designed in MDM for Governanace
    - You can create the MDM workflow using the MS Visio 2003 stencils in the MDM Data manager in the record mode under the workflow table
    - The saved workflow in DM can then be executed either mnaully or automatically based on teh trigger actions
    - The trigger action for teh MDM wf are record Add,Update,Import,Manual
    Kindly refer the below link to know more on this:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/60559952-ff62-2910-49a5-b4fb8e94f167  (MDM Workflows Overview)
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/90990743-91c0-2a10-fd8f-fad371c7ee40  (Demo of MDM Workflows)
    Matching Mode
    - This mode is exclusively for Master data deduplication
    - We need to create Rules,Strategies,Transformation in MDM data manager in teh record mode
    - Then you need to run these strategies on the selected records
    - Based on your score and threshold set in the strategy MDM will identify duplicate records
    - This score will be seen in teh Matching mode
    - Colour coding is used along with scores to find out dupliactes
    - Green - 100%dupliacte Blue- 50?% Red- No duplicate
    Kindly refer the below link to know more on this:
    /people/michael.reil/blog/2006/05/18/mdm-matching-strategies-for-master-data-consolidation (matching merging in mdm)
    Hope It Helped
    Thanks & Regards
    Simona Pinto

  • What about the performance of MDM???

    when I execute 8 matching strategys at the same time, at this time I will could not to do other thing,I almost can not get the response from mdm!

    From What i have seen, yes, if you are performing matching on data manager and execute a query on portal the response either takes eternity or you get a locking exception.
    in 7.1 the worst part was matching on tuple values which has improved over the hot fixes. I am working on mdm71 since start of ramp up.
    What i can suggest is, when you run matching strategies, add some search filters to it. that will reduce your target records and would increase your performance on matching execution.
    btw, we had the performance issue while running 1record against 40000 records and only 1 matching strategy, running 8....definately not something that some one should test performance on. I don't think anything would help:-). Though would strongly suggest to check the KPIs of performance on matching with SAP directly as there are no such KPI's available in documents.
    Regards,
    Nitin
    Edited by: Nitin Mahajan on Jun 25, 2009 4:30 PM

  • SAP content integrator

    Hello,
    IN MDM 3.0 we hade Content integrator for matching stretegy.
    what about MDM 5.5?
    as in MDM 3.0 it was seperate installation of SAP CI
    in MDM 5.5?
    Appreciate your help
    Regards
    Ken

    Hi Ken,
    You are right. In older versions of SAP MDM 3.0, the matching statergy was executed by using Content Integrator. You can know about Content Integrator in the link below:
    http://help.sap.com/saphelp_mdm300/helpdata/EN/9c/860a3369454f409cc61215d8b76bd2/frameset.htm
    Configuration of Matching-Strategies for SAP Master Data Management :
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/1139df90-0201-0010-0cb3-e2f96a400070
    However, with MDM 5.5, you have the provision of executing the Matching Stratergy in Data manager itself. You do not require separate installation for that. To know about the Matching Stratergy in Data manager, you can refer to the link below:
    http://help.sap.com/saphelp_mdm550/helpdata/en/43/e0677c82b40a2ee10000000a11466f/frameset.htm
    Go to matching Mode. You will find the details of executing the Matching Stratergy in MDM. You have to define rules, stratergy etc and then you can run them on Records present in MDM so find out potential duplicates.
    For other details, you can refer the foll links:
    SAP Network Blog: MDM Matching Strategies for Master Data Consolidation:
    MDM Matching Strategies for Master Data Consolidation
    How to Identify Identical Master Data Records Using SAP Master Data Management 5.5 SP4 (NW7.0):
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/909108b0-64a1-2910-c39d-bcd63a012f1d
    Hope this info helps.
    Thanks and Regards
    Nitin Jain

  • MDM Performance problems

    Hi All:
    We are suffering terrible connections problem when we tried to connect using MDM Data Manager to the MDM Server. To give an example, sometime we wait for more than 10 minutes to complete the connection and the repository load. This obviously would make sense if we would have all the records loaded and we would have an enormous repository to be loaded; however this is not the case.
    Have you ever performed repository loading problems or any other sort of performance problem. How are you handling it? What sort of best practices have you implemented?
    Kind regards
    Gonzalo Perez-Prim

    Have you sized your MDM Server properly?
    MDM Sizing guide is available in Service Market place.
    For running client applications, I would recommend atleast 2 Gb ram.
    CPU Consumption is high when you are executing some matching strategies or Import Manager.
    If the repository has lot of binary data(imange) then the archiving would take a lot of time. We are experiencing an hour to archive a repository and 20 to 25 minutes to load the repository.
    This is after the fact that the sizing was done properly.

Maybe you are looking for