Matching Mode

Hi All,
When i work in matching mode, i am getting false results some times,False results might be due to
success,failure scores and High and low thresold scores what i gave in matching strategy.
Is there any rule to define sucess scores,High and low thersold scores?
Please share your knowledge.
Thanks
Narendra

Hi Narendra,
                    Matching is the most important phase when we are trying to remove the duplication among our data.
Some Important Terms and there Functions related to Matching and Merging Mode:
1. Normalization: When we remove the Special Characters as well as the Short forms from our data we say that the data is Normalized and this is used in Transformation technique.
2. Token: When we have to reduce the short forms they are known as Tokens.
3. Score : Score actually helps us to define the Result in the following ways:
u2022 Success :   If we find the duplicate fields it shows Success
u2022 Failure : If we do not get any Duplicate field we say it is a Failure
u2022 Undefined : If any of the field contains Null Value we say that it is undefined.
There are two types of Scores also:
u2022 Maximum Score
u2022 Minimum Score
Maximum Score and Minimum Score: The read-only Min Score and Max Score properties are calculated automatically by MDM based on the Success scores of ever matching rule included in the strategy, and allow you to set the values of Low Threshold and High Threshold properties to classify the results.
4.Difference between Equals and Token Equals:
u2022 Equals : Exactly matches the data
u2022 Token Equals: Fuzzy Matches are also considered.
5.Threshold: There are two categories of Threshold:
u2022 High: Records whose total score is greater than or equal to the High threshold score are included in the list of potential matches in the Matches tab and placed in the High match level.
u2022 Low: Records whose total score is greater than or equal to the Low Threshold score are included in the list of potential matches in the Matches tab and placed in the Low match level.
Hope this would be helpful!!!!!!!
If helpful do reward Points!!!!!!!!!!!
Regards,
Parul

Similar Messages

Transformation in matching mode in data manager

Hi ,
Can anyone tell me when should we do trasformation in data manager (matching mode)? How can we do it?
Can any one provide me example?
Thanks

Hi,
   Transformations is a first step that we need to do in matching and merging process in MDM data
   manager to eliminate the duplicates.
Generally the same data in different remote systems will be maintained differently according to their
naming conventions, but it does n't allow us to do deduplication in data manager.
We need to normalize the data in specific format so that we can go for deduplication on a specific field.
   To create transformation ,
   Select transformations tab in data manager
   Give name for transformation.
   Select the field on which you want to apply transformation.
   Create the substitutions .In substitutions we have From means original data and To means destination
   data and Token means whether source data has to be converted in token wise or not.
   After that create rule and include transformation there.
Hope it helps,
Reward points,if found useful
Cheers,
Narendra.M

Data Manager: Transformations( Matching Mode)

Hi All,
In Matching mode of data manager, I set some transformation. In preview field of transformation tab, data is changing as per in substitution.
But after merging it is not reflecting into the data( what I set in substitution, is not reflecting into the data).
What I have to do for this? Any other settings?
Please help....
Regards,
Nikhil

Hi Nikhil ,
You could use assignments in this case and build it accordingly :
in the DM ->assignments tab -> add an assignment -> give a it a name -> and in the assignment field tab click the ... that appears , this opens the assignemtn builder now use the functions provide and create this assignment
IF(IS_NOT_NULL(field name where INDIA is to be placed ),INDIA)
close the expression builder & in the table field row maintain the field name where you want the INDIA value to be placed.
In the record mode choose a record where this is to be replaced right click ,run the assignment -you get a success or failure message ,now if this is what you require then select all the records where you want this update & proceed.
Please let us know if your issue is solved , reward points too if so !
Regards,
Anita

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?

Data manager - Matching mode

Hi,
I am using MDM 5.5. and in Vendor deduplication I have created the rules and startegies. And in the matching mode the system gave me the list of HIGH possible duplicates. Is there a way that i can pull the data our from the data manager and send it to the user to confirm that this is the duplicate vendors.
Appreciate your quick reply
Thanks,
Suresh

