After you configure the match model, you can define a job to match records and another job to merge records or a single job to match and merge records. The match and merge job depends on the match and merge process. When you run a match and merge job, it completes the match and merge process.
Additionally, you can run a match and merge job exclusively to update match explainability metrics based on the most recent match jobs. After the job completes, the match analysis and explainability dashboard in your business application shows the latest metrics. Alternatively, you can update the metrics as part of a regular match and merge job. However, if you want the job to complete faster, you can exclude the metrics update. When you configure a job to update the match explainability metrics, you can also choose to update large cluster metrics.
When you configure a job to update the match explainability metrics, you can also update the large cluster metrics. Large clusters form when a large number of records match one another. You can update the large cluster metrics to identify and analyze these clusters, or exclude them to complete the job faster.
A process is a Cloud Application Integration asset that is a set of instructions to automate a business requirement. For more information about processes, see Informatica Cloud Application Integration Design.
When you define jobs to match and merge records, you can choose the following process types:
Match and Merge
Identifies matching records, creates record pairs, and automatically merges them depending on the merge configuration. Based on the merge configuration of the model, the process merges the records automatically, queues the records for manual merge, or skips the records as not a candidate for merge. Optionally updates the match explainability metrics, and can also update the large cluster metrics.
Match Only
Identifies matching records and creates record pairs. If you select the Match Only process, you can view and analyze the number of record pairs that automatically merge or require manual review. You can then decide whether you want to enhance the match configuration. Optionally updates the match explainability metrics, and can also update the large cluster metrics.
Merge Only
Merges record pairs that are identified by the match process for automated merge. You can choose the Merge Only process for the existing matched records.
Reset the Matched Records
Resets the matched records that are not yet merged and makes the records available for matching again. You can reuse the records multiple times for matching. For example, if you publish a new match model, you can choose to rematch the matched records that are not yet merged.
Update Match Explainability Metrics
Updates the match explainability metrics, including large cluster metrics, on the match analysis and explainability dashboard based on the most recent match jobs. If no match job has run, the metrics don't appear.
Run a match and merge job after you complete running the ingress jobs to load all your data. If you run a match and merge job after every ingress job, data that has already undergone matching goes through the match process again.
If declarative rules aren't configured properly or the quality of data is poor, a match job can generate excessive match pairs that might affect the performance of your organization. To prevent excessive match pair generation, MDM SaaS limits the number of match pairs a match job can generate. When the match pairs exceed the limit, MDM SaaS fails the job. Modify the declarative rules or enhance the quality of the data before running the job again.
For more information about generating fewer match pairs, contact Informatica Global Customer Support.
After you run match and merge jobs, you can monitor the status of the jobs on the My Jobs page. For more information about monitoring jobs, see Monitor MDM SaaS.
Note:
You cannot run two match and merge jobs in parallel for a business entity.