Hi Suresh,
You can use APIs for this purpose.
Other, workaround is that you can use MDM Workflow. As i don't have MS Visio installed but think it should work.
See in workflow when your Merge step comes, you will come to know the scores and hence therefore can send these duplicate vendor records out of MDM.
I think for this there should be two WORKFLOW1: START>MATCH>STOP
WORKFLOW2: START->SYNDICATE-->STOP
During WORKFLOW1 MATCH STEP when a use Execute this step, he will come to know Duplicate records by SCORE and COLOR, SAY DURING MATCH STEP you have 10 records out of 40 which are duplicates, now you will select these all 10 duplicate records right click >Choose Workflow>Split records into a new JOB(WORKFLOW2).
So all these duplicate records will syndicate out of MDM as WORKFLOW2 contains SYNDICATE STEP.
Also after sending only duplicate records, you can complete WORKFLOW1 by sending it to next step STOP.
I don't have work-flow(MS-VISIO) installed, so cant test it at my end.
Just Check it and revert with Result if it helps, i think it should work else you can use APIs
Regards,
Mandeep Saini

Search tabs in Matching Mode

Hi All ,
Reference guide of MDM data manager page 484 says
There is also a search tab corresponding to the [Level]
column and free-form search parameters corresponding to the [Count]
and [Score] columns, which allow you to filter based on which records
have matches that may require merging.
Has any one tried this how these search tabs are enabled ?
Regards
Yogesh

Hi Yogesh,
I had also tried the same thing but didnt get any search tab for level and free form search for score and count. I think they might have mised out this feature and there are no special or extra configuration is required.
Regards,
Jitesh Talreja

ITunes Match on a NAS?

How do fellow Apple'ers,
Quick spec on what's being used at the minute:
-rMBP
-iPad Mini
-iPhone 4S
-Time Capsule
-ATV (don't know what gen you call it - the new one..)
-iTunes Match
Prospectively looking to add:
-A NAS
-Mac Pro on release (for no other reason than it will complete my life..)
So, what I'm looking to do;
-Have a NAS set as the main and only iTunes library (most likely set up as a 3rd party iTunes Server)
-Have iTunes Match see this iTunes Library (on the NAS), and upload for all devices to use in iTunes Match mode (including the rMBP)
Most other threads I've found basically say "point your rMBP to the NAS for the iTunes Server and it'll work" - which isn't what I want. I've had a play with this, but then the rMBP is seen as the 'host' for iTunes Match - therefore can't stream/cache songs - ie, when out of internet range, it can't connect to the NAS so hasn't any music cached on it.
Hope this makes sense to someone, and they can advise?
Much love,
Ash x

Presumably the Mac Pro will be resident on the network alongside the NAS?
iTunes Match requires a computer based iTunes library to act as the conduit to the Cloud.
The NAS is effectively a 'local Cloud', however it is unlikely that the NAS can host iTunes.
So the options are:
1. Use the Mac Pro iTunes library and the main conduit to the Cloud - periodically manually backup to the NAS, so the NAS can provide a local iTunes service; or
2. Configure the Mac Pro to always use NAS as the location of its iTunes library - a neat solution provided the NAS is always on.
In both options, once iTunes Match has completed its 'matching' / 'upload' the iDevices and rMBP can use Match as there source. A NAS with decent RAID configuration makes a superb local backup option.

After updating to ios 7, iTunes Match doesn't work on iPhone 4

I updated to ios 7 on my iPhone 4 last night.
I purchased iTunes Match today. Everything has been uploaded through my computer, and everything is fine on my computer's end. But when I open up my music app on my iPhone 4, I get a screen that says Loading iTunes Match... and it stays there for hours. Without ever having my music pop up.

I have the same problem which started after I upgraded to iOS 7. It works particularly bad on the iPhone 4. It is in "Loading iTunes Match" mode most of the time with no or very slow progress, and when it finally ends, the uploaded Playlists are never there, not one. "Loading iTunes Match" would restart again after leaving and restarting music, say 50% of the time. Not sure what really is being loaded and can't understand why it has to be reloaded so often.
I had a problem ticket with Apple Support, but the specialist asked for a series of screenshots documenting the start time of "Loading iTunes Match" and the eventual completion time. I told him to forget it because I had already spent too much time turning this and that on and off for so many times in so many days trying to listen to my own uploaded music and I did not want to fiddle around anymore. I have decided not to renew my iTunes Match service in November, and have since turned off iTunes Match on all my devices and gone back to syncing to keep things simple.
I also have Amazon Cloud Player which is working just fine for the purpose of having some kind of cloud access of my music. I will be renewing this $24 service this month for another year instead of iTunes Match.
Apple was supposed to be very good at software development, and for them not resolving a problem in a paid service since the rollout of iOS 7 is just disappointing.

Setting template start mode in java

In my stylesheet I have templates like this:
<xsl:template match="/" mode="query">

</xsl:template>
How do I pass a start mode to my XSLStylesheet in java?

Terrence,
Thank you for responding and confirming the issues I'm having with static addressing. As far as the example above, I do have the standard LEDs working correctly, however, the example I'm referring to above is from the JavaME samples using the GPIO Port for the LEDS, according to the Device I/O Preconfigured List you referenced:
GPIO Ports
The following GPIO ports are preconfigured.
Devicel ID
Device Name
Mapped
Configuration
8
LEDS
PTB22
PTE26
PTB21
direction = 1 (Output only)
initValue = 0
GPIOPins:
controllerNumber = 1
pinNumber = 22
mode = 4 (Push-pull mode)
controllerNumber = 4
pinNumber = 26
mode = 4 (Push-pull mode)
controllerNumber = 1
pinNumber = 21
mode = 4 (Push-pull mode)
So is the assumption that using GPIOPort for accessing the GPIO port for Device ID 8 as listed in the Device I/O Preconfigured list not supported?

Problem in Workflow matching step

Hi,
I am facing a problem in Workflow matching step. I have user kaushikb assigned to it.
Execution Type: Any Single, Assignee Type: User and Execution Type: Any Single.
Match Record Scope: Records vs Records, Strategy: MDM_NAME.
This Strategy: MDM_NAME is based on 3 rules: MDM_NAME1, MDM_NAME2 and MDM_NAME3.
MDM_NAME1 is done based on transformations MDM_NAME1[XFM], MDM_NAME2[XFM] and MDM_NAME3[XFM].
Now my problem is even after matching and merging a large number of records it is not going to
the next step. Do I need to match and merge all duplicate records? If the Matching process is rerun
the score becomes less as the same records are compared again. After this the link assume gets activated and then clicking it activates the next step.
Regards
Kaushik Banerjee

Hi Kaushik,
Match step is an Automated step in the MDM workflow.On selecting this step you need to mention the strategy that needs to run on the records to match them.When you reach the Match step you need to Perform the step to run the mentioned Strategy .
When you Perform the Match step it will display the Matching result provided you select the Matching mode in MDM data manager.
You can merge or not merge the matched records Once your Matching is performed by the system, You can move your Workflow to the Next step which is Process.
When you are selecting Any single as your execution type it means you have more tahn one user for executing this task but you want any single one of them to perform it.
So whenever you have selected Any single as the excution type for any process .The user accepting to perfrom the task needs to Accept the task .
So when User1 wants to perform the task he will have to select Accept and then proceed with the task.
When the owner of the workflow is testing the entire workflow he needs to Assume the task as he is not the Assigned user but the Assumed one.
So if you have build your workflows correctly and moving in step as explained you should be able to select the next step
You can follow the below link to understand the process better:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0be83e4-a1e6-2a10-c1be-8395ae948844
Hope It Helped
Thanks & Regards
Simona Pinto

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

What are the MDM Modes and explain them?

hi friends,
What are the MDM Modes
please explain each mode with examples?
thanks and regards,
ramu.

Hi,
There are five modes in Data Manager which are as follows:
1. Record Mode: When Data Manager starts, record mode is opened.It is the primary working view. From here, the content of the data can be
managed. We perform various operations like
a. Adding a record
b. Deleting a record
c. Searching a record. The search for a record in record mode can be started from the tree view located in the left area of the main window. The search parameters are shown here.
2. Hierarchy Mode: In this mode, the user of the Data Manager can view and change all hierarchies stored in the repository. The hierarchy table to be edited can be selected here. The tree view displays the tree structure of the hierarchy.
3. Taxonomy Mode: The taxonomy determines how records belonging to different categories are defined. Through a taxonomy, an attribute can be attached to a record. These additional attributes are defined for records, which belong to a certain category. An example of this could be personal data, which differs according to the role in the organization, and thus includes additional information.
The taxonomy mode can only be selected if there is a table of type Taxonomy in the repository.
4. Matching Mode: We can define transformations, substitutions, and matching rules u2014 and bundle these rules into matching strategies.
According to a matching strategy, for example, SAP net weaver MDM will calculate scores for the probability that specific records are duplicates. We can then compare potential duplicates and merge any objects that are in fact repeated.
In Rules Tab, we set up rules to automate the detection of duplicate master data.
In Strategies tab, we bundle rules into matching strategies to calculate the probability of duplicates.
A high matching score indicates that a data entry is likely a duplicate record.
5. Family Mode: In family mode, all existing records that are already assigned to a category can be subdivided into families. The taxonomy table in which the family definitions are to be stored is selected in the toolbar. Then the family can be selected in the tree view.
Regards
Richa

Workflow: Stuck at Automating matching

Hi,
I am using WF to assign some values to matched records. How it works is I have assigned a matchig straegy and said Record Vs All. And if the threshhold is between 95 and 100 assign Y to a field in this record.
Everything works fine except that I need it to make it completely automatic. In Match step in WF, as a requirement, I need to assign a user/role. So even after making Autolaunch as Immediate and Trigger Action as Record Add, the WF acks for action at Match step and does not go through... I am unable to remove User/Role at Match step as that is mandatory.
Does anyone have a workaround for this?
Regards,
Dev.

Hi,
Suppose you created two workflows as
1. start->Match-->Stop you can add this workflow on (Record add, Record Import, manuall etc)
2. start-->Assign>Stop
Using 1workfow In Matching mode you can check Score mean Corresponding to your threshold you can select all the records of score say 100 then right click workflows>add to job>2 workflow as soon as you launched 2 workflow it will asign the value Y to your only selected records.
you can not skip User/Role at Match Step. beccause only this user at Match step corresponding to your strategy score could add the records to 2 workflow
Hope it will Help you,
Rewards if Useful......
Mandeep Saini
Edited by: Mandeep Saini on Jun 12, 2008 6:59 PM

Different types of tables and modes

Hi Experts
What is the specification of different tables in console and different modes in data manager.
What is the major difference between them.
Can we create a table of one type in console and can use the same table in another mode in data manager, say if I create a taxanomy table and can I use it as the hierarchy mode in the data manager.
have fun..
Hari

Hi Hari,
Differnt types of tables in Console are :
Actually the Tables in Console are further categorized as :
Main Table and Sub table which include:
Flat Tables : It is a simple table consisting of record and fields ( rows and column) . In MDM Main table is always a flat table.
Hierarchy Table : A hierarchy table organizes information in a hierarchy, where each record is related to a parent record (even if the only parent is the root) and may also be related to sibling records and/or child records.
Taxonomy Table : A taxonomy is the classification scheme that defines the categories and subcategories that apply to a collection of records. Categorizing records enables you to isolate subsets of records for various organizing, searching, editing and publishing purposes.
Qualified Table : A qualified table in MDM stores a set of lookup records,and also supports qualifiers, u201Csubfieldsu201D that apply not to the qualified table record by itself, but rather to each association of a qualified table record with a main table record. MDM supports multiple simultaneous qualified tables.
Tables are also Categorized as Object Tables like :
Images : For storing Images
Sounds : For Sound File.
Videos : For storing Video Files .
Binary Objects : To store Binary Objects.
Text Blocks : To store block of text.
Copy Blocks : Stores block of text interpreted as a Copy.
Text HTML`s : Stores block of text interpreted as a HTML.
PDFs : To store PDF files.
There are various types of Special Tables also:
Image Variants : Used to define the structure
and format of each of the variants for each image. Each variant is a modified version derived from an original image; the original image is never modified.
Masks : In this defined subset of records are included in Mask i.e. in any scenario whether new records are added or deleted in the repository the records in the Mask remains the same unless edited by the user.
Families : Used to further partition main table records in each category into smaller groups based upon the values of other fields and/or attributes.
Relationships : Used to define each of the different record-level relationships. Each relationship can be either bidirectional (sibling) or unidirectional (parent-child).
Workflows : Stores the workflows of an MDM repository, where each workflow is stored as a record in the table.
Name Searches : Unlike Masks in case of Name search there are again a defined set of records but those records are selected on the basis of Search Selection. In this case if a record is added then the record is checked whether it fulfills the particular search criteria if it does than it is added to the Name serach else not.
Data Groups : Stores the hierarchy of data groups used to break the entire set of objects in the MDM repository into manageable subgroups.
There are various types of System Tables :
Roles : A single table named Roles. One of three tables used to implement MDM repository security and access control. Each role can selectively grant or deny access to any MDM function and to any table or field. This table is managed in the MDM Console and is not visible in the MDM Client.
Users : A single table named Users. One of three tables used to implement MDM repository security and access control. Each user can have one or more roles. This table is managed in the MDM Console and is not visible in the MDM Client.
Connections : A single table named Connections. One of three tables used to implement MDM repository security and access control. Contains an entry for each currently connected MDM client application, which can be terminated by the MDM Console user. This table is not visible in the MDM Client.
Change Tracking : A single table named Change Tracking. Allows you to specify the fields for which adds, modifies, and deletes should be tracked and stored in the Change Tracking table.
Remote Systems : A single table named Remote Systems. Used to define the different remote systems for import and export. Each specifies whether it supports inbound, outbound, or both. This table is managed in the MDM Console and is not visible in the MDM Client.
Ports : A single table named Ports. Used to encapsulate the logistical and configuration info for inbound and outbound processing of MDM data, for consolidation and distribution respectively. This table is managed in the MDM Console and is not visible in the MDM Client.
Links : A single table named Links. Used to specify the URLs that can be used as the target of an embedded browser in the Web tab in the MDM Client. This table is managed in the MDM Console and is not visible in the MDM Client.
XML Schema : A single table named XML Schemas. Used to identify the XML schemas for import and syndication. Each XML schema is the name of an .xsd file. This table is managed in the MDM Console and is not visible in the MDM Client.
Reports : A single table named Reports. Contains an entry for each report file generated by the various MDM repository operations, which can be accessed and viewed by the MDM Console user. This table is not visible in the MDM Client.
Logs : A single table named Logs. Contains an entry for the log files generated by the MDM Server, which can be accessed and viewed by the MDM Console user. This table is not visible in the MDM Client.
Data Manager:
Data Manager in simple terms can be stated as a place where we manage the data that is taken from various systems.
All the data that you take from all the various systems that a business is using is then taken into data manager, so that it could be cleansed and can be maintained easily in future.
There are basically four different modes in Data Manager:
1. Record Mode: This mode allows us to search, view and edit the records of any table in MDM repository. This is the mode that one uses most often, primarily to view and edit records in the main table and also to view and edit records in any of the sub tables.
2. Hierarchy mode. This mode allow us to view and edit the hierarchy tables in the MDM repository, including regular hierarchy tables, taxonomy tables, and the Masks table. Though we can also view and edit the records of a hierarchy table in Record mode, Hierarchy mode specifically allows us to edit the parent/child relationships and the sibling ordering of the hierarchy.
3. Taxonomy mode. This mode allows us to view and edit the taxonomy tables in the MDM repository. We usually use this mode to create and maintain the category hierarchy used in the repository, and to manage the attributes associated with each category and subcategory. Though we can also view and edit taxonomy tables in both Record mode (for searching) and Hierarchy mode (for editing the other fields of information associated with each category), Taxonomy mode is unique in that instead of focusing on the records of the taxonomy table, it allows you to create and manage the pool of attributes associated with the taxonomy table, and to assign attributes to categories on a category-by-category basis.
4. Matching mode. This mode allows us to identify and eliminate duplicate records within an MDM repository. When you view the main table in Matching mode, MDM allows you to perform u201Cmatching-and-mergingu201D on and against any or all of its records, using various user-defined criteria (like creation of Rules and Strategies) to decide whether or not records are potential duplicates.
5. Family mode. This mode allows us to view and edit the Families table, which layers a hierarchy of families upon the taxonomy hierarchy to further break down each category into smaller groups of main table records. We usually use this mode to partition the categories of the taxonomy hierarchy by the values of other fields and/or attributes, and then to associate family data (such as an image, a paragraph, and bullets) once with each family of main table records rather than each individual record.
Can we create a table of one type in console and can use the same table in another mode in data manager, say if I create a taxanomy table and can I use it as the hierarchy mode in the data manager.
The structure of the tables are defined in Console and those tables are then used in Data Manager, but if you have defined a table as a Hierarchy table you cannot use that table in Taxonomy Mode but you will be able to see all the tables in Record Mode.
Hope this would be useful...
If useful do reward points!!!!
Regards,
Parul

Matching Mode

Similar Messages

Maybe you are looking